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

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

ConceptMap: R5ResourceElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 Resource to FHIR R4.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Resource|5.0.0 to Resourceversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Resource.meta (meta)​is equivalent toResource.metaElement `Resource.meta` is mapped to FHIR R4 element `Resource.meta` as `Equivalent`.
Resource.implicitRules (implicitRules)​is equivalent toResource.implicitRulesElement `Resource.implicitRules` is mapped to FHIR R4 element `Resource.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 its narrative along with other profiles, value sets, etc.
Resource.language (language)​is equivalent toResource.languageElement `Resource.language` is mapped to FHIR R4 element `Resource.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).

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Resource|5.0.0 to R5: Issues with the Bundle (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Resource.meta (meta)​is equivalent toExtension.extension:meta (R5: meta)Element `Resource.meta` is mapped to FHIR R4 element `Resource.meta` as `Equivalent`.
Resource.implicitRules (implicitRules)​is equivalent toExtension.extension:implicitRules (R5: implicitRules)Element `Resource.implicitRules` is mapped to FHIR R4 element `Resource.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 its narrative along with other profiles, value sets, etc.
Resource.language (language)​is equivalent toExtension.extension:language (R5: language)Element `Resource.language` is mapped to FHIR R4 element `Resource.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).