Fixation of Periprosthetic Femoral Shaft Fractures Adjacent to a Well-Fixed Femoral Stem With Reversed Distal Femoral Locking Plate
Bibliographic record
Abstract
BACKGROUND: Numerous fixation methods have been described for the fixation of Vancouver type B1 periprosthetic fractures, but there have been a very few reports in the literature regarding the use of locking plates and their outcomes for this fracture. The objective of this study was to analyze clinically and radiographically, the results of fixation of Vancouver type B1 periprosthetic femoral fractures with a reversed distal femoral locking plate. METHODS: Thirteen consecutive patients with Vancouver type B1 periprosthetic femoral fracture were stabilized with reversed distal femoral locking plate. Patients were followed up at 2, 6, 12, 24, and 48 weeks and yearly thereafter. They were assessed clinically and radiographically for union, delayed union, malunion, hardware failure, nonunion, infection, and stability of the femoral prosthesis. RESULTS: The average duration of follow-up was 18 months. All fractures healed at an average of 14 weeks from fixation. Complications include superficial wound infection in one and flare-up of previous infection in one with union at 20 and 28 weeks, respectively. Twelve femoral prostheses were stable and all patients were ambulatory, with or without a walking aid at final follow-up. There was no hardware failure or nonunion. CONCLUSIONS: Reversed distal femoral locking plate treatment is a feasible and effective choice for stabilization with femoral stem retention after Vancouver type B1 periprosthetic femoral fracture in an elderly patient population.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 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.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".