<?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 ↔ DiagnosticReportEuCore</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 ↔ DiagnosticReportEuCore</h3>
    <a> </a>
    <p></p>
    <p>
  This page explains how conceptual elements from the EHDS logical model are expressed
  in the corresponding FHIR DiagnosticReportEuCore 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-diagnosticReport-eu-core.html">
        DiagnosticReportEuCore
          </a>
        </li>
      </ul>
    </div>
    <p></p>
    <div class="table-wrap">
      <table summary="EHDSDocument ↔ DiagnosticReportEuCore">
        <caption>EHDSDocument ↔ DiagnosticReportEuCore</caption>
        <thead>
          <tr>
            <th colspan="1" class="src-head">EHDSDocument (Logical Model)</th>
            <th class="relhead">Relationship</th>
            <th colspan="3" class="tgt-head">DiagnosticReportEuCore</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 class="">
            <td>header</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>.</td>
            <td>Dataset-level information across the DiagnosticReport instance. <strong>Category (classCode) is missing ?</strong></td>
          </tr>
          <tr>
            <td>header.subject</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>subject</td>
            <td></td>
          </tr>
          <tr>
            <td>header.identifier</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>identifier</td>
            <td>Multiple identifiers allowed; DiagnosticReport 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>related-to</td>
            <td>DiagnosticReport</td>
            <td>performer</td>
            <td>The author of the report is captured in the Composition.author element; but usually the performer is also the author of the report, even if they are distict participants</td>
          </tr>
          <tr>
            <td>header.date</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>issued</td>
            <td></td>
          </tr>
          <tr>
            <td>header.status</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>status</td>
            <td></td>
          </tr>
          <tr>
            <td>header.language</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>language</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentType</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>code</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentTitle</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
          </tr>
          <tr>
            <td>header.period</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>effectivePeriod</td>
            <td></td>
          </tr>
          <tr>
            <td>header.version</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
          </tr>
          <tr>
            <td>header.attestation</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td>No native element in DiagnosticReport. Details about attestation are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.attestation.attester[x]</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td>No native element in DiagnosticReport. Details about attester are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.attestation.datetime</td>
            <td>no-map</td>
            <td>DiagnosticReport</td><td></td>
            <td>No native element in DiagnosticReport. Details about attestation date time are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.legalAuthentication</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td>No native element in DiagnosticReport. Details about legal authentication are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.legalAuthentication.legalAuthenticator[x]</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td>No native element in DiagnosticReport. Details about legal authenticator are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.legalAuthentication.datetime</td>
            <td>no-map</td>
            <td>DiagnosticReport</td><td></td>
            <td>No native element in DiagnosticReport. Details about legal authentication date time are documented in the Compostion resource.</td>
          </tr>
          <tr>
            <td>header.eventType</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>category</td>
            <td>The mapping proposed reflects a possible interpretation of this element as classification of the report; DocumentReference.category should be used if used for filtering document searches. If instead it represents the type of event that occurred, Composition.event.code for <span style="color:#2e7d32;font-weight:600;">〔R4〕</span> and Composition.event.detail.concept for<span style="color:#2e7d32;font-weight:600;">〔R5〕</span>is more appropriate.</td>
          </tr>
          <tr>
            <td>header.serviceSpecialty</td>
            <td>source-is-narrower-than-target</td>
            <td>DiagnosticReport</td>
            <td>category</td>
            <td></td>
          </tr>
          <tr>
            <td>header.custodian</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
          </tr>
<!-- DOCUMENT BODY -->
          <tr>
            <td>presentedForm</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>presentedForm</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>
