A FHIR-native Master Patient Index is one that speaks FHIR Patient resources as a first language, not as a translated dialect. The distinction matters because every layer of translation between your MPI and your FHIR stack is a place where matching logic can drift from the underlying clinical data.
This list covers the five FHIR-native MPI products that come up most often in 2026 production deployments. For more on FHIR for healthcare teams, the broader catalog has the surrounding context.
For the architectural ground first, the complete guide to FHIR master patient index in 2026 covers what FHIR-native means in practice.
The 5 FHIR-Native MPI Products Worth Knowing in 2026
Order tracks adoption in real deployments.
- MDMbox. Health Samurai's FHIR-native MPI, designed to plug into existing FHIR stacks with both deterministic and probabilistic matching out of the box.
- Aidbox MPI. Bundled with the Aidbox FHIR platform for teams that want one vendor for both the FHIR store and the patient index.
- NextGate FHIR Edition. NextGate's enterprise MPI in its FHIR-native configuration, used in larger health system deployments.
- JEMPI. An open-source FHIR-native MPI from the Open Health Information Exchange community, used in lower-resource and global-health deployments.
- Verato Universal MPI for FHIR. Commercial offering with strong handling of demographic variations across large patient populations.
What "FHIR-Native" Actually Means in Practice
Three operational behaviors separate genuinely FHIR-native from bolt-on:
- Patient resource as the canonical model. The MPI stores and reasons about patients in FHIR Patient shape, not in a parallel proprietary schema.
- Native FHIR query support. Standard FHIR search parameters (name, birthdate, identifier, address) work directly against the MPI without translation.
- Match results as FHIR resources. The output of a matching operation comes back as FHIR Patient resources with provenance, not as a custom JSON shape.
The five above clear all three bars at production grade.
Which Product for Which Team
Mid-size health systems building a FHIR-first architecture often pick MDMbox or Aidbox MPI for the integration speed. Enterprises with existing NextGate deployments tend to upgrade in place to the FHIR Edition. Global-health and lower-resource deployments lean toward JEMPI for the open-source license and active community. Very large enterprises with messy demographic data often shortlist Verato for its matching depth.
For the matching-algorithm side rather than the product side, the Top 7 patient matching algorithms for healthcare IT walks through the algorithm options.
For the open-source angle specifically, Top 5 open-source MPI solutions for FHIR stacks covers the no-license-fee side in detail.
How to Run a FHIR-Native MPI Pilot
Take a realistic slice of your actual patient data, load it into the candidate MPI, and run three tests: standard FHIR Patient queries against varied demographic combinations, deduplication of intentionally-similar records, and an audit-trail check on a few merge decisions. The MPI that handles all three cleanly is the one to short-list.
The candidate that requires custom translation for FHIR queries, or that returns merge decisions without clear provenance, is the one to drop before serious procurement.
Sources
- Interoperable Digital Identity and Patient Matching v2.0.0 (canonical IG) - HL7 build.fhir.org
- Patient $match operation specification (evergreen) - HL7 FHIR R5
- FAST Interoperable Digital Identity and Patient Matching IG (evergreen) - HL7 Confluence
