TruaceTracing the truth around AIMonday, July 20, 2026
TRV-2026-0314Certified recordPeer-reviewed

Quantifying the impact of slice thickness on cardiovascular risk stratification in lung cancer screening: a multi-center "RESCUE" study

Background: Patients undergoing routine non-gated chest computed tomography (CT) for health checkups or atypical chest discomfort often present with a coronary artery calcium (CAC) score of zero on standard 5.0 mm reconstructions. We hypothesized that these thick slices obscure mild calcification due to partial volume effects (PVEs), which could be recovered by retrospective analysis of native thin-slice images. This study aimed to quantify the rate of unrecognized coronary calcification on standard thick-slice…

Health · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

Retrospective AI quantification of routinely available thin-slice chest CT reclassifies patients from CAC zero to positive, improving sensitivity for early subclinical atherosclerosis without additional radiation.

Current reading — problem

Standard 5.0 mm chest CT reconstructions obscure mild calcification due to partial volume effects, causing significant false-negative CAC zero assessments in routine screening.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0314, v1: “Quantifying the impact of slice thickness on cardiovascular risk stratification in lung cancer screening: a multi-center "RESCUE" study.” Truvace, 2026-07-20. /record/TRV-2026-0314 (accessed at citation time). sha256 1ab7ddf11fe59495

Calibration history

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

  1. Certifiedv11ab7ddf11fe5

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