<?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 article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">ResProt</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Res Protoc</journal-id>
      <journal-title>JMIR Research Protocols</journal-title>
      <issn pub-type="epub">1929-0748</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">v15i1e101691</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/101691</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Protocol</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Protocol</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>AI for Causality Assessment in Pharmacovigilance: Protocol for a Scoping Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Schwartz</surname>
            <given-names>Amy</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hammad</surname>
            <given-names>Tarek</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Khan</surname>
            <given-names>Sohil</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Ohta</surname>
            <given-names>Miki</given-names>
          </name>
          <degrees>MD, MPH, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Clinical Research Promotion Center</institution>
            <institution>The University of Tokyo Hospital</institution>
            <addr-line>7-3-1 Hongo, Bunkyo-ku</addr-line>
            <addr-line>Tokyo, 113-8655</addr-line>
            <country>Japan</country>
            <phone>81 0338155411</phone>
            <email>mjohta@g.ecc.u-tokyo.ac.jp</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4896-8868</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Ota</surname>
            <given-names>Miki</given-names>
          </name>
          <degrees>PharmD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-9578-2830</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Ohta</surname>
            <given-names>Mikihiko</given-names>
          </name>
          <degrees>JD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0003-4318-951X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Clinical Research Promotion Center</institution>
        <institution>The University of Tokyo Hospital</institution>
        <addr-line>Tokyo</addr-line>
        <country>Japan</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Office of Informatic and Management for Safety</institution>
        <institution>Pharmaceuticals and Medical Devices Agency</institution>
        <addr-line>Tokyo</addr-line>
        <country>Japan</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Fuji Partnership Law Firm</institution>
        <addr-line>Tokyo</addr-line>
        <country>Japan</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Miki Ohta <email>mjohta@g.ecc.u-tokyo.ac.jp</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>16</day>
        <month>7</month>
        <year>2026</year>
      </pub-date>
      <volume>15</volume>
      <elocation-id>e101691</elocation-id>
      <history>
        <date date-type="received">
          <day>18</day>
          <month>5</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>9</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>26</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>30</day>
          <month>6</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Miki Ohta, Miki Ota, Mikihiko Ohta. Originally published in JMIR Research Protocols (https://www.researchprotocols.org), 16.07.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 Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on https://www.researchprotocols.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.researchprotocols.org/2026/1/e101691" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Pharmacovigilance aims to protect patient safety by identifying and managing adverse events associated with pharmaceuticals. Determining the causality of these adverse events is central at both the individual case and population levels; however, it is increasingly challenging as the volume and complexity of safety data grow. Although AI and related technologies have been proposed to support causality assessment, limited research has examined how these methods are used, their information and quality requirements, or how associated risks are addressed.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This scoping review aims to determine the available evidence on AI-based methods for causality assessment in pharmacovigilance. The primary objective is to characterize how these methods are applied or proposed with a focus on their functional roles, reported data inputs and information needs, and associated risks. Secondary objectives include comparing applications at the individual case and population levels; describing the types of AI-based techniques and automation tools used in causality assessment workflows; and summarizing reported data quality considerations and governance mechanisms, including risk management approaches.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Sources describing or proposing AI-based approaches, including data-driven models (machine learning, natural language processing, knowledge graphs, and causal inference) and knowledge- or rule-based systems implementing causal assessment logic, will be eligible. Searches will be conducted in PubMed, Web of Science Core Collection, ProQuest, EBSCOhost, and Ichushi Web and will be restricted to English- and Japanese-language sources. Two reviewers will independently screen records and full-text articles, with disagreements resolved by a third reviewer. Data will be charted on use cases, information inputs, data quality dimensions, model characteristics, governance mechanisms, and identified risks. Synthesis will follow a reflexive thematic analysis approach and be reported in accordance with PRISMA-ScR (Preferred Reporting Items for Systematic reviews and Meta-Analyses extension for Scoping Reviews) guidelines informed by applicable PRISMA-S (Preferred Reporting Items for Systematic reviews and Meta-Analyses literature search extension) elements.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>This protocol was registered in the Open Science Framework platform on December 23, 2025. The registration was subsequently updated on May 19, 2026, to reflect an extension to the data collection period. A preliminary database search was conducted in December 2025, retrieving a total of 760 records, of which the preliminary title and abstract screening identified 196 (25.8%) articles for full-text review. Database searches are scheduled for July 2026. Data charting is scheduled for August 2026, and synthesis is scheduled for September 2026. Findings are expected to be submitted for publication by the end of December 2026.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This review is expected to provide a structured map of AI-based applications for causality assessment in pharmacovigilance, clarify reported information inputs and data quality dimensions, and synthesize risk management and governance approaches. The findings are expected to inform methodological development, practical implementation, and the governance of AI-supported causality assessment.</p>
        </sec>
        <sec sec-type="trial registration">
          <title>Trial Registration</title>
          <p>Open Science Framework 10.17605/OSF.IO/QVF5C; https://osf.io/qvf5c/overview</p>
        </sec>
        <sec sec-type="registered-report">
          <title>International Registered Report Identifier (IRRID)</title>
          <p>DERR1-10.2196/101691</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
        <kwd>pharmacovigilance</kwd>
        <kwd>causality assessment</kwd>
        <kwd>machine learning</kwd>
        <kwd>scoping review</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Pharmacovigilance aims to protect patient safety by detecting, assessing, understanding, and preventing adverse events associated with medicinal products [<xref ref-type="bibr" rid="ref1">1</xref>]. A central activity in pharmacovigilance is the assessment of causal relationships between a drug and an adverse event at both the individual-case and population levels [<xref ref-type="bibr" rid="ref2">2</xref>]. At the individual-case level, causality assessment is conducted in clinical settings, by regulatory authorities, and by the pharmacovigilance departments of pharmaceutical companies, most often through clinical judgment alone or in combination with standardized tools (eg, the World Health Organization Uppsala Monitoring Centre scale [<xref ref-type="bibr" rid="ref3">3</xref>] and the Naranjo algorithm [<xref ref-type="bibr" rid="ref4">4</xref>]). At the population level, statistical and epidemiological methods such as disproportionality analyses and observational studies support signal detection and benefit-risk assessment [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>The rapid expansion in both the volume and complexity of safety data, driven by electronic reporting, large numbers of spontaneous reports, and diverse real-world data sources, has made timely and consistent causality assessment increasingly difficult to achieve through manual review alone. Accordingly, interest has grown in the use of advanced IT, particularly AI, sometimes in combination with automation tools such as robotic process automation to support and potentially transform causality assessment in pharmacovigilance.</p>
      <p>Recent developments in AI, including machine learning, natural language processing, knowledge graphs, and causal inference methods, have been explored for various pharmacovigilance tasks such as automated coding [<xref ref-type="bibr" rid="ref6">6</xref>], duplicate detection [<xref ref-type="bibr" rid="ref7">7</xref>], case triage, signal detection and prioritization [<xref ref-type="bibr" rid="ref8">8</xref>], and literature screening [<xref ref-type="bibr" rid="ref9">9</xref>]. Concurrently, robotic process automation has been introduced to automate repetitive tasks such as case intake, data transfer, and report generation [<xref ref-type="bibr" rid="ref10">10</xref>]. Although many of these applications primarily aim to improve efficiency and consistency, AI-based models are increasingly being developed to contribute directly to causality assessment—for example, by predicting causality categories for individual cases [<xref ref-type="bibr" rid="ref11">11</xref>] or identifying patterns indicative of causal associations in large databases [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
      <p>The application of AI-based methods to causality assessment raises several methodological, operational, and governance issues [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. These systems must integrate structured and unstructured data at the individual case level and heterogeneous real-world data at the population level, often supplemented by external knowledge databases [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. In addition, pharmacovigilance databases are affected by missing data, underreporting, misclassification, and reporting bias, all of which may influence AI performance [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. Consequently, data quality metrics and performance indicators beyond standard measures of accuracy must be considered to ensure that outputs align with clinically and regulatorily meaningful outcomes. Explainability and human-in-the-loop designs also remain essential as ultimate decisions regarding causality and safety actions continue to rest with experts [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>]. Furthermore, AI-based systems and associated automation introduce risks such as algorithmic bias, model drift, overfitting, automation bias, and privacy and security concerns, which may manifest differently at the individual case and population levels and require tailored governance approaches [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      <p>In response to these emerging applications and challenges, international and national organizations, including the Council for International Organizations of Medical Sciences, the European Medicines Agency, and the US Food and Drug Administration, have begun to articulate principles for the use of AI across the medicinal product life cycle [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. These initiatives emphasize data quality, model validation, explainability, human oversight, and governance throughout the AI life cycle.</p>
      <p>Despite these advancements, several knowledge gaps remain. First, existing guidance documents are largely high level and cross-cutting and rarely specify, in a concrete or systematic manner, the types of information required, the data quality thresholds that should be met, or the risk management approaches needed in this context. Second, although the literature on AI in pharmacovigilance is expanding, most reviews provide broad overviews of applications and do not focus specifically on causality assessment, nor do they systematically distinguish between individual case– and population-level applications. Third, there is limited synthesis regarding which AI techniques and related automation tools are used at specific stages of causality assessment, the information and data quality assumptions on which they rely, and how associated risks are identified and addressed. Finally, the interplay and potential complementarity between AI-supported processes at the individual case and population levels remain insufficiently described.</p>
      <p>Given this combination of emerging applications and persistent knowledge gaps, a scoping review is an appropriate approach for mapping the existing evidence, clarifying key concepts, and identifying areas requiring further research. Rather than quantifying the effect of a specific intervention, this review will provide an overview of how AI-based methods and, where applicable, AI-enabled automation are currently used, proposed, or discussed for causality assessment in pharmacovigilance. It will also summarize reported information inputs, data quality considerations, and associated risks. A preliminary search of MEDLINE (via PubMed), the Cochrane Database of Systematic Reviews, and <italic>JBI Evidence Synthesis</italic> identified no current or ongoing systematic or scoping reviews on this topic.</p>
      <p>The main objectives of this study are described in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>.</p>
      <boxed-text id="box1" position="float">
        <title>Objectives of this scoping review.</title>
        <p>
          <bold>Primary objective</bold>
        </p>
        <list list-type="bullet">
          <list-item>
            <p>Characterize how AI-based methods are applied or proposed for causality assessment between medicinal products and adverse events in pharmacovigilance, with a focus on their functional roles, reported data inputs, information needs, and associated risks</p>
          </list-item>
        </list>
        <p>
          <bold>Secondary objectives</bold>
        </p>
        <list list-type="bullet">
          <list-item>
            <p>Compare how these AI-based approaches differ between individual case–level and population-level applications, including potential complementarities between the 2 levels</p>
          </list-item>
          <list-item>
            <p>Describe the types of AI-based techniques and supporting automation tools used in causality assessment workflows</p>
          </list-item>
          <list-item>
            <p>Summarize reported data quality considerations and governance mechanisms (eg, human oversight, explainability, monitoring, and model maintenance) that support the safe use of AI in this context</p>
          </list-item>
        </list>
      </boxed-text>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>A scoping review methodology was selected to map concepts, approaches, and evidence within a heterogeneous and rapidly evolving field rather than to estimate effect sizes or conduct a meta-analysis. This protocol follows guidance from the <italic>JBI</italic> <italic>Manual for Evidence Synthesis</italic> [<xref ref-type="bibr" rid="ref25">25</xref>] and will be reported, as applicable, in accordance with PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews) [<xref ref-type="bibr" rid="ref26">26</xref>] and PRISMA-S (Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for reporting literature searches in systematic reviews) [<xref ref-type="bibr" rid="ref27">27</xref>]. The PRISMA-ScR and PRISMA-S checklists are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendices 1</xref> and <xref ref-type="supplementary-material" rid="app2">2</xref>, respectively. The protocol was prospectively registered in the Open Science Framework [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
      </sec>
      <sec>
        <title>Operational Definitions</title>
        <sec>
          <title>Causality Assessment</title>
          <p>In this review, causality assessment is defined as the plausibility evaluation of a causal relationship between a drug and an observed adverse event through the structured, qualitative synthesis of all available evidence streams [<xref ref-type="bibr" rid="ref2">2</xref>]. This definition encompasses both individual case–level assessment, in which evidence from a specific report or patient is evaluated, and population-level assessment, in which evidence from aggregated safety data, real-world data, or epidemiological analyses is used to evaluate potential causal associations or safety signals.</p>
          <p>Population-level causality assessment refers specifically to the evaluation of causal plausibility at the population level. This includes the explicit causal interpretation of detected safety signals, such as signal evaluation or validation, confounding assessment, causal modeling, or structured benefit-risk reasoning. In contrast, routine signal detection based solely on frequency-based disproportionality measures without causal interpretation is not considered population-level causality assessment and is excluded.</p>
        </sec>
        <sec>
          <title>AI-Based Methods</title>
          <p>AI-based methods are operationally defined as computational approaches that use data-driven learning, natural language processing, knowledge representation, causal modeling, or explicit knowledge- or rule-based reasoning to support or perform causality assessment. These include but are not limited to the following: (1) data-driven approaches such as machine learning models, deep learning models, natural language processing models, knowledge graph–based approaches, and causal inference models; (2) knowledge- or rule-based systems, including expert systems, that explicitly implement causal assessment logic, structured causality criteria, or rules for evaluating drug-event relationships; and (3) hybrid systems that combine statistical, machine learning, natural language processing, and knowledge- or rule-based components.</p>
        </sec>
        <sec>
          <title>AI-Based Causality Assessment</title>
          <p>AI applications relevant to causality assessment can be classified into 4 categories, as shown in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>. The applications covered in this review fall into categories 1 to 3, which are distinguished from upstream support functions and pure business automation (category 4).</p>
          <boxed-text id="box2" position="float">
            <title>AI application categories.</title>
            <p>
              <bold>Category 1: AI used for extracting or structuring information relevant to causality assessment</bold>
            </p>
            <p>This category is limited to tools that extract, structure, or synthesize evidence elements explicitly relevant to causal review, such as temporal relationships between exposure and event, de- or rechallenge information, dose-response information, alternative explanations, concomitant medications, comorbidities, relevant laboratory or clinical findings, and prior evidence. General information extraction, coding, or data processing will not be considered sufficient for inclusion unless the extracted information is explicitly used or intended to be used to support causal judgment or structured causality assessment.</p>
            <p>
              <bold>Category 2: AI used to assign or predict individual case–level causality or relatedness categories</bold>
            </p>
            <p>This category includes systems that support or automate the application of structured causality criteria or assign relatedness categories for observed adverse events at the individual case level. AI used exclusively for adverse event forecasting (ie, estimating the likelihood of adverse events occurring in patients who have not yet experienced them) is outside the scope of this review.</p>
            <p>
              <bold>Category 3: AI used for population-level causal inference or signal evaluation</bold>
            </p>
            <p>This category includes methods that explicitly address causal interpretation, confounding, counterfactual reasoning, causal modeling, signal evaluation, or totality-of-evidence assessment in relation to a potential drug-event association. The use of frequency-based disproportionality measures alone or the term “signal detection” alone will not be sufficient for inclusion unless the method is explicitly linked to causal interpretation, confounding assessment, signal evaluation, causal inference, or totality-of-evidence assessment.</p>
            <p>
              <bold>Category 4: AI or automation used solely for operational efficiency</bold>
            </p>
            <p>This category includes tools used for case intake, routing, duplicate detection, Medical Dictionary for Regulatory Activities coding, data transfer, report generation, workflow management, or administrative prioritization when they do not incorporate any causal reasoning component or explicit linkage to causal evidence synthesis.</p>
          </boxed-text>
          <p>Causality assessment algorithms such as the World Health Organization Uppsala Monitoring Centre system or the Naranjo algorithm will not be considered AI-based methods when they are used only as manually applied criteria or as simple automated score calculators. They will be considered within scope only when AI- or knowledge-based methods automate the interpretation or application of the criteria, for example, by extracting relevant information from case narratives or other evidence sources and applying the criteria to support a causality judgment.</p>
          <p>Simple statistical models such as logistic regression will be included only when explicitly implemented as a causal model or as part of a rule-based system for causality assessment. Models used solely for outcome prediction, prioritization, or classification without explicit causal framing will be excluded. Similarly, conventional descriptive statistics, disproportionality analyses used only as frequency-based screening without causal interpretation, and noncausal workflow automation will not be considered AI-based causality assessment by themselves.</p>
          <p>For methods that fall near the eligibility boundary, inclusion will be determined by whether they are explicitly used to support a causal judgment regarding the relationship between a medicinal product and an adverse event.</p>
        </sec>
      </sec>
      <sec>
        <title>Eligibility Criteria</title>
        <p>The review will address the population, concept, and context framework recommended by the JBI for scoping reviews [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
        <p>The central concept of interest is the use of AI-based methods to support or perform causality assessment for relationships between medicinal products for human use, including vaccines and biologics, and adverse events at either the individual case or population level. Medical devices, as well as device components of drug-device combination products, are excluded; studies concerning the medicinal component of such products remain eligible. At the population level, causality assessment is distinguished from routine signal detection: it encompasses approaches that address confounding or bias, apply causal inference methods, or provide explicit causal interpretation of a signal.</p>
        <p>Sources that describe or evaluate systems, methods, or workflows in which AI-based methods directly contribute to causality assessment or its interpretation in pharmacovigilance; propose frameworks, requirements, or governance models specifically for AI-based causality assessment in pharmacovigilance; or both will be included.</p>
        <p>The context of interest is pharmacovigilance and medicinal product safety for human use, encompassing marketing authorization holders and pharmaceutical companies, regulatory agencies and public health authorities, health care settings (eg, hospitals and clinics), and academic or collaborative research networks conducting pharmacovigilance or pharmacoepidemiological studies. No restrictions will be placed on country, health system, or regulatory framework.</p>
        <p>Nonempirical publications, including opinion pieces, editorials, and narrative commentaries that do not include substantive descriptions of AI-based methods or their application to causality assessment will be excluded. The complete eligibility criteria are summarized in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Eligibility criteria (population, concept, and context framework).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="130"/>
            <col width="450"/>
            <col width="420"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Inclusion criteria</td>
                <td>Exclusion criteria</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Population and data sources</td>
                <td>Human pharmacovigilance or drug safety–related data, including individual case safety reports and spontaneous reports; electronic health records and hospital information systems; disease or drug registries; pharmacoepidemiological datasets; clinical trial safety datasets; published literature for safety assessment; and social media, patient forums, and direct patient reports used for pharmacovigilance purposes</td>
                <td>Studies focusing exclusively on veterinary pharmacovigilance and sources not involving medicinal product safety, adverse events, pharmacovigilance, pharmacoepidemiology, or drug safety–related evidence</td>
              </tr>
              <tr valign="top">
                <td>Concept</td>
                <td>AI-based methods directly contributing to causality assessment, including (1) data-driven approaches (machine learning, deep learning, natural language processing, knowledge graphs, and causal inference models) and (2) knowledge- or rule-based systems explicitly implementing causal assessment logic. Both individual case– and population-level causality assessment are eligible. Eligible applications include AI used to extract or structure causality-relevant evidence elements, assign or predict case-level causality or relatedness categories, or support population-level causal inference or signal evaluation with explicit causal interpretation. Frameworks, requirements, or governance models for AI-based causality assessment in pharmacovigilance are also eligible.</td>
                <td>AI applied only to pharmacovigilance tasks unrelated to causality assessment with no explicit causal link, including general information extraction, MedDRA<sup>a</sup> coding, duplicate detection, case routing, or workflow automation without extraction or structuring of causality-relevant evidence elements; automation-only tools without an AI component; simple automated scoring of causality algorithms without AI-enabled evidence interpretation or application; statistical or prediction models without explicit causal framing; frequency-based disproportionality analyses or “signal detection” with no explicit causal interpretation, confounding assessment, signal evaluation, causal inference, or totality-of-evidence assessment; and AI used solely for purposes unrelated to drug safety or pharmacovigilance</td>
              </tr>
              <tr valign="top">
                <td>Context</td>
                <td>Human pharmacovigilance and medicinal product safety settings, including marketing authorization holders; pharmaceutical companies; regulatory agencies; public health authorities; health care settings; and academic or collaborative research networks conducting pharmacovigilance, pharmacoepidemiological, or drug safety research, with no restrictions based on country, health system, or regulatory framework</td>
                <td>Veterinary pharmacovigilance; AI applications used solely outside pharmacovigilance or medicinal product safety, such as marketing, adherence prediction, general clinical decision support unrelated to safety, or nonsafety administrative processes; and medical devices (including device-only vigilance) and combination products with respect to their device component</td>
              </tr>
              <tr valign="top">
                <td>Types of sources</td>
                <td>Quantitative, qualitative, and mixed methods empirical studies; methodological or technical papers; evaluation, feasibility, and pilot implementation studies; case studies; regulatory or industry reports with sufficient methodological details; and theses and conference proceedings with sufficient methodological details</td>
                <td>Opinion pieces, editorials, or narrative commentaries without substantive descriptions of AI-based methods, requirements, or governance</td>
              </tr>
              <tr valign="top">
                <td>Language and time frame</td>
                <td>English or Japanese; no restriction based on publication year</td>
                <td>All languages other than English or Japanese</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>MedDRA: Medical Dictionary for Regulatory Activities.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Information Sources</title>
        <p>Searches will be conducted in the following bibliographic databases: (1) PubMed (MEDLINE), (2) Web of Science Core Collection (Science Citation Index Expanded, Social Sciences Citation Index, Arts and Humanities Citation Index, Emerging Sources Citation Index, Book Citation Index, Conference Proceedings Citation Index, Current Chemical Reactions, and Index Chemicus), (3) ProQuest, (4) EBSCOhost platform (Academic Search Complete, Bibliography of Asian Studies, Business Source Complete, CINAHL Plus with Full Text, Communication Abstracts, EconLit, Education Resources Information Center, GreenFILE, Historical Abstracts, Index to Legal Periodicals &amp; Books, Information Science &amp; Technology Abstracts, Linguistics Abstracts Online, MEDLINE, MLA Directory of Periodicals, MLA International Bibliography, Peace Research Abstracts, Philosopher’s Index, PsycArticles, PsycInfo, Race Relations Abstracts, Regional Business News, SocINDEX with Full Text, Teacher Reference Center, and American Antiquarian Society Historical Periodicals Collection: Series 1-5), and (5) Ichushi Web (Japanese medical literature database).</p>
        <p>To identify additional sources not captured through database searches, the following supplementary strategies will be used. First, the reference lists of all included articles and relevant reviews or guidelines will be screened. Second, forward citation tracking may be conducted using Web of Science or Google Scholar where appropriate. Third, targeted searches of the websites of the following regulatory and organizational bodies will be conducted: the US Food and Drug Administration, the European Medicines Agency, the Council for International Organizations of Medical Sciences, the World Health Organization, the Uppsala Monitoring Centre, and the Pharmaceuticals and Medical Devices Agency. For each website, searches will use terms related to AI, pharmacovigilance, and causality assessment, focusing on guidance documents, reflection papers, and technical reports. The date of each search will be recorded.</p>
        <p>The database searches will be limited to English and Japanese. Finally, no study design filter will be applied.</p>
      </sec>
      <sec>
        <title>Search Strategy</title>
        <p>A 3-step search strategy as recommended by the JBI [<xref ref-type="bibr" rid="ref25">25</xref>] will be used. The search strategy was developed a priori in consultation with an information specialist and will be reported in accordance with applicable elements of the PRISMA-S [<xref ref-type="bibr" rid="ref27">27</xref>] adapted for the scoping review context in 3 steps.</p>
        <p>First, the development of the final strategy (initial limited search): an initial limited search of PubMed and Web of Science was conducted using a small set of key terms related to AI, pharmacovigilance, and causality assessment. Titles, abstracts, and indexing terms (eg, MeSH terms and keywords) of relevant articles were examined to identify additional terms.</p>
        <p>Second, the comprehensive database search: a full search strategy was developed for PubMed and adapted for each database, combining controlled vocabulary and free-text terms covering 3 main concept blocks (<xref ref-type="table" rid="table2">Table 2</xref>). All 3 blocks were combined using the Boolean operator AND; terms within each block were combined using OR.</p>
        <p>Third, citation tracking and supplementary searches: the reference lists of all the included studies and key reviews or guidelines will be screened for additional relevant sources. Where appropriate, forward citation tracking may be conducted using Web of Science or Google Scholar. Targeted searches of relevant websites and repositories (as prespecified in the Information Sources section) will also be performed.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Search concept blocks and representative terms (all 3 blocks will be combined using “AND”)<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="90"/>
            <col width="220"/>
            <col width="310"/>
            <col width="380"/>
            <thead>
              <tr valign="top">
                <td>Block</td>
                <td>Concept domain</td>
                <td>MeSH terms or controlled vocabulary terms (PubMed)</td>
                <td>Free-text keywords</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Pharmacovigilance</td>
                <td>“Pharmacovigilance” (MeSH), “Drug-Related Side Effects and Adverse Reactions” (MeSH), “Adverse Drug Reaction Reporting Systems” (MeSH), and “Product Surveillance, Postmarketing” (MeSH)</td>
                <td>“Pharmacovigilance,” “drug safety,” “adverse drug reaction*,” “adverse drug event*,” “adverse reaction,*” “drug-related adverse event*,” “ADR,” “adverse event*,” “safety signal*,” “safety report*,” “spontaneous report*,” and “ICSR*”</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Causality and causal assessment</td>
                <td>“Causality” (MeSH), “Bayes Theorem” (MeSH), and “Models, Statistical” (MeSH)</td>
                <td>“Causality assessment,” “causal inference,” “causal model*,” “causal relationship*,” “signal assessment,” “Naranjo,” and “WHO-UMC”</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>AI</td>
                <td>“Artificial Intelligence” (MeSH), “Machine Learning” (MeSH), “Deep Learning” (MeSH), “Natural Language Processing” (MeSH), and “Expert Systems” (MeSH)</td>
                <td>“Artificial intelligence,” “machine learning,” “deep learning,” “natural language processing,” “NLP,” “knowledge graph*,” “expert system*,” “prediction model*,” “generative AI,” “agentic AI,” “large language model*,” “LLM*,” “ChatGPT,” “Claude,” “Gemini,” “GPT-5*,” “GPT-4*,” and “GPT-3*”</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>The PubMed database search strategy uses MeSH terms combined with free-text keywords in the title and abstract field. For the other information sources, the strategy was translated into database-appropriate field codes and, where available, controlled vocabulary terms while maintaining the same conceptual structure. Complete search strings for all 5 databases are provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Handling of Japanese- and English-Language Records</title>
        <p>As all members of the review team are fluent in both Japanese and English, records in both languages will be screened and charted in their original language. For Japanese-language records retrieved from Ichushi Web and other sources, title and abstract and full-text screening will be performed directly in Japanese by at least 2 reviewers. Data charting for Japanese sources will likewise be conducted based on the original Japanese texts, with key data items (eg, study design, data sources, AI methods, outcomes, and main conclusions) entered into the shared data charting form in English to facilitate integrated synthesis across languages. Where important concepts or terminology do not have a straightforward English equivalent, the original Japanese wording will be recorded in the data charting form alongside an English summary. Any uncertainties or disagreements regarding language interpretation will be resolved through discussion within the review team using the same multistep consensus process as that for other reviewer disagreements.</p>
      </sec>
      <sec>
        <title>Study and Source Selection</title>
        <sec>
          <title>Overview</title>
          <p>All search results will be exported to a reference manager (eg, EndNote; Clarivate Analytics), deduplicated, and then imported into a screening tool (eg, Rayyan; Rayyan Systems Inc) for study selection. When multiple publications describe the same AI system or implementation, they will be grouped as a single system unit during data charting. The most recent and most methodologically comprehensive publication will serve as the primary reference, with others consulted as supplementary sources. Descriptive statistics will report both the number of distinct systems identified and the total number of publications included.</p>
          <p>Study selection will proceed in 2 stages as follows. First, for title and abstract screening, 2 reviewers will independently screen titles and abstracts against the eligibility criteria. Records clearly not meeting the inclusion criteria will be excluded. Records retained by either reviewer will proceed to the full-text screening stage. Second, for full-text screening, the full texts of potentially relevant records will be retrieved. Two reviewers will independently assess each full text against the inclusion and exclusion criteria. Reasons for exclusion at this stage will be recorded (eg, not a pharmacovigilance context, AI not used for causality assessment, or insufficient methodological details).</p>
        </sec>
        <sec>
          <title>Calibration and Agreement</title>
          <p>Before full screening, the reviewers will pilot the eligibility criteria on a sample of approximately 20 to 30 records to ensure shared understanding and refine operational definitions if needed.</p>
        </sec>
        <sec>
          <title>Disagreement Resolution</title>
          <p>At both the title and abstract and full-text stages, disagreements between the 2 reviewers will first be flagged within the screening tool. A prespecified third reviewer will then independently assess the record. If consensus is not reached after the third reviewer’s assessment, disagreements will be resolved through discussion within the review team and, where necessary, by involving additional members. Study selection will be documented using a PRISMA-ScR flow diagram [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Data Charting (Data Extraction)</title>
        <p>A structured data charting form will be developed in NVivo (Lumivero) or Microsoft Excel informed by the review objectives and the <italic>JBI Manual for Evidence Synthesis</italic> [<xref ref-type="bibr" rid="ref25">25</xref>]. This form will be piloted on a small number of included sources prior to full implementation and refined as necessary. The planned data charting items are summarized in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Planned data charting items.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="260"/>
            <col width="740"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Data items</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Bibliographic and general information</td>
                <td>Authors, year of publication, and country or region; journal or source type; and funding sources and author-declared conflicts of interest</td>
              </tr>
              <tr valign="top">
                <td>Study characteristics</td>
                <td>Study design (eg, methodological paper, retrospective cohort study, cross-sectional study, qualitative study, mixed methods study, case study, or pilot implementation) and setting and organization type</td>
              </tr>
              <tr valign="top">
                <td>Population and data sources</td>
                <td>Types of safety data used (eg, individual case safety reports, electronic health records, registries, claims data, clinical trial data, published literature, and social media), key patient population or therapeutic area characteristics, and sample size or data volume</td>
              </tr>
              <tr valign="top">
                <td>Causality assessment level and role</td>
                <td>Levels targeted: individual case level, population level, or both and position of the AI-based method within the workflow (eg, information extraction and structuring, application of causality criteria, signal detection and causal interpretation, or governance and reporting)</td>
              </tr>
              <tr valign="top">
                <td>AI techniques and implementation details</td>
                <td>AI methods used (eg, supervised, unsupervised, or reinforcement learning; deep learning; natural language processing; knowledge graphs; rule-based systems; causal models; and hybrid systems), any automation technologies and their role, inputs and features, training and validation data, implementation maturity level (conceptual proposal, prototype or proof of concept, retrospective or prospective validation, pilot implementation, routine deployment, or regulatory or organizational framework), and source type</td>
              </tr>
              <tr valign="top">
                <td>Information requirements for causality assessment</td>
                <td>Types and granularity of the information required at the individual case level (eg, exposure and event timing, de- or rechallenge information, concomitant medications, comorbidities, and laboratory results), information requirements at the population level (eg, exposure populations, comparator groups, follow-up time, confounders, and health care use patterns), and any explicitly stated minimal datasets or mandatory data elements</td>
              </tr>
              <tr valign="top">
                <td>Data quality and performance metrics</td>
                <td>Data quality dimensions (completeness, accuracy, timeliness, consistency, and representativeness) and preprocessing steps; model performance metrics (eg, sensitivity, specificity, PPV<sup>a</sup>, NPV<sup>b</sup>, AUROC<sup>c</sup>, <italic>F</italic><sub>1</sub>-score, and calibration); validation strategies (internal, cross-validation, temporal, external, and comparison with expert assessment); and fairness, generalizability, or robustness evaluation</td>
              </tr>
              <tr valign="top">
                <td>Governance and oversight</td>
                <td>Human-in-the-loop design (thresholds for manual review, override mechanisms, and escalation pathways); approaches to explainability and transparency; and monitoring, maintenance, and updating (drift detection, retraining schedules, and performance auditing)</td>
              </tr>
              <tr valign="top">
                <td>Risks and their management</td>
                <td>Types of risks discussed (eg, algorithmic bias, model drift, overfitting, misclassification, automation bias, lack of explainability, and accountability and liability) and strategies for risk mitigation</td>
              </tr>
              <tr valign="top">
                <td>Interaction between individual case– and population-level applications</td>
                <td>How outputs from individual-level tools may inform population-level signal detection or causal modeling and vice versa, mechanisms for cross-validation, and shared infrastructure or data pipelines</td>
              </tr>
              <tr valign="top">
                <td>Main findings and authors’ conclusions</td>
                <td>Reported benefits, limitations, and recommendations and identified knowledge gaps and future research directions</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>PPV: positive predictive value.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>NPV: negative predictive value.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>AUROC: area under the receiver operating characteristic curve.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Two reviewers will independently chart data from each included source. One reviewer may perform the initial charting, and the second reviewer will verify the entries. Disagreements will be handled using the same 3-reviewer and consensus process used for study selection. The data charting form will remain flexible, and new fields may be added if important themes emerge during the review. Modifications will be reported in the final review.</p>
      </sec>
      <sec>
        <title>Critical Appraisal of Individual Sources of Evidence</title>
        <p>In accordance with JBI guidance for scoping reviews, a formal risk-of-bias assessment is not required when the objective is to map existing evidence and concepts [<xref ref-type="bibr" rid="ref25">25</xref>]. However, given this review’s focus on data quality, validation, and governance, methodological characteristics relevant to interpreting AI-based methods will be documented in a structured manner during data charting. For each included AI-based or prediction model study, the following will be recorded: (1) whether training data provenance is reported, (2) whether the reference standard or labeling process is described, (3) whether subgroup performance is evaluated, (4) whether data leakage controls are described, and (5) whether transportability or generalizability is addressed. These items are informed by the TRIPOD+AI (Transparent Reporting of a Multivariable Prediction Model for Individual Prognosis or Diagnosis for AI studies) reporting guidelines [<xref ref-type="bibr" rid="ref29">29</xref>] and the PROBAST+AI (Prediction Model Risk-of-Bias Assessment Tool for AI studies) appraisal tool [<xref ref-type="bibr" rid="ref30">30</xref>], used here as organizing frameworks rather than formal scoring instruments. These methodological characteristics will be reported descriptively in the completed review.</p>
      </sec>
      <sec>
        <title>Data Synthesis and Presentation</title>
        <p>Thematic synthesis will follow a reflexive thematic analysis approach [<xref ref-type="bibr" rid="ref31">31</xref>] using both inductive and deductive strategies. An initial deductive coding framework will be derived from the review’s population, concept, and context framework elements; primary and secondary objectives; and planned data items. Additional themes will be identified inductively. Findings will be presented using a combination of tables, figures (eg, workflow diagrams), and narrative synthesis. Descriptive summaries will be stratified by source type and implementation maturity level to avoid conflating conceptual proposals, prototype systems, validation studies, pilot implementations, and routine deployments. Analysis will be conducted using NVivo, structured Microsoft Excel matrices, or both.</p>
        <p>Each analytic product corresponds to a specific research objective: descriptive summaries and thematic findings on requirements and risks address primary objective 1, cross-level comparisons address secondary objective 1, AI technique characterization addresses secondary objective 2, and governance synthesis addresses secondary objective 3.</p>
      </sec>
      <sec>
        <title>Patient and Public Involvement</title>
        <p>No patients or members of the public are involved in the design, conduct, reporting, or dissemination of this scoping review as it relies solely on previously published and publicly available data and documents.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>This protocol was registered in the Open Science Framework on December 23, 2025 (osf.io QVF5C) [<xref ref-type="bibr" rid="ref28">28</xref>]. The registration was subsequently updated on May 19, 2026, to reflect an extension to the data collection period. A preliminary database search was conducted in December 2025, retrieving a total of 760 records, of which the preliminary title and abstract screening identified 196 (25.8%) articles for full-text review. The formal search based on this protocol will be conducted in July 2026. Data charting is scheduled for August 2026, and synthesis is scheduled for September 2026. The completed review is expected to be submitted for publication by the end of December 2026. Deviations from this protocol will be documented and reported in the final review. This research was funded by the Ministry of Health, Labor and Welfare from April 2025 to March 2026 and by the Japan Society for the Promotion of Science from April 2026 to the present.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Expected Findings</title>
        <p>This review is expected to offer several contributions. First, it will provide a structured map of AI-based applications for causality assessment at the individual case and population levels, identifying areas of concentration and evidence gaps. Second, mapping reported information inputs, data quality dimensions, and validation practices is expected to support pharmacovigilance departments and marketing authorization holders when designing or procuring AI-based tools. Third, synthesizing reported risks and mitigation strategies may assist regulators and guideline developers in refining governance frameworks and help AI developers align system designs with pharmacovigilance needs.</p>
        <p>Despite these contributions, several limitations are expected. For example, restricting inclusion to English- and Japanese-language sources introduces a potential source of selection bias; relevant work—particularly implementation descriptions and regulatory guidance documents from non–English- or Japanese-speaking regions—may be underrepresented. The broad scope of AI-based methods and the heterogeneous nature of implementations may constrain the ability to compare performance quantitatively. Additionally, the review will be limited by what is documented in the published literature; practical implementation details and internal organizational practices may not be captured.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This scoping review protocol sets out a systematic and transparent approach to mapping how AI-based methods are used, proposed, and discussed for causality assessment in pharmacovigilance across the individual case and population levels. By consolidating evidence that is currently dispersed across methodological, implementation, and regulatory sources, the planned review is intended to clarify the current landscape and establish a foundation for future empirical and methodological research on AI-supported causality assessment.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>PRISMA-ScR checklist.</p>
        <media xlink:href="resprot_v15i1e101691_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 517 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>PRISMA-S (Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for reporting literature searches in systematic reviews) checklist.</p>
        <media xlink:href="resprot_v15i1e101691_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 221 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Search strategies.</p>
        <media xlink:href="resprot_v15i1e101691_app3.docx" xlink:title="DOCX File , 24 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">JBI</term>
          <def>
            <p>Joanna Briggs Institute</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">PRISMA-S</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for reporting literature searches in systematic reviews</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PRISMA-ScR</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">PROBAST+AI</term>
          <def>
            <p>Prediction Model Risk-of-Bias Assessment Tool for AI studies</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">TRIPOD+AI</term>
          <def>
            <p>Transparent Reporting of a Multivariable Prediction Model for Individual Prognosis or Diagnosis for AI studies</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank Professor Daisuke Koide (the University of Tokyo) and Professor Shinichiroh Yokota (Chiba University) for their helpful advice on developing the search strategy and for their constructive comments on the search strings for this scoping review protocol. They would also like to thank Editage for English-language editing. The views expressed in this paper are the personal views of the authors and may not be understood or quoted as being made on behalf of or reflecting the position of the Pharmaceuticals and Medical Devices Agency. The authors declare the use of generative AI (GenAI) in the research and writing process. According to the Generative AI Delegation Taxonomy (2025), the following tasks were delegated to GenAI tools under full human supervision: evaluation of the research novelty and identification of knowledge gaps, translation, and recommendations. The GenAI tool used was GPT-5.1 Pro (OpenAI) and DeepL Pro (DeepL SE). Responsibility for the final manuscript lies entirely with the authors. GenAI tools are not listed as authors and do not bear responsibility for the final outcomes.</p>
    </ack>
    <notes>
      <title>Data Availability</title>
      <p>Data sharing is not applicable to this article as no data sets were generated or analyzed during this study.</p>
    </notes>
    <notes>
      <title>Funding</title>
      <p>This work is supported by the Ministry of Health, Labor, and Welfare of Japan (grant 23KC1005) and the Japan Society for the Promotion of Science Grants-in-Aid for Scientific Research (grant 26K09796). The funders had no role in the study design, data collection, data analysis, decision to publish, or manuscript preparation.</p>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>What is pharmacovigilance?</article-title>
          <source>World Health Organization</source>
          <access-date>2026-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/teams/regulation-prequalification/regulation-and-safety/pharmacovigilance">https://www.who.int/teams/regulation-prequalification/regulation-and-safety/pharmacovigilance</ext-link>
          </comment>
        </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>Hammad</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Afsar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McAvoy</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Le Louet</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Aspects to consider in causality assessment of safety signals: broadening the thought process</article-title>
          <source>Front Drug Saf Regul</source>
          <year>2023</year>
          <month>5</month>
          <day>25</day>
          <volume>3</volume>
          <fpage>1193413</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fdsfr.2023.1193413"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdsfr.2023.1193413</pub-id>
          <pub-id pub-id-type="medline">40980101</pub-id>
          <pub-id pub-id-type="pii">1193413</pub-id>
          <pub-id pub-id-type="pmcid">PMC12443079</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>The use of the WHO-UMC system for standardised case causality assessment</article-title>
          <source>World Health Organization</source>
          <year>2013</year>
          <month>06</month>
          <day>05</day>
          <access-date>2026-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/m/item/WHO-causality-assessment">https://www.who.int/publications/m/item/WHO-causality-assessment</ext-link>
          </comment>
        </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>Naranjo</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Busto</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Sellers</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Sandor</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ruiz</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Janecek</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Domecq</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Greenblatt</surname>
              <given-names>DJ</given-names>
            </name>
          </person-group>
          <article-title>A method for estimating the probability of adverse drug reactions</article-title>
          <source>Clin Pharmacol Ther</source>
          <year>1981</year>
          <month>08</month>
          <volume>30</volume>
          <issue>2</issue>
          <fpage>239</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1038/clpt.1981.154</pub-id>
          <pub-id pub-id-type="medline">7249508</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <source>Practical Aspects of Signal Detection in Pharmacovigilance: Report of CIOMS Working Group VIII</source>
          <year>2010</year>
          <publisher-loc>Geneva, Switzerland</publisher-loc>
          <publisher-name>Council for International Organizations of Medical Sciences</publisher-name>
        </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>Martin</surname>
              <given-names>GL</given-names>
            </name>
            <name name-style="western">
              <surname>Jouganous</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Savidan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bellec</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Goehrs</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Benkebil</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miremont</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Micallef</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Salvo</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Pariente</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Létinier</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Validation of artificial intelligence to support the automatic coding of patient adverse drug reaction reports, using nationwide pharmacovigilance data</article-title>
          <source>Drug Saf</source>
          <year>2022</year>
          <month>05</month>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>535</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35579816"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40264-022-01153-8</pub-id>
          <pub-id pub-id-type="medline">35579816</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40264-022-01153-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC9112264</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>Barrett</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Erlanson</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>China</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Norén</surname>
              <given-names>GN</given-names>
            </name>
          </person-group>
          <article-title>A scalable predictive modelling approach to identifying duplicate adverse event reports for drugs and vaccines</article-title>
          <source>arXiv. Preprint posted online on March 31, 2025</source>
          <pub-id pub-id-type="doi">10.48550/arXiv.2504.03729</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>Lieber</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gosselt</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Kools</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Kruijssen</surname>
              <given-names>OC</given-names>
            </name>
            <name name-style="western">
              <surname>Van Lierop</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Härmark</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Van Hunsel</surname>
              <given-names>FP</given-names>
            </name>
          </person-group>
          <article-title>Natural language processing for automated triage and prioritization of individual case safety reports for case-by-case assessment</article-title>
          <source>Front Drug Saf Regul</source>
          <year>2023</year>
          <month>02</month>
          <day>7</day>
          <volume>3</volume>
          <fpage>1120135</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fdsfr.2023.1120135"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdsfr.2023.1120135</pub-id>
          <pub-id pub-id-type="medline">40980103</pub-id>
          <pub-id pub-id-type="pii">1120135</pub-id>
          <pub-id pub-id-type="pmcid">PMC12443081</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>Tao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yisha</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>LitAutoScreener: development and validation of an automated literature screening tool in evidence-based medicine driven by large language models</article-title>
          <source>Health Data Sci</source>
          <year>2025</year>
          <month>9</month>
          <day>2</day>
          <volume>5</volume>
          <fpage>0322</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://spj.science.org/doi/10.34133/hds.0322?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.34133/hds.0322</pub-id>
          <pub-id pub-id-type="medline">40904687</pub-id>
          <pub-id pub-id-type="pii">0322</pub-id>
          <pub-id pub-id-type="pmcid">PMC12404845</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>Ghosh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kempf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pufko</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Barrios Martinez</surname>
              <given-names>LF</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Sethi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Automation opportunities in pharmacovigilance: an industry survey</article-title>
          <source>Pharmaceut Med</source>
          <year>2020</year>
          <month>02</month>
          <volume>34</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1007/s40290-019-00320-0</pub-id>
          <pub-id pub-id-type="medline">32036574</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40290-019-00320-0</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>Cherkas</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ide</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van Stekelenborg</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Leveraging machine learning to facilitate individual case causality assessment of adverse drug reactions</article-title>
          <source>Drug Saf</source>
          <year>2022</year>
          <month>05</month>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>571</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1007/s40264-022-01163-6</pub-id>
          <pub-id pub-id-type="medline">35579819</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40264-022-01163-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Diao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Shu</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Prediction of adverse drug reactions based on knowledge graph embedding</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2021</year>
          <month>02</month>
          <day>04</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-021-01402-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-021-01402-3</pub-id>
          <pub-id pub-id-type="medline">33541342</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-021-01402-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7863488</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Deng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Machine learning in causal inference: application in pharmacovigilance</article-title>
          <source>Drug Saf</source>
          <year>2022</year>
          <month>05</month>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>459</fpage>
          <lpage>76</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35579811"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40264-022-01155-6</pub-id>
          <pub-id pub-id-type="medline">35579811</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40264-022-01155-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC9114053</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kreimeyer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dang</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Spiker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Muñoz</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Rosner</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ball</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Botsis</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Feature engineering and machine learning for causality assessment in pharmacovigilance: lessons learned from application to the FDA Adverse Event Reporting System</article-title>
          <source>Comput Biol Med</source>
          <year>2021</year>
          <month>08</month>
          <volume>135</volume>
          <fpage>104517</fpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2021.104517</pub-id>
          <pub-id pub-id-type="medline">34130003</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(21)00311-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hazell</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shakir</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Under-reporting of adverse drug reactions: a systematic review</article-title>
          <source>Drug Saf</source>
          <year>2006</year>
          <volume>29</volume>
          <issue>5</issue>
          <fpage>385</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.2165/00002018-200629050-00003</pub-id>
          <pub-id pub-id-type="medline">16689555</pub-id>
          <pub-id pub-id-type="pii">2953</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Matsuda</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aoki</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kawamata</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kimotsuki</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kobayashi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kuriki</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Nakayama</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Okugawa</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sugimura</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tomita</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Takahashi</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Bias in spontaneous reporting of adverse drug reactions in Japan</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <month>5</month>
          <day>1</day>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>e0126413</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0126413"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0126413</pub-id>
          <pub-id pub-id-type="medline">25933226</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-57364</pub-id>
          <pub-id pub-id-type="pmcid">PMC4416713</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sturkenboom</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mann</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lagnaoui</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Begaud</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Biases affecting the proportional reporting ratio (PPR) in spontaneous reports pharmacovigilance databases: the example of sertindole</article-title>
          <source>Pharmacoepidemiol Drug Saf</source>
          <year>2003</year>
          <month>06</month>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>271</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1002/pds.848</pub-id>
          <pub-id pub-id-type="medline">12812006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ferreira-da-Silva</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cruz-Correia</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ribeiro</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Beyond black boxes: using explainable causal artificial intelligence to separate signal from noise in pharmacovigilance</article-title>
          <source>Int J Clin Pharm</source>
          <year>2026</year>
          <month>04</month>
          <volume>48</volume>
          <issue>2</issue>
          <fpage>677</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1007/s11096-025-02004-z</pub-id>
          <pub-id pub-id-type="medline">40889016</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11096-025-02004-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC12992339</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ball</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Talal</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Dang</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Muñoz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Markatou</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Trust but verify: lessons learned for the application of AI to case-based clinical decision-making from postmarketing drug safety assessment at the US Food and Drug Administration</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <month>06</month>
          <day>06</day>
          <volume>26</volume>
          <fpage>e50274</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e50274/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/50274</pub-id>
          <pub-id pub-id-type="medline">38842929</pub-id>
          <pub-id pub-id-type="pii">v26i1e50274</pub-id>
          <pub-id pub-id-type="pmcid">PMC11190620</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
          <source>Artificial Intelligence in Pharmacovigilance</source>
          <year>2025</year>
          <publisher-loc>Geneva, Switzerland</publisher-loc>
          <publisher-name>Council for International Organizations of Medical Sciences</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goddard</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Roudsari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Automation bias - a hidden issue for clinical decision support system use</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2011</year>
          <volume>164</volume>
          <fpage>17</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="medline">21335682</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdelwanis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alarafati</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Tammam</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Simsekler</surname>
              <given-names>MC</given-names>
            </name>
          </person-group>
          <article-title>Exploring the risks of automation bias in healthcare artificial intelligence applications: a Bowtie analysis</article-title>
          <source>J Saf Sci Resil</source>
          <year>2024</year>
          <month>12</month>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>460</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jnlssr.2024.06.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>Reflection paper on the use of artificial intelligence (AI) in the medicinal product lifecycle</article-title>
          <source>European Medicines Agency</source>
          <year>2024</year>
          <month>9</month>
          <day>9</day>
          <access-date>2026-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ema.europa.eu/en/documents/scientific-guideline/reflection-paper-use-artificial-intelligence-ai-medicinal-product-lifecycle_en.pdf">https://www.ema.europa.eu/en/documents/scientific-guideline/reflection-paper-use-artificial-intelligence-ai-medicinal-product-lifecycle_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>Considerations for the use of artificial intelligence to support regulatory decision-making for drug and biological products draft guidance for industry and other interested parties</article-title>
          <source>U.S. Food &amp; Drug Administration</source>
          <year>2025</year>
          <month>01</month>
          <access-date>2026-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/regulatory-information/search-fda-guidance-documents/considerations-use-artificial-intelligence-support-regulatory-decision-making-drug-and-biological">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/considerations-use-artificial-intelligence-support-regulatory-decision-making-drug-and-biological</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McInerney</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Munn</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Aromataris</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lockwood</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Porritt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Pilla</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jordan</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Scoping reviews</article-title>
          <source>JBI Manual for Evidence Synthesis</source>
          <year>2024</year>
          <publisher-loc>North Adelaide, Australia</publisher-loc>
          <publisher-name>JBI Global</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Lillie</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zarin</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Colquhoun</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Levac</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Horsley</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Weeks</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hempel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McGowan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hartling</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Aldcroft</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Garritty</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lewin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Macdonald</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Langlois</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Soares-Weiser</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Moriarty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Clifford</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tunçalp</surname>
              <given-names>Ö</given-names>
            </name>
            <name name-style="western">
              <surname>Straus</surname>
              <given-names>SE</given-names>
            </name>
          </person-group>
          <article-title>PRISMA extension for scoping reviews (PRISMA-ScR): checklist and explanation</article-title>
          <source>Ann Intern Med</source>
          <year>2018</year>
          <month>10</month>
          <day>02</day>
          <volume>169</volume>
          <issue>7</issue>
          <fpage>467</fpage>
          <lpage>73</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/M18-0850?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M18-0850</pub-id>
          <pub-id pub-id-type="medline">30178033</pub-id>
          <pub-id pub-id-type="pii">2700389</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rethlefsen</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Kirtley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Waffenschmidt</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ayala</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Koffel</surname>
              <given-names>JB</given-names>
            </name>
          </person-group>
          <article-title>PRISMA-S: an extension to the PRISMA statement for reporting literature searches in systematic reviews</article-title>
          <source>Syst Rev</source>
          <year>2021</year>
          <month>01</month>
          <day>26</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>39</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://systematicreviewsjournal.biomedcentral.com/articles/10.1186/s13643-020-01542-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13643-020-01542-z</pub-id>
          <pub-id pub-id-type="medline">33499930</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13643-020-01542-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7839230</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ohta</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ota</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ohta</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence for causality assessment in pharmacovigilance: protocol for a scoping review</article-title>
          <source>Open Science Framework</source>
          <year>2025</year>
          <access-date>2026-06-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://osf.io/qvf5c/overview">https://osf.io/qvf5c/overview</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Moons</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Dhiman</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Beam</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Van Calster</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</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>Reitsma</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>van Smeden</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Boulesteix</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Camaradou</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</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>Glocker</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Golub</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffman</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Kengne</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Lam</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Loder</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Maier-Hein</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mateen</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>McCradden</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Oakden-Rayner</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>Parnell</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rose</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wynants</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Logullo</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>TRIPOD+AI statement: updated guidance for reporting clinical prediction models that use regression or machine learning methods</article-title>
          <source>BMJ</source>
          <year>2024</year>
          <month>04</month>
          <day>16</day>
          <volume>385</volume>
          <fpage>e078378</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=38626948"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2023-078378</pub-id>
          <pub-id pub-id-type="medline">38626948</pub-id>
          <pub-id pub-id-type="pmcid">PMC11019967</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moons</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Damen</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Kaul</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Andaur Navarro</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Dhiman</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Beam</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Van Calster</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</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>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kengne</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Maier-Hein</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Logullo</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>Liu</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Oakden-Rayner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Wynants</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Reitsma</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>van Smeden</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>PROBAST+AI: an updated quality, risk of bias, and applicability assessment tool for prediction models using regression or artificial intelligence methods</article-title>
          <source>BMJ</source>
          <year>2025</year>
          <month>03</month>
          <day>24</day>
          <volume>388</volume>
          <fpage>e082505</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj-2024-082505</pub-id>
          <pub-id pub-id-type="medline">40127903</pub-id>
          <pub-id pub-id-type="pmcid">PMC11931409</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using thematic analysis in psychology</article-title>
          <source>Qual Res Psychol</source>
          <year>2008</year>
          <month>07</month>
          <day>21</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
