Software Validation Procedure for ISO 13485 compliance?
Don’t panic :) Yes, you have to validate software and it feels like overhead, but it’s manageable and not a huge effort. Write down your intended use
Type at least 3 characters to search
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).
Dr. Oliver Eidel
Don’t panic :) Yes, you have to validate software and it feels like overhead, but it’s manageable and not a huge effort. Write down your intended use
Dr. Oliver Eidel
List all your software which you use either in your Quality Management System or as part of your product
development. Typically, those include Slack, GitHub, your IDE (e.g., IntelliJ) and programming libraries
which you (only) use during development.Libraries which you include in your product (i.e., which are deployed with it) don't belong here. They belong
in the SOUP list.
| ID | Name | Manufacturer | Bug tracker URL | Needs validation? | Next validation | Last validation | Decommissioning |
|---|---|---|---|---|---|---|---|
| 1 | GitHub | GitHub, Inc. | yes | 2020-05-17 | |||
| 2 | IntelliJ IDEA | JetBrains s.r.o. | https://youtrack.jetbrains.com/issues/IDEA | yes | 2020-05-17 |
Template Copyright openregulatory.com. See template
license.
Please don't remove this notice even if you've modified contents of this template.