TRV-2026-1819Certified recordPeer-reviewed

Ambient Artificial Intelligent Scribes in Oncology: Impact on Clinician Experience and Documentation Burden

PURPOSE Ambient artificial intelligence (AI) scribes, widely implemented to reduce clinician burden and dissatisfaction, are not optimized for oncology. We evaluated this technology at-scale at a high-volume cancer center. METHODS This prospective mixed-methods study used surveys, electronic health record (EHR), and utilization data to assess adoption, burden, and satisfaction with an ambient AI scribe that was implemented from June to September 2025. Descriptive statistics categorized clinicians as adopters (3+…

Health · The Trace — both readings · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

Among oncology clinicians who completed both surveys, high or excessive note-writing time fell after the AI scribe rollout, and most postrollout respondents said they would recommend it.

Current reading — problem

Despite enterprise-wide implementation and training, only about one in five oncology clinicians used the AI scribe, and measured note-closing and after-hours documentation changes were small or inconsistent.

What this doesn’t fix

Adoption was low and survey samples were small (45 paired respondents, 77 postrollout), and the authors say adoption barriers and tool optimization still need study, so the results may not represent all oncology clinicians.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1819, v1: “Ambient Artificial Intelligent Scribes in Oncology: Impact on Clinician Experience and Documentation Burden.” Truvace, 2026-10-18. /record/TRV-2026-1819 (accessed at citation time). sha256 d7a496d747d92287…

Calibration history

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

  1. Certifiedv1d7a496d747d9…

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