HL7 Europe Imaging Report R5, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.1-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/imaging-r5/ and changes regularly. See the Directory of published versions
This page lists the structural profiles defined in this specification
| Name | Title | Description |
| BundleReportEuImaging | Bundle: Imaging Report | Document Bundle for Imaging Report |
| CompositionEuImaging | Composition: Imaging Report | Clinical document used to represent a Imaging Report for the scope of the HL7 Europe project. |
| DiagnosticReportEuImaging | DiagnosticReport: Imaging Report | 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 |
| Name | Title | Description |
| DocumentReferenceImagingReport | EEHRxF MHD DocumentReference Profile for Imaging Reports | 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. |
| DocumentReferenceUnstructuredImagingReport | EEHRxF MHD DocumentReference Profile for unstructured imaging reports | 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, and the anatomical region of interest. It is intended for unstructured reports needed to support legacy reports, where the content is provided as an attachment without a specific structure or format. |
| Name | Title | Description |
| EEHRxFImagingReportDocumentAccessProvider | EEHRxF Imaging Report Document Access Provider CapabilityStatement | 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. |
| EEHRxFImagingReportDocumentConsumer | EEHRxF ImagingReport Document Consumer CapabilityStatement | 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. |
| EEHRxFResourceAccessProvider | 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. |
| EEHRxFResourceConsumer | EEHRxF Imaging Report Resource Consumer CapabilityStatement | 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. |
| Name | Title | Description |
| AccessionNumberIdentifierEuImaging | Identifier: Accession Number | 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). |
| AdverseEventEuImaging | AdverseEvent: Imaging Adverse Event | Adverse Event that occurred during an imaging procedure. |
| DeviceEuImaging | Device: Imaging Device | The device the made the image. |
| ImagingSelectionEuImaging | ImagingSelection: General | Imaging Selection |
| ImagingSelectionKeyImageEuImaging | ImagingSelection: Key Image | Key images represented as an ImagingSelection |
| ImagingStudyEuImaging | ImagingStudy: General | This profile represents an imaging study instance. |
| ObservationFindingEuImaging | Observation: Imaging Finding | Finding during imaging procedure. |
| ObservationGestationalAgeEuImaging | Observation: Gestational Age | Gestational Age Observation |
| ObservationRadiationDoseEuImaging | Observation: Radiation Dose | 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 |
| ProcedureEuImaging | Procedure: Imaging Acquisition | 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. |
| ServiceRequestOrderEuImaging | ServiceRequest: Imaging Order | This profile on ServiceRequest represents the order for the Imaging Study and report. In DICOM this is referred
to as the Requested Procedure. The |
| SopInstanceUidIdentifierEuImaging | Identifier: SOP Instance UID | This profile on Identifier represents the SOP Instance UID (0008,0018) for the Imaging Order. |
| SrInstanceImagingSelectionEuImaging | ImagingSelection: DICOM SR Instance | Imaging Selection referring to a DICOM SR instance |
| StudyInstanceUidIdentifierEuImaging | Identifier: Study Instance UID | This profile on Identifier represents the Study Instance UID (0020,000D) for the Imaging Order. |
| Name | Title | Description |
| DiagnosticReportSupportingInfoCodeSystem | ValueSet: Diagnostic Report Support Info Code System | Code system for codes to be used in |
| MissingDicomTerminology | ValueSet: Missing DICOM Terminology | Code system for codes that are defined in DICOM but for which no matching code system is available in FHIR. |
| Name | Title | Description |
| DeviceEuImagingType | ValueSet: Imaging Device Type | Imaging Device Type. |
| DiagnosticReportSupportingInfoVCodes | ValueSet: DiagnosticReport supportInfo codes | Codes to be used in |
| Hl7EuImagingSectionValueSet | ValueSet: Section codes used to label annotations. | These codes define what an annotation annotates. |
| ImagingReportTypesEuVSEuImaging | ValueSet: Radiology Report Types | The set of radiology types as defined by LOINC. |
| ImagingStudyEuImagingPerformerTypeVS | ValueSet: Imaging Study Performer Type Value Set | Imaging Study series performer type codes, it extends on the base set defined in the FHIR specification. |
| ProcedureEuImagingType | ValueSet: Imaging Procedure 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. |
| SectionEmptyReasonEuImaging | ValueSet: Reasons a section in an imaging report is empty. | Reasons a section in an imaging report is empty. |
| ValueSetAnatomicalRegion | ValueSet: Anatomical Region | 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. |
| XdsClassCodeVs | ValueSet: XDS Class Codes | 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. |