MétaCan
Menu
Back to cohort
Record W7028717593

Fracturas femorales periprotésicas

2007· article· en· W7028717593 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueDialnet (Universidad de la Rioja) · 2007
Typearticle
Languageen
FieldComputer Science
TopicNonlinear Dynamics and Pattern Formation
Canadian institutionsnot available
Fundersnot available
KeywordsPeriprostheticOrthopedic surgeryIncidence (geometry)Consolidation (business)
DOInot available

Abstract

fetched live from OpenAlex

Introduction: The incidence of periprosthetic fractures has been increasing in the last 2 decades, representing a serious challenge even for the best trained orthopedic surgeons. The Vancouver classification has largely contributed to a better characterization and therapeutic approach. The aims of this study are to review the latest advances on this topic, and present our experience in the treatment of theses fractures. Methods: Based on the Vancouver classification we evaluated 46 patients treated in 2 different institutions from March 1995 to December 2005. Results: Average age: 74.5 (range 23-87). There was a predominance of females (71.73%). 5 cases were Type A of the Vancouver classification, 32 Type B, and 9 Type C. 44 patients received surgical treatment. Average hospitalization time: 12 days (range 9-34 days). Average consolidation time in type B and C fractures was 4 months, (range 3-6 months). Six patients presented complications. Ten cases were evaluated as excellent (22.72%), 28 as good (63.63%) and 6 as poor (13.65%). Conclusions: A careful individual evaluation based on Vancouver classification, age, and the patient’s functional requirements are the most important parameters for a successful outcome.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.537
Threshold uncertainty score0.444

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.001
Open science0.0010.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.009
GPT teacher head0.254
Teacher spread0.245 · 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