Insights From Inputs: Enhancing Revision Total Joint Arthroplasty Resource Allocation With Machine Learning Prediction
Bibliographic record
Abstract
BACKGROUND: Revision total knee arthroplasty (rTKA) and revision total hip arthroplasty (rTHA) are among the most resource-intensive orthopaedic procedures. The primary aim of this study was to compare the accuracy of machine learning models between administrative and institutional datasets for predicting duration of surgery, length of stay, and 30-day hospital readmission for rTKA and rTHA based on preoperative factors and identify significant predictive features. METHODS: A national quality improvement database was queried from 2014 to 2019, and a local institutional arthroplasty database was queried from 2012 to 2022 for rTKAs and rTHAs. Datasets were independently split into training, validation, and testing and normalized based on year. Artificial neural networks (ANNs) for both procedures and each outcome were created, and their performance was compared to multivariable regression models. Models were compared between datasets using buffer accuracy (BA). Feature importance of ANNs was retrieved using Shapley Additive exPlanations values. RESULTS: A total of 22,851 and 1,025 rTKA and 14,262 and 703 rTHA patients were included from the national and institutional datasets, respectively. For duration of surgery, the institutional ANNs outperformed the national ANNs with a 76.2 versus 45.4%, and 55.4 versus 43.1% 30-minute BA for rTKA and rTHA, respectively. For length of stay, the national ANNs yielded a superior 2-day BA than the institutional ANNs of 81.8 versus 67.7%, and 71.4 versus 48.2% for rTKA and rTHA, respectively. The 30-day readmission prediction using the national database had area under the curve scores of 0.593 and 0.590 for rTKA and rTHA, respectively. CONCLUSIONS: The performance of ANN models varied significantly by dataset, but all models were superior to using historic averages. Future work should consider using accurate, arthroplasty-specific datasets based on the important features identified. LEVEL OF EVIDENCE: III.
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.002 | 0.016 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".