ONC calls QHINs the central connection points within TEFCA. The RCE describes them as highly reliable, secure central nodes that support a network-of-networks approach. Each QHIN signs the Common Agreement and exchanges data with every other QHIN, so an organization connected to one QHIN can reach organizations connected to the others.
How a network becomes a QHIN
Only the RCE designates QHINs. An applicant must be a US entity, complete the application, onboarding and designation process, and sign the Common Agreement; ONC says the process typically takes about 12 months. The RCE's requirements include a network governance body, compliance with the QHIN Technical Framework (including 12 months of prior experience supporting query functionality), and the financial and personnel resources to meet QHIN obligations. Applications are processed on a rolling basis.
The RCE's site lists the designated networks. They include eHealth Exchange, Epic Nexus, CommonWell, Surescripts and the Oracle Health Information Network, among others.
What it means for buyers and builders
Most organizations will never be a QHIN. Hospitals, practices and technology companies connect as participants or subparticipants, either directly with a QHIN or through a network or vendor that is already connected. They sign a framework agreement and are listed in the RCE Directory, which QHINs use to route queries. Your EHR vendor may already be your path in.
For a product team, the QHIN choice affects which exchange purposes you can use, what the onboarding paperwork looks like, and whether the network supports FHIR-based exchange yet. The QHIN Technical Framework rolls FHIR out in stages, so ask a prospective QHIN which stage it supports.
Example
A consumer app that wants to help people gather their records under individual access services signs an agreement with a QHIN or with a provider already connected to one, and queries through that QHIN for records held anywhere on the network.