How do you handle CAPA investigations and bug triage for SaMDs?
In our case, we don't open a CAPA for every bug. We triage bugs and determine their criticality—low, medium, high, critical, or emergency. Only those
Type at least 3 characters to search
Template
This is a free template, provided by OpenRegulatory. If you are a user of Formwork, our eQMS software, you can save time by choosing “QMS” on the top menu and “OpenRegulatory Templates” on the left menu, then opening the relevant folder to find this template ready to load into Formwork.
Using a different QMS? Download below as Word (.docx), PDF, Google Docs or Markdown. The template license applies (keep the copyright at the bottom, don’t re-use for commercial purposes).
Sven Piechottka
In our case, we don't open a CAPA for every bug. We triage bugs and determine their criticality—low, medium, high, critical, or emergency. Only those
Dr. Oliver Eidel
| ISO 13485:2016 Section | Document Section |
|---|---|
| 8.5.1 | (All) |
| 8.5.2 | (All) |
| 8.5.3 | (All) |
This SOP describes how CAPAs are implemented and tracked.
| Process Owner | <enter role of process owner> |
| Key Performance Indicators | <enter KPIs to be tracked for the Management Review> |
Various events may lead to creation of CAPA. Examples include:
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 |
If immediate action is necessary (e.g. field safety corrective action or a notification to authorities according to SOP Vigilance), 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 |
The QMO coordinates a root cause analysis with the person closest to the issue. The preferred method for this
is Five Whys. The result is added to the CAPA list.
| Participants |
|---|
| QMO |
| Other people in company (optional) |
| Input | Output |
|---|---|
| CAPA | CAPA, updated with root cause |
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 |
| Other people in company (optional) |
| Input | Output |
|---|---|
| CAPA | CAPA, updated with action plan |
The QMO conducts the verification and effectiveness review of the implemented action. These are defined as
below. Thereafter, the QMO closes the CAPA.
| Participants |
|---|
| QMO |
| Input | Output |
|---|---|
| CAPA | CAPA, updated with verification, effectiveness review, closed date |
Template Copyright openregulatory.com. See template
license.
Please don't remove this notice even if you've modified contents of this template.