TRV-2026-1709Certified recordPeer-reviewed

Broader factors associated with current adolescent overweight/obesity status in YRBSS 2023: Survey-aware analysis and calibrated AI-assisted classification

Adolescent overweight and obesity are shaped by demographic, behavioral and psychosocial factors, but it remains unclear whether broader predictor information improves cross-sectional classification of current overweight/obesity status more consistently than changing the machine-learning algorithm. This cross-sectional secondary analysis used 2023 Youth Risk Behavior Surveillance System data from 17,814 United States adolescents aged 12-18 years. Survey-aware multivariable logistic regression was used to identif…

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

Current reading — gain

Extended predictor sets raised discrimination for both tree-based models on held-out data, and isotonic recalibration made predicted probabilities far more reliable for the selected Random Forest model.

What this doesn’t fix

Predictors and BMI status were measured in the same survey cycle, so the models classify current status rather than predict future obesity. Any screening or prevention use would require prospective and external validation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1709, v1: “Broader factors associated with current adolescent overweight/obesity status in YRBSS 2023: Survey-aware analysis and calibrated AI-assisted classification.” Truvace, 2026-10-17. /record/TRV-2026-1709 (accessed at citation time). sha256 9b34ba2fcff92841…

Calibration history

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

  1. Certifiedv19b34ba2fcff9…

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