EU Validation Requirement vs. FDA Validation Requirement - EN 62304

H

Hrobot

#1
Dear all,

Our software development SOP (for a class 2 medical device with an embedded software) is based on EN 62304. I am now trying to submit a 510(k) and realised that the terminology for software testing requirement has changed from Unit Testing and verification/System testing to IQ/OQ/PQ (Installation/Operational/Performance Qualification).
Do we have to change our terminology documentation format to fulfill FDA's requirement?

The same goes to the final device functionality test protocol. Whilst this is fine for MDD do I need to create an IQ/OQ/PQ protocol for the US market?

Your advice will be greatly appreciated

H
 
Last edited by a moderator:
Elsmar Forum Sponsor

harry

Super Moderator
#3
Dear all,

Our software development SOP (for a class 2 medical device with an embedded software) is based on EN 62304. I am now trying to submit a 510(k) and realised that the terminology for software testing requirement has changed from Unit Testing and verification/System testing to IQ/OQ/PQ (Installation/Operational/Performance Qualification). ........
Somebody correct me if I am wrong. Unit testing applies to software - unit testing is a procedure used to validate that individual units of source code are working properly whereas IQ/OQ/PQ refers to the need to validate the complete equipment or machine at the relevant stages suggested by the term itself.
 
H

Hrobot

#4
I think I made a mistake there to reference unit testing where I should have just referred to the final system testing.

I have checked the standards which are recognised by FDA and it includes 62304 Software life cycle, 60601 medical electronic equipment and 14971 risk management which are all the standards that we adhere to.

DOes this mean that I could use the Abrreviated 510(k) with a declaration of conformity to these standards?

regards,
H
 
W

Watchwait

#5
I just went back through and read both the FDA 510(k) new Paradigm and the requirements for using an Abbreviated 510(k). Sounds like your case is a good example of why they created this abbreviated path! Good Luck!
 
W

Watchwait

#6
I am also very interested in the interpretation of the IQ/OQ/PQ comment in HROBOTs first posting. Is the implication that if these particular terms are not mentioned in IEC 62304 that they are not required by FDA? I'm far from a software expert, hence my naivete/curiosity.
 

yodon

Staff member
Super Moderator
#7
I am also very interested in the interpretation of the IQ/OQ/PQ comment in HROBOTs first posting. Is the implication that if these particular terms are not mentioned in IEC 62304 that they are not required by FDA? I'm far from a software expert, hence my naivete/curiosity.
There is nothing in 21 CFR 820 (regulation by which FDA requires compliance for device development and manufacturing) that requires a particular test paradigm for product verification and validation.

In my experience, IQ/OQ/PQ are typically (only) used in manufacturing equipment validation, not product V&V.
 
A

Asherlee

#8
I recently submitted a 510(k) for a medical device with embedded SW. I based my SW documentation and terminology on the outlines described in the FDA Guidance document entitled:" Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices, dated May 11, 2005".

From my experience with the FDA, when they publish a Guidance Document that is applicable to your situation, then you should carry out the recommendations contained in the Guidance Document as much as possible/applicable.

Note that if you submit Declarations of Conformity in lieu of actual test reports, then they should comply with the FDA requirements listed in the attached table.

Also, the FDA has several Guidance Documents on the Use of Standards in Substantial Equivalence Determinations.

Regards,

Asherlee
 

Attachments

H

Hrobot

#9
Hi all,
I just want to update on my findings after speaking to several regulatory consultants. That no matter if the standard is a recognised standard by FDA it is best to reword any test protocols, or reports to fit the guidance documents' terminology during the submission. Basically the easier we make for them to review the documents the better chances we have to get an approval.

Hrobot
 
W

Watchwait

#10
Probably not the right specific thread, but I'll give it a whirl anyway. I came across a posting on another (related) site that I want to bring to our esteemed group of colleagues at The Cove:

Situation: The control software of an instrument is upgraded to a new version, and the vendor documents (probably release note, or software change history log) indicate that there are no significant changes (or
add some enhancements that we don't care about). Based on this information, it is appropriate to conclude that "the change has no impact on the functionality of the application and no revalidation is necessary based on the documentation provided."?

We have exactly the same situation and always agonize over how to handle them. On one hand (the conservative one) FDA says all changes to an approved device must be validated. Period. On the other hand, the "rationalization" that the vendor provided adequate documentation (and we audit the vendor and know his quality system is OK) would seem to be adequate justification for the "no validation required" position.

Thoughts? :evidence:
 
Thread starter Similar threads Forum Replies Date
C Software Validation Procedure per FDA requirement Qualification and Validation (including 21 CFR Part 11) 3
R System Requirement - FDA - Software Validation on various OSs ISO 13485:2016 - Medical Device Quality Management Systems 13
M Requirement for manufacturing process validation in IATF 16949 IATF 16949 - Automotive Quality Systems Standard 8
S Requirement for Sterilization Validation completion before issuance of ISO cert ISO 13485:2016 - Medical Device Quality Management Systems 0
N ETO Sterilisation Validation - EO Residual Minimum Sample Requirement ISO 13485:2016 - Medical Device Quality Management Systems 2
S Validation requirement after moving labeling data base to different drive Software Quality Assurance 7
S Sterilization Validation Accreditation - A mandated standard requirement? ISO 13485:2016 - Medical Device Quality Management Systems 5
I CNC Machine Validation Requirement ISO 13485:2016 - Medical Device Quality Management Systems 20
I AS9100B Cl 7.5.1.3 - How to comply with validation of production tools requirement? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
C Meeting Validation of Process Requirement - Stainless steel pipe & tube manufacturer ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
Manix GM Requirement for Trim Clip Validation - Anyone know a specification number Customer and Company Specific Requirements 4
A Validation of Processes - How to meet requirement of TS 16949 para. 7.5.2.1? IATF 16949 - Automotive Quality Systems Standard 12
J 7.5.2.1 Validation of processes - supplemental requirement IATF 16949 - Automotive Quality Systems Standard 11
Y SaMD Verification and Validation SOP and Plan IEC 62304 - Medical Device Software Life Cycle Processes 2
C Spreadsheet Validation and Release Qualification and Validation (including 21 CFR Part 11) 2
M Packing Validation & Accelerated Aging Test ISO 13485:2016 - Medical Device Quality Management Systems 2
M Sterile packing validation tests to be performed and protocol Other Medical Device and Orthopedic Related Topics 1
S OEM full range calibrations vs Validation special test points Medical Device and FDA Regulations and Standards News 0
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
C ISO 19227 Validation Cost Other Medical Device Related Standards 2
A CNC Mill and Lathe - Validation Manufacturing and Related Processes 2
N Example for design and development planning,input,output,review,verification,validation and transfer Misc. Quality Assurance and Business Systems Related Topics 4
N Sterilization Protocol Change in Validation Process and further impacts ISO 13485:2016 - Medical Device Quality Management Systems 1
B Oracle Cloud ERP Validation during Quarterly Patch ISO 13485:2016 - Medical Device Quality Management Systems 1
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
W LTPD, AQL, Ppk and Cpk validation sampling plan table Inspection, Prints (Drawings), Testing, Sampling and Related Topics 0
J Validation Sample Size for Tray Seal Qualification and Validation (including 21 CFR Part 11) 3
F AS9100 - Validation, FAIR's, ITAR and Sub-Contracting AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
R PCBA process validation Qualification and Validation (including 21 CFR Part 11) 2
A ISO 17025 - Methods validation and clients ISO 17025 related Discussions 3
S Sterilization validation after changing sterilization process provider Qualification and Validation (including 21 CFR Part 11) 3
B Sterilization Validation Plan Other Medical Device Related Standards 3
D Difference between Test Method Validation and Gage R&R Qualification and Validation (including 21 CFR Part 11) 18
T Laboratory Verification after validation ISO 17025 related Discussions 3
silentmonkey Rationalising the level of effort and depth of software validation based on risk ISO 13485:2016 - Medical Device Quality Management Systems 10
D Questions regarding process validation ISO 13485:2016 - Medical Device Quality Management Systems 6
Y We found out we have been using a equipment without validation for past 4 years Quality Manager and Management Related Issues 6
Z Is IQ necessary for laser marking validation? EU Medical Device Regulations 3
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
A Validation of Forced Aeration Process ISO 13485:2016 - Medical Device Quality Management Systems 3
E Mentor for Test Method Validation (TMV) Design and Development of Products and Processes 2
M API 4F/7K/8C Design Package Validation Oil and Gas Industry Standards and Regulations 2
I ISO 2233:2000 Question - Medical Device Shipping/Transportation Validation Other ISO and International Standards and European Regulations 1
T Annual Validation as a detection mode on a PFMEA? FMEA and Control Plans 5
B TMV - Selection of TM's for Validation ISO 13485:2016 - Medical Device Quality Management Systems 5
S Forced ServiceNow validation - No change in our current user and functional requirements IT (Information Technology) Service Management 4
P Human Factors / Usability validation in the time of COVID Human Factors and Ergonomics in Engineering 17
C Template for Excel Validation Reliability Analysis - Predictions, Testing and Standards 6

Similar threads

Top Bottom