FDA requires that all software in computer systems used in GxP activities must be validated. The validation of computer system software is completely different from than validation of device software (embedded software). Validation is much more than testing. It is testing plus design control and configuration management.
How to plan and conduct a risk-based validation will be explained. The overall risk for a computer system is a combination of software complexity and product risk as determined by probability, severity, and detectability rankings. Also involved in the risk evaluation is the requirement for purchased software supplier qualification. You'll learn how to integrate risk-based supplier evaluation into the validation process.
The validation Master plan and System Validation Plans will be explained.
Testing, based on risk, includes requirements validation and IQ, OQ, and PQ. A procedure for each level of complexity and risk will be described.
You will learn in detail:
How to plan and conduct a risk-based validation will be explained. The overall risk for a computer system is a combination of software complexity and product risk as determined by probability, severity, and detectability rankings. Also involved in the risk evaluation is the requirement for purchased software supplier qualification. You'll learn how to integrate risk-based supplier evaluation into the validation process.
The validation Master plan and System Validation Plans will be explained.
Testing, based on risk, includes requirements validation and IQ, OQ, and PQ. A procedure for each level of complexity and risk will be described.
Why you should Attend:
The validation of computer system software is completely different from than validation of device software (embedded software). Attempting to conduct a CSV following device software validation concepts could result in a 483 or rejection of a product approval submission.You will learn in detail:
- How to manage the validation process
- Validation life cycle models and Validation Plan contents
- How to determine the complexity category of your system based on GAMP 5 principles
- How to evaluate risk level using GAMP 5 modifications to the ISO 14971 procedure
- What level of testing is necessary based on software complexity and risk
- Integrating software supplier evaluation into the validation process
- What documentation is necessary
- How to minimize documentation to reduce costs based on risk
- How to plan and conduct IQ, OQ, and PQ
Areas Covered in the Session:
- Validation strategy
- Requirements documentation
- Complexity and risk analysis
- Creating a detailed test plan based on risk
- Supplier Qualification
- IQ, OQ and PQ
