inventory_2

SOP Corrective and Preventative Action

Use this SOP Corrective and Preventive Action (CAPA) template to systematically document, implement, and track actions taken to address and prevent actual or potential quality issues and nonconformities in your medical device processes, products, or services. This template is essential for meeting key ISO 13485, FDA 21 CFR 820.100, and MDR/IVDR requirements, and should be filled out whenever nonconformities, audit findings, customer complaints, or other significant quality events arise that require root cause analysis and long-term resolution. Completing this SOP ensures regulatory compliance, supports continuous improvement, and helps maintain the safety and effectiveness of your medical devices.
Generate ->

SOP Corrective and Preventive Action

ID: Curabitur ullamcorper ultricies nisi. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc.

1. Purpose

This document describes the processes for creating, implementing, and documenting corrective and preventative actions (CAPAs). Action should be taken to eliminate the cause of nonconformities in order to prevent recurrence and to eliminate the cause of potential nonconformities in order to prevent their occurrence. Corrective and preventative actions should be proportionate to the effects of the nonconformities and/or issues encountered or the effects of the potential problems, respectively.

2. Scope

This procedure applies to all actual or potential nonconformities (or other undesirable situations) that may affect the quality of Company operations, products or services.

3. Responsibilities

3.1 All Employees

  • Identify and report actual or potential nonconformities or other quality issues.
  • Provide initial information about the observed event.

3.2 Quality Team and/or Management Representative

  • Oversight & Coordination:
    • Oversee the entire CAPA process.
    • Determine if a reported event requires a CAPA based on the qualification process (Section 4.1).
    • Assign a CAPA number and maintain CAPA records.
    • Ensure no similar open CAPAs exist for the same issue.
    • Coordinate CAPA activities and timelines, involving relevant personnel as needed.
    • Report CAPA status and trends during management reviews.
    • Update this procedure as needed.
  • Investigation & Planning:
    • Lead or delegate the investigation, including impact assessment and root cause analysis (Section 4.3.1).
    • Develop and document immediate/containment actions, if necessary.
    • Develop a corrective and/or preventive action plan based on the root cause analysis (Section 4.3.2).
    • Involve subject matter experts from affected functions (e.g., R&D, Operations) as needed for investigation and planning.
    • Ensure the action plan considers potential adverse effects and meets regulatory requirements.
    • Develop a plan to verify the effectiveness of the actions.
  • Execution & Verification:
    • Ensure the planned actions are implemented.
    • Document the execution of actions.
    • Verify the effectiveness of the implemented actions (Section 4.3.3).
  • Approval & Closure:
    • Approve the CAPA plan, any necessary extensions, and the final CAPA completion.
    • Formally close the CAPA record once effectiveness is confirmed.
    • Ensure relevant documentation (e.g., risk management file) is updated if new risks are identified or existing ones are affected.

4. Processes

4.1 CAPA Qualification

Not all events lead to the implementation of a CAPA. Examples of what can initiate a CAPA include:

  • Product or QMS non-conformities
  • Customer complaints
  • Internal bug reports, e.g. by developers
  • Audit findings
  • Post-market surveillance findings, including trends
  • Management review findings, including trends

The quality team shall determine if a CAPA is required for the resolution of any events that have been identified internally or externally to the company. If the quality team determines that a CAPA is necessary then it can initiate a CAPA for the issue.

The following risk based approach should be used to determine if an input requires a CAPA.

4.1.1 CAPA Qualification Process

As mentioned, the quality team should perform CAPA qualification. Using the metric below, a member of the quality team can score the event to determine if a CAPA should be initiated. Go through each row sequentially. For each row that presents a numerical score, summarize the appropriate score from each row. For each row with an agree/disagree question, answer each question to be best of your knowledge. Follow the CAPA Initiation Criteria instructions below the table to determine if a CAPA should be initiated.

CAPA Initiation Criteria

Once each row has been visited and answers have been collected, sum all numerical values if they designate a number value for the answer. Use the criteria below to determine if a CAPA should be initiated or not.

Initiate CAPA if:

  • If the summed score calculated above is >3 and all answers to the agree/disagree questions are "Disagree".

MAY NOT initiate CAPA if:

  • If any answer to the agree/disagree questions are "Agree" regardless of the score.
  • If the summed score calculated above is under 3.

Note: CAPA can be initiated if these criteria are not met but if there is a need for a CAPA.

4.2 CAPA Initiation

If it has been determined through the CAPA qualification process above that a CAPA is required, the CAPA Report shall be created by the quality team. The quality team is required to participate in CAPA Report creation and resolution process.

If immediate action is necessary in the case of field safety corrective action or a notification to authorities, the quality team shall initiate that process without undue delay according to SOP Vigilance.

4.3 CAPA Report

As mentioned, the quality team shall create the CAPA Report. As part of the CAPA Report, a root cause analysis shall be performed alongside the member of the company closest to the issue that initiated the event. For example, events related to software issues shall involve the software team and events related to marketing materials shall involve the business team.

4.3.1 Root Cause Analysis

As part of the CAPA Report, a root cause analysis should be performed on the initiating event according to the Five Whys method or a similar root cause analysis method.

For the Five Whys method, fill in the problem statement below and ask the "Why" question to the problem statement for "Why #1". Provide the answer to the question "Why did this problem occur" in the box next to "Why #1". Each consecutive "Why" asks the same question, "why did this happen?" to the previous "Why" answer above it, until it is determined that the root cause has been identified for the original problem statement. This can take less than 5 "Whys" or more than 5 "Whys".

For the Five Whys method, the following table can be used to perform the Five Whys analysis but is not required. The final root cause shall be added to the CAPA Report.

Continue with more "Whys" if the root cause isn't identified at 5th Why.

For more complex issues, the CAPA teams may use other methods including but not limited to the Fishbone Diagram / Ishikawa (Man, Machine, Environment, Measurement, Material and Method) etc.

4.3.2 Corrective and/or Preventive Actions

The quality team coordinates defining and implementing corrective and preventive actions to correct each root cause and ensure the problem is resolved. This can also include containment actions.

Additionally, the quality team shall take into account adverse negative implications and verifies that the actions do not adversely affect the ability to meet applicable regulatory requirements or the safety and performance of the medical device. Subject matter experts related to the problem and actions to be taken should be consulted, as needed, in order to ensure that the actions are reasonable and address the root cause.

After defining the planned actions to be implemented, the team will sign the CAPA Report and execute the planned actions.

4.3.3 CAPA Verification and Effectiveness

Once the actions have been undertaken, the CAPA Report can be updated with the actions performed. Once all actions have been performed to resolve the problem, the second set of signatures can be signed by the team. This is considered verification of the CAPA action plan.

Once all actions have been verified, the quality team conducts an effectiveness review of the implemented actions. After the effectiveness review is complete, the CAPA can be closed. If the CAPA is not deemed to be effective, a new CAPA can be opened to address the open problems.

Mapping of Requirements