<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="letter"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e103162</article-id><article-id pub-id-type="doi">10.2196/103162</article-id><article-categories><subj-group subj-group-type="heading"><subject>Letter to the Editor</subject></subj-group></article-categories><title-group><article-title>AI Scribe Safety: Measuring What Happens After Signing</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Sorin</surname><given-names>Vera</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Klang</surname><given-names>Eyal</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Radiology, Mayo Clinic Hospital</institution><addr-line>Rochester</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff2"><institution>Department of Radiology, Beth Israel Deaconess Medical Center</institution><addr-line>330 Brookline Avenue</addr-line><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Iannaccio</surname><given-names>Amanda</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Coristine</surname><given-names>Andrew</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Eyal Klang, MD, Department of Radiology, Beth Israel Deaconess Medical Center, 330 Brookline Avenue, Boston, MA, 02215, United States, 1-617-754-9500; <email>eyalklang@gmail.com</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>10</day><month>8</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e103162</elocation-id><history><date date-type="received"><day>31</day><month>05</month><year>2026</year></date><date date-type="rev-recd"><day>16</day><month>07</month><year>2026</year></date><date date-type="accepted"><day>17</day><month>07</month><year>2026</year></date></history><copyright-statement>&#x00A9; Vera Sorin, Eyal Klang. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 10.8.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://medinform.jmir.org/2026/1/e103162"/><related-article related-article-type="commentary article" ext-link-type="doi" xlink:href="10.2196/89337" xlink:title="Comment on" xlink:type="simple">https://medinform.jmir.org/2026/1/e89337/</related-article><abstract><p>Coiera and Fraile-Navarro question whether AI scribes are being evaluated on metrics that truly impact care. While current evaluations focus on the quality of the initial draft, signed clinical notes are dynamic, as their content can be copied, summarized, coded, and re-ingested by downstream AI tools. We argue that safety must be measured downstream, focusing on how small errors in initial documentation can compound across the patient&#x2019;s electronic health record.</p></abstract><kwd-group><kwd>artificial intelligence</kwd><kwd>AI</kwd><kwd>digital scribes</kwd><kwd>medical scribes</kwd><kwd>electronic documentation</kwd><kwd>patient safety</kwd><kwd>error prevention</kwd></kwd-group></article-meta></front><body><p>In a recent <italic>JMIR Medical Informatics</italic> editorial, Coiera and Fraile-Navarro ask whether artificial intelligence (AI) scribes are being measured on what matters [<xref ref-type="bibr" rid="ref1">1</xref>]. We agree with their central point: scribe output shapes what downstream clinicians and systems see and act upon. We build on that point by focusing on what happens to documentation errors after a note is signed and integrated into the health record.</p><p>This is far from theoretical. Reddy et al [<xref ref-type="bibr" rid="ref2">2</xref>] compared notes from 11 ambient AI scribe tools with human notes across 5 standardized primary care visits; they found that human notes scored higher in thoroughness, organization, and usefulness in clinical context . Similarly, a pragmatic pilot study also found omissions, hallucinations, and other errors in AI-generated clinician notes [<xref ref-type="bibr" rid="ref3">3</xref>]. These flaws can persist beyond the initial draft and propagate after the note is signed.</p><p>A signed clinical note is not the end of a visit. Another clinician may read it, a later note may copy it forward, or a referral may summarize it. Orders, billing codes, quality measures, registries, and downstream AI tools may rely on it. Thus, small errors can compound.</p><p>For instance, if dyspnea is omitted, the next clinician may not know it was discussed. If a medication dose is wrong, the next medication list may repeat it. If the reason for a plan is missing, a later clinician may follow it without knowing why. In the electronic health record (EHR), an AI-generated omission may be copied, summarized, coded, or used as input for another AI system.</p><p>This risk is familiar: EHRs already spread errors through copy-paste, copy-forward, and reused text [<xref ref-type="bibr" rid="ref4">4</xref>]. Ambient AI scribes add another entry point: one error can become source material for later care.</p><p>While clinician review is thus necessary, it cannot catch every flaw. Omissions are hard to detect because the notes do not show omissions. Future studies should follow errors across the lifecycle of the the clinical note: from the visit to the AI draft, signed note, and subsequent notes, referrals, handoffs, orders, patient instructions, registries, and AI summaries. Was the information complete and correct when reused? Was it corrected? Did it affect care? These questions align with established EHR data-quality work [<xref ref-type="bibr" rid="ref5">5</xref>].</p><p>Our goal is not to reject ambient AI scribes, as documentation burden is a critical challenge. However, as Coiera and Fraile-Navarro argue, safety should be measured across the clinical workflow. We maintain that studies should follow the note after signing. The question is not only whether AI scribes produce acceptable first drafts, but whether their errors stay contrained or become part of the patient&#x2019;s clinical story.</p></body><back><ack><p>Generative AI was used for spelling, grammar, and language refinement. The authors reviewed and take full responsibility for the final text.</p></ack><notes><sec><title>Funding</title><p>The authors declared no financial support was received for this work.</p></sec><sec><title>Data Availability</title><p>Data sharing is not applicable to this article as no data sets were generated or analyzed.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: VS, EK.</p><p>Writing &#x2013; original draft: VS, EK.</p><p>Writing &#x2013; review &#x0026; editing: VS, EK.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AI</term><def><p>artificial intelligence</p></def></def-item><def-item><term id="abb2">EHR</term><def><p>electronic health record</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Coiera</surname><given-names>E</given-names> </name><name name-style="western"><surname>Fraile-Navarro</surname><given-names>D</given-names> </name></person-group><article-title>AI scribes: are we measuring what matters?</article-title><source>JMIR Med Inform</source><year>2026</year><month>02</month><day>6</day><volume>14</volume><fpage>e89337</fpage><pub-id pub-id-type="doi">10.2196/89337</pub-id><pub-id pub-id-type="medline">41650281</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Reddy</surname><given-names>A</given-names> </name><name name-style="western"><surname>Gunnink</surname><given-names>E</given-names> </name><name name-style="western"><surname>Wheat</surname><given-names>CL</given-names> </name><etal/></person-group><article-title>Rapid evaluation of artificial intelligence technology used for ambient dictation in primary care: comparing the quality of documentation of artificial intelligence-generated and human-produced clinical notes</article-title><source>Ann Intern Med</source><year>2026</year><month>06</month><volume>179</volume><issue>6</issue><fpage>765</fpage><lpage>772</lpage><pub-id pub-id-type="doi">10.7326/ANNALS-25-02772</pub-id><pub-id pub-id-type="medline">41996184</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Taylor</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Jost</surname><given-names>M</given-names> </name><name name-style="western"><surname>MacDonald</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Quality of clinical notes created by ambient listening generative ai: pragmatic prospective pilot study</article-title><source>JMIR Med Inform</source><year>2026</year><month>04</month><day>17</day><volume>14</volume><fpage>e86474</fpage><pub-id pub-id-type="doi">10.2196/86474</pub-id><pub-id pub-id-type="medline">41996389</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tsou</surname><given-names>AY</given-names> </name><name name-style="western"><surname>Lehmann</surname><given-names>CU</given-names> </name><name name-style="western"><surname>Michel</surname><given-names>J</given-names> </name><name name-style="western"><surname>Solomon</surname><given-names>R</given-names> </name><name name-style="western"><surname>Possanza</surname><given-names>L</given-names> </name><name name-style="western"><surname>Gandhi</surname><given-names>T</given-names> </name></person-group><article-title>Safe practices for copy and paste in the ehr. systematic review, recommendations, and novel model for health IT collaboration</article-title><source>Appl Clin Inform</source><year>2017</year><month>01</month><day>11</day><volume>8</volume><issue>1</issue><fpage>12</fpage><lpage>34</lpage><pub-id pub-id-type="doi">10.4338/ACI-2016-09-R-0150</pub-id><pub-id pub-id-type="medline">28074211</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Penev</surname><given-names>YP</given-names> </name><name name-style="western"><surname>Buchanan</surname><given-names>TR</given-names> </name><name name-style="western"><surname>Ruppert</surname><given-names>MM</given-names> </name><etal/></person-group><article-title>Electronic health record data quality and performance assessments: scoping review</article-title><source>JMIR Med Inform</source><year>2024</year><month>11</month><day>6</day><volume>12</volume><fpage>e58130</fpage><pub-id pub-id-type="doi">10.2196/58130</pub-id><pub-id pub-id-type="medline">39504136</pub-id></nlm-citation></ref></ref-list></back></article>