Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-NamingSystem-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R2NamingSystemElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 NamingSystem to FHIR R5.
Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|1.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 as much as possible. |
| 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. |
| 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"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 `SourceIsNarrowerThanTarget`. The mappings for `NamingSystem.status` do not allow expression of the necessary codes, per the bindings on the source and target. |
| NamingSystem.kind (kind) | is equivalent to | NamingSystem.kind | Element `NamingSystem.kind` is mapped to FHIR R5 element `NamingSystem.kind` as `Equivalent`. |
| 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. 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 `Equivalent`. May be a web site, an email address, a telephone number (tel:), 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.date (date) | is equivalent to | NamingSystem.date | Element `NamingSystem.date` is mapped to FHIR R5 element `NamingSystem.date` as `Equivalent`. Additional specific dates may be added as extensions. |
| 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`. |
| NamingSystem.useContext (useContext) | is equivalent to | NamingSystem.jurisdiction | Element `NamingSystem.useContext` is mapped to FHIR R5 element `NamingSystem.jurisdiction` as `Equivalent`. |
| 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.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|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.meta (meta) | is equivalent to | Extension (DSTU2: 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|1.0.2 to DSTU2: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.text (text) | is equivalent to | Extension (DSTU2: 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. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|1.0.2 to DSTU2: Name of a individual to contact (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.contact.name (name) | is broader than | Extension (DSTU2: Name of a individual to contact (new)) | Element `NamingSystem.contact.name` has a context of NamingSystem.contact based on following the parent source element upwards and mapping to `NamingSystem`. Element `NamingSystem.contact.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If there is no named individual, the telecom is for the organization as a whole. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|1.0.2 to DSTU2: Contact details for individual or publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.contact.telecom (telecom) | is broader than | Extension (DSTU2: Contact details for individual or publisher (new)) | Element `NamingSystem.contact.telecom` has a context of NamingSystem.contact based on following the parent source element upwards and mapping to `NamingSystem`. Element `NamingSystem.contact.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|1.0.2 to DSTU2: oid | uuid | uri | other additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.uniqueId.type (type) | is equivalent to | Extension (DSTU2: 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|1.0.2 to DSTU2: period additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.uniqueId.period (period) | is equivalent to | Extension (DSTU2: 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|1.0.2 to DSTU2: Use this instead (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| NamingSystem.replacedBy (replacedBy) | is equivalent to | Extension (DSTU2: 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-r2.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