This page is part of the FHIR Specification (v4.3.0: R4B -  STU). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4 R3
FHIR Infrastructure   Work Group | Maturity Level: 0 | Trial Use | Use Context: Not yet ready for Production use | 
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/report-result-codes | 
| Version: | 4.3.0 | 
| Name: | TestReportResult | 
| Title: | TestReportResult | 
| Definition: | The reported execution result.  | 
| Committee: | FHIR Infrastructure   Work Group | 
| OID: | 2.16.840.1.113883.4.642.3.718 (for OID based terminology systems) | 
| Source Resource | XML / JSON | 
This value set is used in the following places:
http://hl7.org/fhir/report-result-codes
This expansion generated 28 May 2022
This value set contains 3 concepts
Expansion based on TestReportResult v4.3.0 (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/report-result-codes
| Code | Display | Definition | 
| pass | Pass | All test operations successfully passed all asserts. | 
| fail | Fail | One or more test operations failed one or more asserts. | 
| pending | Pending | One or more test operations is pending execution completion. | 
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Lvl | 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 for further information | 
| Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) | 
| Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') | 
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application | 
| Definition | An explanation of the meaning of the concept | 
| Comments | Additional notes about how to use the code |