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
Conduct systematic CAPA investigation from initiation through closure:
- 1. 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 Type | CAPA Required | Criteria |
|---|
| Customer complaint (safety) | Yes | Any complaint involving patient/user safety |
| Customer complaint (quality) |
Evaluate | Based on severity and frequency |
| Internal audit finding (Major) | Yes | Systematic failure or absence of element |
| Internal audit finding (Minor) | Recommended | Isolated lapse or partial implementation |
| Nonconformance (recurring) | Yes | Same NC type occurring 3+ times |
| Nonconformance (isolated) | Evaluate | Based on severity and risk |
| External audit finding | Yes | All Major and Minor findings |
| Trend analysis | Evaluate | Based on trend significance |
Investigation Team Composition
| CAPA Severity | Required Team Members |
|---|
| Critical | CAPA Officer, Process Owner, QA Manager, Subject Matter Expert, Management Rep |
| Major |
CAPA Officer, Process Owner, Subject Matter Expert |
| Minor | CAPA 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
CODEBLOCK0
5 Why Analysis
Use when: Single-cause issues with linear causation, process deviations with clear failure point.
Template:
CODEBLOCK1
Example - Calibration Overdue:
CODEBLOCK2
Fishbone Diagram Categories (6M)
| Category | Focus Areas | Typical Causes |
|---|
| Man (People) | Training, competency, workload | Skill gaps, fatigue, communication |
| Machine (Equipment) |
Calibration, maintenance, age | Wear, malfunction, inadequate capacity |
| Method (Process) | Procedures, work instructions | Unclear steps, missing controls |
| Material | Specifications, suppliers, storage | Out-of-spec, degradation, contamination |
| Measurement | Calibration, methods, interpretation | Instrument error, wrong method |
| Mother Nature | Temperature, humidity, cleanliness | Environmental 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:
- 1. 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
| Type | Purpose | Timeline | Example |
|---|
| Containment | Stop immediate impact | 24-72 hours | Quarantine affected product |
| Correction |
Fix the specific occurrence | 1-2 weeks | Rework or replace affected items |
| Corrective | Eliminate root cause | 30-90 days | Revise procedure, add controls |
| Preventive | Prevent in other areas | 60-120 days | Extend solution to similar processes |
Action Plan Components
CODEBLOCK3
Action Effectiveness Indicators
| Indicator | Target | Red Flag |
|---|
| Action scope | Addresses root cause completely | Treats only symptoms |
| Specificity |
Measurable deliverables | Vague commitments |
| Timeline | Aggressive but achievable | No due dates or unrealistic |
| Resources | Identified and allocated | Not specified |
| Sustainability | Permanent solution | Temporary fix |
Effectiveness Verification
Verify corrective actions achieved intended results:
- 1. 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 Severity | Wait Period | Verification Window |
|---|
| Critical | 30 days | 30-90 days post-implementation |
| Major |
60 days | 60-180 days post-implementation |
| Minor | 90 days | 90-365 days post-implementation |
Verification Methods
| Method | Use When | Evidence Required |
|---|
| Data trend analysis | Quantifiable issues | Pre/post comparison, trend charts |
| Process audit |
Procedure compliance issues | Audit checklist, interview notes |
| Record review | Documentation issues | Sample records, compliance rate |
| Testing/inspection | Product quality issues | Test results, pass/fail data |
| Interview/observation | Training issues | Interview notes, observation records |
Effectiveness Determination
CODEBLOCK4
See references/effectiveness-verification-guide.md for detailed procedures.
CAPA Metrics and Reporting
Monitor CAPA program performance through key indicators.
Key Performance Indicators
| Metric | Target | Calculation |
|---|
| CAPA cycle time | <60 days average | (Close Date - Open Date) / Number of CAPAs |
| Overdue rate |
<10% | Overdue CAPAs / Total Open CAPAs |
| First-time effectiveness | >90% | Effective on first verification / Total verified |
| Recurrence rate | <5% | Recurred issues / Total closed CAPAs |
| Investigation quality | 100% root cause validated | Root causes validated / Total CAPAs |
Aging Analysis Categories
| Age Bucket | Status | Action Required |
|---|
| 0-30 days | On track | Monitor progress |
| 31-60 days |
Monitor | Review for delays |
| 61-90 days | Warning | Escalate to management |
| >90 days | Critical | Management 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
Reference Documentation
Root Cause Analysis Methodologies
INLINECODE2 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
INLINECODE3 contains:
- - Verification planning requirements
- Verification method selection
- Effectiveness criteria definition (SMART)
- Closure requirements by severity
- Ineffective CAPA process
- Documentation templates
Tools
CAPA Tracker
CODEBLOCK5
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
CODEBLOCK6
Regulatory Requirements
ISO 13485:2016 Clause 8.5
| Sub-clause | Requirement | Key Activities |
|---|
| 8.5.2 Corrective Action | Eliminate cause of nonconformity | NC review, cause determination, action evaluation, implementation, effectiveness review |
| 8.5.3 Preventive Action |
Eliminate potential nonconformity | Trend 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
| Observation | Root Cause Pattern |
|---|
| CAPA not initiated for recurring issue | Trend analysis not performed |
| Root cause analysis superficial |
Inadequate investigation training |
| Effectiveness not verified | No verification procedure |
| Actions do not address root cause | Symptom treatment vs. cause elimination |
CAPA专员
质量管理体系中纠正与预防措施(CAPA)管理,专注于系统性根本原因分析、措施实施及有效性验证。
目录
CAPA调查工作流程
从启动到关闭,系统性地开展CAPA调查:
- 1. 记录触发事件并附客观证据
- 评估重要性并确定CAPA必要性
- 组建具备相关专业知识的调查团队
- 系统性地收集数据和证据
- 选择并应用适当的RCA方法
- 识别根本原因并附支持性证据
- 制定纠正和预防措施
- 验证: 根本原因能解释所有症状;若消除该原因,问题将不再复发
CAPA必要性判定
| 触发类型 | 是否需要CAPA | 判定标准 |
|---|
| 客户投诉(安全) | 是 | 任何涉及患者/用户安全的投诉 |
| 客户投诉(质量) |
评估 | 基于严重性和频率 |
| 内部审核发现(主要) | 是 | 系统性失效或要素缺失 |
| 内部审核发现(次要) | 建议 | 孤立失误或部分实施 |
| 不合格项(重复发生) | 是 | 同一NC类型发生3次及以上 |
| 不合格项(孤立) | 评估 | 基于严重性和风险 |
| 外部审核发现 | 是 | 所有主要和次要发现 |
| 趋势分析 | 评估 | 基于趋势显著性 |
调查团队组成
| CAPA严重程度 | 所需团队成员 |
|---|
| 关键 | CAPA专员、流程负责人、QA经理、主题专家、管理层代表 |
| 主要 |
CAPA专员、流程负责人、主题专家 |
| 次要 | CAPA专员、流程负责人 |
证据收集清单
- - [ ] 包含具体细节的问题描述(什么、哪里、何时、谁、程度)
- [ ] 导致问题的事件时间线
- [ ] 相关记录和文档
- [ ] 相关人员的访谈记录
- [ ] 照片或实物证据(如适用)
- [ ] 相关投诉、NC或之前的CAPA
- [ ] 工艺参数和规格
根本原因分析
根据问题特征选择并应用适当的RCA方法。
RCA方法选择决策树
问题是否涉及安全关键或系统可靠性?
├── 是 → 使用故障树分析
└── 否 → 人为错误是否为疑似主要原因?
├── 是 → 使用人为因素分析
└── 否 → 有多少潜在促成因素?
├── 1-2个因素(线性因果)→ 使用5WHY分析
├── 3-6个因素(复杂、系统性)→ 使用鱼骨图
└── 未知/主动评估 → 使用FMEA
5Why分析
适用场景:具有线性因果关系的单一原因问题,具有明确失效点的流程偏差。
模板:
问题:[清晰、具体的陈述]
为什么1:为什么[问题]会发生?
因为:[第一层原因]
证据:[支持性数据]
为什么2:为什么[第一层原因]会发生?
因为:[第二层原因]
证据:[支持性数据]
为什么3:为什么[第二层原因]会发生?
因为:[第三层原因]
证据:[支持性数据]
为什么4:为什么[第三层原因]会发生?
因为:[第四层原因]
证据:[支持性数据]
为什么5:为什么[第四层原因]会发生?
因为:[根本原因]
证据:[支持性数据]
示例 - 校准逾期:
问题:pH计(EQ-042)发现校准逾期2个月
为什么1:为什么校准会逾期?
因为:设备未在校准计划中
证据:审查校准计划,EQ-042未列出
为什么2:为什么它不在计划中?
因为:设备购买时计划未更新
证据:购买日期2023-06-15,计划日期2023-01-01
为什么3:为什么计划未更新?
因为:没有流程要求在设备购买时更新计划
证据:审查SOP-EQ-001,无此要求
为什么4:为什么没有此类要求?
因为:程序在设备跟踪集中管理之前编写
证据:SOP最后修订于2019年,设备系统于2021年实施
为什么5:为什么程序未更新?
因为:定期审查未评估与新系统的兼容性
证据:未记录针对新设备系统的审查
根本原因:程序审查流程未评估与原始程序创建后实施的组织系统的兼容性。
鱼骨图类别(6M)
| 类别 | 关注领域 | 典型原因 |
|---|
| 人 | 培训、能力、工作量 | 技能差距、疲劳、沟通 |
| 机 |
校准、维护、年限 | 磨损、故障、能力不足 |
| 法 | 流程、作业指导书 | 步骤不清晰、控制缺失 |
| 料 | 规格、供应商、存储 | 不符合规格、降解、污染 |
| 测 | 校准、方法、解读 | 仪器误差、方法错误 |
| 环 | 温度、湿度、清洁度 | 环境偏差 |
完整的方法细节和模板请参见 references/rca-methodologies.md。
根本原因验证
在进行措施规划之前,验证根本原因:
- - [ ] 根本原因可通过客观证据验证
- [ ] 若消除根本原因,问题将不再复发
- [ ] 根本原因在组织控制范围内
- [ ] 根本原因能解释所有观察到的症状
- [ ] 没有其他重要原因未得到处理
纠正措施规划
制定针对已识别根本原因的有效措施:
- 1. 定义即时遏制措施
- 制定针对根本原因的纠正措施
- 识别类似流程的预防措施
- 分配职责和资源
- 建立时间表并设定里程碑
- 定义成功标准和验证方法
- 记录在CAPA措施计划中
- 验证: 措施直接针对根本原因;成功标准可衡量
措施类型
| 类型 | 目的 | 时间线 | 示例 |
|---|
| 遏制 | 阻止即时影响 | 24-72小时 | 隔离受影响产品 |
| 纠正 |
修复特定事件 | 1-2周 | 返工或更换受影响物品 |
| 纠正措施 | 消除根本原因 | 30-90天 | 修订程序、增加控制 |
| 预防措施 | 在其他领域预防 | 60-120天 | 将解决方案扩展到类似流程 |
措施计划组成部分
措施计划模板
CAPA编号:[CAPA-XXXX]
根本原因:[已识别的根本原因]
措施1:[具体措施描述]
- - 类型:[ ] 遏制 [ ] 纠正 [ ] 纠正措施 [ ] 预防措施
- 负责人:[姓名、职务]
- 截止日期:[YYYY-MM-DD]
- 资源:[所需资源]
- 成功标准:[可衡量的结果]
- 验证方法:[如何验证成功]
措施2:[具体措施描述]
...
实施时间表:
第1周:[里程碑]
第2周:[里程碑]
第4周:[里程碑]
第8周:[里程碑]
审批:
CAPA负责人: 日期:
流程负责人: 日期:
QA经理: 日期:
措施有效性指标
| 指标 | 目标 | 警示信号 |
|---|
| 措施范围 | 完全针对根本原因 | 仅处理症状 |
| 具体性 |
可衡量的交付成果 | 模糊的承诺 |
| 时间表 | 积极但可实现 | 无截止日期或不切实际 |
| 资源 | 已识别并分配 | 未指定 |
| 可持续性 | 永久解决方案 | 临时修复 |
有效性验证
验证纠正措施已达到预期结果:
- 1. 留出足够的实施期(至少30-90天)
- 收集实施后数据
- 与实施前基线进行比较
- 对照成功标准进行评估
- 验证期间确认无复发
- 记录验证证据
- 确定CAPA有效性
- 验证: 所有标准均满足客观证据;未观察到复发
验证时间线指南
| CAPA严重程度 | 等待期 | 验证窗口 |
|---|
| 关键 | 30天 | 实施后30-90天 |
| 主要 |
60天 | 实施后60-180天 |
| 次要 | 90天 | 实施后90-365天 |
验证方法
| 方法 | 适用场景 | 所需证据 |
|---|
| 数据趋势分析 | 可量化问题 | 前后对比、趋势图 |
| 流程审核 |
程序合规问题 | 审核清单、访谈记录 |