Newborn identity is the hardest patient matching case in a US hospital, and it has been for as long as the modern MPI has existed. The shared birth date and shared address with siblings, the placeholder names that get used in the first 48 hours, the twin births that get duplicated when staff capture both as "Baby A" and "Baby B" in different systems, and the inevitable corrections to the legal name once the parents file the paperwork all stack into the same record reconciliation problem. The matching tool a US hospital picks for newborn identity is going to determine whether the unit spends its time on care or on data cleanup.
This list covers six patient matching tools that have a defensible story for newborn identity in US hospitals in 2026. For FHIR background reading, the homepage covers the broader MPI landscape.
What Newborn Identity Adds to the Job
Newborn matching is structurally different in three ways. The demographic inputs are shared with siblings and parents, so naive matching algorithms over-merge. The name is provisional for at least the first day of life, so matching has to handle name changes gracefully without producing a record split. And the volume of corrections in the first week of life is high, so the audit trail has to absorb the corrections without losing the link history.
For the broader picture of what an MPI has to do, the master patient index buyer's guide is the right primer.
The 6 Tools to Know
NextGate's enterprise MPI handles the newborn case better than most because the matching engine has been tuned against twin-birth scenarios for over a decade. The operational story holds up at hospital scale and the audit trail is defensible.
Verato's referential matching helps the newborn case because the reference identity database often picks up on the parent demographic match in ways that anchor the newborn record correctly. The trade-off is the data residency conversation.
Mirth Match handles the standard matching workloads and pairs well with hospital integration stacks that already run Mirth. The newborn case works, with the limitation that the matching algorithm is closer to deterministic than probabilistic.
Smile Digital Health's MPI handles the newborn case as part of the wider FHIR platform integration. The strength is the clean FHIR Patient resource handling. The trade-off is recurring cost.
OpenEMPI is the open-source pick. The matching engine handles the newborn case with appropriate algorithm tuning, the licensing cost is zero, and the audit trail is defensible. The trade-off is the engineering capacity needed to run it.
JEMPI is a more recent open-source MPI focused on patient matching at scale, with a clean operational story for hospital deployments. The product handles the newborn case with appropriate tuning and the deployment story is lighter than OpenEMPI.
What to Test for Newborn Identity
A few targeted tests will tell you whether a matching tool survives the newborn case.
- Generate a sample of one thousand newborn records including twin births, sibling pairs born within twelve months, and intentional name corrections at 48 hours and 30 days, and verify the matching handles each without over-merging.
- Walk through a name correction at 30 days and confirm the audit trail preserves the link history from the placeholder name to the legal name.
- Add a record where the mother's address changed between the prenatal record and the delivery record, and confirm the matching links the newborn correctly.
- Verify that a manually flagged twin-birth pair stays unlinked after a system-wide re-match, since over-merging twins is the most common newborn failure mode.
Tools that pass those four survive newborn identity work. Tools that fail any of them produce record reconciliation work that compounds.
How to Pick
For enterprise-grade hospital deployments, NextGate and Verato are the strongest picks. Mirth Match fits hospitals already running Mirth. Smile fits hospitals invested in the wider FHIR platform. OpenEMPI and JEMPI are the open-source picks depending on engineering capacity. The natural next read is the Top 6 MPI tools for ACO patient attribution in 2026.
Sources
- IIS Patient-Level De-duplication Best Practices Report - PDF, CDC IIS, February 2025
- Patient Identity and Patient Record Matching - HTML reference, ONC, 2025
- Successful Patient Matching without a Unique ID - PDF, The Sequoia Project, 2018 (foundational)