Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR STU3 - Downloaded Version null See the Directory of published versions

ValueSet: R4StandardsStatusForR3

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-standards-status-for-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4StandardsStatusForR3

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/standards-status|4.0.1 for use in FHIR STU3.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/standards-status|4.0.1 as defined in FHIR R4 in FHIR STU3.

The source value set is bound to the following FHIR R4 elements:

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://hl7.org/fhir/ValueSet/standards-status|4.0.1, defined in FHIR R4 does not have any mapping to FHIR STU3

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 these codes as defined in http://terminology.hl7.org/CodeSystem/standards-status version 📍4.0.1
    CodeDisplayDefinition
    deprecatedDeprecatedThis 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.
    draftDraftThis 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.
    externalExternalThis is content that is managed outside the FHIR Specification, but included for implementer convenience.
    informativeInformativeThis 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.
    normativeNormativeThis 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-useTrial-UseThis 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.

 

Expansion

This value set expansion contains 6 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/standards-status4.0.1  deprecatedDeprecated

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.

http://terminology.hl7.org/CodeSystem/standards-status4.0.1  draftDraft

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.

http://terminology.hl7.org/CodeSystem/standards-status4.0.1  externalExternal

This is content that is managed outside the FHIR Specification, but included for implementer convenience.

http://terminology.hl7.org/CodeSystem/standards-status4.0.1  informativeInformative

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.

http://terminology.hl7.org/CodeSystem/standards-status4.0.1  normativeNormative

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.

http://terminology.hl7.org/CodeSystem/standards-status4.0.1  trial-useTrial-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.

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