Post #57 describes the usual case. This is about the unusual one.
Precision and repeatability: within-run and between-run variability of the method. Acceptance criterion is typically a relative standard deviation of ≤2% for area measurements.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Post #57 describes the usual case. This is about the unusual one.
Precision and repeatability: within-run and between-run variability of the method. Acceptance criterion is typically a relative standard deviation of ≤2% for area measurements.
System suitability is the ongoing evidence that a validated method is still performing. Validation is done once; suitability is done every run, and it is the one that appears on a certificate.
Anyone who has looked at this more carefully, please correct the record.
The distinction between a qualified instrument and a validated method is worth keeping. Both are needed and they fail in different ways.
That is one dataset and I would not build a rule on it.
Precision and repeatability: within-run and between-run variability of the method. Acceptance criterion is typically a relative standard deviation of ≤2% for area measurements.
The answer changed when I changed how I was measuring, which was informative.
Transfer between laboratories: a method can be transferred from one lab to another, but the receiving lab needs to demonstrate that they can achieve the same performance. This requires comparative testing and sometimes small method refinements.
The mechanism is plausible, which is not the same as established.
That is the distinction I keep failing to hold on to. Written down now.
Specificity: the method can distinguish the intended compound from related impurities and degradation products. Tested by comparing results on pure compounds, mixtures of compounds, and degraded samples.
That is what I would do. It may not be what is correct.
Linearity across the working range is a routine demonstration and it constrains how far a result can be extrapolated. A method linear from 80 to 120 per cent of nominal says nothing about a sample at ten per cent.
Everything in post #70 holds. The case it does not cover is the one I have.
Limits of detection and quantitation: LOD is the lowest concentration that produces a signal above background. LOQ is the lowest concentration at which the method meets precision and accuracy acceptance criteria. Both are determined empirically.
Building on post #72 rather than restating it.
Accuracy: the method measures what you intend to measure. For purity methods, this is tested by spike-and-recover experiments: add a known amount of impurity to a sample and measure whether you recover the added amount.
This has been discussed before and I could not find the thread, so, again.
Answering the stability-indicating method question as asked, then the question I think is meant. As asked: yes, with the qualification below. As meant: it depends on how the first measurement was taken.
Stability-indicating method is well covered in the tag pages, and the older discussions are better than the recent ones because they were argued out properly. Worth twenty minutes before adding to this one.
Range: the concentration range over which the method has been validated. Going outside the validated range is going outside the method's demonstrated performance.
Where I part company with post #74, and it is a narrow parting.
Validation is compound-specific and matrix-specific. A method validated for one peptide is a starting point for another and not a validated method for it.
Adding a source would improve this post and I do not have one to hand.
Specificity is the first question: does the method separate the analyte from everything reasonably expected to be present? A method that has not been challenged with its own degradation products has not answered it.
That is my reading. Someone else read the same page differently and was reasonable.
Forced degradation studies: deliberately stress the material with acid, base, oxidant, heat, light to generate degradation products and demonstrate that the method can separate them from the parent peak. Acceptance is that the method is stability-indicating.
Worth checking against a second source before it gets quoted onward.
Robustness: the method gives consistent results when minor parameters vary. Tested by deliberately varying pH, temperature, flow rate, and mobile phase composition within reasonable ranges and demonstrating that results stay within acceptance.
I have left out the parts I could not verify.
Why two laboratories may disagree: after validating the same method, they may still report different purity on the same sample due to integration differences, column age differences, subtle differences in mobile phase pH or temperature. This is normal and not a sign that one is wrong.
It reads as pedantry until the day it does not.
Answering the question post #79 raises rather than the one it answers.
A method transferred between laboratories needs a demonstration that it performs equivalently, not just a document describing it. Transfer is where a great many between-laboratory disagreements originate.
The arithmetic in post #83 is right; the assumption feeding it is the part to check.
A method that reports the same number for every lot is worth a second look. Real processes vary, and a total absence of variation is a statement about the measurement rather than the process.
Stability-indicating method would be much easier to settle if anyone reported the denominator. Almost nobody reports the denominator.
A stability-indicating method is one demonstrated to resolve the analyte from its degradation products, usually through forced degradation. Calling a method stability-indicating without that work is a claim rather than a property.
Reading it back, the second half matters more than the first.
Right, and stated more narrowly than I would have dared to state it.
Robustness testing deliberately varies the parameters most likely to drift — organic percentage, pH, temperature, flow — and shows the result does not. It is the part of validation that predicts whether a method will transfer.