ONC survey maps the public-health role of 76 regional exchange organizations
The national brief shows broad public-health connectivity while documenting the operating services and remaining barriers hidden behind a simple connection count.
Editorial figure by Health Interoperability Review. Source context: ASTP/Office of the National Coordinator for Health IT.
Regional exchange remains operating infrastructure
The report corrects market maps that treat national exchange and FHIR APIs as replacements for community infrastructure. State, local, and regional HIOs continue to connect hospitals, ambulatory practices, behavioral-health organizations, long-term care providers, laboratories, and public-health agencies while performing local data-quality and identity work.
That role is not uniform. A directory should distinguish the populations, jurisdictions, data types, reporting programs, and agencies served by each organization, and whether each service is production, pilot, one-way reporting, bidirectional exchange, or analytical support.
The buyer question moves from connection to operating use
An interface inventory can show that an agency is connected while saying little about timeliness, completeness, matching accuracy, acknowledgement handling, exception queues, or the staff effort required to keep data moving. Those measures determine whether connectivity improves surveillance and response.
Health systems and agencies evaluating exchange partners should ask for named use cases, data-quality controls, escalation paths, service boundaries, and observed participation. Public-health interoperability is an ongoing service model, not a one-time interface installation.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Health Interoperability Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.