The reporting checklist for public versions of guidelines: RIGHT-PVG
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
BACKGROUND: Public or patient versions of guidelines (PVGs) are derivative documents that "translate" recommendations and their rationale from clinical guidelines for health professionals into a more easily understandable and usable format for patients and the public. PVGs from different groups and organizations vary considerably in terms of quality of their reporting. In order to address this issue, we aimed to develop a reporting checklist for developers of PVGs and other potential users. METHODS: First, we collected a list of potential items through reviewing a sample of PVGs, existing guidance for developing and reporting PVGs or other similar evidence-based patient tools, as well as qualitative studies on original studies of patients' needs about the content and/or reporting of information in PVGs or similar evidence-based patient tools. Second, we conducted a two-round Delphi consultation to determine the level of consensus on the items to be included in the final reporting checklist. Third, we invited two external reviewers to provide comments on the checklist. RESULTS: We generated the initial list of 45 reporting items based on a review of a sample of 30 PVGs, four PVG guidance documents, and 46 relevant studies. After the two-round Delphi consultation, we formed a checklist of 17 items grouped under 12 topics for reporting PVGs. CONCLUSION: The RIGHT-PVG reporting checklist provides an international consensus on the important criteria for reporting PVGs.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.015 | 0.084 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 it