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

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

ValueSet: R3SystemVersionProcessingModeForR4B

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-system-version-processing-mode-for-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 2 Responsible: HL7 International / Terminology Infrastructure Computable Name: R3SystemVersionProcessingModeForR4B

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/system-version-processing-mode|3.0.2 for use in FHIR R4B.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/system-version-processing-mode|3.0.2 as defined in FHIR STU3 in FHIR R4B.

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

  • ExpansionProfile.fixedVersion.mode

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/system-version-processing-mode|3.0.2, defined in FHIR STU3 does not have any mapping to FHIR R4B

References

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/system-version-processing-mode version 📍3.0.2
    CodeDisplayDefinition
    checkCheck ValueSet VersionUse this version of the code system. If a value set specifies a different version, the expansion operation should fail
    defaultDefault VersionUse this version of the code system if a value set doesn't specify a version
    overrideOverride ValueSet VersionUse this version of the code system irrespective of which version is specified by a value set. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If a version is override, the version used SHALL explicitly be represented in the expansion parameters

 

Expansion

This value set expansion contains 3 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/system-version-processing-mode3.0.2  checkCheck ValueSet VersionUse this version of the code system. If a value set specifies a different version, the expansion operation should fail
http://hl7.org/fhir/system-version-processing-mode3.0.2  defaultDefault VersionUse this version of the code system if a value set doesn't specify a version
http://hl7.org/fhir/system-version-processing-mode3.0.2  overrideOverride ValueSet VersionUse this version of the code system irrespective of which version is specified by a value set. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If a version is override, the version used SHALL explicitly be represented in the expansion parameters

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