The Dynamic World of Healthcare Implementation Guides: A Guide to Tracking Changes and Contributing to Improvement

The landscape of healthcare interoperability is in constant flux, driven by the relentless development and refinement of Implementation Guides (IGs). Organizations like IHE and HL7 are at the forefront of this effort, producing and revising IGs at an unprecedented pace. But this isn’t limited to these core bodies; regional IHE and HL7 groups, alongside numerous other entities, are actively shaping the future of healthcare data exchange through their own IG initiatives.

The pursuit of a perfect, all-encompassing IG on the first attempt is a common aspiration. However, it’s a largely unrealistic one. In fact, an IG with only a single version is often a sign that it isn’t being actively used or refined based on real-world feedback. The true path to a robust and valuable IG lies in iterative improvement, fueled by transparency and community engagement.

The Cornerstones of a Successful Implementation Guide

Two key mechanisms are critical to achieving a truly effective Implementation Guide: clear documentation of changes and a readily accessible method for users to submit comments and suggestions. Without these, even the most well-intentioned IG can fall short of its potential.

How to Track Changes in an Implementation Guide

Within IHE, a concerted effort is made to provide a human-readable log of changes with each new version. These summaries typically focus on substantive updates – such as the addition of examples or clarifications – and exclude minor corrections like typos. You can find these change logs prominently displayed on the main page (index.html) of the IG, often within a pink “Note” section.

A comprehensive history of all published versions is also readily available. Look for the “Directory of published versions” link, typically located in a bright yellow box at the top of the main page (index.html). This directory allows you to access each historical version and review the associated change summaries.

For a more granular level of detail, delve into the closed GitHub issues (for IHE) or JIRA tickets (for HL7). Access these through the “Issues” link in the footer of the IG. While navigating issue tracking systems can be complex for the uninitiated, they offer a detailed record of discussions and resolutions that shaped the IG’s evolution.

The most technically detailed change tracking is available through the “QA Report,” accessible from the IG’s footer. Within the QA Report, the “Previous Version Comparison” section provides a computer-generated, line-by-line comparison of different versions, revealing even the smallest technical adjustments.

Submitting Your Feedback: Why Your Input Matters

Standards are living documents, and their utility is directly proportional to the quality of feedback they receive. Don’t hesitate to submit comments, regardless of whether you’ve identified a typo, a point of ambiguity, a disagreement with a peer, or a desired feature. All contributions are welcome.

The most impactful time to provide feedback is during the “Public-Comment” period, when the IG maintainers are actively soliciting and planning to address community input. However, comments are valuable at any stage – even after the IG reaches “Trial-Implementation” or “Final-Text” (normative) status.

There are two primary ways to submit comments directly within the Implementation Guide. The first is to create a GitHub issue (indicated by a red circle). The second is to use the “Propose a change” web form (highlighted by a yellow circle), which is accessible to everyone, regardless of membership status.

Did You Know?: The iterative nature of IGs means that even “Final-Text” versions can be updated to address critical issues or incorporate essential improvements.

As an IG matures and achieves normative status, the frequency of changes should naturally decrease. The intention behind “Final-Text” status is to ensure backward compatibility – that is, new versions won’t break systems relying on previous iterations. However, this status should never discourage you from submitting comments or suggestions.

What role do you see for artificial intelligence in automating the process of identifying and incorporating user feedback into future IG revisions? And how can we better encourage broader participation from healthcare professionals in the IG development process?

Share this article with your colleagues and join the conversation below! Let’s work together to build a more interoperable healthcare future.