Example: Document Access Provider Supporting EPS and Laboratory

EU Health Data API
1.0.0-ballot - ballot 150

This page is part of the EU Health Data API (v1.0.0-ballot: STU1 Ballot 1) 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

CapabilityStatement: Example: Document Access Provider Supporting EPS and Laboratory (Experimental)

Official URL: http://hl7.eu/fhir/health-data-api/CapabilityStatement/EEHRxF-DocumentAccessProvider-Example	Version: 1.0.0-ballot	Highlight text changes?
		Computable Name: ExampleDocumentAccessProviderEPSLab
Copyright/Legal: Copyright HL7 Europe. Licensed under Creative Commons public domain (CC0 1.0).

Raw OpenAPI-Swagger Definition file | Download

Language: en

Example: Document Access Provider Supporting EPS and Laboratory

Implementation Guide Version: 1.0.0-ballot
FHIR Version: 4.0.1
Supported Formats: json, xml
Published on: 2026-03-10
Published by: HL7 Europe

Note to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement instantiates the CapabilityStatement EEHRxF Document Access Provider CapabilityStatement

SHALL Support the Following Implementation Guides

http://hl7.eu/fhir/eps
http://hl7.eu/fhir/laboratory

FHIR RESTful Capabilities

Mode: `server`

This server provides document exchange for European Patient Summaries and Laboratory Reports. It supports MHD ITI-67 (Find Document References), ITI-68 (Retrieve Document), and PDQm ITI-78 (Patient Demographics Query).

Security

Enable CORS: no

Security services supported: SMART-on-FHIR

SMART Backend Services authorization required.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

The relevant profiles (if any)
The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
The required, recommended, and some optional search parameters (if any).
The linked resources enabled for _include
The other resources enabled for _revinclude
The operations on the resource (if any)

Resource Type	Profile	R	S	U	C	Searches	`_include`	`_revinclude`	Operations
DocumentReference	Supported Profiles EEHRxF MHD DocumentReference Profile MHD DocumentReference Minimal	y	y			patient, type, status, date, _id
Patient	Supported Profiles Patient (EU core)	y	y			identifier, _id