PERIPROSTHETIC FRACTURES IN A REGIONAL UNIT
Bibliographic record
Abstract
Periprosthetic fractures after total hip arthroplasty are challenging, with potential difficulties associated not only with the fracture but also with implant loosening and bone loss. The incidence of periprosthetic fractures is gradually increasing. We undertook this study to evaluate the periprosthetic fractures presenting to our unit in terms of mechanism of failure, classification and treatment. Charts of patients with periprosthetic fractures presenting within the past six years were retrospectively analysed for demographic and injury details and corresponding radiographs were reviewed to classify the fracture and follow treatment. 45 fractures were identified, with an average age of 78.3 years. The male to female ratio was 5:4. Only 4 fractures occurred in revision prostheses. Two fractures were intraoperative. The Vancouver system was used to classify the fractures, which can also form a basis for treatment. Three fractures of Vancouver type A were managed conservatively without complication. Thirteen fractures were Vancouver type B1, 12 of which underwent internal fixation, mostly plate osteosynthesis; two of these subsequently failed. Recent fractures have been stabilised using locking plates, with no recorded failures. Fifteen fractures were Vancouver type B2, 11 of which were greater than 5 years post arthroplasty. Most underwent revision of the femoral component. Five of these patients had reported pain for some time preceding fracture. Seven fractures were Vancouver type B3, all occurring greater than 7 years post arthroplasty. Most underwent femoral revision. Seven fractures were Vancouver type C, all underwent plate fixation without failure. Although there is variability within the group studied, this series demonstrates gradual standardisation of treatment with use of locking plates and a preferred long revision femoral stem. The reports of pain preceding fracture in a proportion of the Vancouver B2 group prompts greater postoperative surveillance in patients with early signs of femoral loosening.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".