Our recent Linkedin poll asked our community what area you think regulators and vendors should focus on to achieve universal interoperability faster.

Most agreed that incentivising and enforcing universal health IT standards is the best way to reliably and securely provide a common language and information exchange framework, with the aim of building longitudinal patient records across care settings. Here, we take stock of the journey so far.

Interoperability in Healthcare: Not a New Challenge

Firstly, this is not a new problem. Technology and information exchange standards often proliferate thanks to the endeavours of smart individuals working independently to solve a collective problem. While the consequences in any industry can occasionally be very dramatic, what’s unique about healthcare specifically is the growing scale and variety of standards, which are adding to the problem.

Breaking Down Data Silos: Why Open APIs and Data Sharing Are Essential

With that in mind, cultivating a culture of data sharing and collaboration is key.

Successful healthcare organizations are those that prioritize open APIs (Application Programming Interfaces) and data-sharing agreements. By breaking down data silos and promoting information sharing, more healthcare providers are ensuring better outcomes by creating connected, efficient, and patient-centred healthcare ecosystems.

Education and Awareness: A Critical Step Toward Universal Health IT Standards

Any successful roadmap to enforcing universal health IT standards must include education and awareness. Regulators and vendors are increasingly providing training, resources and case studies, along with suggested methods for effectively navigating a transition to standardized health IT systems. Two excellent examples of this are:

  • HL7 Australia’s Sparked, an FHIR Accelerator Programme that aims to deliver a core set of FHIR standards for use in Australian healthcare settings.
  • In the US, the Argonaut Project is a private sector initiative to advance industry adoption of modern, open interoperability standards.

Incentivizing Interoperability Compliance Through Policy and Reimbursement.

Policymakers are also increasingly leveraging regulatory frameworks, such as meaningful use requirements or reimbursement incentives, and testing and certification programs, to encourage providers to prioritize interoperability in their IT strategies. In addition, technology vendors are demonstrating compliance with recognized standards, therefore attracting customers who prioritize interoperability and data exchange capabilities.

The Role of Regulation: 21st Century Cures Act, CMS Rules and TEFCA

Although it’s taken a long time for regulation to be put into place, it’s definitely achieved the desired result.

Key frameworks include:

  • The 21st Century Cures Act
  • CMS Interoperability and Prior Authorization Final Rule
  • Trusted Exchange Framework and Common Agreement (TEFCA)
  • Qualified Health Information Networks (QHINs)

These initiatives were created to support secure access, exchange, and use of electronic health information across disparate systems, helping standardize national data exchange protocols.

The Ongoing Problem: Fragmented Solutions and Inconsistent Standards

However there also is a superfluity of products being developed by organizations without a specialised understanding of healthcare concepts and workflows. This contributes to a lack of standardization, inconsistent protocols for data formats and communication interfaces, and security measures. In many cases, even modern platforms created by the same vendor do not necessarily talk to each other, and require architects to manually standardize and contextualize their data at the point of integration. This is a time-consuming and expensive process that is wholly unnecessary, given technologies like Orion Health’s, Amadeus Digital Care Record, or Virtuoso Digital Front Door.

Interoperability With Purpose: Moving Beyond Compliance

But interoperability compliance for compliance’s sake is no use without a drive towards defined outcomes. It’s vital to cultivate a thorough understanding of what an interoperability function needs achieve, who is utilizing it and how, in order to design the most effective system.

Why True Interoperability Must Be Patient-Centred

In the case of healthcare, rather than profit, the primary purpose of interoperability should be to ensure that organizations and vendors can make their data available to whichever specialist may be required to achieve the best possible outcome for a patient. 100% health-focused companies like Orion Health share that purpose. Our organization has always been about making information flow, starting with the early days of our message mapping libraries to enable developers, through to the early adoption of FHIR back in 2012. Many of our products, standards and approaches have evolved because we have always believed that data needs to flow without interruption to deliver a better healthcare experience for all.

Health Data Should Flow as Seamlessly as Financial or Travel Data

We believe it’s more than reasonable for patients, providers and clinicians to expect disparate health IT systems to communicate with each other regardless of vendor or platform.  If money data or travel data can flow seamlessly, health information should flow too.

Read more about interoperability in our latest white paper The Interoperability Hype – can we trust it?

Read the white paper