HL7 Europe Laboratory Report
2.2.0-ci - ci-build 150

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

EHDS Laboratory Report Mapping

EHDSLaboratoryReport -> Bundle, Composition, DiagnosticReport, ServiceRequest
Ongoing alignment: The mappings are based on the Xt-EHR models 1.0.0. The models may change with the EHDS implementing acts; this guide will follow such changes.

EHDSLaboratoryReport -> Bundle, Composition, DiagnosticReport, ServiceRequest

This page explains how conceptual elements from the EHDSLaboratoryReport logical model are expressed in the corresponding FHIR document profiles used by this Implementation Guide.

Mapping Context
EHDSLaboratoryReport -> Bundle, Composition, DiagnosticReport, ServiceRequest
EHDSLaboratoryReport (Logical Model) Relationship Bundle/Composition/DiagnosticReport/ServiceRequest (EU Lab)
Element Description Relation Resource Element Description Notes
header Laboratory report header. related-to Composition . Document-level metadata container.
header.subject Subject of care for the report. equivalent Composition subject Who/what the document is about. Also aligned with DiagnosticReport.subject.
header.identifier Business identifier of the report. equivalent Composition identifier Identifier for the composition instance.
header.identifier Business identifier of the report. equivalent DiagnosticReport identifier Identifier(s) for the diagnostic report.
header.identifier Business identifier of the report. equivalent Bundle identifier Identifier of the document bundle.
header.author[x] Author(s) of the report. equivalent Composition author Who and/or what authored the report.
header.date Date/time when the report document is authored. equivalent Composition date Composition authoring time.
header.status Workflow/clinical status of the report. equivalent DiagnosticReport status Status of the diagnostic report. Composition and DiagnosticReport status are expected to be aligned.
header.language Language of the report content. equivalent Composition language Language of the narrative/document.
header.documentType Type of document. equivalent Composition type Coded type of the document.
header.documentType Type of document. equivalent DiagnosticReport code Coded report type.
header.documentTitle Human-readable document title. equivalent Composition title Document title.
header.period Time period covered by the report content. related-to Composition event.period Period covered by the documented event.
header.version Business version of the report document. related-to Composition extension:version Business-level document version.
header.attestation Attestation information. related-to Composition attester Attestation container.
header.attestation.attester[x] Attester validating the report content. equivalent Composition attester.party Attesting actor.
header.attestation.datetime Date and time of attestation. equivalent Composition attester.time When the report was attested.
header.legalAuthentication Legal authentication information. related-to Composition attester Legal authenticator details.
header.legalAuthentication.legalAuthenticator[x] Legal authenticator of the report. related-to Composition attester.party Party taking legal responsibility. May require attester mode constraints by implementation rules.
header.legalAuthentication.datetime Date and time of legal authentication. equivalent Composition attester.time When legal authentication was recorded.
header.eventType Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). related-to Composition category:studyType Grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study). The model gives laboratory study types as an example. This guide carries them in the studyType slice, which DiagnosticReport.category has as well.
header.serviceSpecialty Clinical/laboratory specialty context. related-to Composition category:specialty Clinical domain of the laboratory (e.g. microbiology, toxicology, chemistry). The slice is bound to LabSpecialtyEuVs. DiagnosticReport.category has the same slice.
header.custodian Organization responsible for maintaining the report. equivalent Composition custodian Custodian organization.
presentedForm Rendered document payload of the report. equivalent DiagnosticReport presentedForm Entire report as issued (e.g. PDF).
header.intendedRecipient[x] Intended recipients of the report. equivalent Composition extension:informationRecipient Recipients of the document. Uses EU extension on Composition.
body Laboratory report structured body. related-to Composition section Structured narrative/data sections of the report.
body.orderInformation Order/request context of the report. related-to ServiceRequest . Requested service represented as ServiceRequestLabEu. Each order is a ServiceRequestLabEu, which DiagnosticReport.basedOn references. The child elements map to elements of that ServiceRequest.
body.orderInformation.orderId Identifier(s) of the order. equivalent ServiceRequest identifier Business identifier of the request.
body.orderInformation.orderDateAndTime Date/time of order placement. equivalent ServiceRequest authoredOn When the request was authored.
body.orderInformation.orderPlacer[x] Placer/requester of the order. equivalent ServiceRequest requester Who initiated the request.
body.orderInformation.orderReason[x] Clinical reason/justification for the request. equivalent ServiceRequest reasonCode / reasonReference Why the service is requested. Mapping depends on coded, textual, or referenced reason source.
body.orderInformation.clinicalQuestion Clinical question to be answered. related-to ServiceRequest note Additional textual context for the request.
body.supportingInformation Additional context that supports ordering/interpretation. related-to ServiceRequest supportingInfo Container for supporting clinical context.
body.supportingInformation.observation Clinical findings and other observations. equivalent ServiceRequest supportingInfo Reference to an Observation.
body.supportingInformation.condition Condition that may influence the service or result interpretation. equivalent ServiceRequest supportingInfo Reference to a Condition.
body.supportingInformation.medicationAdministration Medication administered before ordering the service. equivalent ServiceRequest supportingInfo Reference to a MedicationAdministration.
body.supportingInformation.sexForClinicalUse Sex parameter for clinical use. related-to Patient extension:sex-for-clinical-use Sex parameter for clinical use. PatientEuCore of HL7 Europe Base profiles this extension.
body.supportingInformation.vaccination Vaccination history of the patient. equivalent ServiceRequest supportingInfo Reference to an Immunization.
body.supportingInformation.otherSupportingInformation Any other relevant supporting information. equivalent ServiceRequest supportingInfo Reference to any other resource.
body.specimen Specimen information used by the report. equivalent DiagnosticReport specimen Specimen references used in the report. Also represented as Bundle entries of type SpecimenEu.
body.serviceRequest Service request(s) answered by the report. equivalent DiagnosticReport basedOn Request fulfilled by this report.
body.resultData Container for report result content. related-to DiagnosticReport result / conclusion / presentedForm Result-bearing part of the report.
body.resultData.laboratoryTestResults Structured laboratory observations in the report. equivalent DiagnosticReport result Result observation references. Observation resources are included as Bundle entries.
body.resultData.laboratoryTestResults Structured laboratory observations in the report. equivalent Composition section.entry Narrative sections link to observation entries.
body.resultData.commentsInterpretationAndRecommendations Narrative comments, interpretation, and recommendations. related-to Composition section:text Human-readable report commentary. Often represented in annotation/comment section.
body.resultData.commentsInterpretationAndRecommendations Narrative comments, interpretation, and recommendations. related-to DiagnosticReport conclusion / conclusionCode Diagnostic interpretation summary. When implemented in the DiagnosticReport profile instance.
attachments Report attachments. related-to DiagnosticReport media.link.extension:link DocumentReference containing additional information or attachments associated with the report. Each attachment is a DocumentReference, referenced through the alternate-reference extension on media.link. The rendered report itself maps from presentedForm.

Return to overview: EHDS Logical Models -> FHIR Profiles