MétaCan
Menu
Back to cohort
Record W2332763508 · doi:10.1097/bco.0000000000000209

Shape-matching

2015· article· en· W2332763508 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

VenueCurrent Orthopaedic Practice · 2015
Typearticle
Languageen
FieldMedicine
TopicTotal Knee Arthroplasty Outcomes
Canadian institutionsJuravinski HospitalHamilton Health SciencesMcMaster University
Fundersnot available
KeywordsCoronal planeSagittal planeMedicineRadiographyOrthodonticsTotal knee arthroplastyLimitingImplantSurgeryRadiology

Abstract

fetched live from OpenAlex

Background: Shape-matching technology provides preoperative three-dimensional templating of total knee arthroplasty (TKA) placement to restore optimal kinematics for the native prearthritic knee. Despite an accurate preoperative plan to construct cutting jigs for placement of the femoral and tibial implants in a TKA, it is hypothesized that the actual implementation or reproduction of this placement of implants remains suboptimal. Methods: A retrospective radiographic review of 67 primary unilateral TKAs performed using the OtisMed™ (OM, Stryker, Kalamazoo, MI) shape-matching technology was conducted to determine how closely the computer-generated OM preoperative plan resembled the postoperative femoral and tibial implant position in both the coronal and sagittal planes. Results: Preoperative and postoperative measurements were correlated in the coronal (r=0.407, P=0.001), but not the sagittal plane (r=−0.124, P=0.329). Postoperative coronal alignment differed from the preoperative plan more than 3° in 33.3% of cases, while sagittal alignment differed more than 3° in 56.3% of cases. Conclusions: A significant number of cases did not achieve precise placement of the implants per the OM plan, most notably in the sagittal plane. While these differences are noteworthy, the limiting factor still remains our ability to precisely execute the plan.

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.005
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.895
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.002

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.062
GPT teacher head0.359
Teacher spread0.297 · 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