65/100

Moderate evidence

Published recordHealthGeneral

Distinct clinical patterns of preterm infants vulnerable to intestinal injury identified by unsupervised clustering

Truvace record
TRV-2026-1201raw data (JSON)
Version
v2Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
b522b5c22bd1…check it

Background Current necrotizing enterocolitis (NEC) diagnostic criteria fail to capture the full spectrum of intestinal injury. We aimed to identify diagnosis-independent clinical patterns of intestinal injury among vulnerable very low birth weight (VLBW) infants using unsupervised hierarchical clustering. Methods Using prospectively collected data from 20,352 VLBW infants in the Korean Neonatal Network (2013-2022), unsupervised clustering was performed after excluding variables reflecting prematurity and NEC dia…

The gain

Unsupervised hierarchical clustering of 20,352 VLBW infants identified eight diagnosis-independent clusters of intestinal injury vulnerability, with high-risk Cluster 8 further split into five etiologic subclusters, creating a framework for a more precise taxonomy beyond traditional NEC staging.

Sources

1 on file
  1. Pediatric Researchdoi:10.1038/s41390-026-05494-3
    Peer-reviewed2026-09-23

Cite this record

v2

Truvace Impact Record TRV-2026-1201, v2: “Distinct clinical patterns of preterm infants vulnerable to intestinal injury identified by unsupervised clustering.” Truvace, 2026-11-04. /record/TRV-2026-1201 (accessed on the day you copy it). sha256 b522b5c22bd14f55…

Change history

2 versions

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

  1. Revisedv2b522b5c22bd1…

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

  2. Publishedv1252ca4d23c16…

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