Care coordination platforms built on a FHIR-native data model put unusual pressure on the MPI underneath. Every Patient resource read, every $match call, every Patient.link relationship has to behave in line with FHIR's specification, not a vendor-specific identity model loosely retrofitted into a FHIR facade. The products below have a credible track record at delivering this kind of FHIR-native identity behaviour for care coordination workloads in 2026.
For broader context on master patient index selection and where FHIR-native care coordination sits within it, more on health data standards is the right entry point to the supporting material.
What FHIR-Native Care Coordination Asks of an MPI
Three demands matter most for these workloads:
- Spec-conformant $match behaviour that produces results care coordination apps can consume without bespoke glue.
- Patient.link relationships that downstream systems can rely on, with predictable behaviour around link type and assurance level.
- Webhooks or subscriptions that notify downstream systems when identity changes, so the coordination view stays current without polling.
A product that hits all three feels like a first-class part of the FHIR stack. A product that misses any of them tends to push the gaps into the care coordination application code, which is exactly the work an MPI was supposed to absorb.
The 7 MPI Products for FHIR-Native Care Coordination Worth Shortlisting
- HAPI FHIR EMPI. HAPI EMPI's tight integration with HAPI's FHIR server gives it the cleanest spec-conformant behaviour of the open-source options. The $match and Patient.link behaviour is by design, not retrofitted.
- Smile CDR MDM. Smile CDR's commercial MDM builds on HAPI EMPI with managed operations and a stewardship interface that scales to care coordination workloads across larger networks.
- Medplum Identity Module. Medplum's bundled platform handles identity as part of the wider FHIR-native stack. The fit is strongest for care coordination platforms built end to end on Medplum, where the identity layer benefits from the platform's overall coherence.
- NextGate MatchMetrix. NextGate's healthcare MPI has matured into a FHIR-conformant product, with $match and Patient.link behaviour suitable for FHIR-native care coordination. The vendor's UK and US healthcare track record makes it a credible pick for larger networks.
- Smile CDR with HAPI. For networks that want HAPI EMPI's open-source baseline with Smile CDR's commercial managed operations, the combined deployment is a common pattern for FHIR-native care coordination at scale.
- Rhapsody Patient Index. Rhapsody's MPI offering has been progressively aligned with FHIR-native consumption patterns, and is a credible pick for networks already running Rhapsody integration components alongside their care coordination platform.
- Verato. Verato's referential matching approach is FHIR-conformant through standard $match calls, and is particularly useful for care coordination workloads that span providers with inconsistent demographic data quality.
Patterns That Work for FHIR-Native Coordination
Three patterns recur in successful FHIR-native care coordination MPI deployments. The MPI is treated as the canonical identity source, with downstream systems reading Patient resources from it rather than maintaining their own identity tables. Care coordination workflows subscribe to identity-change notifications, so the coordination view updates without per-application polling. And stewardship outcomes flow back to the source systems through standard FHIR API calls, so the source providers see the reconciliation work the MPI has done.
A deployment that follows these patterns runs a coherent care coordination stack. A deployment that does not tends to fragment into per-application identity management, which is the failure mode the MPI was supposed to prevent.
How to Evaluate the Shortlist
The most useful evaluation runs a realistic care coordination scenario end to end across each candidate. A patient referred between providers, the receiving care coordination platform reading the canonical Patient resource, a subsequent identity update flowing through the subscription, and the source providers seeing the reconciliation: each step exposes how well the MPI fits the FHIR-native operating model.
For broader strategic context on master patient index selection, the practical guide to master patient index for FHIR in 2026 is the right back-reference. For an adjacent shortlist tuned to Integrated Care System deployments that often run FHIR-native care coordination platforms, the top 5 MPI tools for integrated care networks in 2026 is the natural companion read.
Sources
- MDM Operations reference - HTML docs, HAPI FHIR
- MDM module documentation - HTML docs, Smile CDR
- Patient $match operation reference - HTML docs, Medplum
