Software Validation - CAD-type program that will produce Engineering drawings

A

Alf Gulford

#1
I'd appreciate some opinions on this, even if it's to tell me I'm way off base.

Situation - We're in the process of implementing a software CAD-type program that will be used to produce Engineering drawings that will be used to:

a) define product
b) machine/assemble product
c) contain drawing approvals
d) control revision and distribution

This particular piece of software will not be used to test product, calibrate tools or automate processes.

What is the intent of ISO/FDA regarding software validation?

My kneejerk reaction is that we should validate it for the functions we require, not depend on the developer's validation. But since it's an established program and this use isn't called out in the standards I'm getting a lot of disagreement. And for that matter, I'm not eager to insist on a considerable expense if it isn't actually required.

Any opinions, please.

Thanks.

Alf
 
Elsmar Forum Sponsor

Bubba

Involved In Discussions
#2
We also use CAD software in our facility to produce engineering and tooling drawings. These drawings are printed in a hard copy form and approved by the appropriate personnel signing the drawing. The hard copy of the drawing is then filed and is the official record. In this sense we are performing verification by output and the software does not need to be validated. If, however, you are not fully verifying the output, then the software must be validated for its intended use.

The FDA has issued a draft guidance for Medical Device industry software validation in which they state, "Off-the-shelf software may have many capabilities, only a few of which are needed by the device manufacturer. The software must be validated for those specific uses for which it is intended." If you do need to validate the software, I think your knee-jerk reaction is appropriate and valid.

More information can be found at the FDA's website.
http://www.fda.gov/cdrh/comp/guidance/938.html
 
Q

QualPro

#3
Software Validation

I wish to thank "Buba" for his response to the question regarding software validation, and to concur with his comments. I have worked in the med device and pharmaceutical industries for 11 years, and this approach is sound. Great advice Buba.
 
A

Al Dyer

#4
I'm surely not a medical type person, but software validation covers all fields,

How can it be proven that software data is correct?

The only way I see it is to measure it against human measurements or like software programs.
 

Bubba

Involved In Discussions
#5
How can it be proven that software data is correct?
I think it helps to remember that software is, at its most basic form, simply a process. It takes input and runs it through predefined procedures to produce an output. When you are validating the software, what you are actually validating are those predefined procedures. Unless you are adept at computer languages and have access to the code, the best way to do that is to define what the inputs are and what the expected outputs are. If the outputs do not match what is expected, then there is something wrong with the procedures, i.e. the software.

In order to prove that any software data is correct, you must first know what your inputs are, and what the correct output should be. Obviously, the more features a software package has, the more inputs and outputs you will need to clearly define.

In the case of CAD drawings, the expected output is a graphical and textual representation that communicates to the viewer specified features, requirements, procedures, etc. If the drawing can effectively communicate the needed information (that is input into the software), than the drawing (output of the CAD software) is correct.

I'm not sure if that adequately adresses your question, but that is my basic take on the matter. Whether you use human measurements, or other like software, or some other basis for your expectations, you must be able to define what you expect the outputs to be for the given inputs.:)
 
A

Alf Gulford

#6
I've back after being gone for a few days.

Thank you Bubba and all. That's the info and support I was looking for. It's going to be an uphill battle but I'm going to keep pushing it.

Alf
 
A

Alf Gulford

#7
Bubba-

I owe you a second Thank You for reminding me about the FDA publication, General Principles of Software Validation (draft - 1997). I pulled my dusty old copy out and found exactly what I was looking for.

For anyone else that might benefit from this, the first two sentences in the Scope say:

"This draft guidance is applicable to all medical device software, including blood establishment software, and to software used to design, develop or manufacture medical devices. This draft guidance document represents the agency's current thinking on validation of software related to medical devices."

This couldn't be more clearly related to CAD software, and even though it's a 1997 draft, as far as I know it's still the most current document on the subject.

Does anyone know of anything more recent that supercedes or contradicts this?

Alf
 
A

Alf Gulford

#8
I can't believe it! After waiting four years for the final FDA guidance on software validation, and less than an hour after using the draft version to leverage my position, I get the notice that the final version is available. And from what I see so far, it doesn't support me nearly as well as the old one did.

For anyone that needs it, the final version is at:

www.fda.gov/OHRMS/DOCKETS/98fr/97d-0282_gdl0001.pdf

For whatever reason, I'm not having any luck downloading or printing it but at least it's there.

Alf

Edit Note- The URL isn't coming out right. I'll try again.
 

Bubba

Involved In Discussions
#9
Alf,

Thanks for the information on the final revision of the guidance document. I have also been waiting for a long time for this to come out. I followed your hyperlink, but I was only able to get about half of the document. It appears that it is scheduled for publication tomorrow. Maybe by then it will be completely available. It is kind of funny how much the FDA expects out of us for our software development and validation, yet their website is one of the least user-friendly sources of information on the internet.:confused:

I couldn't get the part that talks about off the self software yet, but I'm anxious to look it over.
 
H

Harold

#10
FDA guidance document on software validation just published

The FDA today anounced in the Federal Register that the "General Principles of Software Validation; Final Guidance for Industry and FDA Staff" has been released. It is available at http://www.fda.gov/cdrh/oc/938

This will answer most if not all of your questions.
 
Thread starter Similar threads Forum Replies Date
N Validation of CAD Software used to generate our Engineering Drawings? Qualification and Validation (including 21 CFR Part 11) 11
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 2
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 9
K ERP System Software Validation - ISO13485 2016 4.1.6 Design and Development of Products and Processes 8
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 1
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
P Software Validation for Equipment - Question ISO 13485:2016 - Medical Device Quality Management Systems 5
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
SteveK Software Validation – Clause 4.1.6 of ISO 13485:2016 ISO 13485:2016 - Medical Device Quality Management Systems 12
B Could I combine IQ, OQ and PQ for Minitab Software Validation ? Software Quality Assurance 3
R Document Management Software : Validation and other requirements Medical Information Technology, Medical Software and Health Informatics 8
E Software Validation - Clinical Trials US Food and Drug Administration (FDA) 3
K What are the minimum requirements for Process Validation (Software)? ISO 13485:2016 - Medical Device Quality Management Systems 5
R ISO - Clause 7.5.1.3 - CMM Software Program Validation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2
I Validation Software Experience? (Valgenesis, etc.) Quality Assurance and Compliance Software Tools and Solutions 1
M Injection Molding Machine Software Validation Calibration and Metrology Software and Hardware 2
E FDA Requirements for Implantable Medical Device Software Validation ISO 13485:2016 - Medical Device Quality Management Systems 5
C Change Control Forms Post Software Validation Medical Information Technology, Medical Software and Health Informatics 2
C Thoughts on validation of Legacy Systems for Medical Device Software EU Medical Device Regulations 2
C Cement Mixing Software Validation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
Y OTS (Off The Shelf) Software Validation for 510k Traditional 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
V Validation of macro - scripts - programs used in statistical software (Minitab-SAS... Qualification and Validation (including 21 CFR Part 11) 5
R ISO 13485 Software Validation Requirements - Help needed ISO 13485:2016 - Medical Device Quality Management Systems 4
M MSA - Validation of Metrology Software such as PCDMIS Calibration and Metrology Software and Hardware 2
T Class II Software Device 510k V&V (Verification and Validation) Criteria and Results 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
A ClassIIa Medical Device Software Validation Report Format and Content IEC 62304 - Medical Device Software Life Cycle Processes 5
A Medical Device Software Validation Guidance Software Quality Assurance 3

Similar threads

Top Bottom