Building on post #28 rather than restating it.
If you are new and reading this thread for the answer to robustness: the answer is conditional, the conditions are in the third reply, and the rest of the thread is worth skipping.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Building on post #28 rather than restating it.
If you are new and reading this thread for the answer to robustness: the answer is conditional, the conditions are in the third reply, and the rest of the thread is worth skipping.
The arithmetic on robustness is the easy part and it is where the errors are, which is an uncomfortable combination. Show your working and someone will catch it.
Reading rather than answering, but this is the post I would point somebody at.
My position on robustness is current rather than settled. I have revised it once already and I expect to again, so treat it accordingly.
Precision has two levels worth distinguishing: repeatability within a run and intermediate precision across days, analysts and instruments. The second is where most methods lose the numbers people quote.
If that is already documented somewhere, ignore me and link it.
A note on how robustness gets discussed rather than on robustness itself: the confident posts get the replies and the careful ones get ignored, and the careful ones have been right more often.
Coming back to post #39, because the follow-up matters more than the original answer.
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.
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.
Happy to be corrected if someone holds better data than mine.
Nothing to add, except that this is the answer I would give if asked.
Post #43 answers the question as asked. The question underneath it is different.
A definition problem is doing most of the work in this robustness discussion. Once the term is pinned down I suspect the disagreement mostly goes away and what is left is small.
I would be cautious about generalising from the robustness example above. It is a good example. It is one example.
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.
I would not lead a decision with this, but I would not ignore it either.
Two sentences on robustness and then I will stop, because the rest is speculation and the thread is better without mine.
What is documented is narrow. What is inferred from it is broad. The gap between them is where every argument here lives.
Post #47 is the version of this I will quote in future. One addition.
The limit of quantitation determines what the impurity table can honestly contain. Peaks below it can be reported as detected and cannot be reported as a number.
I would want to see it done twice before believing it once.
The distinction between a qualified instrument and a validated method is worth keeping. Both are needed and they fail in different ways.
Anyone who has looked at this more carefully, please correct the record.
On robustness, the part that usually goes wrong is that the question is asked as though it has one answer. It has a range, and the width of the range is the interesting bit.
If you can post the two or three numbers you are working from, several people here will check the arithmetic rather than argue about the conclusion.
Saving this. It is the version I will quote when the question comes round again.
Where a pharmacopoeial monograph exists, a method that follows it inherits a great deal of assurance. Almost nothing discussed here has one.
I am not the right person to answer the follow-up to this.
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.
The mechanism is plausible, which is not the same as established.
The arithmetic in post #55 is right; the assumption feeding it is the part to check.
The most useful single question about a method: what would it fail to detect? Every method has an answer and few documents state it.
Robustness has been discussed here with more heat than it deserves, mostly because two definitions have been in play the whole time.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
What a stability-indicating method is and how you demonstrate one — one year on
What a stability-indicating method is and how you demonstrate one — one year on I have a specific reason for asking rather than idle curiosity, and the context is below. Asking about stability-indicating…
|
+100 | 112 | 15k | 19mo |
|
Revisiting: Sample handling between despatch and injection
Posting this under the heading it deserves: Revisiting: Sample handling between despatch and injection Everything below is what sits behind that. Reading back through what has been written here about Sample…
|
+5 | 9 | 1.1k | 6mo |
|
LOD and LOQ: definitions people get wrong
LOD and LOQ: definitions people get wrong — setting out what I have, and where I think it stops being reliable. What changes if the standard account of LOD and LOQ is wrong? I ask because I have been treating…
|
2 | 43k | 8mo | |
|
Validating a method you did not develop — does this still hold?
Validating a method you did not develop — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. Validating a method, and specifically the version of…
|
+128 | 148 | 47k | 16mo |
|
Second pass at: Robustness: the parameters worth deliberately varying
On the subject in the title: Second pass at: Robustness: the parameters worth deliberately varying Working notes rather than a conclusion. Something about Robustness does not reconcile and I would like a…
|
+61 | 66 | 9.5k | 3mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
What a stability-indicating method is and how you demonstrate one
Asking directly, because I could not find a straight answer: What a stability-indicating method is and how you demonstrate one Posting a small dataset on stability-indicating method. It is mine, it is…
|
4 | 57k | 6mo | |
|
Spike-and-recover accuracy for a peptide assay
Posting this under the heading it deserves: Spike-and-recover accuracy for a peptide assay Everything below is what sits behind that. Asking about spike-and-recover accuracy on behalf of the question I keep…
|
+121 | 126 | 1.5k | 4mo |
|
Second pass at: LOD and LOQ: definitions people get wrong
Posting this under the heading it deserves: Second pass at: LOD and LOQ: definitions people get wrong Everything below is what sits behind that. Something about LOD and LOQ does not reconcile and I would like…
|
+47 | 51 | 40k | 10mo |
|
An inter-laboratory comparison on one lot, tabulated
On the subject in the title: An inter-laboratory comparison on one lot, tabulated Working notes rather than a conclusion. Collecting what is known about inter-laboratory comparison in one place, because it is…
|
3 | 17k | 10mo | |
|
Repeatability versus intermediate precision — what changed since
Posting this under the heading it deserves: Repeatability versus intermediate precision — what changed since Everything below is what sits behind that. What changes if the standard account of Repeatability…
|
4 | 21k | 5h |