MétaCan
Menu
Back to cohort
Record W2776607725 · doi:10.1037/pha0000152

On how patients with multiple sclerosis weigh side effect severity and treatment efficacy when making treatment decisions.

2017· article· en· W2776607725 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

VenueExperimental and Clinical Psychopharmacology · 2017
Typearticle
Languageen
FieldMathematics
TopicStatistical Methods in Clinical Trials
Canadian institutionsGreo
FundersNational Multiple Sclerosis Society
KeywordsSide effect (computer science)MedicinePsycINFOMultiple sclerosisIntensive care medicineMEDLINEPsychiatry

Abstract

fetched live from OpenAlex

Although effective disease-modifying treatments (DMTs) are available for individuals suffering from multiple sclerosis (MS), many patients fail to take their recommended medications. Unlike medications that provide immediate relief from existing symptoms, DMTs decrease the probability of future symptoms (i.e., a probabilistic benefit) while concurrently carrying an appreciable risk of immediate side effects (i.e., a probabilistic cost). Prior research has shown that both the probability of reducing disease progression and the probability of experiencing side effects impact patients' likelihood of taking a hypothetical DMT. The role that side effect severity plays in treatment decisions remains unexplored. The present study examined how probability of medication efficacy and side effect severity impact patients' likelihood of taking hypothetical DMTs. Patients' likelihood of taking a DMT systematically decreased as medication efficacy decreased and side effect severity increased. Because side effect severity appears to impact decision-making processes in unique ways, the present results suggest that providers should present information on severe (which are typically rare) and mild to moderate side effects (which are more common) separately. (PsycINFO Database Record

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.001
metaresearch head score (Gemma)0.008
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.747
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.008
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.001
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.392
GPT teacher head0.560
Teacher spread0.168 · 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