Feature: FHIR Plain-Language Summary support

[JohnMoehrke]

Given that the IG tooling now supports centralized and post-applied plain-language summaries... do we want to use this?
https://github.com/HL7/plain-language

[JohnMoehrke]

Mary, this likely needs to be discussed on the Documentation workgroup.

[JohnMoehrke]

This does NOT require an AI driven summary, but they do include assistance for using AI to generate summary with prompts to get good results.

Simple way to get AI recommended summary:
At your favorite AI (e.g. Gemini, ChatGpt, co-pilot, etc)

Given the IG published at https://profiles.ihe.net/ITI/MHD/index.html

Explain the IG's purpose, country of use (if applicable), and context of use / use cases, and key features / how it works. Avoid explaining what standards are in general.

Write ~200 words in short paragraphs for a general audience.

Use clear, jargon-free language.

Write in third-person perspective.

Maintain an objective, informative tone.

Present information factually.

Highlight any key stakeholder benefits.

Mention how the IG relates to other standards or regulations, if this is direct and relevant. Otherwise omit this.

Avoid promotional language or unverified claims.
```

see next comments for what these tools gave me today

[JohnMoehrke]

Gemini (google)

The MHD Integration Profile, published by Integrating the Healthcare Enterprise (IHE), aims to standardize how healthcare documents are shared between different systems. Its core purpose is to enable the consistent and reliable exchange of health information, such as patient summaries, lab reports, or imaging studies, across disparate healthcare IT systems.  

This profile is designed for global use, not tied to a specific country. It addresses the common challenge of interoperability, where different healthcare organizations and software applications struggle to communicate effectively. The context of use involves scenarios where healthcare providers need to access patient information from systems outside their immediate network, like referrals, consultations, or when patients move between care settings.  

MHD defines a set of transactions and data formats that systems must adhere to for seamless document exchange. Key features include the use of standardized APIs for querying, retrieving, and submitting documents. It specifies how metadata, which describes the document, is structured and transmitted. This allows systems to understand the content and context of the documents they receive.  

By adopting MHD, healthcare organizations can streamline workflows, reduce manual data entry, and improve patient care coordination. Stakeholders benefit from faster access to patient information, reduced administrative burden, and enhanced data security.

[JohnMoehrke]

ChatGpt

The Mobile Access to Health Documents (MHD) Implementation Guide provides a standardized interface for mobile devices to access and share health documents. It is designed to work with devices that have limited resources, like smartphones or tablets, making it ideal for mobile healthcare applications. The guide outlines how these devices can interact with health information systems to retrieve or share documents, using simple protocols such as HTTP and lightweight data formats like JSON.

The MHD profile is particularly beneficial for systems requiring simplified access to health records. It allows healthcare providers and patients to view essential health information, like summaries or document lists, on mobile devices. This improves the flexibility of healthcare delivery, making records more accessible in various settings, including remote or underserved areas.

The profile is widely applicable across health information exchanges (HIEs) and electronic health record (EHR) systems. It also supports the exchange of documents through other standards like XDS and XCA, ensuring interoperability with broader health data infrastructures.

Key stakeholders, such as healthcare providers, patients, and IT developers, benefit from streamlined document access and improved mobile healthcare solutions. The MHD profile supports efficient, secure healthcare delivery, especially in environments with resource constraints.

[JohnMoehrke]

co-pilot (microsoft)

The Mobile Access to Health Documents (MHD) Implementation Guide (IG) provides a standardized interface for sharing health documents. It is designed to simplify the exchange of medical information, particularly in resource-constrained environments like mobile devices. The IG is applicable globally, supporting healthcare systems in various countries.

The guide is tailored for mobile applications, tablets, and embedded devices, enabling them to submit, query, and retrieve health documents efficiently. It is also suitable for larger systems with simple needs, such as displaying the latest medical summaries. By leveraging lightweight technologies like HTTP and JSON, the IG avoids the complexity of traditional protocols, making it accessible for developers and users alike.

Key use cases include health information exchanges (HIEs), electronic health records (EHRs), and personal health records (PHRs). It facilitates seamless integration with existing systems, enhancing interoperability and reducing implementation barriers. Stakeholders, including healthcare providers and patients, benefit from improved access to medical data, fostering better care coordination and decision-making.

The MHD IG aligns with established standards like XDS and XCA, simplifying their metadata concepts for mobile environments. It also integrates with solutions like XDR and XDM, ensuring compatibility and broader adoption. This approach supports a consistent and reusable framework for health document sharing across diverse platforms

[JohnMoehrke]

none of these look to me like drop-in summaries. But they are helpful input to a workgroup editing effort.

[danielberez]

The IHE Mobile Access to Health Documents (MHD) Implementation Guide provides a standardized interface for securely sharing health records across mobile and resource-constrained devices. Designed for global use, it enables healthcare providers, patients, and developers to exchange clinical documents like lab reports or care summaries through apps on smartphones, tablets, or home medical devices¹²³.

Primary use cases include home health monitoring systems transmitting patient data to clinics, hospital kiosks submitting registration documents, and personal health apps retrieving vaccination histories from electronic health records⁴³. The guide simplifies technical requirements by replacing complex protocols like SOAP with lightweight HTTP and JSON formats, allowing developers to focus on healthcare functionality rather than infrastructure¹⁵.

Key features include two core operations: submitting new documents to health information systems and searching/retrieving existing records based on criteria like date or document type¹³. It integrates with established health data exchanges (XDS/XCA) through modern API standards, enabling mobile apps to interact with hospital EHRs or regional health networks without custom interfaces⁵². For constrained environments, MHD maintains essential metadata for document tracking while eliminating non-essential data fields¹⁶.

The guide benefits health organizations by reducing mobile app development costs and supports patients through portable access to medical histories⁴³. Clinicians gain real-time data from remote monitoring devices, while maintaining compatibility with existing clinical infrastructure through IHE’s document-sharing ecosystem⁵². As part of IHE International’s broader interoperability framework, MHD works alongside profiles for patient identification, audit logging, and granular data queries to support comprehensive health information exchange⁷³⁸.

⁂

Footnotes

1. https://profiles.ihe.net/ITI/MHD/index.html ↩ ↩² ↩³ ↩⁴

2. https://build.fhir.org/ig/IHE/ITI.MHD/ ↩ ↩² ↩³

3. https://profiles.ihe.net/ITI/MHD/1334_overview.html ↩ ↩² ↩³ ↩⁴ ↩⁵

4. https://www.mobihealthnews.com/17669/ihe-releases-draft-implementation-guide-for-mobile-access-to-health-data ↩ ↩²

5. https://www.devdays.com/wp-content/uploads/2023/08/230608_GregorioCanal_XDSonFHIR.pdf ↩ ↩² ↩³

6. https://github.com/IHE/ITI.MHD ↩

7. https://www.ihe.net/2020visionbenefits/ ↩

8. https://profiles.ihe.net/ITI/MHD/index.html ↩