<?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>EHDSLocation → LocationEuCore</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>EHDSLocation → LocationEuCore</h3><a>  </a>
    <p></p>
    <p>
  This page explains how conceptual elements from the EHDS logical model are expressed
  in the corresponding FHIR LocationEuCore 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/EHDSLocation" target="_blank">
        EHDSLocation
          </a>
        </li>
        <li>
          <strong>Target FHIR profile:</strong>
          <a href="StructureDefinition-location-eu-core.html">
        LocationEuCore
          </a>
        </li>
      </ul>
    </div>
    <p></p>
    <p>
      LocationEuCore represents physical service delivery sites and care locations.
    </p>
    <div class="table-wrap">
      <table summary="EHDSLocation → LocationEuCore">
        <caption>EHDSLocation → LocationEuCore</caption>
        <thead>
          <tr>
            <th colspan="2" class="src-head">EHDSLocation (Logical Model)</th>
            <th class="relhead">Relationship</th>
            <th colspan="4" class="tgt-head">LocationEuCore</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>
          <tr>
            <td>identifier</td>
            <td>Identifier for the location.</td>
            <td>equivalent</td>
            <td>Location</td><td>identifier</td>
            <td>Unique code or number identifying the location.</td>
            <td></td>
          </tr>
          <tr>
            <td>name</td>
            <td>Human-readable name of the location.</td>
            <td>equivalent</td>
            <td>Location</td><td>name</td>
            <td>Location name.</td>
            <td></td>
          </tr>
          <tr>
            <td>description</td>
            <td>Textual description of the location and its purpose.</td>
            <td>equivalent</td>
            <td>Location</td><td>description</td>
            <td>Description of the location.</td>
            <td></td>
          </tr>
          <tr>
            <td>type</td>
            <td>Type/category of the location (e.g. ward, lab, pharmacy counter).</td>
            <td>equivalent</td>
            <td>Location</td><td>physicalType<span style="color:#2e7d32;font-weight:600;">〔R4〕</span></td>
            <td>Type of location.</td>
            <td>In R4, physicalType is common; R5 shifts emphasis to type.</td>
          </tr>
          <tr>
            <td>type</td>
            <td>Type/category of the location (e.g. ward, lab, pharmacy counter).</td>
            <td>equivalent</td>
            <td>Location</td><td>type<span style="color:#2e7d32;font-weight:600;">〔R5〕</span>
            </td>
            <td>Type of location.</td>
            <td>In R4, physicalType is common; R5 shifts emphasis to type.</td>
          </tr>
          <tr>
            <td>address</td>
            <td>Physical postal address of the location.</td>
            <td>equivalent</td>
            <td>Location</td><td>address</td>
            <td>Address of the location.</td>
            <td>Uses Address/AddressEu.</td>
          </tr>
          <tr>
            <td>managingOrganisation</td>
            <td>Organisation responsible for the services provided at this location.</td>
            <td>equivalent</td>
            <td>Location</td><td>managingOrganization</td>
            <td>Managing organization.</td>
            <td>Reference to OrganizationEuCore.</td>
          </tr>
          <tr>
            <td>partOf</td>
            <td>Parent/host location of which this one is a physical part.</td>
            <td>equivalent</td>
            <td>Location</td><td>partOf</td>
            <td>Another Location that contains this one.</td>
            <td>Supports hierarchical location trees.</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>
