Cross-state health information exchanges face the hardest patient-matching problem in healthcare. The same patient can appear with a different address in two states, a different name spelling on a marriage record, and a different phone number after a move. A matching tool that handles cross-state cases has to combine probabilistic scoring with referential data and produce defensible match decisions that the participating organizations can trust. The five tools below come up most consistently in 2026 cross-state HIE deployments. For broader background, see the FHIR integration reference.
The master patient index reference guide covers the architectural picture; this list narrows it to the cross-state HIE scenario.
The 5 Tools That Handle Cross-State Cases
- Verato Universal MPI. The dominant referential-matching tool, built around a national reference data set that catches address-change and name-change cases.
- NextGate Enterprise Master Patient Index. A long-running enterprise MPI with strong probabilistic matching, used by several state-level HIEs.
- IBM Master Data Management for Healthcare. The IBM MDM stack tuned for healthcare patient identity, with strong audit capabilities required in multi-state regulatory environments.
- eHealth Exchange Validated Match Service. A matching service designed specifically for participants in the eHealth Exchange network, with cross-organizational audit alignment.
- LightBeam DataLink. A matching platform aimed at health information exchanges and accountable care organizations, with strong cross-source reconciliation features.
What Cross-State Matching Requires
Three factors are weighted more heavily in cross-state HIE work than in single-organization MPI deployments.
The first is handling of address-change cases. A patient moves from Pennsylvania to Texas, gets a new address, a new phone number, and updates their record at the Texas clinic. The MPI has to recognize the new record as the same person despite the demographic shift. Pure probabilistic matching against demographics alone misses these cases at unacceptable rates; referential matching against a national reference set catches them. The second is inter-organizational audit alignment. Match decisions in a multi-state HIE get reviewed by compliance staff from multiple member organizations. A matching tool that produces audit logs the member organizations can understand consistently is the tool the HIE actually wants. The third is performance at HIE scale. State-level HIEs process millions of patient records; matching latency that is acceptable for a single hospital becomes unworkable at HIE scale.
The top patient identifier tools for FHIR integration walkthrough covers the adjacent question of how matched patient identifiers flow into FHIR-based downstream consumers.
How HIEs Should Approach Selection
Selection turns on the HIE's appetite for referential data and the existing vendor footprint. An HIE that values catch rate on address-change cases above all else picks Verato for the referential approach. An HIE that needs enterprise-grade audit and is part of an IBM MDM footprint picks IBM. An HIE that wants a probabilistic match engine without referential dependencies picks NextGate. An HIE inside the eHealth Exchange ecosystem picks the network's validated match service for alignment with the rest of the network.
For the broader question of MPI product selection in HIE contexts specifically, the best MPI products for health information exchanges walkthrough covers the patterns that scale across multi-organizational deployments. A working layer in this part of the stack is mostly invisible; if the team is still discussing it weekly a year later, the layer is doing too much. A reasonable test is whether the team can describe the layer in one sentence to a new hire and have them be productive within a week; layers that resist that test are usually doing too much.
Sources
- Real-world referential vs probabilistic patient matching - JAMIA, Oxford Academic, 2022
- Patient Matching within a HIE - PMC, AHRQ, 2015
- ISA Patient Identification Standards - Web, ONC/HealthIT, 2025