Investigating the cause of a quality failure or other production problem is something that all pharmaceutical companies must do some more frequently than others. The more comprehensive and structured the investigation process is, the more effective it will be.
Thats the consensus of consultants and other experts in the corrective and preventive action (CAPA) field. While CAPA is handled differently at many pharmaceutical manufacturers, best practices for handling complaints and investigations revolve around certain core activities, a basic process and, more often than not, some enabling technology.
The CAPA complaint root cause investigation process is paramount. Having a successful CAPA is more a cultural thing for a company than merely having the technology for CAPA, says Simon Jacobson, research analyst for manufacturing operations at AMR Research in Boston.
In Jacobsons view, most large pharmaceutical companies have more trouble breaking down the silos in which they might have several different CAPA processes and technologies being used in different departments and plants to achieve a single managed view of the process. Many pharmaceutical companies have installed several CAPA solutions, but there is no common way for them to do trending and put preventive action in place across the company, he says.
Surprisingly, smaller pharmaceutical firms often take a more systematic approach to handling CAPA complaints than larger companies. At single-site operations, people are more inclined to work together, so that, for instance, the R&D chief knows the manufacturing guy, Jacobson observes. But with the bigger companies, there are more silos and there is a greater need for a common, systematic approach to CAPA.
Often, CAPA problems can be traced to the lack of consistent process requirements and written procedures. Because of these inconsistencies across sites, companies may have to chase the same complaint at multiple facilities. This is preventing organizations from halting what could be systemic inefficiencies, Jacobson says. In addition, he says, The lack of an organization-wide systemic management process prevents a company from successfully auditing their processes and taking effective preventive actions, such as trending across multiple sites.
The four-step method
In most cases, a CAPA investigation is set in motion by an event either a laboratory investigation, a manufacturing inconsistency, a regulatory or internal audit, or a customer complaint. Any of these investigation records are entered into a CAPA system, which can spawn a related CAPA investigation, explains Robert Fetterman, president of Technical Business Solutions (Royers Ford, Pa.).
The majority of companies initiate their CAPA processes once a complaint or field failure is discovered, says AMRs Jacobson. This is not only too late because the patient is already at risk, but companies are hard pressed to comply with the FDAs CAPA requirements because they lack insight into the root cause of the device malfunction.
The CAPA process, of course, is broader than just the investigation of complaints. But investigation of the root cause of problems lies at its core. As Jacobson says, At the heart of a successful CAPA is a definition of the problem and an assessment of who, what and where is at risk, as well as the potential impact on the organization should the problem grow.
In general, CAPA experts recommend that root cause investigations follow a four-step process:
- Identify the problem.
- Evaluate its magnitude, which includes assessing risk.
- Investigate and assign responsibility.
- Analyze and document the root cause of the problem.
Tracking best practices
Fetterman is nearly completion of a project to install a CAPA solution globally at a major pharmaceutical firm. Were developing the system and rolling it out to all their 30 sites worldwide, he says. The firm is using Sparta Systems (Holmdel, N.J.) TrackWise quality management software package because it is easily customized, Fetterman says. It lends itself to quick configuration of workflows and modifications to meet the business needs. It also runs on the Oracle systems that are in use at many pharmaceutical companies, he says.