-
- Posts: 512
- Joined: Tue Jul 19, 2011 9:26 pm
- If the supplier of the API changes the synthetic route or if the supplier of the final product changes the API source they MUST inform you. THEN it's time to do a risk analysis and based on this analysis consider further actions, possibly revalidating analytical methods.Please read carefully about my original description:
you just supposed that DS is made by us.
In reality, there are many cases companies outsource both API and excipients and formulate them together using some special techs.
You cannot guarantee the supplier of API/excipicents does not change the synthetic route;
Besides, the method can be validated on early phases (so it can be transferred), not necessary to be at final formulation.
Why do you think the USP method can not be transferred? ok, officially, it is called method verification. Can you answer my former question about how to verify a USP method in your own lab?
- There's NOTHING you can do in advance to circumvent this. Do you want to consider every possible synthetic route of the API during method validation? And yes - it's the VALIDATION where this should be considered, not the transfer.
- "the method can be validated on early phases (so it can be transferred), not necessary to be at final formulation". Validation on early phases? You might consider doing some pre-validation work, but, as said above, once you change the product, the method is not valid anymore. You MUST revalidate in this case.
- There's certainly a difference between transferring a method and implementing a USP method in your lab: there's no transfer partner in the latter case
