hmm...according to the FDA requirements, I think you are required to perform a validation on your own sets of system unless the clients specified.
Actually, if you can point me to a reference for that requirement, I'd be grateful. My interpretation has always been that transferrability is what system suitability is all about. To quote from a current FDA draft document:
Basically, if your system meets the system suitability test(s), it is suitable for the analysis.
hm...the way I read it is that the system suitability has to be within criteria in order for the data result to be valid, provided by the fact that the full system validation or partial validation was done by the user or developer. Therefore, the user laboratory should always perform at least partial validation (if stability test is established, then the stability test might not be required...etc) according to (
http://www.fda.gov/cder/guidance/cmc3.pdf). I can be wrong.
Anyway, I always advise the clients to perform at least the partial validation to avoid the trouble from the auditor.
"Methods validation should not be a one-time situation to fulfil Agency filing
requirements, but the methods should be validated and also designed by the developer or user to ensure ruggedness or robustness. Methods should be reproducible when used by other analysts, on other equivalent equipment, on other days or locations, and throughout the life of the drug product. Data that are generated for acceptance, release, stability, or pharmacokinetics will only be trustworthy if the methods used to generate the data are reliable. The process of validation and method design also
should be early in the development cycle before important data are enerated. Validation should be on-going in the form of re-validation with method changes."