Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

How is retrospective validation different from prospective and concurrent validation?


Asked by Briar Costa on Dec 14, 2021 FAQ



The general process for retrospective validation follows the same process as for prospective and concurrent validation except DQ is seldom performed, as the system has already been in use for some time. Instead a survey and review of available information is performed. This normally occurs before the validation plan is created.
Similarly,
Whenever possible, prospective validation is preferred. Retrospective validation is no longer encouraged and is, in any case, not applicable to the manufacturing of sterile products. • control of process parameters being monitored during normal production runs to obtain additional information on the reliability of the process.
In addition, Prospective Validation: This is first time validation of a intermediate / API before launching into market. Concurrent Validation: This type of validation is used only for monitoring the critical steps and end product quality. Usually reprocess / rework of a product shall be considered as Concurrent Validation. a.
And,
4.1.1 There are two basic approaches to validation — one based on evidence obtained through testing ( prospective and concurrent validation), and one based on the analysis of accumulated (historical) data (retrospective validation). Whenever possible, prospective validation is preferred.
In respect to this,
Prospective Validation, 2. Retrospective Validation, 3. Concurrent Validation, 4. Revalidation. Prospective Validation: This is first time validation of a intermediate / API before launching into market. Concurrent Validation: This type of validation is used only for monitoring the critical steps and end product quality.