Extensions for Using Data Elements from FHIR R4 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R4-Composition-element-map-to-R4B"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4-Composition-element-map-to-R4B</b></p><a name="R4-Composition-element-map-to-R4B"> </a><a name="hcR4-Composition-element-map-to-R4B"> </a><p>Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/4.3</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Composition|4.0.1</code> to <a href="http://hl7.org/fhir/R4B/composition.html">Compositionversion: 4.3.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Composition.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.meta</td><td>Element `Composition.meta` is mapped to FHIR R4B element `Composition.meta` as `Equivalent`.</td></tr><tr><td>Composition.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.implicitRules</td><td>Element `Composition.implicitRules` is mapped to FHIR R4B element `Composition.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 it's narrative along with other profiles, value sets, etc.</td></tr><tr><td>Composition.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.language</td><td>Element `Composition.language` is mapped to FHIR R4B element `Composition.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).</td></tr><tr><td>Composition.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.text</td><td>Element `Composition.text` is mapped to FHIR R4B element `Composition.text` as `Equivalent`.
Contained 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.</td></tr><tr><td>Composition.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.contained</td><td>Element `Composition.contained` is mapped to FHIR R4B element `Composition.contained` as `Equivalent`.
This 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.</td></tr><tr><td>Composition.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.identifier</td><td>Element `Composition.identifier` is mapped to FHIR R4B element `Composition.identifier` as `Equivalent`.
Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.</td></tr><tr><td>Composition.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.status</td><td>Element `Composition.status` is mapped to FHIR R4B element `Composition.status` as `Equivalent`.
If 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.
Some 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.</td></tr><tr><td>Composition.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.type</td><td>Element `Composition.type` is mapped to FHIR R4B element `Composition.type` as `Equivalent`.
For 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.</td></tr><tr><td>Composition.category (category)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.category</td><td>Element `Composition.category` is mapped to FHIR R4B element `Composition.category` as `Equivalent`.
This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).</td></tr><tr><td>Composition.subject (subject)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.subject</td><td>Element `Composition.subject` is mapped to FHIR R4B element `Composition.subject` as `Equivalent`.
For clinical documents, this is usually the patient.</td></tr><tr><td>Composition.encounter (encounter)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.encounter</td><td>Element `Composition.encounter` is mapped to FHIR R4B element `Composition.encounter` as `Equivalent`.</td></tr><tr><td>Composition.date (date)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.date</td><td>Element `Composition.date` is mapped to FHIR R4B element `Composition.date` as `Equivalent`.
The Last Modified Date on the composition may be after the date of the document was attested without being changed.</td></tr><tr><td>Composition.author (author)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.author</td><td>Element `Composition.author` is mapped to FHIR R4B element `Composition.author` as `Equivalent`.</td></tr><tr><td>Composition.title (title)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.title</td><td>Element `Composition.title` is mapped to FHIR R4B element `Composition.title` as `Equivalent`.
For 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.</td></tr><tr><td>Composition.confidentiality (confidentiality)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.confidentiality</td><td>Element `Composition.confidentiality` is mapped to FHIR R4B element `Composition.confidentiality` as `Equivalent`.
The 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.</td></tr><tr><td>Composition.attester (attester)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Composition.attester</td><td>Element `Composition.attester` is mapped to FHIR R4B element `Composition.attester` as `Equivalent`.
Only list each attester once.</td></tr><tr><td>Composition.attester.mode (mode)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.attester.mode</td><td>Element `Composition.attester.mode` is mapped to FHIR R4B element `Composition.attester.mode` as `Equivalent`.</td></tr><tr><td>Composition.attester.time (time)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.attester.time</td><td>Element `Composition.attester.time` is mapped to FHIR R4B element `Composition.attester.time` as `Equivalent`.</td></tr><tr><td>Composition.attester.party (party)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.attester.party</td><td>Element `Composition.attester.party` is mapped to FHIR R4B element `Composition.attester.party` as `Equivalent`.</td></tr><tr><td>Composition.custodian (custodian)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.custodian</td><td>Element `Composition.custodian` is mapped to FHIR R4B element `Composition.custodian` as `Equivalent`.
This 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.</td></tr><tr><td>Composition.relatesTo (relatesTo)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Composition.relatesTo</td><td>Element `Composition.relatesTo` is mapped to FHIR R4B element `Composition.relatesTo` as `Equivalent`.
A document is a version specific composition.</td></tr><tr><td>Composition.relatesTo.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.relatesTo.code</td><td>Element `Composition.relatesTo.code` is mapped to FHIR R4B element `Composition.relatesTo.code` as `Equivalent`.
If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.</td></tr><tr><td>Composition.relatesTo.target[x] (target[x])</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.relatesTo.target[x]</td><td>Element `Composition.relatesTo.target[x]` is mapped to FHIR R4B element `Composition.relatesTo.target[x]` as `Equivalent`.
The target context `Composition.relatesTo.target[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Composition.relatesTo`.</td></tr><tr><td>Composition.event (event)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Composition.event</td><td>Element `Composition.event` is mapped to FHIR R4B element `Composition.event` as `Equivalent`.
The event needs to be consistent with the type element, though can provide further information if desired.</td></tr><tr><td>Composition.event.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.event.code</td><td>Element `Composition.event.code` is mapped to FHIR R4B element `Composition.event.code` as `Equivalent`.
An 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.</td></tr><tr><td>Composition.event.period (period)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.event.period</td><td>Element `Composition.event.period` is mapped to FHIR R4B element `Composition.event.period` as `Equivalent`.</td></tr><tr><td>Composition.event.detail (detail)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.event.detail</td><td>Element `Composition.event.detail` is mapped to FHIR R4B element `Composition.event.detail` as `Equivalent`.</td></tr><tr><td>Composition.section (section)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Composition.section</td><td>Element `Composition.section` is mapped to FHIR R4B element `Composition.section` as `Equivalent`.</td></tr><tr><td>Composition.section.title (title)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.title</td><td>Element `Composition.section.title` is mapped to FHIR R4B element `Composition.section.title` as `Equivalent`.
The 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.</td></tr><tr><td>Composition.section.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.code</td><td>Element `Composition.section.code` is mapped to FHIR R4B element `Composition.section.code` as `Equivalent`.
The 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.
If 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.</td></tr><tr><td>Composition.section.author (author)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.author</td><td>Element `Composition.section.author` is mapped to FHIR R4B element `Composition.section.author` as `Equivalent`.</td></tr><tr><td>Composition.section.focus (focus)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.focus</td><td>Element `Composition.section.focus` is mapped to FHIR R4B element `Composition.section.focus` as `Equivalent`.
Typically, 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.</td></tr><tr><td>Composition.section.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.text</td><td>Element `Composition.section.text` is mapped to FHIR R4B element `Composition.section.text` as `Equivalent`.
Document profiles may define what content should be represented in the narrative to ensure clinical safety.</td></tr><tr><td>Composition.section.mode (mode)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.mode</td><td>Element `Composition.section.mode` is mapped to FHIR R4B element `Composition.section.mode` as `Equivalent`.
This element is labeled as a modifier because a change list must not be misunderstood as a complete list.</td></tr><tr><td>Composition.section.orderedBy (orderedBy)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.orderedBy</td><td>Element `Composition.section.orderedBy` is mapped to FHIR R4B element `Composition.section.orderedBy` as `Equivalent`.
Applications 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.</td></tr><tr><td>Composition.section.entry (entry)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.entry</td><td>Element `Composition.section.entry` is mapped to FHIR R4B element `Composition.section.entry` as `Equivalent`.
If there are no entries in the list, an emptyReason SHOULD be provided.</td></tr><tr><td>Composition.section.emptyReason (emptyReason)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.emptyReason</td><td>Element `Composition.section.emptyReason` is mapped to FHIR R4B element `Composition.section.emptyReason` as `Equivalent`.
The 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.</td></tr><tr><td>Composition.section.section (section)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Composition.section.section</td><td>Element `Composition.section.section` is mapped to FHIR R4B element `Composition.section.section` as `Equivalent`.
Nested sections are primarily used to help human readers navigate to particular portions of the document.</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r4b"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r4b"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R4-Composition-element-map-to-R4B"/>
<version value="0.1.0"/>
<name value="R4CompositionElementMapToR4B"/>
<title
value="Cross-version mapping for FHIR R4 Composition to FHIR R4B Composition"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:40.8722321-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR R4 Composition to FHIR R4B."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/4.0"/>
<targetUri value="http://hl7.org/fhir/4.3"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Composition"/>
<sourceVersion value="4.0.1"/>
<target value="http://hl7.org/fhir/StructureDefinition/Composition"/>
<targetVersion value="4.3.0"/>
<element>
<code value="Composition.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.meta"/>
<display value="Composition.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.meta` is mapped to FHIR R4B element `Composition.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.implicitRules"/>
<display value="Composition.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.implicitRules` is mapped to FHIR R4B element `Composition.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 it's narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Composition.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.language"/>
<display value="Composition.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.language` is mapped to FHIR R4B element `Composition.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)."/>
</target>
</element>
<element>
<code value="Composition.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.text"/>
<display value="Composition.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.text` is mapped to FHIR R4B element `Composition.text` as `Equivalent`.
Contained 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."/>
</target>
</element>
<element>
<code value="Composition.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.contained"/>
<display value="Composition.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.contained` is mapped to FHIR R4B element `Composition.contained` as `Equivalent`.
This 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."/>
</target>
</element>
<element>
<code value="Composition.identifier"/>
<display value="identifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.identifier"/>
<display value="Composition.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.identifier` is mapped to FHIR R4B element `Composition.identifier` as `Equivalent`.
Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate."/>
</target>
</element>
<element>
<code value="Composition.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.status"/>
<display value="Composition.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.status` is mapped to FHIR R4B element `Composition.status` as `Equivalent`.
If 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.
Some 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."/>
</target>
</element>
<element>
<code value="Composition.type"/>
<display value="type"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.type"/>
<display value="Composition.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.type` is mapped to FHIR R4B element `Composition.type` as `Equivalent`.
For 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."/>
</target>
</element>
<element>
<code value="Composition.category"/>
<display value="category"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.category"/>
<display value="Composition.category"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.category` is mapped to FHIR R4B element `Composition.category` as `Equivalent`.
This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD))."/>
</target>
</element>
<element>
<code value="Composition.subject"/>
<display value="subject"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.subject"/>
<display value="Composition.subject"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.subject` is mapped to FHIR R4B element `Composition.subject` as `Equivalent`.
For clinical documents, this is usually the patient."/>
</target>
</element>
<element>
<code value="Composition.encounter"/>
<display value="encounter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.encounter"/>
<display value="Composition.encounter"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.encounter` is mapped to FHIR R4B element `Composition.encounter` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.date"/>
<display value="date"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.date"/>
<display value="Composition.date"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.date` is mapped to FHIR R4B element `Composition.date` as `Equivalent`.
The Last Modified Date on the composition may be after the date of the document was attested without being changed."/>
</target>
</element>
<element>
<code value="Composition.author"/>
<display value="author"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.author"/>
<display value="Composition.author"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.author` is mapped to FHIR R4B element `Composition.author` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.title"/>
<display value="title"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.title"/>
<display value="Composition.title"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.title` is mapped to FHIR R4B element `Composition.title` as `Equivalent`.
For 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."/>
</target>
</element>
<element>
<code value="Composition.confidentiality"/>
<display value="confidentiality"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.confidentiality"/>
<display value="Composition.confidentiality"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.confidentiality` is mapped to FHIR R4B element `Composition.confidentiality` as `Equivalent`.
The 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."/>
</target>
</element>
<element>
<code value="Composition.attester"/>
<display value="attester"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Composition.attester"/>
<display value="Composition.attester"/>
<equivalence value="wider"/>
<comment
value="Element `Composition.attester` is mapped to FHIR R4B element `Composition.attester` as `Equivalent`.
Only list each attester once."/>
</target>
</element>
<element>
<code value="Composition.attester.mode"/>
<display value="mode"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.attester.mode"/>
<display value="Composition.attester.mode"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.attester.mode` is mapped to FHIR R4B element `Composition.attester.mode` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.attester.time"/>
<display value="time"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.attester.time"/>
<display value="Composition.attester.time"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.attester.time` is mapped to FHIR R4B element `Composition.attester.time` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.attester.party"/>
<display value="party"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.attester.party"/>
<display value="Composition.attester.party"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.attester.party` is mapped to FHIR R4B element `Composition.attester.party` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.custodian"/>
<display value="custodian"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.custodian"/>
<display value="Composition.custodian"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.custodian` is mapped to FHIR R4B element `Composition.custodian` as `Equivalent`.
This 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."/>
</target>
</element>
<element>
<code value="Composition.relatesTo"/>
<display value="relatesTo"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Composition.relatesTo"/>
<display value="Composition.relatesTo"/>
<equivalence value="wider"/>
<comment
value="Element `Composition.relatesTo` is mapped to FHIR R4B element `Composition.relatesTo` as `Equivalent`.
A document is a version specific composition."/>
</target>
</element>
<element>
<code value="Composition.relatesTo.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.relatesTo.code"/>
<display value="Composition.relatesTo.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.relatesTo.code` is mapped to FHIR R4B element `Composition.relatesTo.code` as `Equivalent`.
If this document appends another document, then the document cannot be fully understood without also accessing the referenced document."/>
</target>
</element>
<element>
<code value="Composition.relatesTo.target[x]"/>
<display value="target[x]"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.relatesTo.target[x]"/>
<display value="Composition.relatesTo.target[x]"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.relatesTo.target[x]` is mapped to FHIR R4B element `Composition.relatesTo.target[x]` as `Equivalent`.
The target context `Composition.relatesTo.target[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Composition.relatesTo`."/>
</target>
</element>
<element>
<code value="Composition.event"/>
<display value="event"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Composition.event"/>
<display value="Composition.event"/>
<equivalence value="wider"/>
<comment
value="Element `Composition.event` is mapped to FHIR R4B element `Composition.event` as `Equivalent`.
The event needs to be consistent with the type element, though can provide further information if desired."/>
</target>
</element>
<element>
<code value="Composition.event.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.event.code"/>
<display value="Composition.event.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.event.code` is mapped to FHIR R4B element `Composition.event.code` as `Equivalent`.
An 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."/>
</target>
</element>
<element>
<code value="Composition.event.period"/>
<display value="period"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.event.period"/>
<display value="Composition.event.period"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.event.period` is mapped to FHIR R4B element `Composition.event.period` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.event.detail"/>
<display value="detail"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.event.detail"/>
<display value="Composition.event.detail"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.event.detail` is mapped to FHIR R4B element `Composition.event.detail` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.section"/>
<display value="section"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Composition.section"/>
<display value="Composition.section"/>
<equivalence value="wider"/>
<comment
value="Element `Composition.section` is mapped to FHIR R4B element `Composition.section` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.section.title"/>
<display value="title"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.title"/>
<display value="Composition.section.title"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.title` is mapped to FHIR R4B element `Composition.section.title` as `Equivalent`.
The 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."/>
</target>
</element>
<element>
<code value="Composition.section.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.code"/>
<display value="Composition.section.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.code` is mapped to FHIR R4B element `Composition.section.code` as `Equivalent`.
The 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.
If 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."/>
</target>
</element>
<element>
<code value="Composition.section.author"/>
<display value="author"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.author"/>
<display value="Composition.section.author"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.author` is mapped to FHIR R4B element `Composition.section.author` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Composition.section.focus"/>
<display value="focus"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.focus"/>
<display value="Composition.section.focus"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.focus` is mapped to FHIR R4B element `Composition.section.focus` as `Equivalent`.
Typically, 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."/>
</target>
</element>
<element>
<code value="Composition.section.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.text"/>
<display value="Composition.section.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.text` is mapped to FHIR R4B element `Composition.section.text` as `Equivalent`.
Document profiles may define what content should be represented in the narrative to ensure clinical safety."/>
</target>
</element>
<element>
<code value="Composition.section.mode"/>
<display value="mode"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.mode"/>
<display value="Composition.section.mode"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.mode` is mapped to FHIR R4B element `Composition.section.mode` as `Equivalent`.
This element is labeled as a modifier because a change list must not be misunderstood as a complete list."/>
</target>
</element>
<element>
<code value="Composition.section.orderedBy"/>
<display value="orderedBy"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.orderedBy"/>
<display value="Composition.section.orderedBy"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.orderedBy` is mapped to FHIR R4B element `Composition.section.orderedBy` as `Equivalent`.
Applications 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."/>
</target>
</element>
<element>
<code value="Composition.section.entry"/>
<display value="entry"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.entry"/>
<display value="Composition.section.entry"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.entry` is mapped to FHIR R4B element `Composition.section.entry` as `Equivalent`.
If there are no entries in the list, an emptyReason SHOULD be provided."/>
</target>
</element>
<element>
<code value="Composition.section.emptyReason"/>
<display value="emptyReason"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.emptyReason"/>
<display value="Composition.section.emptyReason"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.emptyReason` is mapped to FHIR R4B element `Composition.section.emptyReason` as `Equivalent`.
The 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."/>
</target>
</element>
<element>
<code value="Composition.section.section"/>
<display value="section"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Composition.section.section"/>
<display value="Composition.section.section"/>
<equivalence value="equivalent"/>
<comment
value="Element `Composition.section.section` is mapped to FHIR R4B element `Composition.section.section` as `Equivalent`.
Nested sections are primarily used to help human readers navigate to particular portions of the document."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change