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

Change Log

This page lists the changes made in each version of this guide.

Version 9.2.0

Trial-use release for MyHealth@EU Wave 9.

Potentially breaking changes

The changes below may make instances that conform to version 9.1.1 non-conformant, or may affect systems that receive the reports. They are grouped by where the change comes from.

Changes made in this guide
  • Animal patients are no longer supported. The PatientAnimal: Laboratory profile (patient-animal-myhealtheu-lab) and its example have been removed. ServiceRequestLabMyHealthEu.subject no longer allows an animal patient. This also follows HL7 Europe Laboratory Report 2.1.0 (see below).
  • MyHealth@EU datatypes for result values. In ObservationResultsLaboratoryMyHealthEu:
    • valueRange now uses the MyHealth@EU Core RangeMyHealth profile (was RangeEuLab);
    • component.value[x] now uses the same datatype profiles as the top-level value[x]: QuantityMyHealth, RangeMyHealth and RatioMyHealth. Component quantities must therefore use the MyHealth@EU coded units.
  • Observation order restricted. In ObservationResultsLaboratoryMyHealthEu, basedOn now references only ServiceRequestLabMyHealthEu, the laboratory test order (was CarePlan, DeviceRequest, ImmunizationRecommendation, MedicationRequest, NutritionOrder or ServiceRequest). This matches DiagnosticReport.basedOn.
Changes inherited from HL7 Europe Laboratory Report 2.1.0
  • Specimen body site reference moved. The extension that references a BodyStructure is no longer on Specimen.collection (Specimen.collection.extension:bodySite, http://hl7.org/fhir/StructureDefinition/bodySite). It is now on Specimen.collection.bodySite (Specimen.collection.bodySite.extension:bodySite, the R5 cross-version extension http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.bodySite). In SpecimenMyHealthEu, the reference must be a BodyStructureMyHealthCore.
  • Specimen container device required. When Specimen.container is present, its device extension (extension-Specimen.container.device) is now required (1..1, was 0..1).
  • Specimen type optional. Specimen.type is now 0..1 (was 1..1). Receiving systems must accept a specimen without a type.
  • Attachment section removed. CompositionLabReportMyHealthEu no longer defines the attachment section. Additional data associated with the report, such as images or diagrams, is conveyed through DiagnosticReport.media.
  • Media link required. In DiagnosticReportLabMyHealthEu, each media.link must now carry the link extension that references the DocumentReference (1..1, was 0..1).
  • Result required in every component. The invariant eu-lab-2 now requires every Observation.component to have a result, not just one of them, unless the observation status is registered or cancelled.
  • No animal patient as ServiceRequest subject. ServiceRequest.subject no longer allows an animal patient (Patient-animal-eu-lab).
  • Component value extension URL changed. The R5 cross-version extension on Observation.component is now http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.component.value (was …/extension-Observation.value). The same change is in MyHealth@EU Core 1.0.1.
Changes inherited from MyHealth@EU Core 1.0.1
  • DiagnosticReport reference in the Composition. In CompositionLabReportMyHealthEu, the diagnosticReport extension must now reference a DiagnosticReport that conforms to the MyHealth@EU Core DiagnosticReport profile (was any DiagnosticReport). A report that uses DiagnosticReportLabMyHealthEu, which is based on that profile, is not affected.
  • Component value extension URL changed in MedicalTestResultMyHealthCore, as in HL7 Europe Laboratory Report 2.1.0 (see above).

Dependencies

Package Previous Now
HL7 FHIR IPS (hl7.fhir.uv.ips) 2.0.0 2.0.1
HL7 Europe Laboratory Report (hl7.fhir.eu.laboratory) 2.0.0 2.1.0
HL7 Europe Base (hl7.fhir.eu.base) 2.0.0 2.0.1
HL7 Europe Extensions R4 (hl7.fhir.eu.extensions.r4) – 1.3.1 (new)
MyHealth@EU Core (myhealth.eu.fhir.core) 1.0.0 1.0.1
EHDS Logical Information Models (xtehr.eu.ehds.models) 0.3.0 1.0.0

The EHDS logical models package is based on HL7 FHIR R5; see Known Issues.

Logical models

The logical models are not meant to be implemented or exchanged, so these changes do not affect instances.

  • MyHealthEuLabReport:
    • the intended recipient is now header.intendedRecipient[x], as in the EHDS model;
    • header.legalAuthentication.legalAuthenticator[x] is now limited to MyHealthEuHealthProfessional, as in the MyHealth@EU Core document model;
    • body.orderInformation is no longer typed as MyHealthEuLabServiceRequest. It keeps the EHDS definition, with its own elements, which the previous type conflicted with.
  • All logical models now have a maturity level (FMM 2) and the trial-use status.

Other profile changes

  • ObservationResultsLaboratoryMyHealthEu: value[x] is no longer limited to Quantity, Range and Ratio; all the result types of the base resource are allowed (work item 5).
  • ObservationResultsLaboratoryMyHealthEu, aligned with HL7 Europe Laboratory Report 2.1.0:
    • the invariants eu-lab-1 and eu-lab-2 and the lowComparator and highComparator modifier extensions on referenceRange are now shown in the profile. They were already enforced through the imposed HL7 Europe profile;
    • focus can also reference a Substance or a BiologicallyDerivedProduct.
  • SpecimenMyHealthEu:
    • the collector can be a patient or a related person, through the collector extension on Specimen.collection.collector (inherited from HL7 Europe Laboratory Report 2.1.0). The patient must be a PatientMyHealthCore;
    • the targets of the focus extension are defined by the HL7 Europe Laboratory Report specimen focus extension; this guide does not restrict them further.
  • CompositionLabReportMyHealthEu:
    • the diagnosticReport extension no longer requires a literal reference. The DiagnosticReport is part of the document through its own reference to the Composition, as in HL7 Europe Laboratory Report 2.1.0;
    • the guidance on the identifier, type and subject shared with the DiagnosticReport now matches the HL7 Europe Laboratory Report invariants.
  • The animal specimen source profile is now titled RelatedPerson: Animal specimen source.
  • All profiles now have a maturity level (FMM 2) and the trial-use status. Some short descriptions and definitions have been corrected.

Examples

  • The Bundle example now follows a consistent timeline, and populates the mandatory and required elements: language, version and author of the Composition; order, specimen and issue time of the DiagnosticReport; order, specimen and performer of the Observation; identifier, subject and collection time of the Specimen; requester and order date of the ServiceRequest.
  • The standalone examples follow the same timeline as the Bundle, and populate the mandatory and required elements:
    • the DiagnosticReport has its order, specimen, issue time, performer and a PDF rendering of the report (presentedForm);
    • the Observations reference their order and specimen. The hemoglobin result and reference range now suit the male patient;
    • the Specimens have an identifier, and the ServiceRequests a requester, order date and reason.
  • New examples: SampleServiceRequestBloodGroup, SampleServiceRequestAlbuminUrine and SampleSpecimenUrine24h.
  • The device examples AnalyzerExample and DeviceSpecimenSubject are now standalone examples, so every profile has at least one linked example.
  • Example titles and descriptions follow a single pattern.
  • The Czech and Italian NamingSystems, which support the identifiers used in the examples, are now published as examples, not as conformance resources.

Pages

  • New Known Issues page (FHIR version of the EHDS logical models, pattern discriminators, quantity unit value set), and this Change Log page.
  • The obligation levels are described once, in the Introduction; the Laboratory Models Overview links to it.
  • The mapping page (Mapping to Profiles) has been updated for the new logical models:
    • each table now starts with its mapping context (source logical model and target FHIR profile);
    • several FHIR paths have been corrected, and order information is mapped only in the ServiceRequest table;
    • the supporting models mapped in MyHealth@EU Core are listed in one table that links to the Core model, profile and mapping.
  • The Introduction clarifies that consuming systems must display every element with an obligation that is present in the document.

Publication

  • The guide is now published under the CC0-1.0 licence.
  • The artifacts are organised in three groups: Logical Models, Document-related Profiles and Entry Profiles.