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": "R4-Composition-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-r4.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-r4.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4-Composition-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4CompositionElementMapToR5",
  "title": "Cross-version mapping for FHIR R4 Composition to FHIR R5 Composition",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:34.7499436-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 R4 Composition 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.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/StructureDefinition/Composition|5.0.0",
      "element": [
        {
          "code": "Composition.meta",
          "display": "meta",
          "target": [
            {
              "code": "Composition.meta",
              "display": "Composition.meta",
              "relationship": "equivalent",
              "comment": "Element `Composition.meta` is mapped to FHIR R5 element `Composition.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Composition.implicitRules",
              "display": "Composition.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Composition.implicitRules` is mapped to FHIR R5 element `Composition.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": "Composition.language",
          "display": "language",
          "target": [
            {
              "code": "Composition.language",
              "display": "Composition.language",
              "relationship": "equivalent",
              "comment": "Element `Composition.language` is mapped to FHIR R5 element `Composition.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": "Composition.text",
          "display": "text",
          "target": [
            {
              "code": "Composition.text",
              "display": "Composition.text",
              "relationship": "equivalent",
              "comment": "Element `Composition.text` is mapped to FHIR R5 element `Composition.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": "Composition.contained",
          "display": "contained",
          "target": [
            {
              "code": "Composition.contained",
              "display": "Composition.contained",
              "relationship": "equivalent",
              "comment": "Element `Composition.contained` is mapped to FHIR R5 element `Composition.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": "Composition.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Composition.identifier",
              "display": "Composition.identifier",
              "relationship": "equivalent",
              "comment": "Element `Composition.identifier` is mapped to FHIR R5 element `Composition.identifier` as `SourceIsNarrowerThanTarget`.\nSimilar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate."
            }
          ]
        },
        {
          "code": "Composition.status",
          "display": "status",
          "target": [
            {
              "code": "Composition.status",
              "display": "Composition.status",
              "relationship": "equivalent",
              "comment": "Element `Composition.status` is mapped to FHIR R5 element `Composition.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Composition.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nIf a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag \"entered-in-error\" is why this element is labeled as a modifier of other elements.   \n\nSome reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required."
            }
          ]
        },
        {
          "code": "Composition.type",
          "display": "type",
          "target": [
            {
              "code": "Composition.type",
              "display": "Composition.type",
              "relationship": "equivalent",
              "comment": "Element `Composition.type` is mapped to FHIR R5 element `Composition.type` as `Equivalent`.\nFor Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding."
            }
          ]
        },
        {
          "code": "Composition.category",
          "display": "category",
          "target": [
            {
              "code": "Composition.category",
              "display": "Composition.category",
              "relationship": "equivalent",
              "comment": "Element `Composition.category` is mapped to FHIR R5 element `Composition.category` as `Equivalent`.\nThis is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD))."
            }
          ]
        },
        {
          "code": "Composition.subject",
          "display": "subject",
          "target": [
            {
              "code": "Composition.subject",
              "display": "Composition.subject",
              "relationship": "equivalent",
              "comment": "Element `Composition.subject` is mapped to FHIR R5 element `Composition.subject` as `SourceIsNarrowerThanTarget`.\nFor clinical documents, this is usually the patient."
            }
          ]
        },
        {
          "code": "Composition.encounter",
          "display": "encounter",
          "target": [
            {
              "code": "Composition.encounter",
              "display": "Composition.encounter",
              "relationship": "equivalent",
              "comment": "Element `Composition.encounter` is mapped to FHIR R5 element `Composition.encounter` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.date",
          "display": "date",
          "target": [
            {
              "code": "Composition.date",
              "display": "Composition.date",
              "relationship": "equivalent",
              "comment": "Element `Composition.date` is mapped to FHIR R5 element `Composition.date` as `Equivalent`.\nThe Last Modified Date on the composition may be after the date of the document was attested without being changed."
            }
          ]
        },
        {
          "code": "Composition.author",
          "display": "author",
          "target": [
            {
              "code": "Composition.author",
              "display": "Composition.author",
              "relationship": "equivalent",
              "comment": "Element `Composition.author` is mapped to FHIR R5 element `Composition.author` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.title",
          "display": "title",
          "target": [
            {
              "code": "Composition.title",
              "display": "Composition.title",
              "relationship": "equivalent",
              "comment": "Element `Composition.title` is mapped to FHIR R5 element `Composition.title` as `Equivalent`.\nFor many compositions, the title is the same as the text or a display name of Composition.type (e.g. a \"consultation\" or \"progress note\"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period."
            }
          ]
        },
        {
          "code": "Composition.attester",
          "display": "attester",
          "target": [
            {
              "code": "Composition.attester",
              "display": "Composition.attester",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.attester` is mapped to FHIR R5 element `Composition.attester` as `Equivalent`.\nOnly list each attester once."
            }
          ]
        },
        {
          "code": "Composition.attester.mode",
          "display": "mode",
          "target": [
            {
              "code": "Composition.attester.mode",
              "display": "Composition.attester.mode",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.attester.mode` is mapped to FHIR R5 element `Composition.attester.mode` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Composition.attester.time",
          "display": "time",
          "target": [
            {
              "code": "Composition.attester.time",
              "display": "Composition.attester.time",
              "relationship": "equivalent",
              "comment": "Element `Composition.attester.time` is mapped to FHIR R5 element `Composition.attester.time` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.attester.party",
          "display": "party",
          "target": [
            {
              "code": "Composition.attester.party",
              "display": "Composition.attester.party",
              "relationship": "equivalent",
              "comment": "Element `Composition.attester.party` is mapped to FHIR R5 element `Composition.attester.party` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.custodian",
          "display": "custodian",
          "target": [
            {
              "code": "Composition.custodian",
              "display": "Composition.custodian",
              "relationship": "equivalent",
              "comment": "Element `Composition.custodian` is mapped to FHIR R5 element `Composition.custodian` as `Equivalent`.\nThis is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged."
            }
          ]
        },
        {
          "code": "Composition.relatesTo",
          "display": "relatesTo",
          "target": [
            {
              "code": "Composition.relatesTo",
              "display": "Composition.relatesTo",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.relatesTo` is mapped to FHIR R5 element `Composition.relatesTo` as `Equivalent`.\nA document is a version specific composition."
            }
          ]
        },
        {
          "code": "Composition.relatesTo.code",
          "display": "code",
          "target": [
            {
              "code": "Composition.relatesTo",
              "display": "Composition.relatesTo",
              "relationship": "related-to",
              "comment": "Element `Composition.relatesTo.code` is mapped to FHIR R5 element `Composition.relatesTo` as `RelatedTo`.\nThe mappings for `Composition.relatesTo.code` do not cover the following types: code.\nThe mappings for `Composition.relatesTo.code` do not cover the following types based on type expansion: value.\nIf this document appends another document, then the document cannot be fully understood without also accessing the referenced document."
            }
          ]
        },
        {
          "code": "Composition.event",
          "display": "event",
          "target": [
            {
              "code": "Composition.event",
              "display": "Composition.event",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.event` is mapped to FHIR R5 element `Composition.event` as `Equivalent`.\nThe event needs to be consistent with the type element, though can provide further information if desired."
            }
          ]
        },
        {
          "code": "Composition.event.period",
          "display": "period",
          "target": [
            {
              "code": "Composition.event.period",
              "display": "Composition.event.period",
              "relationship": "equivalent",
              "comment": "Element `Composition.event.period` is mapped to FHIR R5 element `Composition.event.period` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.event.detail",
          "display": "detail",
          "target": [
            {
              "code": "Composition.event.detail",
              "display": "Composition.event.detail",
              "relationship": "equivalent",
              "comment": "Element `Composition.event.detail` is mapped to FHIR R5 element `Composition.event.detail` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Composition.section",
          "display": "section",
          "target": [
            {
              "code": "Composition.section",
              "display": "Composition.section",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.section` is mapped to FHIR R5 element `Composition.section` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.section.title",
          "display": "title",
          "target": [
            {
              "code": "Composition.section.title",
              "display": "Composition.section.title",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.title` is mapped to FHIR R5 element `Composition.section.title` as `Equivalent`.\nThe title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element."
            }
          ]
        },
        {
          "code": "Composition.section.code",
          "display": "code",
          "target": [
            {
              "code": "Composition.section.code",
              "display": "Composition.section.code",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.code` is mapped to FHIR R5 element `Composition.section.code` as `Equivalent`.\nThe code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.   \n\nIf the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code."
            }
          ]
        },
        {
          "code": "Composition.section.author",
          "display": "author",
          "target": [
            {
              "code": "Composition.section.author",
              "display": "Composition.section.author",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.author` is mapped to FHIR R5 element `Composition.section.author` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Composition.section.focus",
          "display": "focus",
          "target": [
            {
              "code": "Composition.section.focus",
              "display": "Composition.section.focus",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.focus` is mapped to FHIR R5 element `Composition.section.focus` as `Equivalent`.\nTypically, sections in a doument are about the subject of the document, whether that is a  patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are  a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples."
            }
          ]
        },
        {
          "code": "Composition.section.text",
          "display": "text",
          "target": [
            {
              "code": "Composition.section.text",
              "display": "Composition.section.text",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.text` is mapped to FHIR R5 element `Composition.section.text` as `Equivalent`.\nDocument profiles may define what content should be represented in the narrative to ensure clinical safety."
            }
          ]
        },
        {
          "code": "Composition.section.orderedBy",
          "display": "orderedBy",
          "target": [
            {
              "code": "Composition.section.orderedBy",
              "display": "Composition.section.orderedBy",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.orderedBy` is mapped to FHIR R5 element `Composition.section.orderedBy` as `Equivalent`.\nApplications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order."
            }
          ]
        },
        {
          "code": "Composition.section.entry",
          "display": "entry",
          "target": [
            {
              "code": "Composition.section.entry",
              "display": "Composition.section.entry",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.entry` is mapped to FHIR R5 element `Composition.section.entry` as `Equivalent`.\nIf there are no entries in the list, an emptyReason SHOULD be provided."
            }
          ]
        },
        {
          "code": "Composition.section.emptyReason",
          "display": "emptyReason",
          "target": [
            {
              "code": "Composition.section.emptyReason",
              "display": "Composition.section.emptyReason",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.emptyReason` is mapped to FHIR R5 element `Composition.section.emptyReason` as `Equivalent`.\nThe various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases."
            }
          ]
        },
        {
          "code": "Composition.section.section",
          "display": "section",
          "target": [
            {
              "code": "Composition.section.section",
              "display": "Composition.section.section",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.section` is mapped to FHIR R5 element `Composition.section.section` as `Equivalent`.\nNested sections are primarily used to help human readers navigate to particular portions of the document."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.confidentiality|0.1.0",
      "element": [
        {
          "code": "Composition.confidentiality",
          "display": "confidentiality",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Composition.confidentiality` has a context of Composition based on following the parent source element upwards and mapping to `Composition`.\nElement `Composition.confidentiality` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThe exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section).  This element is labeled as a modifier because highly confidential documents must not be treated as if they are not."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.attester.mode|0.1.0",
      "element": [
        {
          "code": "Composition.attester.mode",
          "display": "mode",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Composition.attester.mode` is mapped to FHIR R5 element `Composition.attester.mode` as `SourceIsNarrowerThanTarget`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.relatesTo.code|0.1.0",
      "element": [
        {
          "code": "Composition.relatesTo.code",
          "display": "code",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Composition.relatesTo.code` is mapped to FHIR R5 element `Composition.relatesTo` as `RelatedTo`.\nThe mappings for `Composition.relatesTo.code` do not cover the following types: code.\nThe mappings for `Composition.relatesTo.code` do not cover the following types based on type expansion: value.\nIf this document appends another document, then the document cannot be fully understood without also accessing the referenced document."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.relatesTo.target|0.1.0",
      "element": [
        {
          "code": "Composition.relatesTo.target[x]",
          "display": "target[x]",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Composition.relatesTo.target[x]` has a context of Composition.relatesTo based on following the parent source element upwards and mapping to `Composition`.\nElement `Composition.relatesTo.target[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.event.code|0.1.0",
      "element": [
        {
          "code": "Composition.event.code",
          "display": "code",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Composition.event.code` has a context of Composition.event based on following the parent source element upwards and mapping to `Composition`.\nElement `Composition.event.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nAn event can further specialize the act inherent in the typeCode, such as where it is simply \"Procedure Report\" and the procedure was a \"colonoscopy\". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Composition|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Composition.section.mode|0.1.0",
      "element": [
        {
          "code": "Composition.section.mode",
          "display": "mode",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Composition.section.mode` has a context of Composition.section based on following the parent source element upwards and mapping to `Composition`.\nElement `Composition.section.mode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThis element is labeled as a modifier because a change list must not be misunderstood as a complete list."
            }
          ]
        }
      ]
    }
  ]
}