MétaCan
Menu
Back to cohort
Record W2022152445 · doi:10.1007/s11999-008-0194-7

Do Patient Expectations of Spinal Surgery Relate to Functional Outcome?

2008· article· en· W2022152445 on OpenAlex
Albert Yee, Nana Adjei, Jennifer Do, Michael Ford, Joel Finkelstein

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

VenueClinical Orthopaedics and Related Research · 2008
Typearticle
Languageen
FieldMedicine
TopicSpine and Intervertebral Disc Pathology
Canadian institutionsHealth Sciences CentreUniversity of TorontoSunnybrook Health Science Centre
Fundersnot available
KeywordsMedicineSurgeryDecompressionPatient satisfactionPhysical therapyOrthopedic surgerySurgical decompressionVitalityOutcome (game theory)

Abstract

fetched live from OpenAlex

It is important for surgeons to understand patients' expectations for surgery. We asked whether patient factors and preoperative functional outcome scores reflect the degree of expectations patients have for posterior spinal surgery. Second, we asked whether patients' expectations for surgery predict improvements in functional outcome scores after surgery. We prospectively enrolled 155 consecutive surgical patients with greater than 90% followup. Patients' expectations were evaluated preoperatively along with SF-36 and Oswestry disability questionnaires. Postoperatively (6 months for decompression; 1 year for fusions), we quantified patient-derived satisfaction regarding whether expectations were met and by patient-derived functional outcome scores. In patients undergoing decompression, gender, SF-36 general health domain, and SF-36 physical component score predicted patients with high expectations for surgery. Patients with high expectations also reported greater postoperative improvements in SF-36 role physical domain scores after surgery. Expectations for surgery were met in 81% of patients. In a subset of patients (21 of 143), expectations were not met. These patients reported lower mean preoperative SF-36 general health, vitality, and mean mental component scores.

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.002
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.042
Threshold uncertainty score0.473

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.288
GPT teacher head0.475
Teacher spread0.187 · 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