TRV-2026-1897Certified recordPeer-reviewed

Longitudinal effects of ambient artificial intelligence scribe use on documentation burden and financial productivity in primary care: a quasi-experimental study

Abstract Objectives To investigate the longitudinal effects of an ambient artificial intelligence (AI) scribe use in primary care on outcomes related to documentation time, note writing patterns, and clinician financial productivity. Materials and Methods We conducted a quasi-experimental study with an interrupted time-series design to ascertain the effect of AI scribe use on note writing time, time outside of scheduled hours (TOSH), pajama time (5:30PM-7:00aM), note length, note closure <24 h, and work relative…

Health · Good Space — documented gain · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

Across 220 primary care clinicians, ambient AI scribe use was linked to a growing reduction in note writing time, less after-hours work, and a slight increase in work relative value units by day 150.

What this doesn’t fix

The study measured outcomes only over 150 days before and after initial access and used a quasi-experimental rather than randomized design, so longer-term effects and causality remain less certain.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1897, v1: “Longitudinal effects of ambient artificial intelligence scribe use on documentation burden and financial productivity in primary care: a quasi-experimental study.” Truvace, 2026-10-19. /record/TRV-2026-1897 (accessed at citation time). sha256 d93f7bb009880d50…

Calibration history

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

  1. Certifiedv1d93f7bb00988…

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