The Instrument Gap

The last piece ended on a question it did not answer. If readiness is not moving with connection, how would any organization know where it actually stands?

The honest answer is that most cannot. Not because they are careless — because nobody built them an instrument.

The one number that stopped moving

The federal survey that tracks hospital interoperability asks about four things: whether a hospital can send records, receive them, find them, and integrate them. Between 2023 and 2025, three of those four climbed. Finding records jumped ten points. Receiving climbed six. Sending reached nearly every hospital in the country.

Integration moved one point.¹

Sit with that shape for a moment, because it is the decoupling rendered in the government’s own numbers. The activities that describe the pipe all accelerated. The single activity that describes what happens to a record after it arrives — whether the receiving system can absorb it without someone retyping it — stayed where it was.

We are not failing to notice this. It is published, in a public table, updated this year. What we have not done is treat it as the headline.

Even that number is not readiness

Here is the harder part. Integration is the closest thing the national instrument has to a readiness measure, and it still is not one.

The question asks whether the EHR integrates an outside summary of care record without manual entry. It is a yes-or-no question about a capability. It does not ask whether integration happens on the four hundredth record of a Tuesday afternoon, or only on the demonstration. It does not ask whether the integrated record is reconciled against what the organization already knows, or simply appended to it. It does not ask whether a clinician can find the relevant line inside the seconds she has. It does not ask who is accountable when the merge is wrong.

It is also self-reported, typically by the chief information officer — the person best positioned to describe what the system can do, and furthest from what it does at 4 p.m. in a busy department. That distance is not dishonesty. It is a structural property of asking one person at the top of the org chart to characterize the behavior of a system with thousands of daily touchpoints.

Every organization I have worked inside had a version of this gap between the attested capability and the lived workflow. Nobody was lying. The instrument simply was not built to see it.

What an instrument for readiness would have to do

I want to be careful here, because it would be easy to turn this into a product pitch and that is not what this piece is. The mechanics of any particular scoring approach are a longer conversation and not the work of this essay. But the requirements are worth stating plainly, because they are what distinguish a real measure from a maturity poster.

And underneath all four: it has to hold governance and trust as first-class dimensions, not a compliance appendix. A record that arrives correctly, integrates cleanly, and was pulled for a purpose nobody would defend is not a readiness success.

Why the instrument does not exist

The uncomfortable explanation is that connection had a forcing function and readiness does not.

Connection was mandated, funded, certified, and attested. There were rules to comply with and money attached to complying. So we built exquisite infrastructure for counting pipes, and the counting itself pulled the field forward — that part worked, and it is worth saying so.

Readiness has no such apparatus. No rule requires an organization to demonstrate that the flood arriving through its new connections becomes usable care. No certification tests it. No survey line item captures it. And a field measures what it is asked to measure.

This is not an argument for another mandate. It is an argument that the absence of a measure is itself the finding — that we should stop reading the climbing connection numbers as progress reports on a capability nobody is checking.

What changes when you can see it

An organization that can locate itself on a readiness curve can do three things it cannot do now: sequence its investments against the actual constraint rather than the visible one, defend a decision not to light up another connection this quarter, and tell the difference between a data problem and a workflow problem before spending a year solving the wrong one.

That is a smaller claim than transformation. It is also the claim I can defend. Measurement does not fix readiness. It makes readiness arguable — and a thing that can be argued about in a budget meeting is a thing that can move.

Connection is arriving for everyone. The organizations that will convert it into care are the ones willing to look at the number that stopped moving, and to build the instrument nobody required of them.