FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

Note: links and images are rebased to the (stated) source

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-Binary-element-map-to-R4",
  "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.r4"
          }
        ]
      }
    },
    {
      "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.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Binary-element-map-to-R4",
  "version": "0.1.0",
  "name": "R5BinaryElementMapToR4",
  "title": "Cross-version mapping for FHIR R5 Binary to FHIR R4 Binary",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:44.0362356-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 R4.",
  "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.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Binary",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Binary",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "Binary.meta",
          "display": "meta",
          "target": [
            {
              "code": "Binary.meta",
              "display": "Binary.meta",
              "equivalence": "equivalent",
              "comment": "Element `Binary.meta` is mapped to FHIR R4 element `Binary.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Binary.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Binary.implicitRules",
              "display": "Binary.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `Binary.implicitRules` is mapped to FHIR R4 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": [
            {
              "code": "Binary.language",
              "display": "Binary.language",
              "equivalence": "equivalent",
              "comment": "Element `Binary.language` is mapped to FHIR R4 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": [
            {
              "code": "Binary.contentType",
              "display": "Binary.contentType",
              "equivalence": "equivalent",
              "comment": "Element `Binary.contentType` is mapped to FHIR R4 element `Binary.contentType` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Binary.securityContext",
          "display": "securityContext",
          "target": [
            {
              "code": "Binary.securityContext",
              "display": "Binary.securityContext",
              "equivalence": "equivalent",
              "comment": "Element `Binary.securityContext` is mapped to FHIR R4 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": [
            {
              "code": "Binary.data",
              "display": "Binary.data",
              "equivalence": "equivalent",
              "comment": "Element `Binary.data` is mapped to FHIR R4 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."
            }
          ]
        }
      ]
    }
  ]
}