Perspectives · Interoperability
The Decoupling
When connection outruns readiness
Lighting up a connection is a settings change. Trusting what flows through it is not.
As TEFCA1 and Care Everywhere2 push connection toward everyone, readiness — safety, trust, quality — isn’t moving with it. The loudest connection numbers and the quietest readiness numbers may belong to the same organizations.
drag, or use ← →
Drag the connection toward one hundred percent, and watch what the second line does. That widening gap — the one that opens exactly as the pipes fill — is the whole subject of this piece.
Readiness is a different animal
Being connected and being ready are not the same capability, and we have spent so long solving the first that we have scarcely named the second.
Connection is a property of the pipe. Readiness is a property of everything downstream of it: whether an out-of-network record can be reconciled against what you already know, whether it reaches the clinician inside the seconds they actually have, whether the person receiving it can act without being buried. None of that turns on with the setting.
And here is what the climbing line hides. More connection, poured into a system that isn’t ready, does not simply fail to help — it can make things worse. A flood of unreconciled records is not more information; it is more noise, more alerts, more to wave away. And dismissal, once it hardens into habit, is indistinguishable from never having been connected at all. Reactivity is what rushes in to fill the space where readiness was supposed to be.
So the honest question was never how many organizations can connect. Nearly all of them soon will. It is how many can safely act on what arrives — and that is a far smaller number, and not one that fits on a slide.
Beneath readiness: trust
There is a second thing the exchange volume does not measure, quieter and more serious than workflow: whether the data moving through the pipe is moving for the reason it is supposed to.
The frameworks assume a purpose — treatment — and the disputes now working through the courts turn on whether that assumption held: records pulled under the banner of care and routed somewhere else entirely.3 Those cases are for the courts to settle. But they make a point no connectivity metric can: readiness is not only operational; it is a matter of governance and trust — whether an organization can stand in the flow without leaking, and whether the people whose records are moving would recognize where they went. Connection without that is not readiness. It is exposure with excellent throughput.
The answer is an input, not an output
The frameworks are among the best things to happen to this field. The flood is not the enemy, and closing the tap on data people need is never the answer.
But the answer does not live in the output the connection produces. It lives in the input. A record that arrives is raw throughput — what turns it into care is everything upstream of the point of arrival: whether the flow is governed for trust, filtered for safety, and held to a standard of quality before it reaches a clinician. Connection is a bet on the output. Readiness is a discipline about the input.
Industry already shows the difference. Where connection is treated as the finish line, the records pile up and reactivity sets in. Where the input side is built — trust, safety, and quality first — the same flood becomes something a clinician can act on with confidence. The distance between those two organizations is not connectivity. It is which end of the pipe they chose to build.
The how is a longer conversation, and not the work of this piece. Naming the gap accurately has to come first — because a field that cannot tell connection from readiness will keep celebrating the one while patients wait on the other.
Connection is arriving for everyone. Readiness is the quieter choice underneath it — and the organizations that treat it as the real work, not the afterthought, are the ones whose connection will ever reach a patient.
Notes
- The Trusted Exchange Framework and Common Agreement (TEFCA) is the national framework established by ASTP/ONC to set a common governance, policy, and technical floor for nationwide health information exchange. See ASTP/ONC, “Trusted Exchange Framework and Common Agreement (TEFCA),” HealthIT.gov.↩
- Care Everywhere is Epic’s record-exchange capability for querying and sharing patient records across organizations, including with non-Epic systems. See Epic, “Care Everywhere.”↩
- On purpose-of-use disputes: a Carequality review found that certain requests had been submitted without a treatment purpose, resulting in sanctions against several participants; separate antitrust litigation between Particle Health and Epic remains ongoing. See Fierce Healthcare’s reporting on the Carequality resolution and on the court’s ruling on the motion to dismiss.↩