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

Radiological assessment of pulmonary vascularity in congenital heart disease: standardized clinician assessment versus deep learning-based prediction

Background Assessment of pulmonary vascularity on chest radiographs (CXRs) in congenital heart disease (CHD) is limited by subjectivity, and existing criteria lack sufficient validation. Artificial intelligence-based deep learning model (DLM) analysis may improve accuracy. We developed and validated structured criteria and a DLM to evaluate pulmonary vascularity and compared it with conventional clinical interpretation. Methods A total of 400 deidentified CXRs from CHD patients with Fick-derived pulmonary-to-sys…

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

Current reading — gain

Artificial intelligence-based deep learning model (DLM) analysis may improve accuracy. Results Intraclass correlation between Fick- and DLM-derived Qp:Qs was 0.782 (P 1.5: 90% specificity, 98% sensitivity, area under the receiver operating characteristic curve [AUROC] 98%; predicting Qp:Qs Conclusion Deep learning-based analysis of CXRs enables accurate evaluation of pulmonary vascularity and outperforms structured assessment by clinicians.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0848, v1: “Radiological assessment of pulmonary vascularity in congenital heart disease: standardized clinician assessment versus deep learning-based prediction.” Truvace, 2026-08-22. /record/TRV-2026-0848 (accessed at citation time). sha256 6cf66d9fbee45ac8

Calibration history

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

  1. Certifiedv16cf66d9fbee4

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