The Cove Business Standards Discussion Forums
ISO 13485:2016 - Validate our use of software that impacts on the QMS
Please read this thread...
Software update
ISO 13485:2016 - Validate our use of software that impacts on the QMS
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > > >
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

ISO 13485:2016 - Validate our use of software that impacts on the QMS

Monitor the Elsmar Forum
Courtesy Quick Links


Links Elsmar Cove visitors will find useful in the quest for knowledge and support:

Jennifer Kirley's
Conway Business Services


Howard's
International Quality Services


Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum


Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining


Ajit Basrur
Claritas Consulting, LLC



International Standards Bodies - World Wide Standards Bodies

AIAG - Automotive Industry Action Group

ASQ - American Society for Quality

International Organization for Standardization - ISO Standards and Information

NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology


Some Related Topic Tags
iso 13485:2016, software validation
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 20th September 2017, 08:39 AM
andesite

 
 
Total Posts: 4
Thank You! ISO 13485:2016 - Validate our use of software that impacts on the QMS



Hi All,

We're in the process of transitioning to the 2016 version of ISO 13485, and one of the biggies for us is the requirement to validate our use of software that impacts on the QMS. I've justified what needs assessing based on risk and need to start writing the validation protocols for it now, but it's something I have absolutely no experience in. I think I could fumble through a new validation but the retrospective need to validate is throwing me completely as we have nothing to work off like a URS etc. Can anyone point me towards any guidance which would give me an idea of what paperwork would be the minimum we need and perhaps a decent way of laying it out? Any suggestions gratefully received.

Sponsored Links
  Post Number #2  
Old 20th September 2017, 10:28 AM
yodon

 
 
Total Posts: 1,156
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

A couple of things:

First, validation is not a one-time event (so just having "paperwork" may be a misconception). Once you complete validation, you need to maintain the system in a validated state throughout its use life. Your validation program (usually captured in a Master Validation Plan) should address the complete life cycle.

Second, the concept of non-product software validation isn't new, it was there for software used in production and service provision. The updated standard does, in fact, expand the scope and emphasis.

You will certainly need to establish requirements for the applications. Just no way to validate something if you can't articulate what its intended use is.

As far as the retrospective aspect goes, you'll just need to generate enough evidence to be able to assert that whatever you have done in the past with the software is valid.

This is a pretty big subject and hard to express in a few lines on a discussion board.
Thank You to yodon for your informative Post and/or Attachment!
  Post Number #3  
Old 21st September 2017, 03:57 AM
pkost

 
 
Total Posts: 824
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

The US/FDA have focused considerably on validation of electronic records. The FDA have issued the following guidance:

https://www.fda.gov/downloads/regula.../ucm125125.pdf
Thanks to pkost for your informative Post and/or Attachment!
  Post Number #4  
Old 21st September 2017, 07:04 AM
kreid

 
 
Total Posts: 57
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

If you do not have a URS for your legacy software, maybe you have a work instruction or training materials on how to use it?
If so you can use this as the input to your validation process, they can be used as a surrogate URS.
  Post Number #5  
Old 27th September 2017, 11:33 AM
MC Eistee

 
 
Total Posts: 6
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

I would advise you to read the new ISO/TR 80002-2 that was just published in June this year.
It is a guide for validation in an ISO environment. Nothing really new in there but it might be a good start for you as it comes with some examples and is easy to read.

If you are also FDA regulated you might also look at the link of pkost.

As yodon said, validation is not a one time event. You need to keep it in a validated state. Simple example: Initial validation and then you need to judge each change on the software (also its environment if there is any impact) whether you have to validate again or not.
Thank You to MC Eistee for your informative Post and/or Attachment!
  Post Number #6  
Old 28th September 2017, 03:32 AM
pkost

 
 
Total Posts: 824
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

Thanks MC Eistee, I was unaware of an ISO standard relating to this
  Post Number #7  
Old 4th October 2017, 08:43 AM
Wolf.K

 
 
Total Posts: 72
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

Hi,

We have the same issue. Our QMS is totally paper-based, that is, all documentation is printed out and filed in folders. But of course we have computers, and our contract manufacturers use software in the production.

So, what I did was:

I wrote a SOP "Validation of QMS software"...

This SOP just requires to write a validation plan, a validation report, and list the validated software in a software validation log (all controlled documents) and statement if it is released for use or not. As applicable, failure modes have to be defined, then a decision has to be made, and the rational for the decision has to be stated.

Validation log
Headlines of the columns:
ID number - Software name, version, date - Description (what is the software used for) - Failure mode (short version of the report) - Validation required? - Rationale (short version from the report) - Software validation report (yes, n/a, not available yet) - Software released for everyday use? (yes/no) - Decision made date / by

So, we fulfill now the requirement of a documented procedure. Is it a good procedure, or a bad one? I don't know, I have never done a software validation before. The new ISO standard did not help me much, though. But: we have a procedure. After the audit I will know, if it is good enough...

I had to think about the software we use and which has to be validated. I came up with the following list:

1. Office. As we print all our documents, so no need to validate. Except:

1.1 Spreadsheet calculations

For our spreadsheet calculations I ask our people who program spreadsheet calculations to write a short report of the algorithm, and test it a bit. That is, plug some (also extreme) values in it and see, if the results are correct. I referenced the FDA requirements/recommendations in the SOP.

2. Our statistics program

We use it for calculating e.g. numbers to treat and else (for our clinical studies). The good thing is: all formulas are already validated by the manufacturer. So, no need for us to validate it.

3. The data retrieval software of our data loggers (to record temperature and humidity)
Our products are manufactured by contract manufacturers and distributed by distributors. But we have a small storage room to store products to be used by our product managers e.g. for clinical trainings. So we have to prove that the sterility of the products is not compromised. SOP Storage Room requires documentation of environmental parameters. We have a data logger and log the parameters. But are the numbers I see on the computer the real ones, or does the import of the data from the logger change the values? So: validation required.

Next year we get a ERP, and I have to learn something about GAMP 5...

Hope this helps!
Thank You to Wolf.K for your informative Post and/or Attachment!
  Post Number #8  
Old 9th August 2018, 10:21 AM
bcoolnow

 
 
Total Posts: 7
Re: ISO 13485:2016 - Validate our use of software that impacts on the QMS

I am also fairly new to the software validation requirements and may have a large one coming up soon, excel spreadsheets used for final inspection. If these are used for data acquisition during final inspection, does this need to be validated? And if so, to what degree? I would assume that any cell where a calculation is done would need to be proven out, even though the formulas themselves may be pre-proven by the manufacturer. We are contemplating going this route so would like to know what all may be involved.
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > > >

Bookmarks



Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Emoticons are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
Software Validation – Clause 4.1.6 of ISO 13485:2016 SteveK ISO 13485:2016 - Medical Device Quality Management Systems 12 5th June 2018 04:52 PM
ISO 13485:2016 Self Certification for Class I (annex 9) Stand-Alone Software? keldez ISO 13485:2016 - Medical Device Quality Management Systems 3 17th July 2017 11:09 AM
EN ISO 13485:2016 vs. ISO 13485:2016 - Unannounced MDD Audit yesterday Shamann2 ISO 13485:2016 - Medical Device Quality Management Systems 4 2nd February 2017 12:13 AM
Software Observation during ISO 9001 Audit - Validate and Re-validate Software al40 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 13 16th August 2006 02:20 PM
Validate Software - Looking for a way to validate software written by a vendor KenW Software Quality Assurance 4 2nd November 2001 03:31 PM



The time now is 12:41 AM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.



Misc. Internal Links


NOTE: This forum uses "Cookies"