Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 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="R4-Organization-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-Organization-element-map-to-R5</b></p><a name="R4-Organization-element-map-to-R5"> </a><a name="hcR4-Organization-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/Organization|4.0.1</code> to <a href="http://hl7.org/fhir/R5/organization.html">Organizationversion: 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>Organization.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>Organization.meta</td><td>Element `Organization.meta` is mapped to FHIR R5 element `Organization.meta` as `Equivalent`.</td></tr><tr><td>Organization.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>Organization.implicitRules</td><td>Element `Organization.implicitRules` is mapped to FHIR R5 element `Organization.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>Organization.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>Organization.language</td><td>Element `Organization.language` is mapped to FHIR R5 element `Organization.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>Organization.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>Organization.text</td><td>Element `Organization.text` is mapped to FHIR R5 element `Organization.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 "text blob" or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>Organization.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>Organization.contained</td><td>Element `Organization.contained` is mapped to FHIR R5 element `Organization.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>Organization.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>Organization.identifier</td><td>Element `Organization.identifier` is mapped to FHIR R5 element `Organization.identifier` as `Equivalent`.</td></tr><tr><td>Organization.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>Organization.active</td><td>Element `Organization.active` is mapped to FHIR R5 element `Organization.active` as `Equivalent`.
This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used.
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>Organization.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Organization.type</td><td>Element `Organization.type` is mapped to FHIR R5 element `Organization.type` as `Equivalent`.
Organizations can be corporations, wards, sections, clinical teams, government departments, etc. Note that code is generally a classifier of the type of organization; in many applications, codes are used to identity a particular organization (say, ward) as opposed to another of the same type - these are identifiers, not codes
When considering if multiple types are appropriate, you should evaluate if child organizations would be a more appropriate use of the concept, as different types likely are in different sub-areas of the organization. This is most likely to be used where type values have orthogonal values, such as a religious, academic and medical center.
We expect that some jurisdictions will profile this optionality to be a single cardinality.</td></tr><tr><td>Organization.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Organization.name</td><td>Element `Organization.name` is mapped to FHIR R5 element `Organization.name` as `Equivalent`.
If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches.</td></tr><tr><td>Organization.alias (alias)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Organization.alias</td><td>Element `Organization.alias` is mapped to FHIR R5 element `Organization.alias` as `Equivalent`.
There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the organization.</td></tr><tr><td>Organization.partOf (partOf)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Organization.partOf</td><td>Element `Organization.partOf` is mapped to FHIR R5 element `Organization.partOf` as `Equivalent`.</td></tr><tr><td>Organization.contact (contact)</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>Organization.contact</td><td>Element `Organization.contact` is mapped to FHIR R5 element `Organization.contact` as `Equivalent`.
Where multiple contacts for the same purpose are provided there is a standard extension that can be used to determine which one is the preferred contact to use.</td></tr><tr><td>Organization.endpoint (endpoint)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Organization.endpoint</td><td>Element `Organization.endpoint` is mapped to FHIR R5 element `Organization.endpoint` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.telecom.html">R4: A contact detail for the organization (new)version: 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>Organization.telecom (telecom)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: A contact detail for the organization (new))</td><td>Element `Organization.telecom` has a context of Organization based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
The use code 'home' is not to be used. Note that these contacts are not the contact details of people who are employed by or represent the organization, but official contacts for the organization itself.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.address.html">R4: An address for the organization (new)version: 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>Organization.address (address)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: An address for the organization (new))</td><td>Element `Organization.address` has a context of Organization based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.address` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.con.purpose.html">R4: The type of contact (new)version: 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>Organization.contact.purpose (purpose)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: The type of contact (new))</td><td>Element `Organization.contact.purpose` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.purpose` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.con.name.html">R4: A name associated with the contact (new)version: 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>Organization.contact.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: A name associated with the contact (new))</td><td>Element `Organization.contact.name` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.con.telecom.html">R4: Contact details (telephone, email, etc.) for a contact (new)version: 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>Organization.contact.telecom (telecom)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: Contact details (telephone, email, etc.) for a contact (new))</td><td>Element `Organization.contact.telecom` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Organization|4.0.1</code> to <a href="StructureDefinition-ext-R4-Organization.con.address.html">R4: Visiting or postal addresses for the contact (new)version: 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>Organization.contact.address (address)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: Visiting or postal addresses for the contact (new))</td><td>Element `Organization.contact.address` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.address` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</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-Organization-element-map-to-R5"/>
<version value="0.1.0"/>
<name value="R4OrganizationElementMapToR5"/>
<title
value="Cross-version mapping for FHIR R4 Organization to FHIR R5 Organization"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:37.2459984-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 Organization 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/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/StructureDefinition/Organization|5.0.0"/>
<element>
<code value="Organization.meta"/>
<display value="meta"/>
<target>
<code value="Organization.meta"/>
<display value="Organization.meta"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.meta` is mapped to FHIR R5 element `Organization.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Organization.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Organization.implicitRules"/>
<display value="Organization.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.implicitRules` is mapped to FHIR R5 element `Organization.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="Organization.language"/>
<display value="language"/>
<target>
<code value="Organization.language"/>
<display value="Organization.language"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.language` is mapped to FHIR R5 element `Organization.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="Organization.text"/>
<display value="text"/>
<target>
<code value="Organization.text"/>
<display value="Organization.text"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.text` is mapped to FHIR R5 element `Organization.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 "text blob" or where text is additionally entered raw or narrated and encoded information is added later."/>
</target>
</element>
<element>
<code value="Organization.contained"/>
<display value="contained"/>
<target>
<code value="Organization.contained"/>
<display value="Organization.contained"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.contained` is mapped to FHIR R5 element `Organization.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="Organization.identifier"/>
<display value="identifier"/>
<target>
<code value="Organization.identifier"/>
<display value="Organization.identifier"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.identifier` is mapped to FHIR R5 element `Organization.identifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Organization.active"/>
<display value="active"/>
<target>
<code value="Organization.active"/>
<display value="Organization.active"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.active` is mapped to FHIR R5 element `Organization.active` as `Equivalent`.
This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used.
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="Organization.type"/>
<display value="type"/>
<target>
<code value="Organization.type"/>
<display value="Organization.type"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.type` is mapped to FHIR R5 element `Organization.type` as `Equivalent`.
Organizations can be corporations, wards, sections, clinical teams, government departments, etc. Note that code is generally a classifier of the type of organization; in many applications, codes are used to identity a particular organization (say, ward) as opposed to another of the same type - these are identifiers, not codes
When considering if multiple types are appropriate, you should evaluate if child organizations would be a more appropriate use of the concept, as different types likely are in different sub-areas of the organization. This is most likely to be used where type values have orthogonal values, such as a religious, academic and medical center.
We expect that some jurisdictions will profile this optionality to be a single cardinality."/>
</target>
</element>
<element>
<code value="Organization.name"/>
<display value="name"/>
<target>
<code value="Organization.name"/>
<display value="Organization.name"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.name` is mapped to FHIR R5 element `Organization.name` as `Equivalent`.
If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches."/>
</target>
</element>
<element>
<code value="Organization.alias"/>
<display value="alias"/>
<target>
<code value="Organization.alias"/>
<display value="Organization.alias"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.alias` is mapped to FHIR R5 element `Organization.alias` as `Equivalent`.
There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the organization."/>
</target>
</element>
<element>
<code value="Organization.partOf"/>
<display value="partOf"/>
<target>
<code value="Organization.partOf"/>
<display value="Organization.partOf"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.partOf` is mapped to FHIR R5 element `Organization.partOf` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Organization.contact"/>
<display value="contact"/>
<target>
<code value="Organization.contact"/>
<display value="Organization.contact"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Organization.contact` is mapped to FHIR R5 element `Organization.contact` as `Equivalent`.
Where multiple contacts for the same purpose are provided there is a standard extension that can be used to determine which one is the preferred contact to use."/>
</target>
</element>
<element>
<code value="Organization.endpoint"/>
<display value="endpoint"/>
<target>
<code value="Organization.endpoint"/>
<display value="Organization.endpoint"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.endpoint` is mapped to FHIR R5 element `Organization.endpoint` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.telecom|0.1.0"/>
<element>
<code value="Organization.telecom"/>
<display value="telecom"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.telecom` has a context of Organization based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
The use code 'home' is not to be used. Note that these contacts are not the contact details of people who are employed by or represent the organization, but official contacts for the organization itself."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.address|0.1.0"/>
<element>
<code value="Organization.address"/>
<display value="address"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.address` has a context of Organization based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.address` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.contact.purpose|0.1.0"/>
<element>
<code value="Organization.contact.purpose"/>
<display value="purpose"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.contact.purpose` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.purpose` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.contact.name|0.1.0"/>
<element>
<code value="Organization.contact.name"/>
<display value="name"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.contact.name` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.contact.telecom|0.1.0"/>
<element>
<code value="Organization.contact.telecom"/>
<display value="telecom"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.contact.telecom` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-Organization.contact.address|0.1.0"/>
<element>
<code value="Organization.contact.address"/>
<display value="address"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `Organization.contact.address` has a context of Organization.contact based on following the parent source element upwards and mapping to `Organization`.
Element `Organization.contact.address` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change