Overview
The Mobile Access to Health Documents (MHD) Profile defines one standardized interface to health document sharing. This profile is applicable to systems where needs are simple, such as pulling the latest summary for display.
The following are examples of environments which may choose the MHD Profile:
- Medical devices such as those targeted by the Patient Care Devices (PCD) domain or Continua organization, submitting data in the form of documents.
- Kiosks used by patients in hospital registration departments, where it is anticipated that a hospital staff member will review, edit, and approve the document before it is allowed into the hospital system.
- PHR publishing into a staging area for subsequent import into an EHR or HIE.
- Patient or provider application that is configured to securely connect to a PHR in order to submit a medical history document. (For example BlueButton+)
- Electronic measurement device participating in an XDW workflow and pulling medical history documents from an HIE.
- A General Practitioner physician’s office with minimal IT capabilities using a mobile application to connect to an HIE or EHR
Actors and Transactions
The following diagram provides an overview of the MHD profile Actors, Transactions and their interactions.
The table below lists the transactions for each actor directly involved in the MHD profile. To claim compliance with MHD, an actor shall support all required transactions (labeled “R”).
Actor | Transaction | Optionality |
|---|
Document Source | Provide Document Bundle [ITI-65] | R |
Document Recipient | Provide Document Bundle [ITI-65] | R |
Document Consumer | Find Document Lists [ITI-66] Find Document References [ITI-67] Retrieve Document [ITI-68] | R R R |
Document Responder | Find Document Lists [ITI-66] Find Document References [ITI-67] Retrieve Document [ITI-68] | R R R |
Transactions
- Provide Document Bundle [ITI-65] – This transaction passes a Provide Document Bundle Request from a Document Source to a Document Recipient. Uses a FHIR POST for a Bundle of DocumentReference and/or Binary resources.
- Find Document Lists [ITI-66] - Used to locate and return metadata for previously stored document submission sets or folders. Uses a FHIR search returning a List of resources.
- Find Document References [ITI-67] - Used to find DocumentReference Resources that satisfy a set of query parameters. Uses a FHIR search that returns a Bundle of DocumentReference resources.
- Retrieve Document [ITI-68] - Used by the Document Consumer to retrieve a document from the Document Responder. Uses a FHIR GET operation returning a single Document.
Sequence Diagram
