<?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">v22i11e15185</article-id>
      <article-id pub-id-type="pmid">33170134</article-id>
      <article-id pub-id-type="doi">10.2196/15185</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>Physicians’ Perceptions of the Use of a Chatbot for Information Seeking: Qualitative Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Dunn</surname>
            <given-names>Adam</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Myreteg</surname>
            <given-names>Gunilla</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Koman</surname>
            <given-names>Jason</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <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-1057-3481</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fauvelle</surname>
            <given-names>Khristina</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <address>
            <institution>Sanofi Aventis</institution>
            <addr-line>82, avenue Raspail</addr-line>
            <addr-line>Gentilly Cedex, 94255</addr-line>
            <country>France</country>
            <phone>33 772219558</phone>
            <email>khristina.fauvelle@sanofi.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2679-8391</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Schuck</surname>
            <given-names>Stéphane</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2642-7726</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Texier</surname>
            <given-names>Nathalie</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3749-254X</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Mebarki</surname>
            <given-names>Adel</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2925-7585</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Kap Code</institution>
        <addr-line>Paris</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>CNRS</institution>
        <institution>PASSAGES</institution>
        <addr-line>Bordeaux</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Bordeaux Population Health Research Center</institution>
        <institution>University of Bordeaux</institution>
        <institution>Inserm</institution>
        <addr-line>Bordeaux</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Sanofi Aventis</institution>
        <addr-line>Gentilly Cedex</addr-line>
        <country>France</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Khristina Fauvelle <email>khristina.fauvelle@sanofi.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>11</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>10</day>
        <month>11</month>
        <year>2020</year>
      </pub-date>
      <volume>22</volume>
      <issue>11</issue>
      <elocation-id>e15185</elocation-id>
      <history>
        <date date-type="received">
          <day>27</day>
          <month>6</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>21</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>9</day>
          <month>3</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>31</day>
          <month>3</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Jason Koman, Khristina Fauvelle, Stéphane Schuck, Nathalie Texier, Adel Mebarki. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 10.11.2020.</copyright-statement>
      <copyright-year>2020</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, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://www.jmir.org/2020/11/e15185/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Seeking medical information can be an issue for physicians. In the specific context of medical practice, chatbots are hypothesized to present additional value for providing information quickly, particularly as far as drug risk minimization measures are concerned.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This qualitative study aimed to elicit physicians’ perceptions of a pilot version of a chatbot used in the context of drug information and risk minimization measures.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>General practitioners and specialists were recruited across France to participate in individual semistructured interviews. Interviews were recorded, transcribed, and analyzed using a horizontal thematic analysis approach.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Eight general practitioners and 2 specialists participated. The tone and ergonomics of the pilot version were appreciated by physicians. However, all participants emphasized the importance of getting exhaustive, trustworthy answers when interacting with a chatbot.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The chatbot was perceived as a useful and innovative tool that could easily be integrated into routine medical practice and could help health professionals when seeking information on drug and risk minimization measures.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health</kwd>
        <kwd>digital health</kwd>
        <kwd>innovation</kwd>
        <kwd>conversational agent</kwd>
        <kwd>decision support system</kwd>
        <kwd>qualitative research</kwd>
        <kwd>chatbot</kwd>
        <kwd>bot</kwd>
        <kwd>medical drugs</kwd>
        <kwd>prescription</kwd>
        <kwd>risk minimization measures</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>A conversational agent, also known as a “chatbot,” is an artificial system that can converse with a human user through automated message exchange [<xref ref-type="bibr" rid="ref1">1</xref>]. In order to interact in a natural way with the user, it employs a question and answer database [<xref ref-type="bibr" rid="ref2">2</xref>]. Commonly used in marketing as a consumers’ guide, chatbots also have been developed in the health field in several applications aimed mostly towards patients [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. However, little scientific research has examined the use of conversational agents through physicians’ viewpoints [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref15">15</xref>], and none have taken into account medical information addressed to health professionals. It has been shown that nearly all physicians use the internet for medical information seeking [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>] but have to cope with an increasing flow of medical information [<xref ref-type="bibr" rid="ref18">18</xref>]. Too much information to scan could be a barrier to respond to a defined medical question [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]; thus, seeking health care information can be an issue for physicians since their information sources can be fragmented, incomplete, and not easy to find [<xref ref-type="bibr" rid="ref19">19</xref>]. Credibility of the source, relevance, unlimited access, speed, and ease of use are the main criteria for information seeking among physicians [<xref ref-type="bibr" rid="ref17">17</xref>]. A national survey conducted in France in 2017 showed that the prescription and delivery methods of drugs could be incorrectly followed by health professionals, despite the risk minimization measures campaign conducted at a national level [<xref ref-type="bibr" rid="ref20">20</xref>]. Providing medical information to health professionals through a conversational agent could help to detect pharmacovigilance cases early and to reinforce the proper intake of medication by patients. More specifically, chatbots could be deployed as a complementary solution to provide information about drugs with the purpose of minimizing drug risks. In France, drug risk minimization measures are generally recommended by the European Pharmacovigilance Risk Assessment Committee and adapted by the French National Agency for Medicines and Health Products Safety (Agence Nationale de Sécurité du Médicament et des Produits de Santé) to regulate medical practice and ensure safe, efficient intake of drugs [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      <p>To improve drug information access and awareness of drug risk minimization measures among physicians, a pilot version of a chatbot was developed and tested. The chatbot was expected to improve drug information access and awareness of drug risk minimization measures. This qualitative study aimed to improve the chatbot to meet physicians’ needs and expectations. User participation [<xref ref-type="bibr" rid="ref22">22</xref>] was used to elicit physicians’ perceptions of the chatbot through the use of the pilot version. Gathering more in-depth qualitative information on these topics may be useful to help develop a conversational agent that meets physicians’ needs and expectations.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>The study focused on the pilot version of a text-based chatbot developed by an international pharmaceutical company. This was qualitative research that employed individual, in-depth, semistructured interviews to explore physicians’ opinions and perceptions of a chatbot. The aim of the chatbot was to provide quick, 24-hour access to information on drugs for physicians to improve their medical practice and the application of recommendations regarding drug risk minimization measures among patients. Thus, all information provided by the chatbot was sourced from official regulatory documents issued by French health authorities to ensure patient security. The chatbot was accessible online through a web browser. When logged in, it displayed a dialog box on the right side of the screen and a female figure in the central area. Answers provided by the chatbot followed pre-established topics related to drugs (eg, treatment initiation, discontinuing treatment, treatment renewal, documentation or information that can be downloaded and obtained by the user). When asked a question, the chatbot provided a direct answer based on its database. When a question was not sufficiently focused, the chatbot proposed between 2 and 4 categories related to the question. The user then had to choose between those categories by typing the corresponding number. When the chatbot was asked a question that was not available in its database or not understood because of a typing error, the user was alerted. In this latter case, the user had to reformulate the question or ask a new question related to pre-established topics. As a pilot version, the chatbot initially focused on one drug. Further information can be added and delivered when the final version is deployed; the chatbot is meant to be used by physicians who seek quick access to information in the presence of a patient or when preparing a consultation.</p>
        <p>General practitioners were approached initially as the conversational agent was developed for this specific population. Specialists were also approached because some of their patients used drugs subject to risk minimization measures.</p>
      </sec>
      <sec>
        <title>Recruitment and Participants</title>
        <p>Participants were recruited on a voluntary basis after being asked by email whether they were interested in “taking part in a project that will test an innovative digital health tool.” Their email addresses were available from a database of health practitioners who had already participated in previous digital epidemiological studies. The interviewer had not met the participants before the interview. General practitioners were recruited to represent various situations such as urban and rural general practice. Specialists were recruited from either public or private practice. Thematic saturation was not taken into account since the study aimed to improve the chatbot through physicians’ needs and expectations in an explorative way without being representative.</p>
      </sec>
      <sec>
        <title>Data Collection</title>
        <sec>
          <title>Interview Design</title>
          <p>Semistructured interviews were conducted during June 2018 and July 2018 and took place primarily in participants’ medical offices. At the beginning of the interview, each participant received a brief summary of the study from the interviewer, and sociodemographic data (gender, age, profession, and workplace) were collected. Interviews were scheduled for approximatively 1 hour.</p>
          <p>To standardize the interviews, they were divided into 3 sections: introduction, introduction of the chatbot, and conclusion.</p>
        </sec>
        <sec>
          <title>Introduction</title>
          <p>The introduction included knowledge about the use of drugs and recommendations about risk minimization measures and acceptability of a chatbot within their daily practice.</p>
        </sec>
        <sec>
          <title>Presentation of the Chatbot</title>
          <p>The chatbot was presented through the example of 3 preselected input phrases based on various situations: “How to accompany a pregnant woman taking this medicine?”, “I want to renew the prescription of a patient.”, “Does this drug decrease the impact of contraception?” Test sessions were conducted as follows. After the introduction, the interviewer logged in to the chatbot with a confidential password. In the dialog box, introductory text was displayed and read aloud by the interviewer to explain the purpose of the chatbot. Then, preselected input phrases were first inputted by the interviewer to show how the chatbot worked. Participants were then asked to try the chatbot by searching for information on drugs as they would do during a real consultation, using their own terminology. Questions were collected by the interviewer after a physician concluded the test, but participants were left free to use the conversational agent as much as they wanted during the rest of the interview. Since it was a pilot version, participants did not have access to the conversational agent before or after the interview. Moreover, the test was different from a real-case scenario since participants were not totally autonomous in using the chatbot and had to share their experience with the interviewer.</p>
        </sec>
        <sec>
          <title>Conclusion</title>
          <p>During the conclusion, feedback was collected on the user experience with the chatbot. Physicians were asked about the relevance and appreciation of the tested tool as well as their needs for and expectations of the chatbot.</p>
        </sec>
        <sec>
          <title>Template</title>
          <p>The interviewer followed a semistructured interview template composed of the following themes: (1) knowledge about drug risk minimization measures and acceptability of digital health within their daily practice (Section 1), (2) relevance and appreciation of the chatbot to facilitate information acquisition (Section 3), and (3) needs for and expectations of the tested chatbot (Section 3).</p>
        </sec>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>Interviews were recorded using a digital audio recorder after receiving participant agreement. They were fully transcribed and anonymized by the interviewer. Transcripts were organized, sorted, and coded using a systematic thematic analysis approach [<xref ref-type="bibr" rid="ref23">23</xref>]. Main themes were developed and identified by the authors as patterns emerged within data [<xref ref-type="bibr" rid="ref24">24</xref>]. Then, they were graphically represented through the use of Visual Understanding Environment (VUE) software. For each participant, data were summarized in one table following the main themes identified during the interviews. Quotations that were not related to the chatbot were excluded from analysis. Data from each theme were gathered in another table to proceed with the horizontal thematic analysis by highlighting sentences expressed by participants on each topic.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Demographics</title>
        <p>A total of 10 health professionals participated in individual, in-depth, semistructured interviews in France.</p>
        <p>The sample size included 8 general practitioners and 2 specialists. The average age of the participants was 51.5 years. There were 7 men and 3 women; 6 participants worked in an urban area only, 3 worked in a rural area only, and 1 worked in both urban and rural areas. All participants were following patients who needed routine drug prescriptions including risk minimization measures.</p>
        <p>All participants reported being vigilant about new recommendations for prescription including risk minimization measures before using the chatbot. Seven physicians reported that they sought information on drugs subject to risk minimization measures only when their patients were directly concerned, when they were confronted with a particular case, or when adverse events had been reported to them:</p>
        <disp-quote>
          <p>I have access to information obviously, but I get more interested when I am confronted with the problem.</p>
          <attrib>Man, in practice for 35 years</attrib>
        </disp-quote>
        <p>They considered the information on drug risk minimization measures easy to find but fragmented. The main source of information they reported was the internet, followed by information from health authorities (letters, email), databases on drugs, medical journals, and communications from laboratories (press, visits). Exchanges with other practitioners had also been cited as sources of information:</p>
        <disp-quote>
          <p>The easiest and most accessible information is the summary of characteristic products, but it is in rather indigestible to read since it’s really big.</p>
          <attrib>Man, in practice for 11 years</attrib>
        </disp-quote>
        <disp-quote>
          <p>Generally, I do research spontaneously. I’m looking out on the internet when I have a question about a treatment or when I’m not sure about a question a patient asked me, we can look together.</p>
          <attrib>Woman, in practice for 8 years</attrib>
        </disp-quote>
        <disp-quote>
          <p>I get information from National Agency for Medicines and Health Products Safety, from health authorities, and from laboratories as well. I receive either emails or letters.</p>
          <attrib>Man, in practice for 30 years</attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>Central Themes</title>
        <sec>
          <title>Emerged Topics</title>
          <p>Several themes and subthemes emerged from the interviews. The central themes were (1) achievement by man including ergonomics and format of asking; (2) achievement by tool including design, tone, and form of presentation; (3) content of output including the amount of information, clarity, and accuracy; and (4) user needs. These topics are discussed with illustrative quotes in the following paragraphs.</p>
        </sec>
        <sec>
          <title>Achievement by Man</title>
          <p>In total, 52 questions were asked to the chatbot by participants. Of the 52 questions formulated by the physicians (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) during tests, 24 were answered by the pilot version of the conversational agent. One-third of the 24 answers (7/24) were obtained on the first try, while the other two-thirds (17/24) needed a complementary question. Furthermore, 28 questions were not understood by the conversational agent, and 8 questions were not included in the conversational agent themes. Questions addressed to the conversational agent were about prescription, medical treatment renewal, drug side effects, drug interactions, and records on drug products.</p>
          <p>Some physicians judged the ergonomics favorably due to simplicity and ease of use:</p>
          <disp-quote>
            <p>This is correct. The style is sober, quiet; it is not aggressive. It is simple and readable.</p>
            <attrib>Man, in practice for 36 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>Yes, it is really easy to use. The ergonomics are really good.</p>
            <attrib>Man, in practice for 11 years</attrib>
          </disp-quote>
          <p>Over half (6/10) of the participants found that the chatbot lacked intuitiveness and fluidity to access information:</p>
          <disp-quote>
            <p>The answer is clear, but I don’t know, there is something with the fluidity... If I compare with where I’m usually looking for information, there is one section for each topic, and I get instant access. Here, the answers are too robotic.</p>
            <attrib>Woman, in practice for 24 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>I would say this is not intuitive. Everyone knows how to use a computer. But the ergonomics... I don’t know, there is just a login page, then the home screen. If it is just that, there is no ergonomics. It would be nice to have a website plan.</p>
            <attrib>Male, in practice for 30 years</attrib>
          </disp-quote>
          <p>The size of the dialog box was also cited as improvable:</p>
          <disp-quote>
            <p>There is a part of the screen that is not used; the dialog box looks really small compared to the rest. It could occupy a larger space, which would allow a bigger typeface.</p>
            <attrib>Man, in practice for 11 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>The window to type our questions is too small. If you enter a long sentence, you can’t see the beginning of your sentence, which is bothering. Indeed, the window is too small and the typeface as well.</p>
            <attrib>Man, in practice for 36 years</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Achievement by Tool</title>
          <p>Most of the participants reported that the colors and icon of the chatbot were too simple, but the global design was judged serious and professional, which was appreciated:</p>
          <disp-quote>
            <p>You could give us the possibility to customize the design by choosing between 3 or 4 different colors. Maybe it should be a bit more cheerful. It looks seriously made, but a little too dark.</p>
            <attrib>Man, 18 years of practice</attrib>
          </disp-quote>
          <disp-quote>
            <p>I like the font; it is quite nice. It looks as if everything was made to be relatively neutral. This is good because the tool can’t be visually aggressive during a consultation. This is not really attractive; it is quite neutral, but this is adapted because visual elements catching your eyes all the time can be tiring. This is better.</p>
            <attrib>Man, in practice for 11 years</attrib>
          </disp-quote>
          <p>Seven participants reported that the tone of the answers was positive. However, the display of the answers provided by the conversational agent needed to be more concise according to half (5/10) of the physicians:</p>
          <disp-quote>
            <p>It speaks from a medical point of view so there is no problem with the tone.</p>
            <attrib>Man, in practice for 36 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>It needs a display with bold characters so we can reach key points by reading through it diagonally</p>
            <attrib>Man, in practice for 23 years</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Content of Output</title>
          <p>The response delay from the chatbot was acceptable for 9 of 10 participants, but 5 physicians were not satisfied with the length of the information, which was too broad to read or to access:</p>
          <disp-quote>
            <p>It is a little bit long because every time it asked me for a clarification, it seems that it doesn’t understand.</p>
            <attrib>Woman, specialist in practice for 24 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>This is accurate but it is too much talking. Two lines should be enough; this is too long in my opinion.</p>
            <attrib>Woman, in practice for 24 years</attrib>
          </disp-quote>
          <p>Even though all participants found the information provided by the chatbot very clear, the main issue pointed out by physicians was the accuracy of the answers. Obtained answers did not provide a sufficient amount of information. Thus, even if they trusted the provided information, it was considered as too generic and not relevant enough:</p>
          <disp-quote>
            <p>We need clear and concise scientific information. We need to know globally what to do; then, we translate the information but at least it needs to be precise. Because for now, it is a little bit general; this is too elementary.</p>
            <attrib>Man, in practice for 35 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>The answers are understandable; it comes out quickly; it comes out clear. The only inconvenience is that it is not the answer I was looking for.</p>
            <attrib>Man, in practice for 18 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>It is centered on the developers’ insight, not from a physician’s insight. This is almost a tool for a patient actually. Physicians have much more questions than the chatbot can answer for now.</p>
            <attrib>Man, in practice for 11 years</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>User Needs</title>
          <p>Participants identified pros and cons of the chatbot after they tested it (<xref ref-type="table" rid="table1">Table 1</xref>). Pros were the concept, ergonomics, assistance for diagnosis, and time savings. Cons were the natural language comprehension issues, data security, and the threat to health care professions.</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Pros and cons of the chatbot.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="370"/>
              <col width="600"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Observation and examples</td>
                  <td>Example excerpts</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Pros</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Relevant concept: give fast and precise information</td>
                  <td>“In my opinion, the concept is really interesting. Why? Because this is provisioning a tool in which we can get precise and fast information. This is a concept that seems very interesting and very relevant to me.” [Man, in practice for 35 years]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Ergonomic tool: can be utilized as a research tool</td>
                  <td>“The ergonomics, the conciseness…Yes, the shape. You call this a conversational agent; to me, it is a good research engine.” [Man, in practice for 11 years]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Diagnosis helping:<break/>can provide assistance to medical care</td>
                  <td>“The fact that it can give answers when we have a question is interesting. That doesn’t mean we’ll necessarily follow the answer but at least it gives a direction. Tools that can help medical care or to diagnose, I find great.” [Woman, in practice for 24 years]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Time-saving</td>
                  <td>“There are only benefits anyway. This is instantaneous, verified information. It saves us time. A consultation is time-consuming; we need to get immediate answers. It has already happened to me that I had to call a laboratory to get an answer, and I was told that someone would call me back. Here, I get my answer almost directly” [Man, in practice for 30 years]</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Cons</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Natural language comprehension issues: can be difficult to access the right information</td>
                  <td>“The tree structure to get to the information. That is to say… If I get some information, in what degree is it intuitive? Does it need to be questioned in a precise way, or can I ask my questions without thinking about the formulation? Can it answer my everyday needs?” [Man, in practice for 18 years]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Medical data issue: can be dangerous for medical data security</td>
                  <td>“Of course, there is hacking. I can’t take control of a doctor, but I can get control of a conversational agent without problems. All the security part, as powerful it can be, can always be breached if someone intends to do it. That’s the limit.” [Man, in practice for 23 years]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Threatens health care professionals: a chatbot could replace doctors</td>
                  <td>“Let’s say that, in 10 years, we are told that our job will be replaced; it is a nightmare. We studied for 10 years, not 2 years, but 10 years. If we are told that we will be replaced by artificial intelligence, it does not make anyone dream.” [Man, in practice for 23 years]</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <p>Nine participants estimated that this tool would be easily integrated in their routine practice when fully developed, especially if it could provide fast, trustful, easily accessible information on a range of medical topics:</p>
          <disp-quote>
            <p>It is simple; it is practical. When it has acquired more vocabulary, I think it will be an efficient tool.</p>
            <attrib>Woman, in practice for 8 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>This is a tool in which we can get precise and fast information. This is a concept that seems very interesting and very relevant to me”</p>
            <attrib>Man, in practice for 35 years</attrib>
          </disp-quote>
          <p>However, half (5/10) of the participants considered that the chatbot did not meet their needs. The main reason was the natural language comprehension issues:</p>
          <disp-quote>
            <p>It needs to be accurate and well-edocumented because, during a consultation and in our daily routine, we don’t have much time. Not having enough time means we need to get to the point; so, we need fast, specific information”</p>
            <attrib>Man, in practice for 35 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>If I get information, what is the degree of intuitiveness? The machine has to adapt, because when I’m doing my job with a patient in front of me, I can’t be focused on how I should formulate my question to the chatbot.</p>
            <attrib>Man, in practice for 18 years</attrib>
          </disp-quote>
          <disp-quote>
            <p>During a consultation, everything has to be done quickly, I need information quickly. If the chatbot doesn’t understand me, I put it aside to get the information elsewhere.</p>
            <attrib>Woman, in practice for 24 years</attrib>
          </disp-quote>
          <p>Participants reported areas to improve the chatbot prototype (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>). Suggestions were made about the content of the conversational agent, its display and appearance, and the extensions of use that could be made. Suggestions included highlighting the most important information provided by the chatbot, the possibility to provide an information sheet to the patients, or integrating medical themes beyond drug risk minimization measures.</p>
          <boxed-text id="box1" position="float">
            <title>Suggestions made by general practitioners and specialists for improvement of the conversational agent.</title>
            <p>Display and appearance</p>
            <list list-type="bullet">
              <list-item>
                <p>Highlight important information in the answers</p>
              </list-item>
              <list-item>
                <p>Possibility to choose interface colors</p>
              </list-item>
            </list>
            <p>Content</p>
            <list list-type="bullet">
              <list-item>
                <p>Provide [printed] information to the patients</p>
              </list-item>
              <list-item>
                <p>Regular updates</p>
              </list-item>
            </list>
            <p>Extensions of use</p>
            <list list-type="bullet">
              <list-item>
                <p>Ask questions orally</p>
              </list-item>
              <list-item>
                <p>Integrate more themes (eg, drug interactions, pathologies)</p>
              </list-item>
              <list-item>
                <p>Declare side effects</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The study was conducted to elicit physicians’ perceptions of a chatbot that is meant to improve drug information access and awareness of drug risk minimization measures. A qualitative approach was chosen to collect detailed data on how the chatbot was used and perceived by physicians on a small scale and needs and expectations for the chatbot. As a pilot version, the chatbot did not meet physicians’ expectations.</p>
        <p>Overall, the findings demonstrated that physicians’ needs towards information delivered by the chatbot were the reliability of sources, precise information, and speed of access. This is consistent with previous research demonstrating that all these features are critical to physicians when seeking information [<xref ref-type="bibr" rid="ref17">17</xref>]. Physicians were particularly vigilant to the conversational agent content. Even though they did appreciate getting information on risk minimization measures and drugs, they had difficulties accessing the right information because of natural language understanding issues. As a tool based on artificial intelligence, physicians also expected that the chatbot would understand natural language. Previous research demonstrated that over half of physicians believed that chatbots lack the intelligence or knowledge to accurately assess the user [<xref ref-type="bibr" rid="ref13">13</xref>], which can be an issue regarding speed and ease of use when using the chatbot.</p>
        <p>The chatbot format was also appreciated, as it could easily be integrated into physicians’ routine practice, either during or before a consultation with a patient. This was judged as innovative since most chatbots in health care are developed to provide information for patients [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. Access to information is also considered easier with a conversational agent than with a classic drug reference database. First, it was considered to provide reliable information in a practical way. Second, it made information accessible so that physicians could quickly find what they were looking for and, consequently, save time. In that way, using a chatbot can improve medical care from physicians’ perspectives. Shared decision making may increase the effectiveness of a treatment if the patient is given a sufficient and appropriate amount of information [<xref ref-type="bibr" rid="ref25">25</xref>]. In this regard, the chatbot could help medical care.</p>
        <p>It was pointed out that the conversational agent did not always respond to the questions they formulated, either because it did not recognize the everyday language employed by the users or because the answers, while based on official regulatory documents, were too broad without highlighting the most important parts of information. However, they were aware that the chatbot was still in an experimental stage. Regarding this fact, most practitioners were willing to use the conversational agent in its fully developed version if this tool remains easy to use, secure, and easily accessible.</p>
        <p>Areas of improvement for the conversational agent proposed by medical practitioners included a better understanding of the questions formulated, highlighting the most important information, and better ergonomics.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This market research is not without limitations. As an exploratory study with a sample size of 10 medical practitioners, findings are not generalizable to the entire population of medical practitioners. This was a qualitative study conducted with semistructured interviews, which allowed us to explore tendencies and opinions on the usage of a conversational agent. The average age of our sample (51.5 years) was slightly above the average age of the medical practitioner population in France, which was 50.8 years in 2018 [<xref ref-type="bibr" rid="ref19">19</xref>]. The majority of our sample was male practitioners (7/10, 70%), which does not reflect the distribution between male (53%) and female (47%) medical practitioners in France in 2018 [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>In addition, medical practitioners who were recruited had already participated in other digital epidemiological studies carried out by the same research team, and it is possible that they were more receptive to new health technology. In other words, while our sampling method was not meant to be representative, this specific market research may be prone to researcher bias.</p>
        <p>Finally, because of the confidentiality policy, the drug associated with the chatbot could not be cited in the paper. However, we believe that it did not interfere with the results, which were meant to elicit physicians’ perceptions of the chatbot.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>According to the results of this study, it appears that chatbots could be a solution for quick and easily accessible information. By reinforcing the knowledge on drugs based on official and institutional recommendations, a chatbot could be used to enhance compliance with the drug risk minimization measure within the physician population. In particular, this chatbot prototype was perceived by medical practitioners as a useful, acceptable, innovative tool that could easily be integrated in their daily medical practice. Finally, even though the chatbot prototype could not be used as it was because of insufficient information in the database, findings suggest that physicians are willing to use a chatbot not only for prescription but also to get information on drug interactions or to obtain assistance within medical care for complex pathology or disease management. A future challenge for the chatbot should be to accommodate physicians’ needs for accurate, concise information based on official regulatory documents that ensure patients’ security.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Questions tested by physicians.</p>
        <media xlink:href="jmir_v22i11e15185_app1.docx" xlink:title="DOCX File , 19 KB"/>
      </supplementary-material>
    </app-group>
    <ack>
      <p>Sanofi is the study funder.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>SS, JK, NT, and AM (Kap-Code) received financial support from SANOFI SA for data collection and interpretation and for writing the manuscript. Kap-Code is a start-up in digital health, which provides solutions in chronic diseases and detection of pharmacovigilance signals on social networks. KF is employed by SANOFI SA.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amato</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Marrone</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moscato</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Piantadosi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Picariello</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Chatbots Meet eHealth: Automatizing Healthcare</article-title>
          <year>2017</year>
          <conf-name>Workshop on Artificial Intelligence with Application in Health</conf-name>
          <conf-date>November 14, 2017</conf-date>
          <conf-loc>Bari, Italy</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://ceur-ws.org/Vol-1982/paper6.pdf"/>
          </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>Corti</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gillespie</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A truly human interface: interacting face-to-face with someone whose words are determined by a computer program</article-title>
          <source>Front Psychol</source>
          <year>2015</year>
          <volume>6</volume>
          <fpage>634</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fpsyg.2015.00634"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2015.00634</pub-id>
          <pub-id pub-id-type="medline">26042066</pub-id>
          <pub-id pub-id-type="pmcid">PMC4434916</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>Gaffney</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mansell</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tai</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Conversational Agents in the Treatment of Mental Health Problems: Mixed-Method Systematic Review</article-title>
          <source>JMIR Ment Health</source>
          <year>2019</year>
          <month>10</month>
          <day>18</day>
          <volume>6</volume>
          <issue>10</issue>
          <fpage>e14166</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mental.jmir.org/2019/10/e14166/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14166</pub-id>
          <pub-id pub-id-type="medline">31628789</pub-id>
          <pub-id pub-id-type="pii">v6i10e14166</pub-id>
          <pub-id pub-id-type="pmcid">PMC6914342</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>D'Alfonso</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Santesteban-Echarri</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Rice</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wadley</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lederman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Miles</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gleeson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Alvarez-Jimenez</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Artificial Intelligence-Assisted Online Social Therapy for Youth Mental Health</article-title>
          <source>Front Psychol</source>
          <year>2017</year>
          <volume>8</volume>
          <fpage>796</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fpsyg.2017.00796"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2017.00796</pub-id>
          <pub-id pub-id-type="medline">28626431</pub-id>
          <pub-id pub-id-type="pmcid">PMC5454064</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lokman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zain</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Komputer</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Perisian</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Designing a Chatbot for Diabetic Patients</article-title>
          <year>2009</year>
          <conf-name>International Conference on Software Engineering &#38; Computer Systems</conf-name>
          <conf-date>October 2009</conf-date>
          <conf-loc>Kuantan, Malaysia</conf-loc>
          <fpage>19</fpage>
          <lpage>21</lpage>
        </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>Crutzen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>GY</given-names>
            </name>
            <name name-style="western">
              <surname>Portugal</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Fisser</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Grolleman</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>An artificially intelligent chat agent that answers adolescents' questions related to sex, drugs, and alcohol: an exploratory study</article-title>
          <source>J Adolesc Health</source>
          <year>2011</year>
          <month>05</month>
          <volume>48</volume>
          <issue>5</issue>
          <fpage>514</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jadohealth.2010.09.002</pub-id>
          <pub-id pub-id-type="medline">21501812</pub-id>
          <pub-id pub-id-type="pii">S1054-139X(10)00430-1</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>Comendador</surname>
              <given-names>BEV</given-names>
            </name>
            <name name-style="western">
              <surname>Francisco</surname>
              <given-names>BMB</given-names>
            </name>
            <name name-style="western">
              <surname>Medenilla</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Nacion</surname>
              <given-names>SMT</given-names>
            </name>
            <name name-style="western">
              <surname>Serac</surname>
              <given-names>TBE</given-names>
            </name>
          </person-group>
          <article-title>Pharmabot: A Pediatric Generic Medicine Consultant Chatbot</article-title>
          <source>JOACE</source>
          <year>2015</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>137</fpage>
          <lpage>140</lpage>
          <pub-id pub-id-type="doi">10.12720/joace.3.2.137-140</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>Ireland</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Atay</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liddle</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bradford</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Rushin</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Mullins</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Angus</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wiles</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McBride</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Hello Harlie: Enabling Speech Monitoring Through Chat-Bot Conversations</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>227</volume>
          <fpage>55</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="medline">27440289</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>Stieger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nißen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rüegger</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Flückiger</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Allemand</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>PEACH, a smartphone- and conversational agent-based coaching intervention for intentional personality change: study protocol of a randomized, wait-list controlled trial</article-title>
          <source>BMC Psychol</source>
          <year>2018</year>
          <month>09</month>
          <day>04</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>43</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpsychology.biomedcentral.com/articles/10.1186/s40359-018-0257-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40359-018-0257-9</pub-id>
          <pub-id pub-id-type="medline">30180880</pub-id>
          <pub-id pub-id-type="pii">10.1186/s40359-018-0257-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC6123904</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghosh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatia</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatia</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Quro: Facilitating User Symptom Check Using a Personalised Chatbot-Oriented Dialogue System</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2018</year>
          <volume>252</volume>
          <fpage>51</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="medline">30040682</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>Hess</surname>
              <given-names>GI</given-names>
            </name>
            <name name-style="western">
              <surname>Fricker</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Improving and Evaluating eMMA's Communication Skills: A Chatbot for Managing Medication</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <volume>259</volume>
          <fpage>101</fpage>
          <lpage>104</lpage>
          <pub-id pub-id-type="medline">30923283</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Megaw</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bond</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mulvenna</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>O'Neill</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Armour</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McTear</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Best practices for designing chatbots in mental healthcare? A case study on iHelpr</article-title>
          <year>2018</year>
          <conf-name>32nd International BCS Human Computer Interaction Conference (HCI)</conf-name>
          <conf-date>July 2-6, 2018</conf-date>
          <conf-loc>Belfast, Northern Ireland</conf-loc>
          <publisher-loc>Swindon</publisher-loc>
          <pub-id pub-id-type="doi">10.14236/ewic/hci2018.129</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Palanica</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Flaschner</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Thommandram</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fossat</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Physicians' Perceptions of Chatbots in Health Care: Cross-Sectional Web-Based Survey</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>04</month>
          <day>05</day>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>e12887</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/4/e12887/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12887</pub-id>
          <pub-id pub-id-type="medline">30950796</pub-id>
          <pub-id pub-id-type="pii">v21i4e12887</pub-id>
          <pub-id pub-id-type="pmcid">PMC6473203</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>Feldman</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffer</surname>
              <given-names>EP</given-names>
            </name>
            <name name-style="western">
              <surname>Barnett</surname>
              <given-names>GO</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Famiglietti</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Chueh</surname>
              <given-names>HC</given-names>
            </name>
          </person-group>
          <article-title>Impact of a computer-based diagnostic decision support tool on the differential diagnoses of medicine residents</article-title>
          <source>J Grad Med Educ</source>
          <year>2012</year>
          <month>06</month>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>227</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23730446"/>
          </comment>
          <pub-id pub-id-type="doi">10.4300/JGME-D-11-00180.1</pub-id>
          <pub-id pub-id-type="medline">23730446</pub-id>
          <pub-id pub-id-type="pii">JGME-D-11-00180</pub-id>
          <pub-id pub-id-type="pmcid">PMC3399617</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>Laranjo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Tong</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Kocaballi</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bashir</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Surian</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gallego</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Magrabi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>AYS</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Conversational agents in healthcare: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>09</month>
          <day>01</day>
          <volume>25</volume>
          <issue>9</issue>
          <fpage>1248</fpage>
          <lpage>1258</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30010941"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy072</pub-id>
          <pub-id pub-id-type="medline">30010941</pub-id>
          <pub-id pub-id-type="pii">5052181</pub-id>
          <pub-id pub-id-type="pmcid">PMC6118869</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Casebeer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kristofco</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Carillo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Centor</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Physician Internet medical information seeking and on-line continuing education use patterns</article-title>
          <source>J Contin Educ Health Prof</source>
          <year>2002</year>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>33</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1002/chp.1340220105</pub-id>
          <pub-id pub-id-type="medline">12004639</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>NL</given-names>
            </name>
            <name name-style="western">
              <surname>Casebeer</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Kristofco</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Strasser</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Physicians' Internet information-seeking behaviors</article-title>
          <source>J Contin Educ Health Prof</source>
          <year>2004</year>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1002/chp.1340240106</pub-id>
          <pub-id pub-id-type="medline">15069910</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nylenna</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aasland</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Primary care physicians and their information-seeking behaviour</article-title>
          <source>Scand J Prim Health Care</source>
          <year>2000</year>
          <month>03</month>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>9</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/02813430050202488"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/02813430050202488</pub-id>
          <pub-id pub-id-type="medline">10811036</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Begaud</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Costagiola</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Rapport sur la surveillance et la promotion du bon usage du medicament en France</article-title>
          <source>French Ministry of Solidarity and Health</source>
          <year>2013</year>
          <access-date>2019-02-21</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://solidarites-sante.gouv.fr/IMG/pdf/Rapport_Begaud_Costagliola.pdf">https://solidarites-sante.gouv.fr/IMG/pdf/Rapport_Begaud_Costagliola.pdf</ext-link>
            <ext-link ext-link-type="webcite" xlink:href="76MHfSLD1"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Sanofi Aventis France</collab>
          </person-group>
          <article-title>Evaluation auprès des pharmaciens d'officine des mesures de minimisation du risqué consistant en des nouvelles conditions de prescription et de délivrance (CPD) du valproate</article-title>
          <source>Synthesis from National Agency for Medicines and Health Products Safety</source>
          <year>2017</year>
          <access-date>2019-03-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ansm.sante.fr/var/ansm_site/storage/original/application/cfc9902b616321c0fc3bc742dc57053b.pdf">https://www.ansm.sante.fr/var/ansm_site/storage/original/application/cfc9902b616321c0fc3bc742dc57053b.pdf</ext-link>
            <ext-link ext-link-type="webcite" xlink:href="76oseOTZv"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <article-title>Mesures additionnelles de minimisation des risques</article-title>
          <source>National Agency for Medicines and Health Products Safety</source>
          <year>2017</year>
          <access-date>2019-02-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ansm.sante.fr/Activites/Surveillance-des-medicaments/Mesures-additionnelles-de-reduction-du-risque/(offset)/1">https://www.ansm.sante.fr/Activites/Surveillance-des-medicaments/Mesures-additionnelles-de-reduction-du-risque/(offset)/1</ext-link>
            <ext-link ext-link-type="webcite" xlink:href="76HXB1P43"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barki</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hartwick</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Measuring User Participation, User Involvement, and User Attitude</article-title>
          <source>MIS Quarterly</source>
          <year>1994</year>
          <month>03</month>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>59</fpage>
          <lpage>82</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/249610?seq=1"/>
          </comment>
          <pub-id pub-id-type="doi">10.2307/249610</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guest</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>MacQueen</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Namey</surname>
              <given-names>EE</given-names>
            </name>
          </person-group>
          <article-title>Introduction</article-title>
          <source>Applied Thematic Analysis</source>
          <year>2011</year>
          <month>11</month>
          <day>09</day>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications, Inc</publisher-name>
          <fpage>3</fpage>
          <lpage>20</lpage>
        </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>Richards</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Readme First For A User's Guide To Qualitative Methods</source>
          <year>2019</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications, Inc</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coulter</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Entwistle</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Gilbert</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Sharing decisions with patients: is the information good enough?</article-title>
          <source>BMJ</source>
          <year>1999</year>
          <month>01</month>
          <day>30</day>
          <volume>318</volume>
          <issue>7179</issue>
          <fpage>318</fpage>
          <lpage>22</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/9924064"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.318.7179.318</pub-id>
          <pub-id pub-id-type="medline">9924064</pub-id>
          <pub-id pub-id-type="pmcid">PMC1114785</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
