<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v21i5e12390</article-id>
      <article-id pub-id-type="pmid">31045497</article-id>
      <article-id pub-id-type="doi">10.2196/12390</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Why Reviewing Apps Is Not Enough: Transparency for Trust (T4T) Principles of Responsible Health App Marketplaces</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>Davis</surname>
            <given-names>Sharon</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Rose</surname>
            <given-names>Jonathan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Stawarz</surname>
            <given-names>Katarzyna</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="author" id="contrib1" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>Til</given-names>
          </name>
          <degrees>BSc (Hon), MPhil, DPhil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>King's College London</institution>
            <institution>Department of Psychology</institution>
            <institution>Institute of Psychiatry, Psychology and Neuroscience</institution>
            <addr-line>De Crespigny Park</addr-line>
            <addr-line>London, SE5 8AF</addr-line>
            <country>United Kingdom</country>
            <phone>44 20 7848 0596</phone>
            <email>til.wykes@kcl.ac.uk</email>
          </address>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-5881-8003</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib2" equal-contrib="yes">
          <name name-style="western">
            <surname>Schueller</surname>
            <given-names>Stephen</given-names>
          </name>
          <degrees>BA, MA, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1003-0399</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
      <label>1</label>
      <institution>King's College London</institution>
      <institution>Department of Psychology</institution>  
      <institution>Institute of Psychiatry, Psychology and Neuroscience</institution>  
      <addr-line>London</addr-line>
      <country>United Kingdom</country></aff>
      <aff id="aff2">
      <label>2</label>
      <institution>Center for Behavioral Intervention Technologies</institution>
      <institution>North Western University</institution>  
      <addr-line>Chicago, IL</addr-line>
      <country>United States</country></aff>
      <author-notes>
        <corresp>Corresponding Author: Til Wykes 
        <email>til.wykes@kcl.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection"><month>05</month><year>2019</year></pub-date>
      <pub-date pub-type="epub">
        <day>02</day>
        <month>05</month>
        <year>2019</year>
      </pub-date>
      <volume>21</volume>
      <issue>5</issue>
      <elocation-id>e12390</elocation-id>
      <!--history from ojs - api-xml-->
      <history>
        <date date-type="received">
          <day>4</day>
          <month>10</month>
          <year>2018</year>
        </date>
        <date date-type="rev-request">
          <day>5</day>
          <month>1</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>1</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>9</day>
          <month>2</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Til Wykes, Stephen Schueller. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 02.05.2019.</copyright-statement>
      <copyright-year>2019</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2019/5/e12390/" xlink:type="simple"/>
      <abstract>
        <p>The overselling of health apps that may provide little benefit and even harm needs the health community’s immediate attention. With little formal regulation, a light-touch approach to consumer protection is now warranted to give customers a modicum of information to help them choose from the vast array of <italic>so-called</italic> health apps. We suggest 4 guiding principles that should be adopted to provide the consumer with information that can guide their choice at the point of download. We call these the Transparency for Trust (T4T) principles, which are derived from experimental studies, systematic reviews, and reports of patient concerns. The T4T principles are (1) privacy and data security, (2) development characteristics, (3) feasibility data, and (4) benefits. All our questions are in a simple form so that all consumers can understand them. We suggest that app stores should take responsibility for providing this information and store it with any app marketed as a health app. Even the absence of information would provide consumers with some understanding and fuel their choice. This would also provide some commercial impetus for app developers to consider this requested information from the outset.</p>
      </abstract>
      <kwd-group>
        <kwd>mobile health</kwd>
        <kwd>digital health applications</kwd>
        <kwd>consumer protection</kwd>
        <kwd>ehealth</kwd>
        <kwd>advertising standards</kwd>
        <kwd>digital mental health interventions</kwd>
        <kwd>digital health</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>Background</title>
      <p>Digital therapeutics are being touted as having the potential to transform health care by improving people’s experience, increasing effectiveness, and reducing costs. A few digital aids are recommended and integral to health services, but much of the e-health field depends on overselling [<xref ref-type="bibr" rid="ref1">1</xref>]. This business plan seems to be working as the digital health field was estimated to be worth $25 billion globally in 2017 [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. One US survey found that 58% of smartphone users have downloaded at least one health app [<xref ref-type="bibr" rid="ref4">4</xref>]. The overselling of health apps needs the health community’s immediate attention as many of these apps may provide little benefit and some apps may cause harm. With little formal regulation, alternative light-touch approaches to consumer protection are necessary to give customers a modicum of information as a basis for choosing from the vast array of <italic>so-called</italic> health apps.</p>
      <p>We believe that simple, but informative, evidence should be available at the point of downloading and propose 4 succinct aspects that represent the critical information required for responsible health app marketplaces. We refer to these 4 principles—privacy and data security, development practices, feasibility, and health benefits—as the Transparency for Trust (T4T) principles. The goal of these principles is to operationalize efforts that can be made by app marketplaces to answer calls for better oversight and backing up products with data and research [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. These T4T principles draw from several sources including patient and regulatory perspectives, recent systematic reviews, and experimental studies (eg [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]). We have used the definition of a health app from Innovate UK as those apps that contribute to the physical, mental, or social well-being of the user [<xref ref-type="bibr" rid="ref15">15</xref>]. Our principles are designed to be applicable to the whole panoply of health apps from sleep apps to diabetes apps, symptom trackers to mindfulness interventions eg[<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. The fastest growing segment of digital therapeutics is health apps. Current estimates suggest that over 300,000 health apps exist with a recent yearly growth rate of 25% [<xref ref-type="bibr" rid="ref17">17</xref>]. The rapid growth of products and lack of growth of information and regulation have resulted in very little information to separate quality health apps from those that are at best useless and at worst harmful. As a result, consumers are left to navigate the app stores alone. For one fast-growing sector, digital mental health, the likelihood of using an app is also affected by the relative lack of access or choice of mental health services as well as the stigma and discrimination experienced by sufferers and the interrelationship with physical health. We know, for instance, that people with depression face a higher risk of developing heart disease than individuals without depression and that following a heart attack, each additional depressive symptom that develops increases the risk of another heart attack by 15% [<xref ref-type="bibr" rid="ref17">17</xref>]. Mental health problems also affect morbidity in other disorders such as rheumatoid arthritis and asthma [<xref ref-type="bibr" rid="ref16">16</xref>]. We have used examples from mental health, but our principles are intended to inform and empower all health app users.</p>
      </sec>
      <sec>
        <title>Why Do We Need Some Simple Principles?</title>
        <sec>
          <title>Exponential Growth and Poor Regulation</title>
          <p>The use of digital technologies to alleviate, prevent, or maintain health has been recognized for many years, but although it offers enormous potential to rethink how services are provided, there are large roadblocks in its way (eg [<xref ref-type="bibr" rid="ref19">19</xref>]). A Lancet Psychiatry Commission suggested that digital therapeutics could provide benefits now to complement current mental health treatments and aid self-management [<xref ref-type="bibr" rid="ref8">8</xref>]. However, evidence suggests that some apps are not only ineffective, unsafe, and hard to use, but do not meet users’ privacy and security expectations [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
          <p>Formal regulation is remarkably light and restricted to a narrow selection of health apps that provide formal diagnoses or treatment for specified medical conditions [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. Even when an app is regulated, we cannot be sure that it will work. For example, the US Food and Drug Administration (FDA) recently approved the first behavioral health app, reSET, for the treatment of substance use by using evidence from a clinical trial of a Web-based version of the treatment, not the app itself [<xref ref-type="bibr" rid="ref24">24</xref>]. In the United Kingdom, the Care Quality Commission issued guidance in 2017 for digital health care providers, but this concentrated on safety [<xref ref-type="bibr" rid="ref25">25</xref>]. The Medicines and Healthcare Products Regulatory Agency (MHRA) provides Conformité Européenne marking for medical devices and Certificates of Free Sale [<xref ref-type="bibr" rid="ref26">26</xref>] but leaves review to the National Information Board. As it stands, many health apps are marketed with few checks and even regulatory approval appears to offer little confidence on whether that specific product was ever directly evaluated.</p>
          <p>More complex regulation has been proposed. The National Institute of Health and Clinical Excellence (NICE) is curating an NHS National Health Service app library. This is a burdensome process, and so few apps will be assessed in any year. Currently, the library has 78 apps, with only 18 for the fastest developing sector, mental health. This is a minute subset of the 325,000 available [<xref ref-type="bibr" rid="ref27">27</xref>]. In the United States, the FDA launched a precertification pilot program involving 9 companies to speed the approval process, but this will evaluate the developers and their practices rather than focusing on the product [<xref ref-type="bibr" rid="ref28">28</xref>]. Apple Inc has introduced additional requirements for medical apps for developers, but these focus mainly on measurement accuracy [<xref ref-type="bibr" rid="ref29">29</xref>]. There is a middle way to fill this important, and now yawning, gap in consumer information. Health app marketplaces could take a lead by providing relatively simple guidance.</p>
        </sec>
      </sec>
      <sec>
        <title>What is Wrong With Current Systems for Reviewing Health Apps?</title>
        <p>Most proposed evaluations (eg, Mobile App Rating Scale, MARS [<xref ref-type="bibr" rid="ref30">30</xref>], Enlight assessment tools [<xref ref-type="bibr" rid="ref31">31</xref>]) assess usability, aesthetics, content, user engagement, and available research evidence, and others have been adding to this list [<xref ref-type="bibr" rid="ref32">32</xref>]. These systems are useful because they facilitate multifaceted and thorough evaluations of apps, but they fall short of allowing clear recommendations. In fact, more recent evidence from Canada involving service users demonstrated that a high MARS rating would not on its own provide enough information to allow service users to form a decision on whether to download an app [<xref ref-type="bibr" rid="ref33">33</xref>]. Advisory bodies such as NICE in the United Kingdom make a determination of what is likely to be cost-effective (effective, cost relative to benefit, and other comparison treatments), before they recommend its use in the UK NHS. Consumers, however, want to make choices based on simpler information. One for-profit company, ORCHA [<xref ref-type="bibr" rid="ref34">34</xref>], provides reviews based on <italic>current standards, regulation and good practice</italic>, but their overall score does not allow a consumer to decide which components are important to them. PsyberGuide [<xref ref-type="bibr" rid="ref35">35</xref>], a nonprofit organization, also provides reviews that include a service user focus but does not receive data directly from app developers. But apart from their lack of fulfilling all users’ expectations, no method provides clear information at the point of sale, and a potential consumer would have to search in 2 places for the information they need, to make a choice. We propose only 4 aspects of apps that represent the critical information required for responsible health app marketplaces. These 4 principles, deemed the T4T principles, are privacy and data security, development characteristics, feasibility data, and benefits.</p>
      </sec>
      <sec>
        <title>Transparency for Trust (T4T) Principles</title>
        <sec>
          <title>Privacy and Data Security</title>
          <p>Privacy and data security are a primary concern for patients and their clinicians [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref38">38</xref>], and its importance has only become more salient with recent events such as the Facebook and Cambridge Analytica scandal [<xref ref-type="bibr" rid="ref39">39</xref>-<xref ref-type="bibr" rid="ref41">41</xref>]. The European Union General Data Protection Regulation is strong and introduces new rights for people to access the information companies hold about them, obligations for better data management for businesses, and a new regime of fines across Europe. There are weaker regulations elsewhere, resulting in varying protections internationally. One review prompted the closure of the NHS app store when it was discovered that accredited apps were not encrypting data adequately and did not explicitly describe the personal data leaving the app [<xref ref-type="bibr" rid="ref42">42</xref>]. Happtique, an early app certification company, met a similar fate when several of its certified apps were hacked, demonstrating the inadequacy of its processes to evaluate privacy and data security [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. Many apps rely on selling the data they collect for their business plan, which jeopardizes personal privacy [<xref ref-type="bibr" rid="ref42">42</xref>]. There is also evidence of poor practice resulting in fines for selling sensitive information to Lottery companies and fraudsters [<xref ref-type="bibr" rid="ref45">45</xref>]. Privacy concerns change with the evolving technology, even though device operating systems are moving toward encryption on the device by default. Nevertheless, users need information about data leaving the app to make informed decisions about their willingness to provide sensitive health information [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>].</p>
          <p>Although full formal audits are needed to ensure apps follow their stated procedures [<xref ref-type="bibr" rid="ref48">48</xref>], even requiring developers to list their privacy and data security procedures in simple terms would be a significant step forward on raising standards [<xref ref-type="bibr" rid="ref49">49</xref>]. We propose 3 questions: (1) what data leave the device? (2) how are those data stored? (eg, de-identified, encrypted), and (3) who will have access to those data? It should be clear what, if any, data are being sold, to whom, and what steps are taken to ensure that users cannot be identified by those data.</p>
        </sec>
        <sec>
          <title>Development Characteristics</title>
          <p>Development characteristics describe how the app was developed, and our recommendations conceptually overlap with those of the FDA’s precertification pilot and the MHRA in the United Kingdom. Good developmental practices would involve all stakeholders (clinicians and the target audience) as well as using evidence-based guidance from the beginning and at all stages of development and testing. The absence of the use of guidance or standards has recently been noticed for physical activity and fitness apps where very few of the thousands of Android apps provided any measurement or used any of the accepted guidance [<xref ref-type="bibr" rid="ref50">50</xref>]. We especially emphasize including the target audience. This may seem obvious, but unfortunately, development practices often include clinicians and experts but more rarely involve the target audience until evaluation. Many studies rely on small numbers of participants or convenience samples, for example, soliciting feedback from stressed college students rather than individuals with depression [<xref ref-type="bibr" rid="ref51">51</xref>]. Again, this may seem obvious, but independent usability evaluations have demonstrated that many popular commercial apps are frustrating and challenging for members of the intended audience, raising questions about their prior involvement and the potential for the app to benefit this community [<xref ref-type="bibr" rid="ref52">52</xref>]. Recent evidence also suggests that good design contributes not only to usability but also engagement with health apps [<xref ref-type="bibr" rid="ref53">53</xref>], and there are several authoritative descriptions of the processes for developing good design [<xref ref-type="bibr" rid="ref54">54</xref>].</p>
          <p>Developers should outline their design and development process and clearly describe how patients were involved. Our 3 questions are as follows: (1) how were target users involved in the initial design? (2) how were target users involved in usability evaluations? and (3) has usability been independently evaluated?</p>
        </sec>
        <sec>
          <title>Feasibility</title>
          <p>Feasibility evaluations should address how people use the app (usability and user experience), how long they use it (engagement), and whether any serious adverse concerns are discovered (safety). These aspects provide information on how people use the app, including expectations on the frequency and length of use. This information is also vital to assess benefits. It would not be possible to run a drug trial or market a drug without some concept of the dosing frequency and expected therapeutic dose, and the same should be true with health apps.</p>
          <p>Again, we have 3 questions: (1) what proportion of users continue to use the app after 2 weeks? (2) what adverse events occurred and what was the rate of those events? and (3) has feasibility been independently evaluated? We propose a 2-week test not because it represents a likely therapeutic dose but because very few users persist in using a health app after the first week [<xref ref-type="bibr" rid="ref55">55</xref>]. A standard metric, such as 2 weeks, could promote cross-app comparisons in engagement. Like usability testing, independent evaluation of apps is the key to promote transparency and confidence in findings. Despite the availability of engagement analytics, few are reported even in the clinical assessments of feasibility [<xref ref-type="bibr" rid="ref56">56</xref>]. Independent evaluations could be carried out by service user groups, which could further strengthen service user involvement in the process of development and evaluation. Transparency could be further facilitated by making these datasets available to the research community.</p>
        </sec>
        <sec>
          <title>Health Benefits</title>
          <p>Health benefits are apparent from rigorous evaluations using standardized and accepted outcomes for the target condition that provides an indication of health benefits. Although many researchers have noted the mismatch between the development cycle for mobile apps and traditional randomized controlled trials [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref58">58</xref>], it is still the case that health apps presented as digital therapeutics require rigorous evaluation to back up their claims. The speed of development should not preclude such evaluations as suggested by some academics and designers [<xref ref-type="bibr" rid="ref59">59</xref>]. We should be presented with direct evidence on an app’s safety and effectiveness because they are not merely mobile versions of websites even if they have similar content. People use apps differently, including more frequently and in shorter bursts [<xref ref-type="bibr" rid="ref60">60</xref>], and these differences could affect their impact. We have already mentioned that this is happening with the FDA-approved (and first) behavioral health app, reSET, using clinical trial evidence from a Web-based version of the treatment [<xref ref-type="bibr" rid="ref32">32</xref>]. Although triangulation of different sorts of data has been suggested (eg, MindTech [<xref ref-type="bibr" rid="ref61">61</xref>]), we believe that health apps should undergo a trial to determine their superiority to other treatment options, especially as many unsubstantiated claims have been made [<xref ref-type="bibr" rid="ref36">36</xref>]. Advertising standards require evidence to support any claims made, so these data fulfill both commercial and patient needs. Evaluations should also consider opportunity cost as using a health app may delay treatments that could be more beneficial, or a delay could worsen the health condition, making it harder to treat. All these benefits and costs need to be weighed in the balance. Our 3 questions are: (1) what is the impact on the health condition? (2) what percentage of users received either no benefit or deteriorated? and (3) are there specific benefits that outweigh any costs?</p>
        </sec>
      </sec>
      <sec>
        <title>What Would This Look Like in Practice?</title>
        <p>We have inserted the information from 4 health apps, one of which was named the app of the year in the iTunes Store in 2017 (Calm) (see <xref ref-type="table" rid="table1">Table 1</xref>). We have extracted, where possible, the information on each of our principles from the information provided with the app. The differences are very clear, especially in privacy and health benefits. There could, of course, be more data available on benefits held elsewhere, but this was not available at the point of download. However, what these simple principles also provide is the ability for a consumer to trade off the attributes. Some may want to know that their data are totally secure, whereas others might want to allow some encrypted anonymized data to be transmitted if the effectiveness of the app is proven. Indeed, in a recent survey of participants recruited from a mood and anxiety disorder clinic, many respondents were willing to allow an app to collect data directly from one’s phone, including global positioning system motion sensors, and screen state [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Evaluating apps with the Transparency for Trust principles.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="210"/>
            <col width="160"/>
            <col width="200"/>
            <col width="200"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td rowspan="2" colspan="2">Transparency for Trust principle</td>
                <td colspan="4">Apps</td>
              </tr>
              <tr valign="top">
                <td>BlueIce<sup>a</sup></td>
                <td>Calm<sup>b</sup></td>
                <td>My Fitness Pal<sup>c</sup></td>
                <td>Dario Diabetes Management<sup>d</sup></td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="6"><bold>Privacy and security</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>1) What data leave the device?</td>
                <td>No information leaves the device.</td>
                <td>Device identifiers, user settings, device operating system, use of app, and location.</td>
                <td>Data related to lifestyle (eg, sleeping habits), life events, dietary restrictions, fitness goals, height, weight, measurements, fitness level, heart rate, sleep data, body mass index, biometric data, similar types of data relating to physiological condition and activity, and personal data (name, email address, postal code, date of birth, and contact number).</td>
                <td>Personal information (registration information, such as full name, gender, email address, phone number, and birth date; financial information, such as PayPal account or credit card number; voluntary information; health information, such as diabetes type; and device information) and nonpersonal information (nonidentifiable information such as software and hardware information).</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>2) How are those data stored?</td>
                <td>All data are stored on the app and owned by the user.</td>
                <td>No information.</td>
                <td>All data are stored on the company’s server</td>
                <td>All data are stored on the company’s server.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>3) Who will have access to those data?</td>
                <td>Only user of the device where BlueIce is installed has access.</td>
                <td>Third party: service providers, marketers with Calm, other systems (Google Fit of HealthKit,), industry research, etc.</td>
                <td>Partners and affiliates, service providers and vendors, and social network providers.</td>
                <td>Unspecified third parties.</td>
              </tr>
              <tr valign="top">
                <td colspan="6"><bold>Development characteristics</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>1) How were target users involved in the initial design of the app?</td>
                <td>Coproduced by Oxford Health NHS Foundation Trust and young people with lived experience.</td>
                <td>No information.</td>
                <td>User testing on various app iterations, but no additional information provided.</td>
                <td>User testing on various app iterations, but no additional information provided.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>2) How were target users involved in usability evaluations?</td>
                <td>Not provided.</td>
                <td>Not provided.</td>
                <td>User testing on various app iterations, but no additional information provided.</td>
                <td>User testing on various app iterations, but no additional information provided.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>3) Has usability been independently evaluated?</td>
                <td>No independent usability evaluations were conducted.</td>
                <td>Independently evaluated by PsyberGuide.org.</td>
                <td>No independent usability evaluations were conducted.</td>
                <td>Independently evaluated by Orcha.com; Food and Drug Administration approval.</td>
              </tr>
              <tr valign="top">
                <td colspan="6"><bold>Feasibility</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>1) What proportion of users continue to use the app after 2 weeks?</td>
                <td>93% of users kept using it.</td>
                <td>No information provided.</td>
                <td>No information provided.</td>
                <td>No information provided.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>2) What adverse events occurred in the test population and what was the rate of those events?</td>
                <td>None found (clinicians did not withdraw user and users did not feel app use increased self-harm).</td>
                <td>No information provided.</td>
                <td>No information provided.</td>
                <td>No information provided.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>3) Has feasibility been independently evaluated?</td>
                <td>No independent evaluations conducted.</td>
                <td>No independent evaluations conducted.</td>
                <td>No information provided.</td>
                <td>No information provided.</td>
              </tr>
              <tr valign="top">
                <td colspan="6"><bold>Benefits</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>1) What was the impact on clinical outcomes?</td>
                <td>Significant reductions in depression and anxiety, and 73% reduced self-harm after 12 weeks.</td>
                <td>No clinical outcomes research reported.</td>
                <td>No clinical outcomes research reported.</td>
                <td>No clinical outcomes research reported.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>2) What percentage of users received no benefit or deteriorated?</td>
                <td>27% reported no reductions in self-harm.</td>
                <td>No description provided of nonresponders or users who deteriorated.</td>
                <td>No description provided of nonresponders or users who deteriorated.</td>
                <td>No description provided of nonresponders or users who deteriorated.</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>3) Are the specific benefits worth the cost?</td>
                <td>No information provided about the expected ratio of benefits to risks.</td>
                <td>No information provided about the expected ratio of benefits to risks.</td>
                <td>No information provided about the expected ratio of benefits to risks.</td>
                <td>No information provided about the expected ratio of benefits to risks.</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>BlueIce is a prescribed evidence-based app to help young people manage their emotions and to reduce urges to self-harm [<xref ref-type="bibr" rid="ref62">62</xref>].</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>Calm was the 2017 app of the year on the Apple store and is for meditation and sleep [<xref ref-type="bibr" rid="ref63">63</xref>].</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>My Fitness Pal is for logging and motivating physical activity and diet and was the top-rated app in the journal <italic>Men’s Health</italic> in 2018 [<xref ref-type="bibr" rid="ref64">64</xref>].</p>
            </fn>
            <fn id="table1fn4">
              <p><sup>d</sup>Dario Diabetes Management monitors blood glucose history, allows carbohydrate counting, and will send messages to up to 4 people if your levels. Scored relatively highly by third-party app rater, Orcha [<xref ref-type="bibr" rid="ref65">65</xref>].</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      
      </sec>
      <sec>
        <title>Are These Principles Different From Those Suggested by Others?</title>
        <p>As we have said, T4T principles were based on those suggested by others in recent years. However, we more clearly operationalize our principles into concrete questions that could be answered and made available to potential users. To do so, we considered information important to regulators, developers, and health services, as well as integrating patient viewpoints taken from a number of different studies [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]. Patients are, after all, the consumer group of interest. Their views do not necessarily coincide with the expert groups’ views, as shown in the Delphi exercise by Zelmer et al [<xref ref-type="bibr" rid="ref33">33</xref>]. Privacy and security feature in every assessment system and in regulations and are high on the list for patients, especially those with a mental health problem who may be more sensitive about information about them being shared [<xref ref-type="bibr" rid="ref11">11</xref>]; So, it is included here, but in the simplest terms and not buried in an incomprehensible privacy statement. Our principle for a <italic>fit-for-purpose</italic> app includes development with patients. This principle is often suggested [<xref ref-type="bibr" rid="ref19">19</xref>] but rarely incorporated into app assessment. As we know that some commercial apps are complex and hard to use by the patient group they were intended for, we have valued this section highly. Effectiveness is often mentioned in many assessment systems, but the promised effects are also dependent on the dose of the app and how intensively it is used. Patients need to consider this time constraint when deciding to make a purchase. Patients also want to know not just how effective it is, but also whether anyone does not receive any benefit. This is also important to clinicians, as patients who receive no benefit may view themselves as hopeless cases and not, as in the BlueIce exemplar, just part of the quarter of patients who report no advantage from following the app.</p>
        <p>Our approach has, therefore, been to provide information to patients at the point of the download that allows them to make an informed decision, and which they can refer to later as part of their self-management plan.</p>
      </sec>
      <sec>
        <title>Responsibility in the Health App Marketplaces</title>
        <p>If these simple T4T principles are followed, then we will have gone some way toward protecting patients. Whose job is it to monitor the T4T principles? Our view is that formal regulation is not needed. We just need the information to allow patients (and patient groups) to make informed choices. Information that is not true can be picked up by advertising standards authorities. Recent examples of this process are the US Federal Trade Commission fining of Lumosity for deceiving consumers with unfounded claims about cognitive benefits [<xref ref-type="bibr" rid="ref67">67</xref>] and Carrot Neurotechnology for claiming that their app, Ultimeyes, can improve users’ vision [<xref ref-type="bibr" rid="ref68">68</xref>]. Health apps are not a passing fad, and the low barrier of entry into current app marketplaces has resulted in an environment that at best confuses and at worst delays effective treatment. The problems have been highlighted but rarely have clear solutions like ours been proposed. Developers may be encouraged to produce these answers by commercial advantages, as apps with T4T principles might increase consumer comfort and produce unique revenue streams through increased adoption, not only from direct-to-patient markets, but also from health systems. They will also enjoy increased legitimacy among patient groups.</p>
        <p>We also note that the contributions of these principles are that they are a small, yet informative, set of questions that could be adopted relatively simply. We suggest these principles as the first, but important step. Further steps could attempt to explore if these principles could be defined with more structure. However, this structure would likely require further empirical work and coordination between different stakeholders in the health app space, particularly, developers and purveyors.</p>
        <p>Confidence in the efficacy and safety of these health apps is the least that patients should expect in making a choice to buy or use them. It is now time that existing commercial app stores, specifically the Google Play and Apple iTunes stores, step back from their libertarian ideology and adopt some rules for health app marketing. They should tighten up the definition of health apps and adopt a system, ours hopefully, to allow patients to understand what to expect from a health app. Although some might believe that this proposal is <italic>other worldly</italic>, starting somewhere is important. Health app marketplaces have a duty to, and health app developers a commercial advantage, from following our suggestions – we should not need to wait for another scandal or disaster before the Google Play or Apple iTunes Stores step up to the plate and help prevent worthless products being pressed on those with health needs.</p>
    </sec>
  </body>
  <back>
    <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">MARS</term>
          <def>
            <p>Mobile App Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">MHRA</term>
          <def>
            <p>Medicines and Healthcare Products Regulatory Agency</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">NICE</term>
          <def>
            <p>National Institute of Health and Clinical Excellence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">NIHR</term>
          <def>
            <p>National Institute for Health Research</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">T4T</term>
          <def>
            <p>Transparency for Trust</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>TW acknowledges support from the National Institute for Health Research (NIHR) Maudsley Biomedical Research Centre at the South London and Maudsley NHS Foundation Trust and King’s College London and the NIHR Senior Investigator Award. SMS acknowledges the support of One Mind as well as the Implementation Research Institute at the George Washington University in St. Louis; support from the National Institute of Mental Health (5R25MH08091607) and the Department of Veterans Affairs, Health Services Research &amp; Development Service, Quality Enhancement Research Initiative. The views expressed are authors’ and not necessarily those of the NHS, the NIHR, the Department of Health, or National Institute for Mental Health .</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>TW presented the outline and together with SS wrote the initial draft. Both authors contributed to the revisions. TW is the guarantor.</p>
      </fn>
      <fn fn-type="conflict">
        <p>TW has developed a novel software intervention (CIRCuiTS) and sits on the PsyberGuide Scientific Advisory Board. She has not received any funding from companies involved in this field. SS has received funding from One Mind and serves as the Executive Director of PsyberGuide, a nonprofit funded by One Mind. SMS serves as a scientific advisor to Joyable, Inc, and Potentia Labs, Inc, and has received stock options for these contributions.</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>Wykes</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Over promised, over-sold and underperforming? - e-health in mental health</article-title>
        <source>J Ment Health</source>  
        <year>2016</year>  
        <volume>25</volume>  
        <issue>1</issue>  
        <fpage>1</fpage>  
        <lpage>4</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26732733"/>
        </comment>  
        <pub-id pub-id-type="doi">10.3109/09638237.2015.1124406</pub-id>
        <pub-id pub-id-type="medline">26732733</pub-id>
        <pub-id pub-id-type="pmcid">PMC4776695</pub-id></nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <collab>The Lancet</collab>
        </person-group>
        <article-title>Does mobile health matter?</article-title>
        <source>Lancet</source>  
        <year>2017</year>  
        <month>11</month>  
        <day>18</day>  
        <volume>390</volume>  
        <issue>10109</issue>  
        <fpage>2216</fpage>  
        <pub-id pub-id-type="doi">10.1016/S0140-6736(17)32899-4</pub-id>
        <pub-id pub-id-type="medline">29165258</pub-id>
        <pub-id pub-id-type="pii">S0140-6736(17)32899-4</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>Duggal</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Brindle</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Bagenal</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Digital healthcare: regulating the revolution</article-title>
        <source>Br Med J</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>15</day>  
        <volume>360</volume>  
        <fpage>k6</fpage>  
        <pub-id pub-id-type="doi">10.1136/bmj.k6</pub-id>
        <pub-id pub-id-type="medline">29335296</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>Krebs</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Duncan</surname>
            <given-names>DT</given-names>
          </name>
        </person-group>
        <article-title>Health app use among US mobile phone owners: a national survey</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2015</year>  
        <month>11</month>  
        <day>4</day>  
        <volume>3</volume>  
        <issue>4</issue>  
        <fpage>e101</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2015/4/e101/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.4924</pub-id>
        <pub-id pub-id-type="medline">26537656</pub-id>
        <pub-id pub-id-type="pii">v3i4e101</pub-id>
        <pub-id pub-id-type="pmcid">PMC4704953</pub-id></nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>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>12</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="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <collab>-</collab>
        </person-group>
        <article-title>Is digital medicine different?</article-title>
        <source>Lancet</source>  
        <year>2018</year>  
        <volume>392</volume>  
        <issue>10142</issue>  
        <fpage>95</fpage>  
        <pub-id pub-id-type="doi">10.1016/S0140-6736(18)31562-9</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
        <source>Research2Guidance</source>  
        <year>2017</year>  
        <access-date>2019-03-08</access-date>
        <comment>325,000 mobile health apps available in 2017 - Android now the leading mHealth platform
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://research2guidance.com/325000-mobile-health-apps-available-in-2017/">https://research2guidance.com/325000-mobile-health-apps-available-in-2017/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ie8Xisj"/></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>Holmes</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Ghaderi</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Harmer</surname>
            <given-names>CJ</given-names>
          </name>
          <name name-style="western">
            <surname>Ramchandani</surname>
            <given-names>PG</given-names>
          </name>
          <name name-style="western">
            <surname>Cuijpers</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Morrison</surname>
            <given-names>AP</given-names>
          </name>
          <name name-style="western">
            <surname>Roiser</surname>
            <given-names>JP</given-names>
          </name>
          <name name-style="western">
            <surname>Bockting</surname>
            <given-names>CL</given-names>
          </name>
          <name name-style="western">
            <surname>O'Connor</surname>
            <given-names>RC</given-names>
          </name>
          <name name-style="western">
            <surname>Shafran</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Moulds</surname>
            <given-names>ML</given-names>
          </name>
          <name name-style="western">
            <surname>Craske</surname>
            <given-names>MG</given-names>
          </name>
        </person-group>
        <article-title>The Lancet Psychiatry Commission on psychological treatments research in tomorrow's science</article-title>
        <source>Lancet Psychiatry</source>  
        <year>2018</year>  
        <month>03</month>  
        <volume>5</volume>  
        <issue>3</issue>  
        <fpage>237</fpage>  
        <lpage>86</lpage>  
        <pub-id pub-id-type="doi">10.1016/S2215-0366(17)30513-8</pub-id>
        <pub-id pub-id-type="medline">29482764</pub-id>
        <pub-id pub-id-type="pii">S2215-0366(17)30513-8</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>S. Bhuyan</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Isehunwa</surname>
            <given-names>OO</given-names>
          </name>
          <name name-style="western">
            <surname>Kumar</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Bhatt</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Wyant</surname>
            <given-names>DK</given-names>
          </name>
          <name name-style="western">
            <surname>Kedia</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Chang</surname>
            <given-names>CF</given-names>
          </name>
          <name name-style="western">
            <surname>Dasgupta</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Privacy and security issues in mobile health: current research and future directions</article-title>
        <source>Health Policy Technol</source>  
        <year>2017</year>  
        <month>06</month>  
        <volume>6</volume>  
        <issue>2</issue>  
        <fpage>188</fpage>  
        <lpage>91</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.hlpt.2017.01.004</pub-id>
        <pub-id pub-id-type="pii">S2215-0366(17)30513-8</pub-id></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
        <source>Academy of Medical Sciences</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>14</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>Academy of Medical Sciences</publisher-name>
        <comment>Our data-driven future in healthcare: People and partnerships at the heart of health related technologies
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://acmedsciacuk/file-download/74634438">https://acmedsciacuk/file-download/74634438</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ieMWDMu"/></comment> </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Castell</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Ashford</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <source>Academy of Medical Sciences</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>14</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>Academy of Medical Sciences</publisher-name>
        <comment>Future data-driven technologies and the implications for use of patient data: Dialogue with public, patients and healthcare professionals
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://acmedsci.ac.uk/file-download/6616969">https://acmedsci.ac.uk/file-download/6616969</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ieZeeju"/></comment> </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>Hollis</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Sampson</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Simons</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Davies</surname>
            <given-names>EB</given-names>
          </name>
          <name name-style="western">
            <surname>Churchill</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Betton</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Butler</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Chapman</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Easton</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Gronlund</surname>
            <given-names>TA</given-names>
          </name>
          <name name-style="western">
            <surname>Kabir</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Rawsthorne</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Rye</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Tomlin</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Identifying research priorities for digital technology in mental health care: results of the James Lind Alliance Priority Setting Partnership</article-title>
        <source>Lancet Psychiatry</source>  
        <year>2018</year>  
        <month>10</month>  
        <volume>5</volume>  
        <issue>10</issue>  
        <fpage>845</fpage>  
        <lpage>54</lpage>  
        <pub-id pub-id-type="doi">10.1016/S2215-0366(18)30296-7</pub-id>
        <pub-id pub-id-type="medline">30170964</pub-id>
        <pub-id pub-id-type="pii">S2215-0366(18)30296-7</pub-id></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
        <source>Federal Trade Commission</source>  
        <year>2016</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Washington</publisher-loc>
        <publisher-name>Federal Trade Commission</publisher-name>
        <comment>Interactive Mobile Health Apps Tool: Developing a mobile health app?
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ftc.gov/tips-advice/business-center/guidance/mobile-health-apps-interactive-tool">https://www.ftc.gov/tips-advice/business-center/guidance/mobile-health-apps-interactive-tool</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iekNRA0"/></comment> </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>Simblett</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Greer</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Matcham</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Curtis</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Polhemus</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ferrão</surname>
            <given-names>José</given-names>
          </name>
          <name name-style="western">
            <surname>Gamble</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Barriers to and facilitators of engagement with remote measurement technology for managing health: systematic review and content analysis of findings</article-title>
        <source>J Med Internet Res</source>  
        <year>2018</year>  
        <month>07</month>  
        <day>12</day>  
        <volume>20</volume>  
        <issue>7</issue>  
        <fpage>e10480</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/7/e10480/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10480</pub-id>
        <pub-id pub-id-type="medline">30001997</pub-id>
        <pub-id pub-id-type="pii">v20i7e10480</pub-id>
        <pub-id pub-id-type="pmcid">PMC6062692</pub-id></nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
        <source>British Standards Institution</source>  
        <year>2015</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>Innovate UK</publisher-name>
        <comment>Health and wellness apps: Quality criteria across the life cycle - Code of practice
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://shop.bsigroup.com/upload/271432/PAS%20277%20(2015)bookmarked.pdf">https://shop.bsigroup.com/upload/271432/PAS%20277%20(2015)bookmarked.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ieq1A8B"/></comment> </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Naylor</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Knapp</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>McDaid</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <source>The Kings Fund</source>  
        <year>2012</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <comment>Long-term conditions and mental health: The cost of co-morbidities
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.kingsfund.org.uk/publications/long-term-conditions-and-mental-health">https://www.kingsfund.org.uk/publications/long-term-conditions-and-mental-health</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76if3LYCM"/></comment> </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>Zuidersma</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ormel</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Conradi</surname>
            <given-names>HJ</given-names>
          </name>
          <name name-style="western">
            <surname>de Jonge</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>An increase in depressive symptoms after myocardial infarction predicts new cardiac events irrespective of depressive symptoms before myocardial infarction</article-title>
        <source>Psychol Med</source>  
        <year>2012</year>  
        <month>04</month>  
        <volume>42</volume>  
        <issue>4</issue>  
        <fpage>683</fpage>  
        <lpage>93</lpage>  
        <pub-id pub-id-type="doi">10.1017/S0033291711001784</pub-id>
        <pub-id pub-id-type="medline">22571951</pub-id>
        <pub-id pub-id-type="pii">S0033291711001784</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>Ismail</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Winkley</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Stahl</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Chalder</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Edmonds</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>A cohort study of people with diabetes and their first foot ulcer: the role of depression on mortality</article-title>
        <source>Diabetes Care</source>  
        <year>2007</year>  
        <month>06</month>  
        <volume>30</volume>  
        <issue>6</issue>  
        <fpage>1473</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.2337/dc06-2313</pub-id>
        <pub-id pub-id-type="medline">17363754</pub-id>
        <pub-id pub-id-type="pii">dc06-2313</pub-id></nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bhugra</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Tasman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Pathare</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Priebe</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Torous</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Arbuckle</surname>
            <given-names>MR</given-names>
          </name>
          <name name-style="western">
            <surname>Langford</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Alarcón</surname>
            <given-names>RD</given-names>
          </name>
          <name name-style="western">
            <surname>Chiu</surname>
            <given-names>HF</given-names>
          </name>
          <name name-style="western">
            <surname>First</surname>
            <given-names>MB</given-names>
          </name>
          <name name-style="western">
            <surname>Kay</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Sunkel</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Thapar</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Udomratn</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Baingana</surname>
            <given-names>FK</given-names>
          </name>
          <name name-style="western">
            <surname>Kestel</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Ng</surname>
            <given-names>RM</given-names>
          </name>
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Picker</surname>
            <given-names>LD</given-names>
          </name>
          <name name-style="western">
            <surname>McKenzie</surname>
            <given-names>KJ</given-names>
          </name>
          <name name-style="western">
            <surname>Moussaoui</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Muijen</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Bartlett</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Davison</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Exworthy</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Loza</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Torales</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Christensen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Firth</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Keshavan</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Onnela</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Elkholy</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Kalra</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Lovett</surname>
            <given-names>KF</given-names>
          </name>
          <name name-style="western">
            <surname>Travis</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Ventriglio</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>The WPA-Lancet Psychiatry Commission on the future of psychiatry</article-title>
        <source>Lancet Psychiatry</source>  
        <year>2017</year>  
        <month>10</month>  
        <volume>4</volume>  
        <issue>10</issue>  
        <fpage>775</fpage>  
        <lpage>818</lpage>  
        <pub-id pub-id-type="doi">10.1016/S2215-0366(17)30333-4</pub-id>
        <pub-id pub-id-type="medline">28946952</pub-id>
        <pub-id pub-id-type="pii">S2215-0366(17)30333-4</pub-id></nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nicholas</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Larsen</surname>
            <given-names>ME</given-names>
          </name>
          <name name-style="western">
            <surname>Proudfoot</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Christensen</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Mobile apps for bipolar disorder: a systematic review of features and content quality</article-title>
        <source>J Med Internet Res</source>  
        <year>2015</year>  
        <month>08</month>  
        <day>17</day>  
        <volume>17</volume>  
        <issue>8</issue>  
        <fpage>e198</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2015/8/e198/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/jmir.4581</pub-id>
        <pub-id pub-id-type="medline">26283290</pub-id>
        <pub-id pub-id-type="pii">v17i8e198</pub-id>
        <pub-id pub-id-type="pmcid">PMC4642376</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>Larsen</surname>
            <given-names>ME</given-names>
          </name>
          <name name-style="western">
            <surname>Nicholas</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Christensen</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>A systematic assessment of smartphone tools for suicide prevention</article-title>
        <source>PLoS One</source>  
        <year>2016</year>  
        <volume>11</volume>  
        <issue>4</issue>  
        <fpage>e0152285</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0152285"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1371/journal.pone.0152285</pub-id>
        <pub-id pub-id-type="medline">27073900</pub-id>
        <pub-id pub-id-type="pii">PONE-D-15-46158</pub-id>
        <pub-id pub-id-type="pmcid">PMC4830444</pub-id></nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
        <source>Food and Drug Administration</source>  
        <year>2015</year>  
        <month>02</month>  
        <day>9</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Washington</publisher-loc>
        <publisher-name>Food and Drug Administration</publisher-name>
        <comment>Mobile Medical Applications: Guidance for industry and food and drug administration staff
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM263366.pdf">https://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM263366.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ijZkMNC"/></comment> </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
        <source>Food and Drug Administration</source>  
        <year>2016</year>  
        <month>07</month>  
        <day>16</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Washington</publisher-loc>
        <publisher-name>Food and Drug Administration</publisher-name>
        <comment>Mobile medical applications
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ftc.gov/tips-advice/business-center/guidance/mobile-health-apps-interactive-tool">https://www.ftc.gov/tips-advice/business-center/guidance/mobile-health-apps-interactive-tool</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iiqocVS"/></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>Campbell</surname>
            <given-names>AN</given-names>
          </name>
          <name name-style="western">
            <surname>Nunes</surname>
            <given-names>EV</given-names>
          </name>
          <name name-style="western">
            <surname>Matthews</surname>
            <given-names>AG</given-names>
          </name>
          <name name-style="western">
            <surname>Stitzer</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Miele</surname>
            <given-names>GM</given-names>
          </name>
          <name name-style="western">
            <surname>Polsky</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Turrigiano</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Walters</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>McClure</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Kyle</surname>
            <given-names>TL</given-names>
          </name>
          <name name-style="western">
            <surname>Wahle</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Van</surname>
            <given-names>VP</given-names>
          </name>
          <name name-style="western">
            <surname>Goldman</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Babcock</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Stabile</surname>
            <given-names>PQ</given-names>
          </name>
          <name name-style="western">
            <surname>Winhusen</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Ghitza</surname>
            <given-names>UE</given-names>
          </name>
        </person-group>
        <article-title>Internet-delivered treatment for substance abuse: a multisite randomized controlled trial</article-title>
        <source>Am J Psychiatry</source>  
        <year>2014</year>  
        <month>06</month>  
        <volume>171</volume>  
        <issue>6</issue>  
        <fpage>683</fpage>  
        <lpage>90</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24700332"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1176/appi.ajp.2014.13081055</pub-id>
        <pub-id pub-id-type="medline">24700332</pub-id>
        <pub-id pub-id-type="pii">1859474</pub-id>
        <pub-id pub-id-type="pmcid">PMC4079279</pub-id></nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
        <source>Care Quality Commission</source>  
        <year>2017</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>Care Quality Commission</publisher-name>
        <comment>Clarification of regulatory methodology: PMS digital healthcare providers
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cqc.org.uk/file/1295582">https://www.cqc.org.uk/file/1295582</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iizMZ0G"/></comment> </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
        <source>Department for Business EIS</source>  
        <year>2012</year>  
        <month>10</month>  
        <day>08</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>Department for Business EIS</publisher-name>
        <comment>CE Marking: How a product complies with EU safety, health and environmental requirements, and how to place a CE marking on your product
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/guidance/ce-marking">https://www.gov.uk/guidance/ce-marking</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ijmm6yp"/></comment> </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
        <source>National Health Service</source>  
        <year>2018</year>  
        <month>08</month>  
        <day>25</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>National Health Service</publisher-name>
        <comment>NHS Apps Library: Find digital tools to help you manage and improve your health
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nhs.uk/apps-library/">https://www.nhs.uk/apps-library/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iqYsPsw"/></comment> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
        <source>Food and Drug Administration</source>  
        <year>2019</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Washington</publisher-loc>
        <publisher-name>Food and Drug Administration</publisher-name>
        <comment>Digital Health Software Precertification (Pre-Cert) Program
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/MedicalDevices/DigitalHealth/DigitalHealthPreCertProgram/default.htm">https://www.fda.gov/MedicalDevices/DigitalHealth/DigitalHealthPreCertProgram/default.htm</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ik9N0Gb"/></comment> </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
        <source>Apple Inc</source>  
        <year>2019</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>California</publisher-loc>
        <publisher-name>Apple</publisher-name>
        <comment>App Store Review Guidelines
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" 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>
        <ext-link ext-link-type="webcite" xlink:href="76ikKLv3J"/></comment> </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>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 xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://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="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Baumel</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Faber</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Mathur</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Kane</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Muench</surname>
            <given-names>F</given-names>
          </name>
        </person-group>
        <article-title>Enlight: a comprehensive quality and therapeutic potential evaluation tool for mobile and web-based eHealth interventions</article-title>
        <source>J Med Internet Res</source>  
        <year>2017</year>  
        <month>12</month>  
        <day>21</day>  
        <volume>19</volume>  
        <issue>3</issue>  
        <fpage>e82</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/3/e82/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/jmir.7270</pub-id>
        <pub-id pub-id-type="medline">28325712</pub-id>
        <pub-id pub-id-type="pii">v19i3e82</pub-id>
        <pub-id pub-id-type="pmcid">PMC5380814</pub-id></nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Drake</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Csipke</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Assessing your mood online: acceptability and use of Moodscope</article-title>
        <source>Psychol Med</source>  
        <year>2013</year>  
        <month>07</month>  
        <volume>43</volume>  
        <issue>7</issue>  
        <fpage>1455</fpage>  
        <lpage>64</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://journals.cambridge.org/abstract_S0033291712002280"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1017/S0033291712002280</pub-id>
        <pub-id pub-id-type="medline">23149120</pub-id>
        <pub-id pub-id-type="pii">S0033291712002280</pub-id>
        <pub-id pub-id-type="pmcid">PMC3683895</pub-id></nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zelmer</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>van Hoof</surname>
            <given-names>Krystle</given-names>
          </name>
          <name name-style="western">
            <surname>Notarianni</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>van Mierlo</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Schellenberg</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Tannenbaum</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>An assessment framework for e-mental health apps in Canada: results of a modified Delphi process</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2018</year>  
        <month>07</month>  
        <day>9</day>  
        <volume>6</volume>  
        <issue>7</issue>  
        <fpage>e10016</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/7/e10016/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10016</pub-id>
        <pub-id pub-id-type="medline">29986846</pub-id>
        <pub-id pub-id-type="pii">v6i7e10016</pub-id>
        <pub-id pub-id-type="pmcid">PMC6056739</pub-id></nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
        <source>Orcha</source>  
        <year>2018</year>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Daresbury</publisher-loc>
        <comment>Orcha: Unlocking the power of Digital Health for the population
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.orcha.co.uk/">https://www.orcha.co.uk/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ikWtXEV"/></comment> </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
        <source>Psyberguide</source>  
        <access-date>2019-03-08</access-date>
        <comment>Looking for a mental health app?
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://psyberguide.org/">https://psyberguide.org/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ikZu58I"/></comment> </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Simons</surname>
            <given-names>DJ</given-names>
          </name>
          <name name-style="western">
            <surname>Boot</surname>
            <given-names>WR</given-names>
          </name>
          <name name-style="western">
            <surname>Charness</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Gathercole</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Chabris</surname>
            <given-names>CF</given-names>
          </name>
          <name name-style="western">
            <surname>Hambrick</surname>
            <given-names>DZ</given-names>
          </name>
          <name name-style="western">
            <surname>Stine-Morrow</surname>
            <given-names>EA</given-names>
          </name>
        </person-group>
        <article-title>Do “Brain-Training” Programs Work? Psychological Science in the Public Interest</article-title>
        <source>Psychol Sci Public Interest</source>  
        <year>2016</year>  
        <month>10</month>  
        <volume>17</volume>  
        <issue>3</issue>  
        <fpage>103</fpage>  
        <lpage>86</lpage>  
        <pub-id pub-id-type="doi">10.1177/1529100616661983</pub-id>
        <pub-id pub-id-type="medline">27697851</pub-id>
        <pub-id pub-id-type="pii">17/3/103</pub-id></nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Di Matteo</surname>
            <given-names>Daniel</given-names>
          </name>
          <name name-style="western">
            <surname>Fine</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Fotinos</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Katzman</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Patient willingness to consent to mobile phone data collection for mental health apps: structured questionnaire</article-title>
        <source>JMIR Ment Health</source>  
        <year>2018</year>  
        <month>08</month>  
        <day>29</day>  
        <volume>5</volume>  
        <issue>3</issue>  
        <fpage>e56</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mental.jmir.org/2018/3/e56/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mental.9539</pub-id>
        <pub-id pub-id-type="medline">30158102</pub-id>
        <pub-id pub-id-type="pii">v5i3e56</pub-id>
        <pub-id pub-id-type="pmcid">PMC6135964</pub-id></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hendrikoff</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Kambeitz-Ilankovic</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Pryss</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Senner</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Falkai</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Pogarell</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Hasan</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Peters</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Prospective acceptance of distinct mobile mental health features in psychiatric patients and mental health professionals</article-title>
        <source>J Psychiatr Res</source>  
        <year>2019</year>  
        <month>02</month>  
        <volume>109</volume>  
        <fpage>126</fpage>  
        <lpage>32</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jpsychires.2018.11.025</pub-id>
        <pub-id pub-id-type="medline">30530207</pub-id>
        <pub-id pub-id-type="pii">S0022-3956(18)31248-2</pub-id></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
        <source>BBC</source>  
        <year>2019</year>  
        <month>02</month>  
        <day>18</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>BBC</publisher-name>
        <comment>Facebook-Cambridge Analytica data breach
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bbc.co.uk/news/topics/c81zyn0888lt/facebook-cambridge-analytica-data-breach">https://www.bbc.co.uk/news/topics/c81zyn0888lt/facebook-cambridge-analytica-data-breach</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ikha6n0"/></comment> </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Meyer</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <source>The Atlantic</source>  
        <year>2018</year>  
        <month>03</month>  
        <day>20</day>  
        <access-date>2019-03-08</access-date>
        <publisher-loc>Washington</publisher-loc>
        <publisher-name>The Atlantic</publisher-name>
        <comment>The Cambridge Analytica Scandal, in Three Paragraphs. What it means for Facebook, for President Trump's world, and for every American
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.theatlantic.com/technology/archive/2018/03/the-cambridge-analytica-scandal-in-three-paragraphs/556046/">https://www.theatlantic.com/technology/archive/2018/03/the-cambridge-analytica-scandal-in-three-paragraphs/556046/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76il0cwkf"/></comment> </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
        <source>Wikipedia</source>  
        <year>2019</year>  
        <month>02</month>  
        <day>21</day>  
        <access-date>2019-03-08</access-date>
        <comment>Facebook - Cambridge Analytica data scandal
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://en.wikipedia.org/wiki/Facebook%E2%80%93Cambridge_Analytica_data_scandal">https://en.wikipedia.org/wiki/Facebook%E2%80%93Cambridge_Analytica_data_scandal</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76imTDBQs"/></comment> </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</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>Prieto</surname>
            <given-names>JT</given-names>
          </name>
          <name name-style="western">
            <surname>Tilney</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Benghozi</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Car</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Unaddressed privacy risks in accredited health and wellness apps: a cross-sectional systematic assessment</article-title>
        <source>BMC Med</source>  
        <year>2015</year>  
        <month>09</month>  
        <day>7</day>  
        <volume>13</volume>  
        <fpage>214</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-015-0444-y"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12916-015-0444-y</pub-id>
        <pub-id pub-id-type="medline">26404673</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12916-015-0444-y</pub-id>
        <pub-id pub-id-type="pmcid">PMC4582624</pub-id></nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Dan</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <source>HIStalk</source>  
        <year>2014</year>  
        <month>12</month>  
        <day>10</day>  
        <access-date>2019-03-08</access-date>
        <comment>The Rise and Fall of Happtique, mHealth?s First App Prescribing Platform
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://histalkmobile.com/the-rise-and-fall-of-happtique-mhealths-first-app-prescribing-platform/">http://histalkmobile.com/the-rise-and-fall-of-happtique-mhealths-first-app-prescribing-platform/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76imeNGg9"/></comment> </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Dolan</surname>
            <given-names>B</given-names>
          </name>
        </person-group>
        <source>Mobi Health News</source>  
        <year>2014</year>  
        <month>12</month>  
        <day>10</day>  
        <access-date>2019-03-08</access-date>
        <comment>SocialWellth acquires health app certification company Happtique
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mobihealthnews.com/38894/socialwellth-acquires-health-app-certification-company-happtique">https://www.mobihealthnews.com/38894/socialwellth-acquires-health-app-certification-company-happtique</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76immiaT0"/></comment> </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
        <source>Pharmacy 2U</source>  
        <year>2015</year>  
        <month>10</month>  
        <day>20</day>  
        <access-date>2019-03-08</access-date>
        <comment>Statement from Pharmacy2U
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pharmacy2u.co.uk/news/statement-oct15/">https://www.pharmacy2u.co.uk/news/statement-oct15/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76inNzqKD"/></comment> </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ennis</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Robotham</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Denis</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Pandit</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Newton</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Collaborative development of an electronic Personal Health Record for people with severe and enduring mental health problems</article-title>
        <source>BMC Psychiatry</source>  
        <year>2014</year>  
        <month>11</month>  
        <day>18</day>  
        <volume>14</volume>  
        <fpage>305</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpsychiatry.biomedcentral.com/articles/10.1186/s12888-014-0305-9"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12888-014-0305-9</pub-id>
        <pub-id pub-id-type="medline">25403285</pub-id>
        <pub-id pub-id-type="pii">s12888-014-0305-9</pub-id>
        <pub-id pub-id-type="pmcid">PMC4245793</pub-id></nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Robotham</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Mayhew</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Wykes</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Electronic personal health records for people with severe mental illness; a feasibility study</article-title>
        <source>BMC Psychiatry</source>  
        <year>2015</year>  
        <month>08</month>  
        <day>6</day>  
        <volume>15</volume>  
        <fpage>192</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpsychiatry.biomedcentral.com/articles/10.1186/s12888-015-0558-y"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12888-015-0558-y</pub-id>
        <pub-id pub-id-type="medline">26245805</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12888-015-0558-y</pub-id>
        <pub-id pub-id-type="pmcid">PMC4527241</pub-id></nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Papageorgiou</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Strigkos</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Politou</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Alepis</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Solanas</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Patsakis</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Security and privacy analysis of mobile health applications: the alarming state of practice</article-title>
        <source>IEEE Access</source>  
        <year>2018</year>  
        <month>03</month>  
        <volume>6</volume>  
        <fpage>9390</fpage>  
        <lpage>403</lpage>  
        <pub-id pub-id-type="doi">10.1109/ACCESS.2018.2799522</pub-id></nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rosenfeld</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Torous</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Vahia</surname>
            <given-names>IV</given-names>
          </name>
        </person-group>
        <article-title>Data security and privacy in apps for dementia: an analysis of existing privacy policies</article-title>
        <source>Am J Geriatr Psychiatry</source>  
        <year>2017</year>  
        <month>08</month>  
        <volume>25</volume>  
        <issue>8</issue>  
        <fpage>873</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jagp.2017.04.009</pub-id>
        <pub-id pub-id-type="medline">28645535</pub-id>
        <pub-id pub-id-type="pii">S1064-7481(17)30301-9</pub-id></nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kebede</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Steenbock</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Helmer</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Sill</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Möllers</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Pischke</surname>
            <given-names>CR</given-names>
          </name>
        </person-group>
        <article-title>Identifying evidence-informed physical activity apps: content analysis</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>18</day>  
        <volume>6</volume>  
        <issue>12</issue>  
        <fpage>e10314</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/12/e10314/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10314</pub-id>
        <pub-id pub-id-type="medline">30563810</pub-id>
        <pub-id pub-id-type="pii">v6i12e10314</pub-id>
        <pub-id pub-id-type="pmcid">PMC6315275</pub-id></nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Fitzpatrick</surname>
            <given-names>KK</given-names>
          </name>
          <name name-style="western">
            <surname>Darcy</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Vierhile</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Delivering cognitive behavior therapy to young adults with symptoms of depression and anxiety using a fully automated conversational agent (Woebot): a randomized controlled trial</article-title>
        <source>JMIR Ment Health</source>  
        <year>2017</year>  
        <month>06</month>  
        <day>6</day>  
        <volume>4</volume>  
        <issue>2</issue>  
        <fpage>e19</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mental.jmir.org/2017/2/e19/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mental.7785</pub-id>
        <pub-id pub-id-type="medline">28588005</pub-id>
        <pub-id pub-id-type="pii">v4i2e19</pub-id>
        <pub-id pub-id-type="pmcid">PMC5478797</pub-id></nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Sarkar</surname>
            <given-names>U</given-names>
          </name>
          <name name-style="western">
            <surname>Gourley</surname>
            <given-names>GI</given-names>
          </name>
          <name name-style="western">
            <surname>Lyles</surname>
            <given-names>CR</given-names>
          </name>
          <name name-style="western">
            <surname>Tieu</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Clarity</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Newmark</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Bates</surname>
            <given-names>DW</given-names>
          </name>
        </person-group>
        <article-title>Usability of commercially available mobile applications for diverse patients</article-title>
        <source>J Gen Intern Med</source>  
        <year>2016</year>  
        <month>12</month>  
        <volume>31</volume>  
        <issue>12</issue>  
        <fpage>1417</fpage>  
        <lpage>26</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27418347"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s11606-016-3771-6</pub-id>
        <pub-id pub-id-type="medline">27418347</pub-id>
        <pub-id pub-id-type="pii">10.1007/s11606-016-3771-6</pub-id>
        <pub-id pub-id-type="pmcid">PMC5130945</pub-id></nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Baumel</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Kane</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Examining predictors of real-world user engagement with self-guided eHealth interventions: analysis of mobile apps and websites using a novel dataset</article-title>
        <source>J Med Internet Res</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>14</day>  
        <volume>20</volume>  
        <issue>12</issue>  
        <fpage>e11491</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/12/e11491/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/11491</pub-id>
        <pub-id pub-id-type="medline">30552077</pub-id>
        <pub-id pub-id-type="pii">v20i12e11491</pub-id>
        <pub-id pub-id-type="pmcid">PMC6315225</pub-id></nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Edwards</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Caton</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Lumsden</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Rivas</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Steed</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Pirunsarn</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Jumbe</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Newby</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Shenvi</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Mazumdar</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>JQ</given-names>
          </name>
          <name name-style="western">
            <surname>Greenhill</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Griffiths</surname>
            <given-names>CJ</given-names>
          </name>
          <name name-style="western">
            <surname>Walton</surname>
            <given-names>RT</given-names>
          </name>
        </person-group>
        <article-title>Creating a theoretically-grounded, gamified health app: lessons from developing the Cigbreak smoking cessation mobile phone game</article-title>
        <source>JMIR Serious Games</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>29</day>  
        <volume>6</volume>  
        <issue>4</issue>  
        <fpage>e10252</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://games.jmir.org/2018/4/e10252/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10252</pub-id>
        <pub-id pub-id-type="medline">30497994</pub-id>
        <pub-id pub-id-type="pii">v6i4e10252</pub-id>
        <pub-id pub-id-type="pmcid">PMC6293248</pub-id></nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Owen</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Jaworski</surname>
            <given-names>BK</given-names>
          </name>
          <name name-style="western">
            <surname>Kuhn</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Makin-Byrd</surname>
            <given-names>KN</given-names>
          </name>
          <name name-style="western">
            <surname>Ramsey</surname>
            <given-names>KM</given-names>
          </name>
          <name name-style="western">
            <surname>Hoffman</surname>
            <given-names>JE</given-names>
          </name>
        </person-group>
        <article-title>mHealth in the wild: using novel data to examine the reach, use, and impact of PTSD coach</article-title>
        <source>JMIR Ment Health</source>  
        <year>2015</year>  
        <volume>2</volume>  
        <issue>1</issue>  
        <fpage>e7</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mental.jmir.org/2015/1/e7/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mental.3935</pub-id>
        <pub-id pub-id-type="medline">26543913</pub-id>
        <pub-id pub-id-type="pii">v2i1e7</pub-id>
        <pub-id pub-id-type="pmcid">PMC4607374</pub-id></nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Pham</surname>
            <given-names>Q</given-names>
          </name>
          <name name-style="western">
            <surname>Graham</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Carrion</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Morita</surname>
            <given-names>PP</given-names>
          </name>
          <name name-style="western">
            <surname>Seto</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Stinson</surname>
            <given-names>JN</given-names>
          </name>
          <name name-style="western">
            <surname>Cafazzo</surname>
            <given-names>JA</given-names>
          </name>
        </person-group>
        <article-title>A library of analytic indicators to evaluate effective engagement with consumer mHealth apps for chronic conditions: scoping review</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2019</year>  
        <month>01</month>  
        <day>18</day>  
        <volume>7</volume>  
        <issue>1</issue>  
        <fpage>e11941</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2019/1/e11941/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/11941</pub-id>
        <pub-id pub-id-type="medline">30664463</pub-id>
        <pub-id pub-id-type="pii">v7i1e11941</pub-id>
        <pub-id pub-id-type="pmcid">PMC6356188</pub-id></nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mohr</surname>
            <given-names>DC</given-names>
          </name>
          <name name-style="western">
            <surname>Cheung</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Schueller</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Hendricks Brown</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Duan</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>Continuous evaluation of evolving behavioral intervention technologies</article-title>
        <source>Am J Prev Med</source>  
        <year>2013</year>  
        <month>10</month>  
        <volume>45</volume>  
        <issue>4</issue>  
        <fpage>517</fpage>  
        <lpage>23</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24050429"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.amepre.2013.06.006</pub-id>
        <pub-id pub-id-type="medline">24050429</pub-id>
        <pub-id pub-id-type="pii">S0749-3797(13)00387-5</pub-id>
        <pub-id pub-id-type="pmcid">PMC3828034</pub-id></nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kumar</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Nilsen</surname>
            <given-names>WJ</given-names>
          </name>
          <name name-style="western">
            <surname>Abernethy</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Atienza</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Patrick</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Pavel</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Riley</surname>
            <given-names>WT</given-names>
          </name>
          <name name-style="western">
            <surname>Shar</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Spring</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Spruijt-Metz</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Hedeker</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Honavar</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Kravitz</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Lefebvre</surname>
            <given-names>RC</given-names>
          </name>
          <name name-style="western">
            <surname>Mohr</surname>
            <given-names>DC</given-names>
          </name>
          <name name-style="western">
            <surname>Murphy</surname>
            <given-names>SA</given-names>
          </name>
          <name name-style="western">
            <surname>Quinn</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Shusterman</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Swendeman</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Mobile health technology evaluation: the mHealth evidence workshop</article-title>
        <source>Am J Prev Med</source>  
        <year>2013</year>  
        <month>08</month>  
        <volume>45</volume>  
        <issue>2</issue>  
        <fpage>228</fpage>  
        <lpage>36</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23867031"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.amepre.2013.03.017</pub-id>
        <pub-id pub-id-type="medline">23867031</pub-id>
        <pub-id pub-id-type="pii">S0749-3797(13)00277-8</pub-id>
        <pub-id pub-id-type="pmcid">PMC3803146</pub-id></nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hollis</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Morriss</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Martin</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Amani</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Cotton</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Denis</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Lewis</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Technological innovations in mental healthcare: harnessing the digital revolution</article-title>
        <source>Br J Psychiatry</source>  
        <year>2015</year>  
        <month>04</month>  
        <volume>206</volume>  
        <issue>4</issue>  
        <fpage>263</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="doi">10.1192/bjp.bp.113.142612</pub-id>
        <pub-id pub-id-type="medline">25833865</pub-id>
        <pub-id pub-id-type="pii">S0007125000278677</pub-id></nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Oulasvirta</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Tamminen</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Roto</surname>
            <given-names>VJK</given-names>
          </name>
        </person-group>
        <article-title>Interaction in 4-second Bursts: The Fragmented Nature of Attentional Resources in Mobile HCI</article-title>
        <source>Proceedings of the SIGCHI conference on Human factors in computing systems</source>  
        <year>2005</year>  
        <conf-name>CHI'05</conf-name>
        <conf-date>April 2-7, 2005</conf-date>
        <conf-loc>Portland, Oregon</conf-loc>
        <publisher-loc>SIGCHI Conference on Human Factors in Computing Systems; Portland, Oregon, USA</publisher-loc>
        <publisher-name>ACM</publisher-name>
        <fpage>919</fpage>  
        <lpage>28</lpage>  
        <pub-id pub-id-type="doi">10.1145/1054972.1055101</pub-id></nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Davies</surname>
            <given-names>EB</given-names>
          </name>
          <name name-style="western">
            <surname>Craven</surname>
            <given-names>MP</given-names>
          </name>
          <name name-style="western">
            <surname>Martin</surname>
            <given-names>JL</given-names>
          </name>
          <name name-style="western">
            <surname>Simons</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Proportionate methods for evaluating a simple digital mental health tool</article-title>
        <source>Evid Based Ment Health</source>  
        <year>2017</year>  
        <month>11</month>  
        <volume>20</volume>  
        <issue>4</issue>  
        <fpage>112</fpage>  
        <lpage>7</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28993317"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1136/eb-2017-102755</pub-id>
        <pub-id pub-id-type="medline">28993317</pub-id>
        <pub-id pub-id-type="pii">eb-2017-102755</pub-id>
        <pub-id pub-id-type="pmcid">PMC5750412</pub-id></nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="web">
        <source>Oxford Health NHS Foundation Trust</source>  
        <access-date>2019-03-12</access-date>
        <comment>BlueIce app
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oxfordhealth.nhs.uk/blueice/">https://www.oxfordhealth.nhs.uk/blueice/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76oplpzty"/></comment> </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="web">
        <source>Calm</source>  
        <access-date>2019-03-12</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.calm.com/">https://www.calm.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76opxSSDs"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="web">
        <source>MyFitnessPal</source>  
        <access-date>2019-03-12</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.myfitnesspal.com/">https://www.myfitnesspal.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76oq55UrV"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
        <source>Dario</source>  
        <access-date>2019-03-12</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://mydario.com/">https://mydario.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76oqIVt44"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Schueller</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Neary</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>O'Loughlin</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Adkins</surname>
            <given-names>EC</given-names>
          </name>
        </person-group>
        <article-title>Discovery of and interest in health apps among those with mental health needs: survey and focus group study</article-title>
        <source>J Med Internet Res</source>  
        <year>2018</year>  
        <month>06</month>  
        <day>11</day>  
        <volume>20</volume>  
        <issue>6</issue>  
        <fpage>e10141</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/6/e10141/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10141</pub-id>
        <pub-id pub-id-type="medline">29891468</pub-id>
        <pub-id pub-id-type="pii">v20i6e10141</pub-id>
        <pub-id pub-id-type="pmcid">PMC6018235</pub-id></nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="web">
        <source>Federal Trade Commission</source>  
        <year>2016</year>  
        <month>01</month>  
        <day>15</day>  
        <access-date>2019-03-08</access-date>
        <comment>Lumosity to Pay $2 Million to Settle FTC Deceptive Advertising Charges for Its
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ftc.gov/news-events/press-releases/2016/01/lumosity-pay-2-million-settle-ftc-deceptive-advertising-charges">https://www.ftc.gov/news-events/press-releases/2016/01/lumosity-pay-2-million-settle-ftc-deceptive-advertising-charges</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ipAICcf"/></comment> </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="web">
        <source>Federal Trade Commission</source>  
        <year>2015</year>  
        <month>09</month>  
        <day>17</day>  
        <access-date>2019-03-08</access-date>
        <comment>FTC Charges Marketers of 'Vision Improvement' App with Deceptive Claims
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ftc.gov/news-events/press-releases/2015/09/ftc-charges-marketers-vision-improvement-app-deceptive-claims">https://www.ftc.gov/news-events/press-releases/2015/09/ftc-charges-marketers-vision-improvement-app-deceptive-claims</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ipKE4WS"/></comment> </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
