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

Lookup for Profile_R3_Binary_R4B

Lookup for FHIR STU3 Binary for use in FHIR R4B

The FHIR STU3 resource is represented in FHIR R4B via the Binary resource.

Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: Binary

A computable version of the following element information is available in: R3BinaryElementMapToR4B

Source Element (FHIR STU3) Target(s) Comments
Binary    
Binary.meta Binary.meta
Extension: ExtensionBinary_Meta		 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.
Binary.implicitRules Binary.implicitRules Element Binary.implicitRules is mapped to FHIR R4B element Binary.implicitRules as Equivalent.
Binary.language Binary.language Element Binary.language is mapped to FHIR R4B element Binary.language as Equivalent.
Binary.contentType Binary.contentType Element Binary.contentType is mapped to FHIR R4B element Binary.contentType as Equivalent.
Binary.securityContext Binary.securityContext
Standard Extension: alternate-reference		 Element 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 Binary.data Element Binary.content is mapped to FHIR R4B element Binary.data as Equivalent.