<?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 article-type="review-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <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">v26i1e58616</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/58616</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Quality Assessment of Digital Health Apps: Umbrella Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Foong</surname>
            <given-names>Yi Chao</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Causio</surname>
            <given-names>Francesco Andrea</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Zych</surname>
            <given-names>Maciej Marek</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>School of Computing</institution>
            <institution>Ulster University</institution>
            <addr-line>2-24 York St</addr-line>
            <addr-line>Belfast, BT15 1AP</addr-line>
            <country>United Kingdom</country>
            <phone>44 7526852505</phone>
            <email>maciejmarekzych@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0791-8976</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Bond</surname>
            <given-names>Raymond</given-names>
          </name>
          <degrees>BSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1078-2232</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Mulvenna</surname>
            <given-names>Maurice</given-names>
          </name>
          <degrees>BSc, MPhil, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1554-0785</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Martinez Carracedo</surname>
            <given-names>Jorge</given-names>
          </name>
          <degrees>PhD, BSc, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8017-2598</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Bai</surname>
            <given-names>Lu</given-names>
          </name>
          <degrees>BEng, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1242-5412</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Leigh</surname>
            <given-names>Simon</given-names>
          </name>
          <degrees>BSc, MSc, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6843-6447</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Computing</institution>
        <institution>Ulster University</institution>
        <addr-line>Belfast</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>School of Electronics, Electrical Engineering and Computer Science</institution>
        <institution>Queen's University Belfast</institution>
        <addr-line>Belfast</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>ORCHA</institution>
        <addr-line>Daresbury</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Maciej Marek Zych <email>maciejmarekzych@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>10</day>
        <month>10</month>
        <year>2024</year>
      </pub-date>
      <volume>26</volume>
      <elocation-id>e58616</elocation-id>
      <history>
        <date date-type="received">
          <day>20</day>
          <month>3</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>7</day>
          <month>6</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>23</day>
          <month>7</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>7</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Maciej Marek Zych, Raymond Bond, Maurice Mulvenna, Jorge Martinez Carracedo, Lu Bai, Simon Leigh. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 10.10.2024.</copyright-statement>
      <copyright-year>2024</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 (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2024/1/e58616" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>With an increasing number of digital health apps available in app stores, it is important to assess these technologies reliably regarding their quality. This is done to mitigate the risks associated with their use. There are many different guidelines, methods, and metrics available to assess digital health apps with regard to their quality.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to give a holistic summary of the current methods and “condition agnostic” frameworks that are broadly applicable for the quality assessment of all digital health apps.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A systematic search of literature was conducted on 4 databases: Scopus, PubMed, ACM Digital Library, and IEEE Xplore. We followed the PICOS (Population, Patient, or Problem; Intervention; Comparison; Outcomes; and Study Design) and PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) methodologies when conducting this umbrella review. The search was conducted on January 26, 2024, for review articles published between 2018 and 2023. We identified 4781 candidate papers for inclusion; after title and abstract screening, 39 remained. After full-text analysis, we included 15 review articles in the full review.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Of the 15 review articles, scoping reviews were the most common (n=6, 40%), followed by systematic reviews (n=4, 27%), narrative reviews (n=4, 27%), and a rapid review (n=1, 7%). A total of 4 (27%) review articles proposed assessment criteria for digital health apps. “Data privacy and/or security” was the most mentioned criterion (n=13, 87%) and “Cost” was the least mentioned criterion (n=1, 7%) for the assessment of digital health apps. The Mobile App Rating Scale was the most frequently used framework for quality assessment of digital health apps.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>There is a lack of unity or consolidation across identified frameworks, as most do not meet all the identified criteria from the reviewed articles. Safety concerns associated with the use of digital health apps may be mitigated with the use of quality frameworks.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>mHealth assessment</kwd>
        <kwd>digital health</kwd>
        <kwd>quality assessment</kwd>
        <kwd>health apps quality</kwd>
        <kwd>assessment criteria</kwd>
        <kwd>evaluation criteria</kwd>
        <kwd>health apps criteria</kwd>
        <kwd>assessment</kwd>
        <kwd>digital health app</kwd>
        <kwd>app</kwd>
        <kwd>umbrella review</kwd>
        <kwd>risk</kwd>
        <kwd>mobile phone</kwd>
        <kwd>frameworks</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Digital health apps have a potential to make health care more accessible to people of different age groups living with a wide range of health-related conditions. Currently, there are ongoing efforts by the National Health Service (NHS) in the United Kingdom to enhance the use of digital health technologies. These efforts were outlined in the NHS long-term plan [<xref ref-type="bibr" rid="ref1">1</xref>]. Moreover, these efforts were accelerated by the COVID-19 pandemic [<xref ref-type="bibr" rid="ref2">2</xref>]. There are approximately 250 new digital health apps available in app stores per day, with a total of approximately 350,000 digital health apps on the market as of 2021 [<xref ref-type="bibr" rid="ref3">3</xref>]. As digital health apps rise in popularity, so do the risks associated with their use. Digital health apps that are classified as “medical devices” [<xref ref-type="bibr" rid="ref4">4</xref>] in the United Kingdom are strictly regulated, but digital health apps that are classified as “wellness apps” do not face such regulations.</p>
      <p>There are organizations that produce guidelines and frameworks regarding the development and assessment of digital health apps. These include the International Organization for Standardization (ISO): Health and Wellness Apps—Quality and Reliability [<xref ref-type="bibr" rid="ref5">5</xref>] and the National Institute for Health and Care Excellence (NICE): Evidence Standards Framework [<xref ref-type="bibr" rid="ref6">6</xref>]. Digital Technology Assessment Criteria (DTAC) [<xref ref-type="bibr" rid="ref7">7</xref>] is an NHS-developed framework that is being used to provide criteria for the assessment of digital health apps. However, some of the guidelines may be open to interpretation, and there are frameworks that are currently being used to assess digital health apps for their quality.</p>
      <p>A scoping review published in 2023 [<xref ref-type="bibr" rid="ref8">8</xref>] examined the problems and barriers related to the use of digital health apps. It found that “validity,” “usability,” “technology,” “data privacy and security,” and “individuality” were addressed in several studies and are partly considered in quality assessment. “Use and adherence,” “patient-physician relationship,” “knowledge and skills,” “implementation,” and “costs” of digital health apps were rarely extensively studied. Furthermore, a systematic review published in 2021 [<xref ref-type="bibr" rid="ref9">9</xref>] found security challenges when developing digital health apps. These and other quality problems surrounding digital health apps may be mitigated by rigorously assessing their quality.</p>
      <p>Digital health apps are complex, and the usual methods for assessing medicines (survival, quality of life, and cost), as recommended by NICE, may not be sufficient to monitor the broad spectrum of potential issues arising from their use. Therefore, more specific requirements for assessment of quality are required. However, there is a lack of consensus on how best to achieve this.</p>
      <p>In this umbrella review, we define quality as “compliance with best practice standards.” The objective of this umbrella review was to give a holistic summary of the current methods and “condition agnostic” frameworks that are broadly applicable for the quality assessment of all digital health apps. Because several review articles have been published regarding the quality assessment of digital health apps, or aspects related to this, we conducted an umbrella review to provide a holistic view of how digital health apps are currently being assessed and where they can improve. This review can be informative to digital health researchers and assessment framework developers. In this umbrella review, we included systematic reviews, scoping reviews, rapid reviews, and narrative reviews.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Search Strategy and Criteria</title>
        <p>For the systematic search of literature, the PICOS (Population, Patient, or Problem; Intervention; Comparison; Outcomes; and Study Design; see <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>) and PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) methodologies have been used. The following search has been conducted using the Scopus, PubMed, ACM Digital Library, and IEEE Xplore databases with the following search objective: find literature, systematic, or scoping review articles for quality assessment of digital health apps. The search for review articles was conducted on January 26, 2024.</p>
        <boxed-text id="box1" position="float">
          <title>PICOS (Population, Patient, or Problem; Intervention; Comparison; Outcomes; and Study Design) methodology for systematic search of previous or related literature reviews.</title>
          <p>
            <bold>Inclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Problem: Review of quality assessment tools for digital health apps, full article, in English, from 2018 to 2023.</p>
            </list-item>
            <list-item>
              <p>Intervention: Quality assessment frameworks or criteria review applicable to all digital health apps.</p>
            </list-item>
            <list-item>
              <p>Comparator: Not applicable (N/A)</p>
            </list-item>
            <list-item>
              <p>Outcome: Review articles regarding quality (or aspects of quality, eg, usability) assessment frameworks or criteria applicable to all digital health apps.</p>
            </list-item>
            <list-item>
              <p>Study design: Search databases included Scopus, PubMed, ACM Digital Library, and IEEE Xplore. Search query for article title and abstract: ( ( mhealth OR ehealth OR m-health OR e-health OR “mobile health” OR “electronic health” OR “health app*” OR “medical health app*” OR “digital health app*” OR “digital health product*” OR “digital health intervention*” OR “digital health technolog*” OR “digital health solution*” ) AND ( assurance* OR assessment* OR evaluation* OR audit* OR framework* ) AND ( review* OR assessment* ) )</p>
            </list-item>
          </list>
          <p>
            <bold>Exclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Problem: Not quality assessment of digital health apps, conference paper, book or book chapter. Not in English.</p>
            </list-item>
            <list-item>
              <p>Intervention: Not a quality assessment frameworks or criteria review.</p>
            </list-item>
            <list-item>
              <p>Comparator: N/A</p>
            </list-item>
            <list-item>
              <p>Outcome: No information on quality assessment frameworks or criteria. Does not focus on digital health apps. Articles targeting specific users (eg, women or adolescence). Focuses on specific feature or category (condition area). Frameworks that focus on user acceptance of technology.</p>
            </list-item>
            <list-item>
              <p>Study design: N/A</p>
            </list-item>
          </list>
        </boxed-text>
        <p><xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> presents the PRIOR checklist and <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> presents the exact search queries that were used for each of the databases.</p>
      </sec>
      <sec>
        <title>Study Screen</title>
        <p>This study used PICOS methodology to set the inclusion and exclusion criteria (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>). The review articles included in this study were initially screened by title and abstract. If the review article focused on quality (or its aspect) assessment of digital health apps, it was read in full. If the article met inclusion criteria and none of the exclusion criteria (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>), it was included in the study. This systematic search followed PRISMA guidelines when screening the articles, where a step-by-step process was set forth. The Rayyan tool has been used to remove article duplicates.</p>
      </sec>
      <sec>
        <title>Critical Appraisal</title>
        <p>Because 4 (27%) of the 15 review articles were systematic reviews, for those reviews, the Joanna Briggs Institute (JBI) critical appraisal of systematic reviews [<xref ref-type="bibr" rid="ref10">10</xref>] has been used (see <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). This has been done to assess the quality of the systematic reviews to determine whether they should be included in this umbrella review.</p>
      </sec>
      <sec>
        <title>Data Extraction</title>
        <p>The characteristics of this study follow the applicable protocols for the umbrella review from the <italic>JBI Manual for Evidence Synthesis</italic> [<xref ref-type="bibr" rid="ref11">11</xref>]. The following information has been extracted: author-year, objectives, total sample size, number of sources searched, date (year) range of searched and included studies, number of studies included, methods of analysis, and key findings (see <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>).</p>
      </sec>
      <sec>
        <title>Data Synthesis</title>
        <p>In this study, we did not synthesize results statistically. Instead, we narratively synthesized key findings of each of the reviews. This was done due to the presumed heterogeneity of the included reviews.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p><xref rid="figure1" ref-type="fig">Figure 1</xref> shows the PRISMA process of selecting article reviews to be included in the study. The search queries used for each of the databases searched (Scopus, PubMed, ACM Digital Library, and IEEE Xplore) are available in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. After duplicates were removed, the articles were reviewed by title and abstract, and were included only if they were related to quality assessment of digital health apps and did not meet the exclusion criteria outlined in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. Afterward, 39 review articles were read in full and 15 met the inclusion criteria and were included in this umbrella review. This review was not registered and a protocol for systematic reviews was not prepared.</p>
        <p>Mendeley (Elsevier) was used to manage all the included review articles (n=15) in the study. The 15 review articles were published between 2018 and 2023. Scoping reviews were the most common (n=6, 40%), followed by systematic reviews (n=4, 27%), narrative reviews (n=4, 27%), and a rapid review (n=1, 7%). <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> depicts which criteria the review articles focused on.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) diagram of reviews selected for inclusion in the umbrella review.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e58616_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>The Assessment Criteria</title>
        <p>The objective of this umbrella review was to give a holistic summary of current methods and frameworks used for quality assessment of digital health apps. <xref ref-type="table" rid="table1">Table 1</xref> depicts 4 (27%) of the 15 review articles that reported on assessment criteria for digital health apps. Of the 4 review articles, 2 (50%) outlined what was being assessed with frameworks [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>] and 2 (50%) focused on what should be assessed [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. The remaining 11 review articles included in this umbrella review either focused on a specific criterion (eg, usability), the methods of assessment (eg, Likert scale), or referenced the criteria of a review article already accounted for (Woulfe et al [<xref ref-type="bibr" rid="ref16">16</xref>] references the Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] criteria). Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] stated that different articles defined assessment criteria differently. For example, usability was mentioned in 14 articles that were reviewed. One article considered usability a subclass of ease of use; other articles placed ease of use under usability.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Framework criteria used for the assessment of digital health apps.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="260"/>
            <col width="200"/>
            <col width="540"/>
            <thead>
              <tr valign="bottom">
                <td>Authors, Year</td>
                <td>Obtained by<sup>a</sup></td>
                <td>Criteria (assessment domains)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Hensher et al, 2021 [<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                <td>Assessing frameworks</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Clarity of purpose of the app</p>
                    </list-item>
                    <list-item>
                      <p>Developer credibility</p>
                    </list-item>
                    <list-item>
                      <p>Content or information validity</p>
                    </list-item>
                    <list-item>
                      <p>User experience</p>
                    </list-item>
                    <list-item>
                      <p>User engagement or adherence and social support interoperability</p>
                    </list-item>
                    <list-item>
                      <p>Value</p>
                    </list-item>
                    <list-item>
                      <p>Technical features and support</p>
                    </list-item>
                    <list-item>
                      <p>Privacy, security, ethical, or legal</p>
                    </list-item>
                    <list-item>
                      <p>Accessibility</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Nouri et al, 2018 [<xref ref-type="bibr" rid="ref13">13</xref>]</td>
                <td>Assessing frameworks</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Design</p>
                    </list-item>
                    <list-item>
                      <p>Information or content</p>
                    </list-item>
                    <list-item>
                      <p>Usability</p>
                    </list-item>
                    <list-item>
                      <p>Functionality</p>
                    </list-item>
                    <list-item>
                      <p>Ethical issues</p>
                    </list-item>
                    <list-item>
                      <p>Privacy and security</p>
                    </list-item>
                    <list-item>
                      <p>User-perceived value</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Moshi et al, 2018 [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>Preset or developed</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Six core criteria:</p>
                    </list-item>
                  </list>
                  <list list-type="bullet">
                    <list-item>
                      <p>Current use of the technology</p>
                    </list-item>
                    <list-item>
                      <p>Description and technical characteristics</p>
                    </list-item>
                    <list-item>
                      <p>Effectiveness</p>
                    </list-item>
                    <list-item>
                      <p>Safety</p>
                    </list-item>
                    <list-item>
                      <p>Cost and cost-effectiveness</p>
                    </list-item>
                    <list-item>
                      <p>Organizational aspects</p>
                    </list-item>
                  </list>
                  <list list-type="bullet">
                    <list-item>
                      <p>Three optional criteria:</p>
                    </list-item>
                  </list>
                  <list list-type="bullet">
                    <list-item>
                      <p>Legal aspects</p>
                    </list-item>
                    <list-item>
                      <p>ethical aspects</p>
                    </list-item>
                    <list-item>
                      <p>social aspects</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Lagan et al, 2021 [<xref ref-type="bibr" rid="ref15">15</xref>]</td>
                <td>Preset or developed</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Mobile health Index and Navigation Database (MIND) criteria:</p>
                    </list-item>
                  </list>
                  <list list-type="bullet">
                    <list-item>
                      <p>App origin</p>
                    </list-item>
                    <list-item>
                      <p>App functionality</p>
                    </list-item>
                    <list-item>
                      <p>Inputs and outputs</p>
                    </list-item>
                    <list-item>
                      <p>Privacy and security</p>
                    </list-item>
                    <list-item>
                      <p>Evidence and clinical foundation</p>
                    </list-item>
                    <list-item>
                      <p>Features and engagement style</p>
                    </list-item>
                    <list-item>
                      <p>App use</p>
                    </list-item>
                    <list-item>
                      <p>Interoperability and data sharing</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>“Obtained by” states whether assessment criteria have been identified by assessing assessment frameworks or preset or developed by other means.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] and Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] identified criteria by assessing assessment frameworks. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] and Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] had their own set of criteria and compared assessment frameworks against those criteria. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] developed a checklist for health technology assessment for mobile medical apps based on previous research [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] used the previously proposed Mobile health Index and Navigation Database (MIND) [<xref ref-type="bibr" rid="ref19">19</xref>], which was developed with inputs from clinicians, patients, family members, researchers, and policy makers with the aim of providing clinically relevant criteria. Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] stated that there may never be complete digital health apps assessment criteria because these criteria apply to digital health apps that are changing in development continuously.</p>
      </sec>
      <sec>
        <title>Data Privacy or Security</title>
        <p>Thirteen (87%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref27">27</xref>] mention the data privacy or security of digital health apps. Three reviews [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>] found that reviewed articles often considered privacy and security together when evaluating digital health apps. Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>] highlighted that although privacy and security overlap, security relates to protection against unauthorized access to data, and privacy is an individual’s right to maintain control of their personal data. The review points out that exclusively focusing on security can lead to increased surveillance, which can introduce privacy risks. Furthermore, Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] stated that interpretation of privacy, security, and safety considerations differed when examining different quality assessment tools or methods.</p>
        <p>Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>] found that methods used to evaluate security are more technical, whereas methods used to evaluate privacy are more user oriented. Some of the review articles [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref21">21</xref>] pointed out that there appears to be greater effort to assess privacy. However, Muro-Culebras et al [<xref ref-type="bibr" rid="ref22">22</xref>] found lack of assessment regarding developer transparency and policies regarding user data privacy and security. Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] found that most of the examined assessment frameworks (43/79, 54%) included privacy-related questions. Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] also found privacy and security to be frequently addressed in assessment frameworks.</p>
        <p>Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] discussed how guidelines such as General Data Protection Regulation (GDPR) [<xref ref-type="bibr" rid="ref28">28</xref>] rely on the users’ knowledge and “notice and consent” model. Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] referenced a study published in 2020 [<xref ref-type="bibr" rid="ref29">29</xref>] that discusses whether GDPR is fit for purpose, as it assumes that users can know why and how their data are being collected and shared. GDPR also assumes that individual app users can control how their personal data are being processed. Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] stated that the majority of digital health apps fail to provide assurances around privacy and security. On the other hand, Carmi et al [<xref ref-type="bibr" rid="ref25">25</xref>] focused on the interpretation of GDPR for mobile health.</p>
        <p>Galvin and DeMuro [<xref ref-type="bibr" rid="ref26">26</xref>] discussed how recent literature has shown that aggregated data that were previously considered deidentified have been shown to be reidentifiable. The review states that data storage and transmission of mobile health data remain a security concern. Moreover, the review points out that because of the lack of privacy policy, or because of the complex language used in such policies, there may be lack of consumer informed consent when using mobile health apps.</p>
      </sec>
      <sec>
        <title>Clinical Assurance, Credibility of Information, or Evidence</title>
        <p>Eleven (73%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>] included in this umbrella review mentioned clinical assurance, credibility of information of digital health apps, and evidence. Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] stated that in 2 studies included in their review, third-party sponsorships were deemed important due to a possible conflict of interest between developers of an app and sponsors, affecting developers’ credibility. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] found that credibility of information of mobile medical apps was assessed by 15 (33%) of 45 frameworks. Moreover, 27 (60%) of 45 frameworks included questions about mobile medical apps’ source of information. None of the frameworks assessed the health impact of mobile medical apps that provide diagnostics or information. The review concluded that none of the included frameworks met all the health technology assessment criteria (see <xref ref-type="table" rid="table1">Table 1</xref>—Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>]) set forth. A total of 3 (7%) of 45 frameworks specifically asked about randomized controlled trials. Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>], which expands on the work done by Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>], has shown that more frameworks include questions around clinical foundation than in their previous article published in 2019 [<xref ref-type="bibr" rid="ref31">31</xref>], indicating an increase of interest around clinical foundation assessment.</p>
        <p>Muro-Culebras et al [<xref ref-type="bibr" rid="ref22">22</xref>] stated that many authors use their own personalized questionnaires for assessment, specifically designed to assess the characteristics of their specific digital health apps. The review article stated that because the approach is a personalized questionnaire, there is greater flexibility than in other generic tools. However, lack of validation and reliability (such as inter-rater reliability) raises questions about their suitability for digital health app assessment. Muro-Culebras et al [<xref ref-type="bibr" rid="ref22">22</xref>] concluded that highly validated tools for the assessment of digital health apps are still a largely unexplored topic in the market. Similarly, Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] stated that there is a lack of measurement tool validation. Furthermore, users do not appear to have much awareness of the source or validity of health information of a digital health app. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] found that digital health apps lack domain expert involvement regarding the app content and provide poor evidence base and poor validation.</p>
      </sec>
      <sec>
        <title>User Experience, Value, Efficacy or Effectiveness, or Engagement</title>
        <p>Eleven (73%) of 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] mentioned user experience, value, efficacy, or engagement. Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] found that aspects of user experience have been frequently assessed by the assessment frameworks. Moreover, the review stated that there is limited evidence on how to evaluate the value domain in the literature. They speculate that this could be due to the current landscape of digital health apps’ market being fast and evolving, and the subjectivity of value. The review also stated that studies to demonstrate apps’ efficacy and value for money are not undertaken often. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] stated that of 45 frameworks included in the review, all assessed effectiveness to some extent. Of 45 frameworks, 11 assessed user satisfaction and 30 assessed technical efficacy of mobile medical apps.</p>
        <p>Maramba et al [<xref ref-type="bibr" rid="ref32">32</xref>] focused on methods of usability testing of eHealth applications. Questionnaires, task completion, think-aloud protocol, interviews, heuristic testing, and focus groups were the most frequently used methods of assessment, whereas methods such as eye tracking were rarely used. The review concludes that more investigation needs to be made into assessing usability of eHealth applications. Muro-Culebras et al [<xref ref-type="bibr" rid="ref22">22</xref>] found that usability among the 8 frameworks assessed in the review was commonly assessed together with engagement, aesthetics, or functionality. Moreover, the review found that 2 (75%) of the 8 frameworks had a user assessor and a professional assessor version. Woulfe et al [<xref ref-type="bibr" rid="ref16">16</xref>] point out that many digital health apps are not based on any behavior change theory, and in many cases, effectiveness is inadequately assessed. They also address the possibility of using different assessment methodologies in high-, low-, and middle-income countries.</p>
        <p>Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] point out that subjective user experience may limit generalizability and standardization of frameworks. This is because assessment would reflect the experience of the assessor. The review further points out that although subjective in nature, information on user friendliness, visual appeal, and interface design may be of great interest to the user and a good predictor of user engagement.</p>
        <p>Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] stated that users should be involved in usability testing of digital health apps. Their review indicates that consumers were able to identify many critical issues with digital health apps, such as incorrect information, inappropriate response to their needs, gaps in features, and faults with alarms. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] suggest that allowing users who are consumers of digital health apps to be involved in usability testing will enable the identification and resolution of usability problems before the apps are made available to the public.</p>
        <p>Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] pointed out that the assessment frameworks mainly focused on content quality and usability, with less attention given to design, security and privacy, functionality, user-perceived value, and ethical issues. Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] stated that usability was treated in different ways by different articles. For example, one article considered usability a subclass of ease of use, and other articles placed ease of use under usability. Azad-Khaneghah et al [<xref ref-type="bibr" rid="ref27">27</xref>] found that many of the usability and quality rating scales are targeted at professionals. Moreover, the review found that System Usability Scale (SUS) was the most widely used framework or scale (12/40 studies), mainly due to its simplicity. Similarly, Hajesmaeel-Gohari et al [<xref ref-type="bibr" rid="ref30">30</xref>] found that general questionnaires with fewer questions and higher reliability, such as SUS, have been used more often. Furthermore, the review recommends using frameworks such as the mHealth App Usability Questionnaire [<xref ref-type="bibr" rid="ref33">33</xref>] that were specifically designed for mobile apps, unlike the SUS.</p>
      </sec>
      <sec>
        <title>Safety</title>
        <p>Safety (in different contexts) has been mentioned by 9 (60%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. Safety and risks of digital health apps can arise from different factors. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] elaborate on different safety concerns and risks associated with the use of digital health apps. The review found 67 safety concerns related to the quality of content, which are grouped into the following 5 categories: incorrect information, incomplete information, variation in content, incorrect output, and inappropriate response to consumer needs. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] found 13 safety concerns related to software functionality. These are grouped into 5 more categories: gaps in features, lack of validation for user input, delayed processing, response to health dangers, and faulty alarms. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] further discuss consequence of safety concerns, for example, how one of the digital health apps led to dangerous levels of alcohol consumption among a group of 341 students. Overall, many of the frameworks do not cover the necessary criteria to quality assess digital health apps [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] consider safety as part of the assessment criteria for digital health apps (see <xref ref-type="table" rid="table1">Table 1</xref>).</p>
      </sec>
      <sec>
        <title>Features or Functionality</title>
        <p>Six (40%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] considered feature or functionality as criteria to be assessed, referred to as technical characteristics by Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>]. Furthermore, Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>] mention that feature assessment was common when assessing security and privacy. Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] stated that features related to ease of use and visual appeal may be the most important drive of user engagement of mental health apps. Moreover, “subjective questions” around user friendliness, visual appeal and interface design, although difficult to standardize and to assess, may be the greatest predictor of user engagement. Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] and Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] identified digital health apps’ features as part of the assessment criteria (<xref ref-type="table" rid="table1">Table 1</xref>). Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] and Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] included functionality and technical characteristics, respectively, as part of their assessment criteria for digital health apps. The terms “features,” “functionality,” and “technical characteristics” seem to overlap in the review articles.</p>
        <p>Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] stated that 2 (9%) of 23 review articles provided dynamic assessment criteria based on the use cases and features of specific digital health apps, meaning that the assessment criteria were selected for apps based on the use case. They provide an example of the criterion “accuracy of the calculations,” being used only when an app provides at least 1 calculation. Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] stated that many digital health apps had gaps in features that inadequately supported user tasks. They gave an example of “Tele dermatology” apps that did not account for allergies or current medication status.</p>
      </sec>
      <sec>
        <title>Cost</title>
        <p>Cost as a criterion has been mentioned by 1 (7%) of the 15 review articles [<xref ref-type="bibr" rid="ref14">14</xref>]. Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] stated that there may be a cost barrier to accessing mobile medical apps because they may contain in-app purchases or require a subscription. They further stated that only 1 (2%) of 45 frameworks assessed cost-effectiveness (in terms of economic assessment) and 11 (24%) of 45 reviewed the cost in terms of price to download or in-app purchases. Nine (60%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] mentioned the cost of digital health apps, the cost of data breaches, or equipment cost, but not as a criterion for quality assessment.</p>
      </sec>
      <sec>
        <title>Ethical or Legal Issues</title>
        <p>Ethical or legal concepts have been mentioned by 10 (67%) of the 15 review articles [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>] and Benjumea et al [<xref ref-type="bibr" rid="ref20">20</xref>] discuss ethical and legal concepts regarding data and data breaches. Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>] discuss how in their review of privacy and security of digital health apps, there was a considerable lack of discussion in the reviewed articles (n=83) regarding privacy or security ethics. Grundy [<xref ref-type="bibr" rid="ref23">23</xref>] stated that quality assessment frameworks give less attention to ethical issues. The author also stated that legal compliance around content and intellectual property is an aspect of quality regarding commercial apps.</p>
        <p>Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] discuss health technology assessment criteria for the assessment of mobile medical apps, including ethical and legal aspects. The review found that 4 (9%) of 45 frameworks discussed legal aspects and 24 (53%) of 45 frameworks discussed ethics. Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] also included ethics and legal aspects as part of their assessment criteria (see <xref ref-type="table" rid="table1">Table 1</xref>). For example, in the reviews of both Moshi et al [<xref ref-type="bibr" rid="ref14">14</xref>] and Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>], ethical aspects included privacy policies and legal aspects with mention of disclaimers. Nouri et al [<xref ref-type="bibr" rid="ref13">13</xref>] included ethical issues as part of the assessment criteria (see <xref ref-type="table" rid="table1">Table 1</xref>). Akbar et al [<xref ref-type="bibr" rid="ref24">24</xref>] stated that health care professionals may hesitate to promote digital health apps in part due to legal issues.</p>
      </sec>
      <sec>
        <title>Assessment Methods and Metrics</title>
        <p>Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] from Deakin University conducted a scoping review focusing on the time frame from 2011 to April 2020 using search terms that were synonyms of “health apps,” “evaluation,” and “frameworks” [<xref ref-type="bibr" rid="ref12">12</xref>]. This review examined 97 evaluation frameworks and studies that included general digital health app evaluation frameworks, such as the Mobile App Rating Scale (MARS), and more domain-specific frameworks, such as the SUS and Software Usability Measurement Inventory (SUMI).</p>
        <p>The scoring and rating techniques varied within the different frameworks, that is, 23% of frameworks used a 5-point scale, 6% a 3-point scale, 3% a 7-point scale, 2% a 4-point scale, and 1% a 10-point scale. A total of 24% frameworks did not elaborate on the scaling system, 20% used a mixed approach, 13% were dichotomous, and 8% did not use a scaling system [<xref ref-type="bibr" rid="ref12">12</xref>]. Moreover, the frameworks’ scoring modalities also varied as 37% did not report a score, 23% used a mean score, 13% used a total sum, 11% used mixed approaches, 9% other, and 6% did not use scoring at all [<xref ref-type="bibr" rid="ref12">12</xref>]. In Nurgalieva et al [<xref ref-type="bibr" rid="ref21">21</xref>], it appears that the evaluation of self-declared data from app developers was the most common privacy assessment method.</p>
        <p>Hensher et al [<xref ref-type="bibr" rid="ref12">12</xref>] examined the domain or criteria needed to evaluate digital health apps and found that user experience together with information validity has been the most evaluated criteria. However, this scoping review included frameworks such as SUS and SUMI, and such frameworks that are designed to evaluate usability are not tailored to digital health apps. In their “count,” if a framework evaluated an aspect of user experience (UX), it was considered a scale for evaluating UX. Usability is only one aspect of UX.</p>
        <p>Lagan et al [<xref ref-type="bibr" rid="ref15">15</xref>] found that most evaluation frameworks for health apps were concerned with evidence, clinical foundation, and privacy. This study suggests that it is unclear whether engagement has been adequately predicted with the existing frameworks. The study also suggests that a balance between objective and subjective questions is a challenge for evaluation frameworks.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This umbrella review included 15 review articles that were obtained via a systematic search of the literature (see <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> and <xref rid="figure1" ref-type="fig">Figure 1</xref>). The objective of this review was to give a holistic summary of current methods and frameworks used for quality assessment of digital health apps. It appears that frameworks are a common way of assessing digital health apps. Four (27%) of the 15 review articles tried to establish appropriate assessment criteria for digital health apps. Two (50%) of these 4 review articles [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>] reviewed frameworks for digital health app assessment and derived their criteria. The other 2 (50%) of these 4 review articles [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>] had predefined criteria based on previous research in the area (see <xref ref-type="table" rid="table1">Table 1</xref>). In the review articles, there was a lack of discussion regarding the unethical use of dark patterns, defined by UX dictionary [<xref ref-type="bibr" rid="ref34">34</xref>] as “deceptive design patterns used to mislead users to make them do something they would not do on their own. They are primarily used to generate sales, increase subscriptions, and hit target business numbers.” Also, there was no mention of equality, diversity, and/or inclusion.</p>
        <p>MARS has been the most frequently used framework for quality assessment according to 2 review articles [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Across the review articles included in this study, 13 (87%) of 15 included data privacy or security as a criterion. Hence, data privacy or security was the most common criterion. The least mentioned criterion was cost, with 1 (7%) of 15 review articles mentioning it (see <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>). Having an overarching assessment framework would reduce the need to apply several separate frameworks in the pursuit of identifying digital health app quality. However, when using frameworks for the quality assessment of digital health apps, it is important to remember the various limitations of frameworks. For example:</p>
        <list list-type="order">
          <list-item>
            <p>A framework can contain a lot of questions that sometimes need to be answered in a specific order. Hence, using it may require training.</p>
          </list-item>
          <list-item>
            <p>A framework may not “capture” all necessary aspects of a product or system for evaluation.</p>
          </list-item>
          <list-item>
            <p>A framework may be better at “capturing” one aspect of a product or system, for example, effectively evaluate ease of use, but lack in clinical assurance.</p>
          </list-item>
          <list-item>
            <p>Evaluation is never perfect; frameworks rely on good interrater and intrarater reliability.</p>
          </list-item>
          <list-item>
            <p>Frameworks are limited by their domain or condition area, meaning a framework may be suitable to assess all digital health apps (such as Enlight [<xref ref-type="bibr" rid="ref34">34</xref>]), but not pick up on a condition area that is specific to quality issues, such as insulin intake for diabetes apps.</p>
          </list-item>
        </list>
        <p>Speculation can be made that health condition–specific frameworks may provide a more accurate view of quality. This is because specific features may be required by digital health apps targeted at a specific health condition. A framework for a specific health condition, for example, may include questions such as insulin intake for diabetic users of an app. A generic, all-encompassing frameworks may include questions such as “did the app development involve a relevant health expert?” which could only indicate, not verify, whether necessary features are included.</p>
        <p>Woulfe et al [<xref ref-type="bibr" rid="ref16">16</xref>] point out that a framework coined Enlight [<xref ref-type="bibr" rid="ref34">34</xref>] is a far-reaching and all-encompassing framework for the assessment of digital health apps. However, Enlight includes many questions, more than other generic frameworks used for the assessment of digital health apps. Hence, using it may take more time and curtail its use. However, the use of such frameworks may help in the mitigation of variety of problems with digital health apps [<xref ref-type="bibr" rid="ref8">8</xref>],9], whereas using inadequate assessment frameworks may lead to overlooking flaws associated with the use of digital health apps. Hence, choosing a framework that adheres to all or most of the criteria mentioned in <xref ref-type="table" rid="table1">Table 1</xref>, such as DTAC [<xref ref-type="bibr" rid="ref7">7</xref>] or Enlight [<xref ref-type="bibr" rid="ref34">34</xref>], should enable a selection of a good quality app, despite not being focused on a specific condition area.</p>
        <p>When developing new quality assessment frameworks, it may be helpful for the assessor to assess related criteria together; however, on the flip side, it can create confusion. For example, Nurgalieva et al [<xref ref-type="bibr" rid="ref20">20</xref>] pointed out that exclusively focusing on security can lead to increased surveillance, which can introduce privacy risks. It can be speculated that if one criterion is being assessed, such as security, then privacy is also being assessed, leading to the omission of questions or areas in the assessment where security and privacy may be in conflict. Hence, caution needs to be taken when merging criteria into one in a framework. <xref ref-type="boxed-text" rid="box2">Textbox 2</xref> provides a list of recommendations to improve the development of quality assessment frameworks.</p>
        <boxed-text id="box2" position="float">
          <title>Recommendations to improve the development of quality assessment frameworks.</title>
          <list list-type="order">
            <list-item>
              <p>Standardize definitions of the criteria used for the quality assessment of digital health apps.</p>
            </list-item>
            <list-item>
              <p>When choosing any framework, ensure that it has been validated regarding its content and inter-rater reliability.</p>
            </list-item>
            <list-item>
              <p>Choosing a framework that adheres to all or most of the criteria mentioned in <xref ref-type="table" rid="table1">Table 1</xref> should enable a selection of a good quality app.</p>
            </list-item>
            <list-item>
              <p>Ensure that improving compliance with one criterion does not sabotage the other. For example, an increase in security does not sabotage data privacy.</p>
            </list-item>
            <list-item>
              <p>Ensure that when frameworks combine multiple criteria into one, for example, data privacy and security, there are no omissions of questions related to the original criteria.</p>
            </list-item>
            <list-item>
              <p>More focus on the unethical use of dark patterns in app design.</p>
            </list-item>
            <list-item>
              <p>Include criteria related to equality, diversity, and inclusion in order to ensure that digital health apps are widely available to different groups of people.</p>
            </list-item>
            <list-item>
              <p>Choosing a framework for a specific health condition may allow for the assessment of specific or necessary features that would not be covered by a generic framework.</p>
            </list-item>
            <list-item>
              <p>Ensure that third-party sponsorships do not lead to conflict of interest between developers of an app and sponsors, thus affecting the developers’ credibility.</p>
            </list-item>
            <list-item>
              <p>Ensure that the language in the privacy policy is easily understandable. Frameworks should point out when privacy policy of an app contains language that is unnecessarily unclear or vague.</p>
            </list-item>
            <list-item>
              <p>Specifying the context in which safety concerns are being assessed can reduce confusion, for example, safety related to data privacy or evidence for clinical assurance.</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This review is based on 15 review articles, most commonly scoping reviews (n=6, 40%), followed by systematic reviews (n=4, 27%), narrative reviews (n=4, 27%), and a rapid review (n=1, 7%). Using different search queries and searching wider publication dates could yield more results. The screening of articles was conducted by 1 coauthor. This review only included article reviews that contained the word “review” in the title. Any review about quality of digital health apps that was condition specific (eg, diabetes) was excluded from this umbrella review.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The majority of frameworks do not meet all the criteria identified from the reviewed articles. Safety concerns associated with the use of digital health apps may be mitigated with the use of quality frameworks. Some criteria for the assessment of digital health apps may conflict with each other. For example, overly focusing on security may lead to privacy concerns. Research indicates that subjective questions, although difficult to standardized, may be the most useful when assessing engagement.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Preferred Reporting Items for Overviews of Reviews (PRIOR) checklist.</p>
        <media xlink:href="jmir_v26i1e58616_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 239 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Search queries.</p>
        <media xlink:href="jmir_v26i1e58616_app2.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>JBI critical appraisal of systematic reviews.</p>
        <media xlink:href="jmir_v26i1e58616_app3.docx" xlink:title="DOCX File , 45 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Article characteristics.</p>
        <media xlink:href="jmir_v26i1e58616_app4.docx" xlink:title="DOCX File , 105 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Criteria addressed by each paper.</p>
        <media xlink:href="jmir_v26i1e58616_app5.docx" xlink:title="DOCX File , 53 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">DTAC</term>
          <def>
            <p>Digital Technology Assessment Criteria</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ISO</term>
          <def>
            <p>International Organization for Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">JBI</term>
          <def>
            <p>Joanna Briggs Institute</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MARS</term>
          <def>
            <p>Mobile App Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">MIND</term>
          <def>
            <p>Mobile health Index and Navigation Database</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">NICE</term>
          <def>
            <p>National Institute for Health and Care Excellence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">PICOS</term>
          <def>
            <p>Population, Patient, or Problem; Intervention; Comparison; Outcomes; and Study Design</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">SUMI</term>
          <def>
            <p>Software Usability Measurement Inventory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">UX</term>
          <def>
            <p>user experience</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The study discussed in this paper has been conducted as part of a PhD Co-operative Awards in Science and Technology (CAST) award, with funding from the Department for the Economy in Northern Ireland and the ORCHA (Organisation for the Review of Care and Health Applications) in the United Kingdom.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <source>The NHS long term plan</source>
          <access-date>2021-12-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.longtermplan.nhs.uk/publication/nhs-long-term-plan/">https://www.longtermplan.nhs.uk/publication/nhs-long-term-plan/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>The NHS long term plan and COVID-19</article-title>
          <source>The Health Foundation</source>
          <access-date>2021-10-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.health.org.uk/publications/reports/the-nhs-long-term-plan-and-covid-19">https://www.health.org.uk/publications/reports/the-nhs-long-term-plan-and-covid-19</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kern</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Skye</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Krupnick</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pawley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Preciado</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Written consent of IQVIA and the IQVIA Institute</article-title>
          <source>Digital Health Trends</source>
          <access-date>2021-06-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iqvia.com/insights/the-iqvia-institute/reports-and-publications/reports/digital-health-trends-2021">https://www.iqvia.com/insights/the-iqvia-institute/reports-and-publications/reports/digital-health-trends-2021</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Regulating medical devices in the UK</article-title>
          <source>GOV.UK</source>
          <access-date>2023-06-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/guidance/regulating-medical-devices-in-the-uk">https://www.gov.uk/guidance/regulating-medical-devices-in-the-uk</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/TS 82304-2:2021 Health software Part 2: Health and wellness apps—quality and reliability</article-title>
          <source>ISO</source>
          <access-date>2023-02-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/78182.html">https://www.iso.org/standard/78182.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Evidence standards framework for digital health technologies</article-title>
          <source>NICE</source>
          <access-date>2022-06-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nice.org.uk/corporate/ecd7">https://www.nice.org.uk/corporate/ecd7</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <article-title>Digital Technology Assessment Criteria (DTAC)</article-title>
          <source>NHS</source>
          <access-date>2021-11-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nhsx.nhs.uk/key-tools-and-info/digital-technology-assessment-criteria-dtac/">https://www.nhsx.nhs.uk/key-tools-and-info/digital-technology-assessment-criteria-dtac/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Giebel</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Speckemeier</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Abels</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Plescher</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Börchers</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wasem</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Blase</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Neusser</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Problems and barriers related to the use of digital health applications: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <volume>25</volume>
          <fpage>e43808</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e43808/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/43808</pub-id>
          <pub-id pub-id-type="medline">37171838</pub-id>
          <pub-id pub-id-type="pii">v25i1e43808</pub-id>
          <pub-id pub-id-type="pmcid">PMC10221513</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>Aljedaani</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Babar</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>Challenges with developing secure mobile health applications: systematic review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>e15654</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/6/e15654/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15654</pub-id>
          <pub-id pub-id-type="medline">34152277</pub-id>
          <pub-id pub-id-type="pii">v9i6e15654</pub-id>
          <pub-id pub-id-type="pmcid">PMC8277314</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Checklist for systematic reviews and research syntheses</article-title>
          <source>JBI</source>
          <year>2017</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbi.global/sites/default/files/2019-05/JBI_Critical_Appraisal-Checklist_for_Systematic_Reviews2017_0.pdf">https://jbi.global/sites/default/files/2019-05/JBI_Critical_Appraisal-Checklist_for_Systematic_Reviews2017_0.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aromataris</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Fernandez</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Holly</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Tungpunkom</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Aromataris</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lockwood</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Porritt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Pilla</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jordan</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Umbrella reviews (2020)</article-title>
          <source>JBI Manual for Evidence Synthesis</source>
          <year>2024</year>
          <publisher-loc>Adelaide, South Australia</publisher-loc>
          <publisher-name>JBI</publisher-name>
        </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>Hensher</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cooper</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dona</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Angeles</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Heynsbergh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Chatterton</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Peeters</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Scoping review: development and assessment of evaluation frameworks of mobile health apps for recommendations to consumers</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <volume>28</volume>
          <issue>6</issue>
          <fpage>1318</fpage>
          <lpage>1329</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33787894"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocab041</pub-id>
          <pub-id pub-id-type="medline">33787894</pub-id>
          <pub-id pub-id-type="pii">6205942</pub-id>
          <pub-id pub-id-type="pmcid">PMC8263081</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nouri</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kalhori</surname>
              <given-names>SRN</given-names>
            </name>
            <name name-style="western">
              <surname>Ghazisaeedi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marchand</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Yasini</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Criteria for assessing the quality of mHealth apps: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <volume>25</volume>
          <issue>8</issue>
          <fpage>1089</fpage>
          <lpage>1098</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29788283"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy050</pub-id>
          <pub-id pub-id-type="medline">29788283</pub-id>
          <pub-id pub-id-type="pii">4996915</pub-id>
          <pub-id pub-id-type="pmcid">PMC7646896</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moshi</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Tooher</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Merlin</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Suitability of current evaluation frameworks for use in the health technology assessment of mobile medical applications: a systematic review</article-title>
          <source>Int J Technol Assess Health Care</source>
          <year>2018</year>
          <volume>34</volume>
          <issue>5</issue>
          <fpage>464</fpage>
          <lpage>475</lpage>
          <pub-id pub-id-type="doi">10.1017/S026646231800051X</pub-id>
          <pub-id pub-id-type="medline">30201060</pub-id>
          <pub-id pub-id-type="pii">S026646231800051X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lagan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sandler</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Torous</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Evaluating evaluation frameworks: a scoping review of frameworks for assessing health apps</article-title>
          <source>BMJ Open</source>
          <year>2021</year>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>e047001</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&amp;pmid=33741674"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2020-047001</pub-id>
          <pub-id pub-id-type="medline">33741674</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2020-047001</pub-id>
          <pub-id pub-id-type="pmcid">PMC7986656</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woulfe</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Fadahunsi</surname>
              <given-names>KP</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chirambo</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Larsson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Henn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mawkin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>O' Donoghue</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Identification and evaluation of methodologies to assess the quality of mobile health apps in high-, low-, and middle-income countries: rapid review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>10</issue>
          <fpage>e28384</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/10/e28384/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/28384</pub-id>
          <pub-id pub-id-type="medline">34636737</pub-id>
          <pub-id pub-id-type="pii">v9i10e28384</pub-id>
          <pub-id pub-id-type="pmcid">PMC8548973</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velasco</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Perleth</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Drummond</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gürtner</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jørgensen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jovell</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Malone</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rüther</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wild</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Best practice in undertaking and reporting health technology assessments. Working group 4 report</article-title>
          <source>Int J Technol Assess Health Care</source>
          <year>2002</year>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>361</fpage>
          <lpage>422</lpage>
          <pub-id pub-id-type="doi">10.1017/s0266462302000284</pub-id>
          <pub-id pub-id-type="medline">12053427</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>Merlin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tamblyn</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ellery</surname>
              <given-names>B</given-names>
            </name>
            <collab>INAHTA Quality Assurance Group</collab>
          </person-group>
          <article-title>What's in a name? Developing definitions for common health technology assessment product types of the International Network of Agencies for Health Technology Assessment (INAHTA)</article-title>
          <source>Int J Technol Assess Health Care</source>
          <year>2014</year>
          <volume>30</volume>
          <issue>4</issue>
          <fpage>430</fpage>
          <lpage>437</lpage>
          <pub-id pub-id-type="doi">10.1017/S0266462314000543</pub-id>
          <pub-id pub-id-type="medline">25397872</pub-id>
          <pub-id pub-id-type="pii">S0266462314000543</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>Mobile health index and navigation database, app evaluation resources</article-title>
          <source>MINDapps</source>
          <access-date>2023-11-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mindapps.org/">https://mindapps.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benjumea</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ropero</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rivera-Romero</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Dorronzoro-Zubiete</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Carrasco</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Privacy assessment in mobile health apps: scoping review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>7</issue>
          <fpage>e18868</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/7/e18868/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18868</pub-id>
          <pub-id pub-id-type="medline">32459640</pub-id>
          <pub-id pub-id-type="pii">v8i7e18868</pub-id>
          <pub-id pub-id-type="pmcid">PMC7367524</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>Nurgalieva</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>O'Callaghan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Doherty</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Security and privacy of mHealth applications: a scoping review</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <volume>8</volume>
          <fpage>104247</fpage>
          <lpage>104268</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1109/ACCESS.2020.2999934"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/access.2020.2999934</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Muro-Culebras</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Escriche-Escuder</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Martin-Martin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Roldán-Jiménez</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>De-Torres</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ruiz-Muñoz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez-Sanchez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mayoral-Cleries</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Biró</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Nikolova</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Salvatore</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cuesta-Vargas</surname>
              <given-names>AI</given-names>
            </name>
          </person-group>
          <article-title>Tools for evaluating the content, efficacy, and usability of mobile health apps according to the consensus-based standards for the selection of health measurement instruments: systematic review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>12</issue>
          <fpage>e15433</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/12/e15433/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15433</pub-id>
          <pub-id pub-id-type="medline">34855618</pub-id>
          <pub-id pub-id-type="pii">v9i12e15433</pub-id>
          <pub-id pub-id-type="pmcid">PMC8686474</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grundy</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>A review of the quality and impact of mobile health apps</article-title>
          <source>Annu Rev Public Health</source>
          <year>2022</year>
          <volume>43</volume>
          <fpage>117</fpage>
          <lpage>134</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.annualreviews.org/content/journals/10.1146/annurev-publhealth-052020-103738?crawler=true&amp;mimetype=application/pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.1146/annurev-publhealth-052020-103738</pub-id>
          <pub-id pub-id-type="medline">34910582</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Akbar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Magrabi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Safety concerns with consumer-facing mobile health applications and their consequences: a scoping review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <volume>27</volume>
          <issue>2</issue>
          <fpage>330</fpage>
          <lpage>340</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31599936"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz175</pub-id>
          <pub-id pub-id-type="medline">31599936</pub-id>
          <pub-id pub-id-type="pii">5585394</pub-id>
          <pub-id pub-id-type="pmcid">PMC7025360</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carmi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zohar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Riva</surname>
              <given-names>GM</given-names>
            </name>
          </person-group>
          <article-title>The European General Data Protection Regulation (GDPR) in mHealth: theoretical and practical aspects for practitioners' use</article-title>
          <source>Med Sci Law</source>
          <year>2023</year>
          <volume>63</volume>
          <issue>1</issue>
          <fpage>61</fpage>
          <lpage>68</lpage>
          <pub-id pub-id-type="doi">10.1177/00258024221118411</pub-id>
          <pub-id pub-id-type="medline">35950240</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Galvin</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>DeMuro</surname>
              <given-names>PR</given-names>
            </name>
          </person-group>
          <article-title>Developments in privacy and data ownership in mobile health technologies, 2016-2019</article-title>
          <source>Yearb Med Inform</source>
          <year>2020</year>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>32</fpage>
          <lpage>43</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0040-1701987"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0040-1701987</pub-id>
          <pub-id pub-id-type="medline">32823298</pub-id>
          <pub-id pub-id-type="pmcid">PMC7442507</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Azad-Khaneghah</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Neubauer</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Miguel Cruz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Mobile health app usability and quality rating scales: a systematic review</article-title>
          <source>Disabil Rehabil Assist Technol</source>
          <year>2021</year>
          <volume>16</volume>
          <issue>7</issue>
          <fpage>712</fpage>
          <lpage>721</lpage>
          <pub-id pub-id-type="doi">10.1080/17483107.2019.1701103</pub-id>
          <pub-id pub-id-type="medline">31910687</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <source>General Data Protection Regulation</source>
          <access-date>2022-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/">https://gdpr-info.eu/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marelli</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lievevrouw</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>van Hoyweghen</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Fit for purpose? The GDPR and the governance of European digital health</article-title>
          <source>Policy Studies</source>
          <year>2020</year>
          <volume>41</volume>
          <issue>5</issue>
          <fpage>447</fpage>
          <lpage>467</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/01442872.2020.1724929"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/01442872.2020.1724929</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hajesmaeel-Gohari</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khordastan</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Fatehi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Samzadeh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bahaadinbeigy</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>The most used questionnaires for evaluating satisfaction, usability, acceptance, and quality outcomes of mobile health</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2022</year>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>22</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-022-01764-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-022-01764-2</pub-id>
          <pub-id pub-id-type="medline">35081953</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-022-01764-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC8793175</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>Henson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>David</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Albright</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Torous</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Deriving a practical framework for the evaluation of health apps</article-title>
          <source>Lancet Digit Health</source>
          <year>2019</year>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>e52</fpage>
          <lpage>e54</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(19)30013-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(19)30013-5</pub-id>
          <pub-id pub-id-type="medline">33323229</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(19)30013-5</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>Maramba</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Newman</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Methods of usability testing in the development of eHealth applications: a scoping review</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <volume>126</volume>
          <fpage>95</fpage>
          <lpage>104</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.03.018</pub-id>
          <pub-id pub-id-type="medline">31029270</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)31318-2</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>Zhou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Setiawan</surname>
              <given-names>IMA</given-names>
            </name>
            <name name-style="western">
              <surname>Saptono</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The mHealth App Usability Questionnaire (MAUQ): development and validation study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>e11500</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/4/e11500/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11500</pub-id>
          <pub-id pub-id-type="medline">30973342</pub-id>
          <pub-id pub-id-type="pii">v7i4e11500</pub-id>
          <pub-id pub-id-type="pmcid">PMC6482399</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>
          <volume>19</volume>
          <issue>3</issue>
          <fpage>e82</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://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-list>
  </back>
</article>
