<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD with MathML3 v1.3 20210610//EN" "JATS-archivearticle1-3-mathml3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"
  dtd-version="1.3" xml:lang="en" article-type="research-article">
  <?DTDIdentifier.IdentifierValue -//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN?>
  <?DTDIdentifier.IdentifierType public?>
  <?SourceDTD.DTDName JATS-journalpublishing1.dtd?>
  <?SourceDTD.Version 1.2?>
  <?ConverterInfo.XSLTName jats2jats3.xsl?>
  <?ConverterInfo.Version 1?>
  <?properties open_access?>
  <front>
    <journal-meta>
      <journal-id journal-id-type="iso-abbrev">Arch Pharm Pract</journal-id>
      <journal-id journal-id-type="publisher-id">archivepp.com</journal-id>
      <journal-id journal-id-type="publisher-id">Arch Pharm Pract</journal-id>
      <journal-title-group>
        <journal-title>Archives of Pharmacy Practice</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2320-5210</issn>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">archivepp.com-1293</article-id>
      <article-id pub-id-type="doi">10.51847/yymC77qBBs</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original research</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>What Happens to the Safety Case When Artificial Intelligence Enters Pharmacovigilance? An Umbrella Review from Intake to Signal Action</article-title>
      </title-group>
                    <contrib-group>
                      <contrib contrib-type="author">
              <name>
                <surname>Thompson</surname>
                <given-names>David</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                                            <xref rid="cor1" ref-type="corresp" />
                          </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Mitchell</surname>
                <given-names>Sarah</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Adams</surname>
                <given-names>Rachel</given-names>
              </name>
                              <xref rid="aff2" ref-type="aff">2</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Brown</surname>
                <given-names>James</given-names>
              </name>
                              <xref rid="aff3" ref-type="aff">3</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Lee</surname>
                <given-names>Michael</given-names>
              </name>
                              <xref rid="aff4" ref-type="aff">4</xref>
                                        </contrib>
                  </contrib-group>
                  <aff id="aff1">
            <label>1</label>Department of AI and Pharmacovigilance Safety, Faculty of Pharmacy, University of Toronto, Toronto, Canada.
          </aff>
                  <aff id="aff2">
            <label>2</label>Department of Drug Safety Signal Processing, Faculty of Pharmaceutical Sciences, University of British Columbia, Vancouver, Canada.
          </aff>
                  <aff id="aff3">
            <label>3</label>Department of AI Signal Action and Clinical Response, Faculty of Pharmacy, McGill University, Montreal, Canada.
          </aff>
                  <aff id="aff4">
            <label>4</label>Department of Safety Case Evaluation and AI, Faculty of Pharmacy, University of Guelph, Guelph, Canada.
          </aff>
                          <author-notes>
            <corresp id="cor1">
              <bold>Address for correspondence:</bold> Prof. Wael Abu Dayyih, Department of
              Pharmaceutical Chemistry, Faculty of Pharmacy, Mutah University, Al-Karak 61710, Jordan.
                              E-mail: <email xlink:href="david.thompson@utoronto.ca">david.thompson@utoronto.ca</email>
                          </corresp>
          </author-notes>
                    <pub-date pub-type="epub">
        <day>16</day>
        <month>08</month>
        <year>2026</year>
      </pub-date>
      <volume>17</volume>
      <issue>3</issue>
      <fpage>46</fpage>
      <lpage>55</lpage>
      <permissions>
        <copyright-statement>
          Copyright: &#x000a9; 2026 Archives of Pharmacy Practice
        </copyright-statement>
        <copyright-year>2026</copyright-year>
        <license>
          <ali:license_ref xmlns:ali="http://www.niso.org/schemas/ali/1.0/"
            specific-use="textmining" content-type="ccbyncsalicense">
            https://creativecommons.org/licenses/by-nc-sa/4.0/</ali:license_ref>
          <license-p>This is an open access journal, and articles are distributed under the terms of
            the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License, which allows
            others to remix, tweak, and build upon the work non-commercially, as long as appropriate
            credit is given and the new creations are licensed under the identical terms.</license-p>
        </license>
      </permissions>
      <abstract>
        <title>A<sc>BSTRACT</sc></title>
        <p>Artificial intelligence is entering pharmacovigilance through case intake, information extraction, coding support, duplicate detection, case linkage, signal detection, prioritization, and communication. These applications may improve processing capacity, yet the safety case depends on more than technical accuracy. To synthesize review-level evidence on how artificial intelligence affects pharmacovigilance from intake to signal action and to identify where evidence supports, qualifies, or leaves unresolved claims of safety benefit. An umbrella review of eligible systematic and scoping reviews published from 2017 through 2026 was conducted using a pathway-based framework. Reviews were eligible when they reported transparent search methods, explicit criteria, identifiable included studies, and findings mappable to at least one pharmacovigilance stage. Data were extracted at review level. Methodological quality, relevance, validation maturity, implementation status, discordance, and primary-study overlap were assessed using design-appropriate tools. Findings were synthesized without pooling incomparable outcomes. Evidence was concentrated in retrospective detection, prediction, text extraction, and data-processing tasks. Reviews repeatedly described heterogeneous data sources, labels, reference standards, metrics, and validation practices. External validation, prospective workflow evaluation, calibration, comparative effectiveness, and downstream assessment of communication or regulatory action were uncommon. Duplicate reporting, noisy intake sources, representativeness, automation bias, and repeated use of the same primary studies could weaken apparent confidence. Artificial intelligence may strengthen selected pharmacovigilance operations, but review-level evidence does not establish an end-to-end, deployment-ready safety case. Confidence depends on traceable data, independent validation, workflow evaluation, overlap-aware synthesis, human accountability, and explicit separation of technical performance from medication-safety benefit in routine practice.</p>
      </abstract>
      <kwd-group>
                <kwd>Umbrella review</kwd>
                <kwd>Digital pharmacy</kwd>
                <kwd>Artificial intelligence</kwd>
                <kwd>Pharmacy practice</kwd>
                <kwd>Medication safety</kwd>
                <kwd>Evidence synthesis</kwd>
              </kwd-group>
    </article-meta>
  </front>
</article>