TruaceTracing the truth around AIFriday, August 28, 2026
TRV-2026-0919Certified recordPeer-reviewed

An Interpretable Machine Learning Framework with Clinical Nomogram for Predicting In-Hospital Mortality in Acute Ischemic Stroke Using High-Granularity Bedside Data

This multicenter study developed and validated an interpretable machine learning model integrating granular nursing and emergency department data collected within the first 24 hours to predict in-hospital mortality in acute ischemic stroke (AIS). We analyzed a retrospective cohort of 5,014 adult AIS patients from three tertiary academic centers (2019-2023). Centers A and B (n=3,512) formed the development cohort; Center C (n=1,502) served as the external validation cohort. Sixty-three predictors across seven dom…

Health · G Space — documented gain · certified 2026-08-28 · v1 · article view · machine-readable

Current reading — gain

A CatBoost model integrating 22 granular nursing and emergency department features collected within the first 24 hours improved early in-hospital mortality prediction for acute ischemic stroke patients, achieving higher discrimination than established ICU scores in both internal and external validation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0919, v1: “An Interpretable Machine Learning Framework with Clinical Nomogram for Predicting In-Hospital Mortality in Acute Ischemic Stroke Using High-Granularity Bedside Data.” Truvace, 2026-08-28. /record/TRV-2026-0919 (accessed at citation time). sha256 69db72576474a0e8

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv169db72576474

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0919 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.