When a DNA test reveals a switched-at-birth event, the first steps for a hospital are not public relations steps. They are verification, preservation, coordinated disclosure, and legal triage. The harder problem is that the evidence may arrive long after the hospital’s ordinary systems have gone quiet: the unit may be closed, the paper chart may be destroyed under a retention schedule, and the people who managed the nursery may be gone.
That is the unsettled fact pattern in the North Dakota lawsuit filed in 2026. Two men allege they were the only two babies born on the same day at Unity Medical Center in Grafton in 1988 and that DNA testing later showed they had been switched. The hospital’s public response, as reported by ABC News, was that records from 38 years earlier “no longer exist.”[1]
For health systems, that is the administrative asymmetry that matters. A family can now arrive with genetic evidence generated outside the hospital. The hospital may be left trying to explain an event from a paper-era workflow using only what survived ordinary record retention. The resulting exposure is not limited to whether an infant identification failure occurred. It also includes whether the institution can respond credibly when the past becomes testable.
The DNA Test Is Often the First Surveillance Event
Hospitals did not build a national surveillance system for historical infant-switching incidents. Direct-to-consumer DNA testing is now filling part of that role, unevenly and accidentally. The person taking the test may be an adult child, a sibling, or another relative. The first signal may be an unexpected genetic match, a missing expected match, or a family tree that no longer fits.
The latency can be extreme. In the Jamaica Hospital case reported by ABC7 New York in 2025, a switch allegedly dating to 1960 went undetected for 65 years until a sister’s Ancestry.com test revealed the discrepancy; the hospital declined to comment.[2] In the United Kingdom, the BBC reported in 2024 on a 1967 NHS baby switch described as the first documented case in NHS history; the trust admitted liability, while compensation was still unresolved 2.5 years later.[3]
Those cases should not be treated as proof of frequency. They are proof of discoverability. They show that the relevant time horizon is not the newborn discharge process alone. It is the period between birth and genetic detection, which can span decades.
A catalog of documented switched-at-birth cases shows incidents across multiple countries and eras, but it is not a denominator-based surveillance dataset.[4] A commercial testing company, DNA Diagnostics Center, has estimated that up to 18 babies a year may go home with the wrong families, while also noting only eight physically documented incidents between 1995 and 2008 because there is no mandatory reporting system.[5] That combination should make risk teams cautious in both directions: the public number is not methodologically strong enough to use as prevalence, but the absence of reports is not evidence of absence.
Why Old Claims Are Not Automatically Closed
The legal difficulty is not simply that an alleged switch happened long ago. It is that the discovery may also have happened long after the birth, and some courts have been willing to treat the injury as more than a stale medical-error allegation.
The central precedent for hospital defense teams is Larsen v. Banner Health System, decided by the Wyoming Supreme Court in 2003. The case involved women switched at birth in 1942 at a hospital in Douglas, Wyoming, and the court held that the hospital owed a duty in the provision of “deeply emotional services.” The ruling allowed claims for emotional damages to proceed decades after the birth event.[6]
For defense teams, the important point is not that Larsen controls every later case. It does not. It is a Wyoming state precedent, and its usefulness depends on jurisdiction, pleaded claims, limitation rules, discovery doctrines, and the facts of the alleged switch. The point is that a court recognized a hospital duty in a setting where the core harm was relational, identity-based, and emotional rather than a conventional physical injury discovered in the immediate course of care.[6]
That matters when a family arrives with a consumer DNA result. Many medical malpractice limitation periods are measured in short windows, often running from discovery or from when an injury reasonably should have been discovered. But in a switched-at-birth case, “discovery” can be contested. Is it the date a person receives an unexpected DNA match? The date a second test confirms the biological relationship? The date hospital-linked facts make the switch plausible? The available cases do not support a universal answer.
Hospitals should therefore avoid treating age alone as a complete answer. A 38-year-old claim may still require preservation, review, and counsel-directed analysis. A 65-year-old discovery may still create institutional questions even if litigation defenses ultimately prevail. The operational mistake is assuming that a retention schedule and a limitations defense are the same thing. They are not.
This is the same kind of liability boundary problem now visible in other healthcare settings, where older legal categories are being tested by newer evidence streams. ClinicalMind has examined similar pressure points in healthcare liability frameworks and in evolving healthcare regulation. Switched-at-birth claims are different in substance, but similar in posture: external information arrives first, and the healthcare organization must decide how to answer before the legal map is settled.
The First Hospital Response Should Be Built Before the First Call
A hospital receiving a switched-at-birth allegation should not begin by confirming, denying, apologizing, or speculating. The initial response should establish process: who will receive the information, what documentation will be preserved, what the hospital can evaluate, and what it cannot responsibly say yet.
| Response question | Operational purpose |
|---|---|
| What genetic evidence has been provided? | Distinguish a consumer match from a confirmed biological relationship and avoid overreading partial information. |
| What records may still exist? | Preserve birth logs, nursery records, admission data, archived indexes, microfilm, billing records, and policy documents if any survive. |
| Who coordinates the response? | Bring legal, risk management, patient relations, health information management, compliance, and genetic counseling into one controlled workflow. |
| What can be disclosed? | Communicate the review process without making unsupported factual concessions or hiding behind silence. |
| What historical policies matter? | Identify the maternity identification practices, record-retention rules, and unit history in place at the time of the alleged event. |
The verification step is delicate because consumer DNA services are not hospital incident-reporting systems. A result may strongly suggest that a person is not biologically related to expected relatives, but the hospital should still distinguish between the genetic finding and the institutional conclusion. A credible workflow asks for the documents the family is willing to share, records chain-of-receipt, avoids informal interpretation by unqualified staff, and routes genetic questions to professionals who understand both test limitations and family impact.
That does not mean delaying until litigation forces action. It means giving the family a named channel, a realistic timeline for review, and an explanation of what information is being sought. Adults discovering a biological switch are not merely reporting a clerical problem. They may be learning that a parent-child relationship, family medical history, inheritance assumption, or cultural identity has been built on facts no one knew were false.
Preserve More Than the Birth Chart
Record preservation should begin even when the hospital expects little to exist. The North Dakota case shows why. A statement that records “no longer exist” may be accurate under retention policy, but it rarely answers every relevant question.[1] Risk teams should ask what adjacent records remain: board minutes discussing maternity operations, historical policy manuals, nursery staffing schedules, archived delivery logs, old patient indexes, insurance files, medical staff rosters, microfilm inventories, and acquisition records if the facility changed ownership.
The purpose is not to reconstruct the impossible. It is to separate “we no longer have the individual chart” from “we made no disciplined effort to identify surviving evidence.” Those are different positions in litigation, in public communication, and in patient relations.
If the maternity unit closed, merged, or changed names, the record map becomes part of the response. A family should not have to infer from silence whether the hospital searched archives, confirmed destruction dates, reviewed off-site storage, or checked successor-entity obligations. Missing records may be unavoidable. An unexplained gap is a second injury to credibility.
Do Not Let Legal Review Become the Only Voice
Counsel should be involved early, especially because limitation defenses, privilege, preservation duties, and potential admissions all matter. But a legal-only response is usually too narrow. Patient relations needs to manage contact with affected adults and relatives. Health information management needs to explain what records exist and what retention policy applied. Risk management needs to document the event as a claim or potential claim. Compliance may need to evaluate whether any current reporting or governance obligations are implicated. Genetic counselors may be needed to help translate what the DNA evidence does and does not prove.
The response should also account for multiple affected parties. A switched-at-birth allegation does not involve one patient record and one complainant. It may involve two adults, living or deceased parents, siblings, estates, and families with conflicting wishes about disclosure. Some may want immediate confirmation. Others may not want contact. A hospital that treats the first caller as the sole stakeholder can create avoidable privacy, consent, and communication problems.
What to Say When Records Are Missing
The most tempting sentence is also the least useful one: records are no longer available. Sometimes that is the truth. It is not, by itself, a response framework.
A stronger communication separates four points. First, what the hospital has received from the family. Second, what the hospital is doing to evaluate the allegation. Third, what records or archives have been searched. Fourth, what cannot be determined because the relevant records were lawfully destroyed, never created, or cannot be located. The distinction matters because an institution can be transparent about uncertainty without pretending to know more than it does.
Hospitals should also avoid language that minimizes the event because it is old. The age of the event may be central to legal defenses, but it does not reduce the significance of the discovery for the people involved. The better institutional tone is sober and bounded: acknowledge receipt, acknowledge the seriousness, describe the review, identify the limits, and avoid public speculation about fault before the facts are assessed.
There is also a documentation issue inside the hospital. Every contact, search step, decision point, and communication should be recorded. If no individual birth record exists, the response file may become the only coherent account of how the institution handled the allegation. That file should show more than defensive posture. It should show a controlled process.
Modern Identification Controls Help, but They Do Not Resolve Legacy Exposure
Current newborn identification systems are materially different from paper-era practices. Contemporary prevention discussions commonly include electronic ID bands, RFID-enabled matching, alarmed security systems, and EHR-linked workflows intended to reduce mismatches and unauthorized movement.[7] Those controls matter for today’s nursery operations.
They do not answer the question presented by a 1960, 1967, 1988, or earlier alleged switch. A hospital cannot defend a historical claim by describing technology adopted decades later. Nor can the industry safely infer that modern systems have eliminated the risk simply because the workflow now appears highly controlled. Dr. Jonathan Marron of Harvard Medical School’s Center for Bioethics has described contemporary mix-ups as “pretty close to never” because of EHR systems, but that confidence has not been validated against comprehensive DNA-based surveillance data.[8]
The practical implication is to keep prevention and legacy response separate. Review current maternity identification policies, test escalation pathways for near-misses, and maintain staff training. But for historical exposure, focus on records, successor obligations, disclosure governance, and claim response. The technology story is secondary when the family’s evidence concerns a birth event from a different operational era.
How Health Systems Should Review Their Exposure
A system with legacy maternity operations does not need to assume a switched-at-birth incident occurred. It does need to know how it would respond if one were alleged tomorrow. That review can be narrow, practical, and tied to existing risk infrastructure.
- Identify current and former facilities that operated maternity units, including acquired hospitals, closed campuses, and renamed entities.
- Map historical record-retention rules for birth records, nursery logs, delivery registers, and administrative policy documents.
- Create an intake pathway for DNA-triggered switched-at-birth allegations that routes immediately to legal, risk, HIM, patient relations, and genetics expertise.
- Prepare communication language that explains process and uncertainty without denying facts that have not been reviewed.
- Review current newborn identification and discharge matching policies separately from the legacy-claim response plan.
The record-retention review deserves particular care. A policy that authorizes destruction after a defined period may be defensible, but the institution should still be able to show what the policy was, when it applied, which categories of records it covered, and whether any exceptions existed. If a hospital cannot explain its own retention history, the lack of records becomes harder to distinguish from lack of control.
The intake pathway should also prevent staff from improvising. A front-desk employee, call center representative, or patient relations specialist may be the first person to hear the allegation. That person should not be expected to interpret DNA evidence, apologize on behalf of the institution, reject the claim, or promise access to archives. The right first answer is a controlled referral into a prepared process.
The Prevalence Problem Is a Governance Problem
No available source supports a reliable national prevalence estimate for historical switched-at-birth events. The documented cases are real, but they are not a complete count. Commercial estimates exist, but their methods are not strong enough to settle risk. Mandatory reporting is absent, and many discoveries may never become public claims.
That uncertainty should not be comforting. In most hospital risk programs, a low-frequency event can still deserve planning when the severity is high, the disclosure pathway is public, the records are weak, and the institution’s first response may shape the entire claim. Switched-at-birth allegations meet that profile.
Direct-to-consumer DNA testing has become the surveillance mechanism hospitals never built. It is not systematic, not mandatory, and not designed for quality reporting. But it is capable of surfacing evidence that hospital records may no longer be able to confirm or refute.
For healthcare organizations, the first operational failure in 2026 may not be the original switch. It may be the inability to respond credibly when a family arrives with genetic evidence and asks the hospital to account for a birth that its own systems can no longer see.
References
- Men sue hospital after DNA tests showed they were switched at birth, ABC News, 2026.
- 1960 Jamaica Hospital, NY case, ABC7 New York, April 2025.
- 1967 UK NHS case, BBC News, November 2024.
- Babies switched at birth, Wikipedia.
- DNA Diagnostics Center blog, DNA Diagnostics Center.
- Larsen v. Banner Health System, Wyoming Supreme Court, 2003.
- Accutech Security blog, Accutech Security.
- Dr. Jonathan Marron, Harvard Medical School Center for Bioethics.
Comments
Join the discussion with an anonymous comment.