IHE-MHD

IHE MHD mobile health documents FHIR-based modernization XDS.

Definition

IHE MHD architecture: (1) Document Source MHD: equivalent IHE XDS Document Source, submits documents via FHIR Bundle POST containing DocumentReference + DocumentManifest + Binary resources. (2) Document Recipient MHD: receives submitted documents, equivalent IHE XDS Document Repository. (3) Document Responder MHD: equivalent IHE XDS Document Registry + Repository combined, exposes FHIR DocumentReference search API. (4) Document Consumer MHD: queries Document Responder via FHIR DocumentReference search (e.g., GET DocumentReference?patient.identifier=... &type=...&date=gt2024-01-01), retrieves Binary content via FHIR Binary read. (5) Transactions: ITI-65 Provide Document Bundle (Source -> Recipient), ITI-66 Find Document Manifests, ITI-67 Find Document References, ITI-68 Retrieve Document. (6) Compared XDS: MHD simpler + FHIR-native (REST + JSON instead SOAP/MTOM + ebXML), better mobile/web support, smaller metadata model (XDS has ~30 attributes, MHD uses subset via FHIR DocumentReference + DocumentManifest), suitable cloud-native deployments. (7) Use cases: mobile health apps (patient access apps need access clinical documents via FHIR), web-based clinical viewers, modern HIE architectures FHIR-first. IHE MHD published 2015, FHIR R4 update 2019, Trial Implementation status since 2020 (Final Text upcoming).

Origin

IHE MHD profile published 2015 by IHE ITI ; FHIR R4 update 2019 ; Trial Implementation status 2020+ ; XDS modernization toward FHIR.

Example in context

Patient Apple Health iOS app uses MHD: fetches DocumentReference resources via GET /DocumentReference?patient=Patient/123 to HIE FHIR endpoint, displays list of clinical documents (discharge summaries + lab results + radiology reports + visit notes) chronologically, taps document fetches Binary via GET /Binary/{id} returns PDF or CCDA content rendered iOS app native viewer.

Related terms

• IHE XDS — predecessor SOAP-based.