Generated Narrative: CapabilityStatement EeehrxfImagingReportResourceAccessProvider Language: en EEHRxF Imaging Report Resource Access Provider CapabilityStatement Implementation Guide Version: 1.0.0-ballot FHIR Version: 4.0.1 Supported Formats: json, xml Published on: 2026-02-02 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 Imaging Report Resource Access Provider actor responds to queries for clinical data resources 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: Validate JWT client credentials (RFC 7523) Verify appropriate scopes for resource access Use TLS 1.2 or higher for all communications Return HTTP 401, 403, or 404 for unauthorized requests Resource Flexibility Following IPA's approach, servers MAY choose which clinical resources to support based on their capabilities and use cases. Patient is required for lookup context; other resources are recommended but servers may implement a subset. The server's CapabilityStatement declares which resources are actually supported. Scopes for Supported Resources Servers SHALL accept scopes for the resources they support: system/AdverseEvent.read, system/AdverseEvent.search system/Patient.read, system/Patient.search system/Condition.read, system/Condition.search (if Condition supported) system/AllergyIntolerance.read, system/AllergyIntolerance.search (if AllergyIntolerance supported) system/Observation.read, system/Observation.search system/Composition.read, system/Observation.search system/DiagnosticReport.read, system/DiagnosticReport.search system/MedicationRequest.read, system/MedicationRequest.search system/MedicationDispense.read, system/MedicationDispense.search system/Encounter.read, system/Encounter.search (if Encounter supported) system/Practitioner.read (if Practitioner supported) system/Organization.read (if Organization supported) system/Procedure.read system/Provenance.read 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 Patient Y Y _id, identifier, family, given, birthdate Practitioner Y Organization Y Condition Y Y patient, clinical-status, category, code AllergyIntolerance Y Y patient, clinical-status Observation Y Y patient, category, code, date, status DiagnosticReport Y Y patient, category, code, date, status MedicationRequest Y Y patient, status, intent, authoredon MedicationDispense Y Y patient, status, whenhandedover Encounter Y Y patient, date, status, class ImagingStudy Y Y based-on, body-site, dicom-class, modality, identifier, instance, patient, performer, reason, referrer, series, started, subject, status Device Y Composition Y Procedure Y patient, subject ServiceRequest Y identifier, patient, subject AdverseEvent Y Provenance Y patient, subject, target ImagingSelection Y Resource Conformance: SHALL Patient 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 support 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 Conformance Parameter Type Documentation SHALL _id token Patient logical ID SHALL identifier token Patient identifier (e.g., national ID, MRN) - required for patient lookup SHOULD family string Patient family name SHOULD given string Patient given name SHOULD birthdate date Patient date of birth Resource Conformance: SHOULD Practitioner Core FHIR Resource Practitioner Reference Policy Interaction summary SHALL support read Read Practitioner by logical ID Documentation Practitioner resources provide clinical context for referenced healthcare providers. Read-only access supports resolving practitioner references in clinical resources. Servers SHOULD support this resource but MAY omit it based on their capabilities. Resource Conformance: SHOULD Organization Core FHIR Resource Organization Reference Policy Interaction summary SHALL support read Read Organization by logical ID Documentation Organization resources provide context for referenced healthcare organizations. Read-only access supports resolving organization references in clinical resources. Servers SHOULD support this resource but MAY omit it based on their capabilities. Resource Conformance: SHOULD Condition 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. If supported, servers SHALL support search by patient and SHOULD support additional filters. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient who has the condition (SHALL support) SHOULD clinical-status token The clinical status of the condition SHOULD category token The category of condition SHOULD code token Code for the condition Resource Conformance: SHOULD AllergyIntolerance 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. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient who has the allergy or intolerance (SHALL support) SHOULD clinical-status token The clinical status of the allergy or intolerance Resource Conformance: SHOULD Observation 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. If supported, servers SHALL support search by patient and category. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient the observation is about (SHALL support) SHALL category token Category of observation (e.g., vital-signs, laboratory) SHOULD code token The code of the observation type SHOULD date date Obtained date/time. Date modifiers ge, le, gt, lt SHOULD be supported. SHOULD status token The status of the observation Resource Conformance: SHOULD DiagnosticReport 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. If supported, servers SHALL support search by patient and category. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient the report is about (SHALL support) SHALL category token Category of report (e.g., LAB, RAD) SHOULD code token The code for the report type SHOULD date date The clinically relevant time of the report SHOULD status token The status of the report Resource Conformance: SHOULD MedicationRequest 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. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient for whom the medication was ordered (SHALL support) SHOULD status token Status of the prescription SHOULD intent token The intent of the medication request SHOULD authoredon date Return prescriptions written on this date Resource Conformance: SHOULD MedicationDispense 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. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient for whom the medication was dispensed (SHALL support) SHOULD status token Status of the dispense SHOULD whenhandedover date When the medication was handed over Resource Conformance: SHOULD Encounter 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.). If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient present at the encounter (SHALL support) SHOULD date date A date within the encounter period SHOULD status token Status of the encounter SHOULD class token Classification of the encounter (e.g., inpatient, outpatient) Resource Conformance: SHALL ImagingStudy Core FHIR Resource ImagingStudy Reference Policy Interaction summary SHALL support read Read ImagingStudy by logical ID search-type Search for ImagingStudy resources. Documentation ImagingStudy resources represent a summary of an imaging exam as represented in DICOM. Search Parameters Conformance Parameter Type Documentation SHALL based-on reference The order that lead to the imaging study. SHALL body-site token The body-site the study examined. SHALL modality token The modality of the imaging study. SHALL identifier token The identifier of the imaging study. SHALL patient reference The patient the study is about. SHALL started date The date the study was started. SHALL subject reference The status of the study. SHALL status token The subject the study is about. SHOULD dicom-class token The type of the instances. SHOULD instance token The SOP Instance UID of the instances in the imaging study. SHOULD performer reference The person who performed the study. SHOULD reason token The reason the study was performed. SHOULD referrer reference The referring physician. SHOULD series token The the UID of a series in the study. Resource Conformance: SHOULD Device Core FHIR Resource Device Reference Policy Interaction summary SHALL support read Read Device by logical ID Documentation Represents a Device. No search has been defined as all compositions should be accessed from a reference. When a server does not support it, the resource is to be included as a contained resource. Resource Conformance: SHALL Composition Core FHIR Resource Composition Reference Policy Interaction summary SHALL support read Read Composition by logical ID Documentation Represents a rendering of a report. No search has been defined as all compositions should be accessed from the DiagnosticReport. Resource Conformance: SHALL Procedure Core FHIR Resource Procedure Reference Policy Interaction summary SHALL support read Read Procedure by logical ID Documentation Represents the procedure that generated the study. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient of the procedure. SHALL subject reference The subject of the procedure. Resource Conformance: SHALL ServiceRequest Core FHIR Resource ServiceRequest Reference Policy Interaction summary SHALL support read Read ServiceRequest by logical ID Documentation Represents the order that generated the study. Search Parameters Conformance Parameter Type Documentation SHALL identifier token The identifier of the order (accession number). SHALL patient reference The patient of the order. SHALL subject reference The subject of the order. Resource Conformance: SHALL AdverseEvent Core FHIR Resource AdverseEvent Reference Policy Interaction summary SHALL support read Read Composition by logical ID Documentation Represents an adverse event that occurred during the imaging procedure. Resource Conformance: SHALL Provenance Core FHIR Resource Provenance Reference Policy Interaction summary SHALL support read Read ServiceRequest by logical ID Documentation Represents the provenance of the report. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The patient of the order. SHALL subject reference The subject of the order. SHALL target reference The target of the provenance. Resource Conformance: SHALL ImagingSelection Core FHIR Resource ImagingSelection Reference Policy Interaction summary SHALL support read Read Composition by logical ID Documentation Represents part of an imaging study.
EEHRxF Imaging Report Resource Access Provider CapabilityStatement
CapabilityStatement for the EEHRxF Imaging Report Resource Access Provider actor. This actor serves clinical data resources following the International Patient Access (IPA) patterns and IHE QEDm Clinical Data Source capabilities.
Copyright HL7 Europe. Licensed under Creative Commons public domain (CC0 1.0).
The Imaging Report Resource Access Provider actor responds to queries for clinical data resources following IPA and QEDm patterns. This enables direct resource access complementing document-based exchange via MHD. All transactions require SMART Backend Services authorization.
SMART Backend Services authorization is REQUIRED for all transactions. Systems SHALL: - Validate JWT client credentials (RFC 7523) - Verify appropriate scopes for resource access - Use TLS 1.2 or higher for all communications - Return HTTP 401, 403, or 404 for unauthorized requests ### Resource Flexibility Following IPA's approach, servers MAY choose which clinical resources to support based on their capabilities and use cases. Patient is required for lookup context; other resources are recommended but servers may implement a subset. The server's CapabilityStatement declares which resources are actually supported. ### Scopes for Supported Resources Servers SHALL accept scopes for the resources they support: - system/AdverseEvent.read, system/AdverseEvent.search - system/Patient.read, system/Patient.search - system/Condition.read, system/Condition.search (if Condition supported) - system/AllergyIntolerance.read, system/AllergyIntolerance.search (if AllergyIntolerance supported) - system/Observation.read, system/Observation.search - system/Composition.read, system/Observation.search - system/DiagnosticReport.read, system/DiagnosticReport.search - system/MedicationRequest.read, system/MedicationRequest.search - system/MedicationDispense.read, system/MedicationDispense.search - system/Encounter.read, system/Encounter.search (if Encounter supported) - system/Practitioner.read (if Practitioner supported) - system/Organization.read (if Organization supported) - system/Procedure.read - system/Provenance.read
Patient resources support 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.
Patient identifier (e.g., national ID, MRN) - required for patient lookup
Practitioner resources provide clinical context for referenced healthcare providers. Read-only access supports resolving practitioner references in clinical resources. Servers SHOULD support this resource but MAY omit it based on their capabilities.
Organization resources provide context for referenced healthcare organizations. Read-only access supports resolving organization references in clinical resources. Servers SHOULD support this resource but MAY omit it based on their capabilities.
Condition resources represent problems, diagnoses, and health concerns. If supported, servers SHALL support search by patient and SHOULD support additional filters. Servers MAY omit this resource based on their capabilities.
The patient who has the condition (SHALL support)
AllergyIntolerance resources represent patient allergies and intolerances. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities.
The patient who has the allergy or intolerance (SHALL support)
The clinical status of the allergy or intolerance
Observation resources represent clinical observations including vital signs, laboratory results, and other measurements. If supported, servers SHALL support search by patient and category. Servers MAY omit this resource based on their capabilities.
The patient the observation is about (SHALL support)
Category of observation (e.g., vital-signs, laboratory)
Obtained date/time. Date modifiers ge, le, gt, lt SHOULD be supported.
DiagnosticReport resources represent laboratory results and imaging reports. If supported, servers SHALL support search by patient and category. Servers MAY omit this resource based on their capabilities.
The patient the report is about (SHALL support)
The clinically relevant time of the report
MedicationRequest resources represent medication orders and prescriptions. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities.
The patient for whom the medication was ordered (SHALL support)
Return prescriptions written on this date
MedicationDispense resources represent medication dispensing events. If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities.
The patient for whom the medication was dispensed (SHALL support)
Encounter resources represent patient encounters (visits, admissions, etc.). If supported, servers SHALL support search by patient. Servers MAY omit this resource based on their capabilities.
The patient present at the encounter (SHALL support)
Classification of the encounter (e.g., inpatient, outpatient)
ImagingStudy resources represent a summary of an imaging exam as represented in DICOM.
The order that lead to the imaging study.
The SOP Instance UID of the instances in the imaging study.
Represents a Device. No search has been defined as all compositions should be accessed from a reference. When a server does not support it, the resource is to be included as a contained resource.
Represents a rendering of a report. No search has been defined as all compositions should be accessed from the DiagnosticReport.
Represents the procedure that generated the study.
Represents the order that generated the study.
The identifier of the order (accession number).
Represents an adverse event that occurred during the imaging procedure.
Represents the provenance of the report.