FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

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

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4B-Endpoint-element-map-to-R5",
  "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-r4b.r5"
          }
        ]
      }
    },
    {
      "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-r4b.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Endpoint-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4BEndpointElementMapToR5",
  "title": "Cross-version mapping for FHIR R4B Endpoint to FHIR R5 Endpoint",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:51.567314-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 R4B Endpoint to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/4.3",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Endpoint|4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Endpoint|5.0.0",
      "element": [
        {
          "code": "Endpoint.meta",
          "display": "meta",
          "target": [
            {
              "code": "Endpoint.meta",
              "display": "Endpoint.meta",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.meta` is mapped to FHIR R5 element `Endpoint.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Endpoint.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Endpoint.implicitRules",
              "display": "Endpoint.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.implicitRules` is mapped to FHIR R5 element `Endpoint.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 it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Endpoint.language",
          "display": "language",
          "target": [
            {
              "code": "Endpoint.language",
              "display": "Endpoint.language",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.language` is mapped to FHIR R5 element `Endpoint.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": "Endpoint.text",
          "display": "text",
          "target": [
            {
              "code": "Endpoint.text",
              "display": "Endpoint.text",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.text` is mapped to FHIR R5 element `Endpoint.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
            }
          ]
        },
        {
          "code": "Endpoint.contained",
          "display": "contained",
          "target": [
            {
              "code": "Endpoint.contained",
              "display": "Endpoint.contained",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.contained` is mapped to FHIR R5 element `Endpoint.contained` as `Equivalent`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."
            }
          ]
        },
        {
          "code": "Endpoint.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Endpoint.identifier",
              "display": "Endpoint.identifier",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.identifier` is mapped to FHIR R5 element `Endpoint.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Endpoint.status",
          "display": "status",
          "target": [
            {
              "code": "Endpoint.status",
              "display": "Endpoint.status",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Endpoint.status` is mapped to FHIR R5 element `Endpoint.status` as `SourceIsBroaderThanTarget`.\nThe target context `Endpoint.status` is a modifier element, so this extension does not need to be defined as a modifier.\nThis element is labeled as a modifier because the status contains codes that mark the endpoint as not currently valid."
            }
          ]
        },
        {
          "code": "Endpoint.connectionType",
          "display": "connectionType",
          "target": [
            {
              "code": "Endpoint.connectionType",
              "display": "Endpoint.connectionType",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.connectionType` is mapped to FHIR R5 element `Endpoint.connectionType` as `SourceIsNarrowerThanTarget`.\nFor additional connectivity details for the protocol, extensions will be used at this point, as in the XDS example."
            }
          ]
        },
        {
          "code": "Endpoint.name",
          "display": "name",
          "target": [
            {
              "code": "Endpoint.name",
              "display": "Endpoint.name",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.name` is mapped to FHIR R5 element `Endpoint.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Endpoint.managingOrganization",
          "display": "managingOrganization",
          "target": [
            {
              "code": "Endpoint.managingOrganization",
              "display": "Endpoint.managingOrganization",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.managingOrganization` is mapped to FHIR R5 element `Endpoint.managingOrganization` as `Equivalent`.\nThis property is not typically used when searching for Endpoint resources for usage. The typical usage is via the reference from an applicable Organization/Location/Practitioner resource, which is where the context is provided. Multiple Locations may reference a single endpoint, and don't have to be within the same organization resource, but most likely within the same organizational hierarchy."
            }
          ]
        },
        {
          "code": "Endpoint.contact",
          "display": "contact",
          "target": [
            {
              "code": "Endpoint.contact",
              "display": "Endpoint.contact",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.contact` is mapped to FHIR R5 element `Endpoint.contact` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Endpoint.period",
          "display": "period",
          "target": [
            {
              "code": "Endpoint.period",
              "display": "Endpoint.period",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.period` is mapped to FHIR R5 element `Endpoint.period` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Endpoint.payloadType",
          "display": "payloadType",
          "target": [
            {
              "code": "Endpoint.payload.type",
              "display": "Endpoint.payload.type",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.payloadType` is mapped to FHIR R5 element `Endpoint.payload.type` as `Equivalent`.\nThe payloadFormat describes the serialization format of the data, where the payloadType indicates the specific document/schema that is being transferred; e.g. DischargeSummary or CarePlan."
            }
          ]
        },
        {
          "code": "Endpoint.payloadMimeType",
          "display": "payloadMimeType",
          "target": [
            {
              "code": "Endpoint.payload.mimeType",
              "display": "Endpoint.payload.mimeType",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.payloadMimeType` is mapped to FHIR R5 element `Endpoint.payload.mimeType` as `Equivalent`.\nSending the payload has obvious security consequences. The server is responsible for ensuring that the content is appropriately secured."
            }
          ]
        },
        {
          "code": "Endpoint.address",
          "display": "address",
          "target": [
            {
              "code": "Endpoint.address",
              "display": "Endpoint.address",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.address` is mapped to FHIR R5 element `Endpoint.address` as `Equivalent`.\nFor rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs)\n\nThis address will be to the service base, without any parameters, or sub-services or resources tacked on.\n\nE.g. for a WADO-RS endpoint, the url should be \"https://pacs.hospital.org/wado-rs\"\n\nand not \"https://pacs.hospital.org/wado-rs/studies/1.2.250.1.59.40211.12345678.678910/series/1.2.250.1.59.40211.789001276.14556172.67789/instances/...\"."
            }
          ]
        },
        {
          "code": "Endpoint.header",
          "display": "header",
          "target": [
            {
              "code": "Endpoint.header",
              "display": "Endpoint.header",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.header` is mapped to FHIR R5 element `Endpoint.header` as `Equivalent`.\nExactly what these mean depends on the channel type. The can convey additional information to the recipient and/or meet security requirements."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Endpoint|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Endpoint.status|0.1.0",
      "element": [
        {
          "code": "Endpoint.status",
          "display": "status",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Endpoint.status` is mapped to FHIR R5 element `Endpoint.status` as `SourceIsBroaderThanTarget`.\nThe target context `Endpoint.status` is a modifier element, so this extension does not need to be defined as a modifier.\nThis element is labeled as a modifier because the status contains codes that mark the endpoint as not currently valid."
            }
          ]
        }
      ]
    }
  ]
}