HL7 Laboratory Report
0.1.0-ci - ci-build International flag

HL7 Laboratory Report, published by Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 0.1.0-ci built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/uv-lab-rep-ig/ and changes regularly. See the Directory of published versions


Official URL: http://hl7.org/fhir/uv/lab-report/ImplementationGuide/hl7.fhir.uv.lab-report Version: 0.1.0-ci
Draft as of 2024-07-16 Computable Name: Hl7LaboratoryReportIg

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

This guide uses the HL7 Europe Laboratory Report FHIR IG as initial content.

This working version may still include pages, profiles, and other artefacts or references copied from the European Guide.

These artefacts and references will be progressivelsy cleaned up.

Obligations have been added to this version of the guide only as Informative material to collect feedback about their usage.

For more details about obligations please refer to the Obligations page

The Laboratory Domain

Clinical laboratory results play an important role in diagnosis, treatment, and follow-up of patients. The availability of high quality test results, and the capacity of sharing them, is therefore essential being often the basis for clinical decision making. For this reason the Laboratory has been selected as one of the priority domains for the European EHR eXchange Format (E-EHRxF).


Specify a set of rules to be applied to HL7 FHIR to define how to represent a Laboratory Report in the European Context, coherently with the European eHN Guidelines (see the European eHealth - Key documents ).

This Implementation Guide applies to laboratory reports within the core fields of in-vitro diagnostics, for example clinical biochemistry, haematology, immunohematology, microbiology, immunology, while leaving out some specialised laboratory domains like histopathology or medical genetics. This version focuses only on common rules that apply to all the in-scope situations, without specifying specialized domain-specific profiles, as for example microbiology profiles.

This guide is not limited to test results performed by clinical laboratories on Human specimens (from human subject), but it considers also results on non-human materials or living subjects; or non-human specimens paired with a human subject. Derived guides may restrict the scope as needed (e.g. limiting the scope to well-identified human beings)


The goal of this Implementation Guide is to define an European standard for the Laboratory Report to facilitate the harmonization among the national initiatives and prepare the ground for the European EHR eXchange Format (E-EHRxF).

This project is promoted by HL7 Europe, but realized in collaboration with several other European and national organizations and projects.

The aspiration of this guide is that of being used as basis for European National Guides, the European EHRxF and - consequently - by MyHealth@EU for the EU cross-border services.


The project background is described in the background page.

Design choices

The solution adopted by this guide - and detailed in the Design choices page - balances the business requirement of Laboratory Report as legally signable document (i.e. as a FHIR document), with the expectation to get Lab Report by searching per DiagnosticReport. All this, taking into account the R5 DiagnosticReport design pattern where the DiagnosticReport <-> Composition relationship is directed from the DiagnosticReport to the Composition resource. This is done by supporting both perspectives (see figure below) requiring the document bundle ( BundleLabReportUv ) to always include a DiagnosticReport ( DiagnosticReportLabUv ) and enabling the pre-adoption of the R5 rules for the inclusion of entries in the Document Bundle.

Laboratory report design approach

Figure 1 - Overview of the report design approach

The following diagrams provide a browseable overview of the profiles specified by this guide (not all the relationships have been reported).

The first highlights the most relevant relationships starting from the DiagnosticReport ( DiagnosticReportLabUv ) resource (REST Perspective).

The second the profiles included in the document bundle ( BundleLabReportUv ) (Document Perspective).


Package hl7.fhir.uv.extensions.r4#5.1.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.uv.ips#1.1.0

International Patient Summary (IPS) FHIR Implementation Guide (built Tue, Nov 22, 2022 03:24+0000+00:00)

Package hl7.fhir.uv.extensions.r4#1.0.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package hl7.fhir.eu.extensions#0.1.0

This guide lists the extensions speciifed for the European REALM. (built Tue, Feb 20, 2024 08:56+0100+01:00)

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.uv.lab-report.r4) and R4B (hl7.fhir.uv.lab-report.r4b) are available.

Global Profiles

There are no Global profiles defined

IP statements

This publication includes IP covered under the following statements.

Authors and Contributors

Please refer to the Authors and Contributors page.