POST-TRAUMATIC ANKLE COMPLICATIONS TREATED WITH POSTERIOR BLADE PLATE ANKLE ARTHRODESIS
Bibliographic record
Abstract
Purpose: To evaluate the appropriateness of posterior blade plate ankle arthrodesis as a salvage procedure, in a complex subgroup of ankle trauma patients. Methods: We retrospectively identified all patients who underwent an ankle arthrodesis from our prospectively collected trauma database at Vancouver General hospital from 1997 to 2005. We then extracted those who had blade plate arthrodesis via the posterior approach for previous failed fracture fixation or failed previous fusion. Demographics, pre arthrodesis diagnosis, previous surgeries, deformity and complications were recorded. Clinical examination was based on outpatient evaluation and physical evaluation. This was supplemented with radiological follow up to confirm union and outcome scoring using the AOFAS and SF36 systems. Results: Sixteen patients were identified from the trauma database who had undergone posterior blade plate ankle arthrodesis. Of these thirteen were available for follow up. There average age was 47 years (range 23–63 years). The male to female ratio was 3:1. Three cases were for failed previous ankle fusion by other means. Of the remaining ten patients with post traumatic osteoarthritis, seven had previous pilon fractures, two talar fractures and one fracture dislocated ankle. All cases went onto bony union. Patient satisfaction was good although functional outcome scoring was not normal Conclusion: We have found this procedure to have several excellent benefits. It allows the surgeon to operate through virgin skin, reducing potential wound complications, and achieve good soft tissue coverage. The blade plate allows reconstitution of a normal plantar grade ankle and distal tibial orientation, when secured appropriately to bone. Excellent compression and union can be achieved with the AO compression device, but it’s important to have a second screw in the talus to prevent blade pull out. The procedure has good satisfaction among patients following previous failed surgery, as a salvage procedure.
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.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 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".