Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B - 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="R5-NamingSystem-element-map-to-R4B"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-NamingSystem-element-map-to-R4B</b></p><a name="R5-NamingSystem-element-map-to-R4B"> </a><a name="hcR5-NamingSystem-element-map-to-R4B"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|5.0.0</code> to <a href="http://hl7.org/fhir/R4B/namingsystem.html">NamingSystemversion: 4.3.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.meta (meta)</td><td><a href="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 R4B element `NamingSystem.meta` as `Equivalent`.</td></tr><tr><td>NamingSystem.implicitRules (implicitRules)</td><td><a href="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 R4B 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>NamingSystem.language (language)</td><td><a href="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 R4B 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="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 R4B element `NamingSystem.text` as `Equivalent`.
Contained resources do not have a 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>NamingSystem.contained (contained)</td><td><a href="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 R4B 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>NamingSystem.name (name)</td><td><a href="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 R4B element `NamingSystem.name` as `Equivalent`.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.The"symbolic name" for an OID would be captured as an extension.</td></tr><tr><td>NamingSystem.status (status)</td><td><a href="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 R4B element `NamingSystem.status` as `Equivalent`.
Allows filtering of naming systems that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).</td></tr><tr><td>NamingSystem.kind (kind)</td><td><a href="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 R4B element `NamingSystem.kind` as `Equivalent`.</td></tr><tr><td>NamingSystem.date (date)</td><td><a href="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 R4B element `NamingSystem.date` as `Equivalent`.
The date is often not tracked until the resource is published, but may be present on draft content. 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.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).</td></tr><tr><td>NamingSystem.publisher (publisher)</td><td><a href="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 R4B 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="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 R4B element `NamingSystem.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).</td></tr><tr><td>NamingSystem.responsible (responsible)</td><td><a href="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 R4B 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="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 R4B 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="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 R4B element `NamingSystem.description` as `Equivalent`.
This description can be used to capture details such as 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 naming system is presumed to be the predominant language in the place the naming system was created).</td></tr><tr><td>NamingSystem.useContext (useContext)</td><td><a href="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 R4B element `NamingSystem.useContext` as `Equivalent`.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.</td></tr><tr><td>NamingSystem.jurisdiction (jurisdiction)</td><td><a href="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 R4B element `NamingSystem.jurisdiction` as `Equivalent`.
Element `NamingSystem.jurisdiction` has been flagged as deprecated.
It may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)</td></tr><tr><td>NamingSystem.usage (usage)</td><td><a href="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 R4B element `NamingSystem.usage` as `Equivalent`.</td></tr><tr><td>NamingSystem.uniqueId (uniqueId)</td><td><a href="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 R4B 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="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>NamingSystem.uniqueId.type</td><td>Element `NamingSystem.uniqueId.type` is mapped to FHIR R4B element `NamingSystem.uniqueId.type` as `RelatedTo`.
The mappings for `NamingSystem.uniqueId.type` do not allow expression of the necessary codes, per the bindings on the source and target.
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. Preferred identifiers for the same identifier type SHOULD NOT overlap by period.</td></tr><tr><td>NamingSystem.uniqueId.value (value)</td><td><a href="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 R4B 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="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 R4B element `NamingSystem.uniqueId.preferred` as `Equivalent`.</td></tr><tr><td>NamingSystem.uniqueId.comment (comment)</td><td><a href="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 R4B 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="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 R4B 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).
The nuance of identifier deprecation is not represented with a separate element. When a determination is made that an identifier should not be used, the validity period end date is updated with the date the identifier is deemed to be deprecated. The identifier should no longer be used once the period end date is reached.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|5.0.0</code> to <a href="StructureDefinition-ext-R5-NamingSystem.uni.type.html">R5: oid | uuid | uri | iri-stem | v2csmnemonic | other additional codesversion: 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.uniqueId.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: oid | uuid | uri | iri-stem | v2csmnemonic | other additional codes)</td><td>Element `NamingSystem.uniqueId.type` is mapped to FHIR R4B element `NamingSystem.uniqueId.type` as `RelatedTo`.
The mappings for `NamingSystem.uniqueId.type` do not allow expression of the necessary codes, per the bindings on the source and target.
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. Preferred identifiers for the same identifier type SHOULD NOT overlap by period.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|5.0.0</code> to <a href="StructureDefinition-ext-R5-NamingSystem.uni.authoritative.html">R5: Whether the identifier is authoritative (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.uniqueId.authoritative (authoritative)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Whether the identifier is authoritative (new))</td><td>Element `NamingSystem.uniqueId.authoritative` has a context of NamingSystem.uniqueId based on following the parent source element upwards and mapping to `NamingSystem`.
Element `NamingSystem.uniqueId.authoritative` has no mapping targets in FHIR R4B. 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-r5.r4b"/>
</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-r5.r4b"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-NamingSystem-element-map-to-R4B"/>
<version value="0.1.0"/>
<name value="R5NamingSystemElementMapToR4B"/>
<title
value="Cross-version mapping for FHIR R5 NamingSystem to FHIR R4B NamingSystem"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:57.7954039-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 R5 NamingSystem to FHIR R4B."/>
<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/5.0"/>
<targetUri value="http://hl7.org/fhir/4.3"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<targetVersion value="4.3.0"/>
<element>
<code value="NamingSystem.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.meta"/>
<display value="NamingSystem.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.meta` is mapped to FHIR R4B element `NamingSystem.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.implicitRules"/>
<display value="NamingSystem.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.implicitRules` is mapped to FHIR R4B 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="NamingSystem.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.language"/>
<display value="NamingSystem.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.language` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.text"/>
<display value="NamingSystem.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.text` is mapped to FHIR R4B element `NamingSystem.text` as `Equivalent`.
Contained resources do not have a 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="NamingSystem.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.contained"/>
<display value="NamingSystem.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.contained` is mapped to FHIR R4B 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="NamingSystem.name"/>
<display value="name"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.name"/>
<display value="NamingSystem.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.name` is mapped to FHIR R4B element `NamingSystem.name` as `Equivalent`.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.The"symbolic name" for an OID would be captured as an extension."/>
</target>
</element>
<element>
<code value="NamingSystem.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.status"/>
<display value="NamingSystem.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.status` is mapped to FHIR R4B element `NamingSystem.status` as `Equivalent`.
Allows filtering of naming systems that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."/>
</target>
</element>
<element>
<code value="NamingSystem.kind"/>
<display value="kind"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.kind"/>
<display value="NamingSystem.kind"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.kind` is mapped to FHIR R4B element `NamingSystem.kind` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.date"/>
<display value="date"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.date"/>
<display value="NamingSystem.date"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.date` is mapped to FHIR R4B element `NamingSystem.date` as `Equivalent`.
The date is often not tracked until the resource is published, but may be present on draft content. 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.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."/>
</target>
</element>
<element>
<code value="NamingSystem.publisher"/>
<display value="publisher"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.publisher"/>
<display value="NamingSystem.publisher"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.publisher` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.contact"/>
<display value="NamingSystem.contact"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.contact` is mapped to FHIR R4B element `NamingSystem.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc.
See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."/>
</target>
</element>
<element>
<code value="NamingSystem.responsible"/>
<display value="responsible"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.responsible"/>
<display value="NamingSystem.responsible"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.responsible` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.type"/>
<display value="NamingSystem.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.type` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.description"/>
<display value="NamingSystem.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.description` is mapped to FHIR R4B element `NamingSystem.description` as `Equivalent`.
This description can be used to capture details such as 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 naming system is presumed to be the predominant language in the place the naming system was created)."/>
</target>
</element>
<element>
<code value="NamingSystem.useContext"/>
<display value="useContext"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.useContext"/>
<display value="NamingSystem.useContext"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.useContext` is mapped to FHIR R4B element `NamingSystem.useContext` as `Equivalent`.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply."/>
</target>
</element>
<element>
<code value="NamingSystem.jurisdiction"/>
<display value="jurisdiction"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.jurisdiction"/>
<display value="NamingSystem.jurisdiction"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.jurisdiction` is mapped to FHIR R4B element `NamingSystem.jurisdiction` as `Equivalent`.
Element `NamingSystem.jurisdiction` has been flagged as deprecated.
It may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)"/>
</target>
</element>
<element>
<code value="NamingSystem.usage"/>
<display value="usage"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.usage"/>
<display value="NamingSystem.usage"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.usage` is mapped to FHIR R4B element `NamingSystem.usage` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId"/>
<display value="uniqueId"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="NamingSystem.uniqueId"/>
<display value="NamingSystem.uniqueId"/>
<equivalence value="wider"/>
<comment
value="Element `NamingSystem.uniqueId` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="NamingSystem.uniqueId.type"/>
<display value="NamingSystem.uniqueId.type"/>
<equivalence value="wider"/>
<comment
value="Element `NamingSystem.uniqueId.type` is mapped to FHIR R4B element `NamingSystem.uniqueId.type` as `RelatedTo`.
The mappings for `NamingSystem.uniqueId.type` do not allow expression of the necessary codes, per the bindings on the source and target.
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. Preferred identifiers for the same identifier type SHOULD NOT overlap by period."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.value"/>
<display value="value"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.uniqueId.value"/>
<display value="NamingSystem.uniqueId.value"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.value` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.uniqueId.preferred"/>
<display value="NamingSystem.uniqueId.preferred"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.preferred` is mapped to FHIR R4B element `NamingSystem.uniqueId.preferred` as `Equivalent`."/>
</target>
</element>
<element>
<code value="NamingSystem.uniqueId.comment"/>
<display value="comment"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.uniqueId.comment"/>
<display value="NamingSystem.uniqueId.comment"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.comment` is mapped to FHIR R4B 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>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="NamingSystem.uniqueId.period"/>
<display value="NamingSystem.uniqueId.period"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.period` is mapped to FHIR R4B 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).
The nuance of identifier deprecation is not represented with a separate element. When a determination is made that an identifier should not be used, the validity period end date is updated with the date the identifier is deemed to be deprecated. The identifier should no longer be used once the period end date is reached."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.uniqueId.type"/>
<targetVersion value="0.1.0"/>
<element>
<code value="NamingSystem.uniqueId.type"/>
<display value="type"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `NamingSystem.uniqueId.type` is mapped to FHIR R4B element `NamingSystem.uniqueId.type` as `RelatedTo`.
The mappings for `NamingSystem.uniqueId.type` do not allow expression of the necessary codes, per the bindings on the source and target.
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. Preferred identifiers for the same identifier type SHOULD NOT overlap by period."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/NamingSystem"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.uniqueId.authoritative"/>
<targetVersion value="0.1.0"/>
<element>
<code value="NamingSystem.uniqueId.authoritative"/>
<display value="authoritative"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `NamingSystem.uniqueId.authoritative` has a context of NamingSystem.uniqueId based on following the parent source element upwards and mapping to `NamingSystem`.
Element `NamingSystem.uniqueId.authoritative` has no mapping targets in FHIR R4B. 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-r5.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change