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/bvdh/jwg-api/ and changes regularly. See the Directory of published versions

CapabilityStatement: EEHRxF Resource Consumer CapabilityStatement

Official URL: http://hl7.eu/fhir/euridice-api/CapabilityStatement/EEHRxF-ResourceConsumer Version: 0.1.0
Computable Name: EEHRxFResourceConsumer

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

CapabilityStatement for the EEHRxF Resource Consumer actor. This actor queries for clinical data resources following the International Patient Access (IPA) patterns and IHE QEDm Clinical Data Consumer capabilities.

This CapabilityStatement defines the requirements for systems consuming direct resource access (beyond document-based exchange) in the EU EHR Exchange Format (EEHRxF) ecosystem. It inherits patterns from:

  • IPA (International Patient Access): Resource profiles and search parameter patterns
  • IHE QEDm (Query for Existing Data for Mobile): Clinical Data Consumer actor capabilities

Supported Resources

  • Patient: Lookup only (search by identifier, read by ID)
  • Practitioner: Read access for clinical context
  • Organization: Read access for organizational context
  • Condition: Problems and diagnoses
  • AllergyIntolerance: Allergy and intolerance records
  • Observation: Clinical observations (vital signs, lab results, etc.)
  • DiagnosticReport: Laboratory and imaging reports
  • MedicationRequest: Medication orders and prescriptions
  • MedicationDispense: Medication dispensing records
  • Encounter: Patient encounters

Security

Systems SHALL support SMART Backend Services authorization for all transactions.

Profile Inheritance

Consumers SHOULD expect resources conforming to EU Core profiles where available.

Raw OpenAPI-Swagger Definition file | Download

Language: en

EEHRxF Resource Consumer CapabilityStatement

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Published on: 2026-01-08
  • 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: client

The Resource Consumer actor queries for clinical data resources from a Resource Access Provider following IPA and QEDm patterns. This enables direct resource access complementing document-based exchange via MHD.

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:

  • Authenticate using JWT client credentials (RFC 7523)
  • Request appropriate scopes for resource access
  • Use TLS 1.2 or higher for all communications

Required scopes to request:

  • system/Patient.rs (search and read Patient)
  • system/Condition.rs (search and read Condition)
  • system/AllergyIntolerance.rs (search and read AllergyIntolerance)
  • system/Observation.rs (search and read Observation)
  • system/DiagnosticReport.rs (search and read DiagnosticReport)
  • system/MedicationRequest.rs (search and read MedicationRequest)
  • system/MedicationDispense.rs (search and read MedicationDispense)
  • system/Encounter.rs (search and read Encounter)
  • system/Practitioner.r (read Practitioner)
  • system/Organization.r (read Organization)

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
Patient YY_id, identifier, family, given, birthdate
Practitioner Y
Organization Y
Condition YYpatient, clinical-status, category, code
AllergyIntolerance YYpatient, clinical-status
Observation YYpatient, category, code, date, status
DiagnosticReport YYpatient, category, code, date, status
MedicationRequest YYpatient, status, intent, authoredon
MedicationDispense YYpatient, status, whenhandedover
Encounter YYpatient, date, status, class

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

    Read Patient by logical ID

    search-type

    Search for patients for lookup purposes

Documentation

Patient resources are queried for patient lookup per PDQm [ITI-78] with identifier as a required search parameter. Note: Patient is used for lookup context, not as a primary clinical data resource in this actor.

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

Patient logical ID

SHALLidentifiertoken

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

SHOULDfamilystring

Patient family name

SHOULDgivenstring

Patient given name

SHOULDbirthdatedate

Patient date of birth

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

    Read Practitioner by logical ID

Documentation

Practitioner resources are read to resolve clinical context for referenced healthcare providers.

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

    Read Organization by logical ID

Documentation

Organization resources are read to resolve context for referenced healthcare organizations.

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

    Read Condition by logical ID

    search-type

    Search for Condition resources

Documentation

Condition resources represent problems, diagnoses, and health concerns. Clients SHALL support search by patient and SHOULD support additional filters.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient who has the condition (SHALL support)

SHOULDclinical-statustoken

The clinical status of the condition

SHOULDcategorytoken

The category of condition

SHOULDcodetoken

Code for the condition

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

    Read AllergyIntolerance by logical ID

    search-type

    Search for AllergyIntolerance resources

Documentation

AllergyIntolerance resources represent patient allergies and intolerances. Clients SHALL support search by patient.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient who has the allergy or intolerance (SHALL support)

SHOULDclinical-statustoken

The clinical status of the allergy or intolerance

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

    Read Observation by logical ID

    search-type

    Search for Observation resources

Documentation

Observation resources represent clinical observations including vital signs, laboratory results, and other measurements. Clients SHALL support search by patient and category.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient the observation is about (SHALL support)

SHALLcategorytoken

Category of observation (e.g., vital-signs, laboratory)

SHOULDcodetoken

The code of the observation type

SHOULDdatedate

Obtained date/time. Date modifiers ge, le, gt, lt SHOULD be supported.

SHOULDstatustoken

The status of the observation

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

    Read DiagnosticReport by logical ID

    search-type

    Search for DiagnosticReport resources

Documentation

DiagnosticReport resources represent laboratory results and imaging reports. Clients SHALL support search by patient and category.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient the report is about (SHALL support)

SHALLcategorytoken

Category of report (e.g., LAB, RAD)

SHOULDcodetoken

The code for the report type

SHOULDdatedate

The clinically relevant time of the report

SHOULDstatustoken

The status of the report

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

    Read MedicationRequest by logical ID

    search-type

    Search for MedicationRequest resources

Documentation

MedicationRequest resources represent medication orders and prescriptions. Clients SHALL support search by patient.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient for whom the medication was ordered (SHALL support)

SHOULDstatustoken

Status of the prescription

SHOULDintenttoken

The intent of the medication request

SHOULDauthoredondate

Return prescriptions written on this date

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

    Read MedicationDispense by logical ID

    search-type

    Search for MedicationDispense resources

Documentation

MedicationDispense resources represent medication dispensing events. Clients SHALL support search by patient.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient for whom the medication was dispensed (SHALL support)

SHOULDstatustoken

Status of the dispense

SHOULDwhenhandedoverdate

When the medication was handed over

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

    Read Encounter by logical ID

    search-type

    Search for Encounter resources

Documentation

Encounter resources represent patient encounters (visits, admissions, etc.). Clients SHALL support search by patient.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The patient present at the encounter (SHALL support)

SHOULDdatedate

A date within the encounter period

SHOULDstatustoken

Status of the encounter

SHOULDclasstoken

Classification of the encounter (e.g., inpatient, outpatient)