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

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

: SystemVersionProcessingMode - XML Representation

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="system-version-processing-mode"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem system-version-processing-mode</b></p><a name="system-version-processing-mode"> </a><a name="hcsystem-version-processing-mode"> </a><p>This case-sensitive code system <code>http://hl7.org/fhir/system-version-processing-mode</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">default<a name="system-version-processing-mode-default"> </a></td><td>Default Version</td><td>Use this version of the code system if a value set doesn't specify a version</td></tr><tr><td style="white-space:nowrap">check<a name="system-version-processing-mode-check"> </a></td><td>Check ValueSet Version</td><td>Use this version of the code system. If a value set specifies a different version, the expansion operation should fail</td></tr><tr><td style="white-space:nowrap">override<a name="system-version-processing-mode-override"> </a></td><td>Override ValueSet Version</td><td>Use 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</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="Informative"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/package-source">
    <extension url="packageId">
      <valueId value="hl7.fhir.uv.xver-r3.r4"/>
    </extension>
    <extension url="version">
      <valueString value="0.1.0"/>
    </extension>
    <extension url="uri">
      <valueUri
                value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"/>
    </extension>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="vocab"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/system-version-processing-mode"/>
  <version value="3.0.2"/>
  <name value="SystemVersionProcessingMode"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2019-10-23T19:53:00-05:00"/>
  <publisher value="HL7 International / Terminology Infrastructure"/>
  <contact>
    <name value="HL7 International / Terminology Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/Vocab"/>
    </telecom>
  </contact>
  <description
               value="How to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profile"/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <valueSet
            value="http://hl7.org/fhir/ValueSet/system-version-processing-mode"/>
  <content value="complete"/>
  <concept>
    <code value="default"/>
    <display value="Default Version"/>
    <definition
                value="Use this version of the code system if a value set doesn't specify a version"/>
  </concept>
  <concept>
    <code value="check"/>
    <display value="Check ValueSet Version"/>
    <definition
                value="Use this version of the code system. If a value set specifies a different version, the expansion operation should fail"/>
  </concept>
  <concept>
    <code value="override"/>
    <display value="Override ValueSet Version"/>
    <definition
                value="Use 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"/>
  </concept>
</CodeSystem>