Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R2-Binary-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 R2-Binary-element-map-to-R5</b></p><a name="R2-Binary-element-map-to-R5"> </a><a name="hcR2-Binary-element-map-to-R5"> </a><p>Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Binary|1.0.2</code> to <a href="http://hl7.org/fhir/R5/binary.html">Binaryversion: 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>Binary.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Binary.meta</td><td>Element `Binary.meta` is mapped to FHIR R5 element `Binary.meta` as `SourceIsBroaderThanTarget`.
The mappings for `Binary.meta` do not cover the following types: Meta.
The mappings for `Binary.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td>Binary.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>Binary.implicitRules</td><td>Element `Binary.implicitRules` is mapped to FHIR R5 element `Binary.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 as much as possible.</td></tr><tr><td>Binary.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>Binary.language</td><td>Element `Binary.language` is mapped to FHIR R5 element `Binary.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>Binary.contentType (contentType)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Binary.contentType</td><td>Element `Binary.contentType` is mapped to FHIR R5 element `Binary.contentType` as `Equivalent`.</td></tr><tr><td>Binary.content (content)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Binary.data</td><td>Element `Binary.content` is mapped to FHIR R5 element `Binary.data` as `Equivalent`.
If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Binary|1.0.2</code> to <a href="StructureDefinition-ext-R2-Binary.meta.html">DSTU2: meta additional typesversion: 0.1.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>Binary.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>Extension (DSTU2: meta additional types)</td><td>Element `Binary.meta` is mapped to FHIR R5 element `Binary.meta` as `SourceIsBroaderThanTarget`.
The mappings for `Binary.meta` do not cover the following types: Meta.
The mappings for `Binary.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</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-r2.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-r2.r5"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R2-Binary-element-map-to-R5"/>
<version value="0.1.0"/>
<name value="R2BinaryElementMapToR5"/>
<title
value="Cross-version mapping for FHIR DSTU2 Binary to FHIR R5 Binary"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:05:26.0578563-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 DSTU2 Binary 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/1.0"/>
<targetScopeUri value="http://hl7.org/fhir/5.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Binary|1.0.2"/>
<target value="http://hl7.org/fhir/StructureDefinition/Binary|5.0.0"/>
<element>
<code value="Binary.meta"/>
<display value="meta"/>
<target>
<code value="Binary.meta"/>
<display value="Binary.meta"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Binary.meta` is mapped to FHIR R5 element `Binary.meta` as `SourceIsBroaderThanTarget`.
The mappings for `Binary.meta` do not cover the following types: Meta.
The mappings for `Binary.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
<element>
<code value="Binary.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Binary.implicitRules"/>
<display value="Binary.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `Binary.implicitRules` is mapped to FHIR R5 element `Binary.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 as much as possible."/>
</target>
</element>
<element>
<code value="Binary.language"/>
<display value="language"/>
<target>
<code value="Binary.language"/>
<display value="Binary.language"/>
<relationship value="equivalent"/>
<comment
value="Element `Binary.language` is mapped to FHIR R5 element `Binary.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="Binary.contentType"/>
<display value="contentType"/>
<target>
<code value="Binary.contentType"/>
<display value="Binary.contentType"/>
<relationship value="equivalent"/>
<comment
value="Element `Binary.contentType` is mapped to FHIR R5 element `Binary.contentType` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Binary.content"/>
<display value="content"/>
<target>
<code value="Binary.data"/>
<display value="Binary.data"/>
<relationship value="equivalent"/>
<comment
value="Element `Binary.content` is mapped to FHIR R5 element `Binary.data` as `Equivalent`.
If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Binary|1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-Binary.meta|0.1.0"/>
<element>
<code value="Binary.meta"/>
<display value="meta"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Binary.meta` is mapped to FHIR R5 element `Binary.meta` as `SourceIsBroaderThanTarget`.
The mappings for `Binary.meta` do not cover the following types: Meta.
The mappings for `Binary.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
</group>
</ConceptMap>