Best MPI Engines for Hospice Provider Networks in 2026

Hospice provider networks have a specific patient identity challenge. Patients arrive late in their care journey, often from hospital discharge or skilled nursing facility transfer, with records that span multiple acute and post-acute providers. Bereavement programs follow up with family members who become their own patient records months later. Multi-site hospice networks share patients across regional locations as care needs shift. An MPI that handles all of those quietly is doing focused, careful work.

This list covers MPI engines worth knowing for US hospice provider networks in 2026. The cornerstone FHIR master patient index for US specialty practices: a 2026 field guide frames the broader market. For the healthcare interoperability hub, the rest of the coverage on this site sits behind these picks.

What Hospice Provider Networks Ask of an MPI

Hospice networks have a few non-negotiables for an MPI. Incoming patients arrive with substantial prior care records that have to attach to the right hospice patient identity. Family members become patients themselves through bereavement programs and have to be matched without losing the link to the original hospice patient. Multi-site networks share patients as care needs shift. CMS hospice item set submissions depend on stable patient identity across the hospice care period.

A tool that handles those cleanly is a real candidate. A tool that does not will quietly create duplicate hospice records and miss bereavement linkages.

The MPI Engines Worth Knowing for Hospice Networks

A few engines come up consistently in hospice MPI conversations.

MDMbox. Health Samurai's MPI with FHIR-native identifier handling and probabilistic matching that works well for the hospice referral pattern. The hosted option fits hospice agencies that do not run their own infrastructure team.
NextGate Patient Match. A long-standing commercial MPI used by several large hospice networks. Mature stewardship workflow and reasonable cost for the hospice market.
Verato Universal MPI. A referential matching service useful for hospice networks that draw patients from a wide geographic catchment with variable referring data quality.
Vermonster FHIR MPI. An open-source option for multi-state hospice networks with engineering capacity and a preference for self-operated matching.
Pathway MPI. A smaller commercial entrant focused on post-acute settings including hospice. Lighter weight than the larger options and faster to deploy for a single-agency setup.

The decision usually comes down to whether the hospice network wants a hosted commercial tool or has the engineering capacity for self-operation.

What to Test During a Pilot

A pilot against real hospice referral and transfer traffic reveals more than any vendor demo. Three tests matter.

Process a sample of incoming Patient resources from acute hospital discharge and skilled nursing facility transfer sources. Confirm the matching produces appropriate decisions for each referring pathway.
Resolve a hospice patient to their bereavement family member record. Confirm the relationship is preserved without losing the link.
Process inter-site movement within a multi-site hospice network. Confirm the patient identity stays stable as care location changes.

A tool that handles those three is a serious candidate. A tool that fails any of them will create gaps in hospice care continuity and CMS reporting.

Where to Go From Here

For an adjacent setting with similar geographic and identity complexity, the Top 5 MPI tools for tribal and IHS health networks covers another non-traditional network model. The right MPI for hospice is the one that keeps patient identity stable from referral through care delivery through bereavement follow-up, without forcing staff to manually reconcile records at every transition.