From Root Cause to Real Cause

root-cause-analysis-qms

Let’s face it; nothing new can be said about root cause analysis (RCA). Standard RCA techniques have been around for decades, and before them being documented and referred to as RCA techniques, they were being employed. It is human to ask why. While it may not be human to ask why five times, it is natural to get to the bottom of problems. Unfortunately, in the regulated world of medical device and pharmaceutical manufacturing, there is a temptation to require intense documentation to prove that not only was the real root cause found but that it was accomplished by following strict processes. The emphasis on establishing the work was done often takes away from real RCA and actual problem-solving.

When MDIC’s Case for Quality took on the Make CAPA Cool project, the intent was to remove barriers to RCA and problem-solving. Engineers voiced frustration that they were spending most of their time in meetings and completing documentation during root cause investigations and spending very little time genuinely solving problems.

To solve a problem and prevent it from recurring, the actual cause must be found. This process isn’t always easy, and from time to time, the results can be inconvenient. Every RCA has two strikes against it before it begins. 1. Getting to the real cause takes time and resources 2. Sometimes the root cause identified is too broad for real problem solving to work.

  1. Getting to the real cause takes time and resources. True. Of course, recalls take time and resources. Consider, though, that RCA is Recall Prevention. If you perform RCA on a problem that never results in a recall, consider whether the effort is worth the time. Those are great opportunities to free up your engineers to go ahead and solve the problem-free from the documentation burden that often comes with CAPA. If the problem you are trying to solve could have resulted in a recall, had it not been caught, then put as much effort into the RCA as you would into a recall investigation. Assemble the investigation team as you would a product recall team. Regulatory, product design, manufacturing, quality engineering, and QA should all be involved. If it makes sense, include any other functions close to the problem, such as sterilization or supplier management. The key is to not view the RCA as an exercise in making things look right to an auditor. Rebrand RCA as Recall Prevention and get to work identifying and preventing the real cause of the problem.
  2. The root cause identified is too broad for real problem-solving. Sometimes the initial root cause is product design, a failure of a quality system element, or something else with broad implications. When general systems are implicated in root cause analysis, it is likely a sign that the RCA team is lacking appropriate subject matter experts. It does not mean that there aren’t occasions when the product design is the cause of failures or that fundamental quality system elements cannot fail. But given the rigor of product verification and validation required to get a product to market, these situations should be rare. Including the product design team in the RCA can help in these situations. If your company has an RCA, Product or Medical Specialists should be involved. If an overall system is implicated, include those experts in the RCA team regarding training, supplier quality, SOP writing, etc., before finalizing your root cause. Those closest to the problem are the most knowledgeable and have skin in the game, making them most likely to identify the actual cause.

QMS for Life Science Industry

Compliance Group QMS Software is a SaaS (Software as a Service) based  application designed especially for life science industries in alignment with the compliance regulations (21 CFR Part 11, ISO 9001:2015). It has a power-packed QMS (Quality Management System), and DMS (Document Management System) interlinked and integrated with analytics. The platform is user-friendly and straightforward with clever configurational aspects as per the needs of an organization and the industry type and built to scale and pay per use model.

Connect with Compliance Group today at sales@complianceg.com or call (847) 327-3167, Ext. 406.

Contact Us

FAQ's

What are RCA and CAPA?

RCA is Root Cause Analysis, the most crucial step in the CAPA process. When we encounter a problem or defect in the process, product, or function, we try to find its real cause to take necessary Corrective and Preventive Actions and ensure the problem does not recur.

CAPA – Corrective Action and Preventive Action.

When a problem occurs, correction is done to rectify the situation. Corrective action is the immediate action taken to resolve the issue. Corrective action is reactive. Preventive measure is to be aware of the potential problem and its real cause and take proactive action to prevent its recurrence.

How does root cause analysis helps maintain the quality management system of the company?

RCA is a tool in QMS that helps organizations retrospectively investigate and conclude the potential and undesirable causes that led to the occurrence of the problem. With this analysis, organizations can bring in corrective and preventive measures to improve patient safety by preventing the issue from recurrence. In addition, an effective RCA tool enables the implementation of a solution that addresses the problem at its source of cause.

What are the significant steps involved in root cause analysis?

The RCA goal is to drill down to the real cause of the problem and determine the action plan to prevent its recurrence. So, RCA is a comprehensive methodology that includes problem-solving measures to identify the actual cause of a Non-conformance or CAPA.

Significant steps in RCA

Identify the Issue – Identify the issue that occurred and document the accurate information like the scope and source of the case and how it happened to clarify the problem.

Identify the Cause – Identify the potential cause of the problem. This step aims to uncover the potential causes as many as possible that can cause the problem to get to a more profound understanding of the problem.

Identify the Actual Cause – The step uncovers the actual cause that led to the occurrence of the issue. There are several tools used in the Quality Management system for this step.

Five Why’s

  • Histogram
  • Fault Tree
  • Scatter Chart
  • Cause and Event Tree
  • Pareto Analysis

Identify the solution and take action – In the final step, identify the actual cause, determine the resolution and implement it to correct and prevent the issue from recurring.