Accountable Care Organization patient attribution sits on a master patient index whether the ACO has built one explicitly or not. Every quality measure rate, every shared savings calculation, every care management cohort definition, and every quarterly report to CMS leans on the answer to the question of which beneficiaries the ACO is responsible for and which of their care events count toward the population. A weak MPI quietly under-reports the population. A strong one keeps the attribution defensible.
This list covers six MPI tools that have a defensible story for ACO patient attribution in 2026. For FHIR background reading, the homepage covers the broader MPI landscape.
What ACO Attribution Asks of an MPI
ACO attribution is a structurally awkward MPI workload. The beneficiary identification has to align with CMS's attribution methodology, which is itself updated periodically. The data inputs include claims, supplemental EHR feeds from participating providers, and Medicare beneficiary files, each with different identifier conventions. And the audit posture is significant because shared savings disputes turn on the attribution decisions.
For the broader picture, the master patient index buyer's guide is the right primer.
The 6 Tools to Know
NextGate's enterprise MPI is the long-running pick for ACOs of meaningful size. The matching engine handles the claims-plus-EHR workload that ACO attribution requires, and the audit trail is defensible against CMS reconciliation. Trade-off: enterprise procurement timeline.
Verato's referential matching helps ACO attribution specifically because the reference identity database can anchor records that fall through deterministic matching. For ACOs with diverse data sources, the referential edge lifts recall noticeably.
Smile Digital Health's MPI fits ACOs investing in a unified FHIR platform. The product handles ACO attribution as part of the wider FHIR stack, which reduces pipeline work for the central team. Cost is the trade-off.
LexisNexis Health Care's patient identity service is well-fit to ACO attribution because the external demographic depth helps with the longitudinal beneficiary view that attribution requires. The data licensing terms have to be settled and have to fit the ACO's BAA posture.
OpenEMPI is the open-source pick for ACOs with central engineering capacity. The matching engine handles ACO attribution workloads with appropriate algorithm tuning, the licensing cost is zero, and the audit trail is defensible. Operational footprint is real.
JEMPI rounds out the list as the lighter-weight open-source MPI. The deployment story is easier than OpenEMPI, the matching engine handles ACO attribution workloads with appropriate tuning, and the operational footprint is acceptable for an ACO with thin IT capacity.
What to Test Against an ACO Attribution Workflow
A few targeted tests will tell you whether an MPI tool holds up.
- Run the matching engine against a sample of one hundred thousand beneficiaries including claims and EHR feeds, and verify the recall and precision against a hand-validated reference.
- Walk through the current CMS attribution methodology against the engine's output and verify the attribution decisions are defensible.
- Add a beneficiary with a name change after a marriage and verify the matching links the records correctly across the change.
- Pull the audit log for the test traffic and verify the chain of custody is intact for each match decision the attribution depends on.
Tools that pass those four are tools that will hold up under ACO attribution workload. Tools that fail any of them produce shared savings disputes that the ACO has to defend without a clean record.
How to Pick
For enterprise-grade ACO attribution, NextGate, Verato, and LexisNexis are the strongest commercial picks, each with a different sourcing model. Smile fits ACOs investing in a unified FHIR platform. OpenEMPI and JEMPI fit ACOs with engineering capacity that prefer to own the engine.
The natural companion read is the Top 5 MPI solutions for Medicare Advantage plans in 2026, which covers a related risk-bearing US workflow.
Sources
- Interoperable Digital Identity and Patient Matching v2.0.0 - HTML IG, HL7 FHIR FAST Identity team, 2025
- Patient Access API FAQ - HTML reference, CMS, 2025
- ONC Patient Demographic Data Quality Framework release - HTML article, Healthcare Innovation, December 2024