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

: R4PlanDefinitionTypeForR3 - XML Representation

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download


<ValueSet xmlns="http://hl7.org/fhir">
  <id value="R4-plan-definition-type-for-R3"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ValueSet R4-plan-definition-type-for-R3</b></p><a name="R4-plan-definition-type-for-R3"> </a><a name="hcR4-plan-definition-type-for-R3"> </a><p>This value set expansion contains 1 concepts.</p><table class="codes"><tr><td><b>System</b></td><td><b>Version</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a name="R4-plan-definition-type-for-R3-http://terminology.hl7.org/CodeSystem/plan-definition-type-workflow-definition"> </a><code>http://terminology.hl7.org/CodeSystem/plan-definition-type</code></td><td>4.0.1</td><td style="white-space:nowrap">  <a href="CodeSystem-plan-definition-type.html#plan-definition-type-workflow-definition">workflow-definition</a></td><td>Workflow Definition</td><td>Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/package-source">
    <extension url="packageId">
      <valueId value="hl7.fhir.uv.xver-r4.r3"/>
    </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-r4.r3"/>
    </extension>
  </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">
        <valueUri
                  value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r3"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ValueSet/R4-plan-definition-type-for-R3"/>
  <version value="0.1.0"/>
  <name value="R4PlanDefinitionTypeForR3"/>
  <title
         value="Cross-version ValueSet R4.PlanDefinitionType for use in FHIR STU3"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T21:02:03.8104715+00:00"/>
  <publisher value="Clinical Decision Support"/>
  <contact>
    <name value="Clinical Decision Support"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/dss"/>
    </telecom>
  </contact>
  <description
               value="This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/plan-definition-type|4.0.1 for use in FHIR STU3 that is appropriate for use but unavailable in `http://hl7.org/fhir/ValueSet/plan-definition-type|3.0.2`."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <purpose
           value="This value set is part of the cross-version definitions generated to enable use of the
value set `http://hl7.org/fhir/ValueSet/plan-definition-type|4.0.1` as defined in FHIR R4
in FHIR STU3.

The source value set is bound to the following FHIR R4 elements:
* `PlanDefinition.type`

The following concepts are not included in this cross-version definition because they have valid representations:

* `http://terminology.hl7.org/CodeSystem/plan-definition-type#clinical-protocol`
* `http://terminology.hl7.org/CodeSystem/plan-definition-type#eca-rule`
* `http://terminology.hl7.org/CodeSystem/plan-definition-type#order-set`

Following are the generation technical comments:
One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened.
The source value set has more active concepts (4) than the target (3), so the source is broader than the target."/>
  <compose>
    <include>
      <system
              value="http://terminology.hl7.org/CodeSystem/plan-definition-type"/>
      <version value="4.0.1"/>
      <concept>
        <code value="workflow-definition"/>
        <display value="Workflow Definition"/>
      </concept>
    </include>
  </compose>
  <expansion>
    <timestamp value="2026-03-17T21:02:03.8104715+00:00"/>
    <contains>
      <system
              value="http://terminology.hl7.org/CodeSystem/plan-definition-type"/>
      <version value="4.0.1"/>
      <code value="workflow-definition"/>
      <display value="Workflow Definition"/>
    </contains>
  </expansion>
</ValueSet>