EU Health Data API, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/euridice-org/eu-health-data-api/ and changes regularly. See the Directory of published versions

FHIR Documents and Resources

This Implementation Guide supports two primary patterns for exchanging health data: FHIR Documents and individual FHIR Resources.

FHIR Documents

FHIR Documents are complete, immutable snapshots of clinical information at a point in time. They are represented as FHIR Bundles with type="document" and contain a Composition resource that provides structure and rendering information. The Composition acts as a table of contents and enables the document to be displayed as a cohesive clinical report.

Documents are self-contained and can be signed and attested by healthcare providers, making them suitable for traditional clinical reports like patient summaries, discharge reports, and lab reports.

FHIR Resources

Individual FHIR Resources represent discrete pieces of health information (observations, conditions, medications, etc.) that can be queried and accessed independently. Resources provide granular, queryable access to health data and support real-time clinical decision support workflows.

Relationship

Resources can be extracted from documents, and documents can be generated from resources. This IG supports both patterns to accommodate different implementation architectures and use cases.

Open Issue #10: We are seeking input on when to use document exchange vs resource access. See FHIR Documents vs Resources Guidance for discussion.