IHP 315 Module 3 Reporting Systems Short Paper Example

When Reporting Goes Quiet: Rebuilding an Incident Reporting System

[Student Name]

Southern New Hampshire University

IHP 315: Patient Safety Systems and Strategies

Module Three Short Paper

[Instructor Name]

[Date]

When Reporting Goes Quiet: Rebuilding an Incident Reporting System

An incident report is a staff member's decision to tell the organization that something went wrong or nearly did. When those decisions stop, leaders lose their early warning system. On the fourth-floor medical-surgical unit at Maple Grove, reports fell from about fourteen a month to seven in the quarter after a nurse received a written warning for an insulin error she reported herself. Some leaders read the drop as good news. This paper argues that it was a warning, explains what makes reporting systems work, sets out why reports cannot measure safety and recommends changes.

Why Staff Stopped Reporting

Conversations with six nurses and two nursing assistants on the unit revealed four reasons. First, the written warning taught staff that reporting a serious error could bring discipline. Second, the electronic form took twelve to fifteen minutes, with many required fields, time few nurses have once their shift is over. Third, staff rarely heard what happened after a report; one nurse said reports went into a black hole. Fourth, several believed that near misses, errors caught before reaching the patient, were not worth reporting because no one was hurt. Each reason is a feature of the system, not a failing of the staff.

What Makes Reporting Systems Work

Leape (2002) distinguished two purposes for reporting systems. Accountability systems, often run by regulators, aim to hold organizations responsible for serious events. Learning systems aim to find hazards and fix them. A hospital's internal system should be a learning system, and Leape drew on experience in aviation and other industries to describe what such systems need. Reporting should not lead to punishment for honest errors. Reports should be confidential, and the system should be independent of anyone with power to discipline the reporter. Experts who understand clinical work and systems should analyze reports. Responses should be timely, and recommendations should focus on changing systems rather than individuals. Finally, the organization must act on what it learns, or reporting will wither.

Measured against these features, the fourth floor's system failed on almost every count: reporting brought discipline, reports went to the unit manager who also evaluated staff, analysis rarely happened and feedback never did.

Why Reports Cannot Measure Safety

Even a healthy reporting system does not count harm accurately. In a three-hospital comparison of ways to detect adverse events, Classen et al. (2011) found that a structured chart review identified many times more events than voluntary reporting, which caught only a small fraction. Reports depend on someone noticing an event, recognizing it as reportable and choosing to file. For that reason, a rise in reports after culture improves usually means more honesty, not more harm, and a fall, as on the fourth floor, often means the opposite.

The practical lesson is that the hospital needs two tools: a reporting system to learn about hazards and a separate measurement method, such as periodic chart review with triggers, to track how often harm actually occurs.

Reporting as Part of Safety Culture

In the view of Reason (2000), the safest organizations keep worrying about what could go wrong and prize near misses as lessons that cost nothing, since they reveal weaknesses without injuring anyone. He emphasized that a reporting culture depends on trust and on a clear, agreed line between blameless errors and truly unacceptable behavior. Without that line, staff cannot predict how a report will be received and will protect themselves by staying silent. The written warning on the fourth floor erased the line.

What Leaders Must Do Differently

Most of the fixes depend on leaders rather than frontline staff. The nurse manager and the director of nursing need to say, in person, that reporting honest errors will not lead to discipline, and then show it the next time a serious error is reported. The patient safety officer needs protected time to analyze reports and draft system fixes, rather than simply filing them. Senior leaders should review a short list of reported hazards monthly and commit resources to at least one fix each quarter. Without these commitments, a new form and a near-miss campaign will produce a brief rise in reports and then another decline, because staff will again see that nothing changes.

Recommendations

Five changes would address the causes staff described. First, adopt a just culture policy that separates honest errors, risky choices and reckless behavior, and review the written warning under that policy. Second, shorten the electronic form to essential fields that take under three minutes, with an optional section for details. Third, route reports to the patient safety office rather than directly to the reporter's manager, and offer an anonymous option. Fourth, close the loop with a monthly one-page summary on each unit showing what was reported and what changed, and send each reporter a brief personal reply. Fifth, run a short campaign on near misses, including examples from the unit, to show that caught errors are valuable.

Table 1. Causes and Responses

Note. Responses map to the causes staff described.

Measuring Success

Success will look counterintuitive. The hospital should expect total reports, and especially near-miss reports, to rise over the next six months, and it should celebrate that rise. It should track the share of reports receiving feedback within two weeks and the time taken to file a report. Separately, the quality department should begin a monthly review of twenty randomly selected records using medication and fall triggers, so leaders can follow actual harm independently of reporting. A follow-up survey question on whether staff feel safe reporting will show whether trust is returning.

Conclusion

The drop in reports on the fourth floor was a symptom of a system that punished reporters, wasted their time and never answered them. Rebuilding it means applying the features Leape described, measuring harm by other means and restoring the trust that makes reporting possible.

References

Classen, D. C., Resar, R., Griffin, F., Federico, F., Frankel, T., Kimmel, N., Whittington, J. C., Frankel, A., Seger, A., & James, B. C. (2011). 'Global trigger tool' shows that adverse events in hospitals may be ten times greater than previously measured. Health Affairs, 30(4), 581-589. https://doi.org/10.1377/hlthaff.2011.0190

Leape, L. L. (2002). Reporting of adverse events. New England Journal of Medicine, 347(20), 1633-1638. https://doi.org/10.1056/NEJMNEJMhpr011493

Reason, J. (2000). Human error: Models and management. BMJ, 320(7237), 768-770. https://doi.org/10.1136/bmj.320.7237.768