Cross-border patient care is one of the harder identity problems in healthcare. A patient with a Scottish CHI number, an English NHS number, a Welsh NHS number, or an Irish PPS number, or several of those at once, has to be recognised as the same individual without the receiving system creating yet another record. Add identifiers from European Health Insurance Cards or US deployments, and the MPI suddenly has to reconcile across data quality patterns from multiple jurisdictions. The solutions below have a credible track record at this kind of cross-border reality in 2026.

For broader context on master patient index selection, related FHIR write-ups is the right entry point to the supporting material.

What Cross-Border Identity Asks of an MPI

Three demands matter most:

• Native handling of multiple national identifier types within a single Patient resource, without forcing one identifier to be the canonical key.
• Matching configurations that can be tuned per jurisdiction, because the demographic data quality patterns differ enough to matter.
• Stewardship workflows that route uncertain matches to staff with the right linguistic and contextual knowledge for the records involved.

A solution that hits all three behaves consistently across jurisdictions. A solution that misses any of them tends to fragment into one match policy per region, which is harder to operate than a single tuned configuration.

The MPI Solutions for Cross-Border Patient Care Worth Shortlisting

1. HAPI FHIR EMPI. HAPI's EMPI module handles multiple identifier types cleanly because the Patient resource supports them as a baseline. The matching configuration can be extended to weight different identifier types differently across jurisdictions. The honest cost is the operational ownership required to keep the per-jurisdiction tuning current.

1. Smile CDR MDM. Smile CDR's commercial MDM module builds on HAPI EMPI with managed operations across jurisdictions. The vendor relationship is useful when the operating culture prefers a single point of accountability for cross-border identity decisions.

1. NextGate MatchMetrix. NextGate's healthcare MPI track record across multiple jurisdictions makes it a credible pick for cross-border deployments. The matching engine handles per-jurisdiction tuning, and the stewardship tooling supports routing by record characteristics.

1. Verato. Verato's referential matching approach is particularly useful in cross-border scenarios where the native demographic data is sparse or inconsistent across jurisdictions. The trade-off is the data residency story for the underlying reference dataset, which needs careful work in any multi-jurisdiction setting.

1. Rhapsody Patient Index. Rhapsody's MPI offering has a long history in international healthcare integration deployments. The fit is strong for cross-border deployments that already use Rhapsody as their integration engine, because the MPI sits naturally alongside the wider integration stack.

Practical Considerations for Cross-Border Identity

Three practical issues tend to come up across cross-border MPI deployments. Data residency for the underlying patient identifiers needs to satisfy each jurisdiction's regulations independently, and the architecture decisions made here are hard to reverse. Consent for cross-border identity reconciliation has to be modelled explicitly, because the legal basis for the reconciliation can vary by record and by use case. And the stewardship operating model needs staff who can read records in multiple languages, because automated matching can only get so far when the input data uses different naming conventions.

A team that addresses these three early avoids a category of expensive rework later. A team that defers them tends to discover them when a regulator or a patient advocacy group raises them.

How to Evaluate the Shortlist

The most useful evaluation is a realistic cross-border match scenario using representative records from each jurisdiction the deployment will cover. The right candidate is the one that handles the realistic match rate, the false-positive rate, and the stewardship volume cleanly across all jurisdictions in the same configuration, not one that requires a separate tuning per region.

For broader strategic context on the MPI choice, the practical guide to master patient index for FHIR in 2026 is the right back-reference. For an adjacent shortlist tuned to federated GP and hospital networks that often share infrastructure with cross-border MPI deployments, the top 6 MPI engines for federated GP and hospital networks is the natural companion read.

Sources

• Patient Matching guidance (Interoperable Digital Identity and Patient Matching IG) - HTML IG, HL7
• NHS Number and the systems used to manage them (foundational) - PDF, CLOSER, 2018
• Approach to record linkage of primary care data from CPRD to other health datasets - Article, PMC, 2019