Dear Tom
Admittedly, there is no hard and fast statement in the regulations that mandates revalidation.
In Europe, this is indirectly implied thorugh the variations regulations (classification guideline), which requires: batch analysis data (in a comparative tabular format) for at least two batches (minimum pilot scale) of the active substance from the current and proposed manufacturers/sites. This equates to validation batches.
In the US the process validation guidance does not contain information as specific as a change in the API, nor does Part 211 specifically require validation for a change in the API. However, CFR 314.70 - NDA supplements - does require a supplement be filed for a change in the "new drug substance". It is clear that there is no explicit requirement to validate when changing an API source.
The Federal Food, Drug and Cosmetic Act section 506A reads as follows:
(b) VALIDATION OF EFFECTS OF CHANGES.-For purposes of subsection (a)(1), a drug made with a manufacturing change (whether a major manufacturing change or otherwise) may be distributed only if, before distribution of the drug as so made, the holder involved validates the effects of the change on the identity, strength, quality, purity, and potency of the drug as the identity, strength, quality, purity, and potency may relate to the safety or effectiveness of the drug.
Having said that, validation is certainly a common industry practice, makes good science and good common sense. It is conceivable that sufficient lab experimentation, testing, supplier qualification, etc., could be conducted and support a decision not to validate. However, validation seems like a more sensible approach.
It is often where you don't expect to see a difference that you find unexpected issues.
Regards
Siegfried
Original Message:
Sent: 03-14-2013 04:50
From: Tom Namsavanh
Subject: Process validation
Hi Siegfried,
I do not completely agree. It is possible to assess (maybe indirectly through its DMF) the manufacture and quality of the proposed API supplier and compare it with the current API supplier. I would say re-validation is not necessary, and usually concurrent long-term stability data and dissolution comparison should suffice. Again, this is from my experience with simple immediate release dosage form, i.e. tablets.
Regards,
-------------------------------------------
Tom Namsavanh RAC
Manager, Regulatory Affairs and Compliance
Intelgenx Corp.
Saint-Laurent QC
Canada
-------------------------------------------
Original Message:
Sent: 03-14-2013 04:13
From: Siegfried Schmitt
Subject: Process validation
Dear Ashish
The answer is, yes you must. Validation is not transferable, nor is there evidence that the APIs are indeed identical. Just because they both meet specifications does not mean they are the same.
It is very likely that you will see differences in either process behaviour, analytical results (e.g. for stability samples) and yields.
Regards
Siegfried
-------------------------------------------
Siegfried Schmitt
Principal Consultant
PAREXEL
Braintree, Essex
United Kingdom
-------------------------------------------
Original Message:
Sent: 03-13-2013 15:48
From: Ashish Prashar
Subject: Process validation
This message has been cross posted to the following Discussions: Global Regulatory and Products News (GRPN) and Regulatory Open Forum .
-------------------------------------------
Hi,
I have one query, if anyone can help. If we have perform process validation of Finish product with API from X vendor now after adding API vendor Y do we need to perform again process validation of FP batches Mfg with this Y API, if there is no difference in API quality or impact on FP or process etc.
-------------------------------------------
Ashish
Senior Regulatory Executive
United Kingdom
-------------------------------------------