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 Generate Metadata Option

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

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

This is the Requirements CapabilityStatement for a Document Recipient with Generate Metadata Option declared Option.

The Document Source uses the Generate Metadata ITI-106 to communicate a document to the Document Recipient to have a DocumentReference generated and processed.

Document SourceDocument Recipient1Generate Metadata (document)2Extract the document3Create DocumentReference from document4Create SubmissionSet from DocumentReference and context5persist (e.g. XDS Provide and Register)6Generated DocumentReference


Figure: Generate Metadata Interactions

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement IHE.MHD.DocumentRecipient.Generate

Document Recipient implementing Generate 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.Minimal.ProvideBundle

  • Supports the transactioninteraction described as follows:

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

  • Supports the transactioninteraction described as follows:

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

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 TypeProfileRSUCSearches_include_revincludeOperations
DocumentReference $$generate-metadata

Resource Conformance: supported DocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
Interaction summary

    Extended Operations
    ConformanceOperationDocumentation
    SHALL$$generate-metadata