Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4B in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R4BNamingSystemElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-NamingSystem-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4BNamingSystemElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR R4B NamingSystem to FHIR R4.

Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/NamingSystem|4.3.0 to NamingSystemversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
NamingSystem.meta (meta)is equivalent toNamingSystem.metaElement `NamingSystem.meta` is mapped to FHIR R4 element `NamingSystem.meta` as `Equivalent`.
NamingSystem.implicitRules (implicitRules)is equivalent toNamingSystem.implicitRulesElement `NamingSystem.implicitRules` is mapped to FHIR R4 element `NamingSystem.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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.
NamingSystem.language (language)is equivalent toNamingSystem.languageElement `NamingSystem.language` is mapped to FHIR R4 element `NamingSystem.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
NamingSystem.text (text)is equivalent toNamingSystem.textElement `NamingSystem.text` is mapped to FHIR R4 element `NamingSystem.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
NamingSystem.contained (contained)is equivalent toNamingSystem.containedElement `NamingSystem.contained` is mapped to FHIR R4 element `NamingSystem.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
NamingSystem.name (name)is equivalent toNamingSystem.nameElement `NamingSystem.name` is mapped to FHIR R4 element `NamingSystem.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.The"symbolic name" for an OID would be captured as an extension.
NamingSystem.status (status)is equivalent toNamingSystem.statusElement `NamingSystem.status` is mapped to FHIR R4 element `NamingSystem.status` as `Equivalent`. Allows filtering of naming systems that are appropriate for use versus not.
NamingSystem.kind (kind)is equivalent toNamingSystem.kindElement `NamingSystem.kind` is mapped to FHIR R4 element `NamingSystem.kind` as `Equivalent`.
NamingSystem.date (date)is equivalent toNamingSystem.dateElement `NamingSystem.date` is mapped to FHIR R4 element `NamingSystem.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the naming system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
NamingSystem.publisher (publisher)is equivalent toNamingSystem.publisherElement `NamingSystem.publisher` is mapped to FHIR R4 element `NamingSystem.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the naming system is the organization or individual primarily responsible for the maintenance and upkeep of the naming system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the naming system. This item SHOULD be populated unless the information is available from context.
NamingSystem.contact (contact)is equivalent toNamingSystem.contactElement `NamingSystem.contact` is mapped to FHIR R4 element `NamingSystem.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
NamingSystem.responsible (responsible)is equivalent toNamingSystem.responsibleElement `NamingSystem.responsible` is mapped to FHIR R4 element `NamingSystem.responsible` as `Equivalent`. This is the primary organization. Responsibility for some aspects of a namespace may be delegated.
NamingSystem.type (type)is equivalent toNamingSystem.typeElement `NamingSystem.type` is mapped to FHIR R4 element `NamingSystem.type` as `Equivalent`. This will most commonly be used for identifier namespaces, but categories could potentially be useful for code systems and authorities as well.
NamingSystem.description (description)is equivalent toNamingSystem.descriptionElement `NamingSystem.description` is mapped to FHIR R4 element `NamingSystem.description` as `Equivalent`. This description can be used to capture details such as why the naming system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the naming system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the naming system is presumed to be the predominant language in the place the naming system was created).
NamingSystem.useContext (useContext)is equivalent toNamingSystem.useContextElement `NamingSystem.useContext` is mapped to FHIR R4 element `NamingSystem.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
NamingSystem.jurisdiction (jurisdiction)is equivalent toNamingSystem.jurisdictionElement `NamingSystem.jurisdiction` is mapped to FHIR R4 element `NamingSystem.jurisdiction` as `Equivalent`. It may be possible for the naming system to be used in jurisdictions other than those for which it was originally designed or intended.
NamingSystem.usage (usage)is equivalent toNamingSystem.usageElement `NamingSystem.usage` is mapped to FHIR R4 element `NamingSystem.usage` as `Equivalent`.
NamingSystem.uniqueId (uniqueId)maps to wider conceptNamingSystem.uniqueIdElement `NamingSystem.uniqueId` is mapped to FHIR R4 element `NamingSystem.uniqueId` as `Equivalent`. Multiple identifiers may exist, either due to duplicate registration, regional rules, needs of different communication technologies, etc.
NamingSystem.uniqueId.type (type)is equivalent toNamingSystem.uniqueId.typeElement `NamingSystem.uniqueId.type` is mapped to FHIR R4 element `NamingSystem.uniqueId.type` as `Equivalent`. Different identifier types may be used in different types of communications (OIDs for v3, URIs for FHIR, etc.). Other includes RUIDs from v3, standard v2 code name strings, etc.
NamingSystem.uniqueId.value (value)is equivalent toNamingSystem.uniqueId.valueElement `NamingSystem.uniqueId.value` is mapped to FHIR R4 element `NamingSystem.uniqueId.value` as `Equivalent`. If the value is a URI intended for use as FHIR system identifier, the URI should not contain "\" or "?" or "," since this makes escaping very difficult.
NamingSystem.uniqueId.preferred (preferred)is equivalent toNamingSystem.uniqueId.preferredElement `NamingSystem.uniqueId.preferred` is mapped to FHIR R4 element `NamingSystem.uniqueId.preferred` as `Equivalent`.
NamingSystem.uniqueId.comment (comment)is equivalent toNamingSystem.uniqueId.commentElement `NamingSystem.uniqueId.comment` is mapped to FHIR R4 element `NamingSystem.uniqueId.comment` as `Equivalent`. e.g. "must be used in Germany" or "was initially published in error with this value".
NamingSystem.uniqueId.period (period)is equivalent toNamingSystem.uniqueId.periodElement `NamingSystem.uniqueId.period` is mapped to FHIR R4 element `NamingSystem.uniqueId.period` as `Equivalent`. Within a registry, a given identifier should only be "active" for a single namespace at a time. (Ideally, an identifier should only ever be associated with a single namespace across all time).