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

EHDSObservation to FHIR Observation Mapping

EHDSObservation → MedicalTestResultEuCore
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.

EHDSObservation → MedicalTestResultEuCore

This page explains how conceptual elements from the EHDS Observation logical model for medical test results are expressed in the corresponding FHIR Observation profile used by this Implementation Guide.

Mapping Context

EHDSObservation → MedicalTestResultEuCore
EHDSObservation (Logical Model) Relationship MedicalTestResultEuCore
Element Relation Resource Element Notes
header related-to Observation . Dataset-level; not usually carried in Observation as-is.
header.subject equivalent Observation subject Reference to Patient (or other allowed subject types).
header.identifier equivalent Observation identifier Copy over all identifiers if multiple.
header.author[x] related-to Observation performer Observation lacks a dedicated author participant. Usually, the performer is also the author; however in case the two participants shall be clearly distinguished, the PerformerFunction extension can be used for this purpose.
header.date equivalent Observation issued
header.status equivalent Observation status
header.source no-map Observation - No direct native Flag element; consider extension if needed.
header.language equivalent Observation language
header.directSubject[x] equivalent Observation focus
observationDate[x] equivalent Observation effective[x] Map to effectiveDateTime or effectivePeriod.
type equivalent Observation code
originalName equivalent Observation code.text
method equivalent Observation method
specimen equivalent Observation specimen
order equivalent Observation basedOn
performer[x] equivalent Observation performer
bodySite source-is-broader-than-target Observation bodySite
bodySite source-is-broader-than-target
equivalent		 Observation extension[bodyStructure]〔R4〕
bodyStructure〔R5〕
result related-to Observation .
result.value[x] equivalent Observation value[x] When the result is a Diagram or Picture (Microbiology), then the Attachment data type should be used. In FHIR R4 this can be done by preadopting the R5 Observation.value[x] element using the cross-version extension.
result.uncertainty related-to Quantity extension See included elements for mapping details
result.uncertainty.value equivalent Quantity extension:uncertainty http://hl7.org/fhir/StructureDefinition/iso21090-uncertainty extension for the Quantity data type.
result.uncertainty.type equivalent Observation extension:uncertaintyType http://hl7.org/fhir/StructureDefinition/iso21090-uncertaintyType extension for the Quantity data type.
result.dataAbsentReason equivalent Observation dataAbsentReason
referenceRange equivalent Observation referenceRange
interpretation equivalent Observation interpretation
note source-is-broader-than-target Observation note
component equivalent Observation component
component.code equivalent Observation component.code
component.originalName equivalent Observation component.code.text
component.result related-to Observation component
component.result.value[x] equivalent Observation component.value[x] When the result is a Diagram or Picture (Microbiology), then the Attachment data type should be used. In FHIR R4 this can be done by preadopting the R5 Observation.value[x] element using the cross-version extension.
component.result.uncertainty related-to Quantity extension See included elements for mapping details
component.result.uncertainty.value equivalent Quantity extension:uncertainty http://hl7.org/fhir/StructureDefinition/iso21090-uncertainty extension for the Quantity data type.
component.result.uncertainty.type equivalent Observation extension:uncertaintyType http://hl7.org/fhir/StructureDefinition/iso21090-uncertaintyType extension for the Quantity data type.
component.result.dataAbsentReason equivalent Observation component.dataAbsentReason
component.referenceRange equivalent Observation component.referenceRange
component.interpretation equivalent Observation component.interpretation
derivedFrom[x] equivalent Observation derivedFrom Supports references to Observation, ImagingStudy, DiagnosticReport, etc.
hasMember[x] equivalent Observation hasMember

Return to overview: EHDS Logical Models → FHIR Profiles