Pharmaceutical QC Analysis Complete

Step 1.2 -- Product Specification Inventory

Build the specification landscape from data structures:

Step 1.3 -- Test Method Inventory

Catalog all analytical methods:

Techniques to identify: HPLC, GC, UV-Vis, FTIR, dissolution, Karl Fischer, titration, endotoxin (LAL/rFC), microbial limits, sterility testing, particulate matter, elemental impurities (ICP-MS/ICP-OES).

Step 1.4 -- Data Integrity Baseline

Assess ALCOA+ compliance in the QC laboratory systems:

• Attributable: every result linked to analyst, instrument, and sample ID.
• Legible: data readable, permanent, not overwritten without audit trail.
• Contemporaneous: recorded at time of activity (not backdated).
• Original: first-capture data preserved (electronic raw data or paper original).
• Accurate: verified through review and approval workflow.
• +: Complete (all data present), Consistent (no contradictions), Enduring (not degrading), Available (retrievable for inspection).

============================================================ PHASE 2: OOS INVESTIGATION ANALYSIS

Evaluate Out-of-Specification investigation practices per FDA guidance (2006):

Step 2.1 -- OOS Metrics

Calculate OOS performance indicators:

• OOS rate by product, test, and laboratory.
• OOS rate trending: increasing (process deterioration), stable, or decreasing (improvement).
• Phase I (laboratory investigation) vs Phase II (manufacturing investigation) outcome distribution.
• Average investigation closure time (days).
• Confirmed OOS rate after investigation vs initial OOS rate.
• OOS outcomes: batch rejection, reprocessing, or release with justification.

Step 2.2 -- Phase I Laboratory Investigation Quality

Evaluate laboratory investigation rigor:

• Is analyst error properly investigated with specific evidence (not just assumed)?
• Are sample preparation steps, dilution calculations, and instrument checks documented?
• Is original data preserved and reviewed before any retesting?
• Are investigation hypotheses specific and testable (not generic "possible analyst error")?
• Are investigations completed within regulatory timeframes?

Step 2.3 -- Phase II Manufacturing Investigation Quality

When Phase I is inconclusive, evaluate extended investigation:

• Manufacturing process parameter review completeness.
• Raw material lot investigation and supplier quality data.
• Environmental condition review (temperature, humidity excursions).
• Equipment and facility assessment.
• Root cause determination quality: specific cause identified vs "could not determine" (flag frequency of inconclusive investigations).

Step 2.4 -- Retesting and Resampling Practices

Assess compliance with FDA OOS guidance on retesting:

• Number of retests is scientifically justified and pre-defined (not "test until passing").
• Resampling is justified and documented per FDA guidance criteria.
• Statistical treatment of original and retest results follows accepted methodology.
• Averaging rules: original OOS results are NOT averaged with passing retests without statistical justification.
• Clear, documented criteria for invalidating original results.

Step 2.5 -- OOS Pattern Detection

Identify systemic OOS patterns:

• Same test/method generating disproportionate OOS rates (method issue vs product issue).
• Same analyst or instrument associated with higher OOS frequency.
• Seasonal or temporal patterns (humidity-sensitive tests, temperature-dependent methods).
• Products testing near specification limits: process capability issue, not lab issue (Cpk analysis).
• OOT (Out-of-Trend) preceding OOS: are early warning signals being missed?

============================================================ PHASE 3: STABILITY PROGRAM ANALYSIS

Evaluate stability program per ICH Q1A-Q1E:

Step 3.1 -- Program Design

Assess completeness:

• Annual stability commitment met (minimum 1 batch/year/product/strength)?
• ICH storage conditions covered: 25C/60%RH (long-term), 30C/65%RH (intermediate), 40C/75%RH (accelerated).
• Photostability studies completed per ICH Q1B for applicable products.
• In-use stability studies for multi-dose products.
• Forced degradation/stress testing data available for degradation pathway understanding.

Step 3.2 -- Stability Trending Analysis

Analyze stability data trends:

• Regression analysis on stability-indicating results (assay, impurities, dissolution).
• Shelf life estimates calculated using ICH Q1E statistical approaches.
• Products with trends approaching specification limits before labeled expiry.
• Confirmed OOT stability results flagged and investigated.
• Batch-to-batch degradation rate consistency comparison.

Step 3.3 -- Shelf Life Validation

Assess shelf life data support:

• Is labeled shelf life supported by long-term real-time stability data?
• Any products with shelf life based solely on accelerated data (higher risk)?
• Post-approval stability data confirming original registration filing data.
• API retest period adequately supported by stability data.
• Container closure system changes reflected in updated stability protocols.

Step 3.4 -- Stability-Indicating Method Validation

Verify stability methods detect degradation:

• Forced degradation study demonstrates acceptable mass balance.
• Degradation products chromatographically resolved from main analyte peak.
• Specificity demonstrated for each degradation pathway (acid, base, oxidative, thermal, photolytic).
• Method sensitivity sufficient to quantify degradants at specification limits.
• Known and unknown impurity quantification capability validated.

============================================================ PHASE 4: METHOD VALIDATION STATUS

Evaluate analytical method validation per ICH Q2(R2) and USP <1225>:

Step 4.1 -- Validation Status Audit

For each analytical method, verify validation parameter coverage:

Step 4.2 -- Compendial Method Verification

For USP/EP compendial methods, confirm verification per USP <1226>:

• Specificity verified for the specific product matrix.
• Precision and accuracy demonstrated using in-house equipment and analysts.
• System suitability criteria established and routinely met.
• Verification documented and approved through QMS.

Step 4.3 -- Method Transfer Assessment

Evaluate method transfers between laboratories:

• Transfer protocols with pre-defined, justified acceptance criteria.
• Equivalence demonstrated statistically (not just "results within spec").
• Statistical comparison: F-test for precision, t-test for accuracy between sending and receiving lab.
• Ongoing method performance monitoring post-transfer.

Step 4.4 -- Method Lifecycle Management

Assess per ICH Q14 (analytical procedure lifecycle):

• Method performance monitoring: system suitability trending, control chart tracking.
• Analytical Target Profile (ATP) defined for each method?
• Continuous improvement framework: method updates driven by performance data.
• Method change management linked to change control system (not ad hoc modifications).

============================================================ PHASE 5: RELEASE TESTING OPTIMIZATION

Step 5.1 -- Testing Turnaround Time

Map the release testing timeline:

• Sample receipt to results availability, per test.
• QC review and approval cycle time.
• QA batch release decision timeline.
• Total time from batch completion to market release.
• Bottleneck tests: which tests have the longest turnaround?

Step 5.2 -- Test Redundancy Analysis

Identify opportunities to reduce testing burden:

• Tests duplicated at IPC (in-process control) and release: can IPC data support release decision?
• Skip-lot testing eligibility based on demonstrated process capability and quality history.
• Reduced testing via statistical sampling plans (ANSI/ASQ Z1.4).
• Parametric release candidates (e.g., terminally sterilized products).
• Real-Time Release Testing (RTRT) candidates per ICH Q8 QbD framework.

Step 5.3 -- Laboratory Efficiency

Evaluate lab operational metrics:

• Instrument utilization rates (idle time, queuing time, active testing time).
• Analyst productivity metrics (tests per analyst-day).
• Sample scheduling optimization (batching similar tests, instrument sharing).
• Reagent and reference standard waste reduction.
• Out-of-hours testing frequency and cost justification.

Step 5.4 -- Specification Review

Assess specification appropriateness:

• Specifications aligned with process capability (Cpk-based assessment)?
• Specifications reflect clinical relevance (patient-centric limits)?
• Unnecessary tests that could be eliminated with regulatory justification?
• Specifications harmonized across markets where feasible?
• ICH Q6A (chemical) / Q6B (biological) decision trees applied for specification setting?

============================================================ SELF-HEALING VALIDATION (max 2 iterations)

After producing output, validate data quality and completeness:

1. Verify all output sections have substantive content (not just headers).
2. Verify every finding references a specific file, code location, or data point.
3. Verify recommendations are actionable and evidence-based.
4. If the analysis consumed insufficient data (empty directories, missing configs), note data gaps and attempt alternative discovery methods.

IF VALIDATION FAILS:

• Identify which sections are incomplete or lack evidence
• Re-analyze the deficient areas with expanded search patterns
• Repeat up to 2 iterations

IF STILL INCOMPLETE after 2 iterations:

• Flag specific gaps in the output
• Note what data would be needed to complete the analysis

============================================================ OUTPUT

Pharmaceutical QC Analysis Complete

• Products evaluated: [count]
• Methods assessed: [count]
• OOS investigations reviewed: [count]
• Stability data points analyzed: [count]

QC Health Dashboard

Risk-Prioritized Findings

• Critical: findings affecting product quality or patient safety.
• Major: regulatory compliance gaps.
• Minor: efficiency improvements.
• Observations: industry best practice recommendations.

Prioritized Recommendations

1. {highest-impact recommendation}
2. {second recommendation}
3. {third recommendation}

DO NOT:

• Modify any QC results, LIMS entries, or approved analytical data.
• Recommend invalidating OOS results without proper scientific justification and documented criteria.
• Average OOS results with passing results unless statistically justified per FDA guidance.
• Overlook data integrity concerns when analytical results are within specification -- integrity is independent of result value.
• Recommend eliminating release tests without noting the regulatory filing implications (supplement or variation required).
• Write analysis reports to disk -- output findings directly in the response.

NEXT STEPS:

• "Run /pharma-compliance to assess overall regulatory inspection readiness."
• "Run /batch-optimization to correlate yield issues with QC trend data."
• "Run /lab-automation to evaluate opportunities for laboratory workflow automation."

============================================================ SELF-EVOLUTION TELEMETRY

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md in that memory directory

Entry format:

### /pharma-quality-control — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}

Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.