Manifest-based Access to DICOM Objects (MADO)
0.1.0 - trial-use

Manifest-based Access to DICOM Objects (MADO), published by IHE Radiology Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/RAD.MADO/ and changes regularly. See the Directory of published versions

## FHIR Imaging Manifest

The MADO FHIR imaging manifest represents a summary of the data stored in a DICOM imaging study. It contains the information stored in a PACS expressed in FHIR. This page defines the FHIR encoding of such manifest. It is the 'document' that is searched for and provides the URL's that allow download of the imaging content.

This section specifies the structure and format of an Imaging Study Manifest for the MADO Profile using the DICOM standards. It is based on the DICOM Key Object Selection (KOS) Document Information Object Definition (IOD) as specified in DICOM PS3.3 Section A.35.4 Key Object Selection Document IOD.

### FHIR Manifest overview

The figure below presents an overview of the data that is part of the imaging-manifest. In order to keep the diagram readable, not all references are included.

Figure: FHIR Manifest Overview

The imaging study manifest is a FHIR bundle that SHALL conform to the MADO FHIR Bundle profile. This `Bundle` includes the MADO FHIR ImagingStudy resource, the MADO Patient, MADO Creator and MADO Creator Organization, the MADO Requested Procedure, and the MADO FHIR WADO Endpoint and MADO FHIR WebViewer Endpoints.

The profiles for the MADO FHIR Bundle and the resources it contains have fields marked as `Must Support` (`MS`) (marked with an S in the Flags column), which SHALL be populated if the value is known.

The MADO Patient resource holds the patient information.

The MADO Creator and MADO Creator Organization resources provide information on the device and organization that created the manifest.

The MADO Requested Procedure provides information on the order for the imaging study, including the order specific identifiers: Accession Number, Placer Number and Filler number.

`Endpoint` resources contain the information that allows the client to access the DICOM data. The current model identifies different `Endpoint`s:

- On study level, the manifest MAY contain:
  - The MADO FHIR WebViewer Endpoint which provides a web based endpoint. The `address` defined in the endpoint, opens a webviewer on the study.
- For each series, the manifest SHALL contain:
  - The MADO FHIR WADO Endpoint which `address` field holds the WADO base url that allows access to the series information (see IHE RAD TF-2: 4.107 WADO-RS Retrieve [RAD-107]).

### Related FHIR profiles

The following links are provided for convenience, they list the different profiles defined in this IG as well as their descriptions. Please note this copies the description text from the profile, please interpret any normative language in these descriptions within the scope of the profile.

Title | Description
MADO Accession Number Identifier | Profile for the Accession Number Identifier used in the MADO context. This profile is used for the Identifier that represents the Accession Number in the MADO context. It includes additional constraints and extensions specific to the MADO context, such as the value set for the type of identifier and the fixed value for the system of the identifier. The combination of the `Identifier.value` of the identifier and the `Identifier.system` of the identifier should be globally unique. The `Identifier.value` of the identifier should be locally unique within the context of the system that assigns the accession number. The `Identifier.system` SHALL be consistent with the content of the DICOM sequence "Issuer of Accession Number Sequence" (0008,0051).
Extension: Anatomical Region | The anatomical region in an ImagingStudy instance. This is additional information next to ImagingStudy.series.bodySite.
MADO Creator | A profile for the Device resource that represents the creator of an imaging study manifest. The primary goal is to communicate the fields: type = MadoDeviceType#mado-creator "MADO Creator" manufacturer owner (Reference to MadoCreatorOrganization)
MADO Creator Organization | Profile on Organization that specifies the required elements for the organization that creates MADO manifests.
MADO Imaging Study Manifest FHIR Bundle | Profile for FHIR Bundles used as a imaging study Manifest in the MADO context. It includes constraints and extensions specific to imaging study manifests, such as the type of study, the clinical specialty, and the anatomical region of interest.
MADO Imaging Study | Profile for ImagingStudy resources that represent the imaging studies manifest in the MADO context. It includes additional constraints and extensions specific to the MADO context, such as the study modality, the clinical specialty, the anatomical region of interest, the presence of significant images. In the case significant images are present, an instance referenced in the `ImagingStudy` is a Key Object Selection document TID 2010, the `ImagingStudy.series.instance.extension[ko-document-title]` SHALL contain the Document Title code of the referenced document, and the `ImagingStudy.series.instance.description` field contains the contents of the KeyObjectSelectionDescription field.
Extension: MADO Document Title of Key Object Selection documents | The document title code of the Key Object Selection document TID 2010 this instance refers to.
Extension: Number of Frames | The number of frames in an ImagingStudy instance.
MADO Patient | Profile on Patient that specifies the required elements for the patient that is the subject of the manifest.
MADO Provenance | The purpose of this resource is to indicate information about the system that created the manifest. Additionally, it can be used to sign the content of the Bundle. In DICOM KOS this information (and the referred MadoCreator) corresponds to the Institution Name, Institution Id, Manufacturer Name in the General Equipment module.
MADO Referenced Accession Number Identifier | Profile for the Reference that contains the Accession Number Identifier used in the MADO context. This profile is used for the Reference that contains the Identifier that represents the Accession Number in the MADO context. It includes additional constraints and extensions specific to the MADO context, such as the value set for the type of identifier and the fixed value for the system of the identifier.
MADO Referenced Study Instance UID Identifier | Profile for the Reference that contains the Study Instance UID Identifier used in the MADO context. This profile is used for the Reference that contains the Identifier that represents the Study Instance UID in the MADO context. It includes additional constraints and extensions specific to the MADO context, such as the value set for the type of identifier and the fixed value for the system of the identifier.
MADO Requested Procedure | A profile for the ServiceRequest resource that represents the Requested Procedure (see 6.X.2.8.1 Referenced Request Macro Description).
Extension: Retrieve Location UID | The location UID of the source of the WADO URL. See XC-WADO and https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_A.35.4.3.html#table_A.35.4-1.
MADO Study Instance UID Identifier | Profile for the Study Instance UID Identifier used in the MADO context. This profile is used for the Identifier that represents the Study Instance UID in the MADO context. It includes additional constraints and extensions specific to the MADO context, such as the value set for the type of identifier and the fixed value for the system of the identifier.
Endpoint: MADO WADO endpoint | This profile defines a WADO endpoint for accessing imaging study content. MADO WADO Endpoint holds an example of a endpoint with a `RetrieveLocationUid` and an address. This profile supports two cases (see X.4.1.2 Intra-community Sharing Infrastructure): The case where `address` is provided in addition to a `RetrieveLocationUID`. The case when only the `RetrieveLocationUID` is known and the `address` is unknown (see example EndpointWadoExampleNoAddress). In this case: The `address` SHALL be set to "http://notspecified" A `Data Absent Reason Exception` with the value `unknown` SHALL be added to indicate that the address is missing. Note that we do not require population of the `payloadMimeType` as this information is not present in the DICOM KOS. As is defined in section 6.X.6.6.2, in MADO, only the `dicom` mimetype is required.
Endpoint: MADO profile for Web Viewer endpoints | This profile defines the Web Viewer endpoint for accessing imaging study content. The URL in the Endpoint SHALL be a fully populated URL that contains all the information required to the launch the viewer to this study. The `address` field in the endpoint corresponds to the `Display URI` in the DICOM KOS manifest (see 6.X.2.13 Hierarchical SOP Instance Reference Macro). The endpoint MAY be encoded using the format defined in IHE-RAD-IID.

### Examples

The sections below show the various MADO data elements that are generated based on a DICOM study.

The Binary resource contains the DICOM KOS Manifest for the study. The `Bundle` resource contains the FHIR Imaging Study Manifest. The `DocumentReference` instances provide MHD DocumentReference instances that point to these manifests.

#### Study A

Based on the DICOM study A, (Study_A.zip), the following resources are created:

Type | Id
Binary | dicom-kos-mado--2047166865
Bundle | mado-bundle--2047166865
DocumentReference | mado-documentreference-fhir--2047166865
DocumentReference | mado-documentreference-kos--2047166865

#### Study B

Based on the DICOM study A, (Study_B.zip), the following resources are created:

Type | Id
Binary | dicom-kos-mado--2047166866
Bundle | mado-bundle--2047166866
DocumentReference | mado-documentreference-fhir--2047166866
DocumentReference | mado-documentreference-kos--2047166866