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

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

ConceptMap: R3BinaryElementMapToR4B

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

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

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


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

Source CodeRelationshipTarget CodeComment
Binary.meta (meta)maps to wider conceptBinary.metaElement `Binary.meta` is mapped to FHIR R4B element `Binary.meta` as `SourceIsBroaderThanTarget`. The mappings for `Binary.meta` do not cover the following types: Meta. The mappings for `Binary.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Binary.implicitRules (implicitRules)is equivalent toBinary.implicitRulesElement `Binary.implicitRules` is mapped to FHIR R4B element `Binary.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.
Binary.language (language)is equivalent toBinary.languageElement `Binary.language` is mapped to FHIR R4B element `Binary.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).
Binary.contentType (contentType)is equivalent toBinary.contentTypeElement `Binary.contentType` is mapped to FHIR R4B element `Binary.contentType` as `Equivalent`.
Binary.securityContext (securityContext)maps to wider conceptBinary.securityContextElement `Binary.securityContext` is mapped to FHIR R4B element `Binary.securityContext` as `SourceIsBroaderThanTarget`. The mappings for `Binary.securityContext` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Binary.securityContext` with unmapped reference targets: Resource.
Binary.content (content)is equivalent toBinary.dataElement `Binary.content` is mapped to FHIR R4B element `Binary.data` as `Equivalent`. If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Binary|3.0.2 to STU3: meta additional typesversion: 0.1.0)

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