Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - 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="R3-NamingSystem-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R3-NamingSystem-element-map-to-R4</b></p><a name="R3-NamingSystem-element-map-to-R4"> </a><a name="hcR3-NamingSystem-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2</code> to <a href="http://hl7.org/fhir/R4/namingsystem.html">NamingSystemversion: 4.0.1)</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>NamingSystem.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>NamingSystem.meta</td><td>Element `NamingSystem.meta` is mapped to FHIR R4 element `NamingSystem.meta` as `Equivalent`.</td></tr><tr><td>NamingSystem.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>NamingSystem.implicitRules</td><td>Element `NamingSystem.implicitRules` is mapped to FHIR R4 element `NamingSystem.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.
This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.</td></tr><tr><td>NamingSystem.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>NamingSystem.language</td><td>Element `NamingSystem.language` is mapped to FHIR R4 element `NamingSystem.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>NamingSystem.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>NamingSystem.text</td><td>Element `NamingSystem.text` is mapped to FHIR R4 element `NamingSystem.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 in formation is added later.</td></tr><tr><td>NamingSystem.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>NamingSystem.contained</td><td>Element `NamingSystem.contained` is mapped to FHIR R4 element `NamingSystem.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.</td></tr><tr><td>NamingSystem.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>NamingSystem.name</td><td>Element `NamingSystem.name` is mapped to FHIR R4 element `NamingSystem.name` as `Equivalent`.
The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. The"symbolic name" for an OID would be captured as an extension.</td></tr><tr><td>NamingSystem.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.status</td><td>Element `NamingSystem.status` is mapped to FHIR R4 element `NamingSystem.status` as `Equivalent`.
Allows filtering of naming systems that are appropriate for use vs. not.
This is labeled as "Is Modifier" because applications should not use a retired naming system without due consideration.</td></tr><tr><td>NamingSystem.kind (kind)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.kind</td><td>Element `NamingSystem.kind` is mapped to FHIR R4 element `NamingSystem.kind` as `Equivalent`.</td></tr><tr><td>NamingSystem.date (date)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.date</td><td>Element `NamingSystem.date` is mapped to FHIR R4 element `NamingSystem.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the naming system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.</td></tr><tr><td>NamingSystem.publisher (publisher)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.publisher</td><td>Element `NamingSystem.publisher` is mapped to FHIR R4 element `NamingSystem.publisher` as `Equivalent`.
Usually an organization, but may be an individual. The publisher (or steward) of the naming system is the organization or individual primarily responsible for the maintenance and upkeep of the naming system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the naming system. This item SHOULD be populated unless the information is available from context.</td></tr><tr><td>NamingSystem.contact (contact)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.contact</td><td>Element `NamingSystem.contact` is mapped to FHIR R4 element `NamingSystem.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc.</td></tr><tr><td>NamingSystem.responsible (responsible)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.responsible</td><td>Element `NamingSystem.responsible` is mapped to FHIR R4 element `NamingSystem.responsible` as `Equivalent`.
This is the primary organization. Responsibility for some aspects of a namespace may be delegated.</td></tr><tr><td>NamingSystem.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>NamingSystem.type</td><td>Element `NamingSystem.type` is mapped to FHIR R4 element `NamingSystem.type` as `Equivalent`.
This will most commonly be used for identifier namespaces, but categories could potentially be useful for code systems and authorities as well.</td></tr><tr><td>NamingSystem.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>NamingSystem.description</td><td>Element `NamingSystem.description` is mapped to FHIR R4 element `NamingSystem.description` as `Equivalent`.
This description can be used to capture details such as why the naming system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the naming system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created).</td></tr><tr><td>NamingSystem.useContext (useContext)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.useContext</td><td>Element `NamingSystem.useContext` is mapped to FHIR R4 element `NamingSystem.useContext` as `Equivalent`.
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.</td></tr><tr><td>NamingSystem.jurisdiction (jurisdiction)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.jurisdiction</td><td>Element `NamingSystem.jurisdiction` is mapped to FHIR R4 element `NamingSystem.jurisdiction` as `Equivalent`.
It may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended.</td></tr><tr><td>NamingSystem.usage (usage)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.usage</td><td>Element `NamingSystem.usage` is mapped to FHIR R4 element `NamingSystem.usage` as `Equivalent`.</td></tr><tr><td>NamingSystem.uniqueId (uniqueId)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>NamingSystem.uniqueId</td><td>Element `NamingSystem.uniqueId` is mapped to FHIR R4 element `NamingSystem.uniqueId` as `Equivalent`.
Multiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc.</td></tr><tr><td>NamingSystem.uniqueId.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>NamingSystem.uniqueId.type</td><td>Element `NamingSystem.uniqueId.type` is mapped to FHIR R4 element `NamingSystem.uniqueId.type` as `Equivalent`.
Different identifier types may be used in different types of communications (OIDs for v3, URIs for FHIR, etc.). Other includes RUIDs from v3, standard v2 code name strings, etc.</td></tr><tr><td>NamingSystem.uniqueId.value (value)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.uniqueId.value</td><td>Element `NamingSystem.uniqueId.value` is mapped to FHIR R4 element `NamingSystem.uniqueId.value` as `Equivalent`.
If the value is a URI intended for use as FHIR system identifier, the URI should not contain "\" or "?" or "," since this makes escaping very difficult.</td></tr><tr><td>NamingSystem.uniqueId.preferred (preferred)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.uniqueId.preferred</td><td>Element `NamingSystem.uniqueId.preferred` is mapped to FHIR R4 element `NamingSystem.uniqueId.preferred` as `Equivalent`.</td></tr><tr><td>NamingSystem.uniqueId.comment (comment)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.uniqueId.comment</td><td>Element `NamingSystem.uniqueId.comment` is mapped to FHIR R4 element `NamingSystem.uniqueId.comment` as `Equivalent`.
e.g. "must be used in Germany" or "was initially published in error with this value".</td></tr><tr><td>NamingSystem.uniqueId.period (period)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>NamingSystem.uniqueId.period</td><td>Element `NamingSystem.uniqueId.period` is mapped to FHIR R4 element `NamingSystem.uniqueId.period` as `Equivalent`.
Within a registry, a given identifier should only be "active" for a single namespace at a time. (Ideally, an identifier should only ever be associated with a single namespace across all time).</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2</code> to <a href="StructureDefinition-ext-R3-NamingSystem.replacedBy.html">STU3: Use this instead (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>NamingSystem.replacedBy (replacedBy)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Use this instead (new))</td><td>Element `NamingSystem.replacedBy` has a context of NamingSystem based on following the parent source element upwards and mapping to `NamingSystem`.
Element `NamingSystem.replacedBy` has no mapping targets in FHIR R4. 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-r3.r4"/>
</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-r3.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R3-NamingSystem-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R3NamingSystemElementMapToR4"/>
<title
value="Cross-version mapping for FHIR STU3 NamingSystem to FHIR R4 NamingSystem"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:24.0621268-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 STU3 NamingSystem to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/3.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<sourceVersion value="3.0.2"/>
<target value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<targetVersion value="4.0.1"/>
<element>
<code value="NamingSystem.meta"/>
<display value="meta"/>
<target>
<code value="NamingSystem.meta"/>
<display value="NamingSystem.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.meta` is mapped to FHIR R4 element `NamingSystem.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="NamingSystem.implicitRules"/>
<display value="NamingSystem.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.implicitRules` is mapped to FHIR R4 element `NamingSystem.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.
This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."/>
</target>
</element>
<element>
<code value="NamingSystem.language"/>
<display value="language"/>
<target>
<code value="NamingSystem.language"/>
<display value="NamingSystem.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.language` is mapped to FHIR R4 element `NamingSystem.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="NamingSystem.text"/>
<display value="text"/>
<target>
<code value="NamingSystem.text"/>
<display value="NamingSystem.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.text` is mapped to FHIR R4 element `NamingSystem.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 in formation is added later."/>
</target>
</element>
<element>
<code value="NamingSystem.contained"/>
<display value="contained"/>
<target>
<code value="NamingSystem.contained"/>
<display value="NamingSystem.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.contained` is mapped to FHIR R4 element `NamingSystem.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."/>
</target>
</element>
<element>
<code value="NamingSystem.name"/>
<display value="name"/>
<target>
<code value="NamingSystem.name"/>
<display value="NamingSystem.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.name` is mapped to FHIR R4 element `NamingSystem.name` as `Equivalent`.
The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. The"symbolic name" for an OID would be captured as an extension."/>
</target>
</element>
<element>
<code value="NamingSystem.status"/>
<display value="status"/>
<target>
<code value="NamingSystem.status"/>
<display value="NamingSystem.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.status` is mapped to FHIR R4 element `NamingSystem.status` as `Equivalent`.
Allows filtering of naming systems that are appropriate for use vs. not.
This is labeled as "Is Modifier" because applications should not use a retired naming system without due consideration."/>
</target>
</element>
<element>
<code value="NamingSystem.kind"/>
<display value="kind"/>
<target>
<code value="NamingSystem.kind"/>
<display value="NamingSystem.kind"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.kind` is mapped to FHIR R4 element `NamingSystem.kind` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.date"/>
<display value="date"/>
<target>
<code value="NamingSystem.date"/>
<display value="NamingSystem.date"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.date` is mapped to FHIR R4 element `NamingSystem.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the naming system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource."/>
</target>
</element>
<element>
<code value="NamingSystem.publisher"/>
<display value="publisher"/>
<target>
<code value="NamingSystem.publisher"/>
<display value="NamingSystem.publisher"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.publisher` is mapped to FHIR R4 element `NamingSystem.publisher` as `Equivalent`.
Usually an organization, but may be an individual. The publisher (or steward) of the naming system is the organization or individual primarily responsible for the maintenance and upkeep of the naming system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the naming system. This item SHOULD be populated unless the information is available from context."/>
</target>
</element>
<element>
<code value="NamingSystem.contact"/>
<display value="contact"/>
<target>
<code value="NamingSystem.contact"/>
<display value="NamingSystem.contact"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.contact` is mapped to FHIR R4 element `NamingSystem.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc."/>
</target>
</element>
<element>
<code value="NamingSystem.responsible"/>
<display value="responsible"/>
<target>
<code value="NamingSystem.responsible"/>
<display value="NamingSystem.responsible"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.responsible` is mapped to FHIR R4 element `NamingSystem.responsible` as `Equivalent`.
This is the primary organization. Responsibility for some aspects of a namespace may be delegated."/>
</target>
</element>
<element>
<code value="NamingSystem.type"/>
<display value="type"/>
<target>
<code value="NamingSystem.type"/>
<display value="NamingSystem.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.type` is mapped to FHIR R4 element `NamingSystem.type` as `Equivalent`.
This will most commonly be used for identifier namespaces, but categories could potentially be useful for code systems and authorities as well."/>
</target>
</element>
<element>
<code value="NamingSystem.description"/>
<display value="description"/>
<target>
<code value="NamingSystem.description"/>
<display value="NamingSystem.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.description` is mapped to FHIR R4 element `NamingSystem.description` as `Equivalent`.
This description can be used to capture details such as why the naming system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the naming system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created)."/>
</target>
</element>
<element>
<code value="NamingSystem.useContext"/>
<display value="useContext"/>
<target>
<code value="NamingSystem.useContext"/>
<display value="NamingSystem.useContext"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.useContext` is mapped to FHIR R4 element `NamingSystem.useContext` as `Equivalent`.
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."/>
</target>
</element>
<element>
<code value="NamingSystem.jurisdiction"/>
<display value="jurisdiction"/>
<target>
<code value="NamingSystem.jurisdiction"/>
<display value="NamingSystem.jurisdiction"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.jurisdiction` is mapped to FHIR R4 element `NamingSystem.jurisdiction` as `Equivalent`.
It may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended."/>
</target>
</element>
<element>
<code value="NamingSystem.usage"/>
<display value="usage"/>
<target>
<code value="NamingSystem.usage"/>
<display value="NamingSystem.usage"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.usage` is mapped to FHIR R4 element `NamingSystem.usage` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId"/>
<display value="uniqueId"/>
<target>
<code value="NamingSystem.uniqueId"/>
<display value="NamingSystem.uniqueId"/>
<equivalence value="wider"/>
<comment
value="Element `NamingSystem.uniqueId` is mapped to FHIR R4 element `NamingSystem.uniqueId` as `Equivalent`.
Multiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.type"/>
<display value="type"/>
<target>
<code value="NamingSystem.uniqueId.type"/>
<display value="NamingSystem.uniqueId.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.type` is mapped to FHIR R4 element `NamingSystem.uniqueId.type` as `Equivalent`.
Different identifier types may be used in different types of communications (OIDs for v3, URIs for FHIR, etc.). Other includes RUIDs from v3, standard v2 code name strings, etc."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.value"/>
<display value="value"/>
<target>
<code value="NamingSystem.uniqueId.value"/>
<display value="NamingSystem.uniqueId.value"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.value` is mapped to FHIR R4 element `NamingSystem.uniqueId.value` as `Equivalent`.
If the value is a URI intended for use as FHIR system identifier, the URI should not contain "\" or "?" or "," since this makes escaping very difficult."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.preferred"/>
<display value="preferred"/>
<target>
<code value="NamingSystem.uniqueId.preferred"/>
<display value="NamingSystem.uniqueId.preferred"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.preferred` is mapped to FHIR R4 element `NamingSystem.uniqueId.preferred` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.comment"/>
<display value="comment"/>
<target>
<code value="NamingSystem.uniqueId.comment"/>
<display value="NamingSystem.uniqueId.comment"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.comment` is mapped to FHIR R4 element `NamingSystem.uniqueId.comment` as `Equivalent`.
e.g. "must be used in Germany" or "was initially published in error with this value"."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.period"/>
<display value="period"/>
<target>
<code value="NamingSystem.uniqueId.period"/>
<display value="NamingSystem.uniqueId.period"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.period` is mapped to FHIR R4 element `NamingSystem.uniqueId.period` as `Equivalent`.
Within a registry, a given identifier should only be "active" for a single namespace at a time. (Ideally, an identifier should only ever be associated with a single namespace across all time)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-NamingSystem.replacedBy"/>
<targetVersion value="0.1.0"/>
<element>
<code value="NamingSystem.replacedBy"/>
<display value="replacedBy"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.replacedBy` has a context of NamingSystem based on following the parent source element upwards and mapping to `NamingSystem`.
Element `NamingSystem.replacedBy` has no mapping targets in FHIR R4. 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-r3.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change