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

Improving turnaround times with artificial intelligence in microbiology

This dual-center study evaluated the impact of artificial intelligence (AI) on urine culture turnaround times in Canadian diagnostic laboratories using microbiology laboratory automation. Data were collected before and after the implementation of PhenoMATRIX (PM), an AI-based software that provides continuous culture sorting and result interpretation support. In both a low-volume tertiary care hospital and a high-volume community laboratory, PM enabled earlier availability of interpretable results; however, redu…

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

Current reading — gain

In two Canadian diagnostic laboratories, AI-based PhenoMATRIX urine culture assessment enabled earlier availability of interpretable results and reduced time to result reporting by about 1.3 hours with automated PM+ release at a tertiary hospital and about 5.3 hours with earlier manual screening at a community lab.

Current reading — problem

At the low-volume tertiary care hospital, implementing PhenoMATRIX alone without a timely release workflow was associated with increased time to result reporting due to delays between result availability and reporting.

What this doesn’t fix

TTRR benefits were not automatic from AI alone; reductions depended on timely result release processes, either automated reporting or optimized manual review workflows.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0322, v1: “Improving turnaround times with artificial intelligence in microbiology.” Truvace, 2026-07-20. /record/TRV-2026-0322 (accessed at citation time). sha256 5b375b0faf42786b

Calibration history

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

  1. Certifiedv15b375b0faf42

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