The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Software Validation Procedure per FDA requirement


Cinti
31st August 2009, 09:21 AM
Hi,

As of now we are using ERP, PLC, power checking for intraocular lenses, label printing softwares etc., We would like to implement software validation procedure as per FDA requirement. Kindly help me.

Usually software validation are done while installation. Is re-validation required as per schedule like once in six months or once in a year? Else we can re-validate only if there is any change in software. Kindly advice.

Regards
Usha

rclanzillotto
31st August 2009, 03:50 PM
http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm085371.pdf

Read this FDA guidance document for starters. you are refering to Quality systems software; section 6. Good luck. Rich

Juan Dude
31st August 2009, 09:22 PM
Hi,

As of now we are using ERP, PLC, power checking for intraocular lenses, label printing softwares etc., We would like to implement software validation procedure as per FDA requirement. Kindly help me.

Usually software validation are done while installation. Is re-validation required as per schedule like once in six months or once in a year? Else we can re-validate only if there is any change in software. Kindly advice.

Regards
Usha
In addition to time-frame revalidation requirements your procedure should definitively require revalidation whenever there is a significant change.

alex.Kennedy
3rd September 2009, 12:11 PM
Hi
Once an item/program/system is validated it must be maintained in the validated status and as long as is maintained in accordance with GMP practices and procedures, then, revalidation is not mandatory.

If you have already produced regulated product using your new software then you should immediately instigate a retrospective validation program.

Alex Kennedy