Software Validation Question

duff999

Quite Involved in Discussions
#1
Regarding software validation to satisfy ISO 13485 requirements. Would a certificate of software validation from the vendor suffice, or do I need to create a test plan for intended use on my end to satisfy the requirement.

Any advice is appreciated.
 
Elsmar Forum Sponsor

duff999

Quite Involved in Discussions
#3
What are the answers to these questions:
  1. Is it product software?
  2. Is it implicated in the risk files for a medical device?
1. The software is provided with the instrument for data collection and analysis
2. It is not currently listed in our risk file.

Thanks Tidge
 

William55401

Quite Involved in Discussions
#4
Duff, for QMS software validation (a form of non product software), GAMP 5 is the recognized approach. The vendor's cert will certainly help for off the shelf software but your org will want to be certain is part of an overall suite of deliverables to maintain the software in a validated state. (Is it cloud based? Does your org control new versions? How are changes assessed before implementation? The list goes on.....).
 

William55401

Quite Involved in Discussions
#5
What is the instrument? Is the instrument used in the inspection, manufacturing, or testing of your finished device? If so, this is a form of non product software and GAMP 5 would apply. If your instrument is the device going to your customer, IEC 62304 would be in play for software in a medical device. Hope this helps.

Edit: Is the software distributed, by itself, to the end customer?
 
Last edited:
#6
Hello,

I have question relating to Periodic Review document(for a validated software). Is there a regulatory guideline/requirement on the Approvals required for this document ? My company follows four levels of approvals ie. by the Process Owner, System owner, IT Compliance & Quality. Any thoughts on this ?
 

duff999

Quite Involved in Discussions
#7
What is the instrument? Is the instrument used in the inspection, manufacturing, or testing of your finished device? If so, this is a form of non product software and GAMP 5 would apply. If your instrument is the device going to your customer, IEC 62304 would be in play for software in a medical device. Hope this helps.

Edit: Is the software distributed, by itself, to the end customer?
It is an instrument we use in final QC testing, I will take a look at GAMP 5 as suggested.
 

ScottK

Not out of the crisis
Leader
Super Moderator
#8
Regarding software validation to satisfy ISO 13485 requirements. Would a certificate of software validation from the vendor suffice, or do I need to create a test plan for intended use on my end to satisfy the requirement.

Any advice is appreciated.
If this is not custom software to your company for that specific machine I would accept the certificate as long as you are not modifying it.
Part of your qualification of the machine would be that the equipment vendor provided the software as specified in the purchase agreement.
This has been fine for me for chemical analytical equipment that came with pre-installed software. My company did not re-validate the software.
 

duff999

Quite Involved in Discussions
#9
If this is not custom software to your company for that specific machine I would accept the certificate as long as you are not modifying it.
Part of your qualification of the machine would be that the equipment vendor provided the software as specified in the purchase agreement.
This has been fine for me for chemical analytical equipment that came with pre-installed software. My company did not re-validate the software.
Thank you. It is not customer software that was tweaked by us in anyway. It was installed per manufacturers specification.
 

Tidge

Trusted Information Resource
#10
With the additional information, I have some general recommendations.

0) Don't over-think it.

1) Don't be quick to Jump to GAMP 5 for a commercially available piece of test & measurement equipment that is going to be used as a general tool for it's (marketed) purpose.

I don't want to poo-poo GAMP 5 (I was once a dues-paying a member of ISPE) but (a) it is expensive to own a legal copy of GAMP 5, and (b) if you don't own a legal copy (it's got a LOT of details and information in it) you are probably working with some watered-down version that you cannot trust is actually implementing GAMP 5. Most NPS process implementations I've seen that are "inspired by GAMP 5" have sharp edges/dark corners that (ironically?) get needlessly complicated for folks who haven't really engaged with the publication (and supplementary materials from ISPE) directly. I am aware that GAMP 5 is intended to be scalable (beyond the inherent scalability of suggested activities based on the nature of the NPS system) but I would never claim to be an old testament scholar just because I get a few select readings and a poem on Sunday mornings.

2) There are elements of this NPS that you will have to consider, even though I am going to go in a different direction.

What you are faced with is a measurement tool, so the primary concerns are about capability and reliability of the system (men, machines, methods) for the appropriate materials. Since it is a piece of equipment, you should have an Installation Qualification that documents all the important elements of the system, including the software version provided by the vendor. After identifying the nature of the objects to be measured/tested, you should (internally) generate confidence through appropriate means that the system is behaving with an acceptable range of outcomes... it could be gage R&R, round-robin challenges, whatever.... just like any other measurement system.

Now the thing you will have to keep an eye on, even if the system meets your needs: The manufacturer may find bugs or offer software updates. You ought to have a mechanism to stay aware of these. In the GAMP 5 approach, this is a lifecycle activity.
 
Thread starter Similar threads Forum Replies Date
P Software Validation for Equipment - Question ISO 13485:2016 - Medical Device Quality Management Systems 5
D Software validation question - TS 16949 Clause 7.6 IATF 16949 - Automotive Quality Systems Standard 4
B Software Validation Procedure Question - Complaint Handling Process software Software Quality Assurance 9
K Software validation question - Contract Manufacturer - ISO 13485 implementation ISO 13485:2016 - Medical Device Quality Management Systems 2
M 3D Scanner Software validation ISO 13485:2016 - Medical Device Quality Management Systems 7
C. Tejeda Computer system validation approach for Minitab Statistical software Software Quality Assurance 7
John C. Abnet ...validation of computer software ISO 13485:2016 - Medical Device Quality Management Systems 14
B ERP software validation - risk assessment vs validation scope ISO 13485:2016 - Medical Device Quality Management Systems 11
R Validation of Software used in Verification Testing ISO 13485:2016 - Medical Device Quality Management Systems 2
Watchcat Software validation vs design V&V? Other US Medical Device Regulations 27
M Initial Importer/Distributor and Software Validation IEC 62304 - Medical Device Software Life Cycle Processes 1
E ISO 13485 software validation ISO 13485:2016 - Medical Device Quality Management Systems 7
Y ISO 13485:2015 Software Validation IQ/OQ/PQ ISO 13485:2016 - Medical Device Quality Management Systems 13
R Debug mode in software/device validation IEC 62304 - Medical Device Software Life Cycle Processes 2
M Software verification and validation AS9100 AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
P Software verification and validation procedure IEC 62304 - Medical Device Software Life Cycle Processes 6
H Software Validation for FFS Packaging Machine Qualification and Validation (including 21 CFR Part 11) 1
Q ISO 13485 7.5.6 Validation - Off the shelf Software ISO 13485:2016 - Medical Device Quality Management Systems 3
M ERP / QMS related software standards for Validation IEC 62304 - Medical Device Software Life Cycle Processes 6
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
silentmonkey Rationalising the level of effort and depth of software validation based on risk ISO 13485:2016 - Medical Device Quality Management Systems 10
E 13485:2016, Sections 4.1.6, 7.5.6 and 7.6 - Validation of Software - Need some Advice please ISO 13485:2016 - Medical Device Quality Management Systems 3
K Software Validation for Measurement Tools used in Process Validation ISO 13485:2016 - Medical Device Quality Management Systems 2
S SOP for ISO 13485:2016 Quality related Software validation ISO 13485:2016 - Medical Device Quality Management Systems 16
K ERP System Software Validation - ISO13485 2016 4.1.6 Design and Development of Products and Processes 11
D Software validation in Medical Equipment Other Medical Device and Orthopedic Related Topics 20
C Looking for simple Software Validation IQ templates. Qualification and Validation (including 21 CFR Part 11) 4
C Software validation - Off The Shelf Software - Web hosted ISO 13485:2016 - Medical Device Quality Management Systems 6
R Validation of Medical Device Hardware containing Software - How many to Validate ISO 13485:2016 - Medical Device Quality Management Systems 1
F 21 CFR Part 11 - Implicit requirements - Validation plan for a Software as a Service Other US Medical Device Regulations 1
R ISO 13485 Software validation procedure and Quality Objectives Monitoring wanted Document Control Systems, Procedures, Forms and Templates 1
S Validation of COTS Equipment plus Software Qualification and Validation (including 21 CFR Part 11) 12
D Software Validation - Contract manufacturer of Components (PCBA's) Qualification and Validation (including 21 CFR Part 11) 7
Pmarszal Software Validation Training Course - Recommendations Training - Internal, External, Online and Distance Learning 3
T Software Validation Certificate (ISO 13485:2016) ISO 13485:2016 - Medical Device Quality Management Systems 19
R FDA Requirements - Printing Equipment Software Validation Qualification and Validation (including 21 CFR Part 11) 1
G Windows 10 OS build Software Validation US Food and Drug Administration (FDA) 1
S Where to keep Enterprise Resource Planning software (ERP) Validation Records ISO 13485:2016 - Medical Device Quality Management Systems 1
C Software validation (4.1.6 ISO 13485:2016) ISO 13485:2016 - Medical Device Quality Management Systems 20
M Software Validation Guidance Suggestions Various Other Specifications, Standards, and related Requirements 6
S QMS software validation - Documentation ISO 13485:2016 - Medical Device Quality Management Systems 5
A SOP for software validation of software in medical device IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 5
R CNC Software Validation requirements as per ISO 13485:2016 Other ISO and International Standards and European Regulations 8
R Software validation - off the shelf X-Ray Software Quality Assurance 3
S What is the clause in ISO 13485 for SAP Software Validation? ISO 13485:2016 - Medical Device Quality Management Systems 3
P Software validation of Data Exporter ISO 13485:2016 - Medical Device Quality Management Systems 3
A Process Validation of QMS Software ISO 13485: 2016 Cl. 4.1.6 ISO 13485:2016 - Medical Device Quality Management Systems 26
D Medical Device Software Tool Validation - Compilers! IEC 62304 - Medical Device Software Life Cycle Processes 7
N When is Medical Device Software Validation required? ISO 13485:2016 - Medical Device Quality Management Systems 6
O Process Mapping prior to Validation and Software to use to Map Process Maps, Process Mapping and Turtle Diagrams 12

Similar threads

Top Bottom