The Interoperability Problem

Value-based care runs on data flowing to where it is needed, and health data famously does not flow. A patient’s record is scattered across systems that were never designed to talk to each other, and stitching it together is one of the central technical problems of the field. This lesson defines the problem before the next lessons address it.

What interoperability means

Interoperability is the ability of one organization’s systems to find, send, receive, and actually use another’s patient data. The last verb is the hard one:

Worth remembering: the four levels are find, send, receive, and use, and use is where most efforts stall. It is one thing to transmit a document from one system to another; it is another for the receiving system to parse it, integrate it into the record, and make it actionable. Records that arrive as a PDF no one can compute on, or a document that cannot be reconciled into the chart, are closer to noise than information. True interoperability is measured at the point of use, not transmission.

Why it is so hard

Several forces keep health data siloed:

• Technical fragmentation. Thousands of systems, many formats, and inconsistent implementation of even shared standards.
• Different vocabularies. The same clinical fact recorded with different codes in different systems, requiring mapping.
• Organizational boundaries. Each organization holds its own data, and historically had little incentive, and sometimes a disincentive, to share it.
• Privacy and trust. Legitimate concerns about who may access what, which the exchange frameworks have to resolve.

Why value-based care makes it urgent

Interoperability was a nagging problem in fee-for-service and is an existential one in value-based care. When an organization is accountable for a patient’s total cost of care across every setting, it needs the data from every setting. The walls problem from Module 1, the EHR that sees only its own care, becomes a direct barrier to managing the population. Value-based care cannot be done well on fragmented data, which is why the standards and rules in the next lessons matter so much to anyone building the analytics.

The honest state of play

Interoperability has improved substantially, standards have matured, exchange networks have grown, and federal rules now require data sharing. But the field’s own research, including work this institute has published, finds that data increasingly flows and yet often goes unused, because the last level, integration into workflow, remains hard. Progress is real and incomplete at the same time, a theme the rest of this course keeps in view.

Key takeaways

• Interoperability is the ability to find, send, receive, and use data; use is the level where most efforts fall short.
• It is hard because of technical fragmentation, differing vocabularies, organizational boundaries, and privacy concerns.
• Value-based care makes it urgent: accountability for total cost of care requires data from every setting, so fragmented data undermines the whole model.