MétaCan
Menu
Back to cohort
Record W4415506485 · doi:10.1136/bmj-2025-084194

Covariate adjustment in cluster randomised trials: a practical guide

2025· article· en· W4415506485 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueBMJ · 2025
Typearticle
Languageen
FieldMathematics
TopicStatistical Methods and Bayesian Inference
Canadian institutionsOttawa HospitalUniversity of Ottawa
FundersUC Berkeley College of ChemistryCollaboration for Leadership in Applied Health Research and Care - Greater ManchesterMedical Research CouncilNational Institute for Health and Care Research
KeywordsCovariateMissing dataOutcome (game theory)Imputation (statistics)Cluster (spacecraft)Confidence intervalIdentification (biology)

Abstract

fetched live from OpenAlex

Covariate adjustment can offer several potential benefits in the analysis of cluster randomised trials. These benefits include increasing statistical precision (ie, narrowing width of confidence intervals), as well as potentially reducing any bias arising from differential identification and recruitment across arms or missing outcome data. This article outlines a guideline for how to choose covariates to include in a prespecified adjustment plan for such trials. Recommendations include adjusting for covariates that have been included in any restricted randomisation; and adjusting for a prespecified set of covariates thought to be prognostic of the outcome, differential recruitment, or outcome missingness. When the prevalence of missing covariate or outcome data are non-negligible, a missing data technique such as multiple imputation (allowing for clustering), cluster mean imputation, or the missing indicator method, is recommended. In a case study, the proposed prespecified analysis plan includes adjustment for minimisation variables as well as four covariates thought to be prognostic of the outcome and potentially related to unblinded identification of participants after randomisation.

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 imitation

Not 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.

metaresearch head score (Codex)0.007
metaresearch head score (Gemma)0.072
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.119
Threshold uncertainty score0.936

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0070.072
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.200
GPT teacher head0.517
Teacher spread0.317 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it