TruaceTracing the truth around AIWednesday, August 5, 2026
TRV-2026-0641Certified recordPeer-reviewed

Comparison of Machine Learning and Logistic Regression in Predicting Mortality from Acute Poisoning in Young Adults: A Multicenter Study Identifying Herbicide Exposure as the Predominant Risk Determinant

Objective Compare the effectiveness of machine learning algorithms and traditional logistic regression in predicting the mortality risk of young patients with acute poisoning, and establish a risk stratification nomogram. Methods This multicenter retrospective study derived a derivation cohort of 406 young adults with acute poisoning from Wenzhou and an external validation cohort of 150 patients from Lishui.LASSO regression was used to screen predictive factors from 43 candidate variables. Compare the predictive…

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

Current reading — gain

Logistic regression achieved comparable discrimination to 14 machine learning algorithms for 28-day mortality prediction in young adults with acute poisoning and enabled a clinically usable nomogram for early risk stratification.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0641, v1: “Comparison of Machine Learning and Logistic Regression in Predicting Mortality from Acute Poisoning in Young Adults: A Multicenter Study Identifying Herbicide Exposure as the Predominant Risk Determinant.” Truvace, 2026-08-04. /record/TRV-2026-0641 (accessed at citation time). sha256 4d05bcf10ac20c80

Calibration history

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

  1. Certifiedv14d05bcf10ac2

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