<?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">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</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">v8i2e15364</article-id>
      <article-id pub-id-type="pmid">32130163</article-id>
      <article-id pub-id-type="doi">10.2196/15364</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>Medication Management Apps for Diabetes: Systematic Assessment of the Transparency and Reliability of Health Information Dissemination</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Sezgin</surname>
            <given-names>Emre</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Baptista</surname>
            <given-names>Shaira</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hussain</surname>
            <given-names>Tasmeen</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Fatehi</surname>
            <given-names>Farhad</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Huang</surname>
            <given-names>Zhilian</given-names>
          </name>
          <degrees>MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Centre for Population Health Sciences</institution>
            <institution>Lee Kong Chian School of Medicine</institution>
            <institution>Nanyang Technological University</institution>
            <addr-line>11 Mandalay Road</addr-line>
            <addr-line>Clinical Sciences Building, Level 18</addr-line>
            <addr-line>Singapore, 308322</addr-line>
            <country>Singapore</country>
            <phone>65 65923945</phone>
            <email>ZHUANG014@e.ntu.edu.sg</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4445-1669</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Lum</surname>
            <given-names>Elaine</given-names>
          </name>
          <degrees>Adv Prac Pharm, BPharm, MClinPharm, 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-0002-0853-3018</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Car</surname>
            <given-names>Josip</given-names>
          </name>
          <degrees>FRCP (Edin)​, FFPH, MSc, DIC, PhD, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8969-371X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Centre for Population Health Sciences</institution>
        <institution>Lee Kong Chian School of Medicine</institution>
        <institution>Nanyang Technological University</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>NTU Institute for Health Technologies</institution>
        <institution>Interdisciplinary Graduate School</institution>
        <institution>Nanyang Technological University</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Institute of Health and Biomedical Innovation</institution>
        <institution>Queensland University of Technology</institution>
        <addr-line>Brisbane</addr-line>
        <country>Australia</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>School of Clinical Sciences</institution>
        <institution>Faculty of Health</institution>
        <institution>Queensland University of Technology</institution>
        <addr-line>Brisbane</addr-line>
        <country>Australia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Zhilian Huang <email>ZHUANG014@e.ntu.edu.sg</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>2</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>19</day>
        <month>2</month>
        <year>2020</year>
      </pub-date>
      <volume>8</volume>
      <issue>2</issue>
      <elocation-id>e15364</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>7</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>21</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>29</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>17</day>
          <month>12</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Zhilian Huang, Elaine Lum, Josip Car. Originally published in JMIR mHealth and uHealth (http://mhealth.jmir.org), 19.02.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://mhealth.jmir.org/2020/2/e15364/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Smartphone apps are increasingly used for diabetes self-management because of their ubiquity and ability to help users to personalize health care management. The number of diabetes apps has proliferated in recent years, but only a small subset of apps that pose a higher risk are regulated by governmental agencies. The transparency and reliability of information sources are unclear for apps that provide health care advice and are not regulated by governmental agencies.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to assess the transparency and reliability of information disseminated via diabetes apps against 8 criteria adapted from the Health On the Net code of conduct (HONcode) principles.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>English-language diabetes-related terms were searched on a market explorer (42matters) on June 12, 2018. Apps with medication and blood glucose management features were downloaded and evaluated against the App-HONcode criteria adapted from the 8 HONcode principles: authoritative, complementarity, privacy, attribution, justifiability, transparency, financial disclosure, and advertising policy. Apps were profiled by operating platforms (ie, Android and iOS) and the number of downloads (ie, Android only: ≥100,000 downloads and &#60;100,000 downloads).</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 143 apps (81 Android and 62 iOS) were downloaded and assessed against the adapted App-HONcode criteria. Most of the apps on the Android and iOS platforms fulfilled between 2 and 6 criteria, but few (20/143, 14.0%) apps mentioned the qualifications of individuals who contributed to app development. Less than half (59/143, 39.2%) of the apps disclaimed that the information provided or app functions do not replace the advice of the health care provider. A higher proportion of iOS apps fulfilled 5 or more App-HONcode criteria compared with Android apps. However, Android apps were more likely to have the developer’s email listed on the app store (Android: 75/81, 98%; and iOS: 52/62, 84%; <italic>P</italic>=.005) compared with iOS apps. Of the Android apps assessed, a significantly higher proportion of highly downloaded apps had a privacy and confidentiality clause (high downloads: 15/17, 88%; and low downloads: 33/64, 52%; <italic>P</italic>=.006) and were more likely to discuss their financial sources (high downloads: 14/17, 82%; and low downloads: 32/64, 50%; <italic>P</italic>=.03) compared with apps with a low number of downloads.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Gaps in the disclosure of the developer’s qualification, funding source, and the complementary role of the app in disease management were identified. App stores, developers, and medical providers should collaborate to close these gaps and provide more transparency and reliability to app users. Future work can further examine the consent-seeking process for data collection, data management policies, the appropriateness of advertising content, and clarity of privacy clause of these apps.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health apps</kwd>
        <kwd>digital health</kwd>
        <kwd>diabetes</kwd>
        <kwd>privacy</kwd>
        <kwd>evidence-based guidance</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Smartphone apps, software designed to run on mobile devices, have integrated into many aspects of daily lives and are increasingly used for disease management. For example, there are more than 2000 consumer apps to choose from to self-manage diabetes [<xref ref-type="bibr" rid="ref1">1</xref>]. In contrast to Web-based information accessed from the computer, apps can help the user to conveniently access information with their portability and improved technological capabilities, such as increased human interaction, interoperability with other devices, and easy data collection. Health apps can have a multitude of uses, including offering advice on healthy living, communication with health care providers, and providing decision support through granular biometric data collection (eg, blood glucose) [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. The adoption of health apps for chronic conditions such as diabetes is expected to grow [<xref ref-type="bibr" rid="ref5">5</xref>]. There are currently 2.5 billion smartphone users in the world [<xref ref-type="bibr" rid="ref6">6</xref>] and more than 300,000 health apps available for consumer download [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>One main reason for the proliferation of health apps is the low barrier of entry for app developers to publish apps [<xref ref-type="bibr" rid="ref3">3</xref>]. Although the 2 major app stores (ie, Apple and Google Play) review apps before publication (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), many apps that do not conform to the prereview checklist fall through the cracks and are published. The regulation of app stores also falls outside the purview of governmental agencies, such as purview of the Food and Drug Administration (FDA) [<xref ref-type="bibr" rid="ref7">7</xref>]. Only a small subset of apps that can pose a higher risk and meet the regulatory definition of <italic>device</italic> are regulated by the FDA [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Therefore, apps with inaccurate content or advertisements may still be published and be available to consumers [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. The lack of transparency regarding an app’s source of content may compromise the reliability of the information it disseminates [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>] and can potentially mislead or cause harm to patients who have low health literacy [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
        <p>Concerns over the credibility and reliability of Web-based health information sources began to surface in the early days of internet usage [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. The Health On the Net code of conduct (HONcode), which covers 8 principles (ie, authoritative, complementarity, privacy, attribution, justifiability, transparency, financial disclosure, and advertising policy) for website certification, was developed to help guide and standardize the reliability of health and medical information published on the internet [<xref ref-type="bibr" rid="ref19">19</xref>]. Websites that were certified by the HONcode were assessed to be of higher quality and may reduce consumers’ burden of searching for good-quality websites [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>As part of a larger study investigating the medication management features of diabetes apps [<xref ref-type="bibr" rid="ref22">22</xref>], this study aimed to assess the transparency and reliability of information disseminated via these apps against 8 criteria adapted from the HONcode principles.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Development of App Assessment Criteria</title>
        <p>We adapted the 8 HONcode principles (ie, authoritative, complementarity, privacy, attribution, justifiability, transparency, financial disclosure, and advertising policy) and termed it the App-HONcode criteria to suit the context of health apps and apps assessment. The initial versions of our criteria were piloted with highly downloaded (≥100,000 downloads) diabetes apps to refine and improve the clarity of the assessment criteria. Unclear statements were discussed among the app assessment team members until a consensus was reached. The <italic>not applicable (N/A)</italic> option was included for the assessment of <italic>attribution</italic> and <italic>justifiability</italic> to account for apps that did not provide health information within the app. The final assessment criteria are shown in (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Adapted Health On the Net code of conduct criteria for health app assessment.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="290"/>
            <col width="420"/>
            <col width="130"/>
            <thead>
              <tr valign="bottom">
                <td>Attribute</td>
                <td>HONcode<sup>a</sup></td>
                <td>App-HONcode criteria</td>
                <td>Options</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Authoritative</td>
                <td>The qualifications of the authors are indicated.</td>
                <td>Does the app indicate the qualifications of specific individuals who developed or contributed to the development of the app?</td>
                <td>Yes or no</td>
              </tr>
              <tr valign="top">
                <td>Complementarity</td>
                <td>Information should support, not replace, the doctor-patient relationship.</td>
                <td>Is there a disclaimer stating or which implies that the information provided and/or app functions do not replace the health care provider’s advice?</td>
                <td>Yes or no</td>
              </tr>
              <tr valign="top">
                <td>Privacy</td>
                <td>Respect the privacy and confidentiality of personal data submitted to the site by the visitor.</td>
                <td>Is there a privacy and confidentiality clause in the app?</td>
                <td>Yes or no</td>
              </tr>
              <tr valign="top">
                <td>Attribution</td>
                <td>Cite the source(s) and date of published information on medical and health pages.</td>
                <td>Are information sources in the app cited?</td>
                <td>Yes, no, or N/A<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td>Justifiability</td>
                <td>Justifiability: site must back up claims relating to benefits and performance.</td>
                <td>Are the claims relating to benefits and performance in the app description backed up by evidence? (Answer <italic>N/A</italic> if there are no claims)</td>
                <td>Yes, no, or N/A</td>
              </tr>
              <tr valign="top">
                <td>Transparency</td>
                <td>Accessible presentation and accurate email contact.</td>
                <td>Are the developers contactable by email?</td>
                <td>Yes or no</td>
              </tr>
              <tr valign="top">
                <td>Financial disclosure</td>
                <td>Identify funding sources.</td>
                <td>Does the app indicate any funding sources? (<italic>Yes</italic> if the app is managed by a registered commercial company)</td>
                <td>Yes or no</td>
              </tr>
              <tr valign="top">
                <td>Advertising policy</td>
                <td>Clearly distinguish advertising from editorial content.</td>
                <td>Are advertorials distinguishable from content of the app?</td>
                <td>Yes, no or no advertising</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>HONcode: Health On the Net code of conduct.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>App Selection and Assessment</title>
        <p>As the app assessments were part of a larger study investigating medicines management functionalities of diabetes apps, a more detailed description of app selection and assessment can be found in another paper [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
        <sec>
          <title>App Search Strategy</title>
          <p>Diabetes terms in the English language were searched in the Google Play and Apple app stores via an app market explorer, 42matters [<xref ref-type="bibr" rid="ref23">23</xref>], on June 12, 2018, to identify apps that were marketed for diabetes self-management. The search terms <italic>(Diabetes OR Diabetic OR Diabetics) OR (glucose OR glycaemic OR glycemic OR blood sugar OR HbA<sub>1c</sub> OR A<sub>1c</sub>) OR insulin</italic> were used to search app descriptions, and a list of app titles with descriptions was produced for screening.</p>
        </sec>
        <sec>
          <title>App Selection</title>
          <p>A random sample of 100 apps was first screened by 2 researchers (ZH and MLT) to ensure consistency in interpretation of the inclusion and exclusion criteria listed below. Differences in interpretations were resolved via consensus discussion with 2 other team members (EL and GJ). Random samples of apps were rescreened until an interrater agreement of above 80.0% was achieved.</p>
        </sec>
        <sec>
          <title>Inclusion Criteria</title>
          <p>The inclusion criteria were as follows: Apps with medication self-management features (ie, medication scheduling, reminders, tracking, information provision, and adherence review), apps with any blood glucose logging features, apps in the English language, free apps, and apps requiring payment.</p>
        </sec>
        <sec>
          <title>Exclusion criteria</title>
          <p>The exclusion criteria were as follows: Patient health portals linking to patients’ electronic health records, apps that were not updated after January 1, 2017, intended only for health care professionals, insulin calculators/bolus correctors only, apps with exclusive blood glucose monitoring device tie-in requirement (ie, not permitting manual entry of blood glucose values), apps duplicated on the same platform, apps with regional restrictions, and technical problems (eg, crashes, screen hangs, unable to login, and unable to download).</p>
        </sec>
        <sec>
          <title>App Assessments</title>
          <p>Included apps were evaluated against the adapted App-HONcode criteria. In total, 5 team members (ZH, EL, GJ, CT, and MLT) underwent a calibration exercise to ensure consistency in criteria interpretation before the app assessments. Apps available on the iOS and Android platforms were treated as unique apps and assessed on both platforms because of possible differences in versions across platforms. The number of <italic>yes</italic> responses was summed up for each app to determine the number of App-HONcode criteria met. <italic>N/A</italic> responses for <italic>attribution</italic> and <italic>justifiability</italic> were treated as <italic>not meeting the criteria</italic> for a more conservative approach, whereas the <italic>no advertising</italic> response for <italic>advertising policy</italic> was treated as a <italic>yes</italic> (conforming to this principle).</p>
        </sec>
      </sec>
      <sec>
        <title>Statistical Analyses</title>
        <p>Apps were grouped by operating platform (ie, Android and iOS) and profiled according to each App-HONcode criterion using descriptive statistics. Only Android apps were further classified by the number of downloads (ie, ≥100,000 downloads and &#60;100,000 downloads), as information on the number of downloads was not available for iOS apps. Pearson chi-square test was used for comparisons between groups, and a 2-tailed Fisher exact test was used where the expected count was less than 5 in a group. Statistical significance was set at a <italic>P</italic> value of less than .05. All analyses were performed using SPSS (version 22; IBM Corp).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>App Screening</title>
        <p>We identified and downloaded 351 apps (191 Android and 160 iOS) after app title and description screening, of which 143 apps (81 Android and 62 iOS) met the inclusion criteria and were assessed against the app assessment criteria. The detailed app search results can be found in our study [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Characteristics of Included Apps</title>
        <p>The number and proportion of the assessed apps meeting the App-HONcode criteria are shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>. Most of the apps on the Android and iOS platforms fulfilled between 2 and 5 criteria; 1 Android app met all 8 criteria, whereas another did not meet any criteria. A higher proportion of apps published on the iOS platform met more App-HONcode criteria compared with apps on the Android platform. For example, 43.6% of iOS apps met at least five App-HONcode criteria compared with 28.3% of Android apps.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>The number and proportion of diabetes apps meeting the App-HONcode app criteria. The number of Yes responses were summed up for each app to determine the number of app-HONcode criteria met. N/A responses for attribution and justifiability were treated as no, whereas the no advertising response for advertising policy was treated as a yes. HONcode: Health On the Net code of conduct.</p>
          </caption>
          <graphic xlink:href="mhealth_v8i2e15364_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The profile of app attributes grouped by platform is shown in <xref ref-type="table" rid="table2">Table 2</xref>. Few (20/143, 14.0%) apps mentioned the qualifications of individuals who contributed to app development. Less than half (56/143, 39.2%) of the apps had a disclaimer stating that the information provided/app functions do not replace a health care provider’s advice, and approximately two-thirds (93/143, 65.0%) of apps had a privacy and confidentiality clause. Of the apps providing health or medical information or made claims on its efficacy, only one-third cited their information sources (15/42, 36%) and/or backed up the claims relating to benefits and performance in the app by evidence (7/23, 30%).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Profile of app attribute grouped by platform.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="450"/>
            <col width="120"/>
            <col width="120"/>
            <col width="90"/>
            <col width="70"/>
            <thead>
              <tr valign="bottom">
                <td>HONcode<sup>a</sup> principle</td>
                <td>App-HONcode criteria</td>
                <td>All apps, n (%)</td>
                <td>Android, n (%)</td>
                <td>iOS, n (%)</td>
                <td><italic>P</italic> value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Authoritative</td>
                <td>Does the app indicate the qualifications of specific individuals who developed or contributed to the development of the app?</td>
                <td>20 (14.0)<sup>b</sup></td>
                <td>9 (11)<sup>c</sup></td>
                <td>11 (18)<sup>d</sup></td>
                <td>.33</td>
              </tr>
              <tr valign="top">
                <td>Complementarity</td>
                <td>Is there a disclaimer stating or which implies that the information provided and/or app functions do not replace the health care provider’s advice?</td>
                <td>56 (39.2)<sup>b</sup></td>
                <td>27 (33)<sup>c</sup></td>
                <td>29 (47)<sup>d</sup></td>
                <td>.12</td>
              </tr>
              <tr valign="top">
                <td>Privacy</td>
                <td>Is there a privacy and confidentiality clause in the app?</td>
                <td>93 (65.0)<sup>b</sup></td>
                <td>48 (59)<sup>c</sup></td>
                <td>45 (73)<sup>d</sup></td>
                <td>.11</td>
              </tr>
              <tr valign="top">
                <td>Attribution</td>
                <td>Are information sources in the app cited?</td>
                <td>15 (34)<sup>e,f</sup></td>
                <td>8 (36)<sup>e,g</sup></td>
                <td>7 (32)<sup>e,h</sup></td>
                <td>&#62;.99<sup>i</sup></td>
              </tr>
              <tr valign="top">
                <td>Justifiability</td>
                <td>Are the claims relating to benefits and performance in the app description backed up by evidence? (Answer <italic>not applicable</italic> if there are no claims)</td>
                <td>7 (30)<sup>e,j</sup></td>
                <td>4 (29)<sup>e,k</sup></td>
                <td>3 (33)<sup>e,l</sup></td>
                <td>&#62;.99<sup>i</sup></td>
              </tr>
              <tr valign="top">
                <td>Transparency</td>
                <td>Are the developers contactable by email?</td>
                <td>131 (91.6)<sup>b</sup></td>
                <td>79 (98)<sup>c</sup></td>
                <td>52 (84)<sup>d</sup></td>
                <td>.005<sup>m</sup></td>
              </tr>
              <tr valign="top">
                <td>Financial disclosure</td>
                <td>Does the app indicate any funding sources? (<italic>Yes</italic> if the app is managed by a registered commercial company)</td>
                <td>88 (61.5)<sup>b</sup></td>
                <td>46 (57)<sup>c</sup></td>
                <td>42 (68)<sup>d</sup></td>
                <td>.23</td>
              </tr>
              <tr valign="top">
                <td rowspan="2">Advertising policy</td>
                <td>There are no advertisements in the app</td>
                <td>119 (83.2)<sup>b</sup></td>
                <td>64 (79)<sup>c</sup></td>
                <td>55 (89)<sup>d</sup></td>
                <td>.18</td>
              </tr>
              <tr valign="top">
                <td>Are advertorials distinguishable from content of the app?</td>
                <td>18 (75)<sup>n,o</sup></td>
                <td>12 (71)<sup>n,p</sup></td>
                <td>6 (86)<sup>n,q</sup></td>
                <td>.63</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>HONcode: Health On the Net code of conduct.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>N=143.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>N=81.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>N=62.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>Not applicable removed before statistical analysis and percentage computation.</p>
            </fn>
            <fn id="table2fn6">
              <p><sup>f</sup>N=44.</p>
            </fn>
            <fn id="table2fn7">
              <p><sup>g</sup>N=22.</p>
            </fn>
            <fn id="table2fn8">
              <p><sup>h</sup>N=22.</p>
            </fn>
            <fn id="table2fn9">
              <p><sup>i</sup>Two-tailed <italic>P</italic> value calculated using Fisher exact test, as the expected count is less than 5 in at least one group.</p>
            </fn>
            <fn id="table2fn10">
              <p><sup>j</sup>N=23.</p>
            </fn>
            <fn id="table2fn11">
              <p><sup>k</sup>N=14.</p>
            </fn>
            <fn id="table2fn12">
              <p><sup>l</sup>N=9.</p>
            </fn>
            <fn id="table2fn13">
              <p><sup>m</sup>Statistical significance <italic>P</italic>&#60;.05 in the comparison between Android and iOS app features.</p>
            </fn>
            <fn id="table2fn14">
              <p><sup>n</sup>Percentage is computed by dividing the number of apps with distinguishable advertisements with the total number of apps with advertisements.</p>
            </fn>
            <fn id="table2fn15">
              <p><sup>o</sup>N=24.</p>
            </fn>
            <fn id="table2fn16">
              <p><sup>p</sup>N=17.</p>
            </fn>
            <fn id="table2fn17">
              <p><sup>q</sup>N=7.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>There were no significant differences between the Android and iOS platforms in the proportion of apps fulfilling each criterion except for the principle of <italic>transparency</italic>. Android apps had a significantly higher proportion of apps with the developer’s email listed on the Google play store compared with apps listed on the Apple store (Android: 75/81, 98%; and iOS: 52/62, 84%; <italic>P</italic>=.005). More than half (88/143, 61.5%) of the apps disclosed funding sources. Finally, most 119/143, 83.2%) of the assessed apps did not have advertisements; of apps with advertisements, three-fourths (18/24, 75%) were distinguishable from the content of the app.</p>
      </sec>
      <sec>
        <title>Android Apps by Downloads</title>
        <p><xref ref-type="table" rid="table3">Table 3</xref> shows the profile of app attribute grouped by a low (&#60;100,000 downloads) and high number of downloads (≥100,000 downloads) for Android apps. There were no significant differences between apps with a low and high number of downloads in terms of the <italic>authoritative, complementarity, attribution, justifiability, transparency,</italic> and <italic>advertising policy</italic>. A significantly higher proportion of highly downloaded apps had a privacy and confidentiality clause (high downloads: 15/17, 88%; and low downloads: 33/64, 52%; <italic>P</italic>=.006) and were more likely to discuss their funding sources (high downloads: 15/17, 82%; and low downloads: 32/64, 50%;</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Profile of Android app attributes grouped by the number of downloads.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="170"/>
            <col width="170"/>
            <col width="180"/>
            <col width="210"/>
            <col width="200"/>
            <col width="70"/>
            <thead>
              <tr valign="bottom">
                <td>HONcode<sup>a</sup> principle</td>
                <td>App-HONcode criteria</td>
                <td>All Android apps, n (%)</td>
                <td>&#60;100,000 downloads, n (%)</td>
                <td>≥100,000 downloads, n (%)</td>
                <td><italic>P</italic> value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Authoritative</td>
                <td>Does the app indicate the qualifications of specific individuals who developed or contributed to the development of the app?</td>
                <td>9 (11)<sup>b</sup></td>
                <td>8 (13)<sup>c</sup></td>
                <td>1 (6)<sup>d</sup></td>
                <td>.68<sup>e</sup></td>
              </tr>
              <tr valign="top">
                <td>Complementarity</td>
                <td>Is there a disclaimer stating or which implies that the information provided and/or app functions do not replace the health care provider’s advice?</td>
                <td>27 (33)<sup>b</sup></td>
                <td>18 (28)<sup>c</sup></td>
                <td>9 (53)<sup>d</sup></td>
                <td>.08</td>
              </tr>
              <tr valign="top">
                <td>Privacy</td>
                <td>Is there a privacy and confidentiality clause in the app?</td>
                <td>48 (59)<sup>b</sup></td>
                <td>33 (52)<sup>c</sup></td>
                <td>15 (88)<sup>d</sup></td>
                <td>.006<sup>f</sup></td>
              </tr>
              <tr valign="top">
                <td>Attribution</td>
                <td>Are information sources in the app cited?</td>
                <td>8 (36)<sup>g,h</sup></td>
                <td>7 (37)<sup>g,i</sup></td>
                <td>1 (33.3)<sup>g,j</sup></td>
                <td>&#62;.99<sup>e</sup></td>
              </tr>
              <tr valign="top">
                <td>Justifiability</td>
                <td>Are the claims relating to benefits and performance in the app description backed up by evidence? (Answer <italic>not applicable</italic> if there are no claims)</td>
                <td>4 (29)<sup>g,k</sup></td>
                <td>3 (30)<sup>g,l</sup></td>
                <td>1 (25)<sup>g,m</sup></td>
                <td>&#62;.99<sup>e</sup></td>
              </tr>
              <tr valign="top">
                <td>Transparency</td>
                <td>Are the developers contactable by email?</td>
                <td>79 (98)<sup>b</sup></td>
                <td>63 (98)<sup>c</sup></td>
                <td>16 (94)<sup>d</sup></td>
                <td>.38</td>
              </tr>
              <tr valign="top">
                <td>Financial disclosure</td>
                <td>Does the app indicate any funding sources? (<italic>Yes</italic> if the app is managed by a registered commercial company)</td>
                <td>46 (57)<sup>b</sup></td>
                <td>32 (50)<sup>c</sup></td>
                <td>14 (82)<sup>d</sup></td>
                <td>.026<sup>f</sup></td>
              </tr>
              <tr valign="top">
                <td rowspan="2">Advertising policy</td>
                <td>There are no advertisements in the app</td>
                <td>64 (79)<sup>b</sup></td>
                <td>50 (78)<sup>c</sup></td>
                <td>14 (82)<sup>d</sup></td>
                <td>&#62;.99<sup>e</sup></td>
              </tr>
              <tr valign="top">
                <td>Are advertorials distinguishable from content of the app?</td>
                <td>12 (71)<sup>n,o</sup></td>
                <td>11 (79)<sup>n,p</sup></td>
                <td>1 (33)<sup>n,q</sup></td>
                <td>.19<sup>n</sup></td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>HONcode: Health On the Net code of conduct.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>N=81.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>N=64.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>N=17.</p>
            </fn>
            <fn id="table3fn5">
              <p><sup>e</sup>Two-tailed <italic>P</italic> value calculated using Fisher exact test, as the expected count is less than 5 in at least one group.</p>
            </fn>
            <fn id="table3fn6">
              <p><sup>f</sup>Statistical significance <italic>P</italic>&#60;.05 in the comparison between Android and iOS app features.</p>
            </fn>
            <fn id="table3fn7">
              <p><sup>g</sup>Not applicable removed before statistical analysis and percentage computation.</p>
            </fn>
            <fn id="table3fn8">
              <p><sup>h</sup>N=22.</p>
            </fn>
            <fn id="table3fn9">
              <p><sup>i</sup>N=19</p>
            </fn>
            <fn id="table3fn10">
              <p><sup>j</sup>N=3.</p>
            </fn>
            <fn id="table3fn11">
              <p><sup>k</sup>N=14.</p>
            </fn>
            <fn id="table3fn12">
              <p><sup>l</sup>N=10.</p>
            </fn>
            <fn id="table3fn13">
              <p><sup>m</sup>N=4.</p>
            </fn>
            <fn id="table3fn14">
              <p><sup>n</sup>Percentage is computed by dividing the number of apps with distinguishable advertisements with the total number of apps with advertisements.</p>
            </fn>
            <fn id="table3fn15">
              <p><sup>o</sup>N=17.</p>
            </fn>
            <fn id="table3fn16">
              <p><sup>p</sup>N=14.</p>
            </fn>
            <fn id="table3fn17">
              <p><sup>q</sup>N=3.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Finding</title>
        <p>We evaluated 143 apps against 8 App-HONcode criteria to assess the transparency and reliability of information disseminated via diabetes apps. Most apps fulfilled between 2 and 5 assessment criteria, and only 1 Android app fulfilled all 8 criteria. Overall, a higher proportion of iOS apps fulfilled more App-HONcode criteria compared with Android apps, although the differences were not significant.</p>
        <p>Many apps were not transparent in indicating the content source of the app. More than half of the assessed apps did not fulfill important criteria, such as indicating the qualifications of individuals involved in the app development and disclaiming that the app does not replace health care provider’s advice. This concurs with a study assessing eczema apps, where only 15% of the app developers indicated their qualifications, and 46% disclaimed that the app does not replace the advice of the health care provider [<xref ref-type="bibr" rid="ref24">24</xref>]. Although it may be challenging to indicate the qualifications of all individuals involved in the development of a complex app, the qualifications of the main content contributors and a representation of their collaborators should minimally be quoted to account for the content source of the app.</p>
        <p>Approximately three-fourths of the assessed apps did not provide any health information. This was not surprising, as disease management apps tend to emphasize management aspects rather than educating the patient [<xref ref-type="bibr" rid="ref1">1</xref>], which, in our view, presents a missed opportunity for patient education, which can be incorporated into apps. Of the apps that provided health information, only one-third cited the source of information. Few of the assessed apps had claims relating to the benefits and performance of the app. However, only one-third of these apps backed the claims with evidence. Apps or any consumer products with unsubstantiated claims have the potential to mislead and cause harm to the undiscerning consumer [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Therefore, it is imperative for app stores to check the veracity of claims used in the app description before its publication on the app stores.</p>
        <p>Most apps had an email of the developer displayed, but the email address does not guarantee access to the app developer. We contacted the developers of apps that had access restrictions, and only 10% responded to our emails (2 emails sent a week apart). This percentage should be higher for apps that are accessible, but there is a possibility of inoperative email addresses being displayed on the app store. App stores should ensure the inclusion of a valid email address for all health apps for consumer inquiries.</p>
        <p>Privacy breaches can erode consumers’ trust in the app. Two-thirds of the apps assessed had a privacy and confidentiality clause. This was an improvement from a study published 6 years ago assessing the availability, scope, and transparency of mobile health (mHealth) app privacy policies on 600 commonly used mHealth iOS and Android apps [<xref ref-type="bibr" rid="ref15">15</xref>]. One explanation for this improvement could be the changes made to the app store policies to improve the quality of apps over the years [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. However, stricter scrutiny is required on the part of the app stores, given the absence of privacy policies in many of the assessed apps. Although there is an improvement in the presence of privacy policy of the English-language apps we assessed, those that are published on other platforms and in other languages may yield different assessment results.</p>
        <p>Approximately 40% of the assessed apps did not have their funding sources indicated. The funding source of an app will affect its development, quality, and the services provided. This represents a gap in which app stores can play a role to improve the quality assurance of health apps. Advertisements were not present in 80% of the assessed apps. The proportion of apps with advertisements in our study may be lower, as we assessed the best version of apps requiring in-app payments for feature upgrades. Previous studies have shown that paid apps were not of higher quality compared with free apps [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Approximately one-third of the in-app advertisements were judged as being nondistinguishable from the content of the app. We did not scrutinize the appropriateness of the advertising content, which may present an additional gap in the quality and reliability of information disseminated via these apps.</p>
        <p>The originators of the HONcode recently published an extension for apps—mHONcode—to cover the certification of health information disseminated on apps [<xref ref-type="bibr" rid="ref30">30</xref>]. This was only available after we completed our app assessments, but there are minimal conceptual differences between our App-HONcode and the mHONcode. Our criteria were worded to minimize the subjectivity of assessment by different researchers.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>There were limitations to the study, despite attempts to minimize bias. First, the scope was limited to diabetes management apps because of being part of a larger study investigating the medication management features of diabetes apps. However, our findings are generalizable to other diabetes apps, as the apps were identified using a systematic search and selection strategy. Second, our assessment criteria may have underrated apps that do not provide health information (eg, medication logging apps). Even so, many apps were not transparent in data privacy and in clearly distinguishing the complementarity of the app (ie, not replacing the health care provider’s advice). Third, the assessment may not reflect the current state of the apps because of constant app updates. However, we believe that our findings remain unchanged, as app updates were mainly for bug fixes and feature upgrades. Fourth, we neither assessed issues surrounding data management nor the content of privacy and confidentiality clauses, which may not accurately disclose the sharing of some personal information [<xref ref-type="bibr" rid="ref31">31</xref>]. Finally, app assessments were subjective to researcher interpretation, although we attempted to reduce researcher bias by piloting the assessment and using a standardized patient profile when interacting with apps.</p>
      </sec>
      <sec>
        <title>Implications and Future Research</title>
        <p>The fulfillment of the 8 App-HONcode criteria are actionable, but not many developers may be aware of the need to indicate background information or to check the content of advertisements, as their main aim is to get the app published. App developers and consumers would benefit from the availability of a standardized checklist to assess the information quality of health apps. It would be challenging for governments to regulate all health apps because of its ubiquity, pace of development, and ambiguity in definition. Therefore, app stores should play a larger role in making the transparency and reliability of information dissemination a basic requirement for app publication. As observed from our app assessments, owing to the higher barriers of entry currently set by the Apple app store (see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), it had a larger proportion of apps that fulfilled more App-HONcode criteria.</p>
        <p>As health apps collect a lot more user data than the internet, the consent-seeking process for data collection and data management policies of these apps should be evaluated in the future. The appropriateness of advertising and clarity of privacy clauses should also be checked, for diabetes management and other chronic disease management apps in other languages and on other platforms, to provide a more complete landscape of the transparency and reliability of information disseminated and collected through these apps.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Our systematic app assessments of the transparency and reliability of health information disseminated in diabetes apps discovered gaps in the disclosure of the developer’s qualification, funding source, and the complementary role of the app in disease management. App stores should play a larger role in scrutinizing app publication, as higher barriers of app entry will lead to the publication of apps with better disclosure of the app’s content source. As the development of the App-HONcode criteria is preliminary, future work can further examine the consent-seeking process for data collection, data management policies, the appropriateness of advertising content, and the clarity of privacy clauses.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Selected pre-review app publication checklist of Apple and Google Play app stores.</p>
        <media xlink:href="mhealth_v8i2e15364_app1.docx" xlink:title="DOCX File , 38 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">FDA</term>
          <def>
            <p>Food and Drug Administration</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">HONcode</term>
          <def>
            <p>Health On the Net code of conduct</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was funded by the Nanyang Technological University, Singapore, through (1) the Centre for Population Health Sciences, Lee Kong Chian School of Medicine, Nanyang Technological University, Singapore; (2) the Ageing Research Institute for Society and Education, Nanyang Technological University, Singapore; and (3) the Institute for Health Technologies, Nanyang Technological University, Singapore. The funder did not have direct involvement in the research including manuscript preparation, apart from employing the authors. The research presented in this paper is solely the responsibility of the authors and does not reflect the views of the funder. The authors wish to acknowledge Mr Geronimo Jimenez for his input in piloting and refining the app assessment criteria and Mr Geronimo Jimenez, Ms Christina Tan, and Ms My Linh Thai for their assistance in app assessment. ZH would like to acknowledge funding from the Nanyang Technological University Research Scholarship.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>ZH conceptualized and contributed to the development and refinement of the adapted HONcode app assessment criteria, screened apps, assessed apps, cleaned and analyzed data, interpreted data, and drafted and revised the manuscript. EL coconceptualized and provided critical input into the developed app assessment criteria, assessed apps, interpreted data, and revised the manuscript. JC conceptualized the study, obtained the funding, supervised the team, and provided critical input into all stages of the study and critical review of the draft manuscript. All authors reviewed and approved the final version of the manuscript before submission.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Soljak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Boehm</surname>
              <given-names>BO</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Clinical relevance of smartphone apps for diabetes management: a global overview</article-title>
          <source>Diabetes Metab Res Rev</source>
          <year>2018</year>
          <month>05</month>
          <volume>34</volume>
          <issue>4</issue>
          <fpage>e2990</fpage>
          <pub-id pub-id-type="doi">10.1002/dmrr.2990</pub-id>
          <pub-id pub-id-type="medline">29431916</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>Dayer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Heldenbrand</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gubbins</surname>
              <given-names>PO</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>BC</given-names>
            </name>
          </person-group>
          <article-title>Smartphone medication adherence apps: potential benefits to patients and providers</article-title>
          <source>J Am Pharm Assoc (2003)</source>
          <year>2013</year>
          <volume>53</volume>
          <issue>2</issue>
          <fpage>172</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23571625"/>
          </comment>
          <pub-id pub-id-type="doi">10.1331/JAPhA.2013.12202</pub-id>
          <pub-id pub-id-type="medline">23571625</pub-id>
          <pub-id pub-id-type="pii">S1544-3191(15)30311-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC3919626</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>West</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Giraud-Carrier</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Barrett</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>There's an app for that: content analysis of paid health and fitness apps</article-title>
          <source>J Med Internet Res</source>
          <year>2012</year>
          <month>05</month>
          <day>14</day>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>e72</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2012/3/e72/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1977</pub-id>
          <pub-id pub-id-type="medline">22584372</pub-id>
          <pub-id pub-id-type="pii">v14i3e72</pub-id>
          <pub-id pub-id-type="pmcid">PMC3799565</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>Tran</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tran</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>Smartphone-based glucose monitors and applications in the management of diabetes: an overview of 10 salient 'apps' and a novel smartphone-connected blood glucose monitor</article-title>
          <source>Clin Diabetes</source>
          <year>2012</year>
          <volume>30</volume>
          <issue>4</issue>
          <fpage>173</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.2337/diaclin.30.4.173</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <source>IQVIA</source>
          <year>2017</year>
          <month>11</month>
          <day>7</day>
          <access-date>2019-06-03</access-date>
          <comment>The Growing Value of Digital Health: Evidence and Impact on Human Health and the Healthcare System<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iqvia.com/institute/reports/the-growing-value-of-digital-health">https://www.iqvia.com/institute/reports/the-growing-value-of-digital-health</ext-link>
                         <ext-link ext-link-type="webcite" xlink:href="78qkViDOa"/>                         </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Statista Research Department</collab>
          </person-group>
          <source>Wayback Machine - Internet Archive</source>
          <year>2016</year>
          <access-date>2019-07-04</access-date>
          <comment>Number of Smartphone Users Worldwide From 2014 to 2020 (in Billions)<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://web.archive.org/web/20190704081902/https:/www.statista.com/statistics/330695/number-of-smartphone-users-worldwide/">https://web.archive.org/web/20190704081902/https:/www.statista.com/statistics/330695/number-of-smartphone-users-worldwide/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Food and Drug Administration</collab>
          </person-group>
          <source>Wayback Machine - Internet Archive</source>
          <year>2015</year>
          <access-date>2019-07-04</access-date>
          <comment>Mobile Medical Applications: Guidance for Industry and Food and Drug Administration Staff<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://web.archive.org/web/20190704082425/https://www.fda.gov/media/80958/download">https://web.archive.org/web/20190704082425/https://www.fda.gov/media/80958/download</ext-link>
                                                </comment>
        </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>Cortez</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>IG</given-names>
            </name>
            <name name-style="western">
              <surname>Kesselheim</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>FDA regulation of mobile health technologies</article-title>
          <source>N Engl J Med</source>
          <year>2014</year>
          <month>07</month>
          <day>24</day>
          <volume>371</volume>
          <issue>4</issue>
          <fpage>372</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMhle1403384</pub-id>
          <pub-id pub-id-type="medline">25054722</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>Torous</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>LW</given-names>
            </name>
          </person-group>
          <article-title>Needed innovation in digital health and smartphone applications for mental health: transparency and trust</article-title>
          <source>JAMA Psychiatry</source>
          <year>2017</year>
          <month>05</month>
          <day>1</day>
          <volume>74</volume>
          <issue>5</issue>
          <fpage>437</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1001/jamapsychiatry.2017.0262</pub-id>
          <pub-id pub-id-type="medline">28384700</pub-id>
          <pub-id pub-id-type="pii">2616170</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>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Landman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Levine</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Health apps and health policy: what is needed?</article-title>
          <source>J Am Med Assoc</source>
          <year>2018</year>
          <month>11</month>
          <day>20</day>
          <volume>320</volume>
          <issue>19</issue>
          <fpage>1975</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2018.14378</pub-id>
          <pub-id pub-id-type="medline">30326025</pub-id>
          <pub-id pub-id-type="pii">2707668</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>Huckvale</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Adomaviciute</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Prieto</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Leow</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Smartphone apps for calculating insulin dose: a systematic assessment</article-title>
          <source>BMC Med</source>
          <year>2015</year>
          <month>05</month>
          <day>6</day>
          <volume>13</volume>
          <fpage>106</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-015-0314-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-015-0314-7</pub-id>
          <pub-id pub-id-type="medline">25943590</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-015-0314-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC4433091</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>Huckvale</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Apps for asthma self-management: a systematic assessment of content and tools</article-title>
          <source>BMC Med</source>
          <year>2012</year>
          <month>11</month>
          <day>22</day>
          <volume>10</volume>
          <fpage>144</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/1741-7015-10-144"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1741-7015-10-144</pub-id>
          <pub-id pub-id-type="medline">23171675</pub-id>
          <pub-id pub-id-type="pii">1741-7015-10-144</pub-id>
          <pub-id pub-id-type="pmcid">PMC3523082</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>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cade</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Allman-Farinelli</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The most popular smartphone apps for weight loss: a quality assessment</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2015</year>
          <month>12</month>
          <day>16</day>
          <volume>3</volume>
          <issue>4</issue>
          <fpage>e104</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/4/e104/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.4334</pub-id>
          <pub-id pub-id-type="medline">26678569</pub-id>
          <pub-id pub-id-type="pii">v3i4e104</pub-id>
          <pub-id pub-id-type="pmcid">PMC4704947</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>Wicks</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chiauzzi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>'Trust but verify'--five approaches to ensure safe medical apps</article-title>
          <source>BMC Med</source>
          <year>2015</year>
          <month>09</month>
          <day>25</day>
          <volume>13</volume>
          <fpage>205</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-015-0451-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-015-0451-z</pub-id>
          <pub-id pub-id-type="medline">26404791</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-015-0451-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC4583172</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>Sunyaev</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dehling</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>PL</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>Availability and quality of mobile health app privacy policies</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2015</year>
          <month>04</month>
          <volume>22</volume>
          <issue>e1</issue>
          <fpage>e28</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2013-002605</pub-id>
          <pub-id pub-id-type="medline">25147247</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2013-002605</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>Ghaddar</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>Valerio</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Adolescent health literacy: the importance of credible sources for online health information</article-title>
          <source>J Sch Health</source>
          <year>2012</year>
          <month>01</month>
          <volume>82</volume>
          <issue>1</issue>
          <fpage>28</fpage>
          <lpage>36</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1746-1561.2011.00664.x</pub-id>
          <pub-id pub-id-type="medline">22142172</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>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Quality of health information for consumers on the web: a systematic review of indicators, criteria, tools, and evaluation results</article-title>
          <source>J Assn Inf Sci Technol</source>
          <year>2015</year>
          <volume>66</volume>
          <issue>10</issue>
          <fpage>2071</fpage>
          <lpage>84</lpage>
          <pub-id pub-id-type="doi">10.1002/asi.23311</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>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hoti</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Emmerton</surname>
              <given-names>LM</given-names>
            </name>
          </person-group>
          <article-title>Interventions to assist health consumers to find reliable online health information: a comprehensive review</article-title>
          <source>PLoS One</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>e94186</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0094186"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0094186</pub-id>
          <pub-id pub-id-type="medline">24710348</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-07282</pub-id>
          <pub-id pub-id-type="pmcid">PMC3978031</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <source>Health On the Net</source>
          <year>1995</year>
          <access-date>2019-07-04</access-date>
          <comment>HONcode Certification<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hon.ch/en/certification.html#principles">https://www.hon.ch/en/certification.html#principles</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Taki</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Elliott</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Laws</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Denney-Wilson</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Infant feeding websites and apps: a systematic assessment of quality and content</article-title>
          <source>Interact J Med Res</source>
          <year>2015</year>
          <month>09</month>
          <day>29</day>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>e18</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.i-jmr.org/2015/3/e18/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/ijmr.4323</pub-id>
          <pub-id pub-id-type="medline">26420339</pub-id>
          <pub-id pub-id-type="pii">v4i3e18</pub-id>
          <pub-id pub-id-type="pmcid">PMC4704960</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>Loy</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>EE</given-names>
            </name>
            <name name-style="western">
              <surname>Yap</surname>
              <given-names>KY</given-names>
            </name>
          </person-group>
          <article-title>Quality assessment of medical apps that target medication-related problems</article-title>
          <source>J Manag Care Spec Pharm</source>
          <year>2016</year>
          <month>10</month>
          <volume>22</volume>
          <issue>10</issue>
          <fpage>1124</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.doi.org/10.18553/jmcp.2016.22.10.1124"/>
          </comment>
          <pub-id pub-id-type="doi">10.18553/jmcp.2016.22.10.1124</pub-id>
          <pub-id pub-id-type="medline">27668561</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>Huang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Lum</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Jimenez</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Semwal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sloot</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Medication management support in diabetes: a systematic assessment of diabetes self-management apps</article-title>
          <source>BMC Med</source>
          <year>2019</year>
          <month>07</month>
          <day>17</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>127</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-019-1362-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-019-1362-1</pub-id>
          <pub-id pub-id-type="medline">31311573</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-019-1362-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC6636047</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <source>42matters: Mobile App Intelligence</source>
          <access-date>2019-07-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://42matters.com/">https://42matters.com/</ext-link>
          </comment>
        </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>van Galen</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Koh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thng</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Eczema apps conformance with clinical guidelines: a systematic assessment of functions, tools and content</article-title>
          <source>Br J Dermatol</source>
          <year>2019</year>
          <month>06</month>
          <day>9</day>
          <pub-id pub-id-type="doi">10.1111/bjd.18152</pub-id>
          <pub-id pub-id-type="medline">31179535</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vladeck</surname>
              <given-names>DC</given-names>
            </name>
          </person-group>
          <article-title>Truth and Consequences: The Perils of Half-Truths and Unsubstantiated Health Claims for Dietary Supplements</article-title>
          <source>J Public Policy Mark</source>
          <year>2000</year>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>132</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1509/jppm.19.1.132.16948</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <source>Apple Developer</source>
          <year>2019</year>
          <access-date>2019-10-27</access-date>
          <comment>App Store Review Guidelines<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://developer.apple.com/app-store/review/guidelines/">https://developer.apple.com/app-store/review/guidelines/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Salim</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Digital Information World</source>
          <year>2019</year>
          <month>04</month>
          <day>18</day>
          <access-date>2019-10-27</access-date>
          <comment>Google Tweaks Its Policy With Aim to Improve 'App Quality' in Play Store<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.digitalinformationworld.com/2019/04/google-android-policy-improve-app-quality-in-play-store.html">https://www.digitalinformationworld.com/2019/04/google-android-policy-improve-app-quality-in-play-store.html</ext-link>
                                                </comment>
        </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>Middelweerd</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mollee</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>van der Wal</surname>
              <given-names>CN</given-names>
            </name>
            <name name-style="western">
              <surname>Brug</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>te Velde</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Apps to promote physical activity among adults: a review and content analysis</article-title>
          <source>Int J Behav Nutr Phys Act</source>
          <year>2014</year>
          <month>07</month>
          <day>25</day>
          <volume>11</volume>
          <fpage>97</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ijbnpa.biomedcentral.com/articles/10.1186/s12966-014-0097-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12966-014-0097-9</pub-id>
          <pub-id pub-id-type="medline">25059981</pub-id>
          <pub-id pub-id-type="pii">s12966-014-0097-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC4132213</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>Bondaronek</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Alkhaldi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Slee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hamilton</surname>
              <given-names>FL</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Quality of publicly available physical activity apps: review and content analysis</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>03</month>
          <day>21</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>e53</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/3/e53/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9069</pub-id>
          <pub-id pub-id-type="medline">29563080</pub-id>
          <pub-id pub-id-type="pii">v6i3e53</pub-id>
          <pub-id pub-id-type="pmcid">PMC5885062</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <source>Health On the Net</source>
          <access-date>2019-07-04</access-date>
          <comment>mHONcode: The New Certification of Health Mobile Applications<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hon.ch/en/certification/app-certification-en.html">https://www.hon.ch/en/certification/app-certification-en.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huckvale</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Torous</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Larsen</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Assessment of the data sharing and privacy practices of smartphone apps for depression and smoking cessation</article-title>
          <source>JAMA Netw Open</source>
          <year>2019</year>
          <month>04</month>
          <day>5</day>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>e192542</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31002321"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2019.2542</pub-id>
          <pub-id pub-id-type="medline">31002321</pub-id>
          <pub-id pub-id-type="pii">2730782</pub-id>
          <pub-id pub-id-type="pmcid">PMC6481440</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
