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

## CapabilityStatement: MADO Document Responder (server)

Official URL: https://profiles.ihe.net/RAD/MADO/CapabilityStatement/IHE.RAD.MADO.DocumentResponder | Version: 0.1.0
Active as of 2026-02-27 | Computable Name: IHE_RAD_MADO_DocumentResponder

IHE RAD Manifest based Access to DICOM Objects(MADO) - Document Responder (server). It extends MHD Document Responder (client).

Please note that this CapabilityStatement representation only shows the delta of this instance with the MHD Document Responder (client). All the functionality specified by the Document Consumer (client) SHALL also be supported.

Raw OpenAPI-Swagger Definition file | Download

## MADO Document Responder (server)

- Implementation Guide Version: 0.1.0
- FHIR Version: 4.0.1
- Supported Formats: `json`, `xml`
- Published on: 2026-02-27
- Published by: IHE Radiology Technical Committee

> Note to Implementers: FHIR Capabilities

> Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement imports the CapabilityStatement Document Responder (server)

## FHIR RESTful Capabilities

### Mode: `server`

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
DocumentReference |  |  |  |  |  | bodysite, modality, study-instance-uid, accession-number |  |  |

#### Resource Conformance: unspecifiedDocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
Interaction summary

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | bodysite | `token` | Anatomical region of the related imaging study
SHALL | modality | `token` | Modality of the related imaging study
SHALL | study-instance-uid | `token` | Study Instance UID of the related imaging study
SHALL | accession-number | `token` | Accession Number of the related imaging study