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 Composition Mapping

EHDSDocument ↔ CompositionEuCore
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 ↔ CompositionEuCore

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

Mapping Context

EHDSDocument ↔ CompositionEuCore
EHDSDocument (Logical Model) Relationship CompositionEuCore
Element Relation Resource Element Notes
header related-to Composition . Dataset-level information across the Composition instance.
header.subject equivalent Composition subject
header.identifier equivalent Composition identifier Multiple identifiers allowed; Composition 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] equivalent Composition author
header.date equivalent Composition date
header.status equivalent Composition status
header.source no-map Composition No native element.
header.language equivalent Composition language
header.documentType equivalent Composition type
header.documentTitle equivalent Composition title
header.period related-to Composition event.period Map to the primary Composition.event entry.
header.version related-to Composition extension:version〔R4〕
version〔R5〕
header.attestation related-to Composition attester Use mode to distinguish assertions.
header.attestation.attester[x] equivalent Composition attester.party
header.attestation.datetime equivalent Composition attester.time Set attester.mode as appropriate (e.g., professional).
header.legalAuthentication related-to Composition attester Use attester.mode = "legal" for the legal authenticator.
header.legalAuthentication.legalAuthenticator[x] related-to Composition attester.party Use attester.mode = "legal" for the legal authenticator.
header.legalAuthentication.datetime equivalent Composition attester.time Use attester.mode = "legal" for the legal authenticator.
header.eventType related-to Composition event.code 〔R4〕
event.detail.concept〔R5〕		 Clarify the scope. If it is a classification of the document it should be category
header.serviceSpecialty source-is-narrower-than-target Composition category Use category to tag specialty if no dedicated extension/profile element exists. (1) Is this a metadata information or something that have to be captured in the document ? (2) is this only for diagnostic reports ? in this case we can use DiagnosticReport.category
header.custodian equivalent Composition custodian Reference to Organization.
presentedForm no-map Composition To be determined

Return to overview: EHDS Logical Models ↔ FHIR Profiles