Validation, Qualification, and Change Control
This domain tests validation types and their regulatory basis, cleaning and computer system validation, and the change control process from request to verified closure. Questions often ask whether a proposed change needs revalidation, requalification or a regulatory filing.
Validation concepts
- Validation is documented evidence providing a high degree of assurance that a process consistently produces product meeting predetermined specifications and quality attributes.
- Prospective validation occurs before commercial distribution. Concurrent validation is used only with justification, such as low-volume or orphan products, with increased monitoring. Retrospective validation is discouraged and is not accepted as a substitute for a prospective approach in modern guidance.
- Cleaning validation uses health-based limits such as permitted daily exposure or a maximum allowable carryover calculation, selects the worst case for solubility and potency, studies recovery from surfaces, and confirms hold times for dirty and clean equipment.
- Computer system validation is risk-based, proportionate to intended use and GxP impact, and covers electronic records and signatures under 21 CFR Part 11 where applicable.
- Analytical method validation is separate from process validation; a validated process tested with an unvalidated method proves little.
Change control
- A change request states the description and rationale, then an impact assessment covering product quality, validated state, stability, methods, suppliers, documentation, training and regulatory filings.
- The quality unit approves, an implementation plan and owner are set, affected documents are revised, training is delivered, and verification or qualification is completed before closure.
- Classification distinguishes major and minor changes, and regulatory pathways differ: in the US, post-approval manufacturing changes may require a prior approval supplement, a changes-being-effected filing within 30 days, a changes-being-effected in 0 days filing, or an annual report; the EU uses variations classified by type.
- Planned changes go through change control; unplanned events go through deviation management, with retrospective change control where a permanent change is adopted.
Worked example
A site replaces a tablet press with a model using a different compression force control. The correct path starts with a user requirement specification and an impact assessment covering critical parameters such as compression force and speed and attributes such as hardness, weight and dissolution. Installation and operational qualification follow with the vendor, then performance qualification on the new equipment with at least three commercial-scale batches including dissolution and stability. Comparability is assessed, stability is committed, the regulatory impact is evaluated, batch records and SOPs are revised, training is delivered, and the change is closed only after verification data confirm the validated state.
Traps that cost marks
- Assuming a like-for-like replacement needs no assessment or documentation.
- Closing a change control when approved, before implementation, training and verification.
- Treating a deviation as a change control, or failing to raise a change control when a deviation produces a permanent fix.
- Overlooking the regulatory filing when the change alters the approved process, specifications or methods.