MyHealth@EU Laboratory Report
9.2.0 - trial-use 150

MyHealth@EU Laboratory Report - Local Development build (v9.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Mapping to Profiles

Mappings from MyHealth@EU / EHDS models to FHIR profiles

MyHealth@EU logical models refine the EHDS logical information models provided by the Xt-EHR project. These models add obligation levels (Mandatory, Required, Optional) to the EHDS base elements.
Please read more about the models on the Laboratory Models Overview page.

The mappings below show how the logical model elements explicitly defined in the MyHealth@EU models are realised in the FHIR R4 profiles of this guide.

Laboratory Report

Mapping Context

Logical model element FHIR Path (R4) Comment
header.subject Composition.subject; DiagnosticReport.subject Reference to PatientMyHealthCore.
header.identifier Composition.identifier; DiagnosticReport.identifier; Bundle.identifier  
header.documentType Composition.type; DiagnosticReport.code  
header.documentTitle Composition.title  
header.status DiagnosticReport.status Composition and DiagnosticReport status are expected to be aligned.
header.date Composition.date  
header.language Composition.language  
header.version Composition.extension:version  
header.custodian Composition.custodian Reference to OrganizationMyHealthCore.
header.eventType Composition.category:studyType  
header.author[x] Composition.author Reference to PractitionerMyHealthCore, PractitionerRoleMyHealthCore, OrganizationMyHealthCore or Device.
header.attestation.attester[x] Composition.attester:validator.party  
header.attestation.datetime Composition.attester:validator.time  
header.legalAuthentication.legalAuthenticator[x] Composition.attester:legalAuthenticator.party Attester mode fixed to legal.
header.legalAuthentication.datetime Composition.attester:legalAuthenticator.time  
header.intendedRecipient[x] Composition.extension:informationRecipient  
body.orderInformation DiagnosticReport.basedOn Reference to ServiceRequestLabMyHealthEu, one per order. The order details are mapped in the Service Request table.
body.supportingInformation.sexForClinicalUse Patient.extension:sex-for-clinical-use Profiled in PatientMyHealthCore.
body.specimen DiagnosticReport.specimen Reference to SpecimenMyHealthEu.
body.resultData.commentsInterpretationAndRecommendations Composition.section:annotations.text; DiagnosticReport.conclusion; DiagnosticReport.conclusionCode  
body.resultData.laboratoryTestResults DiagnosticReport.result; Composition.section.entry Reference to ObservationResultsLaboratoryMyHealthEu.
presentedForm DiagnosticReport.presentedForm  
attachments DiagnosticReport.media.link.extension:link Reference to a DocumentReference, through the alternate-reference extension.

Laboratory Observation

Mapping Context

Logical model element FHIR Path (R4) Comment
type Observation.code  
originalName Observation.code.text  
method Observation.method  
order Observation.basedOn Reference to ServiceRequestLabMyHealthEu.
specimen Observation.specimen Reference to SpecimenMyHealthEu.
performer[x] Observation.performer Reference to PractitionerMyHealthCore, PractitionerRoleMyHealthCore or OrganizationMyHealthCore.
observationDate[x] Observation.effective[x]  
result.value[x] Observation.value[x]  
interpretation Observation.interpretation  
referenceRange Observation.referenceRange The bounds are inclusive unless modifierExtension:lowComparator or modifierExtension:highComparator states otherwise.
component.result.value[x] Observation.component.value[x]  
component.referenceRange Observation.component.referenceRange  
component.interpretation Observation.component.interpretation  
note Observation.note  
accreditationStatus Observation.extension:accredited Laboratory Accredited extension (boolean), from HL7 Europe Extensions.
testKit Observation.extension:labTestKit Laboratory Test Kit extension (reference to a Device), from HL7 Europe Laboratory Report.
calibrator Observation.extension:certifiedRefMaterialCodeable; Observation.extension:certifiedRefMaterialIdentifer  

Service Request

Mapping Context

Logical model element FHIR Path (R4) Comment
header.identifier ServiceRequest.identifier  
header.date ServiceRequest.authoredOn  
header.author[x] ServiceRequest.requester Reference to PractitionerMyHealthCore, PractitionerRoleMyHealthCore, OrganizationMyHealthCore, PatientMyHealthCore, RelatedPerson or Device.
reason[x] ServiceRequest.reasonCode; ServiceRequest.reasonReference  

Specimen

Mapping Context

Logical model element FHIR Path (R4) Comment
identifier Specimen.identifier  
type Specimen.type  
specimenSource[x] Specimen.subject Reference to PatientMyHealthCore or DeviceSpecimenMyHealthEu.
collection.collected[x] Specimen.collection.collected[x]  
collection.method Specimen.collection.method  
collection.device Not mapped R4 Specimen has no such element. Specimen.collection.device exists only in R5.
collection.bodySite Specimen.collection.bodySite; Specimen.collection.bodySite.extension:bodySite Coded body site; the R5 cross-version extension references BodyStructureMyHealthCore.
receivedDate Specimen.receivedTime  

Supporting models mapped in MyHealth@EU Core IG

Several referenced models are implemented through the MyHealth@EU Core IG. The entries below link to existing mapping pages for those profiles.

MyHealth@EU Logical Model FHIR Profile Mapping Details
MyHealthEuPatient PatientMyHealthCore MyHealthEuPatient Mapping
MyHealthEuHumanName HumanName MyHealthEuHumanName Mapping
MyHealthEuAddress AddressMyHealthCore MyHealthEuAddress Mapping
MyHealthEuTelecom ContactPoint MyHealthEuTelecom Mapping
MyHealthEuHealthProfessional PractitionerRoleMyHealthCore, PractitionerMyHealthCore MyHealthEuHealthProfessional Mapping
MyHealthEuOrganisation OrganizationMyHealthCore MyHealthEuOrganisation Mapping
MyHealthEuDevice DeviceMeasuringMyHealthEu, DeviceSpecimenMyHealthEu MyHealthEuDevice Mapping
MyHealthEuBodyStructure BodyStructureMyHealthCore MyHealthEuBodyStructure Mapping