The Near Miss That Never Made the Report
A near miss in infection prevention is an event that had every condition necessary to cause a healthcare-associated infection (HAI) but did not produce one — because of timing, chance, or a catch made late in the process. These events carry nearly the same information as a confirmed infection, without the patient harm and without the reportable event. Most infection prevention programs never capture them.
Consider a central line that stayed in place four days past the last documented necessity assessment. The dressing became compromised. The patient developed a fever, blood cultures were drawn, and the results came back negative. Per National Healthcare Safety Network (NHSN) surveillance protocols, there is no central line-associated bloodstream infection. Nothing to report, and nothing to bring to the hospital's infection control, quality, or patient safety committees.
But every condition that produces a CLABSI was present. Only the outcome was different — and because the outcome was different, nothing appeared on any report.
Somebody noticed that dressing. Probably during a shift where they were doing four other things. Whether they mentioned it to anyone is the entire question.
Why do near misses matter in infection prevention?
Patient safety research has treated close calls as a key learning resource for decades. The Institute of Medicine defines a near miss as an act of commission or omission that could have harmed the patient but did not — as a result of chance, prevention, or mitigation. That last category matters most here, because it means someone caught something.
Near-miss events are estimated to occur 7 to 100 times more frequently than adverse events, yet reporting systems for them remain far less common. Most hospitals already have some version of this working. Medication safety programs have captured close calls for years, with established reporting pathways and a culture that treats a good catch as a good outcome. The infrastructure exists.
Infection prevention has largely not been plugged into it, mostly because HAI surveillance is built to count outcomes. NHSN definitions identify infections meeting specific criteria, which is exactly what they should do. But an outcome-only view of risk means the program learns from a small fraction of the events that actually occurred. I don't know how many of these we're missing, and I'd guess that’s the same in most programs.
A unit with zero CLABSIs this quarter may have had a strong quarter. It may also have had a fortunate one. Event counts alone cannot distinguish between the two. That requires data on process, compliance, and variability in care.
What does a near miss reveal that a confirmed infection does not?
A confirmed infection tells you that something failed. But near misses can show you where your failures tend to begin and can show you earlier, before harm reaches the patient.
Patterns that show up repeatedly during our on-site program assessments:
Devices that remain in place well past documented necessity, removed only after a prompt from someone outside the usual workflow
Transmission-based precautions initiated late, after a patient had already moved through shared spaces
Sterile processing exceptions resolved by one staff member's judgment rather than a defined escalation process
Device access or maintenance practices that vary by shift or by person rather than by protocol
The person who catches these is frequently someone outside the routine — a float nurse, a rounding pharmacist, a new hire who hasn't yet stopped noticing. Familiarity can make risk invisible, and the people least familiar with a unit often see it most clearly.
These variances often don’t generate a reportable event, but they reveal a program operating closer to its margins than the surveillance data suggests.
Why near misses go unreported
The barrier isn't awareness. Most staff can tell you exactly what almost went wrong last week. The barrier is that reporting one means volunteering that something nearly happened on your shift, on your unit, possibly involving your patient. Even in organizations that describe themselves as non-punitive, people watch what happens to the first person who tests it.
This is why framing matters more than mechanism. A "good catch" is a story about someone doing something right. An "incident" is a story about someone doing something wrong. The events can be identical. The reporting rates will not be.
How can a program begin capturing near misses?
The goal isn't another reporting burden. It's a wider view of care, and it works best when the process stays small.
Add a single "good catch" prompt to device rounds you already conduct
Ask one more question during unit rounding: what almost went wrong this week?
Bring close calls to safety committees with the same seriousness given to confirmed events
Then decide what happens next. Most near misses are one-offs and need nothing more than a thank-you. The ones worth acting on are the ones that repeat — same gap, different people, different shifts. That pattern is telling you something about the process, not about the person who reported it.
Programs that do this consistently tend to find the same thing: the conditions were visible long before the infection was.
Looking at what nearly happened
Good surveillance data tells you what happened. It doesn't tell you what nearly happened, and it rarely tells you whether your results depend on reliable process or on one reliable person. That distinction matters, because reliable people take vacations.
If your infection rates look stable but your team senses that outcomes hinge on the right person noticing the right thing, an infection prevention gap assessment is a low-risk way to find out. IP&MA reviews program structure, workflow, and physical environment — the conditions that produce infections — and delivers a written findings report with a prioritized, practical list of recommendations.
Request a discovery call to talk through what a gap assessment would look like at your facility.