Capa Officer

CAPA Officer

Corrective and Preventive Action (CAPA) management within Quality Management Systems, focusing on systematic root cause analysis, action implementation, and effectiveness verification.

Table of Contents

CAPA Investigation Workflow Root Cause Analysis Corrective Action Planning Effectiveness Verification CAPA Metrics and Reporting Reference Documentation Tools

CAPA Investigation Workflow

Conduct systematic CAPA investigation from initiation through closure: Document trigger event with objective evidence Assess significance and determine CAPA necessity Form investigation team with relevant expertise Collect data and evidence systematically Select and apply appropriate RCA methodology Identify root cause(s) with supporting evidence Develop corrective and preventive actions Validation: Root cause explains all symptoms; if eliminated, problem would not recur

CAPA Necessity Determination

Trigger TypeCAPA RequiredCriteriaCustomer complaint (safety)YesAny complaint involving patient/user safetyCustomer complaint (quality)EvaluateBased on severity and frequencyInternal audit finding (Major)YesSystematic failure or absence of elementInternal audit finding (Minor)RecommendedIsolated lapse or partial implementationNonconformance (recurring)YesSame NC type occurring 3+ timesNonconformance (isolated)EvaluateBased on severity and riskExternal audit findingYesAll Major and Minor findingsTrend analysisEvaluateBased on trend significance

Investigation Team Composition

CAPA SeverityRequired Team MembersCriticalCAPA Officer, Process Owner, QA Manager, Subject Matter Expert, Management RepMajorCAPA Officer, Process Owner, Subject Matter ExpertMinorCAPA Officer, Process Owner

Evidence Collection Checklist

Problem description with specific details (what, where, when, who, how much) Timeline of events leading to issue Relevant records and documentation Interview notes from involved personnel Photos or physical evidence (if applicable) Related complaints, NCs, or previous CAPAs Process parameters and specifications

Root Cause Analysis

Select and apply appropriate RCA methodology based on problem characteristics.

RCA Method Selection Decision Tree

Is the issue safety-critical or involves system reliability? ├── Yes → Use FAULT TREE ANALYSIS └── No → Is human error the suspected primary cause? ├── Yes → Use HUMAN FACTORS ANALYSIS └── No → How many potential contributing factors? ├── 1-2 factors (linear causation) → Use 5 WHY ANALYSIS ├── 3-6 factors (complex, systemic) → Use FISHBONE DIAGRAM └── Unknown/proactive assessment → Use FMEA

5 Why Analysis

Use when: Single-cause issues with linear causation, process deviations with clear failure point. Template: PROBLEM: [Clear, specific statement] WHY 1: Why did [problem] occur? BECAUSE: [First-level cause] EVIDENCE: [Supporting data] WHY 2: Why did [first-level cause] occur? BECAUSE: [Second-level cause] EVIDENCE: [Supporting data] WHY 3: Why did [second-level cause] occur? BECAUSE: [Third-level cause] EVIDENCE: [Supporting data] WHY 4: Why did [third-level cause] occur? BECAUSE: [Fourth-level cause] EVIDENCE: [Supporting data] WHY 5: Why did [fourth-level cause] occur? BECAUSE: [Root cause] EVIDENCE: [Supporting data] Example - Calibration Overdue: PROBLEM: pH meter (EQ-042) found 2 months overdue for calibration WHY 1: Why was calibration overdue? BECAUSE: Equipment was not on calibration schedule EVIDENCE: Calibration schedule reviewed, EQ-042 not listed WHY 2: Why was it not on the schedule? BECAUSE: Schedule not updated when equipment was purchased EVIDENCE: Purchase date 2023-06-15, schedule dated 2023-01-01 WHY 3: Why was the schedule not updated? BECAUSE: No process requires schedule update at equipment purchase EVIDENCE: SOP-EQ-001 reviewed, no such requirement WHY 4: Why is there no such requirement? BECAUSE: Procedure written before equipment tracking was centralized EVIDENCE: SOP last revised 2019, equipment system implemented 2021 WHY 5: Why has procedure not been updated? BECAUSE: Periodic review did not assess compatibility with new systems EVIDENCE: No review against new equipment system documented ROOT CAUSE: Procedure review process does not assess compatibility with organizational systems implemented after original procedure creation.

Fishbone Diagram Categories (6M)

CategoryFocus AreasTypical CausesMan (People)Training, competency, workloadSkill gaps, fatigue, communicationMachine (Equipment)Calibration, maintenance, ageWear, malfunction, inadequate capacityMethod (Process)Procedures, work instructionsUnclear steps, missing controlsMaterialSpecifications, suppliers, storageOut-of-spec, degradation, contaminationMeasurementCalibration, methods, interpretationInstrument error, wrong methodMother NatureTemperature, humidity, cleanlinessEnvironmental excursions See references/rca-methodologies.md for complete method details and templates.

Root Cause Validation

Before proceeding to action planning, validate root cause: Root cause can be verified with objective evidence If root cause is eliminated, problem would not recur Root cause is within organizational control Root cause explains all observed symptoms No other significant causes remain unaddressed

Corrective Action Planning

Develop effective actions addressing identified root causes: Define immediate containment actions Develop corrective actions targeting root cause Identify preventive actions for similar processes Assign responsibilities and resources Establish timeline with milestones Define success criteria and verification method Document in CAPA action plan Validation: Actions directly address root cause; success criteria are measurable

Action Types

TypePurposeTimelineExampleContainmentStop immediate impact24-72 hoursQuarantine affected productCorrectionFix the specific occurrence1-2 weeksRework or replace affected itemsCorrectiveEliminate root cause30-90 daysRevise procedure, add controlsPreventivePrevent in other areas60-120 daysExtend solution to similar processes

Action Plan Components

• ACTION PLAN TEMPLATE
• CAPA Number: [CAPA-XXXX]
• Root Cause: [Identified root cause]
• ACTION 1: [Specific action description]
• Type: [ ] Containment [ ] Correction [ ] Corrective [ ] Preventive
• Responsible: [Name, Title]
• Due Date: [YYYY-MM-DD]
• Resources: [Required resources]
• Success Criteria: [Measurable outcome]
• Verification Method: [How success will be verified]
• ACTION 2: [Specific action description]
• ...
• IMPLEMENTATION TIMELINE:
• Week 1: [Milestone]
• Week 2: [Milestone]
• Week 4: [Milestone]
• Week 8: [Milestone]
• APPROVAL:
• CAPA Owner: _____________ Date: _______
• Process Owner: _____________ Date: _______
• QA Manager: _____________ Date: _______

Action Effectiveness Indicators

IndicatorTargetRed FlagAction scopeAddresses root cause completelyTreats only symptomsSpecificityMeasurable deliverablesVague commitmentsTimelineAggressive but achievableNo due dates or unrealisticResourcesIdentified and allocatedNot specifiedSustainabilityPermanent solutionTemporary fix

Effectiveness Verification

Verify corrective actions achieved intended results: Allow adequate implementation period (minimum 30-90 days) Collect post-implementation data Compare to pre-implementation baseline Evaluate against success criteria Verify no recurrence during verification period Document verification evidence Determine CAPA effectiveness Validation: All criteria met with objective evidence; no recurrence observed

Verification Timeline Guidelines

CAPA SeverityWait PeriodVerification WindowCritical30 days30-90 days post-implementationMajor60 days60-180 days post-implementationMinor90 days90-365 days post-implementation

Verification Methods

MethodUse WhenEvidence RequiredData trend analysisQuantifiable issuesPre/post comparison, trend chartsProcess auditProcedure compliance issuesAudit checklist, interview notesRecord reviewDocumentation issuesSample records, compliance rateTesting/inspectionProduct quality issuesTest results, pass/fail dataInterview/observationTraining issuesInterview notes, observation records

Effectiveness Determination

Did recurrence occur during verification period? ├── Yes → CAPA INEFFECTIVE (re-investigate root cause) └── No → Were all effectiveness criteria met? ├── Yes → CAPA EFFECTIVE (proceed to closure) └── No → Extent of gap? ├── Minor gap → Extend verification or accept with justification └── Significant gap → CAPA INEFFECTIVE (revise actions) See references/effectiveness-verification-guide.md for detailed procedures.

CAPA Metrics and Reporting

Monitor CAPA program performance through key indicators.

Key Performance Indicators

MetricTargetCalculationCAPA cycle time<60 days average(Close Date - Open Date) / Number of CAPAsOverdue rate<10%Overdue CAPAs / Total Open CAPAsFirst-time effectiveness>90%Effective on first verification / Total verifiedRecurrence rate<5%Recurred issues / Total closed CAPAsInvestigation quality100% root cause validatedRoot causes validated / Total CAPAs

Aging Analysis Categories

Age BucketStatusAction Required0-30 daysOn trackMonitor progress31-60 daysMonitorReview for delays61-90 daysWarningEscalate to management>90 daysCriticalManagement intervention required

Management Review Inputs

Monthly CAPA status report includes: Open CAPA count by severity and status Overdue CAPA list with owners Cycle time trends Effectiveness rate trends Source analysis (complaints, audits, NCs) Recommendations for improvement

Root Cause Analysis Methodologies

references/rca-methodologies.md contains: Method selection decision tree 5 Why analysis template and example Fishbone diagram categories and template Fault Tree Analysis for safety-critical issues Human Factors Analysis for people-related causes FMEA for proactive risk assessment Hybrid approach guidance

Effectiveness Verification Guide

references/effectiveness-verification-guide.md contains: Verification planning requirements Verification method selection Effectiveness criteria definition (SMART) Closure requirements by severity Ineffective CAPA process Documentation templates

CAPA Tracker

# Generate CAPA status report python scripts/capa_tracker.py --capas capas.json # Interactive mode for manual entry python scripts/capa_tracker.py --interactive # JSON output for integration python scripts/capa_tracker.py --capas capas.json --output json # Generate sample data file python scripts/capa_tracker.py --sample > sample_capas.json Calculates and reports: Summary metrics (open, closed, overdue, cycle time, effectiveness) Status distribution Severity and source analysis Aging report by time bucket Overdue CAPA list Actionable recommendations

Sample CAPA Input

{ "capas": [ { "capa_number": "CAPA-2024-001", "title": "Calibration overdue for pH meter", "description": "pH meter EQ-042 found 2 months overdue", "source": "AUDIT", "severity": "MAJOR", "status": "VERIFICATION", "open_date": "2024-06-15", "target_date": "2024-08-15", "owner": "J. Smith", "root_cause": "Procedure review gap", "corrective_action": "Updated SOP-EQ-001" } ] }

ISO 13485:2016 Clause 8.5

Sub-clauseRequirementKey Activities8.5.2 Corrective ActionEliminate cause of nonconformityNC review, cause determination, action evaluation, implementation, effectiveness review8.5.3 Preventive ActionEliminate potential nonconformityTrend analysis, cause determination, action evaluation, implementation, effectiveness review

FDA 21 CFR 820.100

Required CAPA elements: Procedures for implementing corrective and preventive action Analyzing quality data sources (complaints, NCs, audits, service records) Investigating cause of nonconformities Identifying actions needed to correct and prevent recurrence Verifying actions are effective and do not adversely affect device Submitting relevant information for management review

Common FDA 483 Observations

ObservationRoot Cause PatternCAPA not initiated for recurring issueTrend analysis not performedRoot cause analysis superficialInadequate investigation trainingEffectiveness not verifiedNo verification procedureActions do not address root causeSymptom treatment vs. cause elimination