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.
Reading old certificates: if a certificate is dated years ago, the lot it describes might be old. That is not automatically a problem but it is worth noting. Fresh testing on the current lot is stronger than old testing on an older lot.
Correct me on the arithmetic if it is wrong; I would rather know.
Taking post #61 at face value and following it one step further.
A certificate is a statement by its issuer that a defined test was performed on a defined lot and produced a defined result. That is all it is, and it is not nothing.
I read post #61 twice before replying, because I had assumed the opposite.
Practical answer on field-by-field walk through a certificate, since the theoretical one is upthread: do the simplest check first, write down the result, and only then decide whether the complicated explanation is needed. It usually is not.
Endotoxin testing is separate: a certificate of purity says nothing about endotoxin. A chemically pure preparation can carry a clinically significant endotoxin load. If endotoxin matters, it needs to be tested and reported.
I would rather post the uncertainty than round it away.
An itemised related-substances table with retention times says considerably more about the synthesis than a single total. A total tells you how much is not the main peak and nothing about what it is.
The general case is well covered; this is the awkward specific one.
Post #65 is right about the mechanism and I think understates the practical bit.
What fields matter on a certificate: lot number matching the vial, test date, the analytical method stated specifically, the measured result as a number, and the acceptance limit stated separately. A certificate missing any of these is weaker.
On post #65 — agreed on the reasoning, with one qualification.
Reading back through the field-by-field walk through a certificate threads from last year, the same three questions come up every time and only one of them has ever been answered properly. That seems like a documentation gap rather than a knowledge gap.
Picking up post #68: that is the part I would want checked first.
A certificate of analysis is a statement by its issuer that a defined test was performed on a defined lot and produced a defined result. That is all it is, and it is not nothing. What makes it usable: lot identifier matching the container, test date, method identification specific enough to reproduce, the actual result as a number, and the acceptance criterion stated separately from the result.
The distinction between release testing and characterisation is one industrial documents make and retail ones usually do not. It is the difference between "we tested every lot for this" and "we established this once".
The most useful thing anyone has posted about field-by-field walk through a certificate in this category was a table of what had been measured and by whom. That is what I would want again.
Peptide content and chromatographic purity are separate determinations and a certificate that reports only one has answered only one question. Content is the one that tells you how much is in the vial.
The disagreement above is smaller than it looks once the terms are fixed.
On field-by-field walk through a certificate, 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.
Right — I had this wrong and I am glad to have read it before it mattered.
I had written a reply contradicting post #74 and deleted it. Here is what survived.
"Not less than 98 per cent" is a specification. "98.3 per cent" is a result. A certificate carrying only the first has not told you what was measured.
The conclusion is tentative; the arithmetic underneath it is not.
I disagree with the framing of field-by-field walk through a certificate above, and I think it is a substantive disagreement rather than a terminological one. Setting out why, so it can be checked.
The reasoning depends on an assumption that is doing a lot of work and is never stated. If the assumption holds, the conclusion follows. I do not think it holds generally.
Answering the question post #78 raises rather than the one it answers.
Practical note on field-by-field walk through a certificate: write down what you expect before you look. The number of times I have found what I went looking for is higher than chance would allow.
Taking post #79 at face value and following it one step further.
Where two documents for the same lot disagree, the useful question is which was measured and which was transcribed. Most such disagreements are the second.
I would put a moderate confidence on that and no more.
Second-hand on field-by-field walk through a certificate, so weight it accordingly — someone whose method I trust told me this and I have not verified it myself.
Useful. I have added it to my own notes with the date on it.
A certificate of analysis is a statement by its issuer that a defined test was performed on a defined lot and produced a defined result. That is all it is, and it is not nothing. What makes it usable: lot identifier matching the container, test date, method identification specific enough to reproduce, the actual result as a number, and the acceptance criterion stated separately from the result.
Answering the question post #83 raises rather than the one it answers.
Where the field-by-field walk through a certificate discussion usually stalls is that nobody wants to say "I do not know" and everyone is willing to say "it varies". Those are the same sentence with different clothes on.
A chromatogram supplied as a small image is legible for peak shape and not for baseline detail. That is enough to sanity-check an integration and not enough to reproduce it.
That is the honest state of it as of this week.
The distinction between release testing and characterisation is one industrial documents make and retail ones usually do not. It is the difference between "we tested every lot for this" and "we established this once".
I have left out the parts I could not verify.
An observation about field-by-field walk through a certificate that I cannot explain and am posting anyway, on the principle that unexplained observations are more useful public than private.