TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0846Certified recordPeer-reviewed

EXPRESS: Relation between Albumin-Corrected Anion Gap and In-Hospital Mortality in Patients with Traumatic Lung Injury: A Multicenter Retrospective Cohort Study and the Development of Machine Learning-Based Prediction Models

Background The anion gap is primarily utilized as an indicator for evaluating acid-base imbalances in critically ill patients. However, its accuracy is reduced in such patients due to low albumin levels. The albumin-corrected anion gap (ACAG) enhances the accuracy of assessing acid-base imbalances. Individuals with traumatic lung injury (TLI) in the intensive care unit (ICU) often have severe metabolic acidosis and hypoalbuminemia. Nevertheless, the association of ACAG with the prognosis of patients with TLI is…

Health · P Space — documented harm · certified 2026-08-22 · v1 · article view · machine-readable

Current reading — problem

EXPRESS: Relation between Albumin-Corrected Anion Gap and In-Hospital Mortality in Patients with Traumatic Lung Injury: A Multicenter Retrospective Cohort Study and the Development of Machine Learning-Based Prediction Models: Elevated ACAG was substantially linked to a high risk of mortality in individuals with TLI (hazard ratio (HR) [95% confidence interval (CI)] = 1.115 [1.037-1.199]).

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0846, v1: “EXPRESS: Relation between Albumin-Corrected Anion Gap and In-Hospital Mortality in Patients with Traumatic Lung Injury: A Multicenter Retrospective Cohort Study and the Development of Machine Learning-Based Prediction Models.” Truvace, 2026-08-22. /record/TRV-2026-0846 (accessed at citation time). sha256 2ccfa3c165166605

Calibration history

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

  1. Certifiedv12ccfa3c16516

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