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

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

: R4BodyStructureElementMapToR5 - XML Representation

Page standards status: Trial-use Maturity Level: 0

Raw xml | Download


<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="R4-BodyStructure-element-map-to-R5"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4-BodyStructure-element-map-to-R5</b></p><a name="R4-BodyStructure-element-map-to-R5"> </a><a name="hcR4-BodyStructure-element-map-to-R5"> </a><p>Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/BodyStructure|4.0.1</code> to <a href="http://hl7.org/fhir/R5/bodystructure.html">BodyStructureversion: 5.0.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>BodyStructure.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.meta</td><td>Element `BodyStructure.meta` is mapped to FHIR R5 element `BodyStructure.meta` as `Equivalent`.</td></tr><tr><td>BodyStructure.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.implicitRules</td><td>Element `BodyStructure.implicitRules` is mapped to FHIR R5 element `BodyStructure.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.</td></tr><tr><td>BodyStructure.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.language</td><td>Element `BodyStructure.language` is mapped to FHIR R5 element `BodyStructure.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td>BodyStructure.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.text</td><td>Element `BodyStructure.text` is mapped to FHIR R5 element `BodyStructure.text` as `Equivalent`.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>BodyStructure.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.contained</td><td>Element `BodyStructure.contained` is mapped to FHIR R5 element `BodyStructure.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>BodyStructure.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.identifier</td><td>Element `BodyStructure.identifier` is mapped to FHIR R5 element `BodyStructure.identifier` as `Equivalent`.</td></tr><tr><td>BodyStructure.active (active)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.active</td><td>Element `BodyStructure.active` is mapped to FHIR R5 element `BodyStructure.active` as `Equivalent`.
This element is labeled as a modifier because it may be used to mark that the resource was created in error.</td></tr><tr><td>BodyStructure.morphology (morphology)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.morphology</td><td>Element `BodyStructure.morphology` is mapped to FHIR R5 element `BodyStructure.morphology` as `Equivalent`.
The minimum cardinality of 0 supports the use case of specifying a location without defining a morphology.</td></tr><tr><td>BodyStructure.location (location)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.includedStructure.structure</td><td>Element `BodyStructure.location` is mapped to FHIR R5 element `BodyStructure.includedStructure.structure` as `Equivalent`.</td></tr><tr><td>BodyStructure.locationQualifier (locationQualifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.includedStructure.laterality</td><td>Element `BodyStructure.locationQualifier` is mapped to FHIR R5 element `BodyStructure.includedStructure.laterality` as `SourceIsBroaderThanTarget`.</td></tr><tr><td>BodyStructure.description (description)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.description</td><td>Element `BodyStructure.description` is mapped to FHIR R5 element `BodyStructure.description` as `Equivalent`.
This description could include any visual markings used to orientate the viewer e.g. external reference points, special sutures, ink markings.</td></tr><tr><td>BodyStructure.image (image)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.image</td><td>Element `BodyStructure.image` is mapped to FHIR R5 element `BodyStructure.image` as `Equivalent`.</td></tr><tr><td>BodyStructure.patient (patient)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>BodyStructure.patient</td><td>Element `BodyStructure.patient` is mapped to FHIR R5 element `BodyStructure.patient` as `Equivalent`.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"/>
      </extension>
    </valueInteger>
  </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-r4.r5"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ConceptMap/R4-BodyStructure-element-map-to-R5"/>
  <version value="0.1.0"/>
  <name value="R4BodyStructureElementMapToR5"/>
  <title
         value="Cross-version mapping for FHIR R4 BodyStructure to FHIR R5 BodyStructure"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T16:04:34.4608656-05:00"/>
  <contact>
    <name value="FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description
               value="This ConceptMap represents cross-version mappings for elements from a FHIR R4 BodyStructure to FHIR R5."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <sourceScopeCanonical value="http://hl7.org/fhir/4.0"/>
  <targetScopeUri value="http://hl7.org/fhir/5.0"/>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/BodyStructure|4.0.1"/>
    <target
            value="http://hl7.org/fhir/StructureDefinition/BodyStructure|5.0.0"/>
    <element>
      <code value="BodyStructure.meta"/>
      <display value="meta"/>
      <target>
        <code value="BodyStructure.meta"/>
        <display value="BodyStructure.meta"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.meta` is mapped to FHIR R5 element `BodyStructure.meta` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.implicitRules"/>
      <display value="implicitRules"/>
      <target>
        <code value="BodyStructure.implicitRules"/>
        <display value="BodyStructure.implicitRules"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.implicitRules` is mapped to FHIR R5 element `BodyStructure.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.language"/>
      <display value="language"/>
      <target>
        <code value="BodyStructure.language"/>
        <display value="BodyStructure.language"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.language` is mapped to FHIR R5 element `BodyStructure.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.text"/>
      <display value="text"/>
      <target>
        <code value="BodyStructure.text"/>
        <display value="BodyStructure.text"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.text` is mapped to FHIR R5 element `BodyStructure.text` as `Equivalent`.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.contained"/>
      <display value="contained"/>
      <target>
        <code value="BodyStructure.contained"/>
        <display value="BodyStructure.contained"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.contained` is mapped to FHIR R5 element `BodyStructure.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.identifier"/>
      <display value="identifier"/>
      <target>
        <code value="BodyStructure.identifier"/>
        <display value="BodyStructure.identifier"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.identifier` is mapped to FHIR R5 element `BodyStructure.identifier` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.active"/>
      <display value="active"/>
      <target>
        <code value="BodyStructure.active"/>
        <display value="BodyStructure.active"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.active` is mapped to FHIR R5 element `BodyStructure.active` as `Equivalent`.
This element is labeled as a modifier because it may be used to mark that the resource was created in error."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.morphology"/>
      <display value="morphology"/>
      <target>
        <code value="BodyStructure.morphology"/>
        <display value="BodyStructure.morphology"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.morphology` is mapped to FHIR R5 element `BodyStructure.morphology` as `Equivalent`.
The minimum cardinality of 0 supports the use case of specifying a location without defining a morphology."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.location"/>
      <display value="location"/>
      <target>
        <code value="BodyStructure.includedStructure.structure"/>
        <display value="BodyStructure.includedStructure.structure"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.location` is mapped to FHIR R5 element `BodyStructure.includedStructure.structure` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.locationQualifier"/>
      <display value="locationQualifier"/>
      <target>
        <code value="BodyStructure.includedStructure.laterality"/>
        <display value="BodyStructure.includedStructure.laterality"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.locationQualifier` is mapped to FHIR R5 element `BodyStructure.includedStructure.laterality` as `SourceIsBroaderThanTarget`."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.description"/>
      <display value="description"/>
      <target>
        <code value="BodyStructure.description"/>
        <display value="BodyStructure.description"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.description` is mapped to FHIR R5 element `BodyStructure.description` as `Equivalent`.
This description could include any visual markings used to orientate the viewer e.g. external reference points, special sutures, ink markings."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.image"/>
      <display value="image"/>
      <target>
        <code value="BodyStructure.image"/>
        <display value="BodyStructure.image"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.image` is mapped to FHIR R5 element `BodyStructure.image` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="BodyStructure.patient"/>
      <display value="patient"/>
      <target>
        <code value="BodyStructure.patient"/>
        <display value="BodyStructure.patient"/>
        <relationship value="equivalent"/>
        <comment
                 value="Element `BodyStructure.patient` is mapped to FHIR R5 element `BodyStructure.patient` as `Equivalent`."/>
      </target>
    </element>
  </group>
</ConceptMap>