The actor responsible for creating the Imaging Report resources. Typically this role is combined with the ImReportProvider.

The actor responsible for providing the Imaging Report resources.

This operation generates a FHIR report from an DiagnosticReport resource that points to a Composition resource. Its behavior is identical to the Composition/$document operation but adds the DiagnosticReport and its referenced resources to the Bundle.

EHDS refined base model for Address structure

Healthcare directives concerning life or after life wishes of the patient

Alert flag

EHDS refined base model for allergy/intolerance

EHDS refined base model for Appointment. This is a simplified model with minimal information - it is not intended to cover the full functionality of booking systems.

EHDS refined base model for This type is for containing or referencing attachments - additional data content defined in other formats. The most common use of this type is to include images or reports in some report format such as PDF. However, it can be used for any data that has a MIME type.

EHDS refined base model for Body structure

EHDS simplified model for care plan. The model includes very minimal information and is not designed to cover the full functionality of care plans.

EHDS refined base model for a clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

EHDS refined base model for Coverage

Current pregnancy status

Common elements (including header) for all documents and their independently functioning parts, e.g FHIR resources.

EHDS refined base model for Device information

EHDS refined base model for device use information

EHDS refined base model for Discharge Report

EHDS refined base model for common document data elements, including the common header. Data relevant to document type and its content for administrative and searching purposes.

EHDS refined base model for Dosage

Logical model for usage instructions for administring the requested product. Based on FHIR Dosage complex data type. When implemented, this model may be reduced significantly according to the specific use case.

EHDS refined base model for Encounter

EHDS refined base model for Endpoint

EHDS refined base model for Episode of care

EHDS refined base model for family member history

EHDS refined base model for Functional status

EHDS refined base model for Health professional (HP)

EHDS refined base model for Human name

EHDS refined base model for Medical Imaging Result Report

EHDS refined base model for Imaging study

EHDS refined base model for Immunisation

EHDS refined base model for an infectious contact

EHDS refined base model for Observation performed by laboratory

A - EHDS refined base model for Laboratory order

B.1 - EHDS refined base model for Laboratory order body

A.1 - EHDS refined base model for Laboratory order header data elements

B.1 - EEHRxF refined base model for Laboratory result report body

A.1 - EHDS refined base model for laboratory report header data elements

EHDS refined base model for Laboratory result report

EHDS refined base model for Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.

EHDS refined base model for A photo, video, or audio recording acquired or used in healthcare.

EHDS refined base model for a single medication administration

Explicit statement about declining the dispense request (prescription), usually recorded in order to communicate the issue back to the prescriber. Reasons for declining a dispense may vary, but typically this statement is only sent when a following action is expected on the prescriber’s side (cancelling or changing the problematic prescription or the whole treatment).

Logical model for medication dispensation (based on request or independently)

Logical model for prescribed/dispensed medication. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile. Model is suitable for generic/virtual medications as well as branded/real products.

Logical model for medication prescription. A prescription contains one or more prescription items.

Statement about a single medication as part of a medication summary.

EHDS refined base model for Observation information

EHDS refined base model for Health provider or any other type of organisation

EHDS refined base model for Patient:Animal

EHDS refined base model for patient (subject of care) information

EHDS refined base model for Patient Summary

Pregnancy history for one pregnancy

EHDS refined base model for an action that is or was performed on or for a patient

EHDS refined base model for Patient/subject guardian and other related person information

EHDS refined base model for Specification of requested service or services

EHDS model for social history observations

EHDS refined base model for A sample to be used for Analysis

EHDS refined base model for Substance

Statement about using a substance (such as tobacco, alcohol, drugs, etc).

EHDS refined base model for Telecommunication contact information structure

Relevant information about the patient's recent travel history, for one visit

Adverse Event that occurred during an imaging procedure.

Document Bundle for Imaging Report

Clinical document used to represent a Imaging Study 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.

A DocumentReference profile for the Report DocumentReference used in MHD deployments.

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.

Imaging Selection referring to a DICOM SR instance

Imaging Selection

Key images represented as an ImagingSelection

This profile represents an imaging study instance.

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.

This profile on ServiceRequest represents the order for the Imaging Study and report.

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

entryUUID Identifier holding a UUID, based on IHE-MHD R4.

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.

This extension provides a reference to the DiagnosticReport instance that is associated with this Composition.

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

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

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

Units for Dose Length.

Units for Effective Dose.

Units for Gray Square.

Imaging Device Type.

This value set includes all imaging procedure types.

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.

A list of XDS class codes that can be used for filtering manifests (zie XDS_classCode_MetaData_Coding_System). Note: a IHE needs to make a formal FHIR CodeSystem for this.

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.

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

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

Example of an Imaging Report Bundle for a knee MRI report.

MHD DocumentReference for the knee MRI Imaging Report example.

Example ImagingStudy showing an MRI for the left foot

Transaction Bundle illustrating the upload of a knee MRI Imaging Report DocumentReference with embedded PDF report.