Manifest-based Access to DICOM Objects (MADO) Profile (FHIR-R5 elements)
0.2.0-snapshot1 - draft
150
This page is part of the Manifest-based Access to DICOM Objects (MADO) Profile (FHIR-R5 elements) (v0.2.0-snapshot1: QA Preview) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.
Imaging Manifest Reports Provider/Creator |
This actor is responsible for creating/providing the Imaging Manifest resources. |
Imaging Study Report Provider/Creator |
The actor responsible for creating/providing the Imaging Report resources. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
OperationDefinition: create a FHIR manifest |
This operation generates a FHIR manifest from an ImagingStudy resource by extracting relevant metadata and packaging it according to the FHIR imaging manifest specification. |
These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.
SearchParameter: DateImagesAcquired |
Searches for manifest representing imaging studies that were acquired on a specific date. |
SearchParameter: DateManifestCreated |
Searches for manifest created on a specific date. |
SearchParameter: DocumentReference-Creation |
This SearchParameter enables finding DocumentReference by the creation dateTime. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
Bundle: Imaging Manifest |
This profile represents a manifest of an imaging study. It holds the ImagingStudy resource that mirrors the information in the DICOM study allow with other resources that are required to express the information in DICOM in FHIR. |
Device: Imaging Acquisition Device |
The device the made the image. |
EndPoint: IDD Image Viewer |
This profile defines a placeholder for an Endpoint for a viewer that can be used to access the study, serie it is present on. The application is based on IHE-IID. |
EndPoint: Image Viewer |
An Endpoint holding the URL of an image viewer that can be used to see the DICOM Study it is present on. It is RECOMMENDED that the URL to the viewer is formatted according to IHE-IID, but other formats are possible as well. |
Endpoint: IHE-XC-WADO |
This profile defines the XC-WADO endpoint for accessing imaging study content. |
Endpoint: WADO |
This profile defines the WADO endpoint for accessing imaging study content. |
Imaging Selection |
Imaging Selection |
Imaging Selection: DICOM SR instance reference |
Imaging Selection referring to a DICOM SR instance |
ImagingSelection: Key image |
Key images represented as an ImagingSelection, it refers to minimal 1 instance. |
ImagingStudy: Manifest Imaging Study |
This profile represents an imaging study instance. |
Manifest DocumentReference for MHD deployments |
A DocumentReference profile for the Manifest DocumentReference used in MHD deployments. |
Patient: Imaging Patient |
This profile on Patient represents the Imaging Patient. |
Procedure: Image Acquisition Procedure |
This profile on Procedure represents the imaging procedure. |
ServiceRequest: Imaging Order |
This profile on ServiceRequest represents the order for the Imaging Study and report. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
CodeableReferenceWithRequiredCoding | |
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). |
Identifier: Imaging SOP Class UID Identifier |
This profile on Identifier represents the SOP Class UID (0008,0018) for the Imaging Order. |
Identifier: Study Instance UID |
This profile on Identifier represents the Study Instance UID (0020,000D) for the Imaging Order. |
Placeholder for IHE MHD Entry UUID Identifier in FHIR R5. |
entryUUID Identifier holding a UUID, based on IHE-MHD R4. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
Extension: Instance Description |
A description of the instance in an ImagingStudy. |
These define sets of codes used by systems conforming to this implementation guide.
Anatomical Region |
A shortlist of anatomical regions that can be used for searching reports and manifests. |
DiagnosticReport supportInfo codes |
Codes to be used in |
HL7 EU Imaging Manifest Types |
HL7 EU Imaging Manifest Types used in Compositions and DiagnosticReports. |
Imaging Procedure Type |
This value set includes all imaging procedure types. |
Imaging Study Performer Type Value Set |
Imaging Study series performer type codes, it extends on the base set defined in the FHIR specification. |
Practice Settings |
A list with practice settings to be used for filtering manifests (source IHE PCC) |
ValueSet: Imaging Device Type |
Imaging Device Type. |
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, |
These define new code systems used by systems conforming to this implementation guide.
CodeSystem for terminology used in Endpoint resources in the EU Imaging IG. |
This code system defines various codes used to define ValueSets for Endpoints within the HL7-EU imaging IG. |
Diagnostic Report Support Info Code System |
Code system for codes to be used in |
Missing DICOM Terminology |
Code system for codes that are defined in DICOM but for which no matching code system is available in FHIR. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
Example DocumentReference |
Example DocumentReference |
Example ImagingStudy Manifest 1 |
Example ImagingStudy Manifest |
Example ImagingStudy Manifest 2 |
Example ImagingStudy Manifest |
Example-WadoEndpoint |