The patient identifier is the unit of work that an MPI emits. In a FHIR integration, that identifier flows into the Patient resource's identifier array, gets referenced by every clinical resource downstream, and ultimately decides whether a query returns the right person's data. Picking the right tool for managing patient identifiers in a FHIR stack is therefore one of the higher-leverage decisions in an integration project. The seven tools below cover the production-grade choices in 2026. For broader background, see more on FHIR server architecture.
The master patient index reference guide covers the architectural picture; this list narrows it to identifier-management tools specifically.
The 7 Identifier Tools to Know
- NextGate Enterprise Master Patient Index. The dominant enterprise MPI with strong FHIR identifier emission and a long deployment history.
- Verato Universal MPI. The referential-matching MPI that emits identifiers tied to a national reference dataset, useful for cross-organizational identifier alignment.
- InterSystems HealthShare Patient Index. The MPI inside the InterSystems healthcare stack, with FHIR identifier emission integrated into the broader IRIS for Health platform.
- IBM Master Data Management for Healthcare. The IBM MDM stack producing patient identifiers with strong audit and lineage tracking.
- Aidbox MPI. The Aidbox FHIR-stack MPI, producing patient identifiers inside the same engine that serves the FHIR API.
- OpenEMPI with FHIR adapter. The open-source MPI with a FHIR adapter that exposes identifiers through standard Patient resource endpoints.
- Medplum Patient Matching. The PaaS-style identifier service inside the Medplum platform, fitting cloud-native FHIR applications.
What Identifier Tools Actually Have to Do
Three behaviors separate a strong identifier tool from a weak one in a FHIR context.
The first is clean identifier-system semantics. The FHIR identifier field has a system and a value; the tool has to use a consistent system URI across all identifiers it emits, and downstream consumers have to trust that the URI is stable. Tools that emit identifiers with inconsistent or undocumented system values produce data that downstream systems cannot reliably resolve. The second is cross-reference handling. Real patients carry multiple identifiers: the network MPI identifier, the EHR's MRN, the lab system's accession number, an insurance subscriber ID. A strong tool maintains the cross-references and lets a single query resolve any one identifier to the canonical one. The third is history preservation on identifier changes. When two records are merged, the previous identifiers should not disappear; they should be retained as historical aliases so downstream queries against the old identifiers still resolve.
The top patient matching tools for cross-state health exchanges walkthrough covers the multi-organizational case where identifier emission has to align across participants.
How to Pick
Selection turns on the deployment's FHIR stack and the appetite for managed services. A team running Aidbox picks Aidbox MPI; a team on InterSystems picks HealthShare; a team on Medplum picks the native patient-matching feature; a team that wants enterprise-grade identifier management with vendor support picks NextGate or IBM. A team with strong in-house engineering picks OpenEMPI for full control. A team that needs strong cross-organizational identifier alignment picks Verato for the referential approach.
For the underlying algorithmic question of how matching decisions get made, the top MPI algorithms for duplicate resolution walkthrough covers the algorithmic landscape that drives identifier emission. The right choice tends to be visible in retrospect by what the team stopped thinking about, not by what they advocated for during selection.
Sources
- [PIXm Cross-Reference Query [ITI-83]](https://profiles.ihe.net/ITI/PIXm/ITI-83.html) - Spec, IHE, 2024
- Patient $match - Spec, HL7, 2024
- [PIXm Patient Identity Feed FHIR [ITI-104]](https://profiles.ihe.net/ITI/PIXm/ITI-104.html) - Spec, IHE, 2024