Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "ConceptMap",
"id" : "R4B-NamingSystem-element-map-to-R4",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R4B-NamingSystem-element-map-to-R4</b></p><a name=\"R4B-NamingSystem-element-map-to-R4\"> </a><a name=\"hcR4B-NamingSystem-element-map-to-R4\"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/NamingSystem|4.3.0</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`.\nAsserting 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>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`.\nLanguage 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`.\nContained 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>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`.\nThis 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=\"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`.\nThe 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=\"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`.\nAllows filtering of naming systems that are appropriate for use versus not.</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`.\nNote 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`.\nUsually 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`.\nMay 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`.\nThis 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`.\nThis 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`.\nThis 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 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=\"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`.\nWhen 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=\"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`.\nIt 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`.\nMultiple 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`.\nDifferent 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`.\nIf 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`.\ne.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`.\nWithin 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></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fhir"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 0,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-NamingSystem-element-map-to-R4",
"version" : "0.1.0",
"name" : "R4BNamingSystemElementMapToR4",
"title" : "Cross-version mapping for FHIR R4B NamingSystem to FHIR R4 NamingSystem",
"status" : "active",
"experimental" : false,
"date" : "2026-03-17T16:03:46.7408639-05:00",
"contact" : [
{
"name" : "FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description" : "This ConceptMap represents cross-version mappings for elements from a FHIR R4B NamingSystem to FHIR R4.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"sourceCanonical" : "http://hl7.org/fhir/4.3",
"targetUri" : "http://hl7.org/fhir/4.0",
"group" : [
{
"source" : "http://hl7.org/fhir/StructureDefinition/NamingSystem",
"sourceVersion" : "4.3.0",
"target" : "http://hl7.org/fhir/StructureDefinition/NamingSystem",
"targetVersion" : "4.0.1",
"element" : [
{
"code" : "NamingSystem.meta",
"display" : "meta",
"target" : [
{
"code" : "NamingSystem.meta",
"display" : "NamingSystem.meta",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.meta` is mapped to FHIR R4 element `NamingSystem.meta` as `Equivalent`."
}
]
},
{
"code" : "NamingSystem.implicitRules",
"display" : "implicitRules",
"target" : [
{
"code" : "NamingSystem.implicitRules",
"display" : "NamingSystem.implicitRules",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.implicitRules` is mapped to FHIR R4 element `NamingSystem.implicitRules` as `Equivalent`.\nAsserting 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."
}
]
},
{
"code" : "NamingSystem.language",
"display" : "language",
"target" : [
{
"code" : "NamingSystem.language",
"display" : "NamingSystem.language",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.language` is mapped to FHIR R4 element `NamingSystem.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code" : "NamingSystem.text",
"display" : "text",
"target" : [
{
"code" : "NamingSystem.text",
"display" : "NamingSystem.text",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.text` is mapped to FHIR R4 element `NamingSystem.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code" : "NamingSystem.contained",
"display" : "contained",
"target" : [
{
"code" : "NamingSystem.contained",
"display" : "NamingSystem.contained",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.contained` is mapped to FHIR R4 element `NamingSystem.contained` as `Equivalent`.\nThis 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."
}
]
},
{
"code" : "NamingSystem.name",
"display" : "name",
"target" : [
{
"code" : "NamingSystem.name",
"display" : "NamingSystem.name",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.name` is mapped to FHIR R4 element `NamingSystem.name` as `Equivalent`.\nThe 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."
}
]
},
{
"code" : "NamingSystem.status",
"display" : "status",
"target" : [
{
"code" : "NamingSystem.status",
"display" : "NamingSystem.status",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.status` is mapped to FHIR R4 element `NamingSystem.status` as `Equivalent`.\nAllows filtering of naming systems that are appropriate for use versus not."
}
]
},
{
"code" : "NamingSystem.kind",
"display" : "kind",
"target" : [
{
"code" : "NamingSystem.kind",
"display" : "NamingSystem.kind",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.kind` is mapped to FHIR R4 element `NamingSystem.kind` as `Equivalent`."
}
]
},
{
"code" : "NamingSystem.date",
"display" : "date",
"target" : [
{
"code" : "NamingSystem.date",
"display" : "NamingSystem.date",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.date` is mapped to FHIR R4 element `NamingSystem.date` as `Equivalent`.\nNote 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."
}
]
},
{
"code" : "NamingSystem.publisher",
"display" : "publisher",
"target" : [
{
"code" : "NamingSystem.publisher",
"display" : "NamingSystem.publisher",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.publisher` is mapped to FHIR R4 element `NamingSystem.publisher` as `Equivalent`.\nUsually 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."
}
]
},
{
"code" : "NamingSystem.contact",
"display" : "contact",
"target" : [
{
"code" : "NamingSystem.contact",
"display" : "NamingSystem.contact",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.contact` is mapped to FHIR R4 element `NamingSystem.contact` as `Equivalent`.\nMay be a web site, an email address, a telephone number, etc."
}
]
},
{
"code" : "NamingSystem.responsible",
"display" : "responsible",
"target" : [
{
"code" : "NamingSystem.responsible",
"display" : "NamingSystem.responsible",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.responsible` is mapped to FHIR R4 element `NamingSystem.responsible` as `Equivalent`.\nThis is the primary organization. Responsibility for some aspects of a namespace may be delegated."
}
]
},
{
"code" : "NamingSystem.type",
"display" : "type",
"target" : [
{
"code" : "NamingSystem.type",
"display" : "NamingSystem.type",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.type` is mapped to FHIR R4 element `NamingSystem.type` as `Equivalent`.\nThis will most commonly be used for identifier namespaces, but categories could potentially be useful for code systems and authorities as well."
}
]
},
{
"code" : "NamingSystem.description",
"display" : "description",
"target" : [
{
"code" : "NamingSystem.description",
"display" : "NamingSystem.description",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.description` is mapped to FHIR R4 element `NamingSystem.description` as `Equivalent`.\nThis 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 naming system is presumed to be the predominant language in the place the naming system was created)."
}
]
},
{
"code" : "NamingSystem.useContext",
"display" : "useContext",
"target" : [
{
"code" : "NamingSystem.useContext",
"display" : "NamingSystem.useContext",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.useContext` is mapped to FHIR R4 element `NamingSystem.useContext` as `Equivalent`.\nWhen multiple useContexts are specified, there is no expectation that all or any of the contexts apply."
}
]
},
{
"code" : "NamingSystem.jurisdiction",
"display" : "jurisdiction",
"target" : [
{
"code" : "NamingSystem.jurisdiction",
"display" : "NamingSystem.jurisdiction",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.jurisdiction` is mapped to FHIR R4 element `NamingSystem.jurisdiction` as `Equivalent`.\nIt may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended."
}
]
},
{
"code" : "NamingSystem.usage",
"display" : "usage",
"target" : [
{
"code" : "NamingSystem.usage",
"display" : "NamingSystem.usage",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.usage` is mapped to FHIR R4 element `NamingSystem.usage` as `Equivalent`."
}
]
},
{
"code" : "NamingSystem.uniqueId",
"display" : "uniqueId",
"target" : [
{
"code" : "NamingSystem.uniqueId",
"display" : "NamingSystem.uniqueId",
"equivalence" : "wider",
"comment" : "Element `NamingSystem.uniqueId` is mapped to FHIR R4 element `NamingSystem.uniqueId` as `Equivalent`.\nMultiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc."
}
]
},
{
"code" : "NamingSystem.uniqueId.type",
"display" : "type",
"target" : [
{
"code" : "NamingSystem.uniqueId.type",
"display" : "NamingSystem.uniqueId.type",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.uniqueId.type` is mapped to FHIR R4 element `NamingSystem.uniqueId.type` as `Equivalent`.\nDifferent 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."
}
]
},
{
"code" : "NamingSystem.uniqueId.value",
"display" : "value",
"target" : [
{
"code" : "NamingSystem.uniqueId.value",
"display" : "NamingSystem.uniqueId.value",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.uniqueId.value` is mapped to FHIR R4 element `NamingSystem.uniqueId.value` as `Equivalent`.\nIf 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."
}
]
},
{
"code" : "NamingSystem.uniqueId.preferred",
"display" : "preferred",
"target" : [
{
"code" : "NamingSystem.uniqueId.preferred",
"display" : "NamingSystem.uniqueId.preferred",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.uniqueId.preferred` is mapped to FHIR R4 element `NamingSystem.uniqueId.preferred` as `Equivalent`."
}
]
},
{
"code" : "NamingSystem.uniqueId.comment",
"display" : "comment",
"target" : [
{
"code" : "NamingSystem.uniqueId.comment",
"display" : "NamingSystem.uniqueId.comment",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.uniqueId.comment` is mapped to FHIR R4 element `NamingSystem.uniqueId.comment` as `Equivalent`.\ne.g. \"must be used in Germany\" or \"was initially published in error with this value\"."
}
]
},
{
"code" : "NamingSystem.uniqueId.period",
"display" : "period",
"target" : [
{
"code" : "NamingSystem.uniqueId.period",
"display" : "NamingSystem.uniqueId.period",
"equivalence" : "equivalent",
"comment" : "Element `NamingSystem.uniqueId.period` is mapped to FHIR R4 element `NamingSystem.uniqueId.period` as `Equivalent`.\nWithin 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)."
}
]
}
]
}
]
}
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.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