Publish-box (todo)
FHIR Infrastructure Work Group | Maturity Level: 4 | Trial Use | Use Context: Country: World, Not yet ready for Production use |
Official URL: http://hl7.org/fhir/ValueSet/testscript-scope-phase-codes
|
Version: 6.0.0-ballot2 | |||
draft as of 2021-01-26 | Computable Name: TestScriptScopePhaseType | |||
Flags: Experimental, Immutable | OID: 2.16.840.1.113883.4.642.3.3056 |
This value set is used in the following places:
The phase of testing for this artifact.
Generated Narrative: ValueSet testscript-scope-phase-codes
Last updated: 2024-08-12T16:52:12.437+08:00
Profile: Shareable ValueSet
http://hl7.org/fhir/testscript-scope-phase-codes
This expansion generated 12 Aug 2024
Generated Narrative: ValueSet
Last updated: 2024-08-12T16:52:12.437+08:00
Profile: Shareable ValueSet
Expansion based on codesystem Test Script Scope Phase Type v6.0.0-ballot2 (CodeSystem)
This value set contains 3 concepts
Code | System | Display | Definition |
unit | http://hl7.org/fhir/testscript-scope-phase-codes | Unit | The development or implementation phase. |
integration | http://hl7.org/fhir/testscript-scope-phase-codes | Integration | The internal system to system phase. |
production | http://hl7.org/fhir/testscript-scope-phase-codes | Production | The live system to system phase (Note, this may involve pii/phi data). |
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 |