Healthcare · Maternity & infant protection

Everyone agrees on this one. That’s exactly why it goes untested.

Maternity is the one area where security and the clinical goal fully agree — nobody wants the infant to leave the unit, so nothing on the floor ever argues with the system. And because nothing argues with it, nothing tests it. It’s been quiet for years, and quiet is the only evidence you have.

Print the walk-the-unit checklist →Why quiet isn’t evidence

The inversion

Everywhere else in a hospital, the security control and the daily work argue with each other — a nurse props a door, a clinician overrides an alarm, a policy carves out an exception. That friction is annoying, and it is also information: it tells you where the system and the work collide, and it keeps the system honest.

Maternity has far less of it. The control and the clinical goal point the same way, so nothing pushes back, so nothing reports on the system, so nothing surfaces its decay. It was installed once, correctly, and it has been silent since. A system that is working and a system that quietly stopped working look identical from your desk — and with no friction to tell them apart, maternity is one of the likeliest systems in the building to be quietly broken.

The recurring pattern

The gap isn’t the door. It’s the identity, and the route.

The National Center for Missing & Exploited Children documents a consistent set of characteristics in healthcare infant abductions:

advance observation of the unit • staff impersonation • deception • departure by a fire stairwell.

Read the list and the perimeter assumption everyone brings inverts. The approach doesn’t defeat the protected door; it arrives as a trusted identity and leaves by the door nobody counts as a door. The most expensive protected opening cannot compensate for a convincing false identity — the attack is social, and only the perimeter is technical. Which means the room-and-door layer is necessary, and it is not where the real work is.

The route, not the room: labor & delivery can be protected and postpartum can be protected while the trip between them is the unprotected part of the system — and the fire stairwell, which is on NCMEC’s own list, is often outside the tag system entirely.

What we build

The layer underneath the protocol.

—Tagging & matching — the band, the tag, the match, the alarm — the layer that has to be right, and rarely the layer that fails.

—Nuisance alarms and the trust they cost — water can interrupt tag-to-skin contact during a bath and trip a nuisance alarm; repeated nuisance alarms teach staff to discount the system, and the usual accommodation is more staff work, not less.

—The route, not just the rooms — coverage across the trip between L&D and postpartum, not only the two protected ends.

—Egress — including the fire stairwell — exits, elevators, and the stairwell that is on the authorities’ own list and is the door nobody thinks of as a door.

—Fail-independent door behavior — what the door actually does when the network is down — a known answer, not an assumption.

—A record complete enough to survive a review — the event history that a root-cause analysis would ask for, retrievable as one account.

The physical layer we own

Your protocol does more work than any perimeter we install.

Nearly six in ten infant abductions from hospitals happened in the mother’s room, and in most of them the abductor was dressed as staff. That means how your team verifies who is carrying an infant — and how consistently — is doing more to prevent this than any door we could install.

Ours is the layer underneath it: what the room knows, what the door does when the network drops, the coverage across the route, and a record complete enough to survive a review. And because these events are rare enough that you will never learn from your own outcomes, the only way to know the layer works is to test it deliberately — which is the one thing four quiet years has never asked anyone to do.

What a look turns up

Nothing dramatic — just the things nobody had a reason to check.

Illustrative · replaced with your verified findings at onboarding

Director of Security · an illustrative women’s & children’s unit

“Everything passed. It always had. Then someone asked when we’d last actually tested it, and the honest answer was the day it was installed, six years earlier.”

What a walkthrough surfaced — calmly, on a normal day: the fire stairwell was alarmed but not in the tag system, the trip between L&D and postpartum crossed an uncovered corridor, and staff had quietly started checking tags by hand because nuisance alarms had worn down their trust.

The result — illustrative: each was straightforward to remediate once identified; none needed an incident to reveal it. The verification protocol stayed with clinical leadership.

Walk-the-unit findings

stairwell: alarmed, not tagged
route L&D→postpartum: gap
last deliberate test: commissioning

[ your real findings appear here ]

Illustrative example — not a real client and not a guarantee. On a live deployment this shows a named facility’s actual walkthrough findings.

Start here

Go find out what quiet means.

The instrument

Print it, walk to the unit, and break the silence

A one-page checklist you carry onto the floor: the fire stairwell, the route, the nuisance-alarm question, and when the system was last deliberately tested. It stages nothing; it just makes you look.

Open the checklist → The depth

It’s been quiet for four years. That’s not evidence.

Why a system nobody tests isn’t a system — the argument you already make to your own clients, turned on your own maternity floor.

Read the article →

Talk to a specialist — book the walkthrough →