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

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

ConceptMap: R4BDomainResourceElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4B DomainResource to FHIR STU3.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DomainResource|4.3.0 to http://hl7.org/fhir/StructureDefinition/DomainResource|3.0.2

Source CodeRelationshipTarget CodeComment
DomainResource.meta (meta)maps to wider conceptDomainResource.metaElement `DomainResource.meta` is mapped to FHIR STU3 element `DomainResource.meta` as `SourceIsBroaderThanTarget`. The mappings for `DomainResource.meta` do not cover the following types: Meta. The mappings for `DomainResource.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.
DomainResource.implicitRules (implicitRules)is equivalent toDomainResource.implicitRulesElement `DomainResource.implicitRules` is mapped to FHIR STU3 element `DomainResource.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.
DomainResource.language (language)is equivalent toDomainResource.languageElement `DomainResource.language` is mapped to FHIR STU3 element `DomainResource.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).
DomainResource.text (text)maps to wider conceptDomainResource.textElement `DomainResource.text` is mapped to FHIR STU3 element `DomainResource.text` as `SourceIsBroaderThanTarget`. The mappings for `DomainResource.text` do not cover the following types: Narrative. The mappings for `DomainResource.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 information is added later.
DomainResource.contained (contained)is equivalent toDomainResource.containedElement `DomainResource.contained` is mapped to FHIR STU3 element `DomainResource.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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DomainResource|4.3.0 to R4B: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DomainResource.meta (meta)is equivalent toExtension (R4B: meta additional types)Element `DomainResource.meta` is mapped to FHIR STU3 element `DomainResource.meta` as `SourceIsBroaderThanTarget`. The mappings for `DomainResource.meta` do not cover the following types: Meta. The mappings for `DomainResource.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DomainResource|4.3.0 to R4B: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DomainResource.text (text)is equivalent toExtension (R4B: text additional types)Element `DomainResource.text` is mapped to FHIR STU3 element `DomainResource.text` as `SourceIsBroaderThanTarget`. The mappings for `DomainResource.text` do not cover the following types: Narrative. The mappings for `DomainResource.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 information is added later.