This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: 4 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/testscript-scope-conformance-codes
|
Version: 5.0.0 | |||
draft as of 2021-01-26 | Computable Name: TestScriptScopeConformanceType | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.3057 |
This value set is used in the following places:
The expectation of whether the test must pass for the system to be considered conformant with the artifact.
http://hl7.org/fhir/testscript-scope-conformance-codes
This expansion generated 26 Mar 2023
This value set contains 3 concepts
Expansion based on Test Script Scope Conformance Type v5.0.0 (CodeSystem)
Code | System | Display | Definition |
required | http://hl7.org/fhir/testscript-scope-conformance-codes | Required | All tests are expected to pass. Warning statuses are permitted. This is the default value. |
optional | http://hl7.org/fhir/testscript-scope-conformance-codes | Optional | All tests are expected to pass but non-pass statuses may be allowed. |
strict | http://hl7.org/fhir/testscript-scope-conformance-codes | Strict | All tests are expected to pass. Warnings are treated as a failure. |
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 |