This page is part of the FHIR Core Extensions Registry (v5.1.0: Release 5.1) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/ValueSet/standards-status | Version: 5.1.0 | |||
Standards status: Trial-use | Maturity Level: 3 | Computable Name: StandardsStatus | ||
Other Identifiers: OID:2.16.840.1.113883.4.642.3.1365 |
Description Needed Here
References
Changes since version 1.0.0:
http://hl7.org/fhir/standards-status
Expansion based oncodesystem standards status code system v5.1.0 (CodeSystem)
This value set contains 7 concepts.
Code | System | Display | Definition |
draft | http://hl7.org/fhir/standards-status | Draft | This portion of the specification is not considered to be complete enough or sufficiently reviewed to be safe for implementation. It may have known issues or still be in the "in development" stage. It is included in the publication as a place-holder, to solicit feedback from the implementation community and/or to give implementers some insight as to functionality likely to be included in future versions of the specification. Content at this level should only be implemented by the brave or desperate and is very much "use at your own risk". The content that is Draft that will usually be elevated to Trial Use once review and correction is complete after it has been subjected to ballot. |
normative | http://hl7.org/fhir/standards-status | Normative | This content has been subject to review and production implementation in a wide variety of environments. The content is considered to be stable and has been 'locked', subjecting it to FHIR Inter-version Compatibility Rules. While changes are possible, they are expected to be infrequent and are tightly constrained. Compatibility Rules. |
trial-use | http://hl7.org/fhir/standards-status | Trial-Use | This content has been well reviewed and is considered by the authors to be ready for use in production systems. It has been subjected to ballot and approved as an official standard. However, it has not yet seen widespread use in production across the full spectrum of environments it is intended to be used in. In some cases, there may be documented known issues that require implementation experience to determine appropriate resolutions for. Future versions of FHIR may make significant changes to Trial Use content that are not compatible with previously published content. |
informative | http://hl7.org/fhir/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. |
deprecated | http://hl7.org/fhir/standards-status | Deprecated | This portion of the specification is outdated; it is documented for historical purposes, but no longer supported and may be withdrawn in a future version. Implementers who already support it should continue to do so for backward compatibility. |
withdrawn | http://hl7.org/fhir/standards-status | Withdrawn | This content has been removed from the specification. |
external | http://hl7.org/fhir/standards-status | External | This is content that is managed outside the FHIR Specification, but included for implementer convenience. |
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 |