<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</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">v27i1e65651</article-id>
      <article-id pub-id-type="pmid">40063946</article-id>
      <article-id pub-id-type="doi">10.2196/65651</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Assessment of the Efficiency of a ChatGPT-Based Tool, MyGenAssist, in an Industry Pharmacovigilance Department for Case Documentation: Cross-Over Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>de Azevedo Cardoso</surname>
            <given-names>Taiane</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Matsuda</surname>
            <given-names>Shinichi</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chrimes</surname>
            <given-names>Dillon</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Benaïche</surname>
            <given-names>Alexandre</given-names>
          </name>
          <degrees>PharmD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Bayer Healthcare SAS France</institution>
            <addr-line>1 Rue Claude Bernard</addr-line>
            <addr-line>Lille, 59000</addr-line>
            <country>France</country>
            <phone>33 320445962</phone>
            <email>benaichealexandre@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0008-4407-2782</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Billaut-Laden</surname>
            <given-names>Ingrid</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-8651-000X</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Randriamihaja</surname>
            <given-names>Herivelo</given-names>
          </name>
          <degrees>PharmD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0005-5468-043X</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Bertocchio</surname>
            <given-names>Jean-Philippe</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4104-702X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Bayer Healthcare SAS France</institution>
        <addr-line>Lille</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>SKEZI, Les Papèteries—Image Factory</institution>
        <addr-line>Annecy</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Assistance Publique—Hôpitaux de Paris, Pitié-Salpêtrière Hospital</institution>
        <addr-line>Paris</addr-line>
        <country>France</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Alexandre Benaïche <email>benaichealexandre@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>10</day>
        <month>3</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e65651</elocation-id>
      <history>
        <date date-type="received">
          <day>21</day>
          <month>8</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>26</day>
          <month>9</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>17</day>
          <month>11</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>13</day>
          <month>1</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Alexandre Benaïche, Ingrid Billaut-Laden, Herivelo Randriamihaja, Jean-Philippe Bertocchio. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 10.03.2025.</copyright-statement>
      <copyright-year>2025</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 the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2025/1/e65651" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>At the end of 2023, Bayer AG launched its own internal large language model (LLM), MyGenAssist, based on ChatGPT technology to overcome data privacy concerns. It may offer the possibility to decrease their harshness and save time spent on repetitive and recurrent tasks that could then be dedicated to activities with higher added value. Although there is a current worldwide reflection on whether artificial intelligence should be integrated into pharmacovigilance, medical literature does not provide enough data concerning LLMs and their daily applications in such a setting. Here, we studied how this tool could improve the case documentation process, which is a duty for authorization holders as per European and French good vigilance practices.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The aim of the study is to test whether the use of an LLM could improve the pharmacovigilance documentation process.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>MyGenAssist was trained to draft templates for case documentation letters meant to be sent to the reporters. Information provided within the template changes depending on the case: such data come from a table sent to the LLM. We then measured the time spent on each case for a period of 4 months (2 months before using the tool and 2 months after its implementation). A multiple linear regression model was created with the time spent on each case as the explained variable, and all parameters that could influence this time were included as explanatory variables (use of MyGenAssist, type of recipient, number of questions, and user). To test if the use of this tool impacts the process, we compared the recipients’ response rates with and without the use of MyGenAssist.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>An average of 23.3% (95% CI 13.8%-32.8%) of time saving was made thanks to MyGenAssist (<italic>P</italic>&#60;.001; adjusted <italic>R</italic><sup>2</sup>=0.286) on each case, which could represent an average of 10.7 (SD 3.6) working days saved each year. The answer rate was not modified by the use of MyGenAssist (20/48, 42% vs 27/74, 36%; <italic>P</italic>=.57) whether the recipient was a physician or a patient. No significant difference was found regarding the time spent by the recipient to answer (mean 2.20, SD 3.27 days vs mean 2.65, SD 3.30 days after the last attempt of contact; <italic>P</italic>=.64). The implementation of MyGenAssist for this activity only required a 2-hour training session for the pharmacovigilance team.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Our study is the first to show that a ChatGPT-based tool can improve the efficiency of a good practice activity without needing a long training session for the affected workforce. These first encouraging results could be an incentive for the implementation of LLMs in other processes.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>MyGenAssist</kwd>
        <kwd>large language model</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>ChatGPT</kwd>
        <kwd>pharmacovigilance</kwd>
        <kwd>efficiency</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Artificial intelligence (AI) is currently the center of attention in a lot of disciplines. Health is no exception. For instance, AI could be useful for the analysis of pictures for detecting local signs of catheter-associated infections [<xref ref-type="bibr" rid="ref1">1</xref>] or for reducing both the time and costs required for drug discovery [<xref ref-type="bibr" rid="ref2">2</xref>]. It could also play a role in the education of future health care professionals [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>Studies from previous years already provided evidence that the use of AI would benefit pharmaceutical companies [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. However, most of those studies used complex applications of AI to extract or synthesize data from documents like health records [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>] or social media content [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>].</p>
      <p>Although not yet reachable to a wide audience, large language models (LLMs) offer possibilities to integrate AI in several domains without requiring a long training of the workforce, thanks to its accessibility and ease of use. While everyone can use some LLMs that are open access—including ChatGPT since November 2022 [<xref ref-type="bibr" rid="ref12">12</xref>]—getting an adequate answer sometimes requires gradually improving the prompts. Hence, the integration of LLMs in the work environment can provide new soft skills at a low cost and promote the empowerment of workers. Several studies already showed that pharmacists and other health care professionals are willing to use LLMs as a help in their work [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>However, the use of LLMs raises concerns about data privacy. Recent news showed that the information provided by some users in their prompts could be transferred by ChatGPT to others [<xref ref-type="bibr" rid="ref16">16</xref>]. This threat can be answered by companies with the opportunity to develop their own LLM for internal use.</p>
      <p>Hence, Bayer AG launched on September 21, 2023, its own internal LLM called MyGenAssist, based on ChatGPT technology. Bayer, as a market authorization holder in Europe, has the duty to set a system to collect, register, and analyze adverse events related to its products according to European [<xref ref-type="bibr" rid="ref17">17</xref>] and French good pharmacovigilance practices (GVPs) [<xref ref-type="bibr" rid="ref18">18</xref>] and the European Directive 2001/83/CE [<xref ref-type="bibr" rid="ref19">19</xref>]. Tasks related to this imperative follow internal procedures, which make some of them repetitive and time-consuming. A semiautomatization of these tasks thanks to an LLM could make them less arduous for workers and procure more time for other activities at higher added value.</p>
      <p>In the pharmacovigilance field, the Giens Workshop [<xref ref-type="bibr" rid="ref20">20</xref>] in 2022 aimed to initiate a reflection on the integration of AI in this area and highlighted the actions implying the writing of a letter to contact a patient or a health care professional as a good opportunity for this. To the best of our knowledge, no study described LLMs’ use cases in pharmacovigilance from a daily and practical perspective.</p>
      <p>In this study, we aim to determine whether the use of MyGenAssist in the pharmacovigilance case documentation process can provide an improvement in efficiency (ie, save time without leading to a decrease in the answer rate).</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Description of the Activity and Materials Used</title>
        <sec>
          <title>Description of the Case Documentation Process and Potential Contribution of MyGenAssist</title>
          <p>The current internal process for collecting, recording, and documenting spontaneous case reports of adverse drug events at Bayer France is described here (<xref rid="figure1" ref-type="fig">Figure 1</xref>): reporters can notify Bayer about cases by phone, mail, or electronic means. The report is compiled into a source document, which is then added to an internal pharmacovigilance database by a local pharmacovigilance officer. The source document is analyzed by a case evaluator who is part of the company’s global pharmacovigilance team. Based on the global analysis, the pharmacovigilance officer is in charge of defining the final list of relevant questions to complete the case. The GVPs, written by the French Agence Nationale de Sécurité du Médicament et des produits de santé, add a duty to contact the reporter a second time if the first attempt of contact was unsuccessful [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Description of the process for documenting spontaneous notifications of adverse drug events.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e65651_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>MyGenAssist was added to this process at the stage of drafting documentation letters. This LLM was used to write a first draft of the letters, which was then reviewed and modified if needed by the pharmacovigilance officer.</p>
        </sec>
        <sec>
          <title>Software and Applications Used</title>
          <p>MyGenAssist is an LLM internal to Bayer based on the technology of ChatGPT-4 Turbo (OpenAI), a conversational agent based on generative AI [<xref ref-type="bibr" rid="ref21">21</xref>]. The model used here has no differences compared to the one available to the public, apart from the fact that MyGenAssist is securely hosted by Bayer. All manipulations performed on this internal LLM can be reproduced on ChatGPT, which is accessible to the public on the web. Here, MyGenAssist was used by ourselves as final users; the prompt was created without any fine-tuning or modification of its algorithm.</p>
          <p>Pharmacovigilance cases reported to Bayer are compiled on an internal pharmacovigilance database supported by the Argus pharmacovigilance case management software developed by Oracle [<xref ref-type="bibr" rid="ref22">22</xref>]. This software assigns a specific reference to each case. It contains all documents related to the case as well as information regarding the actions taken to analyze the case, such as attempts to contact the reporter.</p>
          <p>The questions formulated by the case evaluators following their analysis of the case are listed on the FAST application (Bayer internal application). The pharmacovigilance officer can select the relevant questions and add others if needed.</p>
        </sec>
        <sec>
          <title>Use of MyGenAssist for the Activity</title>
          <p>Pharmacovigilance case documentation letters were written according to templates validated by an internal process. Two templates exist depending on the type of recipient (patients or health care professionals). The pharmacovigilance officer could adapt the template in function of the pharmacovigilance case. To make the LLM predraft the pharmacovigilance case documentation letters, the 2 templates were used. The elements of the templates corresponding to information specific to each case were replaced by titles placed into brackets in the letter templates. These 2 letter templates were then provided via the following prompt as shown in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> (original version in French; the translation corresponds to <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>, an example of a query is shown in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>, and its translation is shown in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>).</p>
        </sec>
      </sec>
      <sec>
        <title>Staff Training</title>
        <p>To train staff to use MyGenAssist specifically for this activity, a training session was planned before initiating its use. The earlier-described operating mode was given to the pharmacovigilance officers. A training phase was also planned to verify their good understanding of the use of the tool. The operating procedure was also formalized for the use of potential new arrivals. To allow pharmacovigilance officers to report any difficulties or suggestions for improvement regarding the operating procedure, meetings were scheduled every other week until the termination of the study.</p>
      </sec>
      <sec>
        <title>Data Collection</title>
        <p>The study was conducted between January 2 and May 3, 2024. The time spent on each case was measured from the moment the pharmacovigilance case was acknowledged until the letter was sent and the Argus database was filled out.</p>
        <p>Over an initial period of 9 weeks, the time spent on drafting each documentation letter, without the use of MyGenAssist, was measured. Over a second equivalent period, the time spent on the same task, but using the LLM as a drafting aid, was also measured. During the 2 periods, apart from the addition of MyGenAssist, no significant changes in the management of the activity took place: 3 workers, including 2 experimented participants and a newcomer were present throughout the 4 months of the study, and the process did not undergo any notable modifications.</p>
      </sec>
      <sec>
        <title>Statistical Analysis</title>
        <sec>
          <title>Calculation of Time Savings</title>
          <p>To determine the average time saved for each case thanks to MyGenAssist, a multiple linear regression was performed, in which the explained variable or outcome was the time spent per case. To highlight the impact of MyGenAssist, the parameters that could potentially influence the time spent per case were researched and selected on the basis of a review of the pharmacovigilance documentation process with experienced pharmacovigilance officers who defined, based on their daily practice, which elements could weigh on the time spent. Because of the company’s specificities in the pharmacovigilance documentation process, the judgment of pharmacovigilance officers was then the unique criteria to add these parameters to the model. Among them, all parameters that could be modelized were included in the regression model as independent or explanatory variables (<xref rid="figure2" ref-type="fig">Figure 2</xref>):</p>
          <p><italic>Y</italic>=<italic>a</italic><sub>1</sub><italic>X</italic><sub>1</sub>+<italic>a</italic><sub>2</sub><italic>X</italic><sub>2</sub>+<italic>a</italic><sub>3</sub><italic>X</italic><sub>3</sub>+<italic>a</italic><sub>4</sub><italic>X</italic><sub>4</sub>+<italic>a</italic><sub>5</sub><italic>X</italic><sub>5</sub>+<italic>b</italic></p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Causal diagram of factors potentially impacting the time spent on the activity, built with Dagitty software (version 3.1).</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e65651_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p><italic>Y</italic> is the time spent per case (continuous quantitative variable, expressed in minutes). <italic>X</italic><sub>1</sub> is the use of MyGenAssist (dichotomous categorical variable: use or no use). <italic>X</italic><sub>2</sub> is the type of recipient (dichotomous categorical variable: patient or health care professional). The letter template differs significantly depending on this parameter. It may also be necessary to simplify the questions contained in the letter for patients, leading to more time spent on the task. <italic>X</italic><sub>3</sub> is the number of questions formulated by the case evaluator (discrete quantitative variable). This parameter can also impact the time spent. Each question is asked in English. Without the use of MyGenAssist, a French translation is automatically provided by the internal software FAST, but the translations need to be reviewed and the questions sometimes need to be adapted according to the recipient. This adaptation is a step in the workflow whose duration could be correlated to the number of questions. When using MyGenAssist, this latter also provides a translation of the questions, but some adaptation work is still necessary. <italic>X</italic><sub>4</sub> is the number of questions added or removed by the pharmacovigilance officer (discrete quantitative variable). The pharmacovigilance officer has the option to remove questions prepared by the case evaluator considering them irrelevant in the context of the case. Conversely, this latter can also add questions to obtain information considered as necessary. Adding questions or considering the removal of questions from the case processor leads to additional reflection time that can impact the overall duration of the task. <italic>X</italic><sub>5</sub> is the user (categorical variable: user 1, 2, or 3). The user was taken into account. The personal characteristics of the user will influence the time spent on the task. <italic>a</italic><sub>1</sub>, <italic>a</italic><sub>2</sub>, <italic>a</italic><sub>3</sub>, <italic>a</italic><sub>4</sub>, and <italic>a</italic><sub>5</sub> are, respectively, the coefficients of the variables <italic>X</italic><sub>1</sub>, <italic>X</italic><sub>2</sub>, <italic>X</italic><sub>3</sub>, <italic>X</italic><sub>4</sub>, and <italic>X</italic><sub>5</sub>, and <italic>b</italic> is the intercept. Three parameters in this causal diagram were not included in the model because they cannot be measured: the experience in the activity, the electronic literacy of the user, and the complexity of the case.</p>
          <p>The multiple linear regression was performed using the R software (R Foundation for Statistical Computing) with the “lm” function, which can be found in the <italic>stats</italic> package (all R equations used in this study are described in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>). The outliers were researched thanks to the function “check_outliers” from the <italic>performance</italic> package [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
          <p>The linear regression was completed with a hierarchical regression to study the relevance of the independent variables in the model. It was performed with the function “stepAIC” from the package <italic>mass</italic> [<xref ref-type="bibr" rid="ref24">24</xref>] on R. The hierarchical regression is a backward stepwise Akaike information criterion.</p>
          <p>Cases were randomly distributed among the pharmacovigilance officers without considering the context of the case, the type of recipient, and the number of questions a priori. The number of questions formulated was not related to the type of recipient.</p>
        </sec>
        <sec>
          <title>Measurement of Effectiveness</title>
          <p>The reliability of the LLM was not studied because the use of MyGenAssist was intended only as an aid in drafting documentation letters. However, a measure of the effectiveness of the task with or without the tool was carried out. For this, a comparison of the proportion of cases for which a response from the recipient was obtained after the first and the second contact attempt was made, depending on whether MyGenAssist was used or not. A subgroup analysis was also realized in function of the type of recipient (physician or patient). The comparison was made on R thanks to the “chisq.test” function that can be found in the <italic>stats</italic> package. In the subgroup analysis, the same comparison was done but specifically for cases whose recipient was a physician on one hand, and on the other hand, for cases whose recipient was a patient.</p>
        </sec>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study was not considered as being related to human research in health, as it clearly focused on evaluating work performance with or without an AI-based tool. Regulations in France require such studies to be in compliance with the General Data Protection Regulation (ie, European Regulation 2016/679) [<xref ref-type="bibr" rid="ref25">25</xref>]. The data used in this study were retrieved first during the normal course of the pharmacovigilance activities and reused for the study as authorized by General Data Protection Regulation [<xref ref-type="bibr" rid="ref25">25</xref>] and after having received oral consent from pharmacovigilance workers who were informed of the objective of the study and how the data will be used.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Statistical Study</title>
        <p>The study included 122 cases (48 without the use of MyGenAssist and 74 with its use). The average time spent on each case was 19.05 (SD 6.05; 95% CI 17.97-20.12) minutes. The average time for cases handled was 22.25 (SD 7.62; 95% CI 20.09-24.41) minutes without the use of MyGenAssist and 16.97 (SD 3.50; 95% CI 16.17-17.77) minutes when the LLM was used (<xref rid="figure3" ref-type="fig">Figure 3</xref>). When all factors that potentially impact the time spent on the activity are taken into account in a multiple linear regression model, an average of 23.3% (95% CI 13.8%-32.8%; <italic>P</italic>&#60;.001) of time savings were realized for each case thanks to MyGenAssist (adjusted <italic>R</italic><sup>2</sup>=0.286; <italic>df</italic>=115; <xref rid="figure4" ref-type="fig">Figure 4</xref>). All explanatory variables of the linear regression model got a <italic>P</italic> value inferior to .05 apart from the number of questions added or removed by the pharmacovigilance officer (<italic>P</italic>=.05).</p>
        <p>The hierarchical regression performed found that all the parameters used as explanatory variables were useful to get the best model (the lowest Akaike information criterion is obtained with all the parameters included in the model; <xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Time spent on each case in function of the use of MyGenAssist.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e65651_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Influence of explanatory variables on the time spent on a case. A logarithmic transformation was performed to fulfill the conditions of the linear regression model (the actual model is log <italic>t</italic>=a1X1+a2X2+a3X3+a4X4+a5X5+b). “log T” is the logarithmic transformation of the variable T; hence, the result obtained is a percentage of difference of time in function of each parameter.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e65651_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Akaike information criterion (AIC) of the multilinear regression model in function of the parameters used.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="400"/>
            <col width="100"/>
            <col width="180"/>
            <col width="220"/>
            <col width="100"/>
            <thead>
              <tr valign="top">
                <td>Parameters included</td>
                <td>
                  <italic>df</italic>
                </td>
                <td>Sum of squares</td>
                <td>Residual sum of squares</td>
                <td>AIC</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>All</td>
                <td>—<sup>a</sup></td>
                <td>—</td>
                <td>7.0929</td>
                <td>–333.08</td>
              </tr>
              <tr valign="top">
                <td>Variable “number of questions added or removed by the pharmacovigilance officer” removed</td>
                <td>1</td>
                <td>0.23076</td>
                <td>7.3237</td>
                <td>–331.17</td>
              </tr>
              <tr valign="top">
                <td>Variable “type of recipient” removed</td>
                <td>1</td>
                <td>0.30945</td>
                <td>7.4024</td>
                <td>–329.87</td>
              </tr>
              <tr valign="top">
                <td>Variable “user” removed</td>
                <td>2</td>
                <td>0.44116</td>
                <td>7.5341</td>
                <td>–329.72</td>
              </tr>
              <tr valign="top">
                <td>Variable “number of questions formulated by the case evaluator” removed</td>
                <td>1</td>
                <td>0.48239</td>
                <td>7.5753</td>
                <td>–327.05</td>
              </tr>
              <tr valign="top">
                <td>Variable “use of MyGenAssist” removed</td>
                <td>1</td>
                <td>1.45757</td>
                <td>8.5505</td>
                <td>–312.28</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>According to the number of spontaneous pharmacovigilance reports for which a documentation request was necessary during the last 3 years, it can be estimated that the mean time saved on the activity with the use of the LLM could be between 66.27 (SD 22.79) and 108.70 (SD 37.23) hours per year, on the basis of an average 23.3% time saved on the average 22.25 (SD 7.62) minutes spent on a case without the use of MyGenAssist. Based on a working day of 8 hours, the use of MyGenAssist for this activity in the 3 previous years could have saved an average of 10.7 (SD 3.6) days of work per year (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Potential time saved on the pharmacovigilance case documentation process each year with the use of MyGenAssist.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="60"/>
            <col width="260"/>
            <col width="170"/>
            <col width="170"/>
            <col width="170"/>
            <col width="170"/>
            <thead>
              <tr valign="top">
                <td>Year</td>
                <td>Pharmacovigilance cases requiring documentation request, n</td>
                <td colspan="2">Potential time saved (hours)</td>
                <td colspan="2">Potential time saved (working days)<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Mean (SD)</td>
                <td>95% CI</td>
                <td>Mean (SD)</td>
                <td>95% CI</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>2021</td>
                <td>1258</td>
                <td>108.70 (37.23)</td>
                <td>98.16-119.23</td>
                <td>13.6 (4.7)</td>
                <td>12.3-14.9</td>
              </tr>
              <tr valign="top">
                <td>2022</td>
                <td>947</td>
                <td>81.82 (28.02)</td>
                <td>73.89-89.75</td>
                <td>10.2 (3.5)</td>
                <td>9.2-11.2</td>
              </tr>
              <tr valign="top">
                <td>2023</td>
                <td>767</td>
                <td>66.27 (22.79)</td>
                <td>60.12-72.72</td>
                <td>8.3 (2.8)</td>
                <td>7.5-9.1</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>A working day is considered to last 8 hours.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>No statistical difference has been found regarding the answers’ rates after 1 attempt of contact, whether MyGenAssist was used or not: 31% (15/48) of letters produced without MyGenAssist were provided with an answer and 24% (18/74) when the generative AI was used for the writing (<italic>P</italic>=.40; <italic>χ</italic><sup>2</sup><sub>1</sub>=0.7). The same situation occurred after 2 attempts: 42% (20/48) without the tool vs 36% (27/74; <italic>P</italic>=.57; <italic>χ</italic><sup>2</sup><sub>1</sub>=0.3). In a subgroup analysis in function of the type of recipient, these results were consistent (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Rates of answers to letters sent for pharmacovigilance case documentation in function of the use of MyGenAssist and the type of recipient.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="130"/>
            <col width="330"/>
            <col width="320"/>
            <col width="80"/>
            <col width="140"/>
            <thead>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Without the use of MyGenAssist, n/N (%)</td>
                <td>With the use of MyGenAssist, n/N (%)</td>
                <td><italic>P</italic> value</td>
                <td>Chi-square (<italic>df</italic>=1)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Total</td>
                <td>20/48 (42)</td>
                <td>27/74 (36)</td>
                <td>.57</td>
                <td>0.3</td>
              </tr>
              <tr valign="top">
                <td>Physicians</td>
                <td>14/29 (48)</td>
                <td>15/45 (33)</td>
                <td>.20</td>
                <td>1.6</td>
              </tr>
              <tr valign="top">
                <td>Patients</td>
                <td>6/19 (32)</td>
                <td>12/29 (41)</td>
                <td>.49</td>
                <td>0.5</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In cases for which an answer is provided, the average time between the answer and the last attempt of contact does not differ significantly (<xref rid="figure5" ref-type="fig">Figure 5</xref>): 2.20 (SD 3.27; 95% CI 1.27-3.13) days when the letter was written without MyGenAssist and 2.65 (SD 3.30; 95% CI 1.90-3.41) days with its use (<italic>P</italic>=.64; t<sub>44</sub>=–0.46).</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Comparison of the duration time between the answer and the last attempt of contact in function of the use of MyGenAssist.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e65651_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Staff Meetings</title>
        <p>Before the study, a 2-hour training was planned to present the use of MyGenAssist in the pharmacovigilance case documentation process to the pharmacovigilance officers. During the study, meetings were planned in the team on a 2-week basis. No difficulties in the use of MyGenAssist were identified, and users only suggested slight improvements in the prompt used to consider specific cases for which additional elements are required in the letter. An operating mode, detailing all the steps required to use MyGenAssist for the activity, was written to offer a reminder for the users if necessary.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Main Results</title>
        <p>In this study, we demonstrated that the implementation of MyGenAssist to the pharmacovigilance case documentation process provided an average of 23.3% time saving on the task without any modification in the rate of answers. Whatever the experience of the workers, the use of MyGenAssist induces time savings, although this effect is higher in nonexperimented ones. Moreover, while using MyGenAssist, it seems that the time spent on the different pharmacovigilance cases becomes less variable: when the use of the tool is added to the process, the range of time is decreased from 9-38 minutes to 10-25 minutes. MyGenAssist may have a more beneficial impact in cases for which more time is required. The easiest cases needing a slight amount of time to be handled would benefit less (or not) from its use, but the ones that are the more time-consuming would be realized significantly quicker than without it.</p>
        <p>Therefore, the use of Bayer’s LLM improved the efficiency of this activity. That must save dozens of hours yearly for our local pharmacovigilance team, which could be dedicated to other activities with higher added value. A unique, short, and reachable training was sufficient to implement the use of MyGenAssist. This consisted of introducing the changes in the tool’s operating mode to the users. No additional training content was required to enable them to use the LLM in the activity, though they did not have any specific qualifications or skills in informatics. Hence, we showed in this study that making workers use an LLM could be easy, as far as they are assisted at the beginning, while other AI tools require important training to be used daily. However, the daily use of an LLM can make the user continually improve their abilities with this tool. Therefore, LLMs seem easy to integrate into several work environments and a way for the worker to get new skills without needing a large amount of time. Thanks to its ease, all users kept using the generative AI for their activity after the end of the study.</p>
        <p>Although we included in the linear regression model all parameters that could have an influence on the time spent on the activity, in our point of view, the adjusted <italic>R</italic><sup>2</sup> is low (0.286). Therefore, the most part of the time spent on each case could not be fully explained by the considered parameters. It seems that some aspects that are specific to each and difficult to transcribe in the model are important factors too. Moreover, a “human factor” could play a role here, as the user could spend a variable duration of time for the same task, in function of a lot of exterior parameters. Whatever explanatory variable was not included here, the average difference created by MyGenAssist (more than 5 minutes on a task requiring about 22 minutes without its use) seems too high to be questioned by these potential “hidden” parameters.</p>
        <p>Nonetheless, 3 factors could not be included in the model. First, the experience of the user in the activity may directly influence the time spent on each case. It could also have an effect on the number of questions added or removed by the pharmacovigilance officer: while a newcomer could have difficulties selecting the required information to request from the recipient, an experienced one would more accurately determine which question is important enough to assess an adverse event. Second, electronic literacy, which is the capacity to understand or create messages using electronic means, may have an influence on the time spent on the activity. This impact exists for all cases because they are handled by using informatics, but must be stronger in the cases for which MyGenAssist would be used, as the ability of the user to handle technology could also impact their ease of familiarizing themselves with this new tool. By the time we started this experiment, we were not able to measure either user experience or user electronic literacy [<xref ref-type="bibr" rid="ref26">26</xref>]. Even if we could not include them in the model, the variable “user” integrates both their experience and their electronic literacy: so, without deciphering which parameter has more impact, we still take them into account. Third, the complexity of the case, which may have an influence on the time spent on the case, is a subjective parameter that could not be measured accurately. The parameters we chose to include in this study were selected during a meeting with experienced pharmacovigilance officers, who were asked to give all factors that could influence the time spent on each case. It seems that no study so far, to the best of our knowledge, has been published reporting the parameters influencing the time spent to document a pharmacovigilance case. Moreover, no comparison of our internal process and the ones of other pharmaceutical companies could be done, as none of them seems to be available publicly. The European GVPs [<xref ref-type="bibr" rid="ref17">17</xref>] do not define a strict process for the documentation of pharmacovigilance cases and let the market authorization holders organize the activity. Pharmaceutical companies have to create a Pharmacovigilance System Master File that describes the handling of all pharmacovigilance activities. It has to be sent to the national and European health authorities but is not publicly disclosed [<xref ref-type="bibr" rid="ref27">27</xref>]. Our process could then have specificities (eg, the implication of both a case evaluator and a pharmacovigilance officer) that are not possible to detect and could create a lack of reproducibility of our study.</p>
        <p>Other ways could have been explored to determine the effectiveness of generative AI. In this study, we chose to use the fulfillment of the objective of our task as the main criteria of effectiveness: to get the necessary information to analyze the pharmacovigilance case. From our perspective, other criteria did not seem relevant in this context. Moreover, we made the choice not to analyze the quality of the drafts written by MyGenAssist because it was clear in our operating mode and in the training that a human assessment of the letter was mandatory before sending it out. To get a relevant analysis of the effectiveness, recipients were not informed that the letter they received was first written with the help of an LLM: on the one hand, the recipient could have had the impression that its report was “automatically” handled, which could have encouraged this latter not to answer. On the other hand, the potential curiosity created by an eventual mention of generative AI, in a current era in which all eyes are turned to such tools, could have created a bias by making the recipient more willing to answer.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>While our study was realized over a 4-month period, this latter only includes 122 cases. Even if it was enough to notice a difference in the time spent in function of the use of the tool, this has to be taken into account, particularly while analyzing the answers’ rate. However, this study is a first step before the extension of the use of the LLM in the pharmacovigilance case documentation process to all Bayer local pharmacovigilance teams worldwide. The efficiency improvement noticed by the French pharmacovigilance team could give fresh impetus to make other teams adopt the same principle. This will give us the opportunity to retrieve more data concerning our question.</p>
      </sec>
      <sec>
        <title>Comparison to Prior Work</title>
        <p>Other publications regard the use of LLMs in pharmacovigilance: the use of ChatGPT without any optimization or fine-tuning of the public does not seem to fulfill the objective fixed, whatever this latter is providing answers to pharmacovigilance-related questions [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] or assess the risk of mortality of patients with toxic epidermal necrolysis [<xref ref-type="bibr" rid="ref30">30</xref>]. On the other hand, another LLM, Bidirectional Encoder Representations from Transformers, was used with success for the extraction of adverse events from notes [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] or social media [<xref ref-type="bibr" rid="ref33">33</xref>], but it always implied a step of fine-tuning that could not be handled by a simple user. Therefore, we could not find in the literature any study describing the successful use of ChatGPT or a strict equivalent in pharmacovigilance without the necessity to fine-tune the LLM after its use.</p>
        <p>Moreover, the need to explore the possibilities that AI could offer to pharmacovigilance was highlighted by several publications before, particularly with the idea that the implementation of such tools could make both time and cost savings and provide an efficiency improvement, especially as the number of declarations of adverse events has been sharply increasing in the last few years [<xref ref-type="bibr" rid="ref34">34</xref>]. Gholap et al [<xref ref-type="bibr" rid="ref35">35</xref>] and Danysz et al [<xref ref-type="bibr" rid="ref36">36</xref>] evoke the possibility for pharmacovigilance workers to focus on high-level tasks thanks to these time savings on administrative or repetitive tasks. However, in all these papers, these statements remain at the step of hypothesis without any experimental assessment.</p>
        <p>Regarding the potential benefits that AI could represent for pharmacovigilance, the TransCelerate initiative, which includes 19 pharmaceutical companies, aimed to ask pharmacovigilance representatives of these companies which steps of the pharmacovigilance case processing might be the best suited for a pharmacovigilance implementation. In 2 surveys set between 2018 [<xref ref-type="bibr" rid="ref37">37</xref>] and 2021 [<xref ref-type="bibr" rid="ref38">38</xref>], the pharmacovigilance workers considered the pharmacovigilance case documentation process as one of the more appropriate steps for an AI implementation. The automation opportunity score, which combines the effort realized by companies to include AI in the task and the benefit or risk assessment regarding this inclusion, was 4.5/5 in 2021. The percentage of companies that set an AI-based process in this task rose from 19% to 35% between 2020 and 2021. Nonetheless, no information was given in these publications about a possible efficiency increase after an AI implementation.</p>
        <p>Hence, our study may fulfill what seems to be, to the best of our knowledge, a lack in the medical literature. Descriptions of LLMs’ use cases for pharmacovigilance exist, but none of them include a measure of time saving realized thanks to this tool. A study showed that the use of ChatGPT for writing tasks enhanced the productivity of the workers by decreasing the time required by 40%, while the quality rose by 18% [<xref ref-type="bibr" rid="ref39">39</xref>], but did not concern health. Hence, our objective was to determine if the integration of the LLM in the adverse event case documentation process can improve efficiency by reducing the time required for this GVP-related task without decreasing the response rate from the reporters.</p>
        <p>These first encouraging results could be an incentive to implement MyGenAssist in other processes. In the pharmacovigilance field, some tasks fit well with the integration of MyGenAssist. For example, the comparison of different versions of the same procedure with this tool can provide a rapid insight into the modifications in order in a second step to assess their impact on other quality documents. Other use cases could be found in other departments, as the task given to the LLM, which is writing letters based on a template, seems pretty reproducible in other contexts for different objectives. The results of this study show that using LLMs in pharmaceutical activities, whatever the field, is relevant and can create improvements without losing quality concerning the regulations of good practice activities.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this study, we showed the first example of a use case for a ChatGPT-based tool, MyGenAssist, in a pharmacovigilance industry department and assessed its efficiency over a 4-month period. An average of 23.3% of time savings was achieved thanks to this LLM, while its implementation did not modify the effectiveness of the task. It only required a short training to be set up. These results could be the first step to the largest use of LLMs in pharmaceutical activities.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Original prompt used in French.</p>
        <media xlink:href="jmir_v27i1e65651_app1.png" xlink:title="PNG File , 156 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Translation of the prompt used in English.</p>
        <media xlink:href="jmir_v27i1e65651_app2.png" xlink:title="PNG File , 195 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Example of a query by the user and output generated by MyGenAssist in French.</p>
        <media xlink:href="jmir_v27i1e65651_app3.png" xlink:title="PNG File , 325 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Translation in  English of an example of a query by the user and output generated by MyGenAssist.</p>
        <media xlink:href="jmir_v27i1e65651_app4.png" xlink:title="PNG File , 417 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Description of the R equations used in the paper.</p>
        <media xlink:href="jmir_v27i1e65651_app5.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">GVP</term>
          <def>
            <p>good pharmacovigilance practices</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors thank all members of the Bayer French local pharmacovigilance team for their kind help and their implication in the study, French Bayer IA champions for the mutual sharing of tips, and Bayer AG for its funding support. No specific funding was necessary or used for this study. Bayer AG provided the authors, who are part of the company, with the usual support provided to their employees. MyGenAssist, ChatGPT, or any other large language models were not used for the writing of our paper.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The datasets generated or analyzed during this study are not publicly available due to our internal data privacy policies, but specific elements are available from the corresponding author on reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>Conceptualization and elaboration of the methodology were realized by all authors collectively. Data curation, formal analysis, investigation, project administration, creation of the prompt, and the writing of the original draft were made by AB. The review and editing of the paper were carried out by IB-L, HR, and JPB. IB-L and JPB were in charge of the supervision and validation. Visualization was done by AB, IB-L, and JPB.</p>
      </fn>
      <fn fn-type="conflict">
        <p>AB, IB-L, and HR were employees of the company (Bayer) at the time this study was performed. Bayer was informed of this study but was not involved in the design of the study or the writing of the manuscript. Bayer gave authorization to the authors to use MyGenAssist for this study.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>ICUREsearch</article-title>
          <source>DEEPCATH: artificial intelligence for the detection of local signs of infections around catheters</source>
          <access-date>2024-06-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://icrs.fr/en/ai/deepcath/">https://icrs.fr/en/ai/deepcath/</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>Paul</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sanap</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Shenoy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kalyane</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kalia</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tekade</surname>
              <given-names>RK</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in drug discovery and development</article-title>
          <source>Drug Discov Today</source>
          <year>2021</year>
          <month>01</month>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>80</fpage>
          <lpage>93</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33099022"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.drudis.2020.10.010</pub-id>
          <pub-id pub-id-type="medline">33099022</pub-id>
          <pub-id pub-id-type="pii">S1359-6446(20)30425-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7577280</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mondal</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Panigrahi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Behera</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Mondal</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A pilot study on the capability of artificial intelligence in preparation of patients' educational materials for Indian public health issues</article-title>
          <source>J Family Med Prim Care</source>
          <year>2023</year>
          <month>08</month>
          <volume>12</volume>
          <issue>8</issue>
          <fpage>1659</fpage>
          <lpage>1662</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37767452"/>
          </comment>
          <pub-id pub-id-type="doi">10.4103/jfmpc.jfmpc_262_23</pub-id>
          <pub-id pub-id-type="medline">37767452</pub-id>
          <pub-id pub-id-type="pii">JFMPC-12-1659</pub-id>
          <pub-id pub-id-type="pmcid">PMC10521817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cova</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vitorino</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nunes</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rondon-Villarreal</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pais</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and quantum computing as the next pharma disruptors</article-title>
          <source>Methods Mol Biol</source>
          <year>2022</year>
          <volume>2390</volume>
          <fpage>321</fpage>
          <lpage>347</lpage>
          <pub-id pub-id-type="doi">10.1007/978-1-0716-1787-8_14</pub-id>
          <pub-id pub-id-type="medline">34731476</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lamberti</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Donzanti</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Wohlhieter</surname>
              <given-names>GE</given-names>
            </name>
            <name name-style="western">
              <surname>Parikh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkins</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Getz</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A study on the application and use of artificial intelligence to support drug development</article-title>
          <source>Clin Ther</source>
          <year>2019</year>
          <month>08</month>
          <volume>41</volume>
          <issue>8</issue>
          <fpage>1414</fpage>
          <lpage>1426</lpage>
          <pub-id pub-id-type="doi">10.1016/j.clinthera.2019.05.018</pub-id>
          <pub-id pub-id-type="medline">31248680</pub-id>
          <pub-id pub-id-type="pii">S0149-2918(19)30294-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Payra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>SK</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and machine learning in pharmacological research: bridging the gap between data and drug discovery</article-title>
          <source>Cureus</source>
          <year>2023</year>
          <month>08</month>
          <volume>15</volume>
          <issue>8</issue>
          <fpage>e44359</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37779744"/>
          </comment>
          <pub-id pub-id-type="doi">10.7759/cureus.44359</pub-id>
          <pub-id pub-id-type="medline">37779744</pub-id>
          <pub-id pub-id-type="pmcid">PMC10539991</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>Adamson</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Waskom</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Blarre</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Krismer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Nemeth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gippetti</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ritten</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Harrison</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ho</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Linzmayer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bansal</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Amster</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Estola</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Benedum</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Fidyk</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Estévez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shapiro</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>AB</given-names>
            </name>
          </person-group>
          <article-title>Approach to machine learning for extraction of real-world data variables from electronic health records</article-title>
          <source>Front Pharmacol</source>
          <year>2023</year>
          <month>9</month>
          <day>15</day>
          <volume>14</volume>
          <fpage>1180962</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37781703"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fphar.2023.1180962</pub-id>
          <pub-id pub-id-type="medline">37781703</pub-id>
          <pub-id pub-id-type="pii">1180962</pub-id>
          <pub-id pub-id-type="pmcid">PMC10541019</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>Banerji</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lai</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Saff</surname>
              <given-names>RR</given-names>
            </name>
            <name name-style="western">
              <surname>Camargo</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Blumenthal</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Natural language processing combined with ICD-9-CM codes as a novel method to study the epidemiology of allergic drug reactions</article-title>
          <source>J Allergy Clin Immunol Pract</source>
          <year>2020</year>
          <month>03</month>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>1032</fpage>
          <lpage>1038.e1</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31857264"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jaip.2019.12.007</pub-id>
          <pub-id pub-id-type="medline">31857264</pub-id>
          <pub-id pub-id-type="pii">S2213-2198(19)31028-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7064405</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>Gupta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katarya</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>PAN-LDA: A latent Dirichlet allocation based novel feature extraction model for COVID-19 data using machine learning</article-title>
          <source>Comput Biol Med</source>
          <year>2021</year>
          <month>11</month>
          <volume>138</volume>
          <fpage>104920</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34655902"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2021.104920</pub-id>
          <pub-id pub-id-type="medline">34655902</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(21)00714-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC8505021</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>Chen</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>ZC</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>FIR: an effective scheme for extracting useful metadata from social media</article-title>
          <source>J Med Syst</source>
          <year>2015</year>
          <month>11</month>
          <volume>39</volume>
          <issue>11</issue>
          <fpage>139</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-015-0333-0</pub-id>
          <pub-id pub-id-type="medline">26330225</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>Hasan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Levene</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weston</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Learning structured medical information from social media</article-title>
          <source>J Biomed Inform</source>
          <year>2020</year>
          <month>10</month>
          <volume>110</volume>
          <fpage>103568</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(20)30198-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2020.103568</pub-id>
          <pub-id pub-id-type="medline">32942027</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(20)30198-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <source>OpenAI Platform</source>
          <access-date>2024-03-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://platform.openai.com">https://platform.openai.com</ext-link>
          </comment>
        </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>Abu Hammour</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Alhamad</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Ashwal</surname>
              <given-names>F Y</given-names>
            </name>
            <name name-style="western">
              <surname>Halboup</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abu Farha</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Abu Hammour</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT in pharmacy practice: a cross-sectional exploration of Jordanian pharmacists' perception, practice, and concerns</article-title>
          <source>J Pharm Policy Pract</source>
          <year>2023</year>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>129</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1186/s40545-023-00640-2?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40545-023-00640-2</pub-id>
          <pub-id pub-id-type="medline">37789443</pub-id>
          <pub-id pub-id-type="pii">10.1186/s40545-023-00640-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC10614371</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>Abu-Farha</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fino</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Ashwal</surname>
              <given-names>FY</given-names>
            </name>
            <name name-style="western">
              <surname>Zawiah</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gharaibeh</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Harahsheh</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Darwish Elhajji</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of community pharmacists’ perceptions and willingness to integrate ChatGPT into their pharmacy practice: a study from Jordan</article-title>
          <source>J Am Pharm Assoc</source>
          <year>2023</year>
          <month>11</month>
          <volume>63</volume>
          <issue>6</issue>
          <fpage>1761</fpage>
          <lpage>1767.e2</lpage>
          <pub-id pub-id-type="doi">10.1016/j.japh.2023.08.020</pub-id>
          <pub-id pub-id-type="medline">37648157</pub-id>
          <pub-id pub-id-type="pii">S1544-3191(23)00291-1</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>Temsah</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Aljamaan</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Malki</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Alhasan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Altamimi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Aljarbou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bazuhair</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Alsubaihin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abdulmajeed</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alshahrani</surname>
              <given-names>FS</given-names>
            </name>
            <name name-style="western">
              <surname>Temsah</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Alshahrani</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Eyadhy</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Alkhateeb</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Saddik</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Halwani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jamal</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Tawfiq</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Eyadhy</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT and the future of digital health: a study on healthcare workers' perceptions and expectations</article-title>
          <source>Healthcare (Basel)</source>
          <year>2023</year>
          <month>06</month>
          <day>21</day>
          <volume>11</volume>
          <issue>13</issue>
          <fpage>1812</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare11131812"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare11131812</pub-id>
          <pub-id pub-id-type="medline">37444647</pub-id>
          <pub-id pub-id-type="pii">healthcare11131812</pub-id>
          <pub-id pub-id-type="pmcid">PMC10340744</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ray</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Samsung bans ChatGPT among employees after sensitive code leak</article-title>
          <source>Forbes</source>
          <year>2023</year>
          <month>05</month>
          <day>02</day>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.forbes.com/sites/siladityaray/2023/05/02/samsung-bans-chatgpt-and-other-chatbots-for-employees-after-sensitive-code-leak/">https://www.forbes.com/sites/siladityaray/2023/05/02/samsung-bans-chatgpt-and-other-chatbots-for-employees-after-sensitive-code-leak/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>Guideline on good pharmacovigilance practices (GVP): Module VI—collection, management and submission of reports of suspected adverse reactions to medicinal products (Rev 2)</article-title>
          <source>European Medicines Agency</source>
          <access-date>2024-03-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/guideline-good-pharmacovigilance-practices-gvp-module-vi-collection-management-and-submission-reports-suspected-adverse-reactions-medicinal-products-rev-2_en.pdf">https://tinyurl.com/48zjc968</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Bonnes pratiques de pharmacovigilance</article-title>
          <source>Agence Nationale de Sécurité du Médicament et des produits de santé</source>
          <access-date>2024-03-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ansm.sante.fr/documents/reference/bonnes-pratiques-de-pharmacovigilance">https://ansm.sante.fr/documents/reference/bonnes-pratiques-de-pharmacovigilance</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>Directive 2001/83/EC of the European Parliament and of the Council of 6 November 2001 on the Community code relating to medicinal products for human use, vol 311</article-title>
          <source>European Union</source>
          <year>2001</year>
          <access-date>2024-06-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://data.europa.eu/eli/dir/2001/83/oj/eng">http://data.europa.eu/eli/dir/2001/83/oj/eng</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pariente</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Micallef</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lahouegue</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Molimard</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Auffret</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chouchana</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Denis</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Faillie</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Grandvuillemin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Letinier</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Pierron</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Pons</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pujade</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Rubino</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Salvo</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>What place for intelligent automation and artificial intelligence to preserve and strengthen vigilance expertise in the face of increasing declarations</article-title>
          <source>Therapies</source>
          <year>2023</year>
          <month>01</month>
          <volume>78</volume>
          <issue>1</issue>
          <fpage>131</fpage>
          <lpage>143</lpage>
          <pub-id pub-id-type="doi">10.1016/j.therap.2022.11.004</pub-id>
          <pub-id pub-id-type="medline">36572627</pub-id>
          <pub-id pub-id-type="pii">S0040-5957(22)00267-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <article-title>Best practices for prompt engineering with the OpenAI API</article-title>
          <source>OpenAI</source>
          <access-date>2024-04-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://help.openai.com/en/articles/6654000-best-practices-for-prompt-engineering-with-the-openai-api">https://help.openai.com/en/articles/6654000-best-practices-for-prompt-engineering-with-the-openai-api</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Argus database</article-title>
          <source>Oracle</source>
          <access-date>2024-03-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oracle.com/life-sciences/pharmacovigilance/argus-safety-case-management/">https://www.oracle.com/life-sciences/pharmacovigilance/argus-safety-case-management/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lüdecke</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ben-Shachar</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Patil</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Waggoner</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Makowski</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>performance: an R package for assessment, comparison and testing of statistical models</article-title>
          <source>JOSS</source>
          <year>2021</year>
          <month>04</month>
          <volume>6</volume>
          <issue>60</issue>
          <fpage>3139</fpage>
          <pub-id pub-id-type="doi">10.21105/joss.03139</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Venables</surname>
              <given-names>WN</given-names>
            </name>
            <name name-style="western">
              <surname>Ripley</surname>
              <given-names>BD</given-names>
            </name>
          </person-group>
          <article-title>Modern applied statistics with S</article-title>
          <source>Statistics and Computing. 4th Edition</source>
          <year>2002</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (text with EEA relevance), vol 119</article-title>
          <source>European Union</source>
          <year>2016</year>
          <access-date>2024-12-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://data.europa.eu/eli/reg/2016/679/oj/eng">http://data.europa.eu/eli/reg/2016/679/oj/eng</ext-link>
          </comment>
        </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>Marsall</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Engelmann</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Skoda</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Teufel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bäuerle</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Measuring electronic health literacy: development, validation, and test of measurement invariance of a revised German version of the eHealth literacy scale</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>02</month>
          <day>02</day>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>e28252</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/2/e28252/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/28252</pub-id>
          <pub-id pub-id-type="medline">35107437</pub-id>
          <pub-id pub-id-type="pii">v24i2e28252</pub-id>
          <pub-id pub-id-type="pmcid">PMC8851340</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>Lavery</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Emmott</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jeck-Thole</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rouben</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Usher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>van der Spuij</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Woodward</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>An industry survey on managing the Pharmacovigilance System Master File in a global environment: the need for a pragmatic approach</article-title>
          <source>Pharm Med</source>
          <year>2022</year>
          <month>06</month>
          <day>20</day>
          <volume>36</volume>
          <issue>4</issue>
          <fpage>233</fpage>
          <lpage>245</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35723862"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40290-022-00422-2</pub-id>
          <pub-id pub-id-type="medline">35723862</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40290-022-00422-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC9334448</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morath</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Chiriac</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Jaszkowski</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Deiß</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Nürnberg</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hörth</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hoppe-Tichy</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Performance and risks of ChatGPT used in drug information: an exploratory real-world analysis</article-title>
          <source>Eur J Hosp Pharm</source>
          <year>2023</year>
          <month>06</month>
          <day>01</day>
          <volume>31</volume>
          <issue>6</issue>
          <fpage>491</fpage>
          <lpage>497</lpage>
          <pub-id pub-id-type="doi">10.1136/ejhpharm-2023-003750</pub-id>
          <pub-id pub-id-type="medline">37263772</pub-id>
          <pub-id pub-id-type="pii">ejhpharm-2023-003750</pub-id>
          <pub-id pub-id-type="pmcid">PMC11672346</pub-id>
        </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>Montastruc</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Storck</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>de Canecaude</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Victor</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cesbron</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zelmat</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Barus</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Will artificial intelligence chatbots replace clinical pharmacologists? An exploratory study in clinical practice</article-title>
          <source>Eur J Clin Pharmacol</source>
          <year>2023</year>
          <month>10</month>
          <volume>79</volume>
          <issue>10</issue>
          <fpage>1375</fpage>
          <lpage>1384</lpage>
          <pub-id pub-id-type="doi">10.1007/s00228-023-03547-8</pub-id>
          <pub-id pub-id-type="medline">37566133</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00228-023-03547-8</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>Pandya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sojitra</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Karamata</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Causality assessment of adverse drug reaction toxic epidermal necrolysis with the aid of ChatGPT: a case report</article-title>
          <source>Cureus</source>
          <year>2024</year>
          <month>05</month>
          <volume>16</volume>
          <issue>5</issue>
          <fpage>e60638</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38903274"/>
          </comment>
          <pub-id pub-id-type="doi">10.7759/cureus.60638</pub-id>
          <pub-id pub-id-type="medline">38903274</pub-id>
          <pub-id pub-id-type="pmcid">PMC11187461</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>Silverman</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Sushil</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bhasuran</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ludwig</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Buchanan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Racz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Parakala</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>El‐Kamary</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ahima</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Belov</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Billings</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Habal</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Tiwari</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Butte</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rudrapatna</surname>
              <given-names>VA</given-names>
            </name>
          </person-group>
          <article-title>Algorithmic identification of treatment‐emergent adverse events from clinical notes using large language models: a pilot study in inflammatory bowel disease</article-title>
          <source>Clin Pharmacol Ther</source>
          <year>2024</year>
          <month>03</month>
          <day>08</day>
          <volume>115</volume>
          <issue>6</issue>
          <fpage>1391</fpage>
          <lpage>1399</lpage>
          <pub-id pub-id-type="doi">10.1002/cpt.3226</pub-id>
          <pub-id pub-id-type="medline">38459719</pub-id>
          <pub-id pub-id-type="pmcid">PMC11090709</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dang</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Tong</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>RxBERT: Enhancing drug labeling text mining and analysis with AI language modeling</article-title>
          <source>Exp Biol Med (Maywood)</source>
          <year>2023</year>
          <month>11</month>
          <volume>248</volume>
          <issue>21</issue>
          <fpage>1937</fpage>
          <lpage>1943</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38166420"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/15353702231220669</pub-id>
          <pub-id pub-id-type="medline">38166420</pub-id>
          <pub-id pub-id-type="pmcid">PMC10798181</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Patterson</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>BERT-based language model for accurate drug adverse event extraction from social media: implementation, evaluation, and contributions to pharmacovigilance practices</article-title>
          <source>Front Public Health</source>
          <year>2024</year>
          <volume>12</volume>
          <fpage>1392180</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38716250"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpubh.2024.1392180</pub-id>
          <pub-id pub-id-type="medline">38716250</pub-id>
          <pub-id pub-id-type="pmcid">PMC11074401</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>MK</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in pharmacovigilance—opportunities and challenges</article-title>
          <source>Perspect Clin Res</source>
          <year>2024</year>
          <volume>15</volume>
          <issue>3</issue>
          <fpage>116</fpage>
          <lpage>121</lpage>
          <pub-id pub-id-type="doi">10.4103/picr.picr_290_23</pub-id>
          <pub-id pub-id-type="medline">39140015</pub-id>
          <pub-id pub-id-type="pii">PCR-15-116</pub-id>
          <pub-id pub-id-type="pmcid">PMC11318788</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gholap</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Uddin</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Faiyazuddin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Omri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gowri</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khalid</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Advances in artificial intelligence for drug delivery and development: a comprehensive review</article-title>
          <source>Comput Biol Med</source>
          <year>2024</year>
          <month>08</month>
          <volume>178</volume>
          <fpage>108702</fpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2024.108702</pub-id>
          <pub-id pub-id-type="medline">38878397</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(24)00787-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Danysz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cicirello</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mingle</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Assuncao</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Tetarenko</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mockute</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Abatemarco</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Widdowson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and the future of the drug safety professional</article-title>
          <source>Drug Saf</source>
          <year>2018</year>
          <month>10</month>
          <day>20</day>
          <volume>42</volume>
          <issue>4</issue>
          <fpage>491</fpage>
          <lpage>497</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30343417"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40264-018-0746-z</pub-id>
          <pub-id pub-id-type="medline">30343417</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40264-018-0746-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC6450851</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</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>Pharm Med</source>
          <year>2020</year>
          <month>02</month>
          <day>08</day>
          <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="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kassekert</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Grabowski</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Schaffer</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kempf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Roy</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kjoersvik</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Saldana</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>ElShal</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Industry perspective on artificial intelligence/machine learning in pharmacovigilance</article-title>
          <source>Drug Saf</source>
          <year>2022</year>
          <month>05</month>
          <day>17</day>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>439</fpage>
          <lpage>448</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35579809"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40264-022-01164-5</pub-id>
          <pub-id pub-id-type="medline">35579809</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40264-022-01164-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC9114066</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Noy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Experimental evidence on the productivity effects of generative artificial intelligence</article-title>
          <source>Science</source>
          <year>2023</year>
          <month>07</month>
          <day>14</day>
          <volume>381</volume>
          <issue>6654</issue>
          <fpage>187</fpage>
          <lpage>192</lpage>
          <pub-id pub-id-type="doi">10.1126/science.adh2586</pub-id>
          <pub-id pub-id-type="medline">37440646</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
