• Inadequate Batch Records: Batch records that do not detail the source, quality, or specifications of APIs.
• Inspection Findings: Regulatory inspectors flagging documentation discrepancies during audits.
• Supplier Issues: Non-compliance issues raised by suppliers regarding documentation.
• Quality Control Failures: Increased incidence of deviations or out-of-specification results linked to improperly sourced APIs.
• Employee Feedback: Reports of confusion among staff regarding documentation requirements during API procurement.

Likely Causes

Understanding potential causes of documentation misalignment is critical. Here’s a categorization framework:

• Materials: Incomplete supplier Dossiers, poorly defined API specifications, or lacking Certificates of Analysis (CoA).
• Method: Ineffective processes for reviewing and approving API documentation; unclear SOPs.
• Machine: Systems used for logging and storing documentation may lack integration or be non-compliant.
• Man: Poor training of personnel responsible for documentation practices or misunderstandings of WHO standards.
• Measurement: Inaccurate or subjective assessments of documentation accuracy.
• Environment: Cultural issues within the organization discouraging proper documentation and adherence to standards.

Immediate Containment Actions (First 60 Minutes)

Upon identification of misaligned documentation, immediate containment actions are necessary:

1. Assemble a crisis response team comprising representatives from QA, QC, and Regulatory.
2. Cease production of any batches associated with the non-compliant documentation until resolution.
3. Isolate affected records and communicate findings to all relevant stakeholders in real-time.
4. Conduct a preliminary review to gauge the scope and magnitude of the documentation issues.
5. Document all containment actions taken in a corrective action log to maintain transparency.

Investigation Workflow

Data collection is paramount in the investigation process. Here is a workflow approach:

• Identify Affected Batches: Catalog all API batches that used the affected documentation.
• Review Batch Records: Thoroughly inspect batch records for accuracy and completeness.
• Gather Supplier Documentation: Verify the availability and alignment of relevant supplier documents (e.g., CoA, Specifications).
• Interviews: Conduct interviews with personnel involved in the API sourcing and documentation processes.
• Timeline Creation: Construct a timeline of events leading up to the identification of discrepancies.

Root Cause Tools

Utilizing structured root cause analysis tools is essential. Here are three tools recommended based on scenarios:

• 5-Why Analysis: Ideal for straightforward issues where a simple chain of inquiry can uncover underlying causes.
• Fishbone Diagram: Useful for visualizing complex problem areas that may involve multiple contributing factors across categories (Materials, Methods, etc.).
• Fault Tree Analysis: Best when dealing with multifaceted failures requiring a comprehensive breakdown of events leading to documentation discrepancies.

CAPA Strategy

Corrective and Preventive Actions (CAPA) are critical for addressing identified issues and preventing recurrence. The CAPA strategy includes:

• Correction: Immediate rectification of the identified documentation issues to align with WHO requirements.
• Corrective Action: Implement systemic changes to ensure all future API sourcing aligns with WHO documentation standards. This may include revising SOPs and supplier agreements.
• Preventive Action: Establish ongoing training programs for staff to keep them updated on evolving regulatory expectations and documentation practices.

Control Strategy & Monitoring

To maintain ongoing compliance, a robust control strategy must be developed. Key elements include:

• Statistical Process Control (SPC): Implement SPC techniques to monitor documentation practices continuously.
• Sampling Plans: Create risk-based sampling plans for documentation review to verify compliance regularly.
• Monitoring Alarms: Set up alerts for recurring discrepancies in sourcing documentation that may signal endemic issues.
• Verification Processes: Establish routine verification processes to double-check documents at each stage of the sourcing cycle.

Validation / Re-qualification / Change Control Impact

When documentation practices shift, the following validation and change control measures may be necessary:

Related Reads

• Achieving QMS Compliance in the Pharmaceutical Industry
• Ensuring Audit Readiness and Successful Regulatory Inspections in Pharma

• Re-validation: If significant changes are made to sourcing or documentation processes, re-validation of these practices should be undertaken.
• Change Control: Ensure all proposed changes go through a formal change control procedure to assess their potential impact on compliance.
• Documentation of Changes: Maintain thorough records of all changes and their justification for inspections.

Inspection Readiness: What Evidence to Show

During inspections, the following documentation should be readily available to demonstrate compliance:

• Records of All Actions Taken: Maintain a log of all corrective and preventive actions, along with timeline documentation.
• Training Records: Document training completion for all employees responsible for API sourcing and documentation.
• Batch Documentation:** Ensure complete and accurate batch documentation is retrievable for all API sourced products.
• Deviation Logs: Keep records of any deviations related to sourcing documentation and the resolution of these issues.