Root cause corrective actions

Cause analysis is usually divided into three types (1) direct causes (2) contributing causes and (3) root causes. The direct cause of an incident is the immediate event or condition that caused the incident. Contributing causes are events or conditions that collectively increase the likelihood of the direct cause but that are not the main factors causing the incident. Root causes are the events or conditions underlying the root cause. Corrective measures for root causes will prevent the recurrence of the incident. In simple cases, root causes include materials or equipment deficiencies or their inappropriate handling. More complex examples are management failures, inadequate competencies, omissions, nonadherence to procedures, and inadequate communication. Root causes can be typically attributed to an action or lack of action by a group or individual. 

If yes, for each incident, attach the incident report or give the following information Description of the incident, chronology of verifiable events, other pertinent facts, root causes and contributing factors, and proposals for corrective action. 

Check whether a documented system is in place, which covers the reporting, investigation, root cause analysis and corrective actions taken. 

As stated previously, traceability is fundamental to establishing and eliminating the root cause of nonconforming product and therefore it should be mandatory in view of the requirements for Corrective Action. Providing traceability can be an onerous task. Some applications require products to be traced back to the original ingot from which they were produced. In situations of safety or national security it is necessary to identify product in such a manner because if a product is used in a critical application and subsequently found defective, it may be necessary to track down all other products of the same batch and eliminate them before there is a disaster. It happens in product recall situations. It is also very important in the automobile and food industries in fact, any industry where human life may be at risk due to a defective product being in circulation. 

Once you have identified the root cause of the nonconformity you can propose corrective action to prevent its recurrence. Eliminating the cause of nonconformity and preventing the recurrence of nonconformity are essentially the same thing. The key to successful diagnosis of causes is to keep asking the question why When you encounter a don t know then continue the investigation to find an answer. 

Ensure corrective actions address root causes violations are identified... 

Root cause 3. Corrective action not yet implemented management had been aware of problems with the vessel and solvent banks but had done nothing about it. 

Nonconformity evaluations ensure that the root causes of any failures are identified and corrected. This ties in closely with Corrective Action. 

Thorough investigations should be conducted according to a predetermined SOP to ensure that the root cause is identified, if not already obvious. Once this has been done, a corrective action plan must be agreed and the process closed out by verifying that the corrective or preventative action has been implemented effectively. 

Improvement - Implement Corrective Action, Preventative Action (CAPA) procedures, incorporating root cause investigation... 

Consider again a batch polymerization process where the process is characterized by the sequential execution of a number of steps that take place in the two reactors. These are steps such as initial reactor charge, titration, reaction initiation, polymerization, and transfer. Because much of the critical product quality information is available only at the end of a batch cycle, the data interpretation system has been designed for diagnosis at the end of a cycle. At the end of a particular run, the data are analyzed and the identification of any problems is translated into corrective actions that are implemented for the next cycle. The interpretations of interest include root causes having to do with process problems (e.g., contamination or transfer problems), equipment malfunctions (e.g., valve problems or instrument failures), and step execution problems (e.g., titration too fast or too much catalyst added). The output dimension of the process is large with more than 300 possible root causes. Additional detail on the diagnostic system can be found in Sravana (1994). 

CE has suffered from an assortment of common operator errors, which in turn have characterized the technique as not being robust. Like any analytical piece of equipment, there can be hardware and chemistry/operator issues. CE requires a keen background and user knowledge of the technique so as to avoid common problems that may initially be diagnosed as instrumental issues. For the early user of CE, the table below lists some common problems followed by their root causes and corrective actions. Following the suggested corrective actions should help the beginner get the maximum performance out of the CE instrumentation. 

Once all of the root causes are identified, the investigator is ready to develop the corrective actions, as described in Chapter 10. 

Structured root cause analysis uncovers the underlying reasons for human error and consequently provides guidance on suitable corrective actions. Humans make errors. Our task is to design systems that detect and correct an error before it leads to a serious consequence. Chapter 6 provides extensive information applicable during root cause analysis. 

The laboratory shall establish a policy and procedure and shall designate appropriate authorities for implementing corrective action when nonconforming work or departures from the policies and procedures in the quality management system or techiucal operations have been identified. The procedure for corrective action shall start with an investigation determining the root cause(s) of the problem. 

If the root cause is assignable, corrective action needs to be taken and documented. If three consecutive runs over action levels occur, a problem analysis corrective action report (PACAR) must be issued. 

The root cause is assignable corrective action needs to be taken and documented. 

Corrective actions PAT opens the door for new tools for root cause investigations and data collection in production Manufacturing Science provides the foundation for more effective approaches CGMP initiative objective f-5 Product is out of specification (OOS) or procedural deviations Crisis —immediate action needed Required by regulators... 

Root cause analysis with corrective action to help understand the cause of the deviation and prevent recurrence of a similar problem... 

A corrective action is initiated to correct the cause of an identified nonconformity and to prevent it or similar problems from reoccurring. It may include initial and follow-up actions (e.g., conducted after root cause analysis). Current quality system models and the cGMP regulations emphasize corrective actions and require that actions be documented. Under current quality system models, preventive actions include actions taken in response to quality data to address the cause of potential nonconformities to prevent their occurrence. An effective CAPA system therefore includes both reactive and proactive components. The effectiveness of corrective and preventive actions should be evaluated using objective criteria when possible and the evaluation documented. 

Subsection 4.11 of the standard gives details the approach for identifying the root causes of nonconformance and explains how to select and implement actions to correct the problem. 

When nonconformances occur, the corrective action plan is activated. Anyone seeing the need for corrective action is responsible for reporting the problem to the proper supervisor or manager. Merely correcting the particular unsatisfactory product does not achieve corrective action. If possible, the root cause of the unsatisfactory condition is determined, and a proposed remedy is put in place. The effectiveness of the corrective action is verified. 

The balance of participants time is spent studying the Dowville case and preparing team reports to be delivered at the end of the workshop. In the reports, the team identifies the root causes of the Dowville incident, identifies deficiencies in Dowville s S/LP/S programs that allowed the root causes to exist, and recommend actions to correct those deficiencies. The team presentations are judged by a panel of managers with one report selected as the winner. 

If the observed error rate in the sample is equal to or less than the predefined acceptable level, no further action is required. Nevertheless, it is recommended that the opportunity be taken to correct any errors found and to investigate any commonalties between the errors, to identify any root cause that might affect the rest of the data population. 

Software control deficiencies (lack of control on software configuration settings, software put into production with contaminant decision logic package errors, lack of root cause and preventative/corrective action, etc.)... 

Stratified sampling is more likely to reveal uniformity problems than if less discriminating methods were used. A tool was developed and published (84) to aid formulation and process development scientists in troubleshooting content uniformity problems. The approach is that if stratified sample results were available for blend and/or product samples, the data will point the troubleshooter towards potential causes for uniformity problems in rank order of likelihood. Once potential root causes have been identified, areas for further investigation and possible corrective actions are also presented. 

Once possible root causes have been identified, the next step is to perform additional analyses to confirm the primary root cause. Once the primary root cause has been confirmed, corrective actions can be taken. 

---