Sop Capa PDF
Sop Capa PDF
Sop Capa PDF
Summary
This SOP describes how CAPAs are implemented and tracked.
Process Steps
1. Input for CAPA
Various events may lead to creation of CAPA. Examples 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
These inputs may be received from any person inside or outside the company.
The QMO is responsible for creating the CAPA and tracking its resolution.
CAPAs are tracked in the CAPA list.
Participants
QMO
Input Output
Non-conformity, complaint, etc. CAPA created
1
2. Decision on Next Steps, Immediate Action
If immediate action is necessary (e.g. product recall, notification of authorities),
the QMO consults the Person Responsible for Regulatory Compliance. Immediate
action is carried out without undue delay (see ISO 13485 para. 8.5.2).
In any case, the QMO discusses the next steps with the person closest to the
issue, e.g. for software bugs, the Head of Software Development.
Participants
QMO
Medical Device Safety Officer / Person Responsible for Regulatory Compliance
(optional)
Input Output
CAPA CAPA, updated with action
Participants
QMO
Other people in company (optional)
Input Output
CAPA CAPA, updated with root cause
4. Implementation of Action
The QMO coordinates defining and implementing corrective and preventive
action. Additionally, the QMO takes 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.
Outcomes are documented in the CAPA list.
Participants
QMO
2
Participants
Other people in company (optional)
Input Output
CAPA CAPA, updated with action plan
Participants
QMO
Input Output
CAPA CAPA, updated with verification, effectiveness review, closed date