US health systems shopping for a FHIR-native MPI in 2026 have more credible options than they did two years ago, and the bar for what counts as FHIR-native has moved up. The product has to expose patient match through a FHIR API, integrate with US identity workflows, and stay accurate under real patient volume. These five products are the ones US health system procurement teams keep evaluating.
The cornerstone Complete US FHIR Master Patient Index Buyer's Guide for 2026 sets the broader frame. For the FHIR news index, the broader desk runs alongside.
NextGate EMPI
NextGate is the most common US enterprise MPI pick at the larger health system end of the market. The product has a deep matching engine, strong support for US identifier patterns, and a track record in multi-state IDN deployments. FHIR API coverage has grown over the past two years and now meets the bar most US health systems set for FHIR-native procurement.
Verato Universal MDM
Verato's Universal MDM is a US-focused identity platform that has won procurements where matching accuracy is the headline requirement. The product uses a referential matching approach against a US reference dataset, and the accuracy claims hold up under independent review more often than vendors usually manage. For US health systems where matching quality is the procurement-driving question, Verato is on most shortlists.
Smile Digital Health MPI
Smile Digital Health has built MPI capability on top of its broader FHIR platform. The fit is best for US health systems already running a Smile FHIR stack. The matching engine is credible, the FHIR API surface is clean, and the operational model matches the rest of the Smile platform. For health systems that want one vendor across FHIR and identity, this is the natural pick.
Open-Source FHIR-Native MPI Stacks
Several open-source projects in the broader FHIR ecosystem provide FHIR-native MPI capability that is credible for US deployments. The pattern is usually a FHIR server plus a matching engine plus a UI for human resolvers. For US health systems with strong identity engineering benches and a preference for open-source stacks, this route is viable, though it carries the full operational load.
Custom FHIR Match on a Commercial Engine
A handful of US health systems run a custom FHIR API layer on top of a commercial identity engine like an existing EMPI deployment. The pattern preserves the operational maturity of the commercial engine while exposing a FHIR-native interface to downstream applications. For US health systems with a substantial sunk-cost MPI deployment, this is often the path forward into FHIR-aligned workflows without ripping out the engine.
Picking a FHIR-Native MPI for a US Health System
The shortlist for most US health systems comes down to four questions. Does the system need referential matching accuracy first? Then Verato. Does the system need broad US enterprise depth? Then NextGate. Does the system want one vendor across the FHIR stack and the MPI? Then Smile Digital Health. Does the system prefer open source and have the engineering bench to support it? Then an open-source FHIR-native stack fits, optionally wrapped around an existing identity engine.
The Top 7 patient matching algorithms for US healthcare IT is the right next read if matching algorithm depth is the deciding factor for the procurement. The right FHIR-native MPI for a US health system is the one the team can keep tuned, audited, and current under real patient volume for years.
Sources
- Patient $match operation definition - Spec page, HL7 FHIR build, 2026 v6.0.0-ballot4
- Interoperable Digital Identity and Patient Matching IG - IG page, HL7, 2025 v2.0.0
- Patient Matching profile reference in Identity Matching IG - IG page section, HL7, 2025 v2.0.0