HL7 Europe Base and Core FHIR IG
2.0.0-recon - ci-build 150

HL7 Europe Base and Core FHIR IG, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 2.0.0-recon built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/base/ and changes regularly. See the Directory of published versions

EHDSDocument to FHIR DiagnosticReport Mapping

EHDSDocument ↔ DiagnosticReportEuCore
Ongoing alignment: 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.
Yellow row/cells: 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.

EHDSDocument ↔ DiagnosticReportEuCore

This page explains how conceptual elements from the EHDS logical model are expressed in the corresponding FHIR DiagnosticReportEuCore profile used by this Implementation Guide.

Mapping Context

EHDSDocument ↔ DiagnosticReportEuCore
EHDSDocument (Logical Model) Relationship DiagnosticReportEuCore
Element Relation Resource Element Notes
header related-to DiagnosticReport . Dataset-level information across the DiagnosticReport instance. Category (classCode) is missing ?
header.subject equivalent DiagnosticReport subject
header.identifier equivalent DiagnosticReport identifier Multiple identifiers allowed; DiagnosticReport R4 allows 0..1, R5 0..*. setId in HL7 CDA
header.identifier equivalent Bundle identifier Identifier of a specific version of this document. id in HL7 CDA
header.author[x] related-to DiagnosticReport performer
header.date equivalent DiagnosticReport issued
header.status equivalent DiagnosticReport status
header.source no-map DiagnosticReport No native element
header.language equivalent DiagnosticReport language
header.documentType equivalent DiagnosticReport code
header.documentTitle no-map DiagnosticReport
header.period related-to DiagnosticReport effectivePeriod
header.version no-map DiagnosticReport
header.attestation no-map DiagnosticReport
header.attestation.attester[x] no-map DiagnosticReport No native element in DiagnosticReport.
header.attestation.datetime no-map DiagnosticReport No native element in DiagnosticReport.
header.legalAuthentication no-map DiagnosticReport
header.legalAuthentication.legalAuthenticator[x] no-map DiagnosticReport No native element in DiagnosticReport.
header.legalAuthentication.datetime no-map DiagnosticReport No native element in DiagnosticReport.
header.eventType related-to DiagnosticReport category Clarify the scope. If it is a classification of the report it should be category
header.serviceSpecialty source-is-narrower-than-target DiagnosticReport category Use category to tag specialty if no dedicated extension/profile element exists. Is this a metadata information or something that have to be captured in the document ? in this case we can use DiagnosticReport.category
header.custodian no-map DiagnosticReport
presentedForm equivalent DiagnosticReport presentedForm

Return to overview: EHDS Logical Models ↔ FHIR Profiles