What is healthcare interoperability?

Healthcare interoperability is the ability of health IT systems to exchange electronic health information and use it without special effort on the part of the user, as the 21st Century Cures Act defines it. In practice it means records move between EHRs, apps, payers and networks in standard formats and arrive in a form the receiving system can act on.

ONC summarizes the Cures Act definition as the ability to exchange and use electronic health information without special effort on the part of the user, and notes that interoperability does not include information blocking. The information blocking rules split the idea into three parts: access, the means to make EHI available; exchange, the ability to send it between systems, platforms or networks; and use, the ability for EHI to be understood and acted on once received. ASTP has clarified that exchange and use are bidirectional, so blocking an app from writing data back can count as interference too.

The building blocks in the US

  • Data: USCDI names the data classes and elements certified health IT must support.
  • Format and API: FHIR, constrained by US Core and secured with SMART App Launch, for app access; HL7 v2 for much of the event traffic inside hospitals.
  • Networks: TEFCA connects networks nationally through QHINs, alongside health information exchanges, which ONC describes as the confidential electronic exchange of clinical information among authorized organizations.
  • Rules: ONC certification sets what EHRs must support, and the information blocking rules penalize practices that get in the way.

Why it matters

ONC says interoperability helps clinicians deliver safe, effective, patient-centered care and gives individuals new ways to reach their own information. For a buyer, the test of an interoperable product is whether data from a real partner system lands in the right place without someone retyping it. A list of supported standards does not answer that.

Example

A remote monitoring program reads a patient's problem list and medications from the hospital EHR through its FHIR API when the patient enrolls, receives admission and discharge events over an HL7 v2 feed, and writes summary readings back so they appear in the chart. Each link uses a different standard, and all three have to work for the program to run without manual steps. We have shipped Epic and athenahealth integrations.