<?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="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v12i1e55061</article-id>
      <article-id pub-id-type="pmid">38904994</article-id>
      <article-id pub-id-type="doi">10.2196/55061</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Medical Information Protection in Internet Hospital Apps in China: Scale Development and Content Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Buis</surname>
            <given-names>Lorraine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Shi</surname>
            <given-names>Jinming</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lee</surname>
            <given-names>Yura</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Liu</surname>
            <given-names>Shuqing</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Jiang</surname>
            <given-names>Jiayi</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0673-848X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Zheng</surname>
            <given-names>Zexing</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Law School</institution>
            <institution>Central South University</institution>
            <addr-line>Number 932 Lushan South Road</addr-line>
            <addr-line>Yuelu District</addr-line>
            <addr-line>Changsha, 410083</addr-line>
            <country>China</country>
            <phone>86 18718479720</phone>
            <email>xing986@126.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9906-4754</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Law School</institution>
        <institution>Central South University</institution>
        <addr-line>Changsha</addr-line>
        <country>China</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Zexing Zheng <email>xing986@126.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>21</day>
        <month>6</month>
        <year>2024</year>
      </pub-date>
      <volume>12</volume>
      <elocation-id>e55061</elocation-id>
      <history>
        <date date-type="received">
          <day>1</day>
          <month>12</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>17</day>
          <month>1</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>23</day>
          <month>3</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>22</day>
          <month>5</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Jiayi Jiang, Zexing Zheng. Originally published in JMIR mHealth and uHealth (https://mhealth.jmir.org), 21.06.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 JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on https://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://mhealth.jmir.org/2024/1/e55061" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Hospital apps are increasingly being adopted in many countries, especially since the start of the COVID-19 pandemic. Web-based hospitals can provide valuable medical services and enhanced accessibility. However, increasing concerns about personal information (PI) and strict legal compliance requirements necessitate privacy assessments for these platforms. Guided by the theory of contextual integrity, this study investigates the regulatory compliance of privacy policies for internet hospital apps in the mainland of China.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this paper, we aim to evaluate the regulatory compliance of privacy policies of internet hospital apps in the mainland of China and offer recommendations for improvement.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We obtained 59 internet hospital apps on November 7, 2023, and reviewed 52 privacy policies available between November 8 and 23, 2023. We developed a 3-level indicator scale based on the information processing activities, as stipulated in relevant regulations. The scale comprised 7 level-1 indicators, 26 level-2 indicators, and 70 level-3 indicators.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The mean compliance score of the 52 assessed apps was 73/100 (SD 22.4%), revealing a varied spectrum of compliance. Sensitive PI protection compliance (mean 73.9%, SD 24.2%) lagged behind general PI protection (mean 90.4%, SD 14.7%), with only 12 apps requiring separate consent for processing sensitive PI (mean 73.9%, SD 24.2%). Although most apps (n=41, 79%) committed to supervising subcontractors, only a quarter (n=13, 25%) required users’ explicit consent for subcontracting activities. Concerning PI storage security (mean 71.2%, SD 29.3%) and incident management (mean 71.8%, SD 36.6%), half of the assessed apps (n=27, 52%) committed to bear corresponding legal responsibility, whereas fewer than half (n=24, 46%) specified the security level obtained. Most privacy policies stated the PI retention period (n=40, 77%) and instances of PI deletion or anonymization (n=41, 79%), but fewer (n=20, 38.5%) committed to prompt third-party PI deletion. Most apps delineated various individual rights, but only a fraction addressed the rights to obtain copies (n=22, 42%) or to refuse advertisement based on automated decision-making (n=13, 25%). Significant deficiencies remained in regular compliance audits (mean 11.5%, SD 37.8%), impact assessments (mean 13.5%, SD 15.2%), and PI officer disclosure (mean 48.1%, SD 49.3%).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Our analysis revealed both strengths and significant shortcomings in the compliance of internet hospital apps’ privacy policies with relevant regulations. As China continues to implement internet hospital apps, it should ensure the informed consent of users for PI processing activities, enhance compliance levels of relevant privacy policies, and fortify PI protection enforcement across the information processing stages.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>hospital apps</kwd>
        <kwd>privacy policy</kwd>
        <kwd>personal information protection</kwd>
        <kwd>policy evaluation</kwd>
        <kwd>content analysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>The emergence and rapid expansion of hospital apps represents a significant milestone in the evolution of global health care services [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>], especially during the COVID-19 pandemic [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. These digital platforms provide a range of medical services, from digital consultations [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>] to telemedicine [<xref ref-type="bibr" rid="ref10">10</xref>] and digital care management [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Their growing use reflects a trend toward digital health solutions as enhanced, accessible, and cost-efficient health care services [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>However, the rise of hospital apps has been accompanied by substantial concerns regarding patient privacy and data security [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>], as with other mobile health (mHealth) applications [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. The apps’ extensive collection of personal health and medical information, as well as the sensitive nature of that data, suggest a need for comprehensive, rigorously enforced regulations to prevent unauthorized access, misuse, and disclosure. In regions like the United States [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>] and the European Union, similar digital health initiatives have been developed that focus on interoperability, patient-centricity, and adherence to strict data protection regulations, such as the HIPAA (Health Insurance Portability and Accountability Act) in the United States [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>] and the General Data Protection Regulation in the EU [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. Striking a balance between leveraging the benefits of digital health services and ensuring the confidentiality and integrity of patient information remains an ongoing challenge in the industry.</p>
        <p>In China, the response to the evolution of digital health care has been swift, aided by the prevalence of mobile internet [<xref ref-type="bibr" rid="ref24">24</xref>] and the development of mHealth services [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>], as evidenced by the 2014 launch of the country’s first officially approved internet hospital in Guangdong province [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. This milestone, coupled with the enactment of several “internet plus healthcare” policies [<xref ref-type="bibr" rid="ref30">30</xref>], has led to a surge in digital hospital apps, bringing the terms “internet diagnosis” and “internet hospitals” into the national health care context [<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. “Internet diagnosis” encompasses medical services provided in digital form by registered doctors, including consultations for certain common and chronic diseases and “internet plus” family doctor services [<xref ref-type="bibr" rid="ref34">34</xref>]. Hospital apps are divided into two categories: (1) digital extensions of traditional hospitals and (2) stand-alone entities operated by internet enterprises [<xref ref-type="bibr" rid="ref34">34</xref>]. The former involves local doctors and patients, whereas the latter combines the resources of various medical institutions to expand service to patients across different locations.</p>
        <p>Internet hospital apps offer digital consultation, appointment scheduling, diagnosis and treatment of common and chronic diseases, and medical guidance, as well as prescription and delivery of medications and other treatments [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. These apps have significantly enhanced health care by addressing the disparities in resource distribution and access across the mainland of China’s large population [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref36">36</xref>] and improved overall patient experiences by enhancing communication, transparency, and efficiency [<xref ref-type="bibr" rid="ref37">37</xref>]. The COVID-19 pandemic further underscored the efficacy of digital health care providers, which facilitated crucial health care services for prevention and control in the pandemic’s early stages [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref42">42</xref>].</p>
        <p>However, the existing application of these apps presents significant challenges to patient information protection [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. First, sensitive personal information (PI) generated during medical visits, such as biometric and health data, is vulnerable to unauthorized sharing and cyberattacks, which can lead to privacy breaches [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. Second, the complexity of integrating and applying health data weakens individuals’ control over their health information once it transforms into big health care data [<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref49">49</xref>]. Finally, the difficulty of implementing and upholding informed consent is compounded by the lack of unified industry standards and the realities of “algorithmic black boxes,” which often leave individual patients in a relatively disadvantaged position [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>].</p>
        <p>To manage these issues, China has established a regulatory framework to protect PI. Since 2017, the Information Security Technology-Personal Information Specification (PI Specification) has been adopted as a voluntary standard for PI protection practice by all kinds of enterprises in information processing activities [<xref ref-type="bibr" rid="ref52">52</xref>-<xref ref-type="bibr" rid="ref54">54</xref>]. In addition, the Personal Information Protection Law (PIPL), guided by the Chinese Civil Code [<xref ref-type="bibr" rid="ref55">55</xref>] and effective starting November 11, 2021, serves as the nation’s first comprehensive national PI legislation. The PIPL specifies the rights of individuals and the obligations of PI processors [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. The Chinese government has also made a specific commitment to protect personal health information and prohibits illegal processing, trade, or disclosure of personal health information in article 92 of the Law on the Promotion of Basic Medical Care, Hygiene, and Health, enacted on June 1, 2020.</p>
        <p>Internet hospital apps represent a critical intersection of PI and digital technology, which underscores the urgent need for scrutiny of these providers’ privacy policies within a framework that balances self-regulation and governmental oversight [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref59">59</xref>]. Privacy policies delineate how PI processors collect, use, disclose, and manage a customer or client’s data [<xref ref-type="bibr" rid="ref60">60</xref>]. They are also the primary grounds for the transparent data processing requirements mandated by privacy-related regulations [<xref ref-type="bibr" rid="ref61">61</xref>]. Drawing inspiration from contextual integrity (CI) theory, we also investigated how the privacy policies articulated and adhered to the norms of information flow [<xref ref-type="bibr" rid="ref62">62</xref>]. In keeping with Nissenbaum’s [<xref ref-type="bibr" rid="ref63">63</xref>] assertion that privacy “is preserved when informational norms are respected and violated when informational norms are breached,” we set the basis of evaluation with a focus on the norms and values that govern appropriate flows of PI.</p>
        <p>Previous research on privacy compliance of mHealth apps in different countries has identified gaps between rules for privacy protection and the apps’ implementations in various aspects, such as lack of complete privacy policies, lack of informed consent, and insufficient protection of sensitive data [<xref ref-type="bibr" rid="ref64">64</xref>-<xref ref-type="bibr" rid="ref73">73</xref>]. Such investigations have also raised concerns about internet hospital apps’ uneven design quality and the challenges in minimizing users’ cognitive load while ensuring information security [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]. However, these studies have not thoroughly examined web-based hospitals’ compliance with China’s comprehensive legal framework for PI protection.</p>
        <p>This study uses a legal framework to assess the compliance of internet hospital apps’ privacy policies with China’s PI-related regulations. The Methods section elaborates on the collection and selection of sample apps, describes the development of an evaluation scale based on relevant policy documents, and outlines the procedures for app assessment and scoring. In the Results section, we present the compliance scores of sample apps. The Discussion section contextualizes these results within the broader landscape of mHealth app privacy compliance, underscoring the importance of legal compliance in the evolving digital health landscape.</p>
      </sec>
      <sec>
        <title>Objective</title>
        <p>In this study, we aimed to (1) collect the privacy policies of internet hospital apps developed for users in the mainland of China, (2) develop a scale based on the provisions stipulated in the PIPL, PI Specification, and rules of the hospitals, (3) assess the compliance of the privacy policies within the regulatory framework of PI protection, and (4) offer recommendations for improving the legal compliance of internet hospital apps’ privacy policies to enhance PI protection in the evolving landscape of mHealth innovation. This study contributes to the global discussion on balanced policies for PI protection in digital health initiatives in the postpandemic era and provides insights for policymakers, hospital app providers, and users across different countries while highlighting the importance of improving legal compliance and strengthening enforcement.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>We conducted a content analysis of the privacy policies of internet hospital apps available in the Apple App Store in the mainland of China and evaluated their compliance with the PIPL, PI Specification, and hospital app rules. Drawing from CI theory, we considered the adherence of internet hospital apps’ privacy policies to PI norms as essential to PI protection.</p>
      </sec>
      <sec>
        <title>App Selection and Inclusion Criteria</title>
        <p>In this study, we focused on the privacy policies of internet hospital apps available in the Apple App Store and tailored for the market of Chinese mainland. To identify relevant apps, we used the keyword “internet hospital” (<italic>hu lian wang yi yuan</italic> in Chinese) to search on Diandian (<italic>Dian Shu Ju</italic> in Chinese), a prominent mobile data analytics platform in China. We conducted the search on November 7, 2023.</p>
        <p>The apps included in the sample fell under the following definitions: (1) apps or platforms specifically developed to provide a range of hospital app services, and (2) apps intended for use by the general population rather than health care professionals. Excluded apps fit the following: (1) apps designed for health care professionals managing internal hospital operations, and (2) apps with scope or functionality unrelated to hospital app services, such as those dedicated to health insurance, maintaining a healthy lifestyle, or health education and popular science. The initial search resulted in a total of 231 apps, out of which 59 met the inclusion criteria and were included in the final analysis upon review (<xref rid="figure1" ref-type="fig">Figure 1</xref>). We obtained and reviewed the full text of corresponding privacy policies as text files or screenshots from the sample apps between November 8 and 23, 2023.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Filtering procedure for the selection and inclusion of hospital apps.</p>
          </caption>
          <graphic xlink:href="mhealth_v12i1e55061_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Development of the Compliance Evaluation Scale</title>
        <sec>
          <title>Overview</title>
          <p>We systematically developed a compliance evaluation scale to assess the privacy policies of internet hospital apps against the PIPL, PI Specification (GB/<italic>t</italic> 35273-2020), and the Rules for Regulation of Internet Diagnosis and Treatment Management (for Trial Implementation). This process entailed the following sections.</p>
        </sec>
        <sec>
          <title>Comprehensive Review</title>
          <p>First, we obtained and meticulously reviewed the full text of the PIPL, PI Specification, and the aforementioned rules to understand the comprehensive regulatory framework governing PI protection in hospital apps.</p>
        </sec>
        <sec>
          <title>Indicator Development</title>
          <p>Based on the information processing activities delineated in these policy documents, we identified level-1 evaluation indicators encompassing critical processing stages such as PI collection and usage; PI storage and protection; PI sharing, transfer, disclosure, and transmission; PI deletion; individual rights; and PI processor duties. In addition, we introduced “general attributes” as an additional level-1 indicator to evaluate the overall transparency and ongoing maintenance efforts.</p>
        </sec>
        <sec>
          <title>Indicator Elaboration</title>
          <p>We then translated the specific chapters and clauses of these policy documents into a more granular set of 26 level-2 indicators and 70 level-3 indicators, which provided a detailed framework for our evaluation. Each level-2 indicator represented a crucial component within the respective PI processing stage—our level-1 indicators. For example, in the stage of PI collection and usage, we followed different rules for general and sensitive PI as stipulated in the PIPL, and further developed 2 level-2 indicators to evaluate the collection and usage of general PI and sensitive PI. Moreover, we established level-3 indicators to assess the specific compliance requirements as detailed under each level-2 indicator. For example, concerning the collection and usage of sensitive PI, we identified 7 level-3 indicators according to the PIPL, which included: highlighting sensitive PI, stating the specific purpose, clarifying the sufficient necessity, implementing stringent protective measures, communicating the implications of processing sensitive PI, obtaining separate explicit consent for processing sensitive PI, and requiring explicit consent for processing PI of minors.</p>
        </sec>
        <sec>
          <title>Operational Definitions and Examples</title>
          <p>To ensure clarity and consistency in our assessment and support the application of our evaluation criteria, we have included brief explanations, example sentences, and references to the relevant provisions of the policy documents for all the level-3 indicators in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        </sec>
      </sec>
      <sec>
        <title>Scoring and Evaluation Procedure</title>
        <p>We adopted a binary scoring system for level-3 indicators, awarding a score of 1 for privacy policies that adequately addressed a given indicator and 0 for those that did not. This allowed us to calculate the compliance rate for each level-3 indicator based on the proportion of policies scoring “1” from our app sample. We then calculated the scoring rate for each level-2 indicator as the arithmetic mean of the scoring rates for its associated level-3 indicators. Similarly, we determined the compliance rate for the level-1 indicators as the mean of the scoring rates of the corresponding level-2 indicators, which reflects the overall compliance of each app in specific stages of the information processing activities. The overall compliance of each app’s privacy policy was quantified by aggregating the scores of all level-3 indicators and converting this total into a percentage to denote the app’s compliance level.</p>
        <p>To ensure the reliability of our evaluation, 2 independent raters (JJ and ZZ) were engaged to assess the privacy policies of all 59 internet hospital apps between November 8 and 24, 2023. To gauge interrater reliability, both raters independently evaluated a randomly selected subset of 20 apps (34% of the total), achieving an intraclass correlation coefficient of 0.986 (<italic>P</italic>&lt;.001), indicating nearly perfect agreement. Following this assessment, the raters convened to discuss score discrepancies in their initial evaluations. After this, the raters divided the remainder of the apps equally and applied the unified standards to ensure scoring consistency.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Sample Collection</title>
        <p>We accessed 59 internet hospital apps available in the Apple App Store for Chinese mainland users by registering as users with our own identity documents and mobile phone numbers. We obtained the full text of 52 privacy policies. A small but significant percentage of apps (7/59, 12%) altogether lacked a separate privacy policy, a fundamental requirement for safeguarding PI. This absence is a critical oversight and represents direct noncompliance with established PI protection laws, suggesting an urgent need for these apps to develop and implement comprehensive privacy policies.</p>
      </sec>
      <sec>
        <title>Compliance Evaluation</title>
        <p>The overall compliance landscape among the 52 assessed privacy policies was mixed. The mean compliance score of all policies was 73 of a possible 100 (SD 22.4%). Moreover, 36 apps (69%) surpassed the mean score, whereas 16 apps (31%) fell below.</p>
        <p>The evaluation results for level-1 and level-2 indicators are listed in <xref rid="figure2" ref-type="fig">Figure 2</xref> and <xref ref-type="table" rid="table1">Table 1</xref>. Level-1 indicators were ranked by score from highest to lowest, as follows: general attributes (mean 92.1%, SD 16.5%); PI collection and usage (mean 81.5%, SD 17.9%); PI sharing, transfer, disclosure, and transmission (mean 75%, SD 25.2%); PI storage and protection (mean 71.5%, SD 30.7%); individual rights (mean 68.4%, SD 31.5%); PI deletion (mean 64.7%, SD 34.8%); and PI processor duties (mean 59.4%, SD 28.4%). The names and evaluation results for each app are listed in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
        <p>The privacy policies’ general attributes (mean 92.1%, SD 16.5%) scored high, indicating effective efforts in transparency and maintenance. For level-2 indicators, PI processors and services recorded an impressive compliance rate of 95.2% (SD 20.2%), indicating a majority of the privacy policies effectively identified the parties responsible for processing PI and providing services. Policy transparency was a standout area, with a perfect score of 100% (SD 0%) reflecting the apps’ commitment to clear and open communication with users. Policy maintenance also emerged as a strong suit, scoring 84.6% (SD 30.3%). This suggests a significant proportion of apps were proactive in updating their privacy policies, a vital aspect of best practices following the implementation of the PIPL. Specifically, 25 apps updated their privacy policies after the PIPL came into force. However, a concerning 12 apps failed to mention either the effective or updated date of their policies, whereas 15 updated their privacy policies before the PIPL came into effect.</p>
        <p>Regulations for a description of the collection and usage of general PI had an average compliance rate of 90.4% (SD 14.7%). This indicates the majority of internet hospital apps were conscientious in describing how general PI is collected and used within their service functions. Our evaluation found all the reviewed privacy policies specified the purpose and methods of collecting and using PI, demonstrating a high level of transparency. Additionally, a substantial 90% (n=47) of apps provided a list of the types of PI collected, while 83% (n=43) of the policies clarified the consequences of not providing PI. In terms of differentiating between essential and nonessential PI for services, compliance stood at 69% (n=36). Although significant clarity was currently provided, an opportunity still remained for apps to enhance user understanding of the purpose and optional nature of PI collection.</p>
        <p>Meanwhile, the scoring rate of collection and usage of sensitive PI was lower (mean 73.9%, SD 24.2%). We observed strong compliance rates for describing specific purposes (n=48, 92%), protective measures (n=46, 88.5%), implications (n=43, 83%), and necessity (n=41, 79%) of processing sensitive PI. Most assessed apps required explicit consent for processing minors’ PI (n=43, 83%). However, the requirement to obtain separate explicit consent for processing sensitive PI revealed a significant gap, with only 23% (n=12) of apps complying.</p>
        <p>In the PI storage and protection stage (mean 71.5%, SD 30.7), the scoring of level-2 indicators varied slightly. The compliance rate of storage security was 71.2% (SD 29.3%). Most apps explained potential security risks (n=46, 88.5%) and organizational management measures. Fewer than half (n=24, 46%) outlined the compulsory level of technical security measures. As for security incidents (mean 71.8%, SD 36.6%), although a significant portion of apps committed to notifying users (n=43, 83%) and reporting security incidents (n=42, 81%), just over half of PI processors (n=27, 52%) committed to assuming legal responsibility in the event of such an incident.</p>
        <p>In the stage of PI sharing, transfer, disclosure, and transmission (mean 75%, SD 25.2%), the scoring rate of level-2 indicators varied substantially. For public disclosure (mean 93.3%, SD 24.1%), we observed high compliance in specifying conditions for potential public PI disclosure (n=49, 94%) and requiring separate consent for such practices (n=48, 92%). These rates indicated a high degree of transparency and respect for user consent for public disclosure. As for the compliance rate of PI sharing and transfer (mean 77.5%, SD 30%), most privacy policies introduced information about PI recipients (n=37, 71%), the types of PI transferred (n=38, 73%), and the safety precautions adopted in advance (n=37, 71%). In addition, most apps explained the purposes (n=44, 85%) and methods (n=44, 85%) of PI transfer, described the rules governing PI transfer during specific events (n=37, 71%), and required separate consent for sharing or transferring PI (n=44, 85%). Regarding cross-border transmission (mean 71.2%, SD 43.1%), most apps specified PI storage locations (n=39, 75%), whereas fewer mentioned compliance with relevant cross-border transmission laws (n=35, 67%). However, the compliance rate of subcontracting PI processing was low (mean 51.9%, SD 27.7%). Although most apps committed to supervising the subcontracted PI processing activities (n=41, 79%), only a quarter (n=13, 25%) required separate consent for these activities.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Compliance evaluation scores of internet hospital apps for level-1 indicators. PI: personal information.</p>
          </caption>
          <graphic xlink:href="mhealth_v12i1e55061_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Compliance evaluation scores of internet hospital apps for level-2 indicators.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="700"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td>Evaluation results on level-2 indicators</td>
                <td>Compliance rate (%), mean (SD)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>PI<sup>a</sup> processors and service</td>
                <td>95.2 (20)</td>
              </tr>
              <tr valign="top">
                <td>Policy transparency</td>
                <td>100 (0)</td>
              </tr>
              <tr valign="top">
                <td>Policy maintenance</td>
                <td>84.6 (30)</td>
              </tr>
              <tr valign="top">
                <td>Collection and use of general PI in service functions</td>
                <td>90.4 (15)</td>
              </tr>
              <tr valign="top">
                <td>Collection and use of sensitive PI in service functions</td>
                <td>73.9 (24)</td>
              </tr>
              <tr valign="top">
                <td>Storage security</td>
                <td>71.2 (29)</td>
              </tr>
              <tr valign="top">
                <td>Security incidents</td>
                <td>71.8 (37)</td>
              </tr>
              <tr valign="top">
                <td>Subcontracting of PI processing</td>
                <td>51.9 (28)</td>
              </tr>
              <tr valign="top">
                <td>PI sharing and transfer</td>
                <td>77.5 (30)</td>
              </tr>
              <tr valign="top">
                <td>Public disclosure</td>
                <td>93.3 (24)</td>
              </tr>
              <tr valign="top">
                <td>Cross-border transmission</td>
                <td>71.2 (43)</td>
              </tr>
              <tr valign="top">
                <td>Retention period</td>
                <td>76.9 (42)</td>
              </tr>
              <tr valign="top">
                <td>Deletion and cessation</td>
                <td>58.7 (38)</td>
              </tr>
              <tr valign="top">
                <td>Inquiry of PI</td>
                <td>80.8 (39)</td>
              </tr>
              <tr valign="top">
                <td>Obtain copies of PI</td>
                <td>42.3 (49)</td>
              </tr>
              <tr valign="top">
                <td>Correction of PI</td>
                <td>80.8 (39)</td>
              </tr>
              <tr valign="top">
                <td>Deletion of PI</td>
                <td>80.8 (39)</td>
              </tr>
              <tr valign="top">
                <td>Explanation regarding PI processing</td>
                <td>82.7 (38)</td>
              </tr>
              <tr valign="top">
                <td>Consent withdrawal</td>
                <td>51.9 (34)</td>
              </tr>
              <tr valign="top">
                <td>Deregistration</td>
                <td>76.9 (42)</td>
              </tr>
              <tr valign="top">
                <td>Consent exception scenarios</td>
                <td>67.3 (46)</td>
              </tr>
              <tr valign="top">
                <td>PI protection officer disclosure</td>
                <td>48.1 (49)</td>
              </tr>
              <tr valign="top">
                <td>Compliance audits</td>
                <td>11.5 (38)</td>
              </tr>
              <tr valign="top">
                <td>Impact assessment procedures</td>
                <td>13.5 (15)</td>
              </tr>
              <tr valign="top">
                <td>Request management</td>
                <td>72.9 (36)</td>
              </tr>
              <tr valign="top">
                <td>Complaint management</td>
                <td>64.7 (40)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>PI: personal information.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>In the stage of PI deletion (mean 64.7%, SD 34.8%), most privacy policies stated the PI retention period (mean 76.9%, SD 42.1%). In contrast, the scoring rate for deletion and cessation was lower (mean 58.7%, SD 37.6%). Although most apps committed to PI deletion or anonymization after a retention period (n=41, 79%), only 20 apps (38.5%) required third parties to delete PI or cease processing after the same period.</p>
        <p>Concerning individual rights (mean 68.4%, SD 31.5%), most apps explained individuals’ various rights effectively, including the rights to inquire about (n=42, 81%), correct (n=42, 81%), and delete PI (n=42, 81%); cancel the account (n=40, 77%); withdraw or modify consent (n=41, 79%); and request an explanation of the privacy policy (n=43, 83%). However, only 22 apps recognized the right of users to obtain copies of their PI (n=22, 42%) and only 13 explained the right to refuse business marketing using automated decision-making. A majority of apps (n=35, 67%) listed exceptions for obtaining consent as provided by applicable laws or administrative regulations.</p>
        <p>Concerning PI processor duties, we found a compliance rate of 59.3% (SD 28.4%). Fewer than half of the apps appointed a PI officer and disclosed their information in their privacy policies (n=25, 48%). A quarter of the apps (n=13, 25%) presented impact assessment procedures, whereas 11.5% of apps (n=6) engaged in compliance audits. Many apps provided methods for individuals to inquire about (n=41, 79%), correct (n=41, 79%), and delete PI (n=41, 79%); clarify PI processing rules (n=43, 83%); cancel their account (n=41, 79%); withdraw or modify consent (n=40, 79%); and understand limits on the use of automated decision-making (n=29, 56%). However, fewer than half of all the studied apps provided methods to obtain copies of PI (n=21, 40%). Although many apps provided a means for lodging complaints by disclosing contact information (n=37, 71%), fewer committed to addressing these complaints within the stated time limits or explained the methods of dispute resolution (n=32, 61.5%).</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>We developed the evaluation scale to align with the characteristics of internet hospital apps, drawing from the essential CI parameters of context, attributes, actors, and transmission principles. We set the context in the realms of internet diagnosis and hospitals and categorized the attributes of PI, emphasizing the distinction between sensitive and general PI processing activities. Actors encompassed both app users and PI processors, including third-party entities outlined in the privacy policies. We translated the transmission principles of lawfulness, legitimacy, necessity, good faith, minimal impact, openness, and transparency into indicators that aligned with PI-related regulations.</p>
        <p>Our review of 52 privacy policies from internet hospital apps in the mainland of China reveals a varied spectrum of compliance. The compliance score of the apps’ privacy policies varied (mean 73%, SD 22.4%), with some apps demonstrating robust compliance, whereas others fell short. This suggests a need for enhanced regulatory oversight and standardized practices. We also identified variations in legal compliance across different stages of the information processing activities, as shown in <xref rid="figure2" ref-type="fig">Figure 2</xref> and <xref ref-type="table" rid="table1">Table 1</xref>. This underscores the varying application of PI-related regulations in digital hospital apps, raising concerns about users’ potential exposure to privacy risks.</p>
        <p>First, our analysis indicates a notable gap between compliance rates for sensitive PI protection (mean 73.9%, SD 24.2%) and general PI protection (mean 90.4%, SD 14.7%), raising significant concerns regarding the provision of stringent safeguards for sensitive PI [<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>]. This gap is especially concerning given the PIPL (specifically section 2, chapter II) mandates special protection for sensitive PI. The inadequate compliance in this area also potentially diminishes users’ awareness and understanding of the risks associated with the processing of their sensitive PI. Article 28 of the PIPL stipulates that PI processors may only process sensitive PI with a specified purpose, sufficient necessity, and stringent protective measures. Alarmingly, the practice of seeking explicit consent for processing sensitive PI—a fundamental requirement for lawful processing and respecting user rights—is not as widespread as it should be, implying a pervasive reliance on blanket consent strategies among digital hospital apps. These findings also suggest privacy policies often fail to provide the necessary clarity for users to understand the distinctions between various types of PI and the specific reasons for their processing. Enhancing privacy policies to offer more detailed explanations would not only align with the PIPL’s mandate but also elevate the standard of user empowerment, enabling individuals to make informed decisions about their PI.</p>
        <p>Second, the fact that many apps did not fully elucidate the role of third-party subcontractors or the conditions of PI sharing, transferring, or deletion in privacy policies may hinder users’ understanding of the destinations and protections of their PI, which could consequently affect their trust and the integrity of their informed consent [<xref ref-type="bibr" rid="ref78">78</xref>]. The lack of detailed disclosure about PI processors (including involved third parties) and protocols for PI sharing and transfer, particularly in critical scenarios like mergers or acquisitions, underscores a disconnect between regulatory intentions and the operational realities of data governance within these digital platforms. In addition, the apps’ handling of PI deletion remains challenging and becomes more complex when third-party subcontracting activities are involved [<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref80">80</xref>]. It is particularly problematic when privacy policies do not clearly communicate how these third parties are managed or if they are held to the same rigorous standards of PI protection as the primary PI processors.</p>
        <p>Third, we found users’ rights to inquire about, correct, and delete personal data, along with other user-centric controls, were generally recognized within the apps’ privacy policies. The rights of individuals to manage their PI are paramount in the domain of digital health [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>]. However, a deeper look into the specifics of these policies uncovers a gap in the acknowledgment of users’ right to obtain copies of their own PI, a provision stipulated in article 45 of the PIPL. More concerning is the fact that only a quarter of the apps addressed the right to refuse business marketing through automated decision-making, even though article 24 of the PIPL calls for transparency, fairness, and the right to receive an explanation and be able to opt out of such marketing. A lack of explanation of these crucial rights might inadvertently hinder app users from fully realizing their entitlements under PI protection norms.</p>
        <p>Finally, our findings reveal inadequacies in how internet hospital apps execute PI-related responsibilities, even though the roles and responsibilities of PI processors are central to the protection of PI [<xref ref-type="bibr" rid="ref83">83</xref>]. The absence of clear methods for users to obtain copies of their PI or comprehensive explanations of automated decision-making processes stands in stark contrast to the protective intent of the PIPL. Moreover, the relatively low scores of PI protection officer disclosure, compliance audits, and impact assessment procedures suggest a concerning lapse in institutional oversight. Such critical mechanisms are essential for the proactive identification of vulnerabilities and agile adaptation to emergent technological threats.</p>
      </sec>
      <sec>
        <title>Recommendations</title>
        <p>Since the creation of China’s first internet hospital, the nation’s government has shown commendable support for the industry in its policy making [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]. China’s “internet plus” policy paves the way for a promising future for internet hospital apps beyond their role in the prevention and control of the COVID-19 pandemic [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref86">86</xref>]. Constructing health and medical big data requires the aggregation and integration of personal health care information, so it is essential to address PI risks posed by big data technology. The public-interest nature of health and medical information in areas like infectious disease control, medical research, and public safety further underscores the importance of the reasonable use and sufficient protection of PI [<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref88">88</xref>]. However, the rapidly growing sector of internet diagnosis and hospitals still grapples with gaps in patient information protection [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref89">89</xref>], necessitating a balanced approach that judiciously considers both the advantages of processing PI and the inherent challenges associated with PI protection [<xref ref-type="bibr" rid="ref90">90</xref>].</p>
        <p>There is a pressing need to standardize obtaining informed consent in internet hospital services. The prevalent absence of explicit consent, particularly in subcontracting processes, raises significant privacy concerns, ranging from unauthorized data collection to inadequate user disclosure and excessive data harvesting [<xref ref-type="bibr" rid="ref91">91</xref>-<xref ref-type="bibr" rid="ref94">94</xref>]. Individuals often find their control over their own health information reduced, especially as it becomes integrated into big data [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. Drawing on CI’s focus on the principles of actors and transmission, it is essential to adopt a dynamic consent model to reinforce granular control over PI. Implementing robust privacy impact assessments and creating transparent platforms for sharing privacy policies can further enhance public trust [<xref ref-type="bibr" rid="ref50">50</xref>].</p>
        <p>Improving the compliance of privacy policies and their enforcement mechanisms requires adherence to CI principles across the information processing stages. This includes ensuring clarity in the collection and use of PI, enhancing protection for PI storage, and promoting transparency in the sharing, transfer, and deletion of PI. Emphasizing the internet diagnosis and hospitals’ context and the attributes of PI can help in distinguishing between sensitive and general PI, ensuring PI processing activities are aligned with users’ needs and rights. Expanding acknowledgment of individual rights concerning users’ PI, a core aspect of CI, involves not only recognizing users’ rights to access, correct, and delete their PI, but also ensuring they are adequately informed about the purposes and methods of PI processing. This can be achieved through regular audits, impact assessments, and the appointment of PI protection officers, which ensure internet hospital apps not only comply with legal standards but also respect ethical digital health practices.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study, while comprehensive in scope, encountered several limitations common in privacy policy analyses. First, our methodology primarily relied on content analysis of privacy policies, which may not fully capture the actual practices and implementation effectiveness of these policies. There is often a gap between what is stated in policy documents and how those policies are executed. Thus, the findings may not accurately reflect the on-the-ground application of apps’ privacy standards. Second, this study was confined to the examination of publicly available privacy policies, without delving into the apps’ technical backend and data-handling processes. This limitation means we could not assess the real-world effectiveness of the stated privacy measures or the security of the apps’ data management systems. Future researchers could benefit from incorporating technical audits, user-experience studies, and automated analysis, which could provide a more holistic and dynamic view of privacy protection in internet hospital apps.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Our comprehensive evaluation of privacy policies from 52 internet hospital apps in the mainland of China highlights a landscape marked by varied compliance with relevant regulations. Despite some apps demonstrating adherence to legal standards, notable gaps persist, especially in protecting sensitive PI, obtaining informed consent, and clearly delineating individual rights. Inspired by CI theory, in this study, we underscore the urgent need for enhanced regulatory oversight, standardized privacy practices, and a commitment to user empowerment through transparent, comprehensive privacy policies. Addressing these challenges is critical, not only for protecting PI but also for fostering trust and facilitating the sustainable growth of digital health care services in China and other countries.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>This chart provides the 3-level indicator scale developed to evaluate the compliance status of the sample apps.</p>
        <media xlink:href="mhealth_v12i1e55061_app1.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 26 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>This chart provides a list of 59 internet hospital apps that met the inclusion criteria.</p>
        <media xlink:href="mhealth_v12i1e55061_app2.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 18 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CI</term>
          <def>
            <p>contextual integrity</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">PI</term>
          <def>
            <p>personal information</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">PIPL</term>
          <def>
            <p>Personal Information Protection Law</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The research is funded by the Social Science Fund Projects of Hunan Province (23YBQ003 and 23YBQ011).</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="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mosa</surname>
              <given-names>ASM</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Sheets</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of healthcare applications for smartphones</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2012</year>
          <volume>12</volume>
          <fpage>67</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-12-67"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-12-67</pub-id>
          <pub-id pub-id-type="medline">22781312</pub-id>
          <pub-id pub-id-type="pii">1472-6947-12-67</pub-id>
          <pub-id pub-id-type="pmcid">PMC3534499</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weinstein</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Joseph</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Erps</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Holcomb</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barker</surname>
              <given-names>GP</given-names>
            </name>
            <name name-style="western">
              <surname>Krupinski</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine, telehealth, and mobile health applications that work: opportunities and barriers</article-title>
          <source>Am J Med</source>
          <year>2014</year>
          <volume>127</volume>
          <issue>3</issue>
          <fpage>183</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1016/j.amjmed.2013.09.032</pub-id>
          <pub-id pub-id-type="medline">24384059</pub-id>
          <pub-id pub-id-type="pii">S0002-9343(13)00919-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Opportunities and challenges for contactless healthcare services in the post-COVID-19 era</article-title>
          <source>Technol Forecast Soc Change</source>
          <year>2021</year>
          <volume>167</volume>
          <fpage>120712</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33654330"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.techfore.2021.120712</pub-id>
          <pub-id pub-id-type="medline">33654330</pub-id>
          <pub-id pub-id-type="pii">S0040-1625(21)00144-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC7908833</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kondylakis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Logothetidis</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Triantafyllidis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kalamaras</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Votis</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tzovaras</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 mobile apps: a systematic review of the literature</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>12</issue>
          <fpage>e23170</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/12/e23170/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23170</pub-id>
          <pub-id pub-id-type="medline">33197234</pub-id>
          <pub-id pub-id-type="pii">v22i12e23170</pub-id>
          <pub-id pub-id-type="pmcid">PMC7732358</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bokolo</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Application of telemedicine and eHealth technology for clinical services in response to COVID‑19 pandemic</article-title>
          <source>Health Technol (Berl)</source>
          <year>2021</year>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>359</fpage>
          <lpage>366</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33469474"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12553-020-00516-4</pub-id>
          <pub-id pub-id-type="medline">33469474</pub-id>
          <pub-id pub-id-type="pii">516</pub-id>
          <pub-id pub-id-type="pmcid">PMC7808733</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kumari</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Yadav</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Hajela</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>GK</given-names>
            </name>
          </person-group>
          <article-title>Mobile technology: a tool for healthcare and a boon in pandemic</article-title>
          <source>J Family Med Prim Care</source>
          <year>2022</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>43</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35309626"/>
          </comment>
          <pub-id pub-id-type="doi">10.4103/jfmpc.jfmpc_1114_21</pub-id>
          <pub-id pub-id-type="medline">35309626</pub-id>
          <pub-id pub-id-type="pii">JFMPC-11-37</pub-id>
          <pub-id pub-id-type="pmcid">PMC8930125</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sitammagari</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kowalkowski</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kearns</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Batchelor</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rivet</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hole</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>McCreary</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Neuwirth</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>McWilliams</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Insights from rapid deployment of a "Virtual Hospital" as standard care during the COVID-19 pandemic</article-title>
          <source>Ann Intern Med</source>
          <year>2021</year>
          <volume>174</volume>
          <issue>2</issue>
          <fpage>192</fpage>
          <lpage>199</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/abs/10.7326/M20-4076?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M20-4076</pub-id>
          <pub-id pub-id-type="medline">33175567</pub-id>
          <pub-id pub-id-type="pmcid">PMC7711652</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vijayaraghavan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Byrne</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell-Richards</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ramoutar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gutteridge</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hodkinson</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Collard</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Virtual online consultations: advantages and limitations (VOCAL) study</article-title>
          <source>BMJ Open</source>
          <year>2016</year>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>e009388</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&amp;pmid=26826147"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2015-009388</pub-id>
          <pub-id pub-id-type="medline">26826147</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2015-009388</pub-id>
          <pub-id pub-id-type="pmcid">PMC4735312</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>Car</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Koh</surname>
              <given-names>GCH</given-names>
            </name>
            <name name-style="western">
              <surname>Foong</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>CJ</given-names>
            </name>
          </person-group>
          <article-title>Video consultations in primary and specialist care during the covid-19 pandemic and beyond</article-title>
          <source>BMJ</source>
          <year>2020</year>
          <volume>371</volume>
          <fpage>m3945</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.m3945</pub-id>
          <pub-id pub-id-type="medline">33082127</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leite</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hodgkinson</surname>
              <given-names>IR</given-names>
            </name>
            <name name-style="western">
              <surname>Gruber</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>New development: ‘healing at a distance’—telemedicine and COVID-19</article-title>
          <source>Public Money Manage</source>
          <year>2020</year>
          <volume>40</volume>
          <issue>6</issue>
          <fpage>483</fpage>
          <lpage>485</lpage>
          <pub-id pub-id-type="doi">10.1080/09540962.2020.1748855</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Bokolo Anthony Jnr</collab>
          </person-group>
          <article-title>Use of telemedicine and virtual care for remote treatment in response to COVID-19 pandemic</article-title>
          <source>J Med Syst</source>
          <year>2020</year>
          <volume>44</volume>
          <issue>7</issue>
          <fpage>132</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32542571"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-020-01596-5</pub-id>
          <pub-id pub-id-type="medline">32542571</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-020-01596-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7294764</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haleem</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Javaid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Suman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine for healthcare: capabilities, features, barriers, and applications</article-title>
          <source>Sens Int</source>
          <year>2021</year>
          <volume>2</volume>
          <fpage>100117</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2666-3511(21)00038-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.sintl.2021.100117</pub-id>
          <pub-id pub-id-type="medline">34806053</pub-id>
          <pub-id pub-id-type="pii">S2666-3511(21)00038-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC8590973</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>Rowland</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzgerald</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Holme</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McGregor</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>What is the clinical value of mHealth for patients?</article-title>
          <source>NPJ Digit Med</source>
          <year>2020</year>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0206-x"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0206-x</pub-id>
          <pub-id pub-id-type="medline">31970289</pub-id>
          <pub-id pub-id-type="pii">206</pub-id>
          <pub-id pub-id-type="pmcid">PMC6957674</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>Lupton</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jutel</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>'It's like having a physician in your pocket!' a critical analysis of self-diagnosis smartphone apps</article-title>
          <source>Soc Sci Med</source>
          <year>2015</year>
          <volume>133</volume>
          <fpage>128</fpage>
          <lpage>135</lpage>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2015.04.004</pub-id>
          <pub-id pub-id-type="medline">25864149</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(15)00224-5</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>Flaherty</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Digital diagnosis: privacy and the regulation of mobile phone health applications</article-title>
          <source>Am J Law Med</source>
          <year>2014</year>
          <volume>40</volume>
          <issue>4</issue>
          <fpage>416</fpage>
          <lpage>441</lpage>
          <pub-id pub-id-type="medline">27530051</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>Tangari</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ikram</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ijaz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kaafar</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Berkovsky</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Mobile health and privacy: cross sectional study</article-title>
          <source>BMJ</source>
          <year>2021</year>
          <volume>373</volume>
          <fpage>n1248</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=34135009"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.n1248</pub-id>
          <pub-id pub-id-type="medline">34135009</pub-id>
          <pub-id pub-id-type="pmcid">PMC8207561</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>Martínez-Pérez</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>de</surname>
              <given-names>LTI</given-names>
            </name>
            <name name-style="western">
              <surname>López-Coronado</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Privacy and security in mobile health apps: a review and recommendations</article-title>
          <source>J Med Syst</source>
          <year>2015</year>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>181</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-014-0181-3</pub-id>
          <pub-id pub-id-type="medline">25486895</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>Yu</surname>
              <given-names>SWY</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ricks</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Bennet</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Oriol</surname>
              <given-names>NE</given-names>
            </name>
          </person-group>
          <article-title>The scope and impact of mobile health clinics in the United States: a literature review</article-title>
          <source>Int J Equity Health</source>
          <year>2017</year>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>178</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://equityhealthj.biomedcentral.com/articles/10.1186/s12939-017-0671-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12939-017-0671-2</pub-id>
          <pub-id pub-id-type="medline">28982362</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12939-017-0671-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC5629787</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kichloo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Albosta</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dettloff</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wani</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>El-Amir</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Aljadah</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chakinala</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Kanugula</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Solanki</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chugh</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine, the current COVID-19 pandemic and the future: a narrative review and perspectives moving forward in the USA</article-title>
          <source>Fam Med Community Health</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>e000530</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://fmch.bmj.com/lookup/pmidlookup?view=long&amp;pmid=32816942"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/fmch-2020-000530</pub-id>
          <pub-id pub-id-type="medline">32816942</pub-id>
          <pub-id pub-id-type="pii">fmch-2020-000530</pub-id>
          <pub-id pub-id-type="pmcid">PMC7437610</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Glenn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Monteith</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Privacy in the digital world: medical and health data outside of HIPAA protections</article-title>
          <source>Curr Psychiatry Rep</source>
          <year>2014</year>
          <volume>16</volume>
          <issue>11</issue>
          <fpage>494</fpage>
          <pub-id pub-id-type="doi">10.1007/s11920-014-0494-4</pub-id>
          <pub-id pub-id-type="medline">25218603</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>Soumitra</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Hyunmin</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Oluwaseyi</surname>
              <given-names>OI</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wyant</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Kedia</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>CF</given-names>
            </name>
            <name name-style="western">
              <surname>Dasgupta</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Privacy and security issues in mobile health: current research and future directions</article-title>
          <source>Health Policy Technol</source>
          <year>2017</year>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>188</fpage>
          <lpage>191</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.hlpt.2017.01.004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2017.01.004</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>Yuan</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The policy effect of the General Data Protection Regulation (GDPR) on the digital public health sector in the European Union: an empirical investigation</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2019</year>
          <volume>16</volume>
          <issue>6</issue>
          <fpage>1070</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph16061070"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph16061070</pub-id>
          <pub-id pub-id-type="medline">30934648</pub-id>
          <pub-id pub-id-type="pii">ijerph16061070</pub-id>
          <pub-id pub-id-type="pmcid">PMC6466053</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>Rumbold</surname>
              <given-names>JMM</given-names>
            </name>
            <name name-style="western">
              <surname>Pierscionek</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The effect of the general data protection regulation on medical research</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <volume>19</volume>
          <issue>2</issue>
          <fpage>e47</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/2/e47/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7108</pub-id>
          <pub-id pub-id-type="medline">28235748</pub-id>
          <pub-id pub-id-type="pii">v19i2e47</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>The 52nd statistical report on China's internet development</article-title>
          <source>China Internet Network Information Center</source>
          <year>2023</year>
          <access-date>2024-05-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnnic.com.cn/IDR/ReportDownloads/202311/P020231121355042476714.pdf">https://www.cnnic.com.cn/IDR/ReportDownloads/202311/P020231121355042476714.pdf</ext-link>
          </comment>
        </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>Hsu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>YM</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>HT</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>ZR</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>The top Chinese mobile health apps: a systematic investigation</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <volume>18</volume>
          <issue>8</issue>
          <fpage>e222</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2016/8/e222/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5955</pub-id>
          <pub-id pub-id-type="medline">27573724</pub-id>
          <pub-id pub-id-type="pii">v18i8e222</pub-id>
          <pub-id pub-id-type="pmcid">PMC5020314</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>Lv</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Qi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Qiu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Using mobile apps for health management: a new health care mode in China</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2019</year>
          <volume>7</volume>
          <issue>6</issue>
          <fpage>e10299</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/6/e10299/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10299</pub-id>
          <pub-id pub-id-type="medline">31162131</pub-id>
          <pub-id pub-id-type="pii">v7i6e10299</pub-id>
          <pub-id pub-id-type="pmcid">PMC6682298</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>Xie</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Nacioglu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Or</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Prevalence, demographic correlates, and perceived impacts of mobile health app use amongst Chinese adults: cross-sectional survey study</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2018</year>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e103</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/4/e103/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9002</pub-id>
          <pub-id pub-id-type="medline">29699971</pub-id>
          <pub-id pub-id-type="pii">v6i4e103</pub-id>
          <pub-id pub-id-type="pmcid">PMC5945985</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The internet hospital: an emerging innovation in China</article-title>
          <source>Lancet Glob Health</source>
          <year>2015</year>
          <volume>3</volume>
          <issue>8</issue>
          <fpage>e445</fpage>
          <lpage>e446</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2214-109X(15)00042-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2214-109X(15)00042-X</pub-id>
          <pub-id pub-id-type="medline">26187488</pub-id>
          <pub-id pub-id-type="pii">S2214-109X(15)00042-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC7129805</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hesketh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lian</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tian</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Description of an online hospital platform, China</article-title>
          <source>Bull World Health Organ</source>
          <year>2019</year>
          <volume>97</volume>
          <issue>8</issue>
          <fpage>578</fpage>
          <lpage>579</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31384077"/>
          </comment>
          <pub-id pub-id-type="doi">10.2471/BLT.18.226936</pub-id>
          <pub-id pub-id-type="medline">31384077</pub-id>
          <pub-id pub-id-type="pii">BLT.18.226936</pub-id>
          <pub-id pub-id-type="pmcid">PMC6653824</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>Yang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Shu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Understanding "internet plus healthcare" in China: policy text analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>7</issue>
          <fpage>e23779</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/7/e23779/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23779</pub-id>
          <pub-id pub-id-type="medline">34309581</pub-id>
          <pub-id pub-id-type="pii">v23i7e23779</pub-id>
          <pub-id pub-id-type="pmcid">PMC8367124</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>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>User perceptions of virtual hospital apps in China: systematic search</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>8</issue>
          <fpage>e19487</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/8/e19487/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19487</pub-id>
          <pub-id pub-id-type="medline">32687480</pub-id>
          <pub-id pub-id-type="pii">v8i8e19487</pub-id>
          <pub-id pub-id-type="pmcid">PMC7450379</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>Han</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lie</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The internet hospital as a Telehealth Model in China: systematic search and content analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>e17995</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/7/e17995/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17995</pub-id>
          <pub-id pub-id-type="medline">32723721</pub-id>
          <pub-id pub-id-type="pii">v22i7e17995</pub-id>
          <pub-id pub-id-type="pmcid">PMC7424477</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>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Implementation of online hospitals and factors influencing the adoption of mobile medical services in China: cross-sectional survey study</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>2</issue>
          <fpage>e25960</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/2/e25960/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25960</pub-id>
          <pub-id pub-id-type="medline">33444155</pub-id>
          <pub-id pub-id-type="pii">v9i2e25960</pub-id>
          <pub-id pub-id-type="pmcid">PMC7869921</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>National</surname>
              <given-names>HC</given-names>
            </name>
            <name name-style="western">
              <surname>National</surname>
              <given-names>AFTCM</given-names>
            </name>
          </person-group>
          <article-title>Circular on issuing Administrative Measures for Internet Diagnosis (for Trial Implementation) and other policy documents</article-title>
          <source>Guo Wei Yi Fa (2018) no25. Beijing</source>
          <year>2018</year>
          <month>7</month>
          <day>17</day>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.cn/gongbao/content/2019/content_5358684.htm">https://www.gov.cn/gongbao/content/2019/content_5358684.htm</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Internet hospitals in China: cross-sectional survey</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <volume>19</volume>
          <issue>7</issue>
          <fpage>e239</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/7/e239/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7854</pub-id>
          <pub-id pub-id-type="medline">28676472</pub-id>
          <pub-id pub-id-type="pii">v19i7e239</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Implementation and application of telemedicine in China: cross-sectional study</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>10</issue>
          <fpage>e18426</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/10/e18426/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18426</pub-id>
          <pub-id pub-id-type="medline">33095175</pub-id>
          <pub-id pub-id-type="pii">v8i10e18426</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Leigh</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Governor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The use of mobile health applications to improve patient experience: cross-sectional study in Chinese public hospitals</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2018</year>
          <volume>6</volume>
          <issue>5</issue>
          <fpage>e126</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/5/e126/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9145</pub-id>
          <pub-id pub-id-type="medline">29792290</pub-id>
          <pub-id pub-id-type="pii">v6i5e126</pub-id>
          <pub-id pub-id-type="pmcid">PMC5990855</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mirchandani</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <article-title>How hospitals in mainland China responded to the outbreak of COVID-19 using information technology-enabled services: an analysis of hospital news webpages</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <volume>27</volume>
          <issue>7</issue>
          <fpage>991</fpage>
          <lpage>999</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32311036"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa064</pub-id>
          <pub-id pub-id-type="medline">32311036</pub-id>
          <pub-id pub-id-type="pii">5822867</pub-id>
          <pub-id pub-id-type="pmcid">PMC7188168</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bi</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Physicians' perspectives of telemedicine during the COVID-19 pandemic in China: qualitative survey study</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>e26463</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/6/e26463/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/26463</pub-id>
          <pub-id pub-id-type="medline">33945493</pub-id>
          <pub-id pub-id-type="pii">v9i6e26463</pub-id>
          <pub-id pub-id-type="pmcid">PMC8171288</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Assessment of internet hospitals in China during the COVID-19 pandemic: national cross-sectional data analysis study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>e21825</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/1/e21825/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21825</pub-id>
          <pub-id pub-id-type="medline">33417586</pub-id>
          <pub-id pub-id-type="pii">v23i1e21825</pub-id>
          <pub-id pub-id-type="pmcid">PMC7819672</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gong</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Internet hospitals help prevent and control the epidemic of COVID-19 in China: multicenter user profiling study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>e18908</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/4/e18908/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18908</pub-id>
          <pub-id pub-id-type="medline">32250962</pub-id>
          <pub-id pub-id-type="pii">v22i4e18908</pub-id>
          <pub-id pub-id-type="pmcid">PMC7159055</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nicholas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Maitland</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>Application of big data technology for COVID-19 prevention and control in China: lessons and recommendations</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>10</issue>
          <fpage>e21980</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/10/e21980/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21980</pub-id>
          <pub-id pub-id-type="medline">33001836</pub-id>
          <pub-id pub-id-type="pii">v22i10e21980</pub-id>
          <pub-id pub-id-type="pmcid">PMC7561444</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Dilemmas and legislative countermeasures in the development of the internet medical service in China: commentary on measures for the administration of internet diagnosis and treatment (for trial implementation) and two other documents</article-title>
          <source>J Southwest Univ (Soc Sci Ed)</source>
          <year>2022</year>
          <volume>48</volume>
          <issue>02</issue>
          <fpage>37</fpage>
          <lpage>48</lpage>
          <pub-id pub-id-type="doi">10.13718/j.cnki.xdsk.2022.02.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>The status and regulation of the development of internet hospitals in China</article-title>
          <source>Health Econ Res</source>
          <year>2020</year>
          <volume>37</volume>
          <issue>11</issue>
          <fpage>23</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.14055/j.cnki.33-1056/f.2020.11.022</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Risk and prevention and control strategies of privacy leakage of patients under the context of 'internet+ healthcare' in China</article-title>
          <source>Med Soc</source>
          <year>2023</year>
          <volume>36</volume>
          <issue>01</issue>
          <fpage>57</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.13723/j.yxysh.2023.01.011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Research on healthcare data sharing and personal information protection</article-title>
          <source>J Intell</source>
          <year>2023</year>
          <volume>42</volume>
          <issue>05</issue>
          <fpage>192</fpage>
          <lpage>199</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Price</surname>
              <given-names>WN</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>IG</given-names>
            </name>
          </person-group>
          <article-title>Privacy in the age of medical big data</article-title>
          <source>Nat Med</source>
          <year>2019</year>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>43</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30617331"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-018-0272-7</pub-id>
          <pub-id pub-id-type="medline">30617331</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-018-0272-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6376961</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abouelmehdi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Beni-Hessane</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khaloufi</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Big healthcare data: preserving security and privacy</article-title>
          <source>J Big Data</source>
          <year>2018</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <pub-id pub-id-type="doi">10.1186/s40537-017-0110-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Zhan</surname>
              <given-names>QM</given-names>
            </name>
          </person-group>
          <article-title>Big data and medical research in China</article-title>
          <source>BMJ</source>
          <year>2018</year>
          <volume>360</volume>
          <fpage>j5910</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=29437562"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.j5910</pub-id>
          <pub-id pub-id-type="medline">29437562</pub-id>
          <pub-id pub-id-type="pmcid">PMC5797979</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Conflict and reconciliation in big data construction and privacy protection in health care</article-title>
          <source>Med Soc</source>
          <year>2023</year>
          <volume>36</volume>
          <issue>02</issue>
          <fpage>125</fpage>
          <lpage>131</lpage>
          <pub-id pub-id-type="doi">10.13723/j.yxysh.2023.02.023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Tian</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Discussing the security protection of health care big data</article-title>
          <source>Chin Health Serv Manage</source>
          <year>2021</year>
          <volume>38</volume>
          <issue>07</issue>
          <fpage>518</fpage>
          <lpage>520, 525</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Creemers</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>China's emerging data protection framework</article-title>
          <source>J Cybersecurity</source>
          <year>2022</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>tyac011</fpage>
          <pub-id pub-id-type="doi">10.1093/cybsec/tyac011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berti</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Data protection law: a comparison of the latest legal developments in China and European Union</article-title>
          <source>Eur J Privacy Law Technol</source>
          <year>2020</year>
          <volume>1</volume>
          <fpage>34</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://universitypress.unisob.na.it/ojs/index.php/ejplt/article/view/1143"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Standardization Administration of China</collab>
          </person-group>
          <article-title>Information security technology—Personal information security specification (GB/<italic>t</italic> 35273-2020)</article-title>
          <source>Standardization Administration of China</source>
          <year>2020</year>
          <month>10</month>
          <day>01</day>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=4568F276E0F8346EB0FBA097AA0CE05E">https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=4568F276E0F8346EB0FBA097AA0CE05E</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Qi</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The legal construction of personal information protection and privacy under the Chinese Civil Code</article-title>
          <source>Comput Law Secur Rev</source>
          <year>2021</year>
          <volume>41</volume>
          <fpage>105560</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.clsr.2021.105560"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.clsr.2021.105560</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Privacy in AI and the IoT: the privacy concerns of smart speaker users and the personal information protection law in China</article-title>
          <source>Telecommun Policy</source>
          <year>2022</year>
          <volume>46</volume>
          <issue>7</issue>
          <fpage>102334</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.telpol.2022.102334"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.telpol.2022.102334</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Calzada</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Citizens’ data privacy in China: the state of the art of the personal Information Protection Law (PIPL)</article-title>
          <source>Smart Cities</source>
          <year>2022</year>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>1129</fpage>
          <lpage>1150</lpage>
          <pub-id pub-id-type="doi">10.3390/smartcities5030057</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bowie</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Jamal</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Privacy rights on the internet: self-regulation or government regulation?</article-title>
          <source>Bus Ethics Q</source>
          <year>2006</year>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>323</fpage>
          <lpage>342</lpage>
          <pub-id pub-id-type="doi">10.5840/beq200616340</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>MD</given-names>
            </name>
          </person-group>
          <article-title>Gaining trust through online privacy protection: self-regulation, mandatory standards, or caveat emptor</article-title>
          <source>J Manage Inf Syst</source>
          <year>2008</year>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>153</fpage>
          <lpage>173</lpage>
          <pub-id pub-id-type="doi">10.2753/mis0742-1222240406</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karjoth</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Schunter</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A privacy policy model for enterprises</article-title>
          <year>2002</year>
          <conf-name>Proceedings 15th IEEE Computer Security Foundations Workshop. CSFW-15</conf-name>
          <conf-date>June 24–26 2002</conf-date>
          <conf-loc>Cape Breton, NS, Canada</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>271</fpage>
          <lpage>281</lpage>
          <pub-id pub-id-type="doi">10.1109/csfw.2002.1021821</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Flavián</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Guinalíu</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Consumer trust, perceived security and privacy policy: three basic elements of loyalty to a web site</article-title>
          <source>Ind Manage Data Syst</source>
          <year>2006</year>
          <volume>106</volume>
          <issue>5</issue>
          <fpage>601</fpage>
          <lpage>620</lpage>
          <pub-id pub-id-type="doi">10.1108/02635570610666403</pub-id>
          <pub-id pub-id-type="medline">18657047</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shaffer</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Applying a contextual integrity framework to privacy policies for smart technologies</article-title>
          <source>J Inf Policy</source>
          <year>2021</year>
          <volume>11</volume>
          <fpage>222</fpage>
          <lpage>265</lpage>
          <pub-id pub-id-type="doi">10.5325/jinfopoli.11.2021.0222</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nissenbaum</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Privacy as contextual integrity</article-title>
          <source>Wash L Rev</source>
          <year>2004</year>
          <volume>79</volume>
          <fpage>119</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/2mx299bc"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>An Empirical Evaluation of GDPR Compliance Violations in Android mHealth Apps</article-title>
          <year>2020</year>
          <conf-name>2020 IEEE 31st International Symposium on Software Reliability Engineering (ISSRE)</conf-name>
          <conf-date>October 12-15 2020</conf-date>
          <conf-loc>Coimbra, Portugal</conf-loc>
          <publisher-loc>Coimbra, Portugal</publisher-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>253</fpage>
          <lpage>264</lpage>
          <pub-id pub-id-type="doi">10.1109/issre5003.2020.00032</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>The defining approaches and practical paradox of sensitive data: an investigation of data protection laws in 92 Countries and Regions and 200 data breaches in the world</article-title>
          <source>Int J Commun</source>
          <year>2017</year>
          <volume>11</volume>
          <fpage>3286</fpage>
          <lpage>3305</lpage>
          <pub-id pub-id-type="doi">10.1201/9781138069848-29</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braghin</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Cimato</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Libera</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>Are mHealth apps secure? A case study</article-title>
          <year>2018</year>
          <conf-name>2018 IEEE 42nd Annual Computer Software and Applications Conference (COMPSAC)</conf-name>
          <conf-date>July 23-27 2018</conf-date>
          <conf-loc>Tokyo, Japan</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>335</fpage>
          <lpage>340</lpage>
          <pub-id pub-id-type="doi">10.1109/compsac.2018.10253</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alfawzan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Christen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Spitale</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Biller-Andorno</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Privacy, data sharing, and data security policies of women's mHealth apps: scoping review and content analysis</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>e33735</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2022/5/e33735/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/33735</pub-id>
          <pub-id pub-id-type="medline">35522465</pub-id>
          <pub-id pub-id-type="pii">v10i5e33735</pub-id>
          <pub-id pub-id-type="pmcid">PMC9123546</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</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="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hutton</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>McCormick</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bandara</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Hatzakis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Meadows</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nuseibeh</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Assessing the privacy of mHealth apps for self-tracking: heuristic evaluation approach</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2018</year>
          <volume>6</volume>
          <issue>10</issue>
          <fpage>e185</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/10/e185/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9217</pub-id>
          <pub-id pub-id-type="medline">30348623</pub-id>
          <pub-id pub-id-type="pii">v6i10e185</pub-id>
          <pub-id pub-id-type="pmcid">PMC6231850</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sunyaev</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dehling</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>PL</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>Availability and quality of mobile health app privacy policies</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2015</year>
          <volume>22</volume>
          <issue>e1</issue>
          <fpage>e28</fpage>
          <lpage>e33</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/cgi/pmidlookup?view=long&amp;pmid=25147247"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2013-002605</pub-id>
          <pub-id pub-id-type="medline">25147247</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2013-002605</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</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="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Personal information protection and privacy policy compliance of health code apps in China: scale development and Content analysis</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2023</year>
          <volume>11</volume>
          <fpage>e48714</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2023//e48714/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/48714</pub-id>
          <pub-id pub-id-type="medline">37990813</pub-id>
          <pub-id pub-id-type="pii">v11i1e48714</pub-id>
          <pub-id pub-id-type="pmcid">PMC10686616</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ni</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Qian</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Privacy policy compliance of chronic disease management apps in China: scale development and content evaluation</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e23409</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/1/e23409/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23409</pub-id>
          <pub-id pub-id-type="medline">33507159</pub-id>
          <pub-id pub-id-type="pii">v9i1e23409</pub-id>
          <pub-id pub-id-type="pmcid">PMC7878107</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Privacy policy evaluation of internet hospital apps in China from the perspective of cognitive load and content compliance</article-title>
          <source>J Mod Inf</source>
          <year>2023</year>
          <volume>43</volume>
          <issue>03</issue>
          <fpage>110</fpage>
          <lpage>122</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Research on users' privacy protection policy of m-health application based on content analysis</article-title>
          <source>Chin Hosp</source>
          <year>2019</year>
          <volume>23</volume>
          <issue>09</issue>
          <fpage>20</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.19660/j.issn.1671-0592.2019.09.06</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Saxunová</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A perspective on categorizing personal and sensitive data and the analysis of practical protection regulations</article-title>
          <source>Procedia Comput Sci</source>
          <year>2020</year>
          <volume>170</volume>
          <fpage>1110</fpage>
          <lpage>1115</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.procs.2020.03.060"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rakers</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Managing professional personal sensitive information</article-title>
          <year>2010</year>
          <conf-name>SIGUCCS '10: Proceedings of the 38th annual ACM SIGUCCS fall conference: navigation and discovery</conf-name>
          <conf-date>October 24  2010</conf-date>
          <conf-loc>New York, NY, United States</conf-loc>
          <publisher-name>Association for Computing Machinery</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1145/1878335.1878340"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tschider</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The consent myth: improving choice for patients of the future</article-title>
          <source>Wash UL Rev</source>
          <year>2018</year>
          <volume>96</volume>
          <fpage>1505</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/453bzeda"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goldwasser</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vasudevan</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>Formalizing Data Deletion in the Context of the Right to Be Forgotten</source>
          <year>2020</year>
          <publisher-loc>Cham. Switzerland</publisher-loc>
          <publisher-name>Springer International Publishing</publisher-name>
          <fpage>373</fpage>
          <lpage>402</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Gu</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Why data deletion fails? A study on deletion flaws and data remanence in android systems</article-title>
          <source>ACM Trans. Embed. Comput. Syst</source>
          <year>2017</year>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1145/3007211</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nissenbaum</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <source>Protecting Privacy in an Information Age: The Problem of Privacy in Public</source>
          <year>2017</year>
          <publisher-loc>Routledge</publisher-loc>
          <publisher-name>Taylor &amp; Francis Group</publisher-name>
          <fpage>141</fpage>
          <lpage>178</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="confproc">
          <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>
          <year>2020</year>
          <conf-name>IEEE Access</conf-name>
          <conf-date>June 04 2020</conf-date>
          <conf-loc>NA</conf-loc>
          <fpage>104247</fpage>
          <lpage>104268</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.2999934</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wolters</surname>
              <given-names>PTJ</given-names>
            </name>
          </person-group>
          <article-title>The security of personal data under the GDPR: a harmonized duty or a shared responsibility?</article-title>
          <source>Int Data Priv Law</source>
          <year>2017</year>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>165</fpage>
          <lpage>178</lpage>
          <pub-id pub-id-type="doi">10.1093/idpl/ipx008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ung</surname>
              <given-names>COL</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Policy interventions, development trends, and service innovations of internet hospitals in China: documentary analysis and qualitative interview study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>7</issue>
          <fpage>e22330</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/7/e22330/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22330</pub-id>
          <pub-id pub-id-type="medline">34283025</pub-id>
          <pub-id pub-id-type="pii">v23i7e22330</pub-id>
          <pub-id pub-id-type="pmcid">PMC8335616</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Analysis of requirements for developing an mHealth-based health management platform</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2017</year>
          <volume>5</volume>
          <issue>8</issue>
          <fpage>e117</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2017/8/e117/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.5890</pub-id>
          <pub-id pub-id-type="medline">28778840</pub-id>
          <pub-id pub-id-type="pii">v5i8e117</pub-id>
          <pub-id pub-id-type="pmcid">PMC5561389</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Rozanova</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fabre</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 and internet hospital development in China</article-title>
          <source>Epidemiologia (Basel)</source>
          <year>2022</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>269</fpage>
          <lpage>284</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=epidemiologia3020021"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/epidemiologia3020021</pub-id>
          <pub-id pub-id-type="medline">36417257</pub-id>
          <pub-id pub-id-type="pii">epidemiologia3020021</pub-id>
          <pub-id pub-id-type="pmcid">PMC9620872</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Legal protection and fair use of patient health and medical information</article-title>
          <source>Med Soc</source>
          <year>2022</year>
          <volume>35</volume>
          <issue>02</issue>
          <fpage>140</fpage>
          <lpage>144</lpage>
          <pub-id pub-id-type="doi">10.13723/j.yxysh.2022.02.027</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Buijsen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile health in China: does it meet availability, accessibility, acceptability and quality standards? Health policy and technology</article-title>
          <source>Health Policy Technol</source>
          <year>2022</year>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>100660</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.hlpt.2022.100660"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2022.100660</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Research on the current situation, problems and countermeasures of internet medical treatment of traditional Chinese medicine</article-title>
          <source>Chin Hosp</source>
          <year>2023</year>
          <volume>27</volume>
          <issue>11</issue>
          <fpage>34</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.19660/j.issn.1671-0592.2023.11.08</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Internet Hospital: Challenges and Opportunities in China</source>
          <year>2016</year>
          <publisher-loc>Switzerland</publisher-loc>
          <publisher-name>Springer International Publishing</publisher-name>
          <fpage>85</fpage>
          <lpage>90</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="web">
          <article-title>Ministry of industry and information technology reported 31 Apps (SDKs) with infringment on users rights and interest</article-title>
          <source>Information and Communication Bureau</source>
          <access-date>2023-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnii.com.cn/tx/202307/t20230710_485484.html">https://www.cnii.com.cn/tx/202307/t20230710_485484.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="web">
          <article-title>Ministry of industry and information technology reported 56 apps (SDKs) with infringment on users rights and interest</article-title>
          <source>Information and Communication Bureau</source>
          <year>2023</year>
          <access-date>2023-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tjcac.gov.cn/xxh/dzzw/202305/t20230508_6233305.html">https://www.tjcac.gov.cn/xxh/dzzw/202305/t20230508_6233305.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="web">
          <article-title>Ministry of industry and information technology reported 46 apps (SDKs) with infringment on users rights and interest</article-title>
          <source>Information and Communication Bureau</source>
          <year>2023</year>
          <access-date>2023-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnii.com.cn/tx/202302/t20230208_445308.html">https://www.cnii.com.cn/tx/202302/t20230208_445308.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="web">
          <article-title>Ministry of industry and information technology reported 55 apps (SDKs) with infringment on users rights and interest</article-title>
          <source>Information and Communication Bureau</source>
          <year>2023</year>
          <access-date>2023-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://news.china.com.cn/2023-03/22/content_85183464.htm?f=pad&amp;a=true">http://news.china.com.cn/2023-03/22/content_85183464.htm?f=pad&amp;a=true</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abouelmehdi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Beni-Hssane</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khaloufi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Saadi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Big data security and privacy in healthcare: a review</article-title>
          <source>Procedia Comput Sci</source>
          <year>2017</year>
          <volume>113</volume>
          <fpage>73</fpage>
          <lpage>80</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.procs.2017.08.292"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.procs.2017.08.292</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
