MétaCan
Menu
Back to cohort
Record W2035752671 · doi:10.1177/0961203309346505

SLEDAI-2K for a 30-day window

2009· article· en· W2035752671 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueLupus · 2009
Typearticle
Languageen
FieldMedicine
TopicSystemic Lupus Erythematosus Research
Canadian institutionsToronto Western HospitalUniversity of Toronto
Fundersnot available
KeywordsMedicineWindow (computing)Internal medicineWorld Wide WebComputer science

Abstract

fetched live from OpenAlex

The aim of our study was to determine whether the SLEDAI-2K calculated using a timeframe of 30 days prior to a visit for clinical and laboratory variables was equivalent to the prescribed 10-day period. One hundred forty nine consecutive lupus patients seen over 9 weeks at the University of Toronto Lupus Clinic enrolled. The SLEDAI-2K score was completed twice, for a 10- and 30-day window. Forty patients had a classic SLEDAI-2K activity score of 0 and 109 patients had varying levels of disease activity ranging from 1 to 31. In all but one patient, there was agreement between the SLEDAI-2K 10 and 30 days. Thus SLEDAI-2K 30 days is similar to SLEDAI-2K 10 days, both in patients in remission and with a spectrum of disease activity levels. SLEDAI-2K 30 days may now be used to describe disease activity over the previous 30 days.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.175
Threshold uncertainty score0.627

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.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.027
GPT teacher head0.325
Teacher spread0.298 · 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