The actor responsible for consuming the Imaging Report resources.

The actor responsible for producing the Imaging Report resources.

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

CapabilityStatement for the EEHRxF Imaging Report Document Consumer actor. This composite actor consumes EEHRxF FHIR Imaging Report Documents by querying a Imaging Report Document Access Provider.

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.

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

OperationDefinition for creating a document Bundle based on a DiagnosticReport.

Searches for document references with a specific body site.

Searches for document references with a specific modality.

Adverse Event that occurred during an imaging procedure.

Imaging Selection referring to a DICOM SR instance

Basic resource holding cross-version extensions for Imaging Selection allowing ImagingSelection to be used in R4.

Document Bundle for Imaging Report

Collection Bundle with minimal metadata for imaging report exchange

Clinical document used to represent a Imaging Report for the scope of the HL7 Europe project.

The device the made the image.

DiagnosticReport profile for Imaging Reports. This document represents the report of an imaging study. It is the anchor resource that refers to all structured data as well as the Composition resource that contains the narrative text of the report.
The structure of the modelled has been aligned with the DiagnosticResource as defined by IHE-RAD-HL7IDR. As this specification has not been published yet, the relevant extensions have been included in this specification.

DiagnosticReport profile for minimal metadata imaging report exchange. This profile shares all common imaging report modeling with DiagnosticReportEuImaging but does not require a matching Composition resource.

A document containing key images for a patient. It can refer to a DICOM or non-DICOM image. When referring to a DICOM image, the DocumentReference.content.attachment.url should be a WADO-URI. When referring to a non-DICOM image, the DocumentReference.content.attachment.url should be a direct URL to the image.

When the resource represents a DICOM instance it SHALL contain a the SOP Instance UID in the identifier element. When the resource represents a DICOM series it SHALL contain the Series Instance UID in the identifier element.

Profile for DocumentReference resources used in the EEHRxF context, based on the IHE MHD Minimal DocumentReference profile. This profile is used for the DocumentReference resources that represent imaging reports in the EEHRxF context. It includes additional constraints and extensions specific to imaging reports, such as the type of report, the clinical specialty, the anatomical region of interest and the profile of the imaging report.

Profile for DocumentReference resources used in the EEHRxF context, based on the IHE MHD Minimal DocumentReference profile.

Search Strategy:

• category: Use ValueSet EEHRxF Document Priority Category ValueSet (EHDS Priority Categories) for coarse document filtering (Patient Summaries, Discharge Reports, etc.)
• type: Use EEHRxFDocumentTypeVS (LOINC) for clinical precision (specific document types)
• context.practiceSetting: SHOULD be used to differentiate lab vs imaging reports when category=REPORTS

This profile represents an imaging study instance.

Key images represented as an ImagingSelection for R4

Gestational Age Observation

Finding during imaging procedure.

A record for the radiation dose the subject has been exposed to during an imaging procedure. E.g. based on information from https://dicom.nema.org/medical/dicom/current/output/html/part16.html and https://build.fhir.org/ig/HL7/fhir-radiation-dose-summary-ig/index.html

This profile on Procedure represents the imaging procedure. In this DICOM this is referred as the 'Performed Procedure Step' (PPS). This profile is used to capture metadata about the imaging procedure itself.

This profile on ServiceRequest represents the order for the Imaging Study and report. In DICOM this is referred to as the Requested Procedure. The code element represents the requested imaging procedure type which includes the requested modality.

This profile on Identifier represents the Accession Number for the Imaging Order.

Within a Hospital Information System environment, accession numbers will usually uniquely identify a manifest or report but are not required to always map 1:1 with a report or manifest due to certain imaging workflows. The imaging report may not be uniquely identified by accession number in an overread scenario (two radiologists reading a single imaging study). The manifest may not be uniquely identified by accession number in the case that the RIS imaging request (accession number assigner) requires two imaging modalities to perform the exam, and thus produces two image manifests.

In order to ensure uniqueness across Hospital Information Systems, accession numbers are required to have a system value that identifies the namespace for the issuing authority (ensuring their global uniqueness).

This profile on Identifier represents the SOP Instance UID (0008,0018) for the Imaging Order.

This profile on Identifier represents the Study Instance UID (0020,000D) for the Imaging Order.

The anatomical region in an ImagingStudy instance. This is additional information next to ImagingStudy.series.bodySite.

Canonical URL of the profile represented by the referenced content.

Communications captures what communications have been made with other care providers

Studies used for comparison in part of diagnostic reporting

Imaging procedure used for the imaging acquisition and procedure specific information.

Impression in the imaging report

KeyImage in the imaging report

Patient history that are relevant for the report

Recommendations for any follow up actions

A description of the instance in an ImagingStudy.

The number of frames in an ImagingStudy instance as required by Xt-EHR logical ImagingStudy logical model.

ValueSet for priority document categories in EEHRxF as the document categories as defined in the EHDS regulation. See EEHRxFDocumentPriorityCategoryCS for the complete list and background.

Document type codes for clinical precision in document identification.

This ValueSet contains LOINC codes for specific document types used in DocumentReference.type. Unlike category (coarse search), type provides clinical precision for identifying exact document kinds.

Usage Pattern:

• type is primarily used for client-side filtering after a broad category search
• type MAY be used as a search parameter when the specific document type is known
• Multiple type codes may apply to a single document (e.g., a discharge summary that is also a patient summary)

MVP Document Types (Priority Categories):

• Patient Summary (IPS)
• Discharge Summary (HDR)
• Laboratory Report
• Diagnostic Imaging Report

Note: This list will expand as additional priority categories are implemented.

JFM: This ValueSet should be made up of other ValueSets, with each of them assigned to one of the priority categories. Thus it is clear what document types are within each category. Is this the place to find all of them? https://confluence.hl7.org/spaces/HEU/pages/358255737/Implementation+Guides

A shortlist of anatomical regions that can be used for searching reports and manifests. When the MADO manifest is implemented, this ValueSet can be replaced with a reference to that ValueSet.

Codes to be used in DiagnosticReport.supportInfo for imaging reports.

Imaging Device Type.

This value set includes all imaging procedure types defined in SNOMED CT. The codes represent combinations of the modality to be used and the procedure to be performed.

Imaging Study series performer type codes, it extends on the base set defined in the FHIR specification.

The set of radiology types as defined by LOINC.

Reasons a section in an imaging report is empty.

These codes define what an annotation annotates.

CodeSystem for priority document categories in EEHRxF as the document categories as defined in the EHDS regulation.

The codes defined here are directly linked to the Priority Categories defined in the EHDS regulation. The meaning of these codes is directly linked to the meaning given to the concepts in the EHDS regulation.

The EHDS Regulation initially defines six priority categories of electronic health data that all Member States must support first for cross-border primary use. These categories are explicitly listed in Article 14 of Regulation (EU) 2025/327.

Article 105 specifies the date when support for these priority categories is required: 26 March 2029 for categories (a), (b) and (c); 28 March 2031 for (d), (e) and (f).

EHDS empowers the EU Commission to make changes to the list of priority categories at any point in time by means of a Delegated Act (Article 14(2)). There will be a minimum 1-year lead time between the decision to add a new priority category and the initial date when support ahs to be implemented.

The definitions of the priority categories comes from ANNEX I of the EHDS Regulation.

Code system for codes to be used in DiagnosticReport.supportInfo for imaging reports.

Code system for codes that are defined in DICOM but for which no matching code system is available in FHIR.

Minimal metadata bundle carrying the report anchor and context resources.

Document bundle grouping resources in the semi-structured example.

Document bundle grouping resources in the structured example.

Example of a CompositionEuImaging showing the report for the left/right foot study

Example of a CompositionEuImaging showing the report with structured data.

Example of a DiagnosticReportEuImaging showing the report for the left/right foot study

Example of a DiagnosticReportEuImaging showing the report for a stress echo

Minimal metadata DiagnosticReport compliant with DiagnosticReportEuImaging profile.

MHD DocumentReference for semi-structured report.

MHD DocumentReference for structured report.

MHD DocumentReference for unstructured report.

Key image showing the ultrasound at rest.

Key image showing the ultrasound during stress.

Shows the WMSI graphs.

Example ImagingStudy showing an MRI for the left foot

Example ImagingStudy showing an MRI for the right foot

Transthoracic echocardiogram for 3D TEE 2D

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

WMSI measurement.

Patient blood pressure in echo report history section

Patient height in echo report history section

Patient height in echo report history section

Patient weight in echo report history section

The organization employing the report author.

Organization of the report author.

Organization used in the unstructured report

The patient in the semi-structured report

Patient used in the structured report example

Patient used in the unstructured report

The author details

The report author.

The role the author has in the organization.

Role of the report author.

Order to come back next year