What incident reporting is and what it is for
Incident reporting is the structured, voluntary collection of reports of events — or near events — that caused or could have caused harm to a patient. It is not a register of blame: it is a tool for organisational learning. The underlying assumption, well established in the international patient safety literature, is that error in healthcare is rarely the failure of a single professional and almost always the result of system factors: poorly designed processes, broken communication, workload, inadequate technology, look-alike drug names. Every report is a fragment of knowledge about how the system really fails.
For this mechanism to work there is a cultural precondition: a just, non-punitive culture (no-blame, or more precisely just culture). In a blame culture, those who report fear disciplinary consequences, judgement from colleagues or legal repercussions: the result is silence, and the reporting system starves. In a just culture, reporting is protected and encouraged, the analysis focuses on why the event was able to happen rather than on who, and individual accountability is confined to cases of deliberate and unjustifiable violations. It is no coincidence that the volume and quality of reports are among the most telling indicators of a healthcare organisation's maturity.
Incident reporting is one of the building blocks — together with RCA, FMEA/FMECA, clinical audit, Safety Walkaround and M&M review — of the wider clinical risk management system: for the overall picture, see our complete guide to clinical risk in healthcare.
Near miss, adverse event, sentinel event: the definitions
An effective reporting system starts from a shared glossary. The three fundamental categories, aligned with the terminology of the Italian Ministry of Health, are:
- Near miss: an error or hazardous condition that had the potential to harm the patient but did not — by chance or because it was intercepted in time (an incorrect prescription identified before administration). Near misses are the richest seam of a reporting system: they offer the same information as an adverse event, without the harm.
- Adverse event: an unexpected event related to the care process that resulted in unintended and undesirable harm to the patient. Not all adverse events result from an error: it is important to distinguish preventable from non-preventable events, because improvement action focuses on the former.
- Sentinel event: a particularly serious adverse event, potentially indicative of a serious system malfunction, which causes death or serious harm to the patient and undermines public trust in the health service. For sentinel events, reporting is a mandatory information flow to national level, and every single case requires an in-depth investigation.
Correctly distinguishing the three categories at classification stage is not a taxonomic exercise: it determines the analysis pathway the report will follow, as we will see below.
The Italian regulatory framework
In Italy incident reporting is not an optional good practice: it is part of a precise legal framework that every medical directorate needs to know.
Law 208/2015: the risk management function is mandatory
Law no. 208 of 28 December 2015 (art. 1, paragraphs 538-540) required all healthcare organisations, public and private, to set up a function for monitoring, preventing and managing healthcare risk. The activities this function must oversee include precisely the detection of adverse events and the preparation of the resulting actions: without an operational incident reporting system, the function required by law exists only on paper.
Law 24/2017 (Gelli-Bianco): safety of care and protection of the reporter
Law no. 24 of 8 March 2017 elevated safety of care to a constituent part of the right to health (art. 1), established the Regional Centres for healthcare risk management (art. 2) and the National Observatory of good practices at AGENAS (art. 3). For incident reporting, however, the most important provision is art. 16: the minutes and documents resulting from clinical risk management activities cannot be acquired or used in legal proceedings. This is the legal protection that makes the promise of non-punishment credible: what you write in a report or in a clinical risk audit is there to learn from, not to accuse. With the law now fully in force — implementing decrees included, such as Ministerial Decree (D.M.) 232/2023 — demonstrating a functioning reporting system becomes even more important: we discussed this in our in-depth article on the Gelli-Bianco Law fully in force from 16 March 2026.
SIMES and Ministerial Recommendations
SIMES (Information System for Monitoring Errors in Healthcare, D.M. of 11 December 2009) is the national information flow that collects sentinel events and claims notifications: the internal incident reporting system must be able to feed it with complete and timely data. Alongside this flow, the Ministry of Health has published the Recommendations for patient safety (nos. 1-19), which cover the highest-risk areas — from correct patient identification to LASA (look-alike, sound-alike) medicines, from fall prevention to safety in the operating theatre. The reports collected are the tool the organisation uses to check whether the Recommendations are actually applied or whether there are systematic deviations.
How to structure the system: from the reporting form to the PARM
A mature incident reporting system is a closed loop, not a letterbox. The reference flow is made up of six steps.
1. Reporting
The form must be reachable in a few seconds by any member of staff, completable in a few minutes and understandable without specific training. Essential fields: what happened, where, when, what consequences for the patient, what factors contributed. Everything else can be gathered later: every additional mandatory field means one report fewer.
2. Classification
The risk manager (or the delegated function) takes charge of the report and classifies it: near miss, adverse event or sentinel event; area and process involved; actual and potential severity. Classification determines the priority and the analysis pathway and — for sentinel events — triggers the reporting obligations towards the SIMES flow.
3. Analysis
Not every event deserves the same analytical investment. For serious events and sentinel events the reference tool is Root Cause Analysis (RCA): a structured, multidisciplinary investigation that traces back from immediate causes to latent system factors. For near misses and low-severity events, the most productive analysis is aggregated analysis: individual cases say little, but time series by type, ward and time of day reveal recurring patterns before they cause harm. From a proactive perspective, reporting data also feed FMEA/FMECA analyses of critical processes.
4. Corrective actions
Every analysis must end with concrete actions: revising a procedure, a double check on a critical step, targeted training, changing a layout or a technology. Each action has an owner, a deadline and an indicator to verify its effectiveness. An analysis without actions is a cost; an action without verification is a hope.
5. Feedback to the reporter
This is the most neglected step and one of the most important: those who reported need to know that their report was read, analysed and led to something. Feedback — individual or through collective moments such as M&M reviews and periodic ward reports — is the fuel that keeps the system alive. Where feedback is missing, reports fall within a few months.
6. Feeding into the PARM
Reporting data — volumes, types, critical areas, analysis outcomes, status of actions — feed into the Annual Risk Management Plan (PARM, Piano Annuale di Risk Management) and the annual year-end report: they are the evidence base the directorate uses to set priorities for the following year. A PARM built on the data from your own incident reporting can be defended before any stakeholder; a PARM photocopied from the previous year cannot. We have devoted a specific guide to the PARM.
Typical obstacles and how to overcome them
Most incident reporting systems do not fail for technical reasons: they fail for organisational and cultural reasons, almost always the same ones.
- Fear of reprisals. This is obstacle number one. It is overcome with an explicit written commitment from the directorate that reports made in good faith will not be punished, referring to the protection of art. 16 of Law 24/2017, and with consistent behaviour: a single case of a report used for disciplinary purposes is enough to wipe out years of work.
- Complex forms. Long forms, quality jargon, redundant mandatory fields, paper forms to be handed in physically: every point of friction reduces reports, and reduces them most in the wards under pressure, where the risk is highest.
- Lack of feedback. If reporting is like writing into a black hole, staff stop doing it. Systematic acknowledgement is needed, even if only of receipt, together with periodic communication of the improvements achieved thanks to the reports.
- Ambiguity about what to report. If staff do not know what to report, they report only serious events — which are the rarest. Short, recurring training on definitions and concrete examples is needed, with particular emphasis on the value of near misses.
- Data that do not become decisions. If reports pile up without aggregated analysis or visible actions, the system loses credibility in the eyes of the directorate too. The remedy is the closed loop described above, with explicit responsibilities and deadlines.
Clinical incident reporting and cyber incident reporting: the NIS2 duality
For healthcare organisations that fall within the scope of NIS2 (Legislative Decree, D.Lgs. 138/2024), the term "incident reporting" now has a second meaning: the management and notification of significant cyber incidents. The underlying logic is the same as for clinical risk — detect, classify, analyse, correct, learn — but the external flow is different: art. 25 requires notification to ACN (the Italian National Cybersecurity Agency) with an early warning within 24 hours, a notification within 72 hours and a final report within one month of becoming aware of the incident. We have described how this works in practice in our article on the 24h / 72h / 1-month notification procedure to ACN.
For a medical directorate the lesson is twofold. First: the skills developed in clinical incident reporting — reporting culture, classification, root cause analysis — are an asset that can be reused on the cyber front. Second: the two flows must be kept separate but coordinated, because a cyber incident in healthcare — think of an outage of prescribing systems — is often also a clinical risk. The most mature organisations get risk managers and information security officers talking to each other within an integrated risk governance model.
Digitising the flow: the role of incident reporting software
Everything we have described can be done on paper and spreadsheets — but with high management costs, fragmented data and no end-to-end traceability, precisely when the legislation requires organisations to demonstrate that the system works. A platform such as EasyRisk digitises the entire cycle: simplified reporting of near misses, adverse events and sentinel events, accessible to all staff; an analysis workflow with taking charge, classification, corrective actions and closure fully tracked; aggregated reporting that feeds the PARM and the annual report without manual reworking. The result is a reporting system that produces organised evidence, ready for the directorate, supervisory bodies and insurers.
If you are considering how to computerise clinical risk management in your organisation, we have also published a guide to choosing healthcare risk management software, with the criteria to consider before purchasing.
Want an incident reporting system that really works?
The Easy Health team supports medical directorates, risk managers and quality departments in designing the reporting flow and digitising it with the EasyRisk platform.
Discover the EasyRisk platform or contact us to arrange a dedicated call.