EU Health Data API
0.1.0 - ci-build 150

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

CapabilityStatement: EEHRxF Grouped Document Publisher/Access Provider CapabilityStatement

0.1.0
Official URL: http://hl7.eu/fhir/eu-health-data-api/CapabilityStatement/EEHRxF-DocumentPublisherAccessProvider Version:
Computable Name: EEHRxFDocumentPublisherAccessProvider

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

CapabilityStatement for the grouped EEHRxF Document Publisher and Document Access Provider actors. This represents a deployment where document production and access provision are co-located in the same system.

Deployment Pattern

This CapabilityStatement applies when:

  • An EHR system both produces documents AND provides access to them
  • Document publication is handled internally
  • External clients only need to query and retrieve documents

In this grouped deployment, document publication is internal to the system and not exposed externally. The external API provides only document discovery (ITI-67) and retrieval (ITI-68) capabilities.

Actor Grouping

This grouped actor combines:

  • Document Publisher (internal) - Produces and stores documents internally
  • Document Access Provider (external-facing) - Serves documents to Document Consumers

The underlying IHE actors are:

Note: MHD Document Recipient is not listed because publication is internal.

External 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.

When to Use This CapabilityStatement

Use this CapabilityStatement when implementing:

  • Hospital EHR systems that produce and serve their own documents
  • Regional health information exchanges with integrated document repositories
  • Any system where document creation and access are tightly coupled

For systems that need to receive documents from external sources, use the Document Access Provider with Document Submission Option.

Raw OpenAPI-Swagger Definition file | Download

Language: en

EEHRxF Grouped Document Publisher/Access Provider CapabilityStatement

  • Implementation Guide Version: 0.1.0
  • 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

This grouped actor provides document access to external Document Consumers. Document publication is internal and not exposed. The external API supports document discovery (ITI-67), retrieval (ITI-68), and patient lookup (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 access
  • Use TLS 1.2 or higher for all communications

Required scopes to accept:

  • system/DocumentReference.read, system/DocumentReference.search (read and search DocumentReference - ITI-67)
  • system/Binary.read (read Binary - ITI-68)
  • system/Bundle.read (read Bundle - ITI-68 for FHIR Documents)
  • system/Patient.read, system/Patient.search (read and 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 YYpatient, type, _id, category, date, status, identifier, period, formatProvenance:target
Binary Y
Patient 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 served via ITI-67 Find Document References. Document creation is internal; no external create operation is supported.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient the document is about. The server SHALL support at least id value and MAY support both Type and id values.

SHALLtypetoken

Kind of document (LOINC code) - SHALL support for clinical precision filtering

SHALL_idtoken

Logical id of this artifact

SHOULDcategorytoken

Categorization of document (XDS ClassCode) - SHOULD support for coarse filtering

SHOULDdatedate

When this document reference was created. The date modifiers ge, le, gt, lt SHOULD be supported.

SHOULDstatustoken

current | superseded | entered-in-error

SHOULDidentifiertoken

Master Version Specific Identifier

MAYperioddate

Time of service that is being documented

MAYformattoken

Format/content rules for the document

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

    Retrieve document content (ITI-68)

Documentation

Binary resources contain the actual document content and are served via ITI-68 Retrieve Document. Document content is created internally; no external create operation is supported.

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)

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