Hospice and palliative care identity linking has a specific operational signature. Patients arrive with rich prior records from the referring oncology, cardiology, or geriatric service. Family caregivers, hospice nurses, and the hospital discharge planner all reference the same patient through different identifiers. An MPI feeding a hospice or palliative care program has to consolidate these into a single identity and persist it through the end-of-life transition. The six MPIs below have shown up in real hospice and palliative care deployments in 2026. For the FHIR engineering reference, the broader reference covers the related architecture.
The Six MPIs Running in Hospice and Palliative Care Production
- NextGate Patient Identity. Used by several large hospice networks because of strong probabilistic matching on patients arriving from multiple referring services with overlapping but inconsistent identifier sets.
- Verato Universal MDM. Referential matching reduces the duplicate-record creation that happens when a hospice intake from one hospital looks similar to a previous palliative-care consult at a different one.
- Rhapsody EMPI. Used by hospice programs already running Rhapsody for the HL7 v2 to FHIR integration with referring hospitals. Hybrid matching suits the mix of richly-known oncology referrals and minimally-known home-based palliative referrals.
- InterSystems IRIS Patient Index. Enterprise stack, suits hospice programs that are part of an integrated delivery network using IRIS as the broader data fabric.
- JEMPI. Open-source. Adopted by smaller community hospice programs that need MPI capability with no commercial license. Requires local engineering capacity to run reliably.
- IBM Initiate. Long-running enterprise MPI. Used by large hospice chains that operate across multiple states and need consistent identity resolution across geographies.
The six cover the realistic FHIR-aligned options for hospice and palliative care programs in 2026.
Three Workflow Patterns to Stress-Test
A hospice or palliative care program evaluating an MPI should put three patterns through a pilot. Referral-record consolidation: patients arrive with records from multiple prior services, and the MPI should consolidate these into a single identity at intake. Family-proxy modeling: the healthcare proxy or power-of-attorney has to live alongside the patient's record without becoming a candidate match for a future patient. Cross-program linkage: a patient who shifts from palliative consultation to hospice within the same network should retain the same MPI identity across the transition.
A two-month pilot against real intake volume surfaces most issues. The long-term care cornerstone covers the broader selection framework, and the birth registry walkthrough covers identity resolution at the opposite end of the life-span continuum.
Why Hospice and Palliative Care Fit Differs
Hospice and palliative care programs work with patients at a transition where records arrive in bulk and where the family caregiver becomes a critical data-source. The MPI has to consolidate the incoming records and model the proxy-relationship cleanly. All six tools above clear that bar in 2026 hospice deployments, which is the practical reason they made the list ahead of other technically capable but hospice-untested MPI products.
Hospice and palliative-care programs that pilot an MPI against real intake volume surface the operational realities within a quarter. The referral-record consolidation, the family-proxy modeling, and the cross-program linkage together separate the MPIs ready for end-of-life identity workloads from those that handle general identity well and stumble on the hospice-specific patterns.
Beyond the six engines above, hospice-specific software vendors are starting to ship MPI capabilities tuned for the end-of-life workflow. Those tighter integrations can simplify the operator burden for smaller hospice agencies that do not want to run a dedicated MPI deployment.
The six engines above are the practical shortlist that hospice IT teams in 2026 reach for when their existing MPI proves insufficient or when launching a new hospice program from scratch. The decision usually comes down to whether vendor support or open-source flexibility carries more weight.
