FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r4b |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-Binary-element-map-to-R4B.json |
| FHIR Version | R4B |
| Source | http://hl7.org/fhir/uv/xver-r5.r4b/0.1.0/ConceptMap-R5-Binary-element-map-to-R4B.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-Binary-element-map-to-R4B |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:55.7318244-05:00 |
| Name | R5BinaryElementMapToR4B |
| Title | Cross-version mapping for FHIR R5 Binary to FHIR R4B Binary |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 Binary to FHIR R4B. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-Binary-element-map-to-R4B
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Binary|5.0.0 to Binaryversion: 4.3.0)
| Source Code | Relationship | Target Code | Comment |
| Binary.meta (meta) | is equivalent to | Binary.meta | Element `Binary.meta` is mapped to FHIR R4B element `Binary.meta` as `Equivalent`. |
| Binary.implicitRules (implicitRules) | is equivalent to | Binary.implicitRules | Element `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. 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. |
| Binary.language (language) | is equivalent to | Binary.language | Element `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 to | Binary.contentType | Element `Binary.contentType` is mapped to FHIR R4B element `Binary.contentType` as `Equivalent`. |
| Binary.securityContext (securityContext) | is equivalent to | Binary.securityContext | Element `Binary.securityContext` is mapped to FHIR R4B element `Binary.securityContext` as `Equivalent`. Very often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it. |
| Binary.data (data) | is equivalent to | Binary.data | Element `Binary.data` 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. |
FHIR
FHIRsmith{
"resourceType": "ConceptMap",
"id": "R5-Binary-element-map-to-R4B",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Binary-element-map-to-R4B",
"version": "0.1.0",
"name": "R5BinaryElementMapToR4B",
"title": "Cross-version mapping for FHIR R5 Binary to FHIR R4B Binary",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:55.7318244-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 Binary to FHIR R4B.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/4.3",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/Binary",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/Binary",
"targetVersion": "4.3.0",
"element": [
{
"code": "Binary.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.meta",
"display": "Binary.meta",
"equivalence": "equivalent",
"comment": "Element `Binary.meta` is mapped to FHIR R4B element `Binary.meta` as `Equivalent`."
}
]
},
{
"code": "Binary.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.implicitRules",
"display": "Binary.implicitRules",
"equivalence": "equivalent",
"comment": "Element `Binary.implicitRules` is mapped to FHIR R4B element `Binary.implicitRules` as `Equivalent`.\nAsserting 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."
}
]
},
{
"code": "Binary.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.language",
"display": "Binary.language",
"equivalence": "equivalent",
"comment": "Element `Binary.language` is mapped to FHIR R4B element `Binary.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code": "Binary.contentType",
"display": "contentType",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.contentType",
"display": "Binary.contentType",
"equivalence": "equivalent",
"comment": "Element `Binary.contentType` is mapped to FHIR R4B element `Binary.contentType` as `Equivalent`."
}
]
},
{
"code": "Binary.securityContext",
"display": "securityContext",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.securityContext",
"display": "Binary.securityContext",
"equivalence": "equivalent",
"comment": "Element `Binary.securityContext` is mapped to FHIR R4B element `Binary.securityContext` as `Equivalent`.\nVery often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it."
}
]
},
{
"code": "Binary.data",
"display": "data",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Binary.data",
"display": "Binary.data",
"equivalence": "equivalent",
"comment": "Element `Binary.data` is mapped to FHIR R4B element `Binary.data` as `Equivalent`.\nIf 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."
}
]
}
]
}
]
}