Why HIEs could play a key role in accelerating interoperability
The concept of health information exchanges is not new for healthcare. States, regions and other collections of healthcare entities have been attempting to scale up these exchanges for years.
Such efforts clearly predate the major drive into electronic health information that was caused by the Meaningful Use program that has ended up with the vast majority of health systems and physician practices having electronic medical records.
The roots of the recent push to put HIEs into place can be found in the Affordable Care Act, the Meaningful Use program and other initiatives to digitally transform healthcare. As a refresher, an HIE is a dynamic network connecting distinct healthcare systems that enables the transmission of data while maintaining the integrity of the data. The definition of an HIE reveals the idealistic nature of the concept, an idealism that cannot always be matched in actual practice.
Diving further into the purpose of the HIE, it is designed to facilitate the transfer of data between providers. Enabling the easy transfer of data goes to the ongoing hot issue of interoperability. Ensuring data get to where both providers and patients want it is the ongoing challenge and frustration of exchanging data between providers using two different vendors’ information systems.
However, when thinking about whether an HIE will assist in achieving interoperability, it is helpful to remember that various types of HIEs exist. There can be statewide, private, regional, community or other forms. The more public-facing HIEs has faced a number of challenges. Over the past five or so years, a fair number of HIEs launched, oftentimes with the initial benefit of government funding. However, several of the newer HIEs did not last and quickly faded away, which somewhat tarnished the perception of HIEs.
The negative perception is not fair, though. Quickly organized entities that enter a complicated space should not and cannot be expected to be overnight successes. That is why it is more instructive to examine more established, older HIEs for the value that can be added to the system.
Those examples do exist. The Mass HIWay (still in growth), Great Lakes Health Connect and the Utah Health Information Network (UHIN) offer examples of what can be done, although it must be recognized that nothing is perfect or at the ultimate goal. Those HIEs seem to have staying power and do not face immediate jeopardy of closure or failure. Each also offers insight into a beneficial structure, which covers not just the data but getting parties and data into the HIE.
Ultimately, HIEs will need to evolve and truly become integrated into the care delivery system. At least that should be the ultimate goal if an HIE will play a meaningful role in whatever ecosystem it resides. An HIE cannot solely be a connection that is not utilized. Instead, it should be a trusted partner in the environment that helps connect disparate providers and eases the free flow of data. Maintaining optimism can be difficult, but there’s reason for hope with the potential of HIEs.