FEATURED BLOG

Lou Conheady

Recent Posts

Root Cause Analysis in Healthcare

Posted by Lou Conheady on Thu, Mar 26, 2015 @ 13:03 PM

Author: Gary Tyne CMRP

Following the release of a report by economic consultants Frontier Economics(Oct 2014), it was highlighted that the cost of errors in patient safety, which includes the cost of extra treatment, bed space and nursing care as well as huge compensation pay-outs, costs the NHS between £1billion and £2.5billion a year.

In a speech to staff at Birmingham Children's Hospital (Oct 2014), Jeremy Hunt (Health Secretary) said:

hospital“World class care is not just better for patients it reduces costs for the NHS as well. More resources should be invested in improving patient care rather than wasted on picking up the pieces when things go wrong.”

As far back as 2010 Dame Christine Beasley,  chief nursing officer for England said “using Root Cause Analysis (RCA) tools to understand adverse events is “critical” to improving safety across the NHS.”

The National Patient Safety Agency (NPSA) developed a set of root cause analysis guidelines and instruction documents which were taken over by the NHS Commissioning Board Special Health Authority in 2012.

Although the NPSA did not identify a specific RCA process to be used the toolkit advocates the use of the Fish-bone or Ishikawa diagram as a key tool for identifying contributory factors and root causes. Another method utilized within the NHS is a method called ‘5 Whys’

Whilst both Fishbone and 5 Whys are tools that can be utilized in basic problem solving, both methods have received criticism from within other industries for being too basic and not complex enough to analyze root causes to the depth that is needed to ensure that solutions are identified and the problem is fixed.

There are several reasons for this criticism:

  • Tendency for investigators to stop at symptoms rather than going on to lower-level root causes
  • Inability to go beyond the investigator’s current knowledge – cannot find causes that they do not already know
  • Lack of support to help the investigator ask the right “why” questions
  • Results are not repeatable – different people using Fishbone and 5 Whys come up with different causes for the same problem
  • Tendency to isolate a single root cause, whereas each question could elicit many different root causes
  • Considered a linear method of communication for what is often a non-linear event

Many companies we work with successfully utilize the 5 Why technique or Fishbone for very basic incidents or failures. By utilizing the correct placement of triggers, organizations can use the 5 Why or Fishbone for its basic problem solving and then move to a form of Cause and Effect analysis like the Apollo Root Cause Analysis methodology for more complex problems.

A disciplined problem solving approach should push teams to think outside the box, identifying root causes and solutions that will prevent reoccurrence of the problem, instead of just treating the symptoms.

Apollo Root Cause Analysis methodology – A New Way of Thinking

ApolloFourSteps

 

 

 

 

 

 

 

 

The Apollo Root Cause Analysis methodology provides a simple structured approach that can be applied by anyone, at any time on any given event. One of its most powerful attributes is its ability to create a common understanding of contributing causes, and provide a platform to explore a range of creative solutions. Through a simple charting process, everyone involved in an investigation can contribute which generates enthusiasm for the process, resulting in positive problem solving outcomes and experiences.

The key factor for successful problem solving is the inclusion of cause and effect as part of the analytical process.

Root Cause analysis identifies causes, so that solutions are based on controlling those causes, rather than treating the symptoms.

There are many features of the Apollo Root Cause Analysis methodology which naturally fit within any Problem Solving Excellence program.

The Apollo Root Cause Analysis methodology was developed in 1987 by Dean Gano and is utilized across the world in various industries from petrochemical, aerospace, utilities, manufacturing, healthcare and others.

The Apollo Root Cause Analysis process is a 4-step method for facilitating a thorough incident investigation. The steps are:

  • Define the Problem
  • Analyze Cause and Effect Relationships
  • Identify Solutions
  • Implement the Best Solutions

The Apollo Root Cause Analysis methodology is supported by software called RealityCharting™ which is available in full version (standalone or enterprise) or as RealityCharting™ Simplified. The RealityCharting Simplified can be utilized on smaller issues and allows the user to build a cause and effect chart that is no greater than 4 causes high and 5 causes deep. This allows the user of a 5 Whys approach the ability to create a chart using the same thought process adopted in the Apollo Root Cause Analysis methodology. It also demonstrates a non-linear output to what was originally considered a linear type problem.

Training in the NHS

In the study titled: ‘Training health care professionals in Root Cause Analysis: a cross-sectional study of post-training experiences, benefits and attitudes’ by Bowie, Skinner, de Wet. A few interesting statistics begin to arise when it comes to training of RCA with the respondents.

When asked ‘What type of training did you receive?’ 81.1% of respondents had said they had received in-house training compared to 6.6% who had received external training.

When asked ‘How long was the training?’ 89% of respondents said they had less than one day training compared to 1.3% who had received more than 2 days.

From industry experience these statistics are quite surprising and can only contribute to poor quality investigations with low prevention success.

Within industry, Apollo Root Cause Analysis methodology trained facilitators are required to take minimum two day in-class training course with a follow up exam. This is also supported by a pathway for accreditation. RCA participants are given awareness training of the Apollo Root Cause Analysis methodology but only the trained facilitators can lead investigations.

Case Study

bandage

A National Health Service Trust hospital was experiencing patient complaints and was exceeding waiting time targets in the antenatal clinic. Several solutions had previously been implemented to solve this problem. However, the problem continued and it was therefore decided to run a thorough investigation utilizing the Apollo Root Cause Analysis methodology.

The root causes of the problem were identified during the investigation along with effective solutions. The solutions were implemented over a period of time. With the solutions implemented an immediate improvement was seen and   waiting time targets were being met.

“We had tried to solve this problem on a number of occasions and stress levels were increasing within the antenatal team. We had previously only dealt with the symptoms and not the root causes. Only after applying the Apollo Root Cause Analysis methodology were we able to see the evidence based causal relationships. I found the tool simple but effective and one that should be utilized in other areas across the NHS” – Midwife/Deputy Manager, Antenatal Clinic, NHS Trust Hospital

Conclusion

In the study titled ‘The challenges of undertaking root cause analysis in health care’ by Nicolini, Waring, and Mengis, (2011) it was concluded that:

“Health services leaders need to provide open endorsement of root cause analysis and of the staff carrying it out; enhance staff participation within learning activities and new analytic tools; and develop capabilities in change management”

Apollo Root Cause Analysis methodology has been taught to well over 100,000 people worldwide over the last 22 years. It has become known as the preeminent RCA methodology and is used in many fortune 500 companies and US government agencies like the Federal Aviation Authority and NASA.

If you are interested in what the Apollo Root Cause Analysis methodology can do for you and would like further information on the methodology please visit the website: http://www.apollorootcause.com

 

 publictraining

 

 

Topics: Root Cause Analysis in Healthcare

Top 6 Sure-Fire Ways to Kill off a Root Cause Analysis Program

Posted by Lou Conheady on Wed, Sep 24, 2014 @ 15:09 PM

Author: Jack Jager

An effective root cause analysis process can improve business outcomes significantly. Why is it then that few organisations have a functioning root cause analysis process in place? 

Here are the top 6 sure-fire ways to kill off a Root Cause Analysis program

1. Don’t use it.

stop-hand

The company commits to the training, creates an expectation of use and then doesn’t follow through with commitment, process and resources! Now come on, how easy is it to devalue the training and deliver a message that the training was just to tick someone’s KPI box and that the process doesn't really need to be used.

2. Don’t support it.

Success in Root Cause Analysis would be the ultimate goal of each and every defect elimination program. To achieve success however, requires a bit more than just training people in how to do it. It requires structures that initially support the training, that mentor and provide feedback on the journey towards application of excellence and thereafter have structures that delineate exactly when an investigation needs to take place and that delivers clear support in terms of time and people to achieve the desired outcome. Without support for the chosen process the expected outcomes are rarely delivered.  

3. Don’t implement solutions.

To do all of the work involved in an investigation and then notice that there have been no corrective actions implemented, that the problem has recurred because nothing has changed, has got to be one of the easiest ways to kill off a Root Cause Analysis process. What happens when people get asked to get involved in RCAs or to facilitate them when the history indicates that nothing happens from the efforts expended in this pursuit? “I’m too busy to waste my time on that stuff!”  

 

4. Take the easy option and implement soft solutions.

Why are the soft controls implemented instead of the hard controls? Because they are easy and they don’t cost much and we are seen to be doing something about the problem. We have ticked all the boxes. But will this prevent recurrence of the problem? There is certainly no guarantee of this if it is only the soft controls that we implement. We aren’t really serious about problem solving are we, if this is what we continue to do?   

5. Continue to blame people.

The easy way out! Find a scapegoat for any problem that you don’t have time to investigate or that you simply can’t be bothered to investigate properly. But will knowing who did it, actually prevent rectraining your staff urrence of the problem?

Ask a different question! How do you control what people do? You control them or more correctly their actions by training them, by putting in the right procedures and protocols, by providing clear guidelines into what they can or can’t do, by creating standard work    instructions for everyone to follow and by clearly establishing what the rules are in the work place that must be adhered to.

What sort of controls are these if we measure them against the hierarchy of controls? They are all administrative controls, deemed to be soft controls that will give you no certainty that the problem will not happen again. We know this! So why do we implement these so readily? Because it is the easy way out! It ticks all the boxes, except the one that says “will these corrective actions prevent recurrence of the problem?”

We all understand the hierarchy of controls but do we actually use it to the extent that we should?  

6. We don’t know if we are succeeding because we don’t measure anything.

You get what you measure! When management don't implement or audit a process for completed RCAs it sends a strong message that there is no interest, or little, in the work that is being done to complete the analysis.

Tracking KPIs like, how many RCAs have been raised against the triggers set? How many actions have been raised in the month as a result and, of those actions raised, how many have been completed? If management is not interested in reviewing these things regularly along with the number of RCAs subsequently closed off in a relevant period, then it won't be long before people notice that no one is interested in the good work being done.

The additional work done to complete RCAs will not be seen as necessary, as it's not important enough to review and the work or the effort in doing this will then drop away until it's no longer done at all.

measuring success

Another interesting point is that if only the number of investigations is reported, and there is no check on the quality of the analysis being completed, then anything can be whipped up as no one is looking! If a random audit is completed on just one of the analyses completed in a month then this implies that the quality of the analysis is important to the organisation. 

What message do we send if we don’t measure anything?

 

 

In closing, the first step on the road to implementing an effective and sustainable Root Cause Analysis program is to pinpoint what's holding it back. These Top 6 sure-fire ways to kill off a Root Cause Analysis program will help you identify your obstacles, and allow you to develop a plan to overcome them. 

 

Webinar Elements to Sustain a RCA Program
 

 

Topics: root cause analysis, rca success, rca skills, root cause analysis skills, root cause investigation, root cause of success, root cause analysis tips, success definition, root cause analysis program

How to Judge the Quality of an RCA Investigation

Posted by Lou Conheady on Tue, Sep 02, 2014 @ 14:09 PM

Author: Kevin Stewart

 
This question was posed to a discussion group and it got me thinking how do you grade an investigation?

The overall success will be whether the solution actually prevents recurrence of the problem.  One definition of Root Cause Analysis is: “A structured process used to understand the causes of past events for the purpose of preventing recurrence.” So a reasonable assessment of the quality of the analysis would be to determine whether the RCA addressed the problem it set out to fix by ensuring that it never happens again (this may be a lengthy process to prove if the MTBF of the problem is 5 years, or has only happened once). bigstock-Blank-checklist-on-whiteboard--68750128.jpg


Are there some other tangibles that can help you assess the quality of an RCA?  RCAs use some sort of process to accomplish their task. If this is the case then it would stand to reason that there will be some things you can look for in order to gauge the quality of the process followed. While this is no guarantee of a correct analysis, ensuring that due diligence was followed in the process  would lend more credibility to the solutions.


What are some of these criteria by which you can judge an analysis?


  • Are the cause statements ‘binary’? By this we mean unambiguous or explicit. A few words only and precise language use without vague adjectives like “poor” since they can be very subjective.

 

  • Are the causes void of conjunctions? If they have conjunctions there may be multiple causes in the statement. Words such as: and, if, or, but, because.

 

  • Is there valid evidence for each cause? If causes don't have evidence they may not belong in the analysis or worse yet solutions may be tied to them and be ineffective.

 

  • Does each cause path have a valid reason for stopping that makes sense? It is easy to stop too soon and is sometimes obvious. For example, if a cause of “no PM” has no cause for it so that the branch stops, it would seem that an analyst in most cases would want to know why there was no PM.

 

  • Does the structure of the chart meet the process being used? If it is a principle-based process then it should be easy to check the causal elements to verify that they satisfy those principles. These might be causal logic checks or space time logic checks or others that were associated with the particular process.

 

  • Is the chart or analysis completed? Does it have a lot of unfinished branches or questions that need to be answered or action items to complete?

 

  • Is the chart or analysis completed? Does it have a lot of unfinished branches or questions that need to be answered or action items to complete?

 

  • Are the solutions SMART (Specific, Measurable, Actionable, Relevant, and Timely)? Or do they include words like: investigate, review, analyze, gather, contact, observe, verify, etc.

 

  • Do the solutions meet a set of criteria against which they can be judged?

 

  • Do the solutions address specific causes or are they general in nature?  Even though they may be identified against specific causes if they don’t directly address those causes then it may still be a guess.

 

  • If there is a report, is it well written, short, specific and cover just the basics that an executive would be interested in? Information such as cost, time to implement, when will it be completed, a brief causal description and solutions that will solve the identified problem are the requisites.

 

These are some of the things that I currently look at when I review the projects submitted by clients. I’d be interested to know about other things that may be added to the list.

describe the image

Topics: root cause analysis, rca facilitator, rca success, rca skills, root cause analysis skills, rca facilitation, root cause investigation, critical rca skills, root cause of success, root cause analysis tips, facilitation skills