Near Misses in Hospital: How Can a Medical Team Leader Learn from Them?

Start with a precise definition

Before drawing conclusions, the team should establish what kind of incident it is discussing. Under the WHO definition, a near miss is an incident that did not reach the patient. If an incident reached the patient but caused no discernible harm, it belongs to a different category. Imagine an incorrect product set aside before use: the account should explain how it came to be on a path toward the patient and where that path was interrupted. This keeps the discussion focused on what happened, not just on the fortunate outcome. The distinction also helps make the report precise. WHO guidance clarifies definitions and principles for learning from reports, but it does not establish the effectiveness of any particular way of conducting these discussions.

Why no harm does not end the analysis

The fact that the patient was not harmed does not necessarily mean working conditions were safe. First, reconstruct the actual sequence: what happened, how far the hazard progressed, and what stopped it. Only then, separately, consider what might have happened if the sequence had continued. That possible outcome should not replace an account of the facts. A report is a starting point for understanding the risk mechanism and checking whether a similar situation would also be stopped on another shift. The number of completed forms alone measures neither the safety of care nor the frequency of all incidents. Understanding the conditions that led to the outcome therefore matters more than the outcome itself.

What stopped the incident

Once the sequence has been reconstructed, identify the mechanism that interrupted the hazard’s path to the patient. Did a planned safeguard, such as a checklist, work, or did one person spot the problem? Or did an accidental delay help? These answers are not equivalent: they point to safeguards with different degrees of reliability. Ask what information the person who recognized the problem had and what enabled them to respond. Then record the barrier, the conditions that allowed it to work, and how it will be checked on the next shift. The question is not only what prevented harm this time, but whether a similar mechanism would work with a different team and pace of work.

How to talk with those involved

It is best to begin by hearing the perspectives of those involved, without offering a ready-made explanation. Asking what information someone had at the time helps avoid judging a decision using knowledge gained only later. Acknowledge both the act of reporting the situation and the recognition of the hazard, while still discussing errors factually. If someone raises a concern, it should reach a person who can act on it. A systematic review of publications on speaking up in healthcare helps clarify that concept; it does not establish the effectiveness of a single discussion method. The aim of the meeting is therefore to gather information needed for action, not to quickly assign blame.

How to choose a lesson to put into practice

The lesson drawn from the analysis should address the point where the team lost or regained control of the situation. If an incorrect product was stopped just before use, consider whether it could be made easier to identify earlier. Simply telling people to ‘be more careful’ does not specify a safeguard that can be checked. It is better to choose one process change that can be made during similar tasks and name the person responsible for implementing it. The team should also know what it will observe on the next comparable shift: whether the agreed step actually takes place and whether it helps detect the hazard. A lesson recorded this way turns the discussion into a concrete check of a change in practice.

Feedback for the team

After discussing the incident, report back to the team on what the organization learned and what it will change in practice. Asking people to report future situations is no substitute for responding to a report. Those involved should hear what was done with the analysis, what limitation was found, and which safeguard worked and should be maintained. The account can be anonymized without removing details needed to understand the mechanism: the sequence of actions, the information available, and the point where the hazard was stopped. There is no need to publicly name someone as being at fault. This feedback helps the team distinguish a change based on the analysis from a general appeal for caution and see the value of discussing the incident together.

How to assess what the team has learned

The best place to assess what has been learned is where the safeguard is meant to work. The team can compare how the process works before and after the change under similar conditions and see whether a comparable hazard is detected sooner. It is also worth asking people who were not at the discussion whether they understand the new rule and know how to respond. This keeps the assessment from relying solely on what participants remember from one meeting. A fall in the number of reports alone does not prove that safety has improved: report counts capture neither every incident nor the performance of a particular barrier. If the step proves unclear or difficult to carry out on the next shift, the team can review it again rather than consider the matter closed.

No harm does not mean the analysis is over. The team can establish where the hazard’s path to the patient was interrupted and whether the safeguard will work next time.

Empatyzer in discussions about near misses

Before discussing an error caught before a medication was administered, a team leader can ask Em for neutral questions to put to the team. In team mode, the leader can prepare a brief discussion of the sequence of actions, the information available to those involved, the barrier that stopped the incident, and the next step. The questions can help separate what is known about the sequence from assumptions about possible harm. The ‘You and the team’ view can help the leader find a way to invite people from different professions to speak, while a comparison with a selected person can help prepare for a one-to-one conversation. That person’s view can also suggest how to phrase a difficult question without implying blame. After the meeting, micro-lessons can help reinforce the habit of acknowledging what already works, such as noticing an effective safeguard. Empatyzer helps prepare the conversation; establishing the facts, choosing a change, and checking it on the next shift remain the team’s responsibility.