TRV-2026-2217Version 1 · Certified

Written 2026-10-23 18:34:47 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2217
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-23T18:34:47.364618Z
status: published
lens: g_space
sector: health
headline: Application of machine learning prediction models for in-hospital mortality in diabetic sepsis patients: a study based on the MIMIC IV database
dek: Sepsis complicated by diabetes mellitus represents a significant clinical challenge in intensive care units (ICUs), associated with substantial morbidity and mortality. Accurate prognostication of in-hospital mortality in this complex patient population is crucial for optimizing clinical decision making, resource allocation, and patient management strategies. We conducted a retrospective cohort study utilizing data from the Medical Information Mart for Intensive Care (MIMIC-IV) database. The study focused on adu…
gain_title: A gradient boosting model identified in-hospital mortality risk among ICU patients with sepsis and diabetes more accurately than other algorithms and the SOFA score in a retrospective cohort.
problem_title: (none)
trace_subject: (none)
gain_reading: A gradient boosting model identified in-hospital mortality risk among ICU patients with sepsis and diabetes more accurately than other algorithms and the SOFA score in a retrospective cohort.
gain_evidence: This performance surpassed that of other machine learning algorithms and the conventional SOFA score.
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers used the MIMIC-IV intensive care database to study 7716 adult ICU patients diagnosed with both sepsis and diabetes mellitus, of whom 1357 (17.6%) died in hospital. They compared six machine learning algorithms and the SOFA score on how well each discriminated patients who died from those who survived.

Better prognosis for this complex group could support clinical decisions and resource allocation, and SHAP values were used to show which features drove predictions. However, the results come from a retrospective single database, and the authors say multi-center validation and prospective trials are still needed to test generalizability and clinical impact.
limitation: The findings come from a retrospective analysis of one database, and the authors state that multi-center validation and prospective trials are needed to confirm generalizability and clinical impact.
tag: Evidence-backed gain
key_points: The cohort included 7716 adult ICU patients with concurrent sepsis and diabetes mellitus, drawn from MIMIC-IV. | In-hospital mortality occurred in 1357 patients, or 17.6% of the cohort. | Six algorithms were tested: logistic regression, KNN, random forest, GBDT, XGBoost and LightGBM. | GBDT performed best with an AUC of 0.792 (95% CI: 0.769-0.814), above the SOFA score. | SHAP analysis ranked clinical and demographic predictors to make the model more interpretable.
rundown: The study was a retrospective cohort analysis built on the Medical Information Mart for Intensive Care database. It targeted adults in intensive care who had both sepsis and diabetes, a group the authors describe as a significant clinical challenge with substantial morbidity and mortality.

Model discrimination was measured with the area under the receiver operating characteristic curve. The gradient boosting decision tree model scored highest among the machine learning approaches and also exceeded the conventional SOFA score used as a comparison.

To address interpretability, the team applied SHAP values to explain the relative importance of predictor variables. The authors suggest this could facilitate adoption of such tools in clinical practice, though they have not tested real-world implementation.
sources:
- peer_reviewed | BMC Medical Informatics and Decision Making | https://doi.org/10.1186/s12911-026-03580-4 | 2026-10-22
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
0406ad4dca2721a2aeca7508f839a61b5bda6db4738e7691d49a92d096c1eec2
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2217 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.