<?xml version="1.0" encoding="utf-8"?>
<div xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
    <title>EHDSDocument ↔ CompositionEuCore</title>
  </head>
  <body>
    <div class="model-map-block">
      <div class="callout-wrapper">
        <div class="callout-box">
          <strong>Ongoing alignment:</strong>
The models are expected to continue evolving, with updates incorporated into this Implementation Guide to maintain alignment with the EHDS Implementing Acts.
        </div>
      </div>
    </div>
    <h3>EHDSDocument ↔ CompositionEuCore</h3>
    <a> </a>
    <p></p>
    <p>
  This page explains how conceptual elements from the EHDS logical model are expressed
  in the corresponding FHIR CompositionEuCore profile used by this Implementation Guide.
    </p>
    <p></p>
    <div class="table-wrap">
      <strong>Mapping Context</strong>
      <ul>
        <li>
          <strong>Source logical model:</strong>
          <a href="https://www.xt-ehr.eu/fhir/models/0.3.0/StructureDefinition-EHDSDocument.html" target="_blank">
        EHDSDocument
          </a>
        </li>
        <li>
          <strong>Target FHIR profile:</strong>
          <a href="StructureDefinition-composition-eu-core.html">
        CompositionEuCore
          </a>
        </li>
      </ul>
    </div>
    <p></p>
    <div class="table-wrap">
      <table summary="EHDSDocument ↔ CompositionEuCore">
        <caption>EHDSDocument ↔ CompositionEuCore</caption>
        <thead>
          <tr>
            <th colspan="1" class="src-head">EHDSDocument (Logical Model)</th>
            <th class="relhead">Relationship</th>
            <th colspan="3" class="tgt-head">CompositionEuCore</th>
          </tr>
          <tr>
            <th class="src-sub">Element</th>
            <th class="relsub">Relation</th>
            <th class="tgt-sub">Resource</th>
            <th class="tgt-sub">Element</th>
            <th class="tgt-sub">Notes</th>
          </tr>
        </thead>
        <tbody>
          <!-- HEADER BLOCK -->
          <tr>
            <td>header</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>.</td>
            <td>Dataset-level information across the Composition instance.</td>
          </tr>
          <tr>
            <td>header.subject</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>subject</td>
            <td></td>
          </tr>
          <tr>
            <td>header.identifier</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>identifier</td>
            <td>Multiple identifiers allowed; Composition R4 allows 0..1, R5 0..*. <code>setId</code> in HL7 CDA</td>
          </tr>
          <tr>
            <td>header.identifier</td>
            <td>equivalent</td>
            <td>Bundle</td>
            <td>identifier</td>
            <td>Identifier of a specific version of this document. <code>id</code> in HL7 CDA</td>
          </tr>
          <tr>
            <td>header.author[x]</td>            
            <td>equivalent</td>
            <td>Composition</td>
            <td>author</td>            
            <td></td>
          </tr>
          <tr>
            <td>header.date</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>date</td>
            <td></td>
          </tr>
          <tr>
            <td>header.status</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>status</td>
            <td></td>
          </tr>
          <tr>
            <td>header.language</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>language</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentType</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>type</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentTitle</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>title</td>
            <td></td>
          </tr>
          <tr>
            <td>header.period</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>event.period</td>
            <td>Map to the primary Composition.event entry.</td>
          </tr>
          <tr>
            <td>header.version</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>extension:version<span style="color:#2e7d32;font-weight:600;">〔R4〕</span><br></br>version<span style="color:#2e7d32;font-weight:600;">〔R5〕</span></td>
            <td></td>
          </tr>
          <tr>
            <td>header.attestation</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>attester</td>
            <td>Use mode to distinguish assertions.</td>
          </tr>
          <tr>
            <td>header.attestation.attester[x]</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>attester.party</td>
            <td></td>
          </tr>
          <tr>
            <td>header.attestation.datetime</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>attester.time</td>
            <td>Set attester.mode as appropriate (e.g., professional).</td>
          </tr>
          <tr>
            <td>header.legalAuthentication</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>attester</td>
            <td>Use attester.mode = "legal" for the legal authenticator.</td>
          </tr>
          <tr>
            <td>header.legalAuthentication.legalAuthenticator[x]</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>attester.party</td>
            <td>Use attester.mode = "legal" for the legal authenticator.</td>
          </tr>
          <tr>
            <td>header.legalAuthentication.datetime</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>attester.time</td>
            <td>Use attester.mode = "legal" for the legal authenticator.</td>
          </tr>
          <tr>
            <td>header.eventType</td>
            <td>related-to</td>
            <td>Composition</td>
            <td>category</td>
            <td>The mapping proposed reflects a possible interpretation of this element as classification of the document; DocumentReference.category should be used if used for filtering document searches. If instead it represents the type of event that occurred, event.code for <span style="color:#2e7d32;font-weight:600;">〔R4〕</span> and event.detail.concept for<span style="color:#2e7d32;font-weight:600;">〔R5〕</span></td>
          </tr>
          <tr>
            <td>header.serviceSpecialty</td>
            <td>source-is-narrower-than-target</td>
            <td>Composition</td>
            <td>category</td>
            <td>The mapping proposed reflects a possible classification of the document based on the service specialty. However it is more appropriated to be captured in the DiagnosticReport.category, or in the DocumentReference.category if used for filtering document searches.</td>
          </tr>
          <tr>
            <td>header.custodian</td>
            <td>equivalent</td>
            <td>Composition</td>
            <td>custodian</td>
            <td>Reference to Organization.</td>
          </tr>
<!-- DOCUMENT BODY -->
          <tr>
            <td>presentedForm</td>
            <td>no-map</td>
            <td>Composition</td>
            <td></td>            
            <td></td>
          </tr>
        </tbody>
      </table>
    </div>
    <p style="margin-top:2rem;color:#555;">
      Return to overview: <a href="modelmap.html">EHDS Logical Models ↔ FHIR Profiles</a>
    </p>
  </body>
</div>
