TRV-2026-2313Certified recordPeer-reviewed

Clinical Phenotypes, Machine-Learning Risk Stratification and Treatment Outcomes of Constipation in Stroke Patients Receiving Enteral Nutrition: A Retrospective Study

Background: Stroke-related complications and frequent feeding interruptions often compromise nutritional intake, making enteral nutrition (EN) a cornerstone therapy to improve nutritional status and support recovery. Nevertheless, constipation is highly prevalent and clinically consequential among stroke patients receiving EN, particularly in critically ill populations, where enteral nutrition-associated constipation can impede rehabilitation, increase complications and prolong intensive care unit (ICU) stay. Ai…

Health · Good Space — documented gain · certified 2026-10-29 · v1 · article view · machine-readable

Current reading — gain

With full-hospitalisation data, a machine-learning model (Table PFN-3) predicted constipation in stroke ICU patients on tube feeding with good discrimination (ROC-AUC 0.771) and close calibration.

What this doesn’t fix

The models were validated only internally on retrospective data, and the expanded model used information that becomes available only later in hospitalisation. Treatment comparisons were descriptive, and the clustering silhouette coefficient was low (0.108).

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2313, v1: “Clinical Phenotypes, Machine-Learning Risk Stratification and Treatment Outcomes of Constipation in Stroke Patients Receiving Enteral Nutrition: A Retrospective Study.” Truvace, 2026-10-29. /record/TRV-2026-2313 (accessed at citation time). sha256 ca17546ee57dc1be…

Calibration history

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

  1. Certifiedv1ca17546ee57d…

    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-2313 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.