The Standard

Google Cloud Platform to Work with HL7 FHIR Foundation by Providing the Underlying Cloud Technology for the HL7 FHIR Developer Community

The HL7 FHIR Connectathon Medication Track

At the HL7 FHIR Connectathon 14, held January 14 - 15, 2017 in San Antonio, I participated in the medication track. See my previous post to learn more about how I ended up in the medication track. 

HL7’s Fast Healthcare Interoperability Resources (FHIR®) standard has four key resources related to medication:

• MedicationRequest
• MedicationDispense
• MedicationAdministration
• MedicationStatement

Excitement Filled the Room

It was already 9:23 am. One could argue that on a normal Saturday morning, that's an early start time. 

But I was late. The conference room at the Hyatt Regency San Antonio on the Riverwalk was packed ... and buzzing with excitement over FHIR resources, interoperability and the like: 

I later learned the total number of participants at the HL7 FHIR Connectathon 14 was 200+  (a sharp increase from the 6 who attended the first Connectathon just a few years ago).

It seemed like 20+ round tables, packed close to each other, each with 6 to 10 participants, elbow to elbow.  Some attendees engaged in lively discussion, some furiously wrote code, and some just stared at their screens (most displaying a FHIR resource page) brows creased in concentration.

Where Do I Start? 

Why couldn’t I drag my behind out of bed a little earlier for the opening remarks so I could orient myself better?

Which table should I start from?

In this mild confusion, I walked past each table to see if I could find anyone I knew or a track I was familiar with.

Congratulations to the HL7 Leaders Named to Health Data Management's "20 People to Watch in Healthcare IT in 2017" 

The health IT industry publication Health Data Management released its list of the health leaders they expect to make large contributions to the discussion on HIT and provide guidance on where the industry needs to go in "20 People to Watch in Healthcare IT in 2017."  

Happy Holidays!

From our family to yours, Health Level Seven International wishes you a happy holiday season. 

We would like to take this opportunity to thank our members, business partners and colleagues who have donated their time and expertise to help HL7 achieve its mission to empower global health data interoperability. We cannot continue this important work without the support of the health IT community.

Working Together: Our best option to improve C-CDA® Content

Most people have heard of HL7 Fast Healthcare Interoperability Resources (FHIR®) Connectathon events, as well as IHE North America and European Connectathon events, which focus on testing the interoperability of solutions. But did you know that one of the most important content efforts – improving C-CDA® (Consolidated Clinical Document Architecture) documents – is also underway? At each HL7 C-CDA® Implementation-A-Thon, health IT activists have met to improve C-CDA quality and resolve industry differences that result from varying interpretations of standards and implementation guides.

Efforts to Improve the Content of the C-CDA

Many efforts are underway across the industry to help all of us improve the content of C-CDA documents. For example, the Relevant and Pertinent project and the ONC Site C-CDA Scorecard. For anyone who wants to improve C-CDA content quality, you will make the best use of your time at an HL7 C-CDA Implementation-a-Thon.

These two-day events provide an opportunity for multiple participants (20 – 30) from a diverse cross-section of companies and government agencies (16 – 20) to tackle specific use cases for both content creation and content consumption.

What We’ve Accomplished So Far at the C-CDA Implementation-A-Thons

Through the past three C-CDA Implementation-A-Thons, we have accomplished the following:

• Identified many inconsistencies in how document content has been created and consumed
• Clarified language in implementation guides
• Suggested and actually written material for the upcoming C-CDA R2.1 Companion Guide (see C-CDA R1 Companion Guide here)
• Made best-practice statements on a variety of topics
• Exchanged ideas with ONC about certification, validation and document scoring

At Allscripts, we have products that cross the continuum of care, with the ability to both produce and consume CDA-based documents. I am fortunate to work with the very talented Community Solutions group, which is responsible for the creation and consumption of all CDA-based documents for Allscripts products.

Yet, even with this single, focused approach at Allscripts, we are still faced with a number of interesting choices about data, and the construction and consumption of CDA documents. Participation in the C-CDA Implementation-a-Thon events resulted in us making some useful changes, and feeling confident that these were changes made with an industrial consensus for producing an improved quality of C-CDA.

HL7 on FHIR at HIMSS17 

With its world-class education, ever-expanding exhibition and exceptional networking opportunities, no other event brings the brightest minds in health and IT together like HIMSS17. More than 40,000 health and IT professionals are expected to attend to explore creative solutions to real-world challenges in Orlando, Florida at the Orange County Convention Center. 

HL7 is proud to support this annual event that helps health IT professionals find the right products and solutions for their organizations so that they can continue to transform health and lives through IT.

The Spectrum of Interoperability

In a world of polychromatic nuance, it’s interesting to see how often some individuals try to see things in black and white.  This tendency also seems to apply to healthcare data interoperability, as if any given product, organization or service can be classified as either “interoperable” or not. To me it’s absolutely clear that interoperability is a spectrum, which can only be aspired to as a matter of degree. 

Any given player may be viewed as more or less interoperable, but not wholly interoperable, because we live in such a heterogeneous world, with science and medicine continuously evolving. But no matter how you might personally think of interoperability, we can probably all agree that we still have a long, long way to go before we get there.

This is why we need events like Partners in Interoperability.  To achieve real progress, we must engage major stakeholders to stop and listen for awhile, and roll up their sleeves to make small incremental steps to move along that spectrum from the cold blue reality of the recent past to a warm, FHIR-y future based on improved interoperability. 

Partners in Interoperability October Meeting

The second Partners in Interoperability meeting was held at the Johns Hopkins Mt. Washington Conference Center in Baltimore on Oct. 18-19, an arcadian space conducive to deep thought.  As before, the meeting included a set of opening talks each day followed by breakouts focusing on the particular challenges of using FHIR among three distinct business communities:  Clinicians, Payers and Biopharma. 

Day 1

The meeting opened with a welcome from Dr. Christopher Chute, a long-time thought leader in the world of health data standards.  Dr. Chute evoked the history of the Great Baltimore Fire of 1904, which even predates the last Chicago Cubs championship, and led to the establishment of national standards for fire hose fittings.  The metaphor of a great fire being a pivotal event that burned down the old to create a new and improved place did not go unnoticed by the 60+ attendees at the event.

Next was a fast-paced set of five short insights on what FHIR means to the three represented communities, the health IT industry, and, above all, to the future of interoperability which we all aspire toward. 

The morning concluded with three lively presentations on FHIR’s promise and reality:

• Micky Tripathi gave an update on the Argonaut Project, which is close to completing its implementation guides for using the FHIR API and is already thinking about what to tackle next
• Ricky Bloomfield, MD gave an exciting visual talk on how FHIR is enabling several mobile apps to enhance patient care and interaction at Duke University’s Health System
• Sean Khozin, MD, presented on how the FDA is reinventing itself to capitalize on real world evidence from EHRs as well as multiomics big data sources – portraying several opportunity areas where FHIR can help advance the FDA’s mission.

Day 2

The second morning included recaps  from each of the breakouts, followed by one more set of plenary presentations:

• Avinash Shanbhag of ONC discussed the importance of FHIR to realize the goals of the next phase of Meaningful Use
• Titus Schleyer, PhD, of the Regenstrief Institute painted the vision that health information should flow like water, and demoed a FHIR app that allows patients to collect all their medication data from disparate health IT systems into one unified list
• The legendary Dr. Clem McDonald discussed and demonstrated an intriguing JSON-based forms generation toolset used by the National Library of Medicine that can be used, for example, with the Surgeon General’s Family Health History form.