FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-standards-status-for-R4B | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R4_standards_status_for_R4B | ||
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/standards-status | 4.0.1 for use in FHIR R4B. Concepts not present here have direct equivalent mappings crossing all versions from R4 to R4B. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/standards-status version 4.0.1| Code | Display | Definition |
| informative | Informative | This portion of the specification is provided for implementer assistance, and does not make rules that implementers are required to follow. Typical examples of this content in the FHIR specification are tables of contents, registries, examples, and implementer advice. |
This value set expansion contains 1 concepts.
| Code | System | Display | Definition |
| informative | http://terminology.hl7.org/CodeSystem/standards-status | Informative | This portion of the specification is provided for implementer assistance, and does not make rules that implementers are required to follow. Typical examples of this content in the FHIR specification are tables of contents, registries, examples, and implementer advice. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | 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) |
| 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 |