HL7 Belgium FHIR Implementation Guide: Patient Dossier
1.1.1 - STU1
This page is part of the HL7 BE patient dossier IG (v1.1.1: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: https://www.ehealth.fgov.be/standards/fhir/patient-dossier/ImplementationGuide/hl7.fhir.be.patient-dossier | Version: 1.1.1 | ||||
| Active as of 2026-10-30 | Computable Name: PatientDossier | ||||
| Other Identifiers: OID:2.16.840.1.113883.4.642.40.200.14 | |||||
This implementation guide defines the Belgian FHIR profiles for Patient Dossier CareSets — standardized sets of clinical data that are specific to an individual patient and commonly used across care settings, without being transversal in nature.
A CareSet is a structured collection of clinical information designed for secure, standardized exchange between healthcare actors via the national eHealth infrastructure (Hubs & Vaults). Each CareSet defines a logical model, value sets, and business rules that ensure data can be shared, stored, and consulted in a traceable and reusable manner within integrated patient care.
The Patient Dossier CareSets cover clinical domains that are patient-centric — they capture data recorded in the context of a specific patient’s care journey. This distinguishes them from transversal resources (e.g. terminology, practitioner registries) that are shared across patients and contexts.
This guide covers the following Patient Dossier resources:
| Resource | Description | Status |
|---|---|---|
| BeDocument (Logical Model) | Generic logical model for a FHIR document that structures and contains CareSets | Active |
| BeDocument (Bundle Profile) | Minimal document Bundle profile constraining the FHIR Bundle to a document containing a Composition and CareSet entries | Active |
| BeClinicalReport (Logical Model) | Logical model of the CareSet ClinicalReport, consolidating the clinical observations of one medical context over a defined period | Draft |
| BeClinicalReport (DiagnosticReport Profile) | DiagnosticReport profile carrying the CareSet ClinicalReport, with its interpretation, conclusions and referenced observations | Draft |
The BeDocument provides the generic envelope and structure for clinical documents. It does not contain clinical data itself but references and organises other CareSets into a meaningful, shareable, and traceable document. Examples include discharge summaries, referral letters, surgical reports, and consultation reports.
The BeClinicalReport carries the clinical content itself: the consolidated report of one patient’s follow-up over a defined observation period. See its usage, boundaries and relationships for how it relates to BeDocument and to the ClinicalObservation CareSet.
This implementation guide contains the following types of resources:
This guide builds on:
| IG | Package | FHIR | Comment |
|---|---|---|---|
| hl7.fhir.be.patient-dossier#1.1.1 | R4 | ||
| hl7.terminology.r4#7.5.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology | |
| hl7.fhir.uv.extensions.r4#5.4.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack | |
| hl7.fhir.be.core#2.2.0 | R4 | ||
| hl7.fhir.uv.tools.r4#1.3.0 | R4 | for example references |
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.be.patient-dossier.r4) and R4B (hl7.fhir.be.patient-dossier.r4b) are available.
No use of external IP