52/100

Moderate evidence

Published recordHealthGeneral

Toward Clinically Interpretable Perioperative Decision Support: Explainable Machine Learning for 30-Day Postoperative Mortality Prediction

Truvace record
TRV-2026-1207raw data (JSON)
Version
v2Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
52e5332f6da5…check it

Postoperative mortality prediction remains a critical challenge in healthcare, demanding robust and interpretable predictive methods. This study developed and evaluated machine learning (ML) models using the novel Informative Surgical Patient dataset for Innovative Research Environment (INSPIRE), a comprehensive perioperative dataset, to predict 30-day postoperative mortality. Patient-specific features such as ASA physical status, BMI, and temporal medical parameters were incorporated. Data imbalance was address…

The gain

Machine learning models trained on perioperative data achieved high discrimination for 30-day postoperative mortality and identified clinically meaningful predictors, supporting more transparent surgical risk assessment and patient counseling.

Sources

1 on file
  1. The American Surgeon™doi:10.1177/00031348261484511
    Peer-reviewed2026-09-23

Cite this record

v2

Truvace Impact Record TRV-2026-1207, v2: “Toward Clinically Interpretable Perioperative Decision Support: Explainable Machine Learning for 30-Day Postoperative Mortality Prediction.” Truvace, 2026-11-04. /record/TRV-2026-1207 (accessed on the day you copy it). sha256 52e5332f6da5cd1d…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv252e5332f6da5…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain unsupported, problem absent).

  2. Publishedv124b11f5f0212…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1207 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.