|Classes||IEC 62304:2006 Section||Document Section|
|A, B, C||6.2.3||2|
|A, B, C||6.2.4||2|
|A, B, C||6.2.5||2|
|A, B, C||6.3.1||3|
|A, B, C||6.3.2||3|
|A, B, C||7.4.1||2|
|A, B, C||8.2.1||2|
|A, B, C||8.2.2||3|
|A, B, C||8.2.3||3|
|A, B, C||8.2.4||3|
|A, B, C||9.4||(All)|
This SOP describes how we evaluate and make changes to our software after it’s released.
|Process Owner||<enter role of process owner>|
|Key Performance Indicators||<enter KPIs to be tracked for the Management Review>|
Feedback is either classified as a bug fix or a regular change request:
The processing of changes is based on the following regulatory provisions and guidances:
Changes proposals can originate from various sources, e.g.:
They can originate from anywhere inside the company.
The Product Manager creates a change request ticket in the company’s project management software with a description of the proposed change.
|Anyone in the company with a change proposal|
|Change proposal||Documented change request (ID per product version)|
The Product Manager, together with a Regulatory Affairs Manager and the Head of Software Development, then evaluates the proposed change. In a first step, it is assessed if the change constitutes a bug fix or not. In case of a bug fix, the Product Manager directly proceeds with the evaluation as part of the bug fixes documentation list (link here).
If the change does not constitute a bug fix but rather a regular change request, it is evaluated whether the change:
The evaluation is documented as part of the Change Evaluation List and results in a decision on whether the change is implemented and whether the Notified Body needs to be involved if the change is significant. These two decisions are documented in the change request ticket.
If required, a Notified Body shall be informed before the implementation of changes. Multiple proposed changes can be batched and discussed in one session.
If the change request relates to the change of parts of the QMS, the change is assessed with the second part of the change evaluation list for “organizational changes”.
|Head of Software Development|
|Regulatory Affairs Manager|
|Change request||Completed change evaluation|
Change requests result as input to the SOP Software Development and are implemented accordingly.
This includes verification, validation and release activities while ensuring traceability. The relevant documentation is updated and released with an updated declaration of conformity.
Template Copyright openregulatory.com. See template license.
Please don’t remove this notice even if you’ve modified contents of this template.