<?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 ↔ DiagnosticReport</title>
  </head>
  <body>
    <div class="model-map-block">
      <div class="callout-wrapper">
        <div class="callout-box">
          <strong>Ongoing alignment:</strong>
              The Xt-EHR logical models are under active revision and continuous refinement.
              Updates from Xt-EHR will be progressively incorporated into this Implementation
              Guide to maintain alignment with the evolving EHDS specifications.
        </div>
      </div>
    </div>
    <div class="model-map-block">
      <div class="callout-wrapper">
        <div class="callout-box">
          <strong>Yellow row/cells:</strong>
              In this ballot publication, some row/cells of the mapping table have been left in yellow to indicate areas requiring further review or refinement; including feedback from the Xt-EHR joint action (see note above). These highlights will be addressed in subsequent updates to ensure accuracy and completeness of the mappings.
        </div>
      </div>
    </div>
    <h3>EHDSDocument ↔ DiagnosticReport</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 ↔ DiagnosticReport">
        <caption>EHDSDocument ↔ DiagnosticReport</caption>
        <thead>
          <tr>
            <th colspan="2" class="src-head">EHDSDocument (Logical Model)</th>
            <th class="relhead">Relationship</th>
            <th colspan="4" class="tgt-head">DiagnosticReport</th>
          </tr>
          <tr>
            <th class="src-sub">Element</th>
            <th class="src-sub">Description</th>
            <th class="relsub">Relation</th>
            <th class="tgt-sub">Resource</th>
            <th class="tgt-sub">Element</th>
            <th class="tgt-sub">Description</th>
            <th class="tgt-sub">Notes</th>
          </tr>
        </thead>
        <tbody>
          <!-- HEADER BLOCK -->
          <tr class="">
            <td>header</td>
            <td>Document header elements.</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>.</td>
            <td>General metadata.</td>
            <td>Dataset-level information across the DiagnosticReport instance. <strong>Category (classCode) is missing ?</strong></td>
          </tr>
          <tr>
            <td>header.subject</td>
            <td>Patient/subject information.</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>subject</td>
            <td>Who or what the report is about.</td>
            <td>Reference to Patient.</td>
          </tr>
          <tr>
            <td>header.identifier</td>
            <td>Unique identifier of the document.</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>identifier</td>
            <td>Version-independent identifier for the DiagnosticReport</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>Unique identifier of the document.</td>
            <td>equivalent</td>
            <td>Bundle</td>
            <td>identifier</td>
            <td>Persistent identifier for the bundle</td>
            <td>Identifier of a specifc version of this document. <code>id</code> in HL7 CDA</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.author[x]</td>
            <td>Author(s) who authored the resource.</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>performer</td>
            <td>The diagnostic service that is responsible for issuing the report.</td>
            <td></td>
          </tr>
          <tr>
            <td>header.date</td>
            <td>Date and time of authoring/issuing.</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>issued</td>
            <td>DateTime this version was made</td>
            <td></td>
          </tr>
          <tr>
            <td>header.status</td>
            <td>Status of the resource or document.</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>status</td>
            <td>The workflow/clinical status of this report</td>
            <td></td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.source</td>
            <td>Source of the information (e.g. patient, proxy).</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td>No native element</td>
          </tr>
          <tr>
            <td>header.language</td>
            <td>Language of the resource (IETF BCP-47).</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>language</td>
            <td>Language of the narrative.</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentType</td>
            <td>Type of document (e.g., LOINC 60591-5).</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>code</td>
            <td>Kind of report (LOINC preferred).</td>
            <td></td>
          </tr>
          <tr>
            <td>header.documentTitle</td>
            <td>Human readable document title.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td></td>
          </tr>
          <tr>
            <td>header.period</td>
            <td>Time of service being documented.</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>effectivePeriod</td>
            <td>Clinically relevant time/time-period for report</td>
            <td></td>
          </tr>
          <tr>
            <td>header.version</td>
            <td>Business version of the document.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td></td>
          </tr>
          <tr>
            <td>header.attestation</td>
            <td>Document attestation details.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td></td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.attestation.attester[x]</td>
            <td>Attester who validated the document.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td>No native element in DiagnosticReport.</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.attestation.datetime</td>
            <td>Date/time of approval by attester.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td><td></td><td></td>
            <td>No native element in DiagnosticReport.</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.legalAuthentication</td>
            <td>Document legal authentication details.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td></td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.legalAuthentication.legalAuthenticator[x]</td>
            <td>Person responsible for legal authentication.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td>No native element in DiagnosticReport.</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.legalAuthentication.datetime</td>
            <td>Date/time when the document was legally authenticated.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td><td></td><td></td>
            <td>No native element in DiagnosticReport.</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.eventType</td>
            <td>Categorisation of the event covered by the document.</td>
            <td>related-to</td>
            <td>DiagnosticReport</td>
            <td>category</td>
            <td>Service category</td>
            <td>Clarify the scope. If it is a classification of the report it should be category</td>
          </tr>
          <tr class="highlight-yellow">
            <td>header.serviceSpecialty</td>
            <td>Details about where the content was created (clinical specialty).</td>
            <td>source-is-narrower-than-target</td>
            <td>DiagnosticReport</td>
            <td>category</td>
            <td>Categorizes the report.</td>
            <td>Use category to tag specialty if no dedicated extension/profile element exists. <strong>Is this a metadata information or something that have to be captured in the document ? in this case we can use DiagnosticReport.category</strong> </td>
          </tr>
          <tr>
            <td>header.custodian</td>
            <td>Organisation maintaining the document/report.</td>
            <td>no-map</td>
            <td>DiagnosticReport</td>
            <td></td>
            <td></td>
            <td></td>
          </tr>
<!-- DOCUMENT BODY -->
          <tr>
            <td>presentedForm</td>
            <td>Narrative easy-to-read representation (e.g., PDF).</td>
            <td>equivalent</td>
            <td>DiagnosticReport</td>
            <td>presentedForm</td>
            <td>Entire report as issued</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>
