EU Health Data API
1.0.0-ballot - ballot 150

EU Health Data API, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot 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

CapabilityStatement: EEHRxF Document Access Provider CapabilityStatement

Official URL: http://hl7.eu/fhir/health-data-api/CapabilityStatement/document-access-provider-eu-api Version: 1.0.0-ballot
Active as of 2026-01-26 Computable Name: DocumentAccessProviderEuApi

Copyright/Legal: Copyright HL7 Europe. Licensed under Creative Commons public domain (CC0 1.0).

CapabilityStatement for the EEHRxF Document Access Provider actor. This composite actor provides access to EEHRxF FHIR Documents by serving them to Document Consumers via query APIs.

Actor Grouping

This composite actor groups the following IHE actors:

Transactions

Transaction Description Optionality
ITI-67 Find Document References Respond to document metadata queries from Document Consumers R
ITI-68 Retrieve Document Serve document content to Document Consumers R
ITI-78 Patient Demographics Query Respond to patient demographics queries R
Get Access Token Issue authorization tokens to clients R

Security

Systems SHALL support SMART Backend Services authorization for all transactions.

Document Submission Option

To accept document publication from external Document Publishers, implement the Document Submission Option.

Deployment

The Document Access Provider may be grouped with Document Publisher, in which case document publication is internal. See the grouped Document Publisher/Access Provider CapabilityStatement for this deployment pattern.

Raw OpenAPI-Swagger Definition file | Download

Language: en

EEHRxF Document Access Provider CapabilityStatement

  • Implementation Guide Version: 1.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Published on: 2026-01-26
  • 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.

FHIR RESTful Capabilities

Mode: server

The Document Access Provider actor responds to document queries from Document Consumers (ITI-67, ITI-68) and provides patient lookup services (PDQm ITI-78).

All transactions require SMART Backend Services authorization.

Security
Enable CORS: no
Security services supported: SMART-on-FHIR

SMART Backend Services authorization is REQUIRED for all transactions. Systems SHALL:

  • Validate JWT client credentials (RFC 7523)
  • Verify appropriate scopes for document operations
  • Use TLS 1.2 or higher for all communications

Required scopes to accept:

  • system/DocumentReference.rs (read + search DocumentReference - ITI-67)
  • system/Binary.r (read Binary - ITI-68)
  • system/Bundle.r (read Bundle - ITI-68 for FHIR Documents)
  • system/Patient.rs (read + search Patient - ITI-78)
Summary of System-wide Interactions
  • MAY support the search-systeminteraction described as follows:

    System-wide search support

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 TypeProfileRSUCSearches_include_revincludeOperations
DocumentReference YY_id, _lastUpdated, author.given, author.family, category, creation, date, event, facility, format, identifier, patient, patient.identifier, period, related, security-label, setting, status, typeProvenance:target
Binary Y
PatientSupported Profiles
  Patient (EU core)
YYidentifier, _id, family, given, birthdate

Core FHIR Resource
DocumentReference
Reference Policy
resolves
Interaction summary
  • SHALL support
    read

    Read DocumentReference by logical ID

    search-type

    Search for DocumentReference resources (ITI-67)

Documentation

DocumentReference resources are returned as base FHIR resources. No EU or MHD return profile is required.

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

Logical id

SHALLcategorytoken

Document category

SHALLcreationdate

Document creation time

SHALLpatientreference

Patient reference

SHALLpatient.identifiertoken

Chained patient identifier

SHALLtypetoken

Document type

SHOULDdatedate

Reference creation time

SHOULDstatustoken

Document reference status

MAY_lastUpdateddate

Resource version last updated

MAYauthor.givenstring

Author given name

MAYauthor.familystring

Author family name

MAYeventtoken

Main clinical acts documented

MAYfacilitytoken

Facility kind

MAYformattoken

Document format

MAYidentifiertoken

Document identifier

MAYperioddate

Documented service period

MAYrelatedreference

Related identifier or resource

MAYsecurity-labeltoken

Document security label

MAYsettingtoken

Clinical setting

 
Core FHIR Resource
Binary
Reference Policy
Interaction summary
  • SHALL support
    read

    Retrieve document content (ITI-68)

Documentation

Binary resources contain non-FHIR document content (e.g. DICOM KOS imaging manifests per IHE MADO). Served via ITI-68 Retrieve Document.

Core FHIR Resource
Patient
Reference Policy
resolves
Interaction summary
  • SHALL support
    read

    Read Patient by logical ID

    search-type

    Search for patients (PDQm ITI-78)

Supported Profiles

Patient (EU core)

Documentation

Patient resources support patient context lookup per PDQm [ITI-78]. The identifier search parameter is required; additional demographics parameters are optional.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken

Patient identifier (e.g., national ID, MRN) - required for patient lookup

SHALL_idtoken

Patient logical ID

SHOULDfamilystring

Patient family name

SHOULDgivenstring

Patient given name

SHOULDbirthdatedate

Patient date of birth