<?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="review-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">v25i1e41583</article-id>
      <article-id pub-id-type="pmid">36716093</article-id>
      <article-id pub-id-type="doi">10.2196/41583</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Developing a Technical-Oriented Taxonomy to Define Archetypes of Conversational Agents in Health Care: Literature Review and Cluster Analysis</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>Zandesh</surname>
            <given-names>Zahra</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Bunge</surname>
            <given-names>Eduardo</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Denecke</surname>
            <given-names>Kerstin</given-names>
          </name>
          <degrees>DrRerNat</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Bern University of Applied Sciences</institution>
            <addr-line>Quellgasse 21</addr-line>
            <addr-line>Biel, 2502</addr-line>
            <country>Switzerland</country>
            <phone>41 32 321 67 94</phone>
            <email>kerstin.denecke@bfh.ch</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6691-396X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>May</surname>
            <given-names>Richard</given-names>
          </name>
          <degrees>MEng</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7186-404X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Bern University of Applied Sciences</institution>
        <addr-line>Biel</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Harz University of Applied Sciences</institution>
        <addr-line>Wernigerode</addr-line>
        <country>Germany</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Kerstin Denecke <email>kerstin.denecke@bfh.ch</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>30</day>
        <month>1</month>
        <year>2023</year>
      </pub-date>
      <volume>25</volume>
      <elocation-id>e41583</elocation-id>
      <history>
        <date date-type="received">
          <day>1</day>
          <month>8</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>16</day>
          <month>11</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>20</day>
          <month>11</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>12</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Kerstin Denecke, Richard May. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 30.01.2023.</copyright-statement>
      <copyright-year>2023</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 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/2023/1/e41583" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The evolution of artificial intelligence and natural language processing generates new opportunities for conversational agents (CAs) that communicate and interact with individuals. In the health domain, CAs became popular as they allow for simulating the real-life experience in a health care setting, which is the conversation with a physician. However, it is still unclear which technical archetypes of health CAs can be distinguished. Such technical archetypes are required, among other things, for harmonizing evaluation metrics or describing the landscape of health CAs.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The objective of this work was to develop a technical-oriented taxonomy for health CAs and characterize archetypes of health CAs based on their technical characteristics.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We developed a taxonomy of technical characteristics for health CAs based on scientific literature and empirical data and by applying a taxonomy development framework. To demonstrate the applicability of the taxonomy, we analyzed the landscape of health CAs of the last years based on a literature review. To form technical design archetypes of health CAs, we applied a k-means clustering method.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Our taxonomy comprises 18 unique dimensions corresponding to 4 perspectives of technical characteristics (setting, data processing, interaction, and agent appearance). Each dimension consists of 2 to 5 characteristics. The taxonomy was validated based on 173 unique health CAs that were identified out of 1671 initially retrieved publications. The 173 CAs were clustered into 4 distinctive archetypes: a text-based ad hoc supporter; a multilingual, hybrid ad hoc supporter; a hybrid, single-language temporary advisor; and, finally, an embodied temporary advisor, rule based with hybrid input and output options.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>From the cluster analysis, we learned that the time dimension is important from a technical perspective to distinguish health CA archetypes. Moreover, we were able to identify additional distinctive, dominant characteristics that are relevant when evaluating health-related CAs (eg, input and output options or the complexity of the CA personality). Our archetypes reflect the current landscape of health CAs, which is characterized by rule based, simple systems in terms of CA personality and interaction. With an increase in research interest in this field, we expect that more complex systems will arise. The archetype-building process should be repeated after some time to check whether new design archetypes emerge.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>mobile phone</kwd>
        <kwd>user-computer interface</kwd>
        <kwd>telemedicine</kwd>
        <kwd>communication</kwd>
        <kwd>delivery of health care and methods</kwd>
        <kwd>delivery of health care and trends</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>In recent years, artificial intelligence (AI) has become increasingly successful because of its powerful capabilities and possibilities for a variety of application areas. Precisely, AI is the use of computers and technology to simulate intelligent behavior and critical thinking comparable with a human being [<xref ref-type="bibr" rid="ref1">1</xref>]. The possibility of machines behaving in such a way was originally raised by Alan Turing and further explored starting in the 1950s. However, the evolution of AI and natural language processing generates new opportunities for conversational agents (CAs) that communicate and interact with individuals. Enabling those agents to speak becomes straightforward through current speech-to-text and text-to-speech technology.</p>
      </sec>
      <sec>
        <title>Motivation</title>
        <p>In this work, we considered CAs as dialog systems interacting with users in a humanlike manner. Chatbots are a subset of CAs as they are also dialog systems, but the user interface is often button focused. In the health domain, CAs became popular as they allow for simulating the real-life experience in a health care setting, which is the conversation with a physician. They have been tested for patient education [<xref ref-type="bibr" rid="ref2">2</xref>], supporting behavior change [<xref ref-type="bibr" rid="ref3">3</xref>], or delivering cognitive behavioral therapy [<xref ref-type="bibr" rid="ref4">4</xref>]. Furthermore, hospitals and private clinics use CAs to triage and clerk patients even before they come into the consulting room. The intelligent agents ask relevant questions about the patients’ symptoms, with automated responses that aim to produce a comprehensive medical history for the physician [<xref ref-type="bibr" rid="ref5">5</xref>]. In combination with regular care provision, CAs offer the great opportunity of improving the efficiency of patient care delivery, simplifying processes, and ensuring quality of care.</p>
        <p>However, to develop and assess CAs, it is initially important to know how CAs are designed, especially from a technical perspective. Thus, the objective of this work was to develop a taxonomy of technical aspects characterizing health CAs. This taxonomy was used to form unique archetypes. Each of these archetypes was expected to be different in terms of its technical properties. The archetypes aimed to deliver insights into the current landscape of health CAs. Moreover, they could form the basis to specify sets of relevant evaluation metrics for each archetype to ensure harmonized quality assessment.</p>
        <p>Health CAs differ from general domain CAs in multiple aspects. The conversation content has to be tailored based on the application area, use case, and user context, and has to address privacy [<xref ref-type="bibr" rid="ref6">6</xref>]. Similar to the physician-patient communication along a treatment process, health CAs can require multiple interactions over a period. Interaction frequency can be multiple times a day. These interactions require information to be retained persistently between sessions, and sometimes it is even necessary to refer to information from previous dialogs. As patient knowledge increases over time, the language and content should adapt to different knowledge levels. A crucial aspect within health care communication is empathy; thus, a health CA must also “address social, emotional and relational issues” [<xref ref-type="bibr" rid="ref6">6</xref>]. These peculiarities of health CAs lead to technical characteristics that can be used to characterize health CAs.</p>
      </sec>
      <sec>
        <title>Related Work</title>
        <p>There are some classification frameworks for health CAs. The approaches are dispersed into different thematic axes such as application area. Janssen et al [<xref ref-type="bibr" rid="ref7">7</xref>] suggested a taxonomy for CAs focusing on general CA design, the technological structure, and the context in which the CA is embedded. Information on data processing is not included in this taxonomy. Trofymenko et al [<xref ref-type="bibr" rid="ref8">8</xref>] presented a classification of CAs for the purpose of “a clear understanding of nature, approaches to creation, advantages and disadvantages” of CAs. Their classification distinguished 7 dimensions: purpose, location, interface, number of users, form of access, algorithm, and functionality. This taxonomy focuses on the use case perspective but misses information on the technical realization. Nissen et al [<xref ref-type="bibr" rid="ref9">9</xref>] introduced a design taxonomy to characterize user-chatbot relationships. Their taxonomy focuses on the time horizon of a CA and not on technical characteristics. They distinguished 3 time-dependent archetypes of open-domain CAs: ad hoc supporters, persistent companions, and temporary advisors. Other taxonomies considered specific aspects of CAs. As exemplified, Welivita and Pu [<xref ref-type="bibr" rid="ref10">10</xref>] introduced a taxonomy of empathic chatbot responses. Feine et al [<xref ref-type="bibr" rid="ref11">11</xref>] built a taxonomy of social cues of CAs concentrating on verbal, visual, auditory, and invisible aspects. None of the available taxonomies focuses on technical characteristics specifically considered for health CAs.</p>
        <p>In addition, there are reviews of health CAs and descriptions of specific characteristics without any systematic consolidation of the findings in terms of a taxonomy. For instance, Vaidyam et al [<xref ref-type="bibr" rid="ref12">12</xref>] reviewed chatbots and their particularities in mental health. Tudor Car et al [<xref ref-type="bibr" rid="ref13">13</xref>] conducted a scoping review on the characteristics of general health CAs. For these and similar reviews related to health CAs, extraction tables were defined. They reflect the focus of the review but are insufficient as taxonomies of technical characteristics.</p>
        <p>Other CA research identified archetypes of CAs from different perspectives. Diederich et al [<xref ref-type="bibr" rid="ref14">14</xref>] distinguished CA design platforms. They identified text-based, domain-specific CA platforms; general-purpose, cloud-based CA platforms; and multilanguage, integrative CA platforms. Furthermore, they grouped CAs based on their design and interaction paradigms [<xref ref-type="bibr" rid="ref15">15</xref>]. More specifically, they considered 4 dimensions affecting interaction: context, human, perception, and outcome. However, they did not concentrate on a particular domain as we did by focusing on health CAs. Bahja and Lowry [<xref ref-type="bibr" rid="ref16">16</xref>] formed archetypes from a customer-centric value chain perspective. They specified 4 archetypes for service-oriented CAs: informer, planner, facilitator, and performer. Jovanović et al [<xref ref-type="bibr" rid="ref17">17</xref>] formed archetypes regarding health provisioning roles (diagnostic, prevention, or therapy).</p>
        <p>Overall, the related work we identified lacks a comparable taxonomy and archetypes focusing on the technical implementation aspects of health CAs. Although there is already some research available trying to enlighten the facets and appearances of CAs, a taxonomy focusing on the technical aspects of health CAs is still missing. We fill this gap by suggesting a taxonomy of technical CA characteristics. The questions driving our study are as follows: (1) What are the technical characteristics of health CAs? (2) Which archetypes of health CAs can be empirically identified using technical characteristics? (3) Which distinctive properties exist to characterize single groups of health CAs?</p>
        <p>To answer these questions, we developed a technical-oriented taxonomy for health CAs based on scientific literature and empirical data. To develop the taxonomy, we analyzed the landscape of health CAs of the last 12 years by conducting a literature review. To form technical archetypes of health CAs, we deployed a cluster analysis and identified 4 CA archetypes. All these steps are shown in <xref rid="figure1" ref-type="fig">Figure 1</xref> [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Finally, we outlined practical implications and recommendations and discussed the approach.</p>
        <p>The contributions of this work are to (1) present a technical-oriented taxonomy for describing basic characteristics of health CAs, which will allow researchers in the field to classify their health CAs and compare them with others, which—once applied as a reporting guideline for health CAs—will allow users of health CAs to inform on important aspects related to a health CA, in particular on data processing, which will contribute to perceived safety; (2) provide an up-to-date review of health CAs; (3) identify design archetypes of health CAs required to define specific evaluation metrics for different archetypes; and (4) identify the main challenges and research directions for future work.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Overview of all research steps, applied research methods, and outputs of the methods [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. CA: conversational agent.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41583_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Taxonomy Development Procedure</title>
        <p>In this study, a taxonomy of technical characteristics for health CAs was developed based on scientific literature and empirical data. In this way, we pursued the goal of providing a systematic representation of technical characteristics of health CAs and developing a better understanding of technical elements of health CA design. Thus, our taxonomy also allowed for characterizing the current stage of the technology included in health CAs.</p>
        <p>The taxonomy development is an adaptation of the 7-step framework for taxonomy development proposed by Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>]. <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> lists these steps together with our adaptions. More details are given in the following sections.</p>
        <p>In a first step, we formulated the meta-characteristic, which is “the most comprehensive characteristic that will serve as the basis for the choice of characteristics in the taxonomy” [<xref ref-type="bibr" rid="ref18">18</xref>]. We defined the meta-characteristics as the technical characteristics of health CAs. We considered <italic>technical characteristics</italic> as distinctive technical features that frame the CA capabilities in terms of human interaction and conversation.</p>
        <p>The second step comprised the determination of ending conditions to finalize the iterative taxonomy development process. We considered 5 subjective ending conditions suggested by Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>] as our ending conditions (ie, the taxonomy should be concise, robust, comprehensive, extendable, and explanatory). As we did not apply the taxonomy to concrete health CA implementations, the other suggested ending conditions were irrelevant in our process. In the third step, we decided on the taxonomy development approach, which we determined to be conceptual to empirical. Therefore, in the fourth step, we abstracted a preliminary conceptual taxonomic structure based on the CA development experiences of the authors [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>] and existing research on health CAs [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. This taxonomy was discussed among all authors. In addition, it was discussed with 3 researchers working on health CAs. All characteristics of a dimension were considered as exclusive (ie, for a CA, only 1 characteristic can be true within 1 dimension). To assess whether the ending conditions were met, we used the taxonomy developed based on our experiences and applied it to health CA retrieved by the literature review (see <italic>Taxonomy Application</italic> section). When necessary, we included additional characteristics. The resulting taxonomy fulfilled the specified ending conditions.</p>
        <boxed-text id="box1" position="float">
          <title>The 7 steps for taxonomy development proposed by Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>] together with our adaptations.</title>
          <list list-type="bullet">
            <list-item>
              <p>The 7 steps by Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>]</p>
              <list>
                <list-item>
                  <p>Determine meta-characteristics</p>
                </list-item>
                <list-item>
                  <p>Determine ending conditions (Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>] suggest 7 subjective and 8 objective ending conditions)</p>
                </list-item>
                <list-item>
                  <p>Decide on approach (Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>] suggest 1 of 2 options: empirical to conceptual or conceptual to empirical)</p>
                </list-item>
                <list-item>
                  <p>Conceptualize (new) characteristics and dimensions of objects</p>
                </list-item>
                <list-item>
                  <p>Examine objects for these characteristics and dimensions</p>
                </list-item>
                <list-item>
                  <p>Create (revised) taxonomy</p>
                </list-item>
                <list-item>
                  <p>Check whether ending conditions are met</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Adaptation in our work</p>
              <list>
                <list-item>
                  <p>The technical characteristics of health conversational agents (CAs) are considered meta-characteristics.</p>
                </list-item>
                <list-item>
                  <p>We consider 5 subjective ending conditions from the suggestions by Nickerson et al [<xref ref-type="bibr" rid="ref18">18</xref>]: taxonomy should be concise, robust, comprehensive, extendable, and explanatory.</p>
                </list-item>
                <list-item>
                  <p>We follow the approach conceptual to empirical.</p>
                </list-item>
                <list-item>
                  <p>A preliminary conceptual taxonomic structure is abstracted based on the authors’ health CA development experiences.</p>
                </list-item>
                <list-item>
                  <p>Characteristics and dimensions are added to the taxonomic structure based on the authors’ health CA development experiences.</p>
                </list-item>
                <list-item>
                  <p>Revision of the taxonomy is based on input from discussions with 3 experts.</p>
                </list-item>
                <list-item>
                  <p>The taxonomy is applied to the health CAs included in the review; additional characteristics are added when needed.</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Taxonomy Application</title>
        <p>To identify health CAs, we used a literature review following the guidelines by Kitchenham et al [<xref ref-type="bibr" rid="ref19">19</xref>]. We decided on a literature review for the following reasons: (1) identifying CAs in app stores is biased because of country restrictions (not all CAs are available in the app stores of a particular country); (2) we wanted to consider CAs of a certain quality, which can be expected when using literature databases that only include peer-reviewed publications; and (3) we needed technical implementation details that might be missing in descriptions of CAs in app stores. We searched for relevant scientific papers on PubMed, ACM Digital Library, and IEEE Xplore published between 2010 and 2022 and written in English. To identify appropriate literature, we defined the following search string:</p>
        <disp-quote>
          <p>(application OR app OR approach OR implementation) AND (chatbot OR bot OR conversation OR conversational user interface) AND (health OR healthcare) </p>
        </disp-quote>
        <p>As PubMed only lists publications from the medical domain, we excluded the terms “health OR healthcare” when searching PubMed. Only publications that were peer-reviewed conference papers or journal articles of original work were included. Furthermore, the publication had to present a concrete CA applied in health care. We excluded papers not dealing with a concrete health care–related CA or only describing the design process, as well as reviews and meta-analyses.</p>
        <p>The search was conducted on April 4 and 5, 2022, resulting in 212 papers from IEEE Xplore, 970 papers from ACM Digital Library, and 489 papers from PubMed (see the flowchart in <xref rid="figure2" ref-type="fig">Figure 2</xref>). After a first exclusion process, 13.11% (219/1671) of the retrieved items were assessed for eligibility by examining titles and abstracts, where each reviewer looked at half of the papers. In a second round, the full texts were carefully considered by the reviewers to confirm eligibility. Overall, we assessed 82.6% (181/219) of the papers and extracted the characteristics based on our taxonomy. When necessary, characteristics were added to the taxonomy. In more detail, 2 researchers went through the list of relevant CAs (split into 2 parts; each researcher assessed 1 part). Each CA was analyzed based on the descriptions in the related paper. Data reflecting information from our taxonomy were extracted and filled in a standardized Microsoft Excel (Microsoft Corp) spreadsheet.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Flowchart of the literature review.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41583_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Archetype Building</title>
        <p>To form unique archetypes, we implemented k-means (via scikit-learn in Python [version 3.9; Python Software Foundation]) as an unsupervised clustering algorithm to automatically recognize patterns in our extracted features [<xref ref-type="bibr" rid="ref25">25</xref>] based on their technical characteristics. First, the text values (ie, characteristics of the taxonomy) of 13 selected taxonomy dimensions were converted into representative numerical values. This step was required as the clustering algorithm required numerical data and our characteristics were textual. To mitigate the threat of affecting our results’ external validity, we excluded values of 4 out of 18 dimensions (ie, data privacy, data exchange, hosting, and internet access) because of a lack of information. For most cases (ie, data privacy, 157/173, 90.8%; data exchange, 120/173, 69.3%; hosting, 83/173, 48%; internet access 56/173, 32.4%; and sentiment analysis), we were unable to extract corresponding information on these categories from the papers (see the following section). In addition, we excluded the dimension sentiment analysis as it was recognized as insufficiently discriminative for archetype building; for 83.5% (145/173), the value was neglecting integration of sentiment analysis. The conversion was supervised by the second author, who also manually fixed incorrect assignments. Second, cluster seeds were initialized randomly according to a defined number of expected clusters. To generate an appropriate number of clusters while maximizing the distance between clusters, we used the elbow method [<xref ref-type="bibr" rid="ref26">26</xref>], suggesting 4 clusters as appropriate to our data set. Third, the Euclidean distance between each point and seed was calculated (ie, the smallest distance became part of the given seed). Fourth, after covering the data, the seeds were placed in the centroids of the clusters, becoming their representatives. Fifth, the numerical values were converted to their text values, again supervised and manually fixed by the second author.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Our taxonomy comprises 18 unique dimensions corresponding to 4 perspectives of technical characteristics (<xref ref-type="table" rid="table1">Table 1</xref>): agent appearance, domain, interaction, and data processing. Each dimension consists of 2 to 5 characteristics. The dimensions cover aspects related to the CA personality and its embodiment as well as several technical aspects such as hosting, internet access, privacy, application technology, or use of sentiment analysis methods. The complete data extraction table is available in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Final taxonomy of technical characteristics of health conversational agents (CAs) with 18 dimensions and corresponding characteristics; when applicable, the references indicate from which publications the characteristics were adapted.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="600"/>
            <col width="370"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Level 1 (perspective) and level 2 (dimension)</td>
                <td>Level 3 (characteristic)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>Agent appearance</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Personality of CA</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Simple</p>
                    </list-item>
                    <list-item>
                      <p>Complex</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Embodiment [<xref ref-type="bibr" rid="ref27">27</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>None</p>
                    </list-item>
                    <list-item>
                      <p>Avatar</p>
                    </list-item>
                    <list-item>
                      <p>Physical</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Application technology</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Virtual reality</p>
                    </list-item>
                    <list-item>
                      <p>Augmented reality</p>
                    </list-item>
                    <list-item>
                      <p>Vocal</p>
                    </list-item>
                    <list-item>
                      <p>Normal</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Intelligence framework [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Rule based</p>
                    </list-item>
                    <list-item>
                      <p>Self-learning</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sentiment or emotion detection [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Yes</p>
                    </list-item>
                    <list-item>
                      <p>No</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Setting</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Context [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>General-purpose</p>
                    </list-item>
                    <list-item>
                      <p>Domain-specific</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Service duration [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Ad hoc supporters</p>
                    </list-item>
                    <list-item>
                      <p>Persistent companions</p>
                    </list-item>
                    <list-item>
                      <p>Temporary advisors</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Human involvement</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Dyad</p>
                    </list-item>
                    <list-item>
                      <p>Triad</p>
                    </list-item>
                    <list-item>
                      <p>Quadriad</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Interaction</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Input mode and output mode [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Written</p>
                    </list-item>
                    <list-item>
                      <p>Spoken</p>
                    </list-item>
                    <list-item>
                      <p>Visual</p>
                    </list-item>
                    <list-item>
                      <p>Hybrid</p>
                    </list-item>
                    <list-item>
                      <p>Haptic</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Service channel [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Smartphone-embedded</p>
                    </list-item>
                    <list-item>
                      <p>Software</p>
                    </list-item>
                    <list-item>
                      <p>Social media</p>
                    </list-item>
                    <list-item>
                      <p>Website (web-based)</p>
                    </list-item>
                    <list-item>
                      <p>Smart speaker</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Device</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>PC</p>
                    </list-item>
                    <list-item>
                      <p>Mobile device</p>
                    </list-item>
                    <list-item>
                      <p>Both</p>
                    </list-item>
                    <list-item>
                      <p>Other</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Language [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Single language</p>
                    </list-item>
                    <list-item>
                      <p>Multilanguage</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Integration mode</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Stand-alone</p>
                    </list-item>
                    <list-item>
                      <p>Part of a system</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Data processing</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Internet access</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>On the web</p>
                    </list-item>
                    <list-item>
                      <p>Offline</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Hosting [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Local</p>
                    </list-item>
                    <list-item>
                      <p>Outsourced</p>
                    </list-item>
                    <list-item>
                      <p>Other</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Data exchange with third-party device or service</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Access</p>
                    </list-item>
                    <list-item>
                      <p>Storing</p>
                    </list-item>
                    <list-item>
                      <p>Both</p>
                    </list-item>
                    <list-item>
                      <p>None</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Data privacy</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Privacy policy</p>
                    </list-item>
                    <list-item>
                      <p>Data encryption</p>
                    </list-item>
                    <list-item>
                      <p>Both</p>
                    </list-item>
                    <list-item>
                      <p>Nothing</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Agent Appearance</title>
        <p>Considering a CA as a subject, we refer by agent appearance to the visual appearance but also to the intelligence or personality of a CA. The agent appearance can be categorized in 5 dimensions. The <italic>personality of the CA</italic> indicates the human likeness of a CA. The <italic>embodiment</italic> illustrates whether the CA is embodied (eg, by an avatar or even a robot). The <italic>application technology</italic> refers to the technological environment in which the CA is embedded. The <italic>intelligence framework</italic> indicates whether the CA is primarily based on rules or machine learning is applied [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. The dimension <italic>sentiment or emotion detection</italic> characterizes whether the CA can automatically detect users’ emotion or sentiment during an interaction [<xref ref-type="bibr" rid="ref28">28</xref>]. Sentiment analysis would be a prerequisite for being able to generate empathic responses to a particular user.</p>
      </sec>
      <sec>
        <title>Setting</title>
        <p>The setting perspective comprises 3 dimensions and characterizes how a CA is embedded in the environment of a user. The <italic>context</italic> illustrates whether the CA serves a specific domain or can interact on any topic with its users [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. <italic>Service duration</italic> [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] refers to the services offered by a CA. It can be either short-term or cover a longer period and be designed for solving a concrete, time-limited task or focus on a longer interaction. Ad hoc supporters are designed for a short, isolated, one-time–only interaction. Persistent companions are long-term CAs designed for longer, interdependent, and perpetual interactions. Conversation can develop into new directions proactively. Temporary advisors are medium-term CAs [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. <italic>Human involvement</italic> denotes whether the interaction is between a user and the agent or whether other individuals are involved in the human-agent interaction.</p>
      </sec>
      <sec>
        <title>Interaction</title>
        <p>The interaction perspective describes a CA in terms of the human-computer interaction. It comprises 5 dimensions. <italic>Input or output mode</italic> refers to the primary way in which a CA can interact with the user [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. <italic>Service channel</italic> characterizes where the CA is primarily embedded [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. A CA is deployed on a particular device; thus, we included the dimension <italic>device</italic>. Relying on language, a CA might support multiple languages or only one [<xref ref-type="bibr" rid="ref28">28</xref>]. This is expressed in the dimension <italic>language</italic>. The dimension <italic>integration mode</italic> indicates whether the CA is part of a system or works as a stand-alone application.</p>
      </sec>
      <sec>
        <title>Data Processing</title>
        <p>The fourth perspective refers to the processing of data by the CA. The dimension <italic>internet access</italic> indicates whether the CA works in web-based or offline mode (ie, requires internet access). <italic>Hosting</italic> characterizes the data hosting type used by the CA [<xref ref-type="bibr" rid="ref28">28</xref>]. CAs can exploit different services such as speech-to-text or text-to-speech services. They can also exchange data with other devices. The dimension <italic>data exchange with third-party services or devices</italic> denotes whether the CA stores or accesses data from or to third-party services or devices (eg, wearables or electronic health records). <italic>Data privacy</italic> refers to privacy aspects of the personal health data collected, stored, or processed by the CA.</p>
      </sec>
      <sec>
        <title>Application of the Taxonomy</title>
        <sec>
          <title>Overview</title>
          <p>In this section, we summarize the results when applying the taxonomy to the 181 health CAs that were identified in the literature review. <xref rid="figure3" ref-type="fig">Figure 3</xref> provides an overview of the characteristics of the health CAs. More details are provided in the next section.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Mapping of the conversational agents assessed to our taxonomy (N=173). The size of the outer fields corresponds to the number of agents with these features.</p>
            </caption>
            <graphic xlink:href="jmir_v25i1e41583_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Analyzed CAs</title>
          <sec>
            <title>Included Studies</title>
            <p><xref rid="figure4" ref-type="fig">Figure 4</xref> shows the distribution of the publication years of the 181 papers identified through the literature review. It can be seen that more papers were published since 2018. In 2011, 2012, and 2014, no papers were identified, and we collected 1.1% (2/181) of the papers from 2010 and 2016 and 2.8% (5/181) from 2017. The number of publications increased suddenly in 2021 from 21 to 96. We note that the drop in 2022 results from the search date, which was in April 2022. Accordingly, we are aware that 2022 cannot be included in the trend analysis of the increased number of publications (compared with 2021).</p>
            <p>Of the 181 papers from which data were extracted, we identified 173 (95.6%) unique CAs as, for some CAs, more than one paper was included in the review. The results including the references of the considered CAs will be published as a replication package. With these 173 systems, we demonstrated the application of the taxonomy and characterized the landscape of health CAs from a technical perspective. In the following sections, we describe the characteristics of the assessed CAs according to our taxonomy.</p>
            <fig id="figure4" position="float">
              <label>Figure 4</label>
              <caption>
                <p>Distribution of the included publications on health conversational agents over the years.</p>
              </caption>
              <graphic xlink:href="jmir_v25i1e41583_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
          <sec>
            <title>Agent Appearance</title>
            <p>In the <italic>intelligence framework</italic> dimension, which corresponds to the <italic>agent appearance</italic> perspective, most (100/173, 57.8%) of the CAs investigated tended to function based on rules, and 39.3% (68/173) applied machine learning. For 2.9% (5/173), no information could be identified. Consistently with this, sentiment analysis was not integrated in most of the CAs (145/173, 83.8%). Only 14.5% (25/173) used sentiment analysis techniques (there was no information for 3/173, 1.7%). In the <italic>personality</italic> dimension, we recognized that 86.7% (150/173) of the CAs were implemented with a simple personality, and 11% (19/173) were implemented with a complex personality. For 2.3% (4/173), information on the CA personality was unavailable. Most (143/173, 82.7%) CAs were implemented without embodiment, 12.7% (22/173) were implemented as avatars, and 4.6% (8/173) were realized with physical embodiment of the agent. In the <italic>application technology</italic> dimension, most (155/173, 89.5%) CAs applied normal technologies (ie, text-based or standard graphical user interface); 6.9% (12/173) applied virtual reality (VR); 0.6% (1/173) applied augmented reality; 1.2% (2/173 applied vocal technologies; and for 1.7% (3/173) of the CAs, we could not identify the application technology.</p>
          </sec>
          <sec>
            <title>Setting</title>
            <p>In terms of the <italic>context</italic> dimension, most (155/173, 89.6%) CAs were clearly domain specific. A total of 10.4% (18/173) were general-purpose CAs. The service duration was short-term or medium-term—we identified ad hoc supporters (81/173, 46.8%), persistent companions (26/173, 15%), and temporary advisors (65/173, 37.6%); no decision was possible for 0.6% (1/173) of the CAs. Human involvement mainly focused on a single user who interacts with the CA (160/173, 92.5%). In total, 4.6% (8/173) of the CAs involved a clinician [<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref35">35</xref>]. Either the clinician was enabled to access the conversation protocol or they were able to interact with the patient through the chat interface. In total, 1.2% (2/173) of the systems were designed for children. In the latter systems, parents and physicians were enabled to join the system and review the conversation between the children and CAs or interact with the children [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. Another set of systems (5/173, 2.9%) enabled conversations between the CA and multiple users, whether communities of patients or several clinicians [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
          </sec>
          <sec>
            <title>Interaction</title>
            <p>A total of 90% (156/173) of the CAs were only able to talk and understand a single language. Most systems relied on written input (113/173, 65.5%) and output (102/173, 58.8%). Several options (ie, a hybrid interaction mode for input and output) were reported for 25% (45/173; input) and 35% (61/173; output) of the CAs. A total of 4.6% (8/173) of the CAs only used speech as input and output. Visual interaction was reported for 2.3% (4/173) of the CAs as input and 0.6% (1/173) of the CAs as output. In total, 0.6% (1/173) of the CAs allowed for haptic input [<xref ref-type="bibr" rid="ref39">39</xref>].</p>
            <p>In terms of the <italic>service channel</italic> dimension, CAs were made available mainly through smartphones (76/173, 43.9%), were integrated into social media messengers (36/173, 20.8%), or were accessible through websites (42/173, 24.3%). A minority of CAs were available through smart speakers (2/173, 1.2%; [<xref ref-type="bibr" rid="ref40">40</xref>]); no corresponding information was available for 9.8% (17/173). Most (106/173, 61.3%) were implemented as stand-alone systems; 29% (51/173) were part of a system; and for 9.2% (16/173), no information regarding the <italic>integration mode</italic> dimension was available. The most prominent device through which CAs could be accessed were mobile devices (128/173, 74%), 13.9% (24/173) of the systems were accessible through a PC, and 4% (7/173) were accessible through other devices. In total, 1.2% (2/173) of CAs accessible through PC and mobile devices were identified. Information was missing for 6.9% (12/173) of the CAs.</p>
          </sec>
          <sec>
            <title>Data Processing</title>
            <p>Information on data privacy, hosting, and data exchange with other systems was rarely described for the CAs assessed. In total, 90.1% (157/173) of the papers did not mention how data privacy was addressed. For 4.6% (8/173) of the CAs, a privacy policy was mentioned; 0.6% (1/181) of the papers reported on applied data encryption; and 3.9% (7/181) of the papers reported both a privacy policy and data encryption to be implemented in their CAs. In total, 60.1% (104/173) of the CAs ran on the web, thus requiring internet access; 7.5% (13/173) ran offline; and for 31.4% (56/173), we could not extract the corresponding information. Furthermore, information on data access and storing and the use of third-party devices and services was rare. For 69% (120/173) of the CAs, no information on this was available. A total of 14.5% (25/173) of the papers reported on access to third-party systems; 16% (28/173) reported on access and storage on third-party tools. Regarding the <italic>hosting</italic> dimension, for almost half (83/173, 48%) of the CAs, we could not identify related information; for 39% (68/173), we assumed that the CA hosting was outsourced given the information provided. Local hosting was identified for 12.7% (22/173) of the CAs.</p>
          </sec>
        </sec>
      </sec>
      <sec>
        <title>Technical Archetypes of CAs</title>
        <p>The clustering process resulted in 4 distinctive archetypes of health CAs (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). We named the archetypes as follows: (1) text-based ad hoc supporter; (2) multilingual, hybrid ad hoc supporter; (3) hybrid, single-language temporary advisor; and (4) embodied temporary advisor. The names reflect the main characteristics and the service duration. They have in common that they are mainly rule based and domain specific. Moreover, they are often implemented as stand-alone systems, and no additional users to the user and agent interact with each other. Note that we excluded 5 categories from the clustering because of missing information, namely, all dimensions of the <italic>data processing</italic> perspective (data privacy, hosting, data exchange, and internet access) and 1 dimension of the <italic>agent appearance</italic> perspective (sentiment analysis). Only 14.4% (25/173) of the systems integrated sentiment analysis—therefore, this was also not a distinctive feature for clustering. The results of the clustering can be found in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> and <xref rid="figure5" ref-type="fig">Figure 5</xref>.</p>
        <p>Archetypes 1 to 3 show a clear difference from archetype 4 in the 4 dimensions—<italic>personality</italic> (simple), <italic>embodiment</italic> (no), <italic>application technology</italic> (normal), and <italic>device</italic> (mobile device). The main difference of archetype 1 compared with the others is the service duration. A total of 50.5% (87/173) of the CAs assigned to this cluster were ad hoc supporters, and the input and output mode were written. For the other 3 archetypes, there was a larger variability in the service duration. Archetype 2 can be distinguished from the others via the multilingualism and a larger proportion of smartphone-embedded software as service channel. Archetype 4 differs from the others in the service channel, VR as application technology, and a complex personality. In <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, we summarize the characteristics per archetype.</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Radar charts of the 4 archetypes based on 4 clusters. Each chart shows the actual archetype characteristic fulfillment by all clusters (in percentages; the red points indicate nondominant characteristics), highlighting the dominant cluster the archetype is based on (blue line). VR: virtual reality.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41583_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <boxed-text id="box2" position="float">
          <title>Archetype characteristics.</title>
          <list list-type="bullet">
            <list-item>
              <p>Archetype 1: text-based ad hoc supporter (eg, Chetlen et al [<xref ref-type="bibr" rid="ref41">41</xref>])</p>
              <list>
                <list-item>
                  <p>The first group (107/181, 59.1% of conversational agents [CAs]) contains CAs that interact with users mainly via text input and output in 1 language. The CA personality is simple, without any kind of embodiment. The knowledge is domain specific, and most systems are rule based, run on a mobile device, and are implemented as stand-alone software. The interaction time is rather short—most systems are ad hoc supporters.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Archetype 2: multilingual, hybrid ad hoc supporter (eg, Horii et al [<xref ref-type="bibr" rid="ref42">42</xref>])</p>
              <list>
                <list-item>
                  <p>The second group (18/181, 9.9% of CAs) offers multiple input and output options and also covers multiple languages. Technical implementation is again rule based. The CA personality is simple, without embodiment. Running on a mobile device, it is mainly used as an ad hoc supporter. However, medium- and long-term service durations are also covered.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Archetype 3: hybrid, single-language temporary advisor (eg, van Baal et al [<xref ref-type="bibr" rid="ref43">43</xref>])</p>
              <list>
                <list-item>
                  <p>The third group (41/181, 22.7% of CAs) contains CAs that provide multiple input and output options but, again, only in 1 language. The interaction time is medium (ie, these systems are often temporary advisors), but they are also used as ad hoc supporters.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Archetype 4: embodied temporary advisor (eg, Tielman et al [<xref ref-type="bibr" rid="ref44">44</xref>])</p>
              <list>
                <list-item>
                  <p>The fourth group (15/181, 8.3% of CAs) of systems comprises CAs with complex personalities, with physical embodiments or avatars, and realized with virtual reality. In contrast to the other 3 archetypes, this group of CAs runs on websites, and a PC is often required. Data input and output is possible in multiple manners, but only 1 language is supported. Most of those systems have a medium-term use duration (ie, they are temporary advisors).</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Our research resulted in a taxonomy of technical characteristics for health CAs consisting of 18 dimensions that are grouped into 4 perspectives: agent appearance, setting, interaction, and data processing. Existing health CAs can be grouped into 4 archetypes, each of which has specific characteristics. The 4 archetypes are distinguished from each other in the input and output modalities, service duration, or support for multiple languages. One group of systems is more complex in terms of CA personality, which we labeled <italic>embodied temporary advisor</italic>.</p>
      </sec>
      <sec>
        <title>Theoretical and Practical Implications</title>
        <p>We developed a domain-specific taxonomy characterizing health CAs from a technical perspective. The taxonomy can be used as a reporting guideline by researchers and developers to describe essential details of their health CAs. This would ensure that details of the technical implementations are provided in a harmonized manner. From a research perspective, this would support the comparison of health CAs addressing the same use case. From a health CA user perspective, it ensures the transparency of the underlying technologies. It allows for the better judgment of the underlying technology and data processing of the health CA that a user is supposed to interact with. In particular, transparency related to data processing could contribute to perceived user safety. However, it would require technical knowledge to understand the characteristics. From a developer perspective, the application of the taxonomy allows for the classification of a system into one of the design archetypes. It would also help possibly associate technical implementations to outcomes and compare outcomes of different CAs relating to the technical criteria. As exemplified, questions such as the following—“For which use cases machine learning integrated in a health CA is useful”—could be answered.</p>
        <p>Other researchers have so far focused on other aspects of health CAs, such as CA platforms [<xref ref-type="bibr" rid="ref14">14</xref>] or the time dimension [<xref ref-type="bibr" rid="ref9">9</xref>], or on a domain-independent taxonomy [<xref ref-type="bibr" rid="ref7">7</xref>]. Some of our results are comparable with the results of other researchers. Janssen et al [<xref ref-type="bibr" rid="ref7">7</xref>], for example, found that, in most cases, CAs (without specific focus on health care) are rule based, only 1 individual participant interacts with the CA, and the CAs are without embodiment. This also holds true for our results. However, in contrast to their results, health CAs in our study seemed to be distributed as smartphone-embedded software rather than through social media. We can explain this by the requirements regarding data privacy that have to be considered in health care applications. Nissen et al [<xref ref-type="bibr" rid="ref9">9</xref>] focused in their archetypes on domain-specific, text-based chatbots and the time dimensions. We considered their results in our taxonomy by including the dimension <italic>service duration</italic>. Our archetypes also reflect the time dimension of the interaction [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
        <p>In total, 3 out of 4 archetypes are quite similar (archetypes 1, 2, and 3). However, they differ in the length of interaction (ad hoc supporter vs temporary advisor), input and output options, and number of supported languages. Most (107/181, 59.1%) CAs were assigned to archetype 1 (simple, text-based ad hoc supporter). The second most frequently occurring systems fell into archetype 2, the simple, hybrid temporary advisor. The fourth archetype subsumes a different, unique group of systems that seem to be more complex. We argue that this archetype exemplifies the strong interconnection between the higher complexity of specific CA characteristics—such as personality, input and output options, embodiment, and application technology—and the device. In this context, it seems logical to implement an embodied avatar (possibly in combination with physical components) if the application is based on a complexly designed VR world, leading to more immersive effects for patients [<xref ref-type="bibr" rid="ref2">2</xref>]. Moreover, this is why it is conceivable that the more complex the CA is (ie, realization of an embodied CA in a VR), the more complex the system requirements are (ie, a PC is needed instead of a smartphone because of its limited resources). However, such complex applications will probably also run on smartphones in the future because of their increasing capabilities.</p>
        <p>Surprisingly, none of the archetypes represent systems based on machine learning (even though there were a few included in the literature review). CA systems are often labeled as “artificial intelligence,” but it turned out that most of the systems (100/173, 57.8%) were rule based with limited intelligence. A reason might be that self-learning systems are difficult to control and can result in unexpected behavior, which produces a risk for patient safety. Another reason might be that the use cases for which CAs are developed in health care do not produce a demand for sophisticated machine learning and can be realized much more easily using rules. Third, training data in terms of health care dialogs for the various use cases might be missing.</p>
        <p>Regarding the fulfillment of the dominant archetype characteristics by archetype-related publications (<xref rid="figure4" ref-type="fig">Figure 4</xref>), we can see that the actual fulfillment was not dominant (ie, &#62;50% fulfillment) for every characteristic. This finding leads to the fact that every archetype consists of a certain number of dominant or nondominant properties, giving every archetype a certain weight regarding specific characteristics (eg, complex personalities for archetype 4 but with a nondominant service duration). In addition, the publications referring to specific archetypes also fulfilled characteristics or combinations of specific characteristics of other archetypes, highlighting especially the similarities between archetype 1 and archetype 3 but also general similarities among all archetypes (eg, in the context of domain-specific, stand-alone CAs).</p>
        <p>We found that much important information concerning the data processing of the CAs was missing in the publications. When information on data exchange with integrated third-party services or other things is missing, it is impossible to carefully judge the security risks. Therefore, we highly recommend that researchers exploit the taxonomy also as a reporting guideline when publishing on health CAs. Information on data privacy, security, and overall data processing is essential for generating trust in users, which might be important once such CAs become included in treatment workflows.</p>
      </sec>
      <sec>
        <title>Limitations and Further Research</title>
        <p>Our research does not come without limitations. The classification of CAs from the literature required some interpretation as aspects such as hosting or data privacy were not clearly described. A unified terminology and a minimal data set of what should be reported on health CAs would help not only in grouping systems but also in judging their reliability. Therefore, the results depend on our understanding and interpretation of the literature base and, thus, possibly affect the internal validity. Although we have profound knowledge in the field of CAs, there is no guarantee of the “objective validity” of the k-means clusters. Consequently, the external validation of the clusters has to be a next step. Therefore, we highly encourage future research to challenge and enhance our classification system with different design characteristics.</p>
        <p>Furthermore, the reviewed papers did not contain all the information required by our taxonomy. We were also interested in information on hosting, data privacy, or data exchange with third-party devices or services. We recognized that this information was missing in most publications (hosting 83/173, 48%, data privacy 157/173, 90.8%, and data exchange 120/173, 69.3%), although it is more important than ever for the successful transfer of CAs into actual practice [<xref ref-type="bibr" rid="ref20">20</xref>]. Therefore, we ignored these characteristics in our clustering analysis. In addition, k-means clustering has some weaknesses (eg, we had to define the optimal number of clusters in advance, and the algorithm is sensitive to outliers). Future research should investigate the role and nature of objects that do not entirely fit into one of the clusters. Despite all limitations, we argue that our results reveal useful and highly valuable archetypes for health-related CAs, and to the best of our knowledge, this study is the first of its kind focusing on technical aspects.</p>
        <p>For taxonomy building, we selected characteristics and dimensions that are of particular interest in health care settings to ensure data privacy and patient safety (eg, information on access to the internet, integration mode, and data privacy) and that also affect a technical evaluation. It is impossible to affirm the completeness of our taxonomy—technology is changing quickly, and it might become necessary to include additional characteristics or even dimensions. The taxonomy could also be used as a blueprint when designing a health intervention that exploits a CA. The taxonomy was generated in a pragmatic manner, and it is not yet validated. The number of categories remained the same during the process, but a few characteristics were added to the categories if needed during the annotation process. However, this procedure has no impact on the clustering as clustering was conducted after the manual annotation regarding our taxonomy was completed.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this paper, we presented a technical-oriented CA taxonomy for characterizing health CAs. A CA is considered from 4 perspectives: agent appearance, setting, interaction, and data processing. Using 13 relevant characteristics out of the 18 characteristics forming the taxonomy, 4 archetypes of health-related CAs were identified based on 173 unique CAs and using a k-means cluster analysis. We identified that the time dimension matters from a technical perspective to distinguish between archetypes. Moreover, we were able to identify additional distinctive, dominant, and nondominant characteristics that are relevant when evaluating health-related CAs (eg, input and output options or the complexity of the CA personality). Our archetypes reflect the current landscape of health CAs. With an increase in research interest in this field, which was already reflected in the literature review, we expect that more complex systems will arise. The archetype-building process would have to be repeated after some time to check whether new design archetypes come up.</p>
        <p>The resulting archetypes can be used to specify a set of technical metrics for their evaluation from a technical perspective. A careful technical evaluation of a health CA should take place before a clinical trial is conducted or the CA is used in an uncontrolled setting. In a next step, we will combine the archetypes and our previous work on technical evaluation metrics for health CAs [<xref ref-type="bibr" rid="ref45">45</xref>] to define a specific set of technical evaluation metrics for each of our 4 archetypes.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Data extraction table.</p>
        <media xlink:href="jmir_v25i1e41583_app1.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 124 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Results of the cluster analysis. Highlighted in gray are characteristics that contributed to &#62;50% of the conversational agents assigned to this cluster. Not considered in the clustering are sentiment and all dimensions of data processing (internet access, hosting, access to third-party services, and data privacy).</p>
        <media xlink:href="jmir_v25i1e41583_app2.docx" xlink:title="DOCX File , 23 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">CA</term>
          <def>
            <p>conversational agent</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">VR</term>
          <def>
            <p>virtual reality</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Amisha</collab>
            <name name-style="western">
              <surname>Malik</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pathania</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rathaur</surname>
              <given-names>VK</given-names>
            </name>
          </person-group>
          <article-title>Overview of artificial intelligence in medicine</article-title>
          <source>J Family Med Prim Care</source>
          <year>2019</year>
          <month>07</month>
          <volume>8</volume>
          <issue>7</issue>
          <fpage>2328</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jfmpc.com/article.asp?issn=2249-4863;year=2019;volume=8;issue=7;spage=2328;epage=2331;aulast=Amisha%2C"/>
          </comment>
          <pub-id pub-id-type="doi">10.4103/jfmpc.jfmpc_440_19</pub-id>
          <pub-id pub-id-type="medline">31463251</pub-id>
          <pub-id pub-id-type="pii">JFMPC-8-2328</pub-id>
          <pub-id pub-id-type="pmcid">PMC6691444</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>May</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Extending patient education with CLAIRE: an interactive virtual reality and voice user interface application</article-title>
          <source>Proceedings of the 15th European Conference on Technology Enhanced Learning: Addressing Global Challenges and Quality Education</source>
          <year>2020</year>
          <conf-name>EC-TEL '20</conf-name>
          <conf-date>September 14-18, 2020</conf-date>
          <conf-loc>Heidelberg, Germany</conf-loc>
          <fpage>482</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-030-57717-9_49</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>Larbi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gabarron</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Usability testing of a social media chatbot for increasing physical activity behavior</article-title>
          <source>J Pers Med</source>
          <year>2022</year>
          <month>05</month>
          <day>20</day>
          <volume>12</volume>
          <issue>5</issue>
          <fpage>828</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=jpm12050828"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/jpm12050828</pub-id>
          <pub-id pub-id-type="medline">35629252</pub-id>
          <pub-id pub-id-type="pii">jpm12050828</pub-id>
          <pub-id pub-id-type="pmcid">PMC9144074</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>Prochaska</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Chieng</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kendra</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baiocchi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pajarito</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A therapeutic relational agent for reducing problematic substance use (Woebot): development and usability study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>23</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e24850</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/3/e24850/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24850</pub-id>
          <pub-id pub-id-type="medline">33755028</pub-id>
          <pub-id pub-id-type="pii">v23i3e24850</pub-id>
          <pub-id pub-id-type="pmcid">PMC8074987</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>Gashi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Regli</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>May</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Tschopp</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Developing intelligent interviewers to collect the medical history: lessons learned and guidelines</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>05</month>
          <day>07</day>
          <volume>279</volume>
          <fpage>18</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210083</pub-id>
          <pub-id pub-id-type="medline">33965913</pub-id>
          <pub-id pub-id-type="pii">SHTI210083</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>Bickmore</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Giorgino</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Health dialog systems for patients and consumers</article-title>
          <source>J Biomed Inform</source>
          <year>2006</year>
          <month>10</month>
          <volume>39</volume>
          <issue>5</issue>
          <fpage>556</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(05)00141-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2005.12.004</pub-id>
          <pub-id pub-id-type="medline">16464643</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(05)00141-3</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>Janssen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Passlick</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cardona</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Breitner</surname>
              <given-names>MH</given-names>
            </name>
          </person-group>
          <article-title>Virtual assistance in any context: a taxonomy of design elements for domain-specific chatbots</article-title>
          <source>Bus Inf Syst Eng</source>
          <year>2020</year>
          <month>04</month>
          <day>06</day>
          <volume>62</volume>
          <issue>3</issue>
          <fpage>211</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1007/s12599-020-00644-1</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>Trofymenko</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Prokop</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zadereyko</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Loginova</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Classification of chatbots</article-title>
          <source>Syst Technol</source>
          <year>2022</year>
          <month>03</month>
          <day>30</day>
          <volume>2</volume>
          <issue>139</issue>
          <fpage>147</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.34185/1562-9945-2-139-2022-14</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>Nißen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Selimi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Janssen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cardona</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Breitner</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>von Wangenheim</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>See you soon again, chatbot? A design taxonomy to characterize user-chatbot relationships with different time horizons</article-title>
          <source>Comput Human Behav</source>
          <year>2022</year>
          <month>02</month>
          <volume>127</volume>
          <fpage>107043</fpage>
          <pub-id pub-id-type="doi">10.1016/j.chb.2021.107043</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>Welivita</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pu</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A taxonomy of empathetic response intents in human social conversations</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <month>12</month>
          <day>07</day>
        </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>Feine</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gnewuch</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Morana</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Maedche</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A taxonomy of social cues for conversational agents</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>2019</year>
          <month>12</month>
          <volume>132</volume>
          <fpage>138</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijhcs.2019.07.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vaidyam</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Wisniewski</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Halamka</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Kashavan</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Torous</surname>
              <given-names>JB</given-names>
            </name>
          </person-group>
          <article-title>Chatbots and conversational agents in mental health: a review of the psychiatric landscape</article-title>
          <source>Can J Psychiatry</source>
          <year>2019</year>
          <month>07</month>
          <volume>64</volume>
          <issue>7</issue>
          <fpage>456</fpage>
          <lpage>64</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30897957"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/0706743719828977</pub-id>
          <pub-id pub-id-type="medline">30897957</pub-id>
          <pub-id pub-id-type="pmcid">PMC6610568</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>Tudor Car</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dhinagaran</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Kyaw</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Joty</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Theng</surname>
              <given-names>YL</given-names>
            </name>
            <name name-style="western">
              <surname>Atun</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Conversational agents in health care: scoping review and conceptual analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>08</month>
          <day>07</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>e17158</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/8/e17158/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17158</pub-id>
          <pub-id pub-id-type="medline">32763886</pub-id>
          <pub-id pub-id-type="pii">v22i8e17158</pub-id>
          <pub-id pub-id-type="pmcid">PMC7442948</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Diederich</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Brendle</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Kolbe</surname>
              <given-names>LM</given-names>
            </name>
          </person-group>
          <article-title>Towards a taxonomy of platforms for conversational agent design</article-title>
          <source>Proceedings of the 14th International Conference on Wirtschaftsinformatik</source>
          <year>2019</year>
          <conf-name>WI '19</conf-name>
          <conf-date>February 24-27, 2019</conf-date>
          <conf-loc>Siegen, Germany</conf-loc>
          <fpage>1100</fpage>
          <lpage>14</lpage>
        </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>Diederich</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Brendel</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Morana</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kolbe</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>On the design of and interaction with conversational agents: an organizing and assessing review of human-computer interaction research</article-title>
          <source>J Assoc Inf Syst</source>
          <year>2022</year>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>96</fpage>
          <lpage>138</lpage>
          <pub-id pub-id-type="doi">10.17705/1jais.00724</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bahja</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lowry</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Toward a taxonomy of service-oriented chatbots</article-title>
          <source>Proceedings of the 20th Annual Pre-ICIS Workshop on HCI Research in MIS</source>
          <year>2021</year>
          <conf-name>ICIS '21</conf-name>
          <conf-date>December 12, 2021</conf-date>
          <conf-loc>Austin, TX, USA</conf-loc>
          <fpage>1</fpage>
          <lpage>4</lpage>
        </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>Jovanovic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Casati</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Chatbots as conversational healthcare services</article-title>
          <source>IEEE Internet Comput</source>
          <year>2020</year>
          <month>11</month>
          <day>11</day>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>44</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1109/mic.2020.3037151</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>Nickerson</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Varshney</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Muntermann</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A method for taxonomy development and its application in information systems</article-title>
          <source>Eur J Inf Syst</source>
          <year>2013</year>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>336</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.1057/ejis.2012.26</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Budgen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brereton</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>Evidence-Based Software Engineering and Systematic Reviews</source>
          <year>2015</year>
          <publisher-loc>Boca Raton, FL, USA</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </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>May</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Security, privacy, and healthcare-related conversational agents: a scoping review</article-title>
          <source>Inform Health Soc Care</source>
          <year>2022</year>
          <month>04</month>
          <day>03</day>
          <volume>47</volume>
          <issue>2</issue>
          <fpage>194</fpage>
          <lpage>210</lpage>
          <pub-id pub-id-type="doi">10.1080/17538157.2021.1983578</pub-id>
          <pub-id pub-id-type="medline">34617857</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hochreutener</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Pöpel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>May</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Self-anamnesis with a conversational user interface: concept and usability study</article-title>
          <source>Methods Inf Med</source>
          <year>2018</year>
          <month>11</month>
          <volume>57</volume>
          <issue>5-06</issue>
          <fpage>243</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1055/s-0038-1675822</pub-id>
          <pub-id pub-id-type="medline">30875703</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>May</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Usability assessment of conversational agents in healthcare: a literature review</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <month>05</month>
          <day>25</day>
          <volume>294</volume>
          <fpage>169</fpage>
          <lpage>73</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220431</pub-id>
          <pub-id pub-id-type="medline">35612050</pub-id>
          <pub-id pub-id-type="pii">SHTI220431</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gnewuch</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Morana</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Maedche</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Towards designing cooperative and social conversational agents for customer service</article-title>
          <source>Proceedings of the 2017 International Conference on Information Systems</source>
          <year>2017</year>
          <month>12</month>
          <conf-name>ICIS '17</conf-name>
          <conf-date>December 27-29, 2017</conf-date>
          <conf-loc>Seoul, South Korea</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zierau</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wambsganss</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Janson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schöbel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Leimeister</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>The anatomy of user experience with conversational agents: a taxonomy and propositions of service clues</article-title>
          <source>Proceedings of the 2020 International Conference on Information Systems</source>
          <year>2021</year>
          <conf-name>ICIS '20</conf-name>
          <conf-date>December 13-16, 2020</conf-date>
          <conf-loc>Hyderabad, India</conf-loc>
        </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>Kanungo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mount</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Netanyahu</surname>
              <given-names>NS</given-names>
            </name>
            <name name-style="western">
              <surname>Piatko</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Silverman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>AY</given-names>
            </name>
          </person-group>
          <article-title>An efficient K-Means Clustering algorithm: analysis and implementation</article-title>
          <source>IEEE Trans Pattern Anal Machine Intell</source>
          <year>2002</year>
          <month>07</month>
          <volume>24</volume>
          <issue>7</issue>
          <fpage>881</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1109/tpami.2002.1017616</pub-id>
        </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>Kodinariya</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Makwana</surname>
              <given-names>PR</given-names>
            </name>
          </person-group>
          <article-title>Review on determining number of cluster in K-Means Clustering</article-title>
          <source>Int J Adv Res Comput Sci Manag Stud</source>
          <year>2013</year>
          <month>11</month>
          <volume>1</volume>
          <issue>6</issue>
          <fpage>90</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/profile/Trupti-Kodinariya/publication/313554124_Review_on_Determining_of_Cluster_in_K-means_Clustering/links/5789fda408ae59aa667931d2/Review-on-Determining-of-Cluster-in-K-means-Clustering.pdf"/>
          </comment>
        </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>Abd-Alrazaq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Safi</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Alajlani</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Warren</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Househ</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Technical metrics used to evaluate health care chatbots: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>06</month>
          <day>05</day>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>e18301</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/6/e18301/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18301</pub-id>
          <pub-id pub-id-type="medline">32442157</pub-id>
          <pub-id pub-id-type="pii">v22i6e18301</pub-id>
          <pub-id pub-id-type="pmcid">PMC7305563</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>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>AY</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>58</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="ref29">
        <label>29</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Knote</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Janson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Söllner</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Leimeister</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Classifying smart personal assistants: an empirical cluster analysis</article-title>
          <source>Proceedings of the 2019 Hawaii Conference on System Sciences</source>
          <year>2019</year>
          <conf-name>HICSS '19</conf-name>
          <conf-date>January 8-11, 2019</conf-date>
          <conf-loc>Maui, HI, USA</conf-loc>
          <pub-id pub-id-type="doi">10.24251/hicss.2019.245</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>Ganapathy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>KC</given-names>
            </name>
          </person-group>
          <article-title>Acute paediatrics tele-support for caregivers in Singapore: an initial experience with a prototype Chatbot: UPAL</article-title>
          <source>Singapore Med J (forthcoming)</source>
          <year>2021</year>
          <month>09</month>
          <day>28</day>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.11622/smedj.2021119"/>
          </comment>
          <pub-id pub-id-type="doi">10.11622/smedj.2021119</pub-id>
          <pub-id pub-id-type="medline">34581468</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>Piau</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Crissey</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Brechemier</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Balardy</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Nourhashemi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>A smartphone Chatbot application to optimize monitoring of older patients with cancer</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>08</month>
          <volume>128</volume>
          <fpage>18</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.05.013</pub-id>
          <pub-id pub-id-type="medline">31160007</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(19)30210-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Swamy</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Kurapothula</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Murthy</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Harini</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>RaviKumar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kashyap</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Voice assistant and facial analysis based approach to screen test clinical depression</article-title>
          <source>Proceedings of the 1st International Conference on Advances in Information Technology</source>
          <year>2019</year>
          <conf-name>ICAIT '19</conf-name>
          <conf-date>July 25-27, 2019</conf-date>
          <conf-loc>Chikmagalur, India</conf-loc>
          <fpage>39</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.1109/icait47043.2019.8987301</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yen</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kavak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>JY</given-names>
            </name>
          </person-group>
          <article-title>STEMI recognition in electrocardiogram (ECG) by online AI bot for emergency service and mobile medicine</article-title>
          <source>Proceedings of the 30th Wireless and Optical Communications Conference</source>
          <year>2021</year>
          <month>10</month>
          <conf-name>WOCC '21</conf-name>
          <conf-date>October 7-8, 2021</conf-date>
          <conf-loc>Taipei, Taiwan</conf-loc>
          <fpage>142</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9603013"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/wocc53213.2021.9603013</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>Nazareth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hayward</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Simmons</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Snir</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hatchell</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Rojahn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Slotnick</surname>
              <given-names>RN</given-names>
            </name>
            <name name-style="western">
              <surname>Nussbaum</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Hereditary cancer risk using a genetic chatbot before routine care visits</article-title>
          <source>Obstet Gynecol</source>
          <year>2021</year>
          <month>12</month>
          <day>01</day>
          <volume>138</volume>
          <issue>6</issue>
          <fpage>860</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34735417"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/AOG.0000000000004596</pub-id>
          <pub-id pub-id-type="medline">34735417</pub-id>
          <pub-id pub-id-type="pii">00006250-202112000-00007</pub-id>
          <pub-id pub-id-type="pmcid">PMC8594498</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>Hungerbuehler</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Daley</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cavanagh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia Claro</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kapps</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Chatbot-based assessment of employees' mental health: design process and pilot implementation</article-title>
          <source>JMIR Form Res</source>
          <year>2021</year>
          <month>04</month>
          <day>21</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e21678</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2021/4/e21678/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21678</pub-id>
          <pub-id pub-id-type="medline">33881403</pub-id>
          <pub-id pub-id-type="pii">v5i4e21678</pub-id>
          <pub-id pub-id-type="pmcid">PMC8100879</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>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schachner</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Harperink</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Barata</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Dittler</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Stanger</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wangenheim</surname>
              <given-names>FV</given-names>
            </name>
            <name name-style="western">
              <surname>Fleisch</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Oswald</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Möller</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Conversational agents as mediating social actors in chronic disease management involving health care professionals, patients, and family members: multisite single-arm feasibility study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>02</month>
          <day>17</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>e25060</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/2/e25060/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25060</pub-id>
          <pub-id pub-id-type="medline">33484114</pub-id>
          <pub-id pub-id-type="pii">v23i2e25060</pub-id>
          <pub-id pub-id-type="pmcid">PMC7929753</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>Beilharz</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sukunesan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rossell</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Kulkarni</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Development of a positive body image chatbot (KIT) with young people and parents/carers: qualitative focus group study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>06</month>
          <day>16</day>
          <volume>23</volume>
          <issue>6</issue>
          <fpage>e27807</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/6/e27807/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27807</pub-id>
          <pub-id pub-id-type="medline">34132644</pub-id>
          <pub-id pub-id-type="pii">v23i6e27807</pub-id>
          <pub-id pub-id-type="pmcid">PMC8277317</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>Morris</surname>
              <given-names>RR</given-names>
            </name>
            <name name-style="western">
              <surname>Kouddous</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kshirsagar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Schueller</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Towards an artificially empathic conversational agent for mental health applications: system design and user perceptions</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>06</month>
          <day>26</day>
          <volume>20</volume>
          <issue>6</issue>
          <fpage>e10148</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/6/e10148/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10148</pub-id>
          <pub-id pub-id-type="medline">29945856</pub-id>
          <pub-id pub-id-type="pii">v20i6e10148</pub-id>
          <pub-id pub-id-type="pmcid">PMC6039770</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>Bickmore</surname>
              <given-names>TW</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Jack</surname>
              <given-names>BW</given-names>
            </name>
            <name name-style="western">
              <surname>Paasche-Orlow</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeifer</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Odonnell</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Response to a relational agent by hospital patients with depressive symptoms</article-title>
          <source>Interact Comput</source>
          <year>2010</year>
          <month>07</month>
          <day>1</day>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>289</fpage>
          <lpage>98</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20628581"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.intcom.2009.12.001</pub-id>
          <pub-id pub-id-type="medline">20628581</pub-id>
          <pub-id pub-id-type="pmcid">PMC2901553</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Qui</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kanski</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Doerksen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Winkels</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitz</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Abdullah</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Nurse AMIE: using smart speakers to provide supportive care intervention for women with metastatic breast cancer</article-title>
          <source>Extended Abstracts of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          <year>2021</year>
          <month>05</month>
          <conf-name>CHI EA '21</conf-name>
          <conf-date>May 8-13, 2021</conf-date>
          <conf-loc>Yokohama, Japan</conf-loc>
          <fpage>1</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1145/3411763.3451827</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chetlen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Artrip</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Drury</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Arbaiza</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Novel use of chatbot technology to educate patients before breast biopsy</article-title>
          <source>J Am Coll Radiol</source>
          <year>2019</year>
          <month>09</month>
          <volume>16</volume>
          <issue>9 Pt B</issue>
          <fpage>1305</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/31492408/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacr.2019.05.050</pub-id>
          <pub-id pub-id-type="medline">31492408</pub-id>
          <pub-id pub-id-type="pii">S1546-1440(19)30702-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Horii</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Sakurai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sakurai</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tsuruta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Knauf</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Damiani</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kutics</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>More general evaluation of a client-centered counseling agent</article-title>
          <source>Proceedings of the 2019 IEEE World Congress on Services</source>
          <year>2019</year>
          <month>08</month>
          <day>29</day>
          <conf-name>SERVICES '19</conf-name>
          <conf-date>July 8-13, 2019</conf-date>
          <conf-loc>Milan, Italy</conf-loc>
          <fpage>190</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/services.2019.00052</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van Baal</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Le</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fatehi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hohwy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Verdejo-Garcia</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Cory COVID-Bot: an evidence-based behavior change chatbot for COVID-19</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <month>01</month>
          <day>14</day>
          <volume>289</volume>
          <fpage>422</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/35062181/"/>
          </comment>
          <pub-id pub-id-type="doi">10.3233/SHTI210948</pub-id>
          <pub-id pub-id-type="medline">35062181</pub-id>
          <pub-id pub-id-type="pii">SHTI210948</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tielman</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Neerincx</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Bidarra</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kybartas</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Brinkman</surname>
              <given-names>WP</given-names>
            </name>
          </person-group>
          <article-title>A therapy system for post-traumatic stress disorder using a virtual agent and virtual storytelling to reconstruct traumatic memories</article-title>
          <source>J Med Syst</source>
          <year>2017</year>
          <month>08</month>
          <volume>41</volume>
          <issue>8</issue>
          <fpage>125</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28699083"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-017-0771-y</pub-id>
          <pub-id pub-id-type="medline">28699083</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-017-0771-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC5506234</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Denecke</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Abd-Alrazaq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Househ</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Warren</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Evaluation metrics for health chatbots: a Delphi study</article-title>
          <source>Methods Inf Med</source>
          <year>2021</year>
          <month>12</month>
          <volume>60</volume>
          <issue>5-06</issue>
          <fpage>171</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1055/s-0041-1736664</pub-id>
          <pub-id pub-id-type="medline">34719011</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
