MétaCan
Menu
Back to cohort

Delayed Removal of Clavicular Hook Plates; The Effect onComplications and Functional Outcome

2018· article· en· W2907043826 on OpenAlex
Nathan Campbell, Ihab Hujazi, Jeremy Viner, Hans Marynissen

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

VenueInternational Journal of Orthopaedics · 2018
Typearticle
Languageen
FieldMedicine
TopicShoulder and Clavicle Injuries
Canadian institutionsRoyal Ottawa Mental Health Centre
Fundersnot available
KeywordsMedicineSurgeryComplicationHookSignificant differenceInternal medicineDentistry

Abstract

fetched live from OpenAlex

This study aimed to determine whether leaving a clavicular hook plate in-situ for longer than six months is associated with a greater complication rate and reduced function compared to when removed within six months as recommended by manufacturer. Patients treated with a hook plate at our institute between January 2005 and October 2015 were categorised into two groups: removed within six months (group A); removed after six months (group B). Complications, ASES and SST score were compared between the groups. Fifty-two patients were identified with 30 patients in group A and 22 patients in group B. There was no significant difference between the groups in the outcome measures obtained from ASES or SST (p = 0.52; p = 0.33) or the complication rate (p = 0.83). Our study suggests that there is no difference between shoulder function and complication rate when the hook plate was removed after six months compared to when removed within six months.

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.000
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.049
Threshold uncertainty score0.256

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.020
GPT teacher head0.378
Teacher spread0.358 · 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