HEALTH INTEROPERABILITYREVIEW

Move data. Preserve meaning. Prove the exchange.

Coverage desk

TEFCA Network Evidence

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

RCE QHIN lists need designation-and-route timestamps

The Recognized Coordinating Entity distinguishes organizations that completed QHIN onboarding and are designated for TEFCA exchange from candidates still onboarding, and says the rolling list can change. A roster snapshot does not establish the route, relationship, exchange purpose, production status, or time that governed a particular transaction.

Medication history is not an active-medication list

Surescripts presents medication-history, e-prescribing, formulary, benefit, and prior-authorization services as distinct parts of its health-information network. A returned history should remain source evidence until a clinician reconciles patient match, prescriptions, fills, cancellations, reversals, timing, adherence uncertainty, and current intent into an active list.

Datavant's tokenized-record count is not unique-patient reach

Datavant's official site reports one trillion records tokenized annually. That is a provider-reported processing-volume measure, not by itself a count of unique people, longitudinal coverage, usable matches, authorized exchanges, or records delivered for a defined care, payment, research, or operational purpose.

TEFCA exchange needs agreement-and-SOP version pairing

The Recognized Coordinating Entity describes the TEFCA Common Agreement as a contract supported by technical infrastructure, governance, and standard operating procedures, with Version 2 adding FHIR-based exchange. Each production exchange still needs the exact agreement, SOP, technical framework, role, purpose, and implementation version that governed it.

An eHealth Exchange query needs permitted-purpose and responder-scope evidence

eHealth Exchange operates a nationwide health-information network and is a Designated QHIN under TEFCA, with official materials describing query, document exchange, public-health, federal, and other services. A successful query can prove that a request traveled and produced a response, but it does not by itself establish that the purpose, patient match, responders, data classes, and resulting use were appropriate and complete.

A Bamboo Health event alert needs a separate care-action record

Bamboo Health describes real-time notifications when patients experience care events, alongside patient-history, discharge, and transition products. The alert can create timely awareness, but it does not show that the right person received it, assessed its meaning, acted, reached the patient, or completed a safe transition.

CommonWell pairs a master person index with record location—but retrieval is not identity proof

CommonWell's official site presents a nationwide exchange platform with a Master Person Index, Record Locator Service, Data Broker, and Trust Network. Those services can support discovery and retrieval across connected organizations, but a returned document does not by itself prove that every identity attribute is correct, the record belongs to the intended person, or the data is fit for a clinical decision.

TEFCA entry can run through a QHIN, Participant, or Subparticipant

The Recognized Coordinating Entity describes a network-of-networks hierarchy in which organizations may connect directly to a QHIN or use a Participant or Subparticipant path, with contracts and roles preserved at each layer.