TREATMENT OF PERIPROSTHETIC FEMORAL FRACTURES AFTER FEMORAL REVISION USING A LONG STEM
Bibliographic record
Abstract
Periprosthetic femoral fractures are becoming increasingly common and are a major complication of total hip arthroplasty (THA) and bipolar hemiarthroplasty (BHA). We report a retrospective review of the outcomes of treatment of 11 periprosthetic fractures after femoral revision using a long stem. Eleven female patients with a mean age of 79.2 years (70 to 91 years) were treated for a Vancouver type B1 fracture between 1998 and 2013. The status of the initial arthroplasty was THA in 5 patients and BHA in 6 patients. The original diagnosis was femoral neck fracture in 5 patients, osteoarthritis in 5 patients, and avascular necrosis of femoral head in 1 patient. Seven patients had had a cemented femoral component and 4 had had a cementless femoral component. The mean numbers of previous surgeries were 3.2 times (2 to 5 times). A previous history of fracture in the same femur was found in 7 hips including 5 femoral neck fractures, 3 periprosthetic fractures. The cause of the latest revision surgery was aseptic loosening in 6 hips, periprosthetic fracture in 3 hips, and infection in 2 hips. The average time to fracture after femoral revision using a long stem was 106.5 months (12 to 240 months). The average follow-up was 58.9 months (8 to 180 months). The fracture pattern was a transverse fracture in 6 hips and an oblique fracture in 5 hips. The type B1 fractures were treated with open reduction and internal fixation in 9 hips, 6 of which were reinforced with bone grafts. Seven patients were treated with a locking compression plate and cerclage wiring, and 2 patients were treated with a Dall-Miles system. Two other periprosthetic fractures were treated with femoral revision. One was revised because of stem breakage, and the other was a transverse fracture associated with very poor bone quality, which received a femoral revision with a long stem and a locking compression plate. All fractures except one achieved primary union. This failed case had a bone defect at the fracture site, and revision surgery using a cementless long stem and allografts was successful. These finding suggest that a type B1 fracture after revision using a long stem associated with very poor bone quality or bone loss might be considered as a type B3 fracture, and femoral revision might be the treatment of choice.
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.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".