Open Access Articles- Top Results for Root cause analysis

Root cause analysis

Root cause analysis (RCA) is a method of problem solving used for identifying the root causes of faults or problems.[1] A factor is considered a root cause if removal thereof from the problem fault-sequence prevents the final undesirable event from recurring; whereas a causal factor is one that affects an event's outcome, but is not a root cause. Though removing a causal factor can benefit an outcome, it does not prevent its recurrence within certainty. Following the introduction of Kepner-Tregoe Analysis--which had limitations in the highly complex arena of rocket design, development and launch--RCA arose in the 1950s as a formal study by the National Aeronautics and Space Administration (NASA) in the United States. New methods of problem analysis developed by NASA included a high level assessment practice called MORT (Management Oversight Risk Tree).[2][3][4] MORT differed from RCA by assigning causes to common classes of cause shortcomings that could be summarized into a short list. These included work practice, procedures, management, fatigue, time pressure, along with several others. For example: if an aircraft accident occurred as a result of adverse weather conditions augmented by pressure to leave on time; failure to observe weather precautions could indicate a management or training problem; and lack of appropriate weather concern might indict work practices. Because several measures (methods) may effectively address the root causes of a problem, RCA is an iterative process and a tool of continuous improvement.

RCA is applied to methodically identify and correct the root causes of events, rather than to simply address the symptomatic result. Focusing correction on root causes has the goal of entirely preventing problem recurrence. Conversely, RCFA (Root Cause Failure Analysis) recognizes that complete prevention of recurrence by one corrective action is not always possible.

RCA is typically used as a reactive method of identifying event(s) causes, revealing problems and solving them. Analysis is done after an event has occurred. Insights in RCA make it potentially useful as a preemptive method. In that event, RCA can be used to forecast or predict probable events even before they occur. While one follows the other, RCA is a completely separate process to Incident Management.

Rather than one sharply defined methodology, RCA comprises many different tools, processes, and philosophies. However, several very-broadly defined approaches or "schools" can be identified by their basic approach or field of origin: safety-based, production-based, process-based, failure-based, and systems-based.

Despite the different approaches among the various schools of root cause analysis, all share some common principles. Several general processes for performing RCA can also be defined.

General principles of root cause analysis

  1. The primary aim of root cause analysis is: to identify the factors that resulted in the nature, the magnitude, the location, and the timing of the harmful outcomes (consequences) of one or more past events; to determine what behaviors, actions, inactions, or conditions need to be changed; to prevent recurrence of similar harmful outcomes; and to identify lessons that may promote the achievement of better consequences. ("Success" is defined as the near-certain prevention of recurrence.)
  2. To be effective, root cause analysis must be performed systematically, usually as part of an investigation, with conclusions and root causes that are identified backed up by documented evidence. A team effort is typically required.
  3. There may be more than one root cause for an event or a problem, wherefore the difficult part is demonstrating the persistence and sustaining the effort required to determine them.
  4. The purpose of identifying all solutions to a problem is to prevent recurrence at lowest cost in the simplest way. If there are alternatives that are equally effective, then the simplest or lowest cost approach is preferred.
  5. The root causes identified will depend on the way in which the problem or event is defined. Effective problem statements and event descriptions (as failures, for example) are helpful and usually required to ensure the execution of appropriate analyses.
  6. One logical way to trace down root causes is by utilizing hierarchical clustering data-mining solutions (such as GT data mining). A root cause is defined in that context as "the conditions that enable one or more causes". Root causes can be deductively sorted out from upper groups of which the groups include a specific cause.
  7. To be effective, the analysis should establish a sequence of events or timeline for understanding the relationships between contributory (causal) factors, root cause(s) and the defined problem or event to be prevented.
  8. Root cause analysis can help transform a reactive culture (one that reacts to problems) into a forward-looking culture (one that solves problems before they occur or escalate). More importantly, RCA reduces the frequency of problems occurring over time within the environment where the process is used.
  9. Root cause analysis as a force for change is a threat to many cultures and environments. Threats to cultures are often met with resistance. Other forms of management support may be required to achieve effectiveness and success with root cause analysis. For example, a "non-punitive" policy toward problem identifiers may be required.

General process for performing and documenting an RCA-based Corrective Action

RCA (in steps 3, 4 and 5) forms the most critical part of successful corrective action, directing the corrective action at the true root cause of the problem. Knowing the root cause is secondary to the goal of prevention, as it is not possible to determine an absolutely effective corrective action for the defined problem without knowing the root cause.

  1. Define the problem or describe the event to prevent in the future. Include the qualitative and quantitative attributes (properties) of the undesirable outcomes. Usually this includes specifying the natures, the magnitudes, the locations, and the timing of events. In some cases, "lowering the risks of reoccurrences" may be a reasonable target. For example, "lowering the risks" of future automobile accidents is certainly a more economically attainable goal than "preventing all" future automobile accidents.
  2. Gather data and evidence, classifying it along a timeline of events to the final failure or crisis. For every behavior, condition, action and inaction, specify in the "timeline" what should have been done when it differs from what was done.
  3. In data mining Hierarchical Clustering models, use the clustering groups instead of classifying: (a) peak the groups that exhibit the specific cause; (b) find their upper-groups; (c) find group characteristics that are consistent; (d) check with experts and validate.
  4. Ask "why" and identify the causes associated with each sequential step towards the defined problem or event. "Why" is taken to mean "What were the factors that directly resulted in the effect?"
  5. Classify causes into two categories: causal factors that relate to an event in the sequence; and root causes that interrupted that step of the sequence chain when eliminated.
  6. Identify all other harmful factors that have equal or better claim to be called "root causes." If there are multiple root causes, which is often the case, reveal those clearly for later optimum selection.
  7. Identify corrective action(s) that will, with certainty, prevent recurrence of each harmful effect and related outcomes or factors. Check that each corrective action would, if pre-implemented before the event, have reduced or prevented specific harmful effects.
  8. Identify solutions that, when effective and with consensus agreement of the group: prevent recurrence with reasonable certainty; are within the institution's control; meet its goals and objectives; and do not cause or introduce other new, unforeseen problems.
  9. Implement the recommended root cause correction(s).
  10. Ensure effectiveness by observing the implemented solutions in operation.
  11. Identify other possibly useful methodologies for problem solving and problem avoidance.
  12. Identify and address the other instances of each harmful outcome and harmful factor.

Limitations of Root Cause Analysis

RCA is one of the most widely used methods to improving patient safety, but few data exist that uphold its effectiveness.[5] The quality of RCA varies across facilities, and its effectiveness in lowering risk or improving medical safety has not been systematically established.[5] The quality of RCA is dependent on the accuracy of the input data as well as the capability of the RCA team to appropriately use these data to create an action plan.[5] In some cases, only one source of error or a few sources of error are emphasized, when in reality the situation might be more complex. The thoughts, conversations, and relationships of members play an important role in determining the effectiveness of an RCA team.[5] People tend to select and interpret data to support their prior opinions. An atmosphere of trust, openness, and honesty is critical to encourage members to share what they know without fear of being criticized or unacknowledged. In addition, RCA lacks the ability to allow one to determine the probability, criticality, and severity of events, which can be useful for prioritizing management and preventing future undesirable events.[5] RCA can be very time-consuming because of all the time required for data gathering, as the accuracy of the research is crucial.[5] Organizations should ensure that adequate resources, time, and feedback are sufficiently provided during the RCA process so that the team will be able to carry out its task effectively.[5]

See also


  1. ^ Wilson, Paul F.; Dell, Larry D.; Anderson, Gaylord F. (1993). Root Cause Analysis: A Tool for Total Quality Management. Milwaukee, Wisconsin: ASQ Quality Press. pp. 8–17. ISBN 0-87389-163-5. 
  2. ^ Jens Rasmussen, Annelise M. Pejtersen, L.P.Goodstein (1994). Cognitive Systems Engineering. John Wiley & Sons. ISBN 0471011983. 
  3. ^ "The Management Oversight and Risk Tree (MORT)". International Crisis Management Association. Retrieved 1 October 2014. 
  4. ^ Entry for MORT on the FAA Human Factors Workbench
  5. ^ a b c d e f g Shaqdan K, Aran S, Daftari Besheli L, Abujudeh H. Root-cause analysis and health failure mode and effect analysis: two leading techniques in health care quality assessment. J Am Coll Radiol. 2014 Jun; 11(6):572-9