Note there will be yet-another re-write (hopefully just tweaks) this summer after HL7 completes their DSTU2 ballot process. There are a set of gaps identified this winter that we have fixed in the proposed content for DSTU2.
The Mobile Health Documents (MHD) is the result.
- Mobile Access to Health Documents (MHD) - Revised 2015-03-12
The basics are shown here.
The MHD abstract actors are:
- Document Source - the producer and publisher of documents and metadata
- Document Recipient - receives documents and metadata
- Document Consumer - queries for documents metadata, and requests to retrieve documents
- Document Responder - responds to requests for document metadata entries and documents.
The MHD abstract transactions are:
- Provide Document Bundle - This transaction is used to transfer documents and metadata, and is analogous to a Provide and Register Document Set-b transaction.
- Find Document Manifests – This transaction is used to provide parameterized queries that result in a list of Document Manifest resources.
- Find Document References – This transaction is used to provide parameterized queries that result in a list of Document Reference resources.
- Retrieve Document – This transaction is used to get documents.
MHD uses few FHIR Resources:
The MHD Profile enables many deployment models:
As and API to XDS environment
As an API to XCA environment
As a standalone Document Sharing infrastructure
As an API to XDR environment
As a standalone PUSH environmentSimilar to XDR without XDR. Use your imagination that everywhere XDR might be used, the MHD Document Source to Document Recipient could be used.
As an API to the Direct Project HISP
As an API to any document based systemThe backend just needs to have a document concept
As simply a profiled FHIR service
Security and PrivacyAs with any Interoperability API dealing with Healthcare information, Security and Privacy
are important. IHE doesn’t mandate a specific Security or Privacy model, as that would be Policy. But IHE does encourage the use of ATNA, and IUA.This also described on the FHIR Site on the Security page.