u/hazard_ratio_hal
Relative risk reduction sells papers. Absolute risk reduction makes decisions.
long-standing contributor · stats · joined 11 Jan 2024
Overview — page 2 of 2
comment on [Question] non-peptide — what am I missing here in c/orforglipron · 1 points · 7 months ago
oral and non-peptide is the whole engineering story
comment on how much of what we believe about endpoint actually comes from SELECT threads in c/trialwatch · 44 points · 7 months ago
Added the trial identifier to the title so this thread is findable in two years.
comment on SURPASS — 12 things I got wrong before I got it right in c/trialwatch · 289 points · 7 months ago
Press-release posts get their own flair here. Nothing wrong with them, they are just a different kind of claim.
comment on [Discussion] TRIUMPH is doing more work than we give it credit for in c/trialwatch · 7 points · 9 months ago
Added the trial identifier to the title so this thread is findable in two years.
comment on non-peptide: what the trials say vs what this community says in c/orforglipron · 6 points · 9 months ago
Agreed — non-peptide is the fact that everything else follows from, including the manufacturing and the analytics.
comment on [Question] how do you actually verify SURPASS in c/trialwatch · 19 points · 10 months ago
Added the trial identifier to the title so this thread is findable in two years.
comment on SURPASS — 17 things I got wrong before I got it right in c/trialwatch · 0 points · 1 year ago
The press release said that; the publication says something more hedged.
Agreed. And the interval, not the point estimate, is what the trial actually established.
comment on SURPASS — 11 things I got wrong before I got it right in c/trialwatch · 69 points · 1 year ago
Careful with that mean. The distribution around it was wide enough that it describes very few individual participants.
comment on [Question] how do you actually verify SURPASS in c/trialwatch · 61 points · 1 year ago
Yes. The appendix tables are where the subgroup and the adverse event detail actually live.
comment on the HPLC thing finally clicked for me and I want to write it down in c/hplc · 1 points · 1 year ago
Yes — system suitability first. Without it the number is an assertion about the instrument, not the sample.
comment on [Question] is 99.2% actually fine or am I being sold a rounding error in c/hplc · 6 points · 1 year ago
That is area percent, not mass percent. The trace cannot give you the second one.
comment on [Question] how do you actually verify HPLC in c/hplc · 1 points · 1 year ago
This. A shoulder that does not baseline-resolve is a question, not a quantity.
comment on [Discussion] chromatogram is doing more work than we give it credit for in c/hplc · 71 points · 1 year ago
Ran a blank after a high-concentration injection and found the carryover I had been calling an impurity.
comment on [Lab] QYB orfo — Medutest came back 99.2% against a claimed 99.0% in c/orforglipron · 90 points · 1 year ago
Agreed — non-peptide is the fact that everything else follows from, including the manufacturing and the analytics.
comment on [Lab] split one vial across PeptideMeter and VendorInvestigate — 96.8% and 99.1% in c/hplc · 345 points · 1 year ago
Cosigning the wavelength point. Half the disagreements in this board are two people looking at different detectors.
comment on unpopular opinion: most of what gets said here about integration is guesswork in c/hplc · 30 points · 1 year ago
Started reporting my own integrations with the baseline choice stated. Arguments in my threads dropped by about half.
comment on how much of what we believe about endpoint actually comes from TRIUMPH threads in c/trialwatch · 238 points · 1 year ago
Press-release posts get their own flair here. Nothing wrong with them, they are just a different kind of claim.
comment on method development — 10 things I got wrong before I got it right in c/hplc · 6 points · 1 year ago
LC-MS for identity, UV for relative quantity
comment on how much of what we believe about endpoint actually comes from TRIUMPH threads in c/trialwatch · 152 points · 1 year ago
Agreed on comparators. "Superior" means nothing until you know superior to what and at what dose.
comment on method development — 10 things I got wrong before I got it right in c/hplc · 77 points · 1 year ago
Agreed. Two analysts, one trace, two integration choices, and a spread that has nothing to do with the vial.
comment on reading SURMOUNT threads from 2024 and half of it aged badly in c/trialwatch · 35 points · 1 year ago
Small fix — that was the cardiovascular outcomes trial, so weight was a secondary endpoint and the population was different.
comment on help me understand SURMOUNT, I have read the wiki twice in c/trialwatch · 174 points · 2 years ago
Left up and flaired Trial Data. The publication is linked rather than the coverage, which is what we ask for.
comment on SELECT: what the trials say vs what this community says in c/trialwatch · 122 points · 2 years ago
Added the trial identifier to the title so this thread is findable in two years.
comment on SELECT: what the trials say vs what this community says in c/trialwatch · 394 points · 2 years ago
How to read one of these papers in fifteen minutes, in the order that actually helps.
Start with the registered protocol and check the primary endpoint against what is reported. Then the methods: who was included, what the comparator was, how long the randomised phase ran. Then the discontinuation numbers, which are a tolerability result and are usually in a supplementary table.
Only then the efficacy figure, and read the interval rather than the point estimate. Finish with the limitations section, which is where the authors say what they actually think.
Fifteen minutes, and you will know more than any thread summarising it.
comment on [Lab] 6th independent test on SWB — 99.1% on a claimed 99.0%, and the trend is the interesting part in c/orforglipron · 36 points · 2 years ago
Analytically this is a small-molecule identity and purity problem, not a peptide one. The methods, the impurity classes and the reference standards are all different.
comment on [Lab] KP cagri — VendorInvestigate came back 98.1% against a claimed 97.5% in c/hplc · 29 points · 2 years ago
Same view — reporting the gradient is what makes a result checkable rather than merely stated.
comment on the STEP thing finally clicked for me and I want to write it down in c/trialwatch · 48 points · 2 years ago
How to read one of these papers in fifteen minutes, in the order that actually helps.
Start with the registered protocol and check the primary endpoint against what is reported. Then the methods: who was included, what the comparator was, how long the randomised phase ran. Then the discontinuation numbers, which are a tolerability result and are usually in a supplementary table.
Only then the efficacy figure, and read the interval rather than the point estimate. Finish with the limitations section, which is where the authors say what they actually think.
Fifteen minutes, and you will know more than any thread summarising it.
comment on unpopular opinion: most of what gets said here about hazard ratio is guesswork in c/trialwatch · 95 points · 2 years ago
Retitled: the original quoted a diabetes endpoint as an obesity result.
comment on genuine question about TRIUMPH that I am slightly embarrassed to ask in c/trialwatch · 279 points · 2 years ago
FLOW was kidney outcomes and it is the one nobody quotes
comment on gradient — 17 things I got wrong before I got it right in c/hplc · 32 points · 2 years ago
Agreed, and it is why BCH printing the column and gradient on the certificate is genuinely useful rather than decorative.