Using Machine Learning (XGBoost) to Predict Outcomes After Infrainguinal Bypass for Peripheral Artery Disease
Bibliographic record
Abstract
OBJECTIVE: To develop machine learning (ML) algorithms that predict outcomes after infrainguinal bypass. BACKGROUND: Infrainguinal bypass for peripheral artery disease carries significant surgical risks; however, outcome prediction tools remain limited. METHODS: The Vascular Quality Initiative database was used to identify patients who underwent infrainguinal bypass for peripheral artery disease between 2003 and 2023. We identified 97 potential predictor variables from the index hospitalization [68 preoperative (demographic/clinical), 13 intraoperative (procedural), and 16 postoperative (in-hospital course/complications)]. The primary outcome was 1-year major adverse limb event (composite of surgical revision, thrombectomy/thrombolysis, or major amputation) or death. Our data were split into training (70%) and test (30%) sets. Using 10-fold cross-validation, we trained 6 ML models using preoperative features. The primary model evaluation metric was the area under the receiver operating characteristic curve (AUROC). The top-performing algorithm was further trained using intraoperative and postoperative features. Model robustness was evaluated using calibration plots and Brier scores. RESULTS: Overall, 59,784 patients underwent infrainguinal bypass, and 15,942 (26.7%) developed 1-year major adverse limb event/death. The best preoperative prediction model was XGBoost, achieving an AUROC (95% CI) of 0.94 (0.93-0.95). In comparison, logistic regression had an AUROC (95% CI) of 0.61 (0.59-0.63). Our XGBoost model maintained excellent performance at the intraoperative and postoperative stages, with AUROCs (95% CI's) of 0.94 (0.93-0.95) and 0.96 (0.95-0.97), respectively. Calibration plots showed good agreement between predicted and observed event probabilities with Brier scores of 0.08 (preoperative), 0.07 (intraoperative), and 0.05 (postoperative). CONCLUSIONS: ML models can accurately predict outcomes after infrainguinal bypass, outperforming logistic regression.
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.004 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| 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".