Master patient index (MPI): meaning, matching, and Meddle
A master patient index (MPI) is a registry that assigns one persistent identifier to each person and links every record about them across systems in a health organisation. In plain terms, it answers: “Is this the same patient we have seen before?” without creating duplicate charts for minor name or address differences.
An MPI is about identity and record linkage inside (or across) facilities. Patient matching on a platform like Meddle is a different problem: helping a person find a suitable practitioner and book care once their identity is already known to the systems you control. Meddle does not replace an MPI, an enterprise master person index, or your PMS record of care.
How MPI matching works
Common approaches include deterministic rules on exact identifiers, probabilistic scoring across name, date of birth, and address, and human review of “possible match” queues. Poor registration data at intake undermines every method.
IHIs, governance, and Australian context
Individual Healthcare Identifiers strengthen national identity, but local MPI governance still matters for duplicates and overlays. Assign clinical and privacy owners, monitor duplicate rates, and pilot threshold changes before automating merges.
Where Meddle sits in the stack
Referral platforms and booking tools assume the patient is already uniquely identified in your PMS or hospital PAS. Meddle focuses on describing needs, matching to practitioners, and booking. If your MPI project uncovered referral delays rather than duplicate records, pair identity work with clinic coordination features and referral partnerships.
FAQ
Is an MPI the same as an EMPI?
An enterprise master person index spans a network of sites; a traditional MPI may serve one facility. Vendors use terms interchangeably, so read scope carefully.
Does Meddle store the master identifier?
Confirm data flows during onboarding. Treat your PMS or PAS MPI as the authoritative identity layer unless your architecture states otherwise.