Template: SOP Software Problem Resolution

Template Download

This is a free template, provided by OpenRegulatory.

If you are a user of Formwork, our eQMS software, choose “QMS” on the top menu and “OpenRegulatory Templates” on the left menu, and then open the relevant folder to find this template ready to load into Formwork.

If, for some mysterious reason, you’re using a different QMS Software, you can also simply download this template – specifically, as Word (.docx), PDF, Google Docs or Markdown file. Scroll down for a preview!

The template license applies (don’t remove the copyright at the bottom).

Tired of copy-pasting? If you want to save time and edit these templates directly, you can use Formwork, our eQMS software. And if you’re looking for step-by-step instructions for filling them out, check out our Wizard 🙂

Don't Miss Updates to This Template
Subscribe to our newsletter and we'll keep you posted on which templates we've changed.

Questions? Still Lost in Regulation?

Good news! Our goal is to provide lots of stuff for free, but we also offer consulting if you need a more hands-on approach. We get stuff done really fast. Have a look!

Template preview
ClassesIEC 62304:2006 SectionDocument Section
B, C5.6.8(All)
A, B, C6.2.1.31
A, B, C6.2.2(All)
A, B, C9.11
A, B, C9.22
A, B, C9.33
A, B, C9.51
A, B, C9.62
A, B, C9.73

Summary

This SOP describes how problems concerning our software product(s) are processed, evaluated and fixed.

Process Owner<enter role of process owner>
Key Performance Indicators<enter KPIs to be tracked for the Management Review>

Process Steps

1. New Problem Evaluation

New problems are entered as tickets into <your ticketing system>.

Reported problems can originate from customers, users or company employees. Examples include customer feedback and bug reports.

For each problem report, the following must be entered:

  • Affected medical device and version
  • Severity classification (see below)
  • Problem description incl. instructions to reproduce

We classify the severity of problems in the following categories:

Severity ClassificationDescription
HighCauses new or changed risks to patients which are unacceptable.
MediumMay cause new or changed risks to patients which are acceptable.
LowAll other problems.

For all problems classified as “Medium” or higher the person responsible for regulatory compliance (PRRC) must be informed who subsequently assesses it according to the SOP Vigilance.

Participants
Head of product development
Person responsible for regulatory compliance
InputOutput
New problemProblem report as <ticket in your ticketing system>

2. Root Cause Analysis and Procedure

The root cause of the problem is determined (if possible) and a decision is made whether to fix it or not.

We also analyze whether similar problems have occurred in the past and any trends can be discerned. If this is the case, it is noted in the problem report.

Participants
Head of software development
Software developer
InputOutput
Problem reportProblem report updated with cause and procedure

3. Implementation and Verification

The bug fix is implemented. If the fix includes a change to an existing product, it is handled according to SOP Change Management.

After the bug fix has been implemented, the problem report is reviewed whether it has been successfully fixed and can be closed. Closing the problem report is equivalent to successful verification.

Participants
Head of product development
Person responsible for regulatory compliance
InputOutput
Problem reportResolved/closed problem report
Implemented change

Template Copyright openregulatory.com. See template license.

Please don’t remove this notice even if you’ve modified contents of this template.

Template preview

Comments

Leave the first comment