Few events frighten a hospital board like the thought of a missing newborn, and infant abduction prevention is one of the clearest examples of why access control is a chain and not a single device. Abductions from hospitals are rare. That rarity is the trap. A rare event produces complacency, and complacency is what lets a weak link stay weak for years. Leaders who want to prevent the worst outcome need to understand how the chain is built, where it usually fails, and how to find the failure before someone else does.
I am writing at the leadership level on purpose. The aim here is to help executives ask better questions and fix systems, not to describe how any specific system could be beaten.
Think in links, not in devices
Hospitals often point to a piece of technology when asked how they protect newborns: an infant tagging system, a locked unit, a camera. Each is useful. None is sufficient. Protection comes from several controls working in sequence, so that the failure of one is caught by the next.
A reasonable chain looks like this. Entry to the unit is controlled. Every person who handles an infant is identified and recognized. The infant is physically linked to the correct parent through matching identification. The infant is electronically monitored near exits. Staff are trained to challenge anyone who does not fit. Exits are alarmed and someone responds. Finally, there is a rehearsed response if an infant is reported missing. Remove any one link and you have a gap; remove two and you have a plan that works only if nobody tests it.
Guidance on preventing infant abduction has been developed over many years with national child protection organizations and hospital security professionals, and it is worth reading and comparing against your own program. Your risk management team and counsel can help you align with current recommendations and with requirements in your state.
Where the chain typically breaks
The failures I see described in reviews of these events, and the weak points I look for in programs, tend to cluster in the human links rather than the technical ones. The first is trust assigned too quickly. A person who looks like they belong, wears something that resembles a uniform or scrubs, and speaks with confidence is often treated as staff. Hospitals are full of people in similar clothing, and staff are reluctant to question someone who appears to be a colleague. The control that should catch this is a consistent, visible, hard-to-copy identification standard and a culture in which challenging an unfamiliar face is expected.
The second is a gap between the unit and the exit. An infant tag is only as good as the exit it is paired with. If a door is propped, a reader is bypassed, or an alarm is routinely silenced because it nuisance-alarms, the tag becomes a record instead of a barrier. The third is parents who are not told. New parents are exhausted and trusting. If they are not coached to ask for identification and to hand the infant only to staff they recognize, they are the least protected link in the chain.
The fourth is slow response. Even the best chain will occasionally be tested by an event, and the first minutes decide the outcome. If staff do not know how to declare an alert, if the exits are not covered quickly, or if the call goes to the wrong person, time is lost that cannot be recovered.
Make challenge a normal act
The most valuable control in the newborn unit costs nothing and sits inside every employee: the willingness to ask. Many staff hesitate because they fear embarrassment, or fear being wrong about a colleague. Leaders can remove that hesitation. Say clearly and often that a polite question is never a mistake. Give staff a script, such as asking who someone is, whom they are visiting or relieving, and walking them to the right person. Support those who ask, even when the person turns out to be legitimate.
Identification should help rather than fight this culture. Distinct, current badges for the unit, a consistent look, and a process for retrieving badges from departing staff all make an unfamiliar person easier to notice. Visitor identification should be just as clear, and parents should be taught exactly what the staff badge looks like and what to do when someone they do not recognize asks to take the baby.
Keep the technology honest
Infant tagging systems, door controls, and cameras need routine care. Batteries fail, doors drift out of adjustment, software settings change after an update, and an alarm that sounded yesterday may not sound today. Assign someone to check these systems on a schedule, document the checks, and report the results to a leader. Ask whether alarms that fire during normal workflow, such as a planned transfer, are being handled in a way that does not teach staff to ignore them.
Review the physical layout as well. Every route out of the unit and out of the building deserves attention, including stairwells, service corridors, elevators, and loading areas. Walk them with the unit manager and with facilities, and ask what stands between a person with an infant and the street.
Drill it and test it
This is exactly where the idea behind Until Tested applies. The protection is assumed until you test it, and in a unit this sensitive, you do not want your first real test to be the real event. Run alert drills on a regular schedule, across shifts, including nights and weekends when staffing is thinnest. Time the response. How long until the alert is declared? How long until exits are covered? Did everyone know their role? Did the security team and the unit speak the same language?
Test the controls with leadership approval and appropriate safeguards. Check whether staff challenge unfamiliar persons, whether the exit alarms respond when they should, and whether visitors are identified at the unit door. Do not conduct unannounced tests in a way that could frighten patients or put an infant at risk, and involve clinical leadership in planning. Treat the results as design feedback. A failed drill is a gift, because it finds the weak link in a setting where nothing was lost.
Who should own it
Infant security belongs jointly to the newborn unit leader and the security leader, with an executive sponsor who reviews drill results and system checks. Neither can do it alone. The nurse manager knows the workflow and the culture. Security knows the systems and the response. The executive makes sure the program is funded, tested, and not quietly loosened when staffing is tight.
Because the event is rare, the program will always be tempted to drift. A leader’s job is to keep it from drifting. Ask for the last drill date, the last system check, and the last time someone was coached on challenge. If the answers come quickly, the chain is probably strong. If they do not, you have found your work for this quarter.
Go Deeper
Programs like this one need a leader who will keep asking for evidence. If you want to understand how a fractional security leader approaches it, read What Is a Fractional Security Director? The Complete Guide, and see my book Fractional Security Director for the broader method.
Commissioner William Epps is a former elected Fire Commissioner, federal law-enforcement supervisor, and firefighter since 2006, with instructor credentials in Hazardous Materials response, Active Shooter preparedness, and Stop the Bleed®. He spent seven years in federal law enforcement in physical security, executive protection, and incident command, and now serves organizations as a Fractional Security Director. He is the author of The Spirit of Saul, The Spirit of Pharaoh, and other practical books on security, leadership, and faith, built around one idea: knowledge should be practical enough to use when it matters.
Leave a Reply