This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Content Examples Detailed Descriptions Mappings Profiles & Extensions R3 Conversions

7.4 4.4.1.420 Resource TestReport - Content ValueSet http://hl7.org/fhir/ValueSet/condition-ver-status

FHIR Infrastructure Responsible Owner: Patient Care Work Group

Maturity Level : 0   Trial Use Normative

Security Category : Business Compartments Use Context : Not linked to any defined compartments Country: World

A summary of information based on the results of executing a TestScript. 7.4.1 Scope and Usage The TestScript resource is used to define tests that can be executed on one or more FHIR servers. The TestReport resource defines how systems should encode the summarized results of executing a TestScript. The TestReport structure mirrors the TestScript concepts of having sections for setup, tests, and teardown. If present, these ordered lists should mirror the actions (either operations or assertions) of the referenced TestScript with a result code: pass, skip, fail, warning, or error. 7.4.2 Background and Context 7.4.2.1 Background Implementers should be familiar with the testing concepts and descriptions found in Testing FHIR before working with this resource. 7.4.3 Resource Content Structure

• UML Narrative
• XML
• JSON
• Turtle R3 Diff TTL
All

Structure Name Flags Card. Type Description & Constraints score Σ 0..1 decimal The final score (percentage of tests passed) resulting from the execution pass | skip | fail | warning | error TestReportActionResult ( Required ) message detail 0..1 uri A link to further details on

Official URL : http://hl7.org/fhir/ValueSet/condition-ver-status TestReport TU DomainResource Describes the results of a TestScript execution Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension				identifier Σ 0..1 Identifier External identifier name Σ 0..1 string Informal name of the executed TestScript status ?! Σ 1..1 code completed | in-progress | waiting | stopped | entered-in-error TestReportStatus ( Required ) testScript Σ 1..1 Reference ( TestScript ) Reference to the version-specific TestScript that was executed to produce this TestReport result Σ 1..1 code pass | fail | pending TestReportResult ( Required ) Version : 6.0.0-ballot3
active as of the TestScript tester Σ 0..1 string 2020-12-28				Computable Name of the tester producing this report (Organization or individual) issued Σ 0..1 dateTime When the TestScript was executed and this TestReport was generated participant 0..* BackboneElement A participant in the test execution, either the execution engine, a client, or a server type 1..1 code test-engine | client | server TestReportParticipantType ( Required ) uri 1..1 uri The uri of the participant. An absolute URL is preferred display 0..1 string The display name of the participant setup 0..1 BackboneElement The results of the series of required setup operations before the tests were executed action I 1..* BackboneElement A setup operation or assert that was executed + Rule: Setup action SHALL contain either an operation or assert but not both. : ConditionVerificationStatus operation 0..1 BackboneElement The operation to perform result 1..1 code
0..1 Flags : Immutable				markdown OID : 2.16.840.1.113883.4.642.3.166 A message associated with the result

This value set is used in the result assert 0..1 BackboneElement The assertion to perform result 1..1 code following places:

• ConceptMap: Translation source in Canonical Mapping for "Condition Verification Status" pass | skip | fail | warning | error TestReportActionResult
• Resource: Condition.verificationStatus ( (CodeableConcept / Required ) message 0..1 markdown A message associated with the result detail 0..1 string A link to further details on the result test 0..* BackboneElement A test executed from the test script name 0..1 string Tracking/logging name of this test description 0..1 string Tracking/reporting short description of the test action I 1..*

BackboneElement

A test operation or assert that was performed + Rule: Test action SHALL contain either an operation or assert but not both. 4.4.1.420.1 Definition operation 0..1 see operation The operation performed assert 0..1 see assert The assertion performed teardown 0..1 BackboneElement The results of running the series of required clean up steps action 1..* BackboneElement One or more teardown operations performed operation 1..1 see operation The teardown operation performed Documentation for this format

UML Diagram ( Legend ) TestReport ( DomainResource ) Identifier for the TestScript assigned for external purposes outside the context of FHIR identifier : Identifier [0..1] A free text natural language name identifying the executed TestScript name : string [0..1] The current state of this test report (this element modifies the meaning of other elements) status : code [1..1] « The current verification status of the test report. (Strength=Required) TestReportStatus ! » Ideally this is an absolute URL that is used to identify the version-specific TestScript that was executed, matching the `TestScript.url` testScript : Reference [1..1] « TestScript » The overall result from the execution of the TestScript result : code [1..1] « The reported execution result. (Strength=Required) TestReportResult ! » The final score (percentage of tests passed) resulting from the execution of the TestScript score : decimal [0..1] Name of the tester producing this report (Organization support or individual) tester : string [0..1] When the TestScript was executed and this TestReport was generated issued : dateTime [0..1] Participant The type of participant type : code [1..1] « The type of participant. (Strength=Required) TestReportParticipantType ! » The uri of the participant. An absolute URL is preferred uri : uri [1..1] The display name of the participant display : string [0..1] Setup SetupAction Operation The result of this operation result : code [1..1] « The results of executing an action. (Strength=Required) TestReportActionResult ! » An explanatory message associated with the result message : markdown [0..1] A link to further details on the result detail : uri [0..1] Assert The result of this assertion result : code [1..1] « The results of executing an action. (Strength=Required) TestReportActionResult ! » An explanatory message associated with the result message : markdown [0..1] A link to further details on the result detail : string [0..1] Test The name of this test used for tracking/logging purposes by test engines name : string [0..1] A short description of the test used by test engines for tracking and reporting purposes description : string [0..1] TestAction Teardown TeardownAction A participant in the test execution, either decline the execution engine, a client, or a server participant [0..*] The operation performed operation [0..1] The results clinical status of the assertion performed on the previous operations assert [0..1] Action would contain either an operation condition or an assertion action [1..*] The results of the series of required setup operations before the tests were executed setup [0..1] diagnosis.

An operation would involve a REST request to a server operation

[0..1] 4.4.1.420.2 Content Logical Definition The results of the assertion performed on the previous operations assert [0..1]

---

 

[1..*] 4.4.1.420.3 Expansion The results of the series of operations required to clean up after all the tests were executed (successfully or otherwise) teardown [0..1]

XML Template This expansion generated 17 Dec 2025

< <!-- from --> <!-- from --> <</identifier> < < <</testScript> < < < < < < < < </participant> < < < < < < </operation> < < < < </assert> </action> </setup> < < < < <</operation> <</assert> </action> </test> < < <</operation> </action> </teardown> </TestReport> JSON Template

---

Please refer to  

See the Testing FHIR - How Tos full registry of value sets for examples on working with this resource. defined as part of FHIR.

7.4.5 Search Parameters

---

Search parameters for Explanation of the columns that may appear on this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services. page:

Name Type Description Expression In Common

identifier Lvl	token A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System An external identifier for the test report TestReport.identifier further information
issued date Source	The test report generation date TestReport.issued source of the definition of the code (when the value set draws in codes defined elsewhere)
participant uri Code	The reference to a participant code (used as the code in the test execution TestReport.participant.uri resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
result token Display	The result disposition display (used in the display element of a Coding ). If there is no display, implementers should not simply display the test execution TestReport.result code, but map the concept into their application
tester string Definition	The name An explanation of the testing organization TestReport.tester meaning of the concept
testscript reference Comments	The test script executed Additional notes about how to produce this report TestReport.testScript ( TestScript ) use the code