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.
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 rule of thumb is fine; the edge cases are where it earns its keep.
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.
A qualification I should have led with rather than closed on.
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".
Reporting the observation and leaving the explanation open deliberately.
Coming back to post #31, because the follow-up matters more than the original answer.
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.
This follows post #32 rather than contradicting it.
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.
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".
Good question, well framed, and I would like to see it answered properly.
Post #37 and I disagree about the size of the effect, not about the direction.
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.
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.
If that reads as pedantic, it is, and it has saved me twice.
Adding the measurement that post #40 says would settle it.
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.
A modest claim, modestly supported.
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".
Seconded. It reads as careful rather than confident, which is the right register.
Answering the question post #43 raises rather than the one it answers.
When method identifiers are missing: "reversed-phase HPLC" is less specific than "reversed-phase HPLC at 214 nm on a C18 column with a 10 to 40% acetonitrile gradient over 20 minutes". The second lets someone reproduce the analysis. The first does not.
That has been true for the cases I have seen and I have not seen many.
The arithmetic in post #43 is right; the assumption feeding it is the part to check.
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.
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 where I would start, not where I would stop.
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.
I have changed my mind on this once already, so take it as current rather than settled.
Worth separating two things that post #47 runs together.
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".
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.
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.
Old habit: I write down the expected answer before I calculate it.
Everything in post #48 holds. The case it does not cover is the one I have.
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.
I would put this at better than even and not much better.
Staff rationale: Hidden by community flags. The claim about a named supplier was not accompanied by a batch, a date, a method or a document, which R6 requires.
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.
The corresponding entry is in the public moderation log. Hidden posts are never deleted.
The arithmetic in post #52 is right; the assumption feeding it is the part to check.
Method identification means enough to reproduce: column chemistry, dimensions, gradient, flow, wavelength. A method name alone identifies a family of methods.
Posted with less confidence than the sentence structure implies.
Answering the question post #52 raises rather than the one it answers.
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.
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.
I would want to see it done twice before believing it once.
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".
A partial answer, offered because a partial answer beats none.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
A field-by-field walk through a certificate of analysis
Posting this under the heading it deserves: A field-by-field walk through a certificate of analysis Everything below is what sits behind that. I have spent a fortnight trying to pin field-by-field walk…
|
+136 | 147 | 1.8k | 12mo |
|
A checklist for reading a certificate in under two minutes — does this still hold?
A checklist for reading a certificate in under two minutes — does this still hold? — that is the question, and I have not found it answered plainly anywhere I have looked. I would like to understand what this…
|
+49 | 55 | 15k | 9mo |
|
What a certificate commits its issuer to — the long version
Asking directly, because I could not find a straight answer: What a certificate commits its issuer to — the long version A documentation question rather than an analytical one. I have a certificate in front…
|
+20 | 26 | 21k | 2d |
|
Second pass at: A field-by-field walk through a certificate of analysis
Second pass at: A field-by-field walk through a certificate of analysis Writing it up because I had to work it out twice and would rather nobody else did. The question about field-by-field walk through a…
|
+149 | 164 | 36k | 19mo |
|
Counter-ion form: the field almost nobody reports — one year on
On the subject in the title: Counter-ion form: the field almost nobody reports — one year on Working notes rather than a conclusion. The question about Counter-ion form that I actually want answered is the…
|
+121 | 139 | 31k | 16mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Reconciling a label claim with a content assay
On the subject in the title: Reconciling a label claim with a content assay Working notes rather than a conclusion. The question about reconciling a label claim that I actually want answered is the second one…
|
+2 | 6 | 183 | 4mo |
|
One lot is one lot: when a report becomes a pattern — the long version
One lot is one lot: when a report becomes a pattern — the long version — setting out what I have, and where I think it stops being reliable. Structured report rather than an opinion, following the format the…
|
+137 | 152 | 46k | 16mo |
|
Comparing documentation quality across the directory, tabulated
Comparing documentation quality across the directory, tabulated — setting out what I have, and where I think it stops being reliable. I have spent a fortnight trying to pin comparing documentation quality…
|
+7 | 11 | 29k | 19h |
|
Batch numbers that do not match the vial label — what changed since
On the subject in the title: Batch numbers that do not match the vial label — what changed since Working notes rather than a conclusion. What changes if the standard account of Batch numbers is wrong? I ask…
|
+39 | 43 | 14k | 1mo |
|
Coming back to: Why our vendor pages link the storefront and mark it sponsored
Why our vendor pages link the storefront and mark it sponsored I have a specific reason for asking rather than idle curiosity, and the context is below. Reading back through what has been written here about…
|
2 | 22k | 8h |