<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</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">v13i1e92145</article-id>
      <article-id pub-id-type="pmid">42228936</article-id>
      <article-id pub-id-type="doi">10.2196/92145</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Radiologist Perceptions of an AI Tool for Intracranial Hemorrhage Detection in Teleradiology: Cross-Sectional Survey Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lyell</surname>
            <given-names>David</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Baird</surname>
            <given-names>Grayson L</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Del Gaizo</surname>
            <given-names>Andrew J</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Moffitt Cancer Center</institution>
            <addr-line>12902 USF Magnolia Drive,</addr-line>
            <addr-line>Tampa, FL, 33612</addr-line>
            <country>United States</country>
            <phone>1 813 745 4673</phone>
            <email>andrew.delgaizo@moffitt.org</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4438-2082</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Del Gaizo</surname>
            <given-names>Jackson K</given-names>
          </name>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0003-2235-3907</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Shahoumian</surname>
            <given-names>Troy A</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0008-9837-3409</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Moffitt Cancer Center</institution>
        <addr-line>Tampa, FL</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Durham Academy</institution>
        <addr-line>Durham, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Population Health Informatics, Digital Health Office</institution>
        <institution>Veterans Health Administration</institution>
        <addr-line>Washington DC, DC</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Andrew J Del Gaizo <email>andrew.delgaizo@moffitt.org</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>2</day>
        <month>6</month>
        <year>2026</year>
      </pub-date>
      <volume>13</volume>
      <elocation-id>e92145</elocation-id>
      <history>
        <date date-type="received">
          <day>25</day>
          <month>1</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>19</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>13</day>
          <month>4</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>4</day>
          <month>5</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Andrew J Del Gaizo, Jackson K Del Gaizo, Troy A Shahoumian. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 02.06.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 (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2026/1/e92145" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Artificial intelligence (AI) detection tools for intracranial hemorrhage (ICH) are increasingly integrated into radiology workflows. In real-world practice, perceived utility depends not only on diagnostic performance but also on workflow fit, false positive burden, and how clinicians interpret and act on AI outputs.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to characterize radiologists’ perceptions of a Food and Drug Administration (FDA)–cleared ICH AI detection tool in a national teleradiology network, including perceived reliability, false positive burden, workflow impact, medicolegal concerns, and self-reported behaviors during routine use.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted an anonymous cross-sectional survey of radiologists in a national teleradiology practice who had access to an FDA-cleared ICH AI overlay during noncontrast head computed tomography interpretation. Survey items used a 5-point Likert scale. Results are summarized as agreement proportions (“agree” or “strongly agree”) with 95% CIs. We compared neuroradiologists with non-neuroradiologists using Fisher exact tests. One primary end point was prespecified: agreement that time spent reviewing examinations with false positive AI alerts outweighed the benefits. Remaining subgroup comparisons were treated as exploratory, with false discovery rate control using the Benjamini-Hochberg procedure.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 65 radiologists responded, including 23 (35.4%) neuroradiologists and 42 (64.6%) non-neuroradiologists. Only 18.5% (12/65; 95% CI 10.9%-29.6%) agreed that false-positive alerts were infrequent enough to be acceptable. Agreement that the AI correctly identified most ICH cases was 32.3% (21/65; 95% CI 22.2%-44.4%), and agreement that the AI rarely missed clinically important hemorrhages was 43.1% (28/65; 95% CI 31.8%-55.2%). Trust in AI output was conditional: 50.8% (33/65; 95% CI 38.9%-62.5%) reported trusting the AI when it agreed with their interpretation, whereas 3.1% (2/65; 95% CI 0.8%-10.5%) reported trusting it when it conflicted with their interpretation. Only 10.8% (7/65; 95% CI 5.3%-20.6%) reported reduced overall interpretation time, whereas 33.8% (22/65; 95% CI 23.5%-46.0%) agreed that time spent reviewing false-positive alerts outweighed the benefits. Self-reported reduced scrutiny after an AI-negative result was uncommon (4/65, 6.2%; 95% CI 2.4%-14.8%). In subgroup analysis, neuroradiologists more often endorsed the primary end point than non-neuroradiologists (12/23, 52.2% vs 10/42, 23.8%; unadjusted <italic>P</italic>=.03), but no exploratory subgroup differences remained statistically significant after false discovery rate correction. Free-text responses emphasized artifact- and calcification-driven false positives, delayed or inconsistent AI availability, consultation burden, and medicolegal concerns.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>In this national teleradiology setting, radiologists reported substantial false positive burden, limited perceived time savings, and strongly conditional trust in an FDA-cleared ICH AI detection tool. Self-reported reduced scrutiny after negative AI outputs was uncommon but present in a minority of cases. These findings support the importance of specificity, interpretability, latency, and workflow-aware implementation when deploying radiology AI tools in practice.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
        <kwd>intracranial hemorrhage</kwd>
        <kwd>computed tomography</kwd>
        <kwd>teleradiology</kwd>
        <kwd>workflow</kwd>
        <kwd>false positives</kwd>
        <kwd>trust in automation</kwd>
        <kwd>alert fatigue</kwd>
        <kwd>human factors</kwd>
        <kwd>decision support</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Intracranial hemorrhage (ICH) on noncontrast head computed tomography (CT) is a high-stakes diagnosis in emergency and inpatient care requiring timely identification and communication. Artificial intelligence (AI) systems intended to detect ICH are increasingly incorporated into radiology workflows, including as diagnostic assistive tools during radiologist interpretation and, in some implementations, as tools to support prioritization of urgent cases [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. However, the real-world value of these systems depends not only on discriminative performance but also on how they interact with clinical workflow, how often they generate disruptive false-positive alerts, and how clinicians interpret their outputs in routine practice [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>Post-deployment evaluation is increasingly recognized as essential for clinical AI. DECIDE-AI (Developmental and Exploratory Clinical Investigations of Decision Support Systems Driven by Artificial Intelligence) and related implementation literature emphasize that early live clinical evaluation should address workflow integration, human factors, and unintended burdens rather than focusing on accuracy alone [<xref ref-type="bibr" rid="ref5">5</xref>]. Real-world studies of radiology AI have similarly shown that local prevalence, operational context, and implementation strategy can substantially shape perceived utility and clinician acceptance [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. For example, deployment experience with an AI algorithm in clinical practice has highlighted how false discovery burden can create an “accuracy paradox” in which an apparently high-performing system is experienced as inaccurate because positive alerts are frequently false in a low-prevalence setting [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
      <p>Human factors theory suggests that false alarms, workflow interruptions, and opaque outputs can alter clinician reliance on automation [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. In health care more broadly, high alert burden and repeated alerts can contribute to alert fatigue and reduced responsiveness to clinical decision support alerts [<xref ref-type="bibr" rid="ref8">8</xref>]. In radiology, incorrect AI outputs may affect reader confidence and performance, particularly when the AI appears authoritative or visually salient [<xref ref-type="bibr" rid="ref9">9</xref>]. At the same time, survey data alone cannot establish whether AI changes diagnostic behavior; they are better suited to characterizing clinician perceptions, attitudes, and self-reported experiences.</p>
      <p>We previously evaluated a Food and Drug Administration (FDA)–cleared ICH AI tool in a national teleradiology network and reported operational observations, including false positives and radiologist-reported effects on interpretation time [<xref ref-type="bibr" rid="ref1">1</xref>]. The study reported in this paper extends that work by focusing on radiologists’ perceptions during routine exposure to the tool. Specifically, we sought to characterize perceived reliability, false positive burden, workflow impact, medicolegal concerns, and self-reported behaviors during AI-assisted interpretation and explore whether these perceptions differed by neuroradiology subspecialty training.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>This was an anonymous cross-sectional survey study conducted within a national teleradiology practice. This study was designed as a real-world implementation evaluation aligned with early-stage clinical AI assessment principles, with emphasis on workflow context and user experience [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This evaluation met the US Department of Veterans Affairs criteria for quality assessment and nonresearch and received a determination of nonresearch from the Stanford University Institutional Review Board (protocol 73642). Participation was voluntary and anonymous.</p>
      </sec>
      <sec>
        <title>Participants</title>
        <p>Eligible participants were practicing radiologists within the teleradiology group who had access to the ICH AI output during routine noncontrast head CT interpretation. Respondents self-reported whether they had neuroradiology fellowship training or primarily practiced neuroradiology, and responses were stratified as neuroradiologists vs non-neuroradiologists.</p>
      </sec>
      <sec>
        <title>AI Tool and Workflow Context</title>
        <p>The evaluated system was an FDA-cleared and commercially available deep learning algorithm for ICH detection (CINA version 1.0; Avicenna.ai) integrated into the reading workflow for noncontrast head CT. The tool was intended to assist radiologists in identifying suspected ICH during image interpretation and, depending on workflow configuration, could also support prioritization. In practice, radiologists could view AI-generated overlays during interpretation, and the system functioned as an adjunctive diagnostic support tool within routine workflow. The tool did not replace radiologist interpretation, and final clinical interpretation remained the responsibility of the reading radiologist. Because intended use and actual workflow exposure are both relevant to interpretation of user perceptions, we frame these findings as perceptions arising during routine use of the tool in this implementation context.</p>
      </sec>
      <sec>
        <title>Survey Instrument</title>
        <p>The survey included 15 Likert items spanning the following domains: perceived reliability, false positive burden, workflow integration, time impact, medicolegal concerns, adoption preferences, and self-reported behaviors during AI use. Responses were captured on a 5-point scale (“strongly agree,” “agree,” “neutral,” “disagree,” and “strongly disagree”). Items were developed for face validity based on prior operational experience and relevant human factors concepts, but the instrument was not a formally validated psychometric measure. Accordingly, results were interpreted on the face of each item as descriptive measures of respondent perceptions.</p>
      </sec>
      <sec>
        <title>Prespecified End Point and Statistical Analysis</title>
        <p>To limit overinterpretation from multiple comparisons, one primary end point was prespecified: agreement with the following statement: “The extra time spent reviewing AI false-positive studies outweighs the benefits.” This end point was selected because false positive burden was considered a central determinant of usability and adoption in a high-volume teleradiology environment.</p>
        <p>All other item-level subgroup comparisons were considered exploratory. Responses were summarized as agreement proportions, defined as the percentage selecting “agree” or “strongly agree.” We report proportions with 2-sided 95% CIs using Wilson intervals. For subgroup comparisons, we used Fisher exact tests on dichotomized responses (“agree” or “strongly agree” vs all other responses). Because responses were condensed from a 5-point scale to a binary end point for interpretability and consistency with implementation-focused survey reporting, some resolution was necessarily lost. Therefore, we interpret subgroup analyses as descriptive and hypothesis generating. False discovery rate control for exploratory subgroup comparisons was applied using the Benjamini-Hochberg procedure. Analyses were performed in Python (version 3.13.5; Python Software Foundation) using exact tests and Wilson interval estimation with <italic>SciPy</italic> (version 1.17.0) and <italic>statsmodels</italic> (version 0.14.6).</p>
      </sec>
      <sec>
        <title>Qualitative Analysis</title>
        <p>Optional free-text comments were reviewed qualitatively to identify recurring implementation themes. Comments could map to more than one theme. Representative excerpts were selected to illustrate the most common concerns raised by respondents.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Respondent Characteristics</title>
        <p>A total of 65 radiologists completed the survey, including 23 (35.4%) neuroradiologists and 42 (64.6%) non-neuroradiologists. Full quantitative results across all survey items are provided in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Agreement proportions across survey items (“agree” or “strongly agree”) overall and stratified by neuroradiology training. The prespecified primary end point is item 7 (N=65)<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="70"/>
            <col width="330"/>
            <col width="160"/>
            <col width="140"/>
            <col width="160"/>
            <col width="70"/>
            <col width="70"/>
            <thead>
              <tr valign="top">
                <td>Item number</td>
                <td>Question</td>
                <td>Total, n (%; 95% CI)</td>
                <td>Neuroradiologists (n=23), n (%)</td>
                <td>Non-neuroradiologists (n=42), n (%)</td>
                <td><italic>P</italic> value</td>
                <td><italic>q</italic> value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>The AI<sup>b</sup> tool correctly identifies most cases of intracranial hemorrhage.</td>
                <td>21 (32.3; 22.2-44.4)</td>
                <td>8 (34.8)</td>
                <td>13 (31.0)</td>
                <td>.79</td>
                <td>.92</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>False-positive alerts from the AI are infrequent enough to be acceptable.</td>
                <td>12 (18.5; 10.9-29.6)</td>
                <td>4 (17.4)</td>
                <td>8 (19.0)</td>
                <td>&#62;.99</td>
                <td>&#62;.99</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>The AI rarely misses clinically important hemorrhages.</td>
                <td>28 (43.1; 31.8-55.2)</td>
                <td>10 (43.5)</td>
                <td>18 (42.9)</td>
                <td>&#62;.99</td>
                <td>&#62;.99</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>I trust the AI output when it agrees with my own interpretation.</td>
                <td>33 (50.8; 38.9-62.5)</td>
                <td>11 (47.8)</td>
                <td>22 (52.4)</td>
                <td>.80</td>
                <td>.92</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>I trust the AI output when it conflicts with my initial impression.</td>
                <td>2 (3.1; 0.8-10.5)</td>
                <td>0 (0)</td>
                <td>2 (4.8)</td>
                <td>.54</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Using the AI has reduced my overall interpretation time per head CT<sup>c</sup>.</td>
                <td>7 (10.8; 5.3-20.6)</td>
                <td>1 (4.3)</td>
                <td>6 (14.3)</td>
                <td>.41</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>The extra time spent reviewing AI false-positive studies outweighs the benefits.</td>
                <td>22 (33.8; 23.5-46.0)</td>
                <td>12 (52.2)</td>
                <td>10 (23.8)</td>
                <td>.03</td>
                <td>—<sup>d</sup></td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>If the AI labels a study as negative, I tend to scrutinize it less thoroughly than usual.</td>
                <td>4 (6.2; 2.4-14.8)</td>
                <td>0 (0)</td>
                <td>4 (9.5)</td>
                <td>.29</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>The AI reduces the risk that I will overlook a subtle hemorrhage on a busy shift.</td>
                <td>23 (35.4; 24.9-47.5)</td>
                <td>7 (30.4)</td>
                <td>16 (38.1)</td>
                <td>.60</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>Frequent false positive alerts make me second-guess my decisions.</td>
                <td>20 (30.8; 20.9-42.8)</td>
                <td>4 (17.4)</td>
                <td>16 (38.1)</td>
                <td>.10</td>
                <td>.75</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>Overall, the AI has improved the quality of care our patients receive.</td>
                <td>13 (20; 12.1-31.3)</td>
                <td>4 (17.4)</td>
                <td>9 (21.4)</td>
                <td>.76</td>
                <td>.92</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>I feel legally vulnerable if I override an AI recommendation.</td>
                <td>21 (32.3; 22.2-44.4)</td>
                <td>6 (26.1)</td>
                <td>15 (35.7)</td>
                <td>.58</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>The AI integrates smoothly into our PACS<sup>e</sup>/reporting workflow.</td>
                <td>32 (49.2; 37.5-61.1)</td>
                <td>13 (56.5)</td>
                <td>19 (45.2)</td>
                <td>.44</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>14</td>
                <td>I would recommend continued use of this AI tool in our practice.</td>
                <td>19 (29.2; 19.6-41.2)</td>
                <td>5 (21.7)</td>
                <td>14 (33.3)</td>
                <td>.40</td>
                <td>.90</td>
              </tr>
              <tr valign="top">
                <td>15</td>
                <td>I would like additional feedback or training to use the AI tool optimally.</td>
                <td>13 (20; 12.1-31.3)</td>
                <td>3 (13.0)</td>
                <td>10 (23.8)</td>
                <td>.35</td>
                <td>.90</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Between-group comparisons were conducted using Fisher exact tests. False discovery rate control across exploratory subgroup comparisons was applied using the Benjamini-Hochberg procedure; <italic>q</italic> values are reported for exploratory items.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>AI: artificial intelligence.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>CT: computed tomography.</p>
            </fn>
            <fn id="table1fn4">
              <p><sup>d</sup>Not applicable. Item 7 was the prespecified primary end point; <italic>q</italic> values were not applied to this item.</p>
            </fn>
            <fn id="table1fn5">
              <p><sup>e</sup>PACS: picture archiving and communication system.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Perceived Reliability and False Positive Burden</title>
        <p>Agreement that the AI correctly identified most cases of ICH was 32.3% (21/65; 95% CI 22.2%-44.4%). Agreement that the AI rarely missed clinically important hemorrhages was somewhat higher at 43.1% (28/65; 95% CI 31.8%-55.2%). In contrast, only 18.5% (12/65; 95% CI 10.9%-29.6%) agreed that false-positive alerts were infrequent enough to be acceptable, indicating that perceived false positive burden was a prominent limitation.</p>
        <p>The prespecified primary end point was also consistent with this pattern. Overall, 33.8% (22/65) of respondents (95% CI 23.5%-46.0%) agreed that the extra time spent reviewing examinations with false positive AI alerts outweighed the benefits of the system. These radiologists endorsed the view that false positive workload offset the tool’s net value in routine use. Overall agreement across survey items is shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
      </sec>
      <sec>
        <title>Trust in AI Output and Perceived Workflow Impact</title>
        <p>Responses suggested strongly conditional trust in the AI output. Half (33/65, 50.8%) of respondents (95% CI 38.9%-62.5%) agreed that they trusted the AI when it agreed with their own interpretation. In contrast, only 3.1% (2/65; 95% CI 0.8%-10.5%) agreed that they trusted the AI when it conflicted with their initial impression. This asymmetry suggests that respondents were much more likely to experience the AI as confirmatory than as persuasive in discrepant cases.</p>
        <p>Perceived workflow benefit was limited. Only 10.8% (7/65) of respondents (95% CI 5.3%-20.6%) agreed that AI use reduced their overall interpretation time per head CT. Similarly, 35.4% (23/65; 95% CI 24.9%-47.5%) agreed that the AI reduced the risk that they would overlook a subtle hemorrhage on a busy shift, indicating that perceived detection support was present for some respondents but did not translate into broad perception of time savings.</p>
      </sec>
      <sec>
        <title>Self-Reported Behaviors, Quality Perceptions, and Medicolegal Concerns</title>
        <p>Self-reported reduced scrutiny after a negative AI result was uncommon. Only 6.2% (4/65) of the respondents (95% CI 2.4%-14.8%) agreed with the statement that, if the AI labeled a result as negative, they tended to scrutinize it less thoroughly than usual. Because this was a self-reported perception and not a direct behavioral measurement, we interpreted it narrowly as a descriptive response to the survey item.</p>
        <p>Frequent false-positive alerts were also associated with self-reported second-guessing. A total of 30.8% (20/65) of the respondents (95% CI 20.9%-42.8%) agreed that frequent false-positive alerts made them second-guess their decisions. Only 20% (13/65; 95% CI 12.1%-31.3%) agreed that the AI improved the quality of care that patients received. Agreement that the AI integrated smoothly into the picture archiving and communication system or reporting workflow was 49.2% (32/65; 95% CI 37.5%-61.1%), suggesting mixed perceptions of integration. Recommendation for continued use of the tool was endorsed by 29.2% (19/65; 95% CI 19.6%-41.2%). Concern about legal vulnerability when overriding AI output was reported by 32.3% (21/65; 95% CI 22.2%-44.4%). Additional feedback or training to use the tool optimally was desired by 20% (13/65; 95% CI 12.1%-31.3%).</p>
      </sec>
      <sec>
        <title>Subgroup Findings by Neuroradiology Training</title>
        <p>Neuroradiologists more frequently endorsed the primary end point than non-neuroradiologists (12/23, 52.2% vs 10/42, 23.8%; unadjusted <italic>P</italic>=.03). For exploratory items, patterns were broadly similar between groups. Agreement with trusting the AI when it agreed with the reader’s interpretation was 47.8% (11/23) among neuroradiologists and 52.4% (22/42) among non-neuroradiologists. Trust in conflicting AI output remained rare in both groups (0% vs 2/42, 4.8%). Self-reported reduced scrutiny after an AI-negative result was reported by 0% of neuroradiologists and 9.5% (4/42) of non-neuroradiologists. Recommendation for continued use was reported by 21.7% (5/23) of neuroradiologists and 33.3% (14/42) of non-neuroradiologists. After false discovery rate correction, no exploratory subgroup differences remained statistically significant. Descriptive subgroup comparisons for selected survey items are shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Descriptive comparison of agreement by subspecialty training for selected survey items. Bars show the percentage of respondents selecting “agree” or “strongly agree” among neuroradiologists and non-neuroradiologists for selected items related to false positive (FP) burden, trust in artificial intelligence (AI) output, recommendation for continued use, and reported less thorough than usual scrutiny of AI-negative results. These subgroup comparisons are descriptive; no exploratory subgroup differences remained statistically significant after false discovery rate correction.</p>
          </caption>
          <graphic xlink:href="humanfactors_v13i1e92145_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Qualitative Themes From Free-Text Comments</title>
        <p>Free-text responses reinforced the quantitative findings and highlighted recurring implementation concerns.</p>
        <sec>
          <title>Theme 1: Artifact- and Calcification-Driven False Positives Dominated the User Experience</title>
          <p>Many respondents attributed false-positive alerts to parafalcine calcification, skull-adjacent artifacts, motion, or streak artifacts and described these alerts as disruptive or time-consuming.</p>
        </sec>
        <sec>
          <title>Theme 2: Perceived Utility Was Limited Unless the Tool Meaningfully Changed Triage</title>
          <p>Several respondents indicated that the system primarily identified obvious hemorrhages and offered limited incremental value for experienced readers, although some suggested that workflow-level prioritization or routing features might improve perceived utility.</p>
        </sec>
        <sec>
          <title>Theme 3: Latency and Inconsistent Availability Reduced Usefulness</title>
          <p>Multiple respondents noted that AI output was not always available at the time of dictation or arrived too late to be helpful.</p>
        </sec>
        <sec>
          <title>Theme 4: False-Positive Alerts Increased Second-Guessing and Consultation Burden</title>
          <p>Some comments suggested that false-positive AI flags triggered unnecessary consultation or additional cognitive burden.</p>
        </sec>
        <sec>
          <title>Theme 5: Medicolegal Concerns Influenced Acceptance</title>
          <p>Respondents expressed discomfort with the possibility that delayed or discrepant AI outputs could create liability concerns.</p>
        </sec>
        <sec>
          <title>Theme 6: Respondents Wanted Better Localization, Higher Specificity, and More Training</title>
          <p>Suggested improvements included more precise localization, lower false positive rates, better timing, and implementation feedback or training.</p>
        </sec>
        <sec>
          <title>Aggregated Themes</title>
          <p>Aggregated qualitative themes and representative excerpts are summarized in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Qualitative themes from free-text responses. Comments could map to more than one theme; counts reflect the number of comments mentioning each theme at least once (N=65)<sup>a</sup>.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="200"/>
              <col width="420"/>
              <col width="110"/>
              <col width="270"/>
              <thead>
                <tr valign="top">
                  <td>Theme</td>
                  <td>Description</td>
                  <td>Count, n (%)</td>
                  <td>Representative excerpt</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>False positives or low specificity</td>
                  <td>Frequent false-positive alerts, commonly attributed to artifacts or calcification; perceived as disruptive and time-consuming</td>
                  <td>22 (33.8)</td>
                  <td>“False positives are too frequent...”</td>
                </tr>
                <tr valign="top">
                  <td>Limited utility, discontinue, or low value</td>
                  <td>Negative overall sentiment, including requests to discontinue the tool or concerns that its value did not justify its burden</td>
                  <td>13 (20)</td>
                  <td>“Please remove AI completely.”</td>
                </tr>
                <tr valign="top">
                  <td>Latency or availability</td>
                  <td>AI<sup>b</sup> output was sometimes delayed or unavailable at the time of dictation or interpretation</td>
                  <td>7 (10.8)</td>
                  <td>“Sometimes AI image made available very late...”</td>
                </tr>
                <tr valign="top">
                  <td>Medicolegal concerns</td>
                  <td>Concerns about legal vulnerability, accountability, or liability if the AI output appeared after sign-off or conflicted with their interpretation</td>
                  <td>5 (7.7)</td>
                  <td>“It could potentially ‘frame’ me.”</td>
                </tr>
                <tr valign="top">
                  <td>False negatives or missed hemorrhages</td>
                  <td>Concern that the tool could miss subtle hemorrhages, particularly smaller or less conspicuous bleeds</td>
                  <td>4 (6.2)</td>
                  <td>“I have seen several false negatives.”</td>
                </tr>
                <tr valign="top">
                  <td>Positive or supportive comments</td>
                  <td>Explicitly positive feedback or support for continued use despite limitations</td>
                  <td>4 (6.2)</td>
                  <td>“The AI ICH tool is great!”</td>
                </tr>
                <tr valign="top">
                  <td>Triage, prioritization, or assignment routing</td>
                  <td>Suggestions that the tool might be more useful if integrated into prioritization or routing workflows</td>
                  <td>3 (4.6)</td>
                  <td>“Positive studies should be assigned...and prioritized.”</td>
                </tr>
                <tr valign="top">
                  <td>Consultation burden or second-guessing</td>
                  <td>Reports that false-positive AI alerts increased consultation burden or second-guessing</td>
                  <td>3 (4.6)</td>
                  <td>“I frequently get consults.”</td>
                </tr>
                <tr valign="top">
                  <td>Training or feedback requests</td>
                  <td>Requests for additional training, implementation guidance, or feedback on use</td>
                  <td>2 (3.1)</td>
                  <td>“I would like additional training.”</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>Aggregated qualitative findings from optional free-text comments are summarized. Because individual comments could mention more than one concern, counts are not mutually exclusive and reflect the number of comments mentioning each theme at least once.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>AI: artificial intelligence.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In this survey of radiologists exposed to an FDA-cleared ICH AI detection tool in a national teleradiology environment, 3 findings stood out. First, false positive burden was a central driver of dissatisfaction: fewer than 1 in 5 respondents found false-positive alerts infrequent enough to be acceptable, and one-third (22/65, 33.8%) agreed that time spent reviewing false-positive alerts outweighed the tool’s benefits. Second, perceived workflow benefit was limited: only approximately 1 in 10 respondents reported reduced interpretation time despite a larger minority reporting that the tool might reduce the risk of missing subtle hemorrhages during busy shifts. Third, trust in the AI output was strongly conditional. Respondents were willing to trust the AI much more often when it agreed with their own interpretation than when it conflicted with it.</p>
        <p>Taken together, these findings suggest that the practical value of this implementation was constrained less by the abstract idea of AI assistance than by the combined effects of false positive burden, timing, and workflow integration. In other words, the tool appears to have been experienced more as an additional signal to manage than as a consistently efficiency-enhancing aid.</p>
      </sec>
      <sec>
        <title>Relationship to Prior Work</title>
        <p>These results are consistent with a growing literature showing that post-deployment experience with clinical AI may differ substantially from laboratory or regulatory performance summaries [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. In radiology and other clinical settings, user acceptance is shaped not only by sensitivity and specificity but also by local disease prevalence, the timing of alerts, the interpretability of outputs, and how often the system changes action in a useful direction [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. Scaringi et al [<xref ref-type="bibr" rid="ref6">6</xref>] described how real-world deployment can produce an “accuracy paradox” in which acceptable technical performance is experienced as poor because positive alerts carry a high false discovery burden in a low-prevalence setting. That framework is highly relevant in this study, where many respondents perceived the false positive rate as a major practical barrier.</p>
        <p>These findings also align with human factors literature on alarm burden and trust in automation. High alert burden and repeated false-positive alerts can result in cognitive overhead, desensitization, and reduced perceived usefulness of decision support systems [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Meanwhile, trust in automation is often selective rather than global; clinicians may accept AI as supportive when it confirms a preexisting judgment but remain reluctant to defer to it when it conflicts with their own assessment [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Our survey findings fit that pattern closely. However, importantly, because we measured perceptions rather than observed task performance, our data support cautious description of conditional trust patterns, not stronger causal inferences about AI-driven decision change.</p>
      </sec>
      <sec>
        <title>Interpreting the Self-Reported Behavior Item Cautiously</title>
        <p>A survey item about scrutinizing AI-negative results less thoroughly does not establish a behavioral phenomenon in the same way that a controlled multi-reader study could. Accordingly, we interpret this result narrowly. The 6.2% (4/65) agreement rate should be read only as the proportion of respondents who self-reported less thorough scrutiny after a negative AI result on that item. It should not be construed as direct evidence of automation-induced complacency or measurable diagnostic underreading. This distinction is important, particularly because self-report on professionally sensitive behaviors may be influenced by social desirability bias [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>At the same time, the item remains informative as a perception signal. Even a small minority of respondents endorsing reduced scrutiny suggests that how negative AI outputs are presented, timed, and contextualized may matter. Future work using controlled reader studies, audit-based designs, or prospective workflow observation would be better suited to determining whether and when AI output measurably alters vigilance or diagnostic behavior.</p>
      </sec>
      <sec>
        <title>Why False Positive Burden Matters So Much in Teleradiology</title>
        <p>The teleradiology environment may amplify the operational importance of false positives. High case volume, rapid turnaround expectations, and distributed communication structures can magnify the cost of reviewing spurious alerts or revisiting already completed interpretations. In such settings, an alert that does not change management may still consume attention, create uncertainty, or generate downstream consultation. The free-text comments in this study point to precisely these burdens: artifact-driven overcalls, delayed output, second-guessing, and extra communication work.</p>
        <p>This observation has practical implications for how radiology AI tools should be tuned and evaluated. In some settings, maximizing sensitivity may be appropriate, particularly when AI outputs are used to support prioritization or highlight potentially urgent findings; however, if the resulting false positive burden is too high, this may erode clinician acceptance even when the tool performs as intended at a regulatory or technical level [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. Therefore, a workflow-sensitive implementation strategy may matter as much as the operating characteristics of the algorithm itself.</p>
      </sec>
      <sec>
        <title>Implications for Implementation</title>
        <p>Several implementation lessons emerge from these data. First, specificity matters. The comments suggest that calcification, streak artifacts, motion, and skull-adjacent findings were recurrent sources of false-positive alerts. Improving discrimination in these common failure modes could meaningfully improve user acceptance. Second, interpretability matters. If discrepant alerts are to influence radiologist behavior in a useful way, users may need clearer localization, confidence communication, or other forms of contextual explanation rather than a generic positive signal [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Third, timing matters. Decision support that appears after a case has effectively been interpreted is less likely to help and more likely to create noise or ambiguity. Fourth, workflow design matters. Some respondents suggested that the tool’s value might be enhanced by workflow-level prioritization or routing features in addition to its use as an overlay during interpretation.</p>
      </sec>
      <sec>
        <title>Subgroup Findings and Their Interpretation</title>
        <p>Neuroradiologists were more likely than non-neuroradiologists to endorse the primary end point that false positive review time outweighed benefits, but this finding should be interpreted cautiously. It was the only subgroup result meeting nominal significance, and no exploratory subgroup differences remained significant after false discovery rate correction. Therefore, the most appropriate interpretation is descriptive and hypothesis generating rather than confirmatory. It is possible that subspecialty training influences tolerance for false positives, perceived incremental value, or expectations of tool performance, but this survey was not designed to establish those mechanisms.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>A strength of this study is that it captured the views of radiologists exposed to the tool in routine clinical practice rather than in an artificial test setting. The inclusion of both structured survey items and free-text comments helped contextualize quantitative responses and identify concrete implementation barriers.</p>
        <p>This study also has several limitations. First, the findings are based on self-reported perceptions rather than objective measures of diagnostic performance, reading time, or patient outcomes. Second, the survey instrument was not formally validated, so items should be interpreted at face value rather than as established scales of latent constructs. Third, dichotomizing Likert responses improved interpretability but reduced response granularity. Fourth, the sample reflects a single organizational implementation and may not generalize to other workflows, prevalence environments, or AI products. Fifth, responses may be affected by selection bias and social desirability bias, particularly for items concerning vigilance or reliance. Finally, subgroup analyses were exploratory, and the study was not powered to make strong claims about differences by neuroradiology training.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Radiologists using an FDA-cleared ICH AI detection tool in a national teleradiology environment reported substantial false positive burden, limited perceived time savings, and strongly conditional trust in AI output. Self-reported reduced scrutiny after negative AI results was uncommon but endorsed by a minority of respondents. The findings suggest that the real-world value of radiology AI tools depends not only on whether they detect disease but also on whether they do so with sufficient specificity, appropriate timing, and workflow-compatible presentation to earn sustained clinician acceptance.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-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">CT</term>
          <def>
            <p>computed tomography</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DECIDE-AI</term>
          <def>
            <p>Developmental and Exploratory Clinical Investigations of Decision Support Systems Driven by Artificial Intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FDA</term>
          <def>
            <p>Food and Drug Administration</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">ICH</term>
          <def>
            <p>intracranial hemorrhage</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <notes>
      <title>Data Availability</title>
      <p>All data generated or analyzed during this study are included in this published article.</p>
    </notes>
    <notes>
      <title>Funding</title>
      <p>No funding was received for this work.</p>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>Conceptualization: AJDG (lead), JKDG (supporting)</p>
        <p>Data curation: JKDG (lead), AJDG (supporting)</p>
        <p>Formal analysis: TAS (lead), AJDG (supporting)</p>
        <p>Funding acquisition: None</p>
        <p>Investigation: JKDG (lead), AJDG (supporting)</p>
        <p>Methodology: AJDG (lead), JKDG (supporting)</p>
        <p>Project administration: AJDG (lead)</p>
        <p>Resources: AJDG</p>
        <p>Supervision: AJDG</p>
        <p>Validation: AJDG</p>
        <p>Visualization: AJDG</p>
        <p>Writing—original draft: AJDG (lead), JKDG (supporting)</p>
        <p>Writing—review and editing: AJDG (lead), JKDG (supporting), TAS (supporting)</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Del Gaizo</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Osborne</surname>
              <given-names>TF</given-names>
            </name>
            <name name-style="western">
              <surname>Shahoumian</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Sherrier</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Deep learning to detect intracranial hemorrhage in a national teleradiology program and the impact on interpretation time</article-title>
          <source>Radiol Artif Intell</source>
          <year>2024</year>
          <month>09</month>
          <volume>6</volume>
          <issue>5</issue>
          <fpage>e240067</fpage>
          <pub-id pub-id-type="doi">10.1148/ryai.240067</pub-id>
          <pub-id pub-id-type="medline">39017032</pub-id>
          <pub-id pub-id-type="pmcid">PMC11427938</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>Pettet</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Khetani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Golla</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lavis</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A retrospective audit of an artificial intelligence software for the detection of intracranial haemorrhage used by a teleradiology company in the United Kingdom</article-title>
          <source>BJR Open</source>
          <year>2024</year>
          <month>10</month>
          <day>04</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>tzae033</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/bjro/article-lookup/doi/10.1093/bjro/tzae033"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/bjro/tzae033</pub-id>
          <pub-id pub-id-type="medline">39479271</pub-id>
          <pub-id pub-id-type="pii">tzae033</pub-id>
          <pub-id pub-id-type="pmcid">PMC11522876</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>Rohren</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmadzade</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Colella</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kottler</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Poff</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rastogi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wiggins</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Yee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zuluaga</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ramis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ghasemi-Rad</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Post-deployment monitoring of AI performance in intracranial hemorrhage detection by ChatGPT</article-title>
          <source>Acad Radiol</source>
          <year>2025</year>
          <month>10</month>
          <volume>32</volume>
          <issue>10</issue>
          <fpage>6104</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1076-6332(25)00725-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.acra.2025.07.055</pub-id>
          <pub-id pub-id-type="medline">40796469</pub-id>
          <pub-id pub-id-type="pii">S1076-6332(25)00725-1</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>Garcia</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dawood</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Elshikh</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Head-to-head comparison of 2 artificial intelligence computer-aided triage solutions for detecting intracranial hemorrhage on noncontrast head CT</article-title>
          <source>AJNR Am J Neuroradiol</source>
          <year>2026</year>
          <month>02</month>
          <day>03</day>
          <volume>47</volume>
          <issue>2</issue>
          <fpage>376</fpage>
          <lpage>85</lpage>
          <pub-id pub-id-type="doi">10.3174/ajnr.A8986</pub-id>
          <pub-id pub-id-type="medline">40957692</pub-id>
          <pub-id pub-id-type="pii">ajnr.A8986</pub-id>
          <pub-id pub-id-type="pmcid">PMC12981982</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>Vasey</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nagendran</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Clifton</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Denaxas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Denniston</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Faes</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Geerts</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahim</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Mateen</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Mathur</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McCradden</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ordish</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Saria</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Watkinson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wheatstone</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McCulloch</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Reporting guideline for the early stage clinical evaluation of decision support systems driven by artificial intelligence: DECIDE-AI</article-title>
          <source>BMJ</source>
          <year>2022</year>
          <month>05</month>
          <day>18</day>
          <volume>377</volume>
          <fpage>e070904</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=35584845"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2022-070904</pub-id>
          <pub-id pub-id-type="medline">35584845</pub-id>
          <pub-id pub-id-type="pmcid">PMC9116198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scaringi</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>McTaggart</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Alvin</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Atalay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bernstein</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>MV</given-names>
            </name>
            <name name-style="western">
              <surname>Jindal</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Movson</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Swenson</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Baird</surname>
              <given-names>GL</given-names>
            </name>
          </person-group>
          <article-title>Implementing an AI algorithm in the clinical setting: a case study for the accuracy paradox</article-title>
          <source>Eur Radiol</source>
          <year>2025</year>
          <month>07</month>
          <volume>35</volume>
          <issue>7</issue>
          <fpage>4347</fpage>
          <lpage>53</lpage>
          <pub-id pub-id-type="doi">10.1007/s00330-024-11332-z</pub-id>
          <pub-id pub-id-type="medline">39741216</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00330-024-11332-z</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sendelbach</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Funk</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Alarm fatigue: a patient safety concern</article-title>
          <source>AACN Adv Crit Care</source>
          <year>2013</year>
          <month>10</month>
          <day>01</day>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>378</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1097/nci.0b013e3182a903f9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ancker</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nosal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hauser</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mauer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kaushal</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Effects of workload, work complexity, and repeated alerts on alert fatigue in a clinical decision support system</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2017</year>
          <month>04</month>
          <day>10</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>36</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-017-0430-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-017-0430-8</pub-id>
          <pub-id pub-id-type="medline">28395667</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-017-0430-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC5387195</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bernstein</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Atalay</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Dibble</surname>
              <given-names>EH</given-names>
            </name>
            <name name-style="western">
              <surname>Maxwell</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Karam</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ward</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Healey</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Baird</surname>
              <given-names>GL</given-names>
            </name>
          </person-group>
          <article-title>Can incorrect artificial intelligence (AI) results impact radiologists, and if so, what can we do about it? A multi-reader pilot study of lung cancer detection with chest radiography</article-title>
          <source>Eur Radiol</source>
          <year>2023</year>
          <month>11</month>
          <volume>33</volume>
          <issue>11</issue>
          <fpage>8263</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37266657"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s00330-023-09747-1</pub-id>
          <pub-id pub-id-type="medline">37266657</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00330-023-09747-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC10235827</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parasuraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Humans and automation: use, misuse, disuse, abuse</article-title>
          <source>Hum Factors</source>
          <year>1997</year>
          <month>06</month>
          <volume>39</volume>
          <issue>2</issue>
          <fpage>230</fpage>
          <lpage>53</lpage>
          <pub-id pub-id-type="doi">10.1518/001872097778543886</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dzindolet</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Peterson</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Pomranky</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Pierce</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Beck</surname>
              <given-names>HP</given-names>
            </name>
          </person-group>
          <article-title>The role of trust in automation reliance</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>2003</year>
          <month>6</month>
          <volume>58</volume>
          <issue>6</issue>
          <fpage>697</fpage>
          <lpage>718</lpage>
          <pub-id pub-id-type="doi">10.1016/S1071-5819(03)00038-7</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
