Every hospital executive I talk to believes the building has badge access control. Most of them are right about the hardware and wrong about the outcome. Hospital badge access fails not because the readers are weak, but because the people the system serves are doing something more urgent than obeying it. A nurse pushing a patient on a stretcher is not going to stop and swipe. A transporter with both hands full is not going to dig for a card. The door gets held, kicked, wedged, or ignored, and the security system records a clean result that never happened.
I want to explain why this keeps happening, why more technology rarely fixes it, and what a leader can do that actually changes the result.
Clinical urgency will always beat policy
A hospital is a place where the right decision is often the fast one. Staff are trained from their first day to put the patient first, and they should be. When a security rule collides with a patient need, the patient wins. That is not a discipline problem. It is the culture working as intended.
The trouble is that most access control programs are designed as if that collision will not happen. The policy says every person badges every time. The reality is that a unit is short staffed, a code is called, a family is crying in the hallway, and a door that takes four seconds to open is a door that gets propped. If your design assumes people will choose the badge reader over the patient, your design is wrong, and it was wrong before it was installed.
The first job of a leader is to accept this. Do not write a stricter policy and hope. Build a system that expects the propped door and the held door and is still reasonably safe when they occur.
Why the failures persist
Three patterns repeat in the facilities I have worked in. The first is courtesy. Holding a door for the person behind you is how decent people behave, and tailgating is simply that courtesy applied to a secure door. Staff are not trying to defeat security. They are being polite, and they often assume anyone wearing scrubs or carrying a clipboard belongs.
The second is convenience that becomes habit. A door near a loading area or a break room gets propped once because it is hot or because carts keep passing through. Nothing bad happens, so it gets propped again. Within a month it is simply how that door works, and nobody remembers it was ever secured.
The third is that nobody owns the result. Facilities installs the door. Security monitors the system. Nursing leadership runs the unit. When a door stays open for three days, each group assumes another is handling it. Access control sits between departments, and things that sit between departments rot.
Decide which doors actually matter
The most useful move is also the least expensive: stop treating all doors as equal. A hospital can have hundreds of reader-controlled openings, and a leader who tries to enforce every one will enforce none. Rank them by consequence. Which doors protect the pharmacy, the newborn unit, behavioral health, the server rooms, the controlled-substance storage, and the records areas? Those get your attention, your budget, and your strictest rules.
Doors in the lower tiers can be allowed more flexibility. A main corridor between two general inpatient wings does not need the same treatment as a medication room. When you let the low-consequence doors be easier, you gain credibility to be strict where it counts, and staff are far more willing to follow a rule they understand than a rule that seems to apply to everything.
Then walk those priority doors with clinicians, not just with the security team. Ask what makes them hard to use. Sometimes the answer is a reader placed in the wrong spot, a door that closes too slowly or too fast, or a delay setting that does not match how a bed actually moves. Fix the friction and the workarounds often fade on their own.
Make the held-open door visible
A door that is propped open should not be a quiet event. Most modern systems can generate a held-open alarm when a controlled door stays open longer than a set time, and many organizations have that feature turned off or ignored because it produced too many nuisance alarms. That is a tuning problem, not a reason to abandon the control.
Set the time thresholds by door type. A door that moves stretchers needs a longer window than a stairwell door. Route the alarm to someone who will act on it, and define what acting means: a call to the unit, an officer walking over, a photo of the condition. Then review the alarm history monthly. A door that alarms repeatedly is telling you something, either that it is badly designed for its traffic or that a team has decided the rule does not apply to them. Both findings are valuable.
Tell staff the alarms exist and why. People change behavior when they know the door is watched, and they change it more when the conversation is respectful instead of punitive. I have found that most staff will gladly stop propping a door once someone explains what that door protects and offers a better option for the cart traffic.
Audit what really happens, not what is recorded
This is where my doctrine, security is only assumed until it is tested, becomes practical. Your access control logs tell you who badged. They do not tell you who walked in behind them. The only way to learn how a door performs is to observe it. Stand near a priority door for an hour at shift change and count what you see. Review who is entering restricted areas and whether their role justifies it. Look at cards that have not been used in months but are still active.
Run authorized, planned tests with leadership approval. Have a trained person without a credential approach a priority door in a way a real unauthorized visitor might, then see whether staff challenge, escort, or call security. Do this to learn, not to embarrass. Share the results with the unit and treat a failure as a design finding. Keep the methods internal and leadership-level; the purpose is to improve the system, and the details of any single test do not belong in a broad report.
Audits should be routine, documented, and assigned. If they happen only after an incident, you are paying the highest price for the same information.
Who should own it
Name one accountable executive for access control outcomes. Not a committee and not a vendor. That person should receive the held-open reports, the audit results, and the exceptions list, and should have the authority to bring facilities, nursing, and security into the same room. Clinical leaders must be part of that structure, because a control the clinicians reject will be defeated by the clinicians, however good the intent.
Badge access can work in a hospital. It works when leaders rank the doors, accept the reality of clinical urgency, make failures visible, and test the result. It fails when the building is wired and the assumptions are left alone.
Go Deeper
If your organization needs senior security leadership without a full-time hire, read What Is a Fractional Security Director? The Complete Guide to see how that role can own problems like this one. My book Fractional Security Director lays out the approach in more detail.
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