TRV-2026-1921Version 1 · Certified

Written 2026-10-19 18:14:12 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1921
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-19T18:14:12.591488Z
status: published
lens: g_space
sector: health
headline: Real-world before-and-after evaluation of AI support for lung cancer diagnosis at three US lung nodule clinics
dek: Background Health systems and payers require evidence that artificial intelligence (AI)-enabled decision support improves care delivery. Integrating AI into lung nodule management pathways may streamline workflows, improve identification and triage of patients with pulmonary nodules, and enable earlier lung cancer diagnosis. Yet real-world evidence of clinical utility remains limited. This study evaluated the impact of implementing commercially available AI software to support the lung nodule and lung cancer car…
gain_title: After AI software was implemented, monthly new patients at three lung nodule clinics rose from 11.0 to 18.6 and monthly invasive procedures rose from 4.9 to 8.0.
problem_title: (none)
trace_subject: (none)
gain_reading: After AI software was implemented, monthly new patients at three lung nodule clinics rose from 11.0 to 18.6 and monthly invasive procedures rose from 4.9 to 8.0.
gain_evidence: new patients increased from 138 before to 232 after implementation | Monthly patients undergoing at least one invasive procedure increased from 4.9 to 8.0 (p = 0.0085)
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers compared matched 12.5-month periods before and after commercially available AI software was introduced into lung nodule and lung cancer care pathways at three US health systems. The number of new patients seen rose from 138 to 232, and monthly patients undergoing an invasive procedure climbed from 4.9 to 8.0, both statistically significant.

The findings suggest AI-assisted identification and triage may widen access to specialist review, which matters to health systems and payers seeking evidence of clinical utility. However, the diagnostic outcomes that matter most, such as cancers found and time to diagnosis, did not change significantly, so the benefit for patients remains unproven.
limitation: 
tag: Evidence-backed gain
key_points: Median monthly new patients rose from 9 to 16 across the three clinics after implementation. | Monthly cancers moved from 3.0 to 3.8, which was not statistically significant (p = 0.3242). | Monthly early-stage (I-II) cancers rose from 1.4 to 2.4, also not statistically significant (p = 0.125). | Median time to diagnosis was essentially unchanged at 58 versus 57 days, though the interquartile range narrowed from 125 to 58 days.
rundown: The study used a real-world before-and-after design at three US lung nodule clinics, with matched pre- and post-implementation periods of 12.5 months each. Primary outcomes were new patient numbers and patients undergoing at least one invasive procedure.

Secondary outcomes included total lung cancers, early-stage cancers, and time from baseline CT to diagnosis. Analyses used Wilcoxon signed-rank and Mann-Whitney U tests, reporting medians and interquartile ranges for continuous measures.

The authors conclude the software was associated with significantly increased throughput and procedural volume. The narrower spread in time to diagnosis hints at more consistent timelines, though the median did not shift meaningfully.
sources:
- peer_reviewed | PLOS One | https://doi.org/10.1371/journal.pone.0358655 | 2026-10-14
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
9050f38acf30c72f96cdc3419620ec2f82059df5e052b2a0cb92f8bfea26f595
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1921 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.