Confused by UDIs? Check out our step-by-step video course and watch us purchase real UDIs

Templates IEC 62304 Templates

Updated August 31, 2023

Template: SOP Software Problem Resolution

Dr. Oliver Eidel

Template Download

This is a free template, provided by OpenRegulatory.

You can download it 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).

Download as Word File


Download as PDF


Copy-paste to Google Docs


Download as Markdown


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

SOP Software Problem Resolution

Classes IEC 62304:2006 Section Document Section
B, C 5.6.8 (All)
A, B, C 1
A, B, C 6.2.2 (All)
A, B, C 9.1 1
A, B, C 9.2 2
A, B, C 9.3 3
A, B, C 9.5 1
A, B, C 9.6 2
A, B, C 9.7 3


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:

We classify the severity of problems in the following categories:

Severity Classification Description
High Causes new or changed risks to patients which are unacceptable.
Medium May cause new or changed risks to patients which are acceptable.
Low All 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.

Head of product development
Person responsible for regulatory compliance
Input Output
New problem Problem 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.

Head of software development
Software developer
Input Output
Problem report Problem 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.

Head of product development
Person responsible for regulatory compliance
Input Output
Problem report Resolved/closed problem report
Implemented change  

Template Copyright See template license.

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

Digital Health Jobs No Cookie For You Privacy Policy Imprint
No QMS on this planet will save you from creating crappy software.