Subscribe to the Non-Human & AI Identity Journal

Patient Misidentification

Patient misidentification occurs when the wrong person is matched to a medical record or when one person is split across multiple records. In healthcare, this is an identity integrity failure that can affect safety, billing, and care coordination long after the original error occurs.

Expanded Definition

Patient misidentification is an identity integrity failure in healthcare, not just an administrative typo. It occurs when a record is linked to the wrong person, when one patient is split across multiple charts, or when data from different encounters is merged into a single profile. That distinction matters because the issue can distort medication history, lab results, allergies, consent status, and billing. In practice, the term covers both matching errors at registration and downstream reconciliation failures across EHRs, lab systems, imaging, and claims workflows.

Definitions vary across vendors and health systems, but the operational core is consistent: the right clinical data must be bound to the right patient identity with sufficient confidence and traceability. This is closely aligned with identity assurance thinking in the NIST Cybersecurity Framework 2.0, even though patient identity is not an NHI. The same integrity principle applies: if identity binding is weak, the rest of the workflow inherits the error. The most common misapplication is treating patient misidentification as a front-desk cleanup problem, which occurs when organisations ignore cross-system data merge and split errors after registration.

Examples and Use Cases

Implementing patient identity controls rigorously often introduces workflow friction, requiring organisations to weigh faster intake against the cost of stronger verification and reconciliation.

  • A patient arrives for imaging, but a duplicate chart causes prior allergy data to be missed, creating a safety risk during contrast administration.
  • A laboratory result is attached to the wrong chart after a demographic match error, and the error propagates into discharge planning and follow-up care.
  • A newborn is created under one temporary record and later split into multiple records across inpatient and outpatient systems, complicating immunization tracking.
  • An older chart is merged incorrectly after a name change, and a historical medication list is overwritten by another patient’s prescriptions.
  • After a misrouted referral, staff discover that the identity mismatch started at intake and was preserved by downstream system interfaces. For a broader view of how identity errors emerge in real-world environments, see JetBrains GitHub plugin token exposure, which illustrates how weak identity handling can spread risk across systems.

These use cases show why patient identity management is inseparable from governance, not just records administration. Identity workflows should include duplicate detection, probabilistic matching review, manual exception handling, and auditability for merges and splits. They also benefit from the same lifecycle discipline that security teams apply to secrets and service identities, as reflected in the Ultimate Guide to Non-Human Identities.

Why It Matters in NHI Security

Patient misidentification matters because identity errors do not stay local. They can distort access decisions, impair care coordination, and create long-lived compliance exposure when incorrect data is reused across systems. In NHI security terms, it is a useful analogue for what happens when identity binding, lifecycle control, and visibility break down at scale. NHIMG research shows that only 5.7% of organisations have full visibility into their service accounts, and that same lack of visibility is what makes identity errors difficult to detect before they compound. The lesson carries over to healthcare: if the identity layer is not continuously governed, downstream controls inherit bad context.

The operational risk is not limited to immediate clinical harm. A misidentified patient can trigger false billing, denied claims, broken interoperability, and incorrect audit trails that persist long after the original event. The issue becomes even more serious when records are exchanged between hospitals, labs, and external partners, because each handoff can preserve or amplify the original error. This is why identity integrity belongs in the same governance conversation as access control and Zero Trust, not in a separate administrative silo. Organisations typically encounter the cost only after a wrong treatment, denied claim, or legal dispute exposes the mismatch, at which point patient misidentification becomes operationally unavoidable to address.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-63 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

Framework Control / Reference Relevance
NIST CSF 2.0 PR.AC-1 Identity proofing and access decisions depend on correct binding of person to record.
NIST SP 800-63 IAL2 Assurance concepts help frame how confidently a claimed identity is linked to a record.
NIST Zero Trust (SP 800-207) Zero Trust depends on trustworthy identity context before authorization occurs.

Strengthen identity verification and record matching controls before data is accepted into clinical workflows.