After the Event Report: Turning Safety Signals into Meaningful Action
When a safety program works, nothing happens. No fall, no wrong-dose error, no claim. Organizational theorist Karl Weick called reliability a "dynamic non-event": the absence of harm looks like nothing, yet it takes continuous effort to produce.
That makes safety and quality work hard to defend at budget time. The cost shows up as salaries, software, and survey preparation. The patients who were never harmed show up nowhere.
Most harm never reaches the system
The harm that does occur is also poorly captured. A July 2025 report from the HHS Office of Inspector General (OIG) found that hospitals did not capture 49% of patient harm events among hospitalized Medicare patients. Hospitals also did not investigate every event they did capture.
Where programs cannot see harm or prove prevention, they tend to manage what they can document. For many hospitals that means attestations, survey binders, and evidence assembled by hand for the next review. Quality teams spend much of their week pulling records together, and that is time not spent on the unit or with a family.
Why people stop reporting
Ask frontline staff why they stop filing event reports and two answers come up repeatedly. One is fear of what will happen to them. The other is silence: they filed a report and never learned what became of it.
An international systematic review of 30 studies found fear of consequences was the most commonly reported barrier to reporting medical errors, cited in 63% of studies. Lack of feedback came next, along with work climate. A nurse who hears nothing after two or three reports reasonably concludes that nobody reads them.
When reporting drops, the dashboard improves. To the untrained eye, fewer events might look like a safer hospital, which is the wrong conclusion.
Fixes that get finished are not always the fixes that work
Feedback has to say something worth hearing. Too often the answer is "education was completed."
Researchers at a US academic medical center rated the strength of their own corrective actions after safety events. Of 148 actions, 57% were weak (retrain staff, send a reminder, update a policy) and 10% were strong, meaning they changed a device or a process to substantially reduce the likelihood of recurrence. The strong actions were the least likely to be completed. Weak actions depend on people remembering, and they rarely stop the next event.
Naming a cause achieves little without a strong action and a check that it worked. This is the gap between work as imagined, where a policy update closes the issue, and work as done, where the same pump gets programmed the same way next month.
Meaningful Measures
Outcome rates and attestation scores will not tell a board whether the reporting loop works. The following measures offer earlier insight into the effectiveness of the reporting process:
Reporter feedback rate. What share of people who file a report learn the outcome of the review?
Grievance response timeliness. As a potential indicator of patient safety, under the CMS Conditions of Participation at 42 CFR 482.13, a hospital sets its own time frames for grievance review and response, and families should receive a written answer when promised.
Corrective action strength. What share of actions are intermediate or strong rather than weak?
Time from event to verified closure. How long before someone confirms the problem stopped?
A fifth belongs on the list for mature programs: the ratio of near misses to harm events. When a pharmacist catches a dose before it reaches the floor, that is the system working. Although this relies on voluntary reporting, programs that learn to capture these catches will report more, not less. And while all of these measures can be helpful, organizations also need other mechanisms to detect harm and identify emerging risks.
Where technology helps, and where it can mislead
Much of the delay in closing the loop comes from gathering, connecting, and synthesizing information from different sources, the “assembly work.” Someone reads a narrative report, searches for similar events, checks the complaint system, finds the last audit, and writes it all up. Software that can read free-text reports and connect them across systems can take on that work.
Take the 2 a.m. medication error involving an infusion pump. A tool with access to prior reports might notice it is the third event on the same pump model on the same unit in six weeks, and that two patient complaints and a recent audit finding point to the same unit. The safety event investigator would then open a prepared case, not a queue.
The risk is how convincing that case can look. A well-organized software-generated narrative can feel finished when it is not. Automation bias, the tendency to accept a fluent output instead of exercising your own judgment, is a documented hazard of decision-support tools.
Organizations adopting these tools should expect:
competing explanations, such as the device, staffing, and storage practices, presented side by side
a plain statement of what the tool does not know
a link from every claim back to the report, complaint, or audit finding it came from, so staff check evidence rather than trust a summary
Determining cause stays with a person who is accountable for the finding. A governance policy should say so explicitly.
Protect the time you get back
The software may connect the dots, but an accountable person must determine whether those connections are meaningful and what conclusions they support. The free hours can be dedicated to working alongside the units where patterns are emerging and focusing on safety and quality improvement actions. Or those hours can be absorbed by the next request or taken out of the budget.
The workforce evidence points to the first option. In a survey of more than 21,000 physicians and nurses at 60 US Magnet hospitals, both groups rated management action on care delivery as more important to their well-being than programs aimed at their own resilience. Concerns that get answered are management action. So are reports that come back with an outcome.
A place to start
Pick the last five event reports closed in your organization and contact the people who filed them. Ask whether they learned what was found and what changed. The answers will tell you more about your safety culture than most survey scores, and they cost an afternoon.
Key takeaways
Reporting depends on what happens after the report. Fear and silence are the most common reasons staff stop.
Strong corrective actions are harder to finish than weak ones, so track strength and completion together.
Add loop measures, such as reporter feedback rate and time to verified closure, alongside outcome rates.
Use technology for assembly, and design it so that checking its work is easier than trusting it.
Keep cause determination with accountable people, and protect the capacity technology returns.
References
Weick KE. Organizing for transient reliability: the production of dynamic non-events. J Contingencies Crisis Manag. 2011;19(1):21-27. doi:10.1111/j.1468-5973.2010.00627.x
Office of Inspector General, US Department of Health and Human Services. Hospitals Did Not Capture Half of Patient Harm Events, Limiting Information Needed to Make Care Safer. OEI-06-18-00401. July 2025.
Aljabari S, Kadhim Z. Common barriers to reporting medical errors. Sci World J. 2021;2021:6494889. doi:10.1155/2021/6494889
Zerillo JA, Tardiff SA, Flood D, Sokol-Hessner L, Weiss A. Putting the "action" in RCA2: an analysis of intervention strength after adverse events. Jt Comm J Qual Patient Saf. 2024;50(7):492-499. doi:10.1016/j.jcjq.2024.03.012
Aiken LH, Lasater KB, Sloane DM, et al. Physician and nurse well-being and preferred interventions to address burnout in hospital practice: factors associated with turnover, outcomes, and patient safety. JAMA Health Forum. 2023;4(7):e231809. doi:10.1001/jamahealthforum.2023.1809
42 CFR §482.13. Condition of participation: patient's rights.
AI disclosure: An AI tool was used to assist with outlining and editing this article. The authors reviewed and revised all content.
As a Founding Strategic Partner, Ideagen is part of MPSC’s Council of Industry Partners—a community of organizations committed to advancing patient safety through collaboration. Learn more about becoming a Council partner.
