Ontario doctors' AI transcription tool hallucinated and generated clinical errors, auditor finds

What Happened

Ontario's auditor general found that an AI transcription tool deployed for the province's physicians hallucinated content and inserted errors into clinical records, per findings reported by CBC News. The system was operating inside live medical documentation workflows when the errors were identified, meaning corrupted output had already been written back to patient records before detection. The findings emerged through a formal audit rather than vendor self-reporting or clinician complaints, giving them evidentiary standing that anecdotal reports lack. The available reporting does not disclose error types, error volumes, or confirmed patient harm.

Why It Matters

Clinical documentation sits upstream of nearly every downstream hospital decision: diagnosis coding, prescribing, referral letters, billing, and the medico-legal record. A hallucinating transcription layer does not fail loudly — it produces fluent, plausible text that passes casual human review and becomes permanent. The Ontario finding converts hallucination risk in clinical ASR and LLM scribing from a vendor-disputed theoretical into an audited fact, which changes procurement leverage for every health system evaluating these tools. Buyers now have a government audit to cite in RFPs, indemnity negotiations, and contract terms, and vendors can no longer dismiss the risk as speculative. The audit also validates what compliance and clinical informatics teams have argued without hard evidence: human-in-the-loop review is a control to be specified and audited, not a feature to be marketed.

Technical Details

The failure mode is characteristic of LLM-based or hybrid ASR-plus-LLM pipelines, where an acoustic model produces a draft transcript and a language model rewrites, summarizes, or "cleans" it before write-back to the EHR. Hallucination typically occurs when the generative layer fills gaps in ambiguous audio with contextually plausible but factually incorrect clinical content; drug names, dosages, negations, laterality, and temporal markers are common corruption points. Unlike keyword-spotting ASR errors, these substitutions are grammatically fluent and semantically coherent, which defeats regex filters, spell-checkers, and most confidence-threshold gateways. Detection generally requires source-audio comparison or LLM-as-judge verification against the raw transcript, both of which add latency and cost to the pipeline. Per available reporting, the Ontario deployment did not include a disclosed mechanism that reliably caught these errors before EHR write-back.

Operational Impact

For operators running or procuring clinical transcription, "human review" must now be specified as a defined workflow step with an audit trail rather than a checkbox. That means timestamped draft-versus-final diffs, clinician attestation captured in the EHR, and retention of source audio for a defined window so errors can be reconstructed post-hoc. Builders should expect compliance teams to require segment-level confidence scoring rather than document-level, with low-confidence spans flagged for mandatory review instead of silent regeneration. The cost structure of a scribe product rises accordingly: verification passes, diff storage, and clinician review time become part of the unit economics, not overhead. Vendors that ship verifiable review workflows with exportable auditor evidence gain a defensible position in regulated procurement that accuracy marketing alone cannot match.