Near Misses in Hospitals: Why Report an Incident When the Patient Was Not Harmed?

Is every incident without harm a near miss?

The World Health Organization distinguishes between an incident that did not reach the patient and one that reached the patient without causing visible harm. So it is not enough to ask whether the patient was harmed; also ask how far the event got. If the team spotted a mismatch in patient identity before carrying out a procedure, the process stopped before the flaw reached the patient. If the wrong procedure was carried out, the absence of visible harm does not turn the event into a near miss. Staff use their facility’s approved classification when recording the event. ^[1]

There are also unsafe conditions that can be reported before any specific incident happens. A teaching example: similar-looking labels for two different services kept in a shared drawer. If a staff member notices the risk of confusion before any mix-up, they are describing an existing hazard. If a wrong label was actually picked and caught before use, the report describes a near miss. The distinction tells the analyst whether they are studying the design of the work environment or the sequence of an event that actually happened. ^{[1, 3]}

Why does the report matter if the team stopped the error?

What stopped the error this time may not be there next time. An experienced colleague may have caught a difference because they knew the details of the case, or a document may have been rechecked because the patient asked a question. The report shows whether the error was caught by a step designed into the process or by an individual action that cannot be relied on to happen again. A barrier that works can be strengthened, and the gap before it can be fixed before late detection becomes the only line of defence. ^{[1, 2]}

If you hear “we caught it and that’s the end of it”, try asking: what would have happened if the request had moved at shift handover? Would the next team have seen the same information? Could a new member of staff spot the difference relying on the system alone? These teaching questions turn the conversation towards working conditions instead of reducing it to the skill of the person who noticed the problem.

What should I write so someone else can understand the report?

Start with the facts you observed. State the stage of work, what was in front of you, the action that was about to happen, and when and how the difference was detected and stopped. Mark information that still needs checking as unconfirmed. If there is a screen or record to refer to, give its location in the approved system in line with the privacy policy. A sentence such as “the document carried an identifier different from the one shown on the request” is clearer than “the employee was not concentrating”. ^{[1, 3]}

Keep the sequence of events separate from interpretation. Noting that two files were open may be part of the sequence. Assuming that this was the only cause is a hypothesis that needs testing. Also ask whether the verification step was possible in the usual time, and whether the system displayed the necessary information in a way staff could read. If you have an improvement idea, put it in the suggestions field and leave the review team to test it with the people who do the work.

What should staff do before writing the report?

If the risk is still present, staff act within their authority and the facility’s approved escalation route. A written report does not replace informing the person in charge on shift when the situation needs immediate action. If other requests could be affected by the same problem, the responsible person decides what should be reviewed or stopped under the local procedure. Once the immediate situation is handled, staff record what happened in the designated reporting channel, and use the clinical record for the documentation that care requires under facility policy. ^{[1, 2]}

It helps to know the channel before anything happens. At the start of a shift or during training, ask where safety reports go, how urgent risks are escalated, and who answers questions about confidentiality. The channel or authority may differ between departments of the same facility. Knowing these details reduces confusion when a situation needs a quick decision.

How do we review a hypothetical case step by step?

In a hypothetical teaching case, a diagnostic department received two requests one after the other. While preparing the review papers, a page belonging to the first request appeared inside the bundle for the second. A staff member noticed the different identifier when applying the verification step and stopped the bundle before it moved to the point of service. The example involves no real patient and contains no patient data.

The review starts by locating where the mix-up happened: when the files were opened, at printing, or while the papers were being assembled? The team asks staff how work flows at busy times and compares what the policy describes with what happens in practice. It then examines the conditions that made the check succeed. Perhaps all the information was in front of the staff member, but it does not appear the same way at another reception point. These questions show where the barrier works and where it might fail.

The team can test a small change that fits the verified cause, such as separating bundles during preparation or moving the identifier to a more visible place on screen. The change is tested on a limited scale, monitoring its effect on the work and on the ability to detect differences. If alerts increase without improving discrimination, the solution needs revisiting. The purpose of the trial is to learn whether the change blocks the error pathway in real conditions, including workload pressure and shift handover. ^{[1, 2]}

What happens after the report reaches the quality team?

The team triages the report by potential risk, recurrence of the pattern and context. Not every event needs a lengthy investigation. Sometimes grouping similar reports and examining one process is enough; an event with potentially serious consequences may call for a deeper review. WHO guidance stresses moving from collecting reports to analysis, learning and managing improvement. ^[1]

Feedback is useful when it answers the staff’s question: what has changed? The team can share a short lesson explaining the flaw it found, the change it tried and what it will monitor, within confidentiality rules. If the fix has not been decided yet, the message says the event is under review and explains any approved interim measure. Details that identify individuals are not shared beyond those who need them to do their work.

Does a rise in reports mean the hospital has become less safe?

You cannot conclude that from the number of reports alone. Voluntary reporting is affected by how easy it is to report, staff awareness of the channels and their willingness to report. The number may rise after the form is simplified or confidence in the response improves. It may fall because reporting declines while the problem continues. Reports should therefore be read alongside other sources, such as audits, direct observation and record review where needed. ^{[1, 2]}

Choose indicators linked to the process you are trying to improve. If you changed how bundles are prepared, review whether teams follow the verification step, the type of differences detected, and whether bundles move in a way that makes them easy to tell apart. Do not turn the number of reports into a target that pressures staff to report more or less. The value lies in the quality of the signal received and the response to it.

How does this apply in Gulf healthcare facilities?

Staff review their facility’s policy on internal reporting and escalation, and the quality team checks the requirements of the regulator that applies to the facility. In Saudi Arabia, the Saudi Patient Safety Center publishes a manual setting out the policy for reporting and managing sentinel events. That route has its own scope, and it does not follow that every near miss must be reported externally. The channel, deadline and classification are set by the applicable text and the approved internal procedure. ^[4]

A useful training exercise is to present the same scenario to different teams and ask each to describe the facts, classify the event and name the channel they would use. Comparing the answers shows where the definition of an incident or the meaning of urgent escalation is unclear. The explanation or the form can then be adjusted to address that confusion, rather than repeating the same theoretical presentation.