<?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">
<?covid-19-tdm?>
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</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">v9i3e40064</article-id>
      <article-id pub-id-type="pmid">35960593</article-id>
      <article-id pub-id-type="doi">10.2196/40064</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Patient Experience and Feedback After Using an Electronic Health Record–Integrated COVID-19 Symptom Checker: Survey Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Aboueid</surname>
            <given-names>Stephanie</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chrimes</surname>
            <given-names>Dillon</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Andrew W</given-names>
          </name>
          <degrees>BA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8033-2598</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Odisho</surname>
            <given-names>Anobel Y</given-names>
          </name>
          <degrees>MD, MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0975-0812</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Brown III</surname>
            <given-names>William</given-names>
          </name>
          <degrees>MA, DrPH, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4322-4859</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Gonzales</surname>
            <given-names>Ralph</given-names>
          </name>
          <degrees>MD, MSPH</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6061-7219</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Neinstein</surname>
            <given-names>Aaron B</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9774-7180</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Judson</surname>
            <given-names>Timothy J</given-names>
          </name>
          <degrees>MD, MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Center for Digital Health Innovation</institution>
            <institution>University of California, San Francisco</institution>
            <addr-line>1700 Owens St, Suite 541</addr-line>
            <addr-line>San Francisco, CA, 94158</addr-line>
            <country>United States</country>
            <phone>1 415 514 8755</phone>
            <email>timothy.judson@ucsf.edu</email>
          </address>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8376-6260</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Center for Digital Health Innovation</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Urology</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department of Medicine</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Bakar Computational Health Sciences Institute</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Clinical Innovation Center</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>Office of Population Health</institution>
        <institution>University of California, San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Timothy J Judson <email>timothy.judson@ucsf.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Jul-Sep</season>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>13</day>
        <month>9</month>
        <year>2022</year>
      </pub-date>
      <volume>9</volume>
      <issue>3</issue>
      <elocation-id>e40064</elocation-id>
      <history>
        <date date-type="received">
          <day>3</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>18</day>
          <month>7</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>20</day>
          <month>7</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>6</day>
          <month>8</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Andrew W Liu, Anobel Y Odisho, William Brown III, Ralph Gonzales, Aaron B Neinstein, Timothy J Judson. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 13.09.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2022/3/e40064" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Symptom checkers have been widely used during the COVID-19 pandemic to alleviate strain on health systems and offer patients a 24-7 self-service triage option. Although studies suggest that users may positively perceive web-based symptom checkers, no studies have quantified user feedback after use of an electronic health record–integrated COVID-19 symptom checker with self-scheduling functionality.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this paper, we aimed to understand user experience, user satisfaction, and user-reported alternatives to the use of a COVID-19 symptom checker with self-triage and self-scheduling functionality.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We launched a patient-portal–based self-triage and self-scheduling tool in March 2020 for patients with COVID-19 symptoms, exposures, or questions. We made an optional, anonymous Qualtrics survey available to patients immediately after they completed the symptom checker.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Between December 16, 2021, and March 28, 2022, there were 395 unique responses to the survey. Overall, the respondents reported high satisfaction across all demographics, with a median rating of 8 out of 10 and 288/395 (47.6%) of the respondents giving a rating of 9 or 10 out of 10. User satisfaction scores were not associated with any demographic factors. The most common user-reported alternatives had the web-based tool not been available were calling the COVID-19 telephone hotline and sending a patient-portal message to their physician for advice. The ability to schedule a test online was the most important symptom checker feature for the respondents. The most common categories of user feedback were regarding other COVID-19 services (eg, telephone hotline), policies, or procedures, and requesting additional features or functionality.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This analysis suggests that COVID-19 symptom checkers with self-triage and self-scheduling functionality may have high overall user satisfaction, regardless of user demographics. By allowing users to self-triage and self-schedule tests and visits, tools such as this may prevent unnecessary calls and messages to clinicians. Individual feedback suggested that the user experience for this type of tool is highly dependent on the organization's operational workflows for COVID-19 testing and care. This study provides insight for the implementation and improvement of COVID-19 symptom checkers to ensure high user satisfaction.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>COVID-19</kwd>
        <kwd>patient portals</kwd>
        <kwd>digital health</kwd>
        <kwd>diagnostic self evaluation</kwd>
        <kwd>medical informatics</kwd>
        <kwd>internet</kwd>
        <kwd>telemedicine</kwd>
        <kwd>triage</kwd>
        <kwd>feedback</kwd>
        <kwd>medical records systems</kwd>
        <kwd>San Francisco</kwd>
        <kwd>user experience</kwd>
        <kwd>user satisfaction</kwd>
        <kwd>self-triage</kwd>
        <kwd>symptom checker</kwd>
        <kwd>health system</kwd>
        <kwd>workflow</kwd>
        <kwd>feedback</kwd>
        <kwd>integration</kwd>
        <kwd>electronic health record</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>During the COVID-19 pandemic, symptom checkers have become an essential tool for providing patients with on-demand access to triage recommendations [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. These tools take patients through self-guided questions about demographics, symptoms, exposures, and past medical history and suggest a diagnosis or recommend a disposition. They employ algorithms and automation to connect patients to care without requiring intervention from clinical staff. COVID-19 symptom checkers have a variety of potential benefits. When used for triage, they may reduce the risk of COVID-19 transmission [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>] and provide patients with care advice more quickly and efficiently than other methods (ie, telephone hotlines) [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. When used for daily entry screening, they greatly reduce the need for staffing to conduct manual screens [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      </sec>
      <sec>
        <title>Symptom Checkers</title>
        <p>Symptoms checkers are widely considered to be popular with patients because they provide them with 24-7 access to health information, risk assessments, and in some cases, test and appointment scheduling. A handful of studies have reported moderately high user satisfaction ratings for COVID-19 symptom checkers. One study of 296 patients who were predominantly health care workers reported 56% found their institution’s internal web-based symptom checker tool useful [<xref ref-type="bibr" rid="ref11">11</xref>]. Symptom checkers for conditions other than COVID-19 have also reported positive user experiences, including 1 study reporting high satisfaction in 70%-80% of users [<xref ref-type="bibr" rid="ref9">9</xref>]. In a study of 22 college students, qualitative factors related to the decision to use publicly available symptom checkers included presence and knowledge of COVID-19 symptoms; fear of in-person health care services; awareness, paranoia, and curiosity; technical literacy; and acceptability [<xref ref-type="bibr" rid="ref10">10</xref>]. Reported negative characteristics of symptom checkers included doubting accuracy, limited symptom submission possibilities, and unclear logic model of symptom checker [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>While these studies suggest that users may positively perceive web-based symptom checkers, they are insufficient to understand the patient and tool characteristics that contribute to user experience. Furthermore, no studies have quantified user feedback after the use of an electronic health record (EHR)–integrated COVID-19 symptom checker with self-scheduling functionality. Symptom checkers that are EHR-integrated and offer self-scheduling may have higher user satisfaction because they decrease the time it takes for patients to be scheduled for necessary appointments or tests [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
        <p>As symptom checkers become more ubiquitous for COVID-19 and other use cases, it is important to understand user perceptions and to know which features make them attractive. This type of user feedback can inform product development and improvement for these symptom checkers and any other digital health tools. In addition, it is important to understand whether there are demographic differences that drive user perceptions of the tool, as these may impact health disparities.</p>
      </sec>
      <sec>
        <title>Patterns of Symptom Checker Usage</title>
        <p>At the University of California, San Francisco (UCSF), in March 2020, we launched one of the first COVID-19 symptom checkers with self-triage and self-scheduling capabilities. We designed a survey to collect feedback and user experience upon use. This is the first known study to conduct user research on an EHR-integrated symptom checker with self-scheduling functionality. Our primary aims in this analysis are to examine patterns in user experience and user satisfaction by demographic characteristics, determine what patients view as alternatives to symptom checker use, and gather actionable feedback for symptom checker improvements.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Setting</title>
        <p>UCSF Health is a large academic health system providing approximately 1.7 million outpatient visits annually. The UCSF primary care practices serve approximately 90,000 empaneled patients. As of January 2022, approximately 95% of adult primary care patients were enrolled in UCSF’s EHR-tethered patient portal.</p>
        <p>In early March 2020, UCSF established a COVID-19 telephone hotline, which became the primary telephone intake point for all UCSF patient and employee inquiries regarding COVID-19, including general questions, exposures, symptom assessments, and test scheduling requests.</p>
      </sec>
      <sec>
        <title>Symptom Checker Tool</title>
        <p>The UCSF COVID-19 Symptom Checker was developed as an EHR-tethered portal-based self-service option for patients with symptoms of or exposure to COVID-19 or those who are requesting a COVID-19 test. After answering a series of branched logic questions about exposures, symptoms, and comorbidities, patients are directed to the appropriate disposition based on their predicted risk level. The triage algorithm used in this tool was identical to the one used on the telephone hotline. UCSF uses a commercially available EHR from Epic Systems. In early March 2020, we used our EHR vendor’s configuration tools to design, configure, and deploy our UCSF COVID-19 Symptom Checker, which launched on March 12, 2020 [<xref ref-type="bibr" rid="ref6">6</xref>]. Patients could access the tool by logging into the patient portal on a smartphone, tablet, or computer and were directed to the tool from the hotline, primary care phone tree, and UCSF websites. The tool was available in English and Spanish—the two languages currently supported by our patient portal. The Symptom Checker was available to all adult patients at UCSF with active patient portal accounts [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
        <p>If appropriate based on their responses, patients could self-schedule SARS-CoV-2 RNA tests, video visits, or in-person appointments directly through the tool, as described previously [<xref ref-type="bibr" rid="ref6">6</xref>]. When patients chose to schedule their test or visit online, a scheduling tool opened within the Symptom Checker, displaying available appointments and allowing the patient to select one. If no appointments were available, patients were directed to call the telephone hotline.</p>
      </sec>
      <sec>
        <title>User Feedback Survey</title>
        <p>The optional, anonymous user feedback survey for the UCSF COVID-19 Symptom Checker was built on Qualtrics and consisted of 12 total questions (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). The survey link was embedded in the final screen of the tool, where patients were shown their care recommendation. The survey was optional, and there were no reminders or prompts to promote survey completion. Patients who did not complete the tool were not able to access the survey.</p>
        <p>We designed the survey to be lightweight and easy to complete. Questions were a combination of slider-style rating questions, multiple-choice, select-all-that-apply, and optional open-ended questions. Only the first question, in which patients were asked about their overall rating of the tool, was required. The patients were then asked to assess their agreement on Likert scale with statements describing their experience and about how they would have sought care had the tool not been available. Additionally, the participants were asked about the most important features to them and were able to comment on any technical difficulties experienced. The respondents were asked optional demographic questions on age, gender, ethnicity, and race.</p>
      </sec>
      <sec>
        <title>Study Population</title>
        <p>For this analysis, we included all adults who responded to the Qualtrics feedback survey from December 16, 2021, until March 28, 2022. A subanalysis of the peak of the omicron surge (December 16, 2021, to January 28, 2022) and its effect on patient satisfaction and experience was conducted. We defined the peak as the period during which the tool averaged over 200 unique users a day.</p>
      </sec>
      <sec>
        <title>Ethics Approval</title>
        <p>This study was approved by the UCSF Institutional Review Board (20-30903).</p>
      </sec>
      <sec>
        <title>Evaluation and Statistical Analysis</title>
        <p>Data were exported from the Qualtrics survey and analyzed using R 3.5.1 (The R Foundation). The participants’ longitude and latitude at the time of response based on Qualtrics estimation using respondent IP addresses were matched to respective census block tract and area deprivation index national percentile as a proxy for socioeconomic status [<xref ref-type="bibr" rid="ref12">12</xref>]. Descriptive statistics were used to analyze user responses. Differences in the user cohort based on responses were analyzed using the 2-tailed chi-squared test for categorical variables and the two-sample, 2-tailed <italic>t</italic> test for continuous variables. Visualizations were created using the <italic>ggplot2</italic> library. A multivariate linear regression analysis was performed with a primary outcome of user overall rating and the demographic questions of the survey. For the purposes of multivariate analysis, respondent ethnicity was stratified as non-Hispanic and Hispanic, and race was stratified as White and non-White. To assess the collinearity of covariates, variable inflation factors were calculated with a cutoff of &#60;10. Moreover, <italic>P</italic>&#60;.05 was considered significant.</p>
        <p>Constructive open-ended responses were assigned 1 of 10 categories by a physician reviewer who was familiar with the ambulatory COVID-19 care structure. We did not categorize responses that were purely complementary or that did not offer specific feedback.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Survey Response Data</title>
        <p>From December 16, 2021, until March 28, 2022, there were 395 total responses to the experience survey (<xref rid="figure1" ref-type="fig">Figure 1</xref>). During that time, the Symptom Checker was used 29,384 times for a response rate of 1.6%. The median 1-10 rating was 8 (IQR 3-10). In total, 182 users (46.1%) rated their overall experience 9 or 10. When asked how the Symptom Checker affected the overall care experience, about half of the users (n=178, 53.6%) responded that the COVID-19 Testing and Care Tool “improved my care experience,” 91 users (27.4%) responded that the tool “made no impact on my care experience,” and 63 users (19.0%) said the tool “worsened my care experience” (<xref rid="figure2" ref-type="fig">Figure 2</xref>). Most users strongly agreed (162/332, 48.8%) or agreed (44/332, 13.3%) that the tool “helped them get the care I needed,” while 23.1% (77/332) strongly disagreed.</p>
        <p>When asked about the most important feature of the tool, over half of the users (n=254, 64.3%) cited the ability to schedule their COVID-19 test online. The second most popular feature was 24-7 access to triage advice if they had COVID-19 symptoms or exposure (n=129, 32.6%; <xref rid="figure3" ref-type="fig">Figure 3</xref>). Most respondents (253/331, 76.4%) reported no technical difficulties while using the tool. The most commonly reported technical difficulty was problems with visit or test scheduling. When asked about usability, 52.4% (174/332) of users strongly agreed with the statement that “this tool was easy to use,” while 10.2% (34/332) of respondents strongly disagreed. Most respondents (208/332, 62.7%) strongly agreed with the statement that “questions were easy and clear to understand,” while 7.2% (24/332) strongly disagreed.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Overall user ratings of COVID-19 Symptom Checker (n=395).</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i3e40064_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Patient-reported impact of COVID-19 Symptom Checker on care experience (n=332).</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i3e40064_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Most important COVID-19 Symptom-Checker features (n=395). UCSF: University of California, San Francisco.</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i3e40064_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Omicron Surge Subanalysis</title>
        <p>There were 288 responses during the omicron surge from December 16, 2021, to January 28, 2022. The median 1-10 rating during that time was 8 (IQR 4-10), and 139 (48.2%) users gave the tool a rating of 9 or 10. There was no difference in overall rating for responses during the Omicron surge compared with before or after the Omicron surge (<italic>P</italic>=.86).</p>
      </sec>
      <sec>
        <title>Demographics</title>
        <p>Patient demographics of the survey respondents are summarized in <xref ref-type="table" rid="table1">Table 1</xref>. There were no significant differences in the user-reported care experience (“improved,” “made no impact,” or “worsened my care experience”) between cohorts by age, race, ethnicity, sex, or socioeconomic status (<xref ref-type="table" rid="table2">Table 2</xref>). A multivariate linear regression analysis similarly found no significant associations between user rating and respondent demographics and time frame of use. A subanalysis during the omicron peak found similar results.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Patient demographics (N=395).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="670"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Variable</td>
                <td>Value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">Average rating, median (IQR)</td>
                <td>8 (3-10)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Age (years), n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>18-39</td>
                <td>45 (11.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>40-59</td>
                <td>123 (31.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#62;60</td>
                <td>158 (40)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Race, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>White</td>
                <td>222 (56.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Black or African American</td>
                <td>11 (2.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Asian, Native Hawaiian or Other Pacific Islander</td>
                <td>51 (12.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>American Indian or Alaska Native</td>
                <td>5 (1.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Other or prefer not to answer</td>
                <td>37 (9.4)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Ethnicity, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Hispanic</td>
                <td>33 (8.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Non-Hispanic</td>
                <td>227 (57.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Prefer not to answer or unknown</td>
                <td>49 (12.4)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Sex, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td>94 (23.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td>221 (55.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Prefer not to answer</td>
                <td>9 (2.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Time frame, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Omicron</td>
                <td>288 (72.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Before or after Omicron</td>
                <td>107 (27.1)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Area deprivation index national percentile (IQR)</td>
                <td>3 (2-9)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Multivariable linear regression model to identify predictors of user rating.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="400"/>
            <col width="250"/>
            <col width="250"/>
            <col width="0"/>
            <col width="70"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Variable</td>
                <td>Estimate</td>
                <td>95% CI</td>
                <td colspan="2"><italic>P</italic> value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Age (vs 18-39)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>40-59</td>
                <td>–0.65</td>
                <td>–2.02, 0.72</td>
                <td colspan="2">.35</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#62;60</td>
                <td>0.13</td>
                <td>–1.25, 1.52</td>
                <td colspan="2">.85</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Male (vs female)</td>
                <td>0.08</td>
                <td>–0.91, 1.08</td>
                <td colspan="2">.87</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Non-White (vs White)</td>
                <td>0.79</td>
                <td>–0.23, 1.82</td>
                <td colspan="2">.13</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Non-Hispanic (vs Hispanic)</td>
                <td>–0.15</td>
                <td>–1.58, 1.28</td>
                <td colspan="2">.84</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Area deprivation index</td>
                <td>–0.02</td>
                <td>–0.04, 0.00</td>
                <td colspan="2">.09</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Alternatives to Care</title>
        <p>Respondents gave a wide variety of answers when asked what they would have done if they did not have access to the web-based tool (<xref rid="figure4" ref-type="fig">Figure 4</xref>). The most common response was calling the COVID-19 telephone hotline (n=134, 33.9%), followed by sending a patient portal message to their physician (n=104, 26.3%) and calling their primary care clinic for advice (n=96, 24.3%).</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Patient-reported alternatives to COVID-19 Symptom Checker use (n=395).</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i3e40064_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Open-ended Feedback</title>
        <p>The most common categories of open-ended feedback were as follows: (1) requested changes to other COVID-19 services (eg, telephone hotline), policies, or procedures; (2) request for additional tool functionality; and (3) lack of appointment availability (<xref ref-type="table" rid="table3">Table 3</xref>). This feedback was used to inform updates and upgrades to the tool.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Patient feedback categories, counts, and examples.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="350"/>
            <col width="80"/>
            <col width="570"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Count</td>
                <td>Examples and quotations</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Requested changes to other COVID-19 services (eg, telephone hotline), policies, or procedures</td>
                <td>24</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Should do covid testing 24 hours.”</p>
                    </list-item>
                    <list-item>
                      <p>“Would be nice if you had MORE testing locations.”</p>
                    </list-item>
                    <list-item>
                      <p>Long wait times when calling the hotline during surges</p>
                    </list-item>
                    <list-item>
                      <p>Desire to be able to schedule preoperative or preadmission COVID-19 tests online</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Request for additional functionality</td>
                <td>19</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Would be good to see possible appointment times upfront and then opt to continue entering all one's personal info. Many people are first looking for an available time slot that can work for them.”</p>
                    </list-item>
                    <list-item>
                      <p>Same-day cancelation or rescheduling of a visit online</p>
                    </list-item>
                    <list-item>
                      <p>Ability for the tool to recall prior responses</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Lack of appointment availability</td>
                <td>12</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Lack of availability of same- or next-day test appointments during Omicron surge</p>
                    </list-item>
                    <list-item>
                      <p>“There are literally no appointments available even though it recommended I have one.”</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Difficulty navigating patient portal</td>
                <td>8</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Confusion in differentiating this tool from a distinct, “schedule a visit” tool on the patient portal</p>
                    </list-item>
                    <list-item>
                      <p>“I couldn't find the link to schedule a test. I began at ‘Schedule an appointment.’”</p>
                    </list-item>
                    <list-item>
                      <p>Link to this tool not prominent enough</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Request for more personalized health information</td>
                <td>6</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“How do I find out what ‘Your Value=Not Detected’ means? Does this mean I do not have Covid?”</p>
                    </list-item>
                    <list-item>
                      <p>Request for quarantine advice personalized to individual circumstance</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Outdated information or wording</td>
                <td>6</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Recommendation page listed an outdated clinic phone number</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Difficult to understand care directions</td>
                <td>4</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Didn’t go through with scheduling a visit/test because 1) it wasn’t clear if I had to have a video visit before the test; &#38; 2) I didn’t know where I could get tested (for example, at primary care facility in ***?). So I aborted testing tool.”</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Technical difficulties</td>
                <td>4</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“I did not get confirmation that the test was scheduled.”</p>
                    </list-item>
                    <list-item>
                      <p>Network or connectivity problems</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study is the first, to our knowledge, to conduct user research on an EHR-integrated COVID-19 symptom checker with self-scheduling functionality. In this analysis, users generally perceived the symptom checker positively and usually reported that the tool improved their care experience. The most popular features were the ability to self-schedule a COVID-19 test online and 24-7 access to triage advice. Constructive or negative feedback on the tool was often a reflection of the larger ecosystem of care delivery for COVID-19, particularly during times of high demand, rather than related to the digital tool itself. This points toward the need for systems to develop robust, high-quality services in conjunction with usable and functioning digital health tools to aid in access.</p>
      </sec>
      <sec>
        <title>Comparison With Other Studies</title>
        <p>This analysis supports existing literature [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref13">13</xref>] that COVID-19 symptom checkers are generally popular with users. It is well known that there are disparities in access to and ability to use digital tools [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref16">16</xref>]. However, we observed no differences in overall experience by age, sex, race, ethnicity, and socioeconomic status for those who successfully completed the tool. This suggests that disparities in the use and satisfaction of digital tools like this one may be primarily an issue of access to the tool itself, since those who successfully used the tool reported deriving an equivalent degree of benefit regardless of demographics. This finding can be extended to other patient portal–based tools such as self-scheduling and automated prescription refill services.</p>
      </sec>
      <sec>
        <title>Strengths and Weaknesses of the Study</title>
        <p>This survey was completely optional, and we observed a low response rate, so there may be a risk for nonresponse bias. However, recent research suggests that the trends observed may accurately represent attitudes of the population despite low response rate [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Furthermore, we looked not only at quantitative trends but also at written feedback and noticed that most themes were mentioned in several responses, arguing that we may have reached saturation for likely responders or users with high digital literacy [<xref ref-type="bibr" rid="ref19">19</xref>]. To keep the survey concise and anonymous, we were limited in the demographic information we could analyze and had no clinical information about the respondents. For that reason, we were unable to stratify the results based on clinical outcomes, comorbidities, or other patient factors. However, the anonymity of the survey likely promoted more open and honest feedback and responses. Finally, because we embedded the survey at the end of the tool, we were limited in our ability to assess technical barriers to tool use, since those who were unable to use the tool never saw the survey. However, we chose to locate the survey at the end of the tool because our primary goal was to receive timely and actionable user feedback. We chose not to conduct the survey by phone, email, or mail, out of concern that patients would confuse their Symptom Checker experience with other digital and telehealth tools (eg, video visits and remote monitoring) that they may use in the course of an illness, and because we wanted to avoid nonclinical patient communications during times of acute illness.</p>
      </sec>
      <sec>
        <title>Implications</title>
        <p>This analysis may be useful to health systems that are trying to weigh the benefits of developing or integrating a COVID-19 symptom checker or similar tool with potential costs. In addition to the other established benefits, high patient satisfaction may make investment in COVID-19 symptom checkers worthwhile. Second, this tool may help to prevent front-line staff and physician burnout [<xref ref-type="bibr" rid="ref20">20</xref>] by decreasing the volume of calls and patient portal messages. In total, this tool has been used over 80,000 times since it was introduced in March 2020. Based on the proportion of patients who responded that if they had not used this tool, they would have called or messaged their clinicians, the tool may have prevented over 20,000 calls and over 8800 patient messages to date. To our knowledge, this is the first study to assess patient alternatives to use of a symptom checker in the United States. It is consistent with literature from Switzerland and France that most users would have contacted health care systems in the absence of a self-triage tool, and that the use of these tools decreases call center volume [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Our results may also be generalizable to chatbots, which are widely used in health care to automate triage, connect patients, and reduce provider burden.</p>
        <p>Several of the qualitative trends we observed may be useful to health systems and developers for the design and improvement of symptom checkers and other patient self-service tools. First, the most common category of written feedback was pertaining to the COVID-19 services, policies, and procedures, as well as appointment availability at the health system, rather than an intrinsic aspect of the tool. For that reason, it is essential that health systems first optimize their operational workflows and rightsize their capacity for tests and visits prior to or in conjunction with implementing such a tool. Second, users frequently requested software features that were beyond the current capabilities of the platform we used. Developers of these tools must therefore weigh the benefit of more nimble tools with user-friendly features (eg, transparency of visit availability) with the cost of their development and integration into the EHR. Third, users rarely reported technical challenges, suggesting usability of simple patient-portal–embedded tools. Fourth, the most popular feature of the symptom checker was the ability to self-schedule a COVID-19 test online, suggesting that EHR-integrated tools with the ability to offer self-scheduling of tests, screening exam, or imaging may be perceived more positively by patients compared with those without such features. Finally, our experience from reviewing continuous user feedback reinforced the notion that embedding a simple user feedback survey into a digital tool is a helpful way to promote iterative development.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>COVID-19 symptom checkers have effectively aided health systems in handling high volumes of triage and scheduling requests during the COVID-19 pandemic. We report high user satisfaction and user experience across demographic groups. Furthermore, patient-reported alternatives to the use of this tool suggest it may have saved thousands of phone calls and patient messages. COVID-19 symptom checkers are likely to remain in use for the near future in a diverse array of settings, and an examination of characteristics of use provides insight to improve the patient experience.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Qualtric survey questions embedded into electronic health record–integrated COVID-19 self scheduling and triage tool.</p>
        <media xlink:href="humanfactors_v9i3e40064_app1.docx" xlink:title="DOCX File , 17 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">UCSF</term>
          <def>
            <p>University of California, San Francisco</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors recognize the contributions of Chris Miller and Aimee Williams who were instrumental in building and launching the COVID-19 Symptom Checker, and Michael Helle, who led the creation of the COVID-19 hotline. The authors also thank the many individuals from the University of California, San Francisco Clinical Innovation Center, Clinical Systems, Center for Digital Health Innovation, and Office of Population Health who helped to design and implement COVID-19 triage algorithm, hotline workflow, and symptom checker.</p>
      <p>WB was supported by the Agency for Healthcare Research and Quality (K12HS026383) and the National Center for Advancing Translational Sciences (KL2TR001870). The content is solely the responsibility of the authors and does not necessarily represent the official views of the Center for Digital Health Innovation or National Institutes of Health.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>ABN has received research grants from Eli Lilly, Pfizer, Royal Philips, Commonwealth Fund, and Cisco; has served as advisor and received consulting fees from Roche, Sanofi, Medtronic, Eli Lilly, Steady Health, and Intuity Medical; is a medical advisor of Tidepool (for which he has received no compensation); and has received author and speaker honoraria from TCOYD, Medscape/WebMD, and AcademyHealth. RG Exercised stock options with Phreesia, Inc. TJJ has served as an advisor to Assure Health and received consulting fees and equity.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mansab</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goyal</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Performance of national COVID-19 'symptom checkers': a comparative case simulation study</article-title>
          <source>BMJ Health Care Inform</source>
          <year>2021</year>
          <month>03</month>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>e100187</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33685943"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjhci-2020-100187</pub-id>
          <pub-id pub-id-type="medline">33685943</pub-id>
          <pub-id pub-id-type="pii">bmjhci-2020-100187</pub-id>
          <pub-id pub-id-type="pmcid">PMC7942238</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Winn</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Somai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fergestrom</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Crotty</surname>
              <given-names>BH</given-names>
            </name>
          </person-group>
          <article-title>Association of use of online symptom checkers with patients' plans for seeking care</article-title>
          <source>JAMA Netw Open</source>
          <year>2019</year>
          <month>12</month>
          <day>02</day>
          <volume>2</volume>
          <issue>12</issue>
          <fpage>e1918561</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2019.18561"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2019.18561</pub-id>
          <pub-id pub-id-type="medline">31880791</pub-id>
          <pub-id pub-id-type="pii">2757995</pub-id>
          <pub-id pub-id-type="pmcid">PMC6991310</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>Miner</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Laranjo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kocaballi</surname>
              <given-names>AB</given-names>
            </name>
          </person-group>
          <article-title>Chatbots in the fight against the COVID-19 pandemic</article-title>
          <source>NPJ Digit Med</source>
          <year>2020</year>
          <month>5</month>
          <day>4</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>65</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-020-0280-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-020-0280-0</pub-id>
          <pub-id pub-id-type="medline">32377576</pub-id>
          <pub-id pub-id-type="pii">280</pub-id>
          <pub-id pub-id-type="pmcid">PMC7198587</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>Munsch</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gruarin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nateqi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Abdarahmane</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Weingartner-Ortner</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Knapp</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Diagnostic accuracy of web-based COVID-19 symptom checkers: comparison study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>10</month>
          <day>06</day>
          <volume>22</volume>
          <issue>10</issue>
          <fpage>e21299</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/10/e21299/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21299</pub-id>
          <pub-id pub-id-type="medline">33001828</pub-id>
          <pub-id pub-id-type="pii">v22i10e21299</pub-id>
          <pub-id pub-id-type="pmcid">PMC7541039</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>Semigran</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Linder</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Gidengil</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mehrotra</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of symptom checkers for self diagnosis and triage: audit study</article-title>
          <source>BMJ</source>
          <year>2015</year>
          <month>07</month>
          <day>08</day>
          <volume>351</volume>
          <fpage>h3480</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=26157077"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.h3480</pub-id>
          <pub-id pub-id-type="medline">26157077</pub-id>
          <pub-id pub-id-type="pmcid">PMC4496786</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>Judson</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Odisho</surname>
              <given-names>AY</given-names>
            </name>
            <name name-style="western">
              <surname>Neinstein</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Moriarty</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gleason</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Intinarelli</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzales</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Rapid design and implementation of an integrated patient self-triage and self-scheduling tool for COVID-19</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>06</month>
          <day>01</day>
          <volume>27</volume>
          <issue>6</issue>
          <fpage>860</fpage>
          <lpage>866</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32267928"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa051</pub-id>
          <pub-id pub-id-type="medline">32267928</pub-id>
          <pub-id pub-id-type="pii">5817825</pub-id>
          <pub-id pub-id-type="pmcid">PMC7184478</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>Herriman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rosin</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Volpp</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Asked and answered: building a chatbot to address Covid-19-related concerns</article-title>
          <source>Nejm Catalyst</source>
          <year>2020</year>
          <month>06</month>
          <day>18</day>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1056/cat.20.0230</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>Judson</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Odisho</surname>
              <given-names>AY</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bigazzi</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Steuer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzales</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Neinstein</surname>
              <given-names>AB</given-names>
            </name>
          </person-group>
          <article-title>Implementation of a digital chatbot to screen health system employees during the COVID-19 pandemic</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>07</month>
          <day>01</day>
          <volume>27</volume>
          <issue>9</issue>
          <fpage>1450</fpage>
          <lpage>1455</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32531066"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa130</pub-id>
          <pub-id pub-id-type="medline">32531066</pub-id>
          <pub-id pub-id-type="pii">5856745</pub-id>
          <pub-id pub-id-type="pmcid">PMC7313990</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>Chambers</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cantrell</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Preston</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Baxter</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital and online symptom checkers and health assessment/triage services for urgent health problems: systematic review</article-title>
          <source>BMJ Open</source>
          <year>2019</year>
          <month>08</month>
          <day>01</day>
          <volume>9</volume>
          <issue>8</issue>
          <fpage>e027743</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=31375610"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2018-027743</pub-id>
          <pub-id pub-id-type="medline">31375610</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2018-027743</pub-id>
          <pub-id pub-id-type="pmcid">PMC6688675</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>Aboueid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Wallace</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Mahajan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nur</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Chaurasia</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Use of symptom checkers for COVID-19-related symptoms among university students: a qualitative study</article-title>
          <source>BMJ Innov</source>
          <year>2021</year>
          <month>04</month>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>253</fpage>
          <lpage>260</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34192014"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjinnov-2020-000498</pub-id>
          <pub-id pub-id-type="medline">34192014</pub-id>
          <pub-id pub-id-type="pii">bmjinnov-2020-000498</pub-id>
          <pub-id pub-id-type="pmcid">PMC7852069</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kerr</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>O' Regan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Creagh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Geary</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Colgan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Canning</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Merry</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Noonan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bergin</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Acceptability of and symptom findings from an online symptom check-in tool for COVID-19 outpatient follow-up among a predominantly healthcare worker population</article-title>
          <source>BMJ Open</source>
          <year>2021</year>
          <month>09</month>
          <day>28</day>
          <volume>11</volume>
          <issue>9</issue>
          <fpage>e050444</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=34588254"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2021-050444</pub-id>
          <pub-id pub-id-type="medline">34588254</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2021-050444</pub-id>
          <pub-id pub-id-type="pmcid">PMC8479588</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>Kind</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Buckingham</surname>
              <given-names>WR</given-names>
            </name>
          </person-group>
          <article-title>Making neighborhood-disadvantage metrics accessible — The Neighborhood Atlas</article-title>
          <source>N Engl J Med</source>
          <year>2018</year>
          <month>06</month>
          <day>28</day>
          <volume>378</volume>
          <issue>26</issue>
          <fpage>2456</fpage>
          <lpage>2458</lpage>
          <pub-id pub-id-type="doi">10.1056/nejmp1802313</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>Aboueid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wallace</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Mahajan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chaurasia</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Young adults' perspectives on the use of symptom checkers for self-triage and self-diagnosis: qualitative study</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2021</year>
          <month>01</month>
          <day>06</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>e22637</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2021/1/e22637/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22637</pub-id>
          <pub-id pub-id-type="medline">33404515</pub-id>
          <pub-id pub-id-type="pii">v7i1e22637</pub-id>
          <pub-id pub-id-type="pmcid">PMC7817365</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nouri</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Avila-Garcia</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cemballi</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Sarkar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Aguilera</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lyles</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Assessing mobile phone digital literacy and engagement in user-centered design in a diverse, safety-net population: mixed methods study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>08</month>
          <day>29</day>
          <volume>7</volume>
          <issue>8</issue>
          <fpage>e14250</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/8/e14250/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14250</pub-id>
          <pub-id pub-id-type="medline">31469083</pub-id>
          <pub-id pub-id-type="pii">v7i8e14250</pub-id>
          <pub-id pub-id-type="pmcid">PMC6740160</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Levy</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Janke</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Langa</surname>
              <given-names>KM</given-names>
            </name>
          </person-group>
          <article-title>Health literacy and the digital divide among older Americans</article-title>
          <source>J Gen Intern Med</source>
          <year>2015</year>
          <month>03</month>
          <volume>30</volume>
          <issue>3</issue>
          <fpage>284</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25387437"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-014-3069-5</pub-id>
          <pub-id pub-id-type="medline">25387437</pub-id>
          <pub-id pub-id-type="pmcid">PMC4351282</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cresci</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Yarandi</surname>
              <given-names>HN</given-names>
            </name>
            <name name-style="western">
              <surname>Morrell</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>The Digital Divide and urban older adults</article-title>
          <source>Comput Inform Nurs</source>
          <year>2010</year>
          <volume>28</volume>
          <issue>2</issue>
          <fpage>88</fpage>
          <lpage>94</lpage>
          <pub-id pub-id-type="doi">10.1097/NCN.0b013e3181cd8184</pub-id>
          <pub-id pub-id-type="medline">20182159</pub-id>
          <pub-id pub-id-type="pii">00024665-201003000-00007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>ER</given-names>
            </name>
            <name name-style="western">
              <surname>Grant</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Belin</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Brick</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Exploring nonresponse bias in a health survey using neighborhood characteristics</article-title>
          <source>Am J Public Health</source>
          <year>2009</year>
          <month>10</month>
          <volume>99</volume>
          <issue>10</issue>
          <fpage>1811</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.2105/AJPH.2008.154161</pub-id>
          <pub-id pub-id-type="medline">19696379</pub-id>
          <pub-id pub-id-type="pii">AJPH.2008.154161</pub-id>
          <pub-id pub-id-type="pmcid">PMC2741510</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>Meterko</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Restuccia</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stolzmann</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mohr</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Glasgow</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kaboli</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Response rates, nonresponse bias, and data quality: Results from a National Survey of Senior Healthcare Leaders</article-title>
          <source>Public Opinion Quarterly</source>
          <year>2015</year>
          <volume>79</volume>
          <issue>1</issue>
          <fpage>130</fpage>
          <lpage>144</lpage>
          <pub-id pub-id-type="doi">10.1093/poq/nfu052</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saunders</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kingstone</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Waterfield</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bartlam</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Burroughs</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Jinks</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Saturation in qualitative research: exploring its conceptualization and operationalization</article-title>
          <source>Qual Quant</source>
          <year>2018</year>
          <volume>52</volume>
          <issue>4</issue>
          <fpage>1893</fpage>
          <lpage>1907</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29937585"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11135-017-0574-8</pub-id>
          <pub-id pub-id-type="medline">29937585</pub-id>
          <pub-id pub-id-type="pii">574</pub-id>
          <pub-id pub-id-type="pmcid">PMC5993836</pub-id>
        </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>Tai-Seale</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dillon</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Nordgren</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Steinberg</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Nauenberg</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Meehan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Frosch</surname>
              <given-names>DL</given-names>
            </name>
          </person-group>
          <article-title>Physicians' well-being linked to in-basket messages generated by algorithms in electronic health records</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2019</year>
          <month>07</month>
          <volume>38</volume>
          <issue>7</issue>
          <fpage>1073</fpage>
          <lpage>1078</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2018.05509</pub-id>
          <pub-id pub-id-type="medline">31260371</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>Galmiche</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rahbe</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fontanet</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dinh</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bénézit</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lescure</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Denis</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Implementation of a self-triage web application for suspected COVID-19 and its impact on emergency call centers: observational study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>23</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e22924</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e22924/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22924</pub-id>
          <pub-id pub-id-type="medline">33147165</pub-id>
          <pub-id pub-id-type="pii">v22i11e22924</pub-id>
          <pub-id pub-id-type="pmcid">PMC7685697</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>Hautz</surname>
              <given-names>WE</given-names>
            </name>
            <name name-style="western">
              <surname>Exadaktylos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sauter</surname>
              <given-names>TC</given-names>
            </name>
          </person-group>
          <article-title>Online forward triage during the COVID-19 outbreak</article-title>
          <source>Emerg Med J</source>
          <year>2021</year>
          <month>03</month>
          <volume>38</volume>
          <issue>2</issue>
          <fpage>106</fpage>
          <lpage>108</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://emj.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33310732"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/emermed-2020-209792</pub-id>
          <pub-id pub-id-type="medline">33310732</pub-id>
          <pub-id pub-id-type="pii">emermed-2020-209792</pub-id>
          <pub-id pub-id-type="pmcid">PMC7735070</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
