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 models are expected to continue evolving, with updates incorporated into this Implementation Guide to maintain alignment with the EHDS Implementing Acts.

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 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
header.date equivalent DiagnosticReport issued
header.status equivalent DiagnosticReport status
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 No native element in DiagnosticReport. Details about attestation are documented in the Compostion resource.
header.attestation.attester[x] no-map DiagnosticReport No native element in DiagnosticReport. Details about attester are documented in the Compostion resource.
header.attestation.datetime no-map DiagnosticReport No native element in DiagnosticReport. Details about attestation date time are documented in the Compostion resource.
header.legalAuthentication no-map DiagnosticReport No native element in DiagnosticReport. Details about legal authentication are documented in the Compostion resource.
header.legalAuthentication.legalAuthenticator[x] no-map DiagnosticReport No native element in DiagnosticReport. Details about legal authenticator are documented in the Compostion resource.
header.legalAuthentication.datetime no-map DiagnosticReport No native element in DiagnosticReport. Details about legal authentication date time are documented in the Compostion resource.
header.eventType related-to DiagnosticReport category 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 〔R4〕 and Composition.event.detail.concept for〔R5〕is more appropriate.
header.serviceSpecialty source-is-narrower-than-target DiagnosticReport category
header.custodian no-map DiagnosticReport
presentedForm related-to DiagnosticReport presentedForm

Return to overview: EHDS Logical Models ↔ FHIR Profiles