Mobile access to Health Documents (MHD)
4.2.3-current - ci-build International flag

Mobile access to Health Documents (MHD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 4.2.3-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.MHD/ and changes regularly. See the Directory of published versions

CapabilityStatement: Document Recipient implementing Comprehensive Metadata Option

Official URL: https://profiles.ihe.net/ITI/MHD/CapabilityStatement/IHE.MHD.DocumentRecipient.Comprehensive Version: 4.2.3-current
Active as of 2024-11-26 Computable Name: IHE_MHD_DocumentRecipient_Comprehensive

IHE ITI Mobile access to Health Documents (MHD) - Document Recipient - with Comprehensive declared Option.

This is the Requirements CapabilityStatement for a Document Recipient with Comprehensive Metadata Option declared Option. This actor must use Comprehensive Metadata Option. Note that XDS on FHIR Option requires the Comprehensive Metadata Option.

The Document Source uses the Provide Document Bundle ITI-65 to communicate metadata and documents to the Document Recipient.

Provide Document Bundle [ITI-65]Document SourceDocument Recipient1Request to publish documents [ITI-65]2validate content received3propigate to Grouped Actor (e.g. XDS Provide and Register)4Documents published [ITI-65]


Figure: Provide Document Bundle Interactions

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement IHE.MHD.DocumentRecipient.Comprehensive

Document Recipient implementing Comprehensive Metadata Option

  • Implementation Guide Version: 4.2.3-current
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: 2024-11-26 21:28:26+0000
  • Published by: IHE IT Infrastructure 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.

FHIR RESTful Capabilities

Mode: server

Security

Recommend ATNA, encouraged IHE-IUA or SMART-on-FHIR

Summary of System-wide Interactions
  • Supports the transactioninteraction described as follows:

    https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Comprehensive.ProvideBundle