Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-NamingSystem-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3NamingSystemElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 NamingSystem to FHIR R5.
Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to NamingSystemversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.meta (meta) | is broader than | NamingSystem.meta | Element `NamingSystem.meta` is mapped to FHIR R5 element `NamingSystem.meta` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.meta` do not cover the following types: Meta. The mappings for `NamingSystem.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
| NamingSystem.implicitRules (implicitRules) | is equivalent to | NamingSystem.implicitRules | Element `NamingSystem.implicitRules` is mapped to FHIR R5 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. |
| NamingSystem.language (language) | is equivalent to | NamingSystem.language | Element `NamingSystem.language` is mapped to FHIR R5 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). |
| NamingSystem.text (text) | is broader than | NamingSystem.text | Element `NamingSystem.text` is mapped to FHIR R5 element `NamingSystem.text` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.text` do not cover the following types: Narrative. The mappings for `NamingSystem.text` do not cover the following types based on type expansion: div, status. 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. |
| NamingSystem.contained (contained) | is equivalent to | NamingSystem.contained | Element `NamingSystem.contained` is mapped to FHIR R5 element `NamingSystem.contained` as `SourceIsBroaderThanTarget`. 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. |
| NamingSystem.name (name) | is equivalent to | NamingSystem.name | Element `NamingSystem.name` is mapped to FHIR R5 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. |
| NamingSystem.status (status) | is equivalent to | NamingSystem.status | Element `NamingSystem.status` is mapped to FHIR R5 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. |
| NamingSystem.kind (kind) | is equivalent to | NamingSystem.kind | Element `NamingSystem.kind` is mapped to FHIR R5 element `NamingSystem.kind` as `Equivalent`. |
| NamingSystem.date (date) | is equivalent to | NamingSystem.date | Element `NamingSystem.date` is mapped to FHIR R5 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. |
| NamingSystem.publisher (publisher) | is equivalent to | NamingSystem.publisher | Element `NamingSystem.publisher` is mapped to FHIR R5 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. |
| NamingSystem.contact (contact) | is broader than | NamingSystem.contact | Element `NamingSystem.contact` is mapped to FHIR R5 element `NamingSystem.contact` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.contact` do not cover the following types: ContactDetail. The mappings for `NamingSystem.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. |
| NamingSystem.responsible (responsible) | is equivalent to | NamingSystem.responsible | Element `NamingSystem.responsible` is mapped to FHIR R5 element `NamingSystem.responsible` as `Equivalent`. This is the primary organization. Responsibility for some aspects of a namespace may be delegated. |
| NamingSystem.type (type) | is equivalent to | NamingSystem.type | Element `NamingSystem.type` is mapped to FHIR R5 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. |
| NamingSystem.description (description) | is equivalent to | NamingSystem.description | Element `NamingSystem.description` is mapped to FHIR R5 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). |
| NamingSystem.useContext (useContext) | is broader than | NamingSystem.useContext | Element `NamingSystem.useContext` is mapped to FHIR R5 element `NamingSystem.useContext` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.useContext` do not cover the following types: UsageContext. The mappings for `NamingSystem.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. |
| NamingSystem.jurisdiction (jurisdiction) | is equivalent to | NamingSystem.jurisdiction | Element `NamingSystem.jurisdiction` is mapped to FHIR R5 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. |
| NamingSystem.usage (usage) | is equivalent to | NamingSystem.usage | Element `NamingSystem.usage` is mapped to FHIR R5 element `NamingSystem.usage` as `Equivalent`. |
| NamingSystem.uniqueId (uniqueId) | is broader than | NamingSystem.uniqueId | Element `NamingSystem.uniqueId` is mapped to FHIR R5 element `NamingSystem.uniqueId` as `Equivalent`. Multiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc. |
| NamingSystem.uniqueId.type (type) | is broader than | NamingSystem.uniqueId.type | Element `NamingSystem.uniqueId.type` is mapped to FHIR R5 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. |
| NamingSystem.uniqueId.value (value) | is equivalent to | NamingSystem.uniqueId.value | Element `NamingSystem.uniqueId.value` is mapped to FHIR R5 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. |
| NamingSystem.uniqueId.preferred (preferred) | is equivalent to | NamingSystem.uniqueId.preferred | Element `NamingSystem.uniqueId.preferred` is mapped to FHIR R5 element `NamingSystem.uniqueId.preferred` as `Equivalent`. |
| NamingSystem.uniqueId.comment (comment) | is equivalent to | NamingSystem.uniqueId.comment | Element `NamingSystem.uniqueId.comment` is mapped to FHIR R5 element `NamingSystem.uniqueId.comment` as `Equivalent`. e.g. "must be used in Germany" or "was initially published in error with this value". |
| NamingSystem.uniqueId.period (period) | is broader than | NamingSystem.uniqueId.period | Element `NamingSystem.uniqueId.period` is mapped to FHIR R5 element `NamingSystem.uniqueId.period` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.uniqueId.period` do not cover the following types: Period. The mappings for `NamingSystem.uniqueId.period` do not cover the following types based on type expansion: end, start. 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). |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.meta (meta) | is equivalent to | Extension (STU3: meta additional types) | Element `NamingSystem.meta` is mapped to FHIR R5 element `NamingSystem.meta` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.meta` do not cover the following types: Meta. The mappings for `NamingSystem.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.text (text) | is equivalent to | Extension (STU3: text additional types) | Element `NamingSystem.text` is mapped to FHIR R5 element `NamingSystem.text` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.text` do not cover the following types: Narrative. The mappings for `NamingSystem.text` do not cover the following types based on type expansion: div, status. 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. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: contact additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.contact (contact) | is equivalent to | Extension (STU3: contact additional types) | Element `NamingSystem.contact` is mapped to FHIR R5 element `NamingSystem.contact` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.contact` do not cover the following types: ContactDetail. The mappings for `NamingSystem.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: Context the content is intended to support additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.useContext (useContext) | is equivalent to | Extension (STU3: Context the content is intended to support additional types) | Element `NamingSystem.useContext` is mapped to FHIR R5 element `NamingSystem.useContext` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.useContext` do not cover the following types: UsageContext. The mappings for `NamingSystem.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: oid | uuid | uri | other additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.uniqueId.type (type) | is equivalent to | Extension (STU3: oid | uuid | uri | other additional codes) | Element `NamingSystem.uniqueId.type` is mapped to FHIR R5 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. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: period additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.uniqueId.period (period) | is equivalent to | Extension (STU3: period additional types) | Element `NamingSystem.uniqueId.period` is mapped to FHIR R5 element `NamingSystem.uniqueId.period` as `SourceIsBroaderThanTarget`. The mappings for `NamingSystem.uniqueId.period` do not cover the following types: Period. The mappings for `NamingSystem.uniqueId.period` do not cover the following types based on type expansion: end, start. 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). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|3.0.2 to STU3: Use this instead (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.replacedBy (replacedBy) | is equivalent to | Extension (STU3: Use this instead (new)) | 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 R5. Typically, this is because the element has been added (is a new element). |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r3.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change