<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JPP</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Pediatr Parent</journal-id>
      <journal-title>JMIR Pediatrics and Parenting</journal-title>
      <issn pub-type="epub">2561-6722</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">v5i4e38940</article-id>
      <article-id pub-id-type="pmid">36201385</article-id>
      <article-id pub-id-type="doi">10.2196/38940</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>The Current State of Mobile Apps Owned by Large Pediatric Hospitals in the United States: Systematic Search and Analysis on Google Play and Apple App Stores</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Badawy</surname>
            <given-names>Sherif</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lee</surname>
            <given-names>Wui-Chiang</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Tennant</surname>
            <given-names>Ryan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Lieser</surname>
            <given-names>Tyler</given-names>
          </name>
          <degrees>BA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>The Abigail Wexner Research Institute</institution>
            <institution>Nationwide Children's Hospital</institution>
            <addr-line>575 Children's Xrd</addr-line>
            <addr-line>Columbus, OH, 43215</addr-line>
            <country>United States</country>
            <phone>1 6147222210</phone>
            <email>tyler.lieser@nationwidechildrens.org</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5955-7255</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Huang</surname>
            <given-names>Yungui</given-names>
          </name>
          <degrees>MBA, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3265-9902</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Sezgin</surname>
            <given-names>Emre</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8798-9605</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>The Abigail Wexner Research Institute</institution>
        <institution>Nationwide Children's Hospital</institution>
        <addr-line>Columbus, OH</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Tyler Lieser <email>tyler.lieser@nationwidechildrens.org</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Oct-Dec</season>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>6</day>
        <month>10</month>
        <year>2022</year>
      </pub-date>
      <volume>5</volume>
      <issue>4</issue>
      <elocation-id>e38940</elocation-id>
      <history>
        <date date-type="received">
          <day>22</day>
          <month>4</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>18</day>
          <month>8</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>1</day>
          <month>9</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Tyler Lieser, Yungui Huang, Emre Sezgin. Originally published in JMIR Pediatrics and Parenting (https://pediatrics.jmir.org), 06.10.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 Pediatrics and Parenting, is properly cited. The complete bibliographic information, a link to the original publication on https://pediatrics.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://pediatrics.jmir.org/2022/4/e38940" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Pediatric hospitals in the United States are increasingly leveraging patient-facing mobile apps as their digital front doors for patients, families, and caretakers. These mobile health apps are sanctioned by pediatric hospitals to inform the public or populations about pediatric care to provide individualized information, to enhance communication, and to improve patient experience. Yet the functionalities and user feedback of these hospital mobile apps have not been systematically investigated.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Our aim was to understand the current state of hospital-owned mobile apps provided by large pediatric hospitals, comparatively analyze and report the services provided, and identify potential gaps to inform developers and providers. The American Hospital Association defines large hospitals as those having a bed count of more than 400.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted a systematic search on Google Play and Apple App Store to identify all hospital-owned mobile apps from the large pediatric hospitals included in our review. Our inclusion criteria were (1) apps provided by large pediatric hospitals; (2) hospital-owned apps available in Apple App Store and Google Play; and (3) apps that are provided for general populations. Specialty apps that serve specific user groups or populations focusing on education, telehealth, specific conditions or procedures, or apps intended for research or clinician use were excluded. The features and functionality of the included apps were examined.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Of the 16 pediatric hospitals included in our review, 4 (25%) had no general patient-facing apps, 4 (25%) had one app, and 8 (50%) had more than one app available on Google Play or Apple App Store. The 12 hospitals with at least one mobile app had a combined total of 72 apps. Of these 72 apps, 61 (85%) were considered specialty and were excluded from our review, leaving a total of 11 (15%) apps to analyze. Among the 11 apps analyzed, the most common feature was appointment scheduling or reminder (n=9, 82%). Doctor search (n=8, 73%) and patient resources (n=8, 73%) were the second most common, followed by payment, billing, or claims (n=7, 64%), patient portal integration (n=6, 55%), personal health management (n=6, 55%), hospital way finding (n=5, 45%), message a provider (n=4, 36%), urgent care wait times (n=4, 36%), video chat (n=4, 36%), and health information access (n=4, 36%). Parking information (n=3, 27%) was the least common.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Out of the 16 pediatric hospitals identified for our review, 75% (n=12) offer mobile apps. Based on the most common features, these apps were intended to help improve accessibility for patients and families in terms of finding providers, scheduling appointments, and accessing patient resources. We believe the findings will inform pediatric hospital administrators, developers, and other stakeholders to improve app feature offerings and increase their impact on service accessibility and patient experience.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>pediatric</kwd>
        <kwd>child</kwd>
        <kwd>hospital</kwd>
        <kwd>mobile app</kwd>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>health app</kwd>
        <kwd>digital health</kwd>
        <kwd>eHealth</kwd>
        <kwd>hospital-owned app</kwd>
        <kwd>telehealth</kwd>
        <kwd>review</kwd>
        <kwd>app feature</kwd>
        <kwd>accessibility</kwd>
        <kwd>patient experience</kwd>
        <kwd>functionality</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Ownership of smartphones has continued to increase since their introduction in the mid-2000s. According to Pew Research, 85% of Americans own a smartphone, and over half (53%) of US adults own a tablet computer [<xref ref-type="bibr" rid="ref1">1</xref>]. The way we interact and engage with the world has become increasingly mobile. Currently, there are over 4.8 million apps available on the Apple App Store and Google Play [<xref ref-type="bibr" rid="ref2">2</xref>] with over 350,000 of those in the health care domain [<xref ref-type="bibr" rid="ref3">3</xref>], which shows a more than 3-fold increase since 2014 [<xref ref-type="bibr" rid="ref4">4</xref>]. This rapid adoption of health care mobile apps shows that more people are using their mobile devices for their health and health care needs. Consumer’s expectations of how they interact with health care organizations are shifting toward a mobile-first mindset.</p>
      <p>Similarly, recognizing this trend, hospitals have been offering their own apps to meet this demand. An earlier Accenture report presented that two-thirds of the largest US hospitals offer patient-facing mobile health apps [<xref ref-type="bibr" rid="ref5">5</xref>]. Yet a number of these apps have been poorly implemented, failing to improve patient engagement or provide services. Out of those hospital-owned apps, few offered expected services or functionalities, and it resulted in 2% of patients using these apps [<xref ref-type="bibr" rid="ref5">5</xref>]. Similar adoption problems have been observed with mobile patient portals as well [<xref ref-type="bibr" rid="ref6">6</xref>]. Working with younger patients and parents who are more likely to be digital savvy and have stronger desire to be mobile first, pediatric hospitals have more urgency to adapt to this shifting mindset and needs. Pediatric hospitals need to develop their own mobile apps to improve accessibility to better serve their patients and families. There have been mobile health apps to inform the public or populations about pediatric care [<xref ref-type="bibr" rid="ref7">7</xref>], yet mobile apps provided by pediatric hospitals have not been widely investigated.</p>
      <p>The goal of this study is to investigate the hospital-owned apps by large pediatric hospitals in the United States. Large pediatric hospitals serve a high number of patients with a variety of conditions and different populations. Their web-based presence and supporting tools, built to address the patient’s needs with hospital services and resources, are essential to serve the large patient population and potentially have a larger impact. Large hospitals usually have the financial resources to comprehensively develop their apps, and most of the time, they are the first in the market to provide new health care technologies and solutions. Therefore, this study focuses on the large pediatric hospitals with our aims being (1) to understand the current state of hospital-owned mobile apps provided by large pediatric hospitals, (2) to comparatively analyze and report the services provided, and (3) to identify potential gaps to inform hospital administration as they plan and improve their digital health strategies.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Mobile App Inclusion Criteria</title>
        <p>Our inclusion criteria for the health care mobile apps for this study were as follows: (1) they are provided by large pediatric hospitals; (2) they are available in Apple App Store and Google Play; and (3) they are provided for general populations. The American Hospital Association defines large hospitals as having a bed count of more than 400 [<xref ref-type="bibr" rid="ref8">8</xref>]. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram [<xref ref-type="bibr" rid="ref9">9</xref>], reporting the review procedure.</p>
        <p>To identify large pediatric hospitals to include in this review, we leveraged Pediatric Health Information System (PHIS), a comprehensive database with clinical and resource utilization data for inpatient, ambulatory surgery, emergency department, and observation unit encounters for more than 49 children’s hospitals. It is frequently used to study pediatric inpatient care [<xref ref-type="bibr" rid="ref10">10</xref>]. We queried PHIS, last updated in 2020, to identify pediatric hospitals that had a bed count of 390 or greater, to be inclusive of the hospitals that have a small margin to be rated as large hospitals in the following years.</p>
        <p>We used the name of each identified hospital to conduct a systematic search on Google Play and Apple App Store platforms to identify all hospital-owned mobile apps. First, authors identified the keywords. Then, the search was conducted by the first author (TL) between November 2, 2021, and January 14, 2022. Specialty apps centered around education, telehealth, specific conditions or procedures, or apps intended for research or clinician use were excluded, as they are intended to serve a subset of the general population (see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> for the list of excluded apps). The selected apps were downloaded and reviewed by the authors (TL and ES). We downloaded each app from Google Play on a Google Pixel 4a smartphone to review available features. We used an iPhone 11 to download 1 app that only offered an iOS version (myChop). Out of 16 hospitals, apps were provided by 12 (75%), with a total of 72 hospital-owned and specialty apps. A total of 11 apps met our criteria and were included in this review.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram.</p>
          </caption>
          <graphic xlink:href="pediatrics_v5i4e38940_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Mobile App Data Extraction and Analysis</title>
        <p>Data available on Google Play and Apple App Store were collected for each app including app name, developer, last update, number of downloads, rating, size, requirements, permissions, as well as app content rating. We used summary statistics to compare features among these hospital mobile apps. To compare features among hospitals, we created a chart and listed the features of each app (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
        <p>We used appbot.co to conduct sentiment analysis on app reviews. appbot.com was claimed to be trained with 400+ million records and have 93% accuracy [<xref ref-type="bibr" rid="ref11">11</xref>]. The algorithm analyzes and sorts the reviews into four categories: (1) positive sentiment (accounting in positive comments, eg, “Thanks for this app, it makes life a little more easier”), negative sentiment (accounting in negative comments, eg, “Does not accept same log in as online account...”), neutral sentiment (accounting in comments not having strong sentiment, eg, “I am not sure if I like the new design”), and mixed sentiment (accounting in comments with conflicting sentiment, eg, “Excellent app, with great information, but regrettably have to uninstall due its size”) [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overall</title>
        <p>A large pediatric hospital identification query to PHIS resulted in 16 pediatric hospitals being included in our review. Of these 16 hospitals, 4 (25%) had no health care mobile apps, 4 (25%) had 1 app, and 8 (50%) had more than one app available on Google Play or Apple App Store. The 12 hospitals with at least one mobile app had a combined total of 72 apps. Of these apps, 61 (85%) were considered specialty and were excluded from our review, leaving a total of 11 (15%) apps for our analysis.</p>
      </sec>
      <sec>
        <title>App Features</title>
        <p>A total of 12 features were included in our comparison table (<xref ref-type="table" rid="table1">Table 1</xref>). The most common feature among apps was appointment scheduling or reminder (n=9, 82%). Doctor search (n=8, 73%) and patient resources (n=8, 73%) were the second most common, followed by payment, billing, or claims (n=7, 64%), patient portal integration (n=6, 55%), personal health management (n=6, 55%), hospital way finding (n=5, 45%), message a provider (n=4, 36%), urgent care wait times (n=4, 36%), video chat (n=4, 36%), and health information access (n=4, 36%). Parking information (n=3, 27%) was the least common.</p>
        <p>Appointment scheduling and reminders, the most frequently included feature, allows users to schedule appointments with providers directly within the app. Users will also receive a reminder notification of an approaching appointment. Doctor search gives users the ability to search for providers and review their contact information. Patient resources include features such as FAQs, games, blogs, information about nearby hotels, food, and entertainment. Payment, billing, or claims enable users to see statement balances or claims and make a payment within the app. Patient portal integration allows users to log in to Electronic Health Record patient portal, such as EPIC MyChart, directly from the app. Personal health management features allow users to actively manage their health with features such as requesting prescription refills, listing of medications, dosage and immunizations, as well as the ability to enter and track symptoms and medications. Hospital way finding helps direct users to various locations in the hospital using photos or active navigation. Messaging providers and video chat let users directly message providers and allow them to meet via video. Urgent care wait times allow users to review and receive updates on current wait times at urgent care. Health information access is the feature for the patients and caregivers to access detailed medical information. Finally, parking information lets users see available parking prior to arriving at the hospital.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Categorized features of the apps.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="80"/>
            <col width="70"/>
            <col width="70"/>
            <col width="70"/>
            <col width="70"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <thead>
              <tr valign="top">
                <td>Features or pediatric hospitals</td>
                <td>Texas Children's Hospital</td>
                <td>Cincinnati Children's Hospital Medical Center</td>
                <td>Nationwide Children's Hospital</td>
                <td>Children's Hospital of Philadelphia</td>
                <td>Children's Healthcare of Atlanta</td>
                <td>Akron Children's Hospital</td>
                <td>Children's Health, Dallas</td>
                <td>Phoenix Children's</td>
                <td>Boston Children's Hospital</td>
                <td>St. Louis Children's Hospital</td>
                <td>Cook Children's Medical Center</td>
                <td>Apps with the listed feature, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Appointment scheduling and reminder</td>
                <td>X<sup>a</sup></td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>9 (82)</td>
              </tr>
              <tr valign="top">
                <td>Doctor search</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>8 (73)</td>
              </tr>
              <tr valign="top">
                <td>Patient resources</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>8 (73)</td>
              </tr>
              <tr valign="top">
                <td>Payment, billing, or claims</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>7 (64)</td>
              </tr>
              <tr valign="top">
                <td>Patient portal integration</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>6 (55)</td>
              </tr>
              <tr valign="top">
                <td>Personal health management</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>6 (55)</td>
              </tr>
              <tr valign="top">
                <td>Hospital way finding</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>5 (45)</td>
              </tr>
              <tr valign="top">
                <td>Message provider</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>Urgent care wait times</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>Video chat</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>Health information access</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>Parking information</td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>X</td>
                <td>X</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>3 (27)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>X: indicates whether or not a hospital's mobile app offers that feature.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>App Data</title>
        <p>All apps in this comparison have been updated within the last 2 years, with 82% (9/11) having been updated in 2021. In terms of number of downloads, 55% (6/11) have &#62;10,000 downloads, 27% (3/11) have &#62;5000 downloads, and 1 app has been downloaded &#62;100 times. The number of downloads is only available for Android versions on Google Play store. Therefore, we were unable to find the number of downloads for 1 app, as it is only offered in the iOS version. App size ranged from 16 MB to 152.2 MB with an average size of 68 MB. All apps were available in English with 90% (10/11) also offering one or more additional languages. Texas Children’s, Children’s Healthcare of Atlanta, Akron Children’s, Children’s Health, Phoenix Children’s, St. Louis Children’s, and Cook Children’s Medical Center all offer their app in Spanish, in addition to English. Nationwide Children’s, Children’s Hospital of Philadelphia, Boston Children’s, and Cook Children’s Medical Center offer Spanish and other languages.</p>
      </sec>
      <sec>
        <title>App Ratings and Sentiment Analysis</title>
        <p>We combined app ratings and number of reviews from both Google Play and Apple App Stores for each app (MyChop was only available in iOS) to determine the average rating and total number of reviews. Ratings for the selected apps, with minimum and maximum allowed as 1 and 5, respectively, ranged from 3.1 to 5, with an average rating of 4.4. Only 265 people left written reviews, and their ratings averaged at 3.4 (<xref ref-type="table" rid="table2">Table 2</xref>). Texas Children’s Anywhere Care app and Nationwide Children’s myChildren’s app had the highest number of reviews among others (n≥50). The total number of app reviews was 1433. We conducted sentiment analysis (<xref rid="figure2" ref-type="fig">Figure 2</xref>) of app reviews using AppBot, a third-party review and ratings analysis tool, to determine positive, neutral, mixed, and negative sentiment of user reviews. Phoenix Children’s was excluded because the app had no reviews.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>App ratings and comments.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="200"/>
            <col width="150"/>
            <col width="200"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>Pediatric hospitals</td>
                <td>Number of ratings given (n=1433), n (%)</td>
                <td>Average rating (out of 5)</td>
                <td>Number of app comments (n=265), n (%)</td>
                <td>Average rating with comments (out of 5)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Texas Children's Anywhere Care</td>
                <td>488 (34)</td>
                <td>4.8</td>
                <td>53 (20)</td>
                <td>4.15</td>
              </tr>
              <tr valign="top">
                <td>MyCookChildren's</td>
                <td>320 (22)</td>
                <td>4.7</td>
                <td>39 (15)</td>
                <td>4.1</td>
              </tr>
              <tr valign="top">
                <td>NCH<sup>a</sup> myChildren's</td>
                <td>218 (15)</td>
                <td>4.2</td>
                <td>54 (20)</td>
                <td>3.15</td>
              </tr>
              <tr valign="top">
                <td>Kid Care-St. Louis Children's</td>
                <td>105 (7)</td>
                <td>4.7</td>
                <td>36 (14)</td>
                <td>4.55</td>
              </tr>
              <tr valign="top">
                <td>Children's Healthcare of Atlanta</td>
                <td>74 (5)</td>
                <td>4.25</td>
                <td>26 (10)</td>
                <td>3.65</td>
              </tr>
              <tr valign="top">
                <td>Cincinnati Children's Caren</td>
                <td>62 (4)</td>
                <td>4.5</td>
                <td>12 (5)</td>
                <td>4.6</td>
              </tr>
              <tr valign="top">
                <td>Children's Health Mobile App</td>
                <td>61 (4)</td>
                <td>4.7</td>
                <td>15 (6)</td>
                <td>4.05</td>
              </tr>
              <tr valign="top">
                <td>Boston Children's MyChildren's</td>
                <td>40 (3)</td>
                <td>3.7</td>
                <td>15 (6)</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>MyCHOP</td>
                <td>39 (3)</td>
                <td>3.1</td>
                <td>10 (4)</td>
                <td>1.5</td>
              </tr>
              <tr valign="top">
                <td>Akron Children's Anywhere</td>
                <td>20 (1)</td>
                <td>4.45</td>
                <td>5 (19)</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>Phoenix Children's Hospital</td>
                <td>6 (0.04)</td>
                <td>5</td>
                <td>0 (0)</td>
                <td>0</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>NCH: Nationwide Children's Hospital.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Sentiment analysis distribution (Phoenix Children’s excluded due to 0 reviews). NCH: Nationwide Children's Hospital.</p>
          </caption>
          <graphic xlink:href="pediatrics_v5i4e38940_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Mobile Operating System Requirements and Privacy</title>
        <p>Software requirements for each app differed, for both Android and iOS platforms. Apps downloaded from Google Play required Android versions ranging from 4.4 (originally released in 2013) to 7 (originally released in 2016). iOS versions of apps were available on iPhone, iPad, iPod Touch, and Mac devices, and required iOS versions 9 (originally released in 2015) to 13.2 (originally released in 2019). In terms of privacy, Texas Children’s Anywhere Care app required the highest number of permissions (24) including access requests to device location, photos, camera, microphone, etc. MyCHOP required the least with no permissions or data being collected from the app.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This review provides an overview of current state features and functionalities of large pediatric hospital–owned mobile apps in 2022. Out of 16 large pediatric hospitals in the United States, most of them (n=11, 85%) owned at least one app. This suggests the significance and investments on mobile apps by large pediatric hospitals to support communications with patients and caregivers via smartphones. This finding could be essential for decision makers for pediatric hospital investment strategies in mobile health apps [<xref ref-type="bibr" rid="ref13">13</xref>]. The 7 hospitals in our review that do not offer any mobile apps may be at risk of seeing a decline in patient satisfaction, as hospital mobile app use has been shown to increase overall patient experience [<xref ref-type="bibr" rid="ref14">14</xref>]. Hospitals without mobile apps should consider how features made available by other hospital apps could benefit their own patients and families.</p>
        <p>Most of the apps offered similar functionalities. We identified personal health management and patient resources, appointment scheduling and reminders, and doctor search as the top features among included apps, followed by payment, billing, or claims, patient portal integration, hospital way finding, message a provider, urgent care wait times, and parking information. These categories suggest that hospitals aim to facilitate primarily remote care and in-hospital navigation and care management over their apps. Such practices can reduce hospitals’ operation costs, improve efficiency [<xref ref-type="bibr" rid="ref15">15</xref>], and enhance patient engagement [<xref ref-type="bibr" rid="ref16">16</xref>]. Doctor search as well as appointment scheduling and reminders were top features in a similar app review conducted in Taiwan [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
      </sec>
      <sec>
        <title>Accessibility</title>
        <p>Accessibility is reported in terms of app size, cost, maintenance, and language availability in this section. All the apps have been actively maintained, given the fact that they have been updated within a year period (in 2021 or later). They are all free to download. App sizes ranged from 16 MB to 152.2 MB with an average size of 68 MB. With the minimum storage of modern smartphones at or above 32 GB [<xref ref-type="bibr" rid="ref18">18</xref>], these free health care mobile apps offer great accessibility in terms of users being able to download and store an app on their phone without sacrificing storage capacity. Nonetheless, there may still be a digital divide such as lack of access to a smartphone, insufficient data plans or internet access, or low digital literacy, which may limit the access of these mobile services for underserved populations (eg, low-income patients, senior citizens, and rural patients). Practitioners should consider the digital divide and barriers in owning and using technologies by the populations; 1 in 5 low-income adults and approximately 30% of senior citizens do not own a smartphone but have a cell phone. In addition, rural residents, racial and ethnic minorities, people living on tribal lands, low-income families, and senior citizens are less likely to have broadband at home [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>Language could be another potential barrier to patients accessing these apps. Language barriers in health care lead to miscommunication between the medical professional and patient, reducing both parties’ satisfaction and decreasing the quality of health care delivery and patient safety [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. All apps were offered in English, with 90% also offering the app in Spanish. Only 36% (n=11) of hospitals offered their app in more than English and Spanish. Pediatric hospitals serve diverse populations and must account for a broader spectrum of languages.</p>
      </sec>
      <sec>
        <title>App Rating</title>
        <p>The total number of ratings among all 11 apps was 1433 with an average rating of 4.4 out of 5. There was a total of 265 app comments among all 11 apps with an average comment rating of 3.4. Overall, the sentiment of comments left by users in the app stores was positive. There was a 1-point rating difference between average ratings among all raters (4.4) and among raters who provided user comments (3.4). This difference may indicate that a higher volume of less satisfied app users are leaving reviews and comments on the app stores versus satisfied users. However, it is hard to quantitatively interpret correlation among user review sentiments and app ratings and review quantity [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        <p>There is a broad range for the number of ratings per app—Texas Children’s has 488 ratings while Phoenix Children’s has 6. This range may be impacted by factors such as patient volume, location, app functionalities, and more. The apps with high number of ratings and average rating scores and sentiment analysis results could be considered as a benchmark by other hospitals to identify the features to include. For instance, Texas Children’s received the highest average rating and positive sentiment comments (4.8/5). The volume of raters and high ratings may indicate that the features from these apps may offer insight when developing hospital apps (considering potential reviewer biases). Developers should consider user feedback to improve pediatric hospital–owned apps to be more aware of user needs and proactively address app issues and fill the identified gaps [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Privacy</title>
        <p>Privacy and security concerns of user data remain one of the top barriers to adoption of mobile health apps. Users could be concerned about what data are being collected and stored, who can access the data, and what purposes the data are being used for [<xref ref-type="bibr" rid="ref23">23</xref>]. We found that the number of access permissions for pediatric hospital–owned apps goes up to 24 access points, which consist of collecting data from phone sensors and controlling phones (see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> for permission requests by each app). The MyCHOP app does not collect any data from the user, while Texas Children’s Anywhere Care app requested 24 permissions for data collection. Most of the data collected from apps included location, access to photos, videos and camera, microphone, Wi-Fi connections, and more. Several apps collected data that would not be linked to the user’s identity but may be used for the developer’s advertising or marketing purposes.</p>
        <p>Even though privacy is one of the user's concerns, literature shows that most mobile apps do not prioritize privacy of user data. For example, of the 79 mobile health apps certified as being clinically safe and trustworthy by the United Kingdom National Health Service, 89% were found to transfer information online, 66% of which was not encrypted [<xref ref-type="bibr" rid="ref24">24</xref>]. Developers of pediatric hospital–owned apps must follow privacy policies of hospitals and health institutions to ensure the apps are compliant and collect only necessary data and explain how those data will be used and protected to the end users.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>One limitation was the study being limited to large pediatric hospitals in the United States. This limited the study to opt out smaller sized pediatric hospitals or adult hospitals in the United States or abroad. Second, hospitals included in this review were based on bed count. This limitation excludes hospitals that may have lower bed count, but higher number of annual visits. Third, features outlined in this review are subject to change, as these apps are continually being updated on a regular basis. Fourth, we were not able to assess the quality of the mobile apps due to limited access to the apps (without being a hospital patient or having an account). Fifth, due to time and resource constraints, we were not able to analyze user comments to identify which features users felt needed to be improved or which features were lacking from each app. Sixth, the comments and ratings could be impacted from behavioral biases; based on the experience of the reviewer, there could be polarized reviews that we were not able to analyze and identify [<xref ref-type="bibr" rid="ref25">25</xref>]. In addition, negativity bias or confirmation bias could be considered while reviewing the results [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Lastly, we did not focus on the impact of these apps to improve patient care or health outcomes. In that regard, future works are suggested to investigate how hospital-owned mobile apps impact patient experience, health outcomes, as well as comparing app quality across hospitals (eg, using mobile app rating scales [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]).</p>
        <p>Specialty apps (n=61) were excluded from our study, which were provided by specific clinical departments, or focused on research studies, education, telehealth, procedures, or conditions. The number of specialty apps may indicate that app development within some pediatric hospitals is conducted in silos within clinical departments or research groups, which raises questions about their governance, cross-integration, and contributions to the hospital operations. Further studies are suggested toward the specialty apps.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this study, we reviewed hospital-owned mobile apps provided by large pediatric hospitals in the United States. Out of 16 hospitals identified, 75% of pediatric hospitals in our review offer mobile apps. Based on the most common features, these apps were intended to help improve accessibility for patients and families in terms of finding providers, scheduling appointments, and accessing patient resources. Inferring actual usage of the health care apps from the number of downloads and user ratings, the adoption of mobile apps is still a major issue. Future works should study the processes that hospitals use when developing mobile apps to ensure user feedback is considered, as well as accessibility and privacy considerations, when determining the features to be implemented. Gathering user feedback will help developers determine the most desired features and may help increase adoption. Developing apps using user-centric, iterative approaches, soliciting inputs from representative user bases, and incorporating feedback from active users will be key to continuously improving health care mobile apps to reach the goals of having them serve as the digital front door, enhancing patient communication and improving patient experience, among others. We believe our findings will inform hospital administrators, developers, practitioners, and other stakeholders to identify and improve app features and services in pediatric hospitals.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>This file is a list of apps that met our exclusion criteria and were not included our review.</p>
        <media xlink:href="pediatrics_v5i4e38940_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 112 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Spreadsheet containing full app comparison.</p>
        <media xlink:href="pediatrics_v5i4e38940_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 145 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">PHIS</term>
          <def>
            <p>Pediatric Health Information System</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</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="web">
          <article-title>Demographics of mobile device ownership adoption in the United States</article-title>
          <source>Pew Research Center</source>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/internet/fact-sheet/mobile">https://www.pewresearch.org/internet/fact-sheet/mobile</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <source>BuildFire</source>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://buildfire.com/app-statistics">https://buildfire.com/app-statistics</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>Digital health apps balloon to more than 350,000 available on the market, according to IQVIA report</article-title>
          <source>MobiHealthNews</source>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mobihealthnews.com/news/digital-health-apps-balloon-more-350000-available-market-according-iqvia-report">https://www.mobihealthnews.com/news/digital-health-apps-balloon-more-350000-available-market-according-iqvia-report</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>mHealthApps: A Repository and Database of Mobile Health Apps</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2015</year>
          <month>03</month>
          <day>18</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e28</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/1/e28/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.4026</pub-id>
          <pub-id pub-id-type="medline">25786060</pub-id>
          <pub-id pub-id-type="pii">v3i1e28</pub-id>
          <pub-id pub-id-type="pmcid">PMC4382566</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>U.S. hospitals engaging only 2 percent of patients via mobile apps, putting as much as $100 million in annual revenue per hospital at risk, Accenture finds</article-title>
          <source>Accenture</source>
          <access-date>2022-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/38nmujb5">https://tinyurl.com/38nmujb5</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Individuals’ access and use of patient portals and smartphone health apps, 2020</article-title>
          <source>HealthIT.gov</source>
          <access-date>2022-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/data/data-briefs/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2020">https://www.healthit.gov/data/data-briefs/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2020</ext-link>
          </comment>
        </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>Morse</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Murugiah</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Soh</surname>
              <given-names>YC</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>TW</given-names>
            </name>
            <name name-style="western">
              <surname>Ming</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Mobile Health Applications for Pediatric Care: Review and Comparison</article-title>
          <source>Ther Innov Regul Sci</source>
          <year>2018</year>
          <month>05</month>
          <volume>52</volume>
          <issue>3</issue>
          <fpage>383</fpage>
          <lpage>391</lpage>
          <pub-id pub-id-type="doi">10.1177/2168479017725557</pub-id>
          <pub-id pub-id-type="medline">29714538</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <article-title>AHA Stats</article-title>
          <source>American Hospital Association</source>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://guide.prod.iam.aha.org/stats/bed-size-categories">https://guide.prod.iam.aha.org/stats/bed-size-categories</ext-link>
          </comment>
        </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>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bossuyt</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Mulrow</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Shamseer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Glanville</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grimshaw</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hróbjartsson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lalu</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loder</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo-Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Welch</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Whiting</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>PRISMA 2020 explanation and elaboration: updated guidance and exemplars for reporting systematic reviews</article-title>
          <source>BMJ</source>
          <year>2021</year>
          <month>03</month>
          <day>29</day>
          <volume>372</volume>
          <fpage>n160</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33781993"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.n160</pub-id>
          <pub-id pub-id-type="medline">33781993</pub-id>
          <pub-id pub-id-type="pmcid">PMC8005925</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>Harrington</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Rauch</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Leary</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Andrews</surname>
              <given-names>TR</given-names>
            </name>
          </person-group>
          <article-title>How Generalizable Is Freestanding Children's Hospital Data Such as PHIS (Pediatric Health Information System)?</article-title>
          <source>Pediatrics</source>
          <year>2021</year>
          <volume>147</volume>
          <issue>3_MeetingAbstract</issue>
          <fpage>567</fpage>
          <lpage>569</lpage>
          <pub-id pub-id-type="doi">10.1542/peds.147.3MA6.567</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <article-title>App review sentiment analysis made easy</article-title>
          <source>Appbot</source>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://appbot.co/app-review-sentiment-analysis">https://appbot.co/app-review-sentiment-analysis</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>How is the Sentiment Score calculated?</article-title>
          <source>appbot support centre</source>
          <year>2019</year>
          <access-date>2022-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://support.appbot.co/help-docs/sentiment-score">https://support.appbot.co/help-docs/sentiment-score</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vassolo</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Mac Cawley</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Tortorella</surname>
              <given-names>GL</given-names>
            </name>
            <name name-style="western">
              <surname>Fogliatto</surname>
              <given-names>FS</given-names>
            </name>
            <name name-style="western">
              <surname>Tlapa</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Narayanamurthy</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Hospital Investment Decisions in Healthcare 4.0 Technologies: Scoping Review and Framework for Exploring Challenges, Trends, and Research Directions</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>08</month>
          <day>26</day>
          <volume>23</volume>
          <issue>8</issue>
          <fpage>e27571</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/8/e27571/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27571</pub-id>
          <pub-id pub-id-type="medline">34435967</pub-id>
          <pub-id pub-id-type="pii">v23i8e27571</pub-id>
          <pub-id pub-id-type="pmcid">PMC8430851</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>Lu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Leigh</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Governor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The Use of Mobile Health Applications to Improve Patient Experience: Cross-Sectional Study in Chinese Public Hospitals</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>05</month>
          <day>23</day>
          <volume>6</volume>
          <issue>5</issue>
          <fpage>e126</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/5/e126/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9145</pub-id>
          <pub-id pub-id-type="medline">29792290</pub-id>
          <pub-id pub-id-type="pii">v6i5e126</pub-id>
          <pub-id pub-id-type="pmcid">PMC5990855</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>Shah</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Gvozdanovic</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gagnon</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Mobile App-Based Remote Patient Monitoring in Acute Medical Conditions: Prospective Feasibility Study Exploring Digital Health Solutions on Clinical Workload During the COVID Crisis</article-title>
          <source>JMIR Form Res</source>
          <year>2021</year>
          <month>01</month>
          <day>15</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>e23190</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2021/1/e23190/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23190</pub-id>
          <pub-id pub-id-type="medline">33400675</pub-id>
          <pub-id pub-id-type="pii">v5i1e23190</pub-id>
          <pub-id pub-id-type="pmcid">PMC7812915</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>Bao</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bardhan</surname>
              <given-names>IR</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Kirksey</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Patient–Provider Engagement and its Impact on Health Outcomes: A Longitudinal Study of Patient Portal Use</article-title>
          <source>MISQ</source>
          <year>2020</year>
          <month>6</month>
          <day>1</day>
          <volume>44</volume>
          <issue>2</issue>
          <fpage>699</fpage>
          <lpage>723</lpage>
          <pub-id pub-id-type="doi">10.25300/misq/2020/14180</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>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Fen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Hospital-Owned Apps in Taiwan: Nationwide Survey</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>01</month>
          <day>16</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>e22</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/1/e22/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.8636</pub-id>
          <pub-id pub-id-type="medline">29339347</pub-id>
          <pub-id pub-id-type="pii">v6i1e22</pub-id>
          <pub-id pub-id-type="pmcid">PMC5790962</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wanjala</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>How much storage do you need in a smartphone?</article-title>
          <source>MUO</source>
          <access-date>2022-04-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.makeuseof.com/how-much-smartphone-storage">https://www.makeuseof.com/how-much-smartphone-storage</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>Demographics of internet and home broadband usage in the United States</article-title>
          <source>Pew Research Center</source>
          <access-date>2022-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/internet/fact-sheet/internet-broadband">https://www.pewresearch.org/internet/fact-sheet/internet-broadband</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al Shamsi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Almutairi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Al Mashrafi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Al Kalbani</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Implications of Language Barriers for Healthcare: A Systematic Review</article-title>
          <source>Oman Med J</source>
          <year>2020</year>
          <month>03</month>
          <publisher-loc>Implications of Language Barriers for Healthcare</publisher-loc>
          <publisher-name>A Systematic Review. Oman Med J Internet Oman Medical Specialty Board</publisher-name>
          <fpage>e122</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martens</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Johann</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>On the emotion of users in app reviews</article-title>
          <source>arXiv csSE</source>
          <year>2017</year>
          <access-date>2022-09-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/pdf/1703.02256.pdf">https://arxiv.org/pdf/1703.02256.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nicolai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pascarella</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Palomba</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bacchelli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Healthcare android apps: a tale of the customers' perspective</article-title>
          <year>2019</year>
          <conf-name>Proceedings of the 3rd ACM SIGSOFT International Workshop on App Market Analytics</conf-name>
          <conf-date>August 27, 2019</conf-date>
          <conf-loc>New York, US</conf-loc>
          <fpage>33</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1145/3340496.3342758</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Watzlaf</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Barriers to and Facilitators of the Use of Mobile Health Apps From a Security Perspective: Mixed-Methods Study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>04</month>
          <day>16</day>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>e11223</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/4/e11223/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11223</pub-id>
          <pub-id pub-id-type="medline">30990458</pub-id>
          <pub-id pub-id-type="pii">v7i4e11223</pub-id>
          <pub-id pub-id-type="pmcid">PMC6488955</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Galvin</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>DeMuro</surname>
              <given-names>PR</given-names>
            </name>
          </person-group>
          <article-title>Developments in Privacy and Data Ownership in Mobile Health Technologies, 2016-2019</article-title>
          <source>Yearb Med Inform</source>
          <year>2020</year>
          <month>08</month>
          <day>21</day>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>32</fpage>
          <lpage>43</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0040-1701987"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0040-1701987</pub-id>
          <pub-id pub-id-type="medline">32823298</pub-id>
          <pub-id pub-id-type="pmcid">PMC7442507</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Marinescu</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Chamberlain</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Smart</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Online reviews are biased. Here’s how to fix them</article-title>
          <source>Harvard Business Review</source>
          <access-date>2022-08-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hbr.org/2018/03/online-reviews-are-biased-heres-how-to-fix-them">https://hbr.org/2018/03/online-reviews-are-biased-heres-how-to-fix-them</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Mechanisms of negativity bias: An empirical exploration of app reviews in Apple's App Store</article-title>
          <source>Core</source>
          <access-date>2022-08-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://core.ac.uk/download/pdf/301358814.pdf">https://core.ac.uk/download/pdf/301358814.pdf</ext-link>
          </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>Yin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Research Note—When Do Consumers Value Positive vs. Negative Reviews? An Empirical Investigation of Confirmation Bias in Online Word of Mouth</article-title>
          <source>Information Systems Research</source>
          <year>2016</year>
          <month>03</month>
          <volume>27</volume>
          <issue>1</issue>
          <fpage>131</fpage>
          <lpage>144</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://paperpile.com/b/0zkV3q/jrkV"/>
          </comment>
          <pub-id pub-id-type="doi">10.1287/isre.2015.0617</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>Stoyanov</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Hides</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kavanagh</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Zelenko</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Tjondronegoro</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mani</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile app rating scale: a new tool for assessing the quality of health mobile apps</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2015</year>
          <month>03</month>
          <day>11</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e27</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/1/e27/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id>
          <pub-id pub-id-type="medline">25760773</pub-id>
          <pub-id pub-id-type="pii">v3i1e27</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376132</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Biswas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tania</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Kabir</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmud</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kemal</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>ACCU3RATE: A mobile health application rating scale based on user reviews</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <volume>16</volume>
          <issue>12</issue>
          <fpage>e0258050</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0258050"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0258050</pub-id>
          <pub-id pub-id-type="medline">34914718</pub-id>
          <pub-id pub-id-type="pii">PONE-D-21-09300</pub-id>
          <pub-id pub-id-type="pmcid">PMC8675707</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
