HL7.TERMINOLOGY\StandardsStatus

This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: StandardsStatus

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/standards-status

Version:

0.1.0

Name:

StandardsStatus

Status:

Draft as of 2020-02-24T12:41:39+11:00

Definition:

HL7 Ballot/Standards status of artifact.

Publisher:

HL7 (FHIR Project)

Committee:

FHIR Infrastructure

OID:

2.16.840.1.113883.4.642.3.1365 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Include all codes defined in http://terminology.hl7.org/CodeSystem/standards-status

Expansion

This value set contains 6 concepts

Expansion based on StandardsStatus v0.1.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/standards-status

Code	Display	Definition
draft	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	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	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	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	Deprecated	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.
external	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

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)

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

History

Date

Action

Author

Custodian

Comment

2020-10-14

revise