Users' guide to detecting misleading claims in research: Authors' reply
Bibliographic record
Abstract
Users' guide to detecting misleading claims in researchMisleading claims may be symptom of even more serious flaws Editor-Montori et al justifiably draw attention to misleading claims in published clinical trials. 1 This is a serious and common problem. 2 3 However, I object to their radical proposal that only the methods and results sections should be read, while the remainder of the paper should be ignored.The proposal is inconsistent with the title of their paper, "Users' guide to detecting misleading claims in clinical research reports." 1 How are these misleading claims to be identified if the sections containing them are omitted?Furthermore, anyone capable of critically appraising a trial solely on the basis of the methods and results is unlikely to be fooled by misleading claims in the discussion.But, more importantly, the proposal would deprive the discerning reader of witnessing the conflict between the results and the unwarranted conclusions.If researchers are willing to disseminate misleading claims then their integrity is brought into question.But if so, then all aspects of the trial-including the methods and results sections-are also brought into question.Misleading claims should be identified and broadcast loudly for they signal doubts about the entire study.Large scale randomised trials create the ideal conditions for data manipulation.Yet this is merely one of a multitude of problems stemming from a flawed method. 3 The remedy?When reading a study, ignore everything except the number of patients recruited.If this is large proceed no further as there is little prospect of encountering any data of genuine benefit to patients.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.084 | 0.439 |
| Meta-epidemiology (narrow) | 0.004 | 0.004 |
| Meta-epidemiology (broad) | 0.007 | 0.005 |
| Bibliometrics | 0.006 | 0.008 |
| Science and technology studies | 0.008 | 0.022 |
| Scholarly communication | 0.014 | 0.017 |
| Open science | 0.015 | 0.010 |
| Research integrity | 0.114 | 0.105 |
| Insufficient payload (model declined to judge) | 0.030 | 0.058 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".