Article Text


Incident analysis
Analysis of clinical incidents: a window on the system not a search for root causes
  1. C A Vincent
  1. Correspondence to:
 Professor C A Vincent
 Smith & Nephew Foundation Professor of Clinical Safety Research, Department of Surgical Oncology and Technology, Imperial College School of Science, Technology and Medicine, St Mary’s Hospital Campus, London W2 1NY, UK;

Statistics from

It is time to pay more attention to incident analysis

Incident reporting lies at the heart of many initiatives to improve patient safety. The UK National Patient Safety Agency (NPSA)1 has recently launched a national reporting and learning system following substantial piloting and testing across the National Health Service (NHS). In the USA the Agency for Healthcare Research and Quality (AHRQ) made incident reporting the centrepiece of its first patient safety funding programme, investing $25 million in the first year into research in incident reporting systems.2 The Australian incident monitoring system has amassed a massive database of reports over 15 years.3 New risk management and patient safety programmes—whether local or national—rely on incident reporting to provide data on the nature of safety problems and to provide indications of the causes of those problems and the likely solutions.

Incident reports by themselves, however, tell you comparatively little about causes and prevention, a fact which has long been understood in aviation.4 Reports are often brief and fragmented; they are not easily classified or pigeon holed. Making sense of them requires clinical expertise and a good understanding of the task, the context, and the many factors that may contribute to an adverse outcome. At a local level, review of records and, above all, discussions with those involved can lead to a deeper understanding of the causes of an incident. Surprisingly little attention, however—and even less funding—has been given to the key issue of incident analysis.


A clinical scenario can be examined from a number of different perspectives, each of which may illuminate one facet of the case. Cases have, from time immemorial, been used to educate and reflect on the nature of disease. They can also be used to illustrate the process of clinical decision making, treatment options and sometimes, particularly when errors are discussed, the personal impact of incidents and mishaps. Incident analysis, for the purposes of improving the safety of health care, may encompass all of these perspectives but, critically, also includes reflection on the broader healthcare system. This process is usually known by the wholly inappropriate term “root cause analysis”.5

There are a number of methods of incident investigation and analysis available in health care. In the USA the most familiar is the root cause analysis approach of the Joint Commission, an intensive process with its origins in total quality management approaches to healthcare improvement.6 The Veterans Hospital Administration has developed a highly structured system of triage questions which is being disseminated throughout their system.7 In the UK the Clinical Safety Research Unit has developed a “systems analysis” of incidents based on Reason’s model and our own framework of contributory factors.8,9 A revised and updated version is now available.10,11 The NPSA has developed a root cause analysis teaching programme which is an amalgam of elements of all these approaches.


We have described our own approach to the analysis of incidents as a systems analysis rather than a root cause analysis. The term “root cause analysis”, while widespread, is misleading in a number of respects. To begin with, it implies that there is a single root cause, or at least a small number. Typically, however, the picture that emerges is much more fluid and the notion of a root cause is a gross oversimplification.5,9 Usually there is a chain of events and a wide variety of contributory factors leading up to the eventual incident. A more important and fundamental objection to the term “root cause analysis” relates to the very purpose of the investigation. Surely the purpose is obvious? To find out what happened and what caused it. Certainly, it is necessary to find out what happened and why in order to explain to the patient, his or her family, and others involved. However, if the purpose is to achieve a safer healthcare system, then it is necessary to go further and reflect on what the incident reveals about the gaps and inadequacies in the healthcare system in which it occurred. The incident acts as a “window” on the system—hence systems analysis. Incident analysis, properly understood, is not a retrospective search for root causes but an attempt to look to the future. In a sense, the particular causes of the incident in question do not matter as they are now in the past. However, the weaknesses of the system revealed are still present and could lead to the next incident.


Prospective analyses of systems are increasingly being explored in health care on the reasonable argument that it is better to examine safety proactively and to prevent incidents before they happen. Incident analysis is usually seen as retrospective while techniques such as Failure Modes and Effects Analysis (FMEA), which examine a process of care, are seen as prospective. FMEA and related approaches are being trialled in a variety of settings and endorsed by the US Veterans Administration, UK NPSA, and others.12,13 We might think that, as health care becomes safer, these prospective analyses will eventually supplant incident analysis. Leaving aside the fact that health care has rather a long way to go before the supply of incidents dries up, there are a number of reasons for continuing to explore individual incidents as well as examining systems prospectively.

Firstly, there is no sharp division between retrospective and prospective techniques; as argued above, the true purpose of incident analysis is to use the incident as a window onto the system—in essence, looking at current weaknesses and future potential problems. Conversely, so called “prospective analysis” relies extensively on the past experience of those involved. Probabilities and hazards assessed in FMEA are derived almost exclusively from groups of clinicians on the basis of their past experience. Techniques such as FMEA are, in addition, very expensive in terms of time and resources.13 The analysis of single incidents—whether or not they have a bad outcome—can be scaled to the time and resource available, be it 10 minutes or 10 days.14 A single incident—a story—almost always engages a clinical group and can be analysed by an individual risk manager or a whole clinical team. The future probably lies in a judicious application of both forms of techniques, using systems analyses of incidents to generate both enthusiasm and hypotheses as a basis for more resource intensive analyses of whole processes and systems.

A major concern with all the techniques discussed is the lack of formal testing and evaluation. The process of analysing incidents could be considered simply as a method of engaging teams in reflecting on safety; in that case, formal evaluation may not be critical. However, if we believe it could function as a more formal diagnostic technique exposing flaws in healthcare systems, then questions of inter-rater reliability and the validity of the conclusions become important. With vast funds being sunk into the research and development of reporting and tracking of incidents, it is perhaps time to pay more attention to the ultimately more important—but greatly neglected—issue of incident analysis.

It is time to pay more attention to incident analysis

View Abstract

Request permissions

If you wish to reuse any or all of this article please use the link below which will take you to the Copyright Clearance Center’s RightsLink service. You will be able to get a quick price and instant permission to reuse the content in many different ways.