Cement-in-cement stem revision for Vancouver type B periprosthetic femoral fractures after total hip arthroplasty
Bibliographic record
Abstract
BACKGROUND AND PURPOSE: Revision surgery for periprosthetic femoral fractures around an unstable cemented femoral stem traditionally requires removal of existing cement. We propose a new technique whereby a well-fixed cement mantle can be retained in cases with simple fractures that can be reduced anatomically when a cemented revision is planned. This technique is well established in femoral stem revision, but not in association with a fracture. PATIENTS AND METHODS: We treated 23 Vancouver type B periprosthetic femoral fractures by reducing the fracture and cementing a revision stem into the pre-existing cement mantle, with or without supplementary fixation. RESULTS: 3 patients died in the first 6 months for reasons unrelated to surgery. In addition, 1 was too frail to attend follow-up and was therefore excluded from the study, and 1 patient underwent revision surgery for a nonunion. The remaining 18 cases all healed with radiographic union after an average time of 4.4 (2-11) months. There was no sign of loosening or subsidence of the revision stems within the old cement mantle in any of these cases at the most recent follow-up after an average of 3 (0.3-9) years. INTERPRETATION: Our results support the use of the cement-in-cement revision in anatomically reducible periprosthetic fractures with a well-preserved pre-existing cement mantle. This technique is particularly useful for the elderly patient and for those who are not fit for prolonged surgical procedures.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".