<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-journal-title><issn pub-type="epub">1438-8871</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v28i1e83381</article-id><article-id pub-id-type="doi">10.2196/83381</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Perspectives Regarding the Privacy, Security, and Confidentiality of Data Collected via mHealth Apps in Saudi Arabia: Qualitative Analysis</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Alhammad</surname><given-names>Nasser</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Alajlani</surname><given-names>Mohannad</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Abd-alrazaq</surname><given-names>Alaa</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Arvanitis</surname><given-names>Theodoros</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Epiphaniou</surname><given-names>Gregory</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Health Informatics, Saudi Electronic University</institution><addr-line>Jeddah</addr-line><country>Saudi Arabia</country></aff><aff id="aff2"><institution>Institute of Digital Healthcare, Warwick Manufacturing Group (WMG), University of Warwick</institution><addr-line>Millburn House</addr-line><addr-line>Coventry</addr-line><country>United Kingdom</country></aff><aff id="aff3"><institution>Warwick Manufacturing Group (WMG), University of Warwick</institution><addr-line>Coventry</addr-line><country>United Kingdom</country></aff><aff id="aff4"><institution>AI Center for Precision Health, Weill Cornell Medicine</institution><addr-line>Doha</addr-line><country>Qatar</country></aff><aff id="aff5"><institution>School of Engineering, University of Birmingham</institution><addr-line>Birmingham</addr-line><country>United Kingdom</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Stone</surname><given-names>Alicia</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Amanna</surname><given-names>Adaobi</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Bustam</surname><given-names>Aida</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Chakit</surname><given-names>Miloud</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Nasser Alhammad, PhD, Institute of Digital Healthcare, Warwick Manufacturing Group (WMG), University of Warwick, Millburn House, Coventry, CV74AL, United Kingdom, 44 558885007, 44 7563338064; <email>n.alhammad@seu.edu.sa</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>23</day><month>4</month><year>2026</year></pub-date><volume>28</volume><elocation-id>e83381</elocation-id><history><date date-type="received"><day>01</day><month>09</month><year>2025</year></date><date date-type="rev-recd"><day>14</day><month>01</month><year>2026</year></date><date date-type="accepted"><day>15</day><month>01</month><year>2026</year></date></history><copyright-statement>&#x00A9; Nasser Alhammad, Mohannad Alajlani, Alaa Abd-alrazaq, Theodoros Arvanitis, Gregory Epiphaniou. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 23.4.2026. </copyright-statement><copyright-year>2026</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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://www.jmir.org/2026/1/e83381"/><abstract><sec><title>Background</title><p>As Saudi Arabia aims to enhance the adoption and utilization of mobile health (mHealth) apps in the health care sector, it is vital to identify the potential challenges that may be faced in the process and how to address them.</p></sec><sec><title>Objective</title><p>This study aimed to explore patients&#x2019; and stakeholders&#x2019; perspectives regarding the privacy, security, and confidentiality of data collected via mHealth apps in Saudi Arabia.</p></sec><sec sec-type="methods"><title>Methods</title><p>A qualitative research design was used by conducting an in-depth interview with 25 participants, comprising health care workers (HCWs), patients, and mHealth app developers. The interview questions focused on awareness of mHealth apps and issues relating to data security, privacy and confidentiality, benefits of mHealth apps, challenges faced, and features that may improve the utilization of such digital health technologies. Thematic analysis was performed using NVivo software (version 12; QSR International).</p></sec><sec sec-type="results"><title>Results</title><p>Patients were relatively less informed regarding events associated with data privacy and security than HCWs. Specific factors were identified to influence patient awareness with HCWs, suggesting the need for patient education and collaboration with cybersecurity organizations. Participants posited that advanced security features, user-friendly features, online consultation for emergencies, remote monitoring features, and taking patient needs into account are important facilitators of mHealth apps. Shared experiences mainly revolved around the accessibility to information and reliability of mHealth apps, while the challenges were related to poor usability, technical difficulties, data security, and data breaches. Patient autonomy, remote monitoring, self-care management, medical adherence, and time and cost-saving summed up the perceived benefits of the mHealth app.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>These findings may assist policymakers in developing strategies to improve Saudi users&#x2019; and patients&#x2019; adoption of mHealth apps and address the concerns raised to benefit significantly from these advanced health care modalities.</p></sec></abstract><kwd-group><kwd>awareness</kwd><kwd>data privacy</kwd><kwd>confidentiality</kwd><kwd>security</kwd><kwd>health care</kwd><kwd>patients</kwd><kwd>mHealth</kwd><kwd>mobile apps</kwd><kwd>mobile phone</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>With the introduction of smartphones and efforts to improve the delivery of health care services, mobile health (mHealth) apps have witnessed a wider acceptance by the public and health care workers (HCWs) [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. The outbreak of COVID-19 also catalyzed the dependence on digital health as mHealth apps were used in diverse aspects of health care delivery, such as disease management, self-monitoring, health information gathering, supervision of behavioral changes, fitness management, and reminding patients of rehabilitation and medication schedules [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. mHealth apps are also helpful in managing health data, providing easy access to health records, and offering opportunities to execute mobile consultation and remote monitoring either during treatment or follow-up assessment [<xref ref-type="bibr" rid="ref5">5</xref>].</p><p>HCWs and patients constitute the predominant stakeholders within the health care sector. mHealth apps facilitate the sharing of clinical data and information between these 2 bodies [<xref ref-type="bibr" rid="ref6">6</xref>]. Such clinical data are available in the clinical information systems (CISs), which are specific domains in the hospital information systems, directly linked to inpatient and outpatient care. These systems are usually connected to other subsystems within the health care facility, such as department units and laboratories [<xref ref-type="bibr" rid="ref7">7</xref>]. In situations where CISs are the main sources of decision-making and patient management for clinicians, both the accuracy of information provided by patients and how such data are stored and secured are pertinent. Despite the significant roles of integrating mHealth apps and CISs, particularly in terms of hospital workflows, issues relating to data security, confidentiality, and privacy remain a significant challenge. A few studies have demonstrated the adverse effects of data confidentiality, privacy, security, and regulatory supervision of mHealth apps on the adoption and implementation of these digital health technologies [<xref ref-type="bibr" rid="ref8">8</xref>].</p><p>Patients&#x2019; and HCWs&#x2019; awareness about data confidentiality and privacy may influence the risk of data breaches. Moreover, these end users have an obligation for the privacy and security of their data to be guaranteed [<xref ref-type="bibr" rid="ref4">4</xref>]. This data-related relationship between HCWs and patients is contractual and should comply with data privacy regulations, such as the Health Insurance Portability and Accountability Act (HIPAA) and the General Data Protection Regulation (GDPR). Developers of mHealth apps are also encouraged to implement secure authentication and data encryption and carry out timely risk assessments to ensure data security and privacy [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. The HIPAA entails the administrative, physical, and technical aspects to facilitate the privacy of security of personal health data, whereas the GDPR emphasizes the documentation of users&#x2019; consent before recording their personal data and preserving their right to access, amend, delete, or restrict processing their data [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. While mHealth providers are more likely to be aware of the security measures, privacy, and confidentiality related to patients&#x2019; health data, patients and end users appear to be lagging in these important aspects [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Users&#x2019; knowledge and awareness of these aforementioned provisions may influence their perspectives and adoption of mHealth apps.</p><p>In Saudi Arabia&#x2019;s context, the increasing population of smartphone users has facilitated the implementation of several mHealth apps aligning with the country&#x2019;s Vision 2030 goals [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. This transformation to digital health management commenced in 2017 to enhance the delivery of health care services in public and private health [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. However, the adoption of mHealth apps in Saudi Arabia&#x2019;s health care sector is yet to meet the expected benchmark, with issues relating to data privacy and security as one of the mitigating factors [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. While this problem is evident from recent studies using qualitative research methods [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>], the underlying reasons are not fully understood, particularly in the context of Saudi Arabia [<xref ref-type="bibr" rid="ref16">16</xref>].</p><p>Another issue regarding existing literature on mHealth apps in Saudi Arabia is that most previous studies have focused more on health care professionals, whereas patients&#x2019; perspectives have received little attention [<xref ref-type="bibr" rid="ref15">15</xref>]. Both developers&#x2019; and users&#x2019; perspectives need to be balanced to ensure that mHealth apps achieve their targeted goals in enhancing health care service delivery. Qualitative approaches, such as in-depth interviews, focus group discussions, and interpretative phenomenological techniques, offer diverse opportunities to elucidate the underlying events contributing to data privacy and security issues. Such information is pertinent in addressing users&#x2019; needs and developing patient-friendly mHealth apps in Saudi Arabia. This study aims to explore patients&#x2019; and stakeholders&#x2019; perspectives regarding the privacy, confidentiality, and security of data collected via mHealth apps in Saudi Arabia.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design and Location</title><p>To achieve the aim of exploring the use and perceptions of mHealth applications among health care workers and patients, a qualitative study was conducted. Specifically, interviews were carried out to gather in-depth information from HCWs and patients using mHealth apps. The research took place in regions where hospitals feature cutting-edge facilities and currently use mHealth apps for patient management (Riyadh, Madinah, Mecca, Tabuk, Najran, Hall, Northern, Eastern, Al Jouf, Asir, Qassim, Jazan, and Al Baha). These apps are mainly categorized into 4 types: government apps, hospital, insurance, and private clinic apps [<xref ref-type="bibr" rid="ref14">14</xref>]. Examples of these medical applications include Sehhaty, Qariboon, Health Volunteering, SFHP Riyadh, Tawuniya, Labayh, Al Mostajeeb, and Meena Health, which were introduced in the last 6 years. The Sehhaty app, also known as &#x201C;My health,&#x201D; is a robust digital health platform that offers personal health information and promotes knowledge about healthy lifestyles and public health. It was later used for booking COVID-19 vaccine appointments [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. In terms of core functionalities, most of the mHealth apps are designed for general health, such as support or wellness, care delivery, and telemedicine services. Meanwhile, platforms such as Labayh emphasize health education and mental health consultations, addressing specific areas in the health care service delivery [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</p></sec><sec id="s2-2"><title>Study Population</title><p>The study population and unit of analysis in this study encompass all the HCWs, users and nonusers, and developers of mHealth apps who fulfill the inclusion criteria.</p></sec><sec id="s2-3"><title>Participant Selection</title><p>The study used a nonprobability sampling method, specifically purposive sampling, to select participants. Eligible participants included HCWs from hospitals offering mHealth apps for patient management in the identified provinces, patients who are either currently using these apps or nonusers, and developers of these apps. We decided to recruit nonusers because they can equally provide important insights, particularly regarding the barriers to adoption of mHealth apps. mHealth app users are generally classified as either active or passive according to their present usage status. Active users are highly engaged and use the complete provisions in mHealth apps, whereas passive users use the apps occasionally and restrict themselves to a few features [<xref ref-type="bibr" rid="ref19">19</xref>]. Additionally, participants needed to be aged 18 years or older and willing to give both oral and written consent to take part in the research. For qualitative research, sample sizes are not definite but are still required in selecting the study participants [<xref ref-type="bibr" rid="ref20">20</xref>]. According to Leedy and Omrod [<xref ref-type="bibr" rid="ref20">20</xref>], the sample size in qualitative research should range from 5 to 30. Therefore, our target was to recruit about 20&#x2010;30 respondents, depending on the attainment of data saturation. Multidimensional approaches, including emails and social media posts, were used to identify and invite participants in this study.</p></sec><sec id="s2-4"><title>Data Collection Method</title><p>To ensure systematic and organized interviews, an interview guide was developed by the principal investigator (NA) and the supervisor team. Specifically, questions in the interview session were synthesized based on an in-depth review of previous literature and discussion between the researchers. Various studies using either interviews or focus group discussions were reviewed before selecting and modifying the topics, aligning with this study context [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref24">24</xref>].</p><p>Overall, 2 interview guide sections were developed: 1 for the users and nonusers of mHealth apps and 1 for the HCWs and app developers. For the latter, the questions were further divided to suit the HCWs and app developers. The first part contains their personal sociodemographic information. The second part contained specific open-ended questions on both HCWs&#x2019; and app developers&#x2019; perspectives regarding users&#x2019; awareness and understanding of mHealth apps. Meanwhile, HCWs were asked specific questions on their experience with the use of mHealth apps installed in patients&#x2019; personal devices, knowledge of patients&#x2019; health data security and privacy, benefits of mHealth apps to their patients, and potential issues that may prompt the patient to stop using the apps. App developers were probed on the security features that may increase the risk of data breaches and those that could be used to mitigate such risks. For the participating patients, similar questions were asked, except that the items were directed to them. The interview questions were presented in English and no translation to Arabic was performed.</p><p>Interviews were scheduled with the participants upon communicating with them via email or contact directories. Participants were provided with detailed information about the study and their rights, including the right to withdraw at any time without penalty. The interviews were conducted via videoconferencing platforms such as Zoom (Zoom Communications, Inc) or Google Meet, as preferred by the participants. Once the interview session commenced, participants were allowed to share their views on data privacy, confidentiality, and security issues relating to mHealth app usage. Interviews were audio-recorded, professionally transcribed, and checked for accuracy by another reviewer (NA). Data saturation was attained when no additional information was provided by the participant. It took approximately 25 minutes for each participant to complete the interview.</p></sec><sec id="s2-5"><title>Ethical Considerations</title><p>The ethical approval for this research was obtained from the Biomedical and Scientific Research Ethics Committee, University of Warwick (BSREC 03/22&#x2010;23) and the Medical Research &#x0026; Ethics Committee, Ministry of Health in Saudi Arabia. The interview was designed to ensure that participants&#x2019; confidentiality was maintained throughout the research. Informed consent was obtained from all participants prior to the interviews. Videos were turned off during the interview, and only the audio was recorded. Thus, no identifying details were obtained from the participants during the research process. The researcher also stated the confidentiality of all information provided by the participants. Participants were informed that they could decide to withdraw from the study at any time without any penalty. No compensation or incentives were given to the participants. All collected data were stored on a personal computer with a secure password and were accessible only to authorized parties (the supervisory team and the researcher).</p></sec><sec id="s2-6"><title>Data Analysis</title><p>Data obtained from the interviews were analyzed using the NVivo software (version 12; QSR International)&#x2014;a qualitative data analysis software used to organize, code, and identify themes from transcribed data. A thematic analysis was performed in which participants&#x2019; responses during the interview session were analyzed in-depth and checked for any interconnection. Some of the quotations were translated from Arabic to English because a few participants responded to some questions in Arabic despite being informed that the interview would be conducted in English. We also edited the quotations lightly for clarity while ensuring that the content is maintained. Transcription was performed by a research assistant who was not involved in the interview process.</p><p>An inductive approach was used to synthesize themes directly from the transcribed data by following the procedures described by Braun and Clarke [<xref ref-type="bibr" rid="ref25">25</xref>], which is considered a robust systematic guide for thematic analysis. First, the data were scrutinized for familiarity, followed by coding systematically and synthesizing subthemes and themes. The generated themes were cross-checked with the participants&#x2019; verbatim statements, leading to the development of an initial thematic map. Next, the themes were refined and regrouped to address issues with some unsuitable codes and yield metathemes for more detailed grouping. Finally, the themes were defined and given a name. Thematic analysis was conducted by the first author (NA), and validation of the codes and themes was checked by the second author (MA). All other authors discussed the codes and themes, while discrepancies were addressed through consensus. All the experts and members of the research team discussed and agreed on the emerging themes and interrelated responses.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Respondents&#x2019; Demographic Characteristics</title><p>This study involved 25 participants, comprising HCWs (n=11), mHealth app developers (n=2), and users (n=12). As shown in <xref ref-type="table" rid="table1">Table 1</xref>, male participants accounted for more than two-thirds of the samples, but they were evenly distributed in terms of age groups. All the participants were married, employed, and with at least a university or higher educational qualification. All the HCWs and app developers were active users of mHealth apps. Although 3 of the 12 patients or users were passive users, they were all recruited from hospitals where they are currently seeking medical assistance. However, despite considering nonusers of mHealth apps in this study, none of the recruited participants was identified as a nonuser. Apart from HCWs and app developers, the remaining participants were patients visiting the selected hospitals in which mHealth apps are primarily used for clinician-patient communication.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Demographic characteristics of the respondents<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup>.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Variables</td><td align="left" valign="bottom">HCWs<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup> and app developers</td><td align="left" valign="bottom">Patients/users</td></tr></thead><tbody><tr><td align="left" valign="top">Sex</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Male</td><td align="left" valign="top">10 (76.9)</td><td align="left" valign="top">8 (66.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Female</td><td align="left" valign="top">3 (23.1)</td><td align="left" valign="top">4 (33.3)</td></tr><tr><td align="left" valign="top">Age (years)</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>18&#x2010;30</td><td align="left" valign="top">5 (38.4)</td><td align="left" valign="top">4 (33.3)</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>31&#x2010;40</td><td align="left" valign="top">4 (30.7)</td><td align="left" valign="top">5 (41.7)</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x2003;&#x2265;</named-content>41 years</td><td align="left" valign="top">4 (30.7)</td><td align="left" valign="top">3 (25.0)</td></tr><tr><td align="left" valign="top">Marital status</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Single</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">0 (0.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Married</td><td align="left" valign="top">13 (100.0)</td><td align="left" valign="top">12 (100.0)</td></tr><tr><td align="left" valign="top">Educational qualification</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Primary/secondary</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">0 (0.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>University/higher education</td><td align="left" valign="top">8 (61.5)</td><td align="left" valign="top">10 (83.3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Postgraduate</td><td align="left" valign="top">5 (38.5)</td><td align="left" valign="top">2 (16.7)</td></tr><tr><td align="left" valign="top">Employment status</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Employed</td><td align="left" valign="top">13 (100.0)</td><td align="left" valign="top">12 (100.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unemployed</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">0 (0.0)</td></tr><tr><td align="left" valign="top">Type of user</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Active</td><td align="left" valign="top">13 (100.0)</td><td align="left" valign="top">9 (75.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Passive</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">3 (25.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Nonuser</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">0 (0.0)</td></tr><tr><td align="left" valign="top">Currently a patient/HCW attending a hospital in Saudi Arabia</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Yes</td><td align="left" valign="top">11 (100.0)</td><td align="left" valign="top">12 (100.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No</td><td align="left" valign="top">0 (0.0)</td><td align="left" valign="top">0 (0.0)</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Values are presented as n (%).</p></fn><fn id="table1fn2"><p><sup>b</sup>HCWs: health care workers.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Thematic Findings</title><p>The main themes synthesized from the qualitative study are the following: (1) discordant perspectives on the understanding and awareness of mHealth apps, (2) perspectives and awareness of security and privacy of mHealth apps, (3) perceived benefits of mHealth apps, (4) challenges experienced when using mHealth apps (technical difficulties, data security, and data breach), and (5) suggestions to improve the security of mHealth apps. <xref ref-type="other" rid="box1">Textbox 1</xref> shows the theme and respective subthemes.</p><boxed-text id="box1"><title> Themes and subthemes synthesized from the qualitative analysis.</title><p>Theme 1: Discordant perspectives on the understanding and awareness of mobile health (mHealth) apps</p><p>Theme 2: Perspectives and awareness of security and privacy of mHealth apps</p><p>Subthemes</p><list list-type="bullet"><list-item><p>Positive perception</p></list-item><list-item><p>Negative perception</p></list-item><list-item><p>Health care providers&#x2019; responsibilities</p></list-item><list-item><p>Poor knowledge and the need for patient or user education</p></list-item><list-item><p>Collaboration with cybersecurity</p></list-item></list><p>Theme 3: Perceived benefits of mHealth apps</p><p>Subthemes</p><list list-type="bullet"><list-item><p>Patient autonomy</p></list-item><list-item><p>Remote monitoring</p></list-item><list-item><p>Self-care management and medication adherence</p></list-item><list-item><p>Time and cost-saving</p></list-item></list><p>Theme 4: Challenges experienced when using mHealth apps</p><p>Subthemes</p><list list-type="bullet"><list-item><p>Data security and privacy issues</p></list-item><list-item><p>Data breaches</p></list-item><list-item><p>Technical difficulties</p></list-item></list><p>Theme 5: Suggestions to improve the security of mHealth apps</p><list list-type="bullet"><list-item><p>Improved security features</p></list-item><list-item><p>User-friendly features and tailoring toward patient needs</p></list-item><list-item><p>Online consultation for emergencies</p></list-item><list-item><p>Remote monitoring features</p></list-item></list></boxed-text></sec><sec id="s3-3"><title>Discordant Perspectives on the Understanding and Awareness of mHealth Apps</title><p>The first question assessed participants&#x2019; understanding and awareness of mHealth apps. Discordant perspectives were shared by respondents. Specifically, all HCWs and developers of mHealth apps demonstrated a good understanding and awareness, while patients demonstrated otherwise. Overall, HCWs depicted good mHealth app awareness and understanding while emphasizing that such a level of exposure was lacking among their patients. The main subthemes include factors influencing the usage of mHealth apps, poor awareness among users or patients, and the need for patient education. Some of the comments highlighting this theme are illustrated in the following quotations:</p><disp-quote><p>I understand that there is low awareness of mHealth apps among patients. Patients have negative attitudes toward the use of mHealth applications because of various issues, including cost, security concerns, and uncertainty regarding which apps to choose. There is a need to promote mHealth app use among patients.</p><attrib>Health care professional, No. 13; Health care worker 13</attrib></disp-quote><disp-quote><p>My patient has been using a mobile health application for the last couple of years and is well acquainted with the usability of mhealth apps.</p><attrib>Health care worker 11</attrib></disp-quote><p>Most users who reflected a good understanding and awareness of mHealth apps emphasized the role of health care providers in data collection, using the garnered data for remote health monitoring, the positive impact of COVID-19 disease on increased usage of telehealth, and general information on the app operations and functionalities.</p><disp-quote><p>These apps can provide a range of services, including helping users track their physical activity and nutrition, providing educational resources on various health topics, and offering tools to manage conditions such as diabetes or mental health.</p><attrib>mHealth app user, No. 10: US 10</attrib></disp-quote><p>On the other hand, a few users opined that they were unsure of the reason and purpose for collecting their data. Examples of the responses reflecting users&#x2019; poor understanding and awareness of mHealth apps are presented as follows:</p><disp-quote><p>I do not have a deep understanding of mobile health applications, but little that I know is that Mobile health (mHealth) applications are software programs that run on smartphones, tablets, and other mobile devices and are designed to support health and healthcare-related functions.</p><attrib>US 7</attrib></disp-quote></sec><sec id="s3-4"><title>Perspectives and Awareness of Security and Privacy of mHealth Apps</title><sec id="s3-4-1"><title>Overview</title><p>Five subthemes were synthesized from the users&#x2019; responses regarding their perspectives and awareness of mHealth apps&#x2019; data security and privacy. These subthemes included collaboration with cybersecurity organizations, positive perception, negative perception, health care providers&#x2019; responsibilities, and poor knowledge of data security and privacy.</p></sec><sec id="s3-4-2"><title>Positive Perception</title><p>Six of the 10 users perceived that the security and privacy of their data are strictly protected by health care providers and used for the purpose they were collected. These respondents also posited that the database is secure and prevents unauthorized or third-party access to their data. Furthermore, users cited examples of the security features that prompted their positive feedback on mHealth apps, as well as relaying the actions taken by health care providers to ensure the confidentiality and security of patient data.</p><disp-quote><p>I believe to a large extent my data are secured and well-protected because I take my time to navigate through the apps and see the security features available in the app before I start using it.</p><attrib>US 9</attrib></disp-quote><disp-quote><p>The security features strongly protect users&#x2019; data because the app developers provide a range of data-protective mechanisms. Moreover, the data requested is basic regarding my health condition.</p><attrib>US 2</attrib></disp-quote></sec><sec id="s3-4-3"><title>Negative Perception</title><p>On the other hand, 4 of the 10 users opined that the security and privacy of patient data were far from being protected, thus increasing the risk of data breaches and unauthorized access. Among the issues raised by respondents are potential usage of data for nonmedical purposes, ambiguous privacy policies that make it difficult for users to understand how data privacy and security are handled, and a lack of sensitization by health care providers. Therefore, this group of respondents recommended that developers of mHealth apps and health care providers should collaborate to ensure enhanced protection of devices.</p><disp-quote><p>I am afraid of the usage of my data for other things besides the medical and communication with healthcare professionals. This is a critical time whereby data can easily leak to hackers.</p><attrib>US 6</attrib></disp-quote><disp-quote><p>It&#x2019;s a two-way event because data can be used to improve the delivery of healthcare services, but at the same time, unauthorised access to such data may have serious implications, especially if manipulated and used for other purposes.</p><attrib>US 10</attrib></disp-quote></sec><sec id="s3-4-4"><title>Health Care Providers&#x2019; Responsibility</title><p>This theme was synthesized mainly from HCWs&#x2019; responses to the second interview question. Five of the health care professionals highlighted that it is their responsibility to enlighten patients on the available security features on their mHealth apps. They also claimed to be responsible for any data breach since they are considered the custodians of patient data.</p><p>Health care professionals also raised concerns regarding data security and confidentiality, especially challenges in managing patient data. They highlighted the limitations of the current security features in mHealth apps, which may heighten the risk of data breaches and violation of patient privacy.</p><disp-quote><p>It is our duty to ensure that patients&#x2019; data are protected and used solely for medical purposes. Most of these patients are na&#x00EF;ve and not really exposed to mHealth apps because of their backgrounds. Hence, we have to educate them when we have the opportunity to do so.</p><attrib>Health care worker 5</attrib></disp-quote><disp-quote><p>Although the app developers are responsible for designing the security and data privacy features, I believe our role as clinicians is important to mitigate any practices that may lead to data confidentiality and privacy issues. The level of access to patient clinical data needs to be moderated across levels of healthcare services.</p><attrib>Health care worker 2</attrib></disp-quote></sec><sec id="s3-4-5"><title>Poor Knowledge and the Need for Patient Education</title><p>While some users demonstrated either positive or negative attitudes toward data security and privacy, a few participants exhibited poor knowledge of these issues. This theme was reflected in users&#x2019; lack of understanding of the security features available in their devices and their role in ensuring that their data are not shared with unauthorized parties. This finding is reflected in the following statements:</p><disp-quote><p>What is more important to me is to manage my health condition. I don&#x2019;t think I deeply understand the provisions in the apps to address the possibility of my personal data falling into the hands of authorised persons. Seriously, I want to learn more because it&#x2019;s the primary duty of the clinicians and app designers to protect my data, right?</p><attrib>US 8</attrib></disp-quote><disp-quote><p>I can&#x2019;t even recall any information relating to the privacy and security of these apps, despite being a user for almost 2 years. I just focus on using it to book appointments and update my treatment progress.</p><attrib>US 4</attrib></disp-quote><p>As a result, health care professionals and mHealth app developers emphasized the need for more patient education. Accordingly, such interventions should be tailored toward patient needs upon identifying their shortcomings in data security and privacy. This includes proper usage of security features, strong passwords, and who they can share their data with to prevent data breaches.</p><disp-quote><p>We have to educate patients on how to navigate through the security features and use strong passwords to protect against unauthorised data access. This is more important at the moment because there are several websites and apps other than mHealth apps requesting patient personal data.</p><attrib>Health care worker 5</attrib></disp-quote></sec><sec id="s3-4-6"><title>Collaboration With Cybersecurity Organizations</title><p>The fifth theme uncovers the need for health care providers to collaborate with cybersecurity institutions to improve the security, privacy, and confidentiality of data collected via mHealth apps. These respondents did not relay either a positive or negative perspective toward data security and privacy but mainly recommended the approach that can be adopted by health care providers to address the issue. A similar position was shared by the stakeholders who advocated for networking and collaboration between various health care bodies to enhance data security and privacy. The following statements reflect the emerging theme:</p><disp-quote><p>I strongly recommend working together with mHealth app developers, given our experience and understanding of the issues raised by patients and users of these apps. We are in the best position to share the information with the developers since we communicate frequently with patients.</p><attrib>Health care worker 8</attrib></disp-quote><disp-quote><p>It will be challenging for mHealth app developers to enhance the security features of the digital technology without our input as clinicians from the point of patient-clinician relationships. Patients don&#x2019;t have access to the developers of these apps; hence, they often share their concerns with other users or healthcare workers during consultation.</p><attrib>Health care worker 1</attrib></disp-quote></sec></sec><sec id="s3-5"><title>Challenges Experienced When Using mHealth Apps (Technical Difficulties, Data Security, and Data Breach)</title><p>Pertinent information was gleaned regarding the challenges faced by health care professionals and patients while using mHealth apps. These barriers ranged from data security and privacy issues to data breaches and technical difficulties. Poor usability encompasses problems with navigation, understanding the features, and slow operation. These problems made some patients prefer visiting their doctors since the app was not effective in delivering mHealth services. These findings are captured in the following statement:</p><disp-quote><p>I had some challenges navigating through some features. Sometimes I preferred visiting the doctor since I needed to utilise the application to suit my needs effectively. When using the application, I was unsure if my data records were safe since there have been increased hacking and theft cases that could easily compromise my medical records. On rare occasions, the application could freeze, and I needed more time to get what I needed.</p><attrib>US7</attrib></disp-quote><p>A similar scenario was highlighted by health care professionals, who claimed that the app could be misleading with usability, especially when notifications are delayed and during data updates. These challenges are also linked to the issues of violation of data privacy, incidents of data breach, and technical difficulties.</p><disp-quote><p>The mHealth app can sometimes be misleading, especially when the notifications are delayed. I have also experienced misfunctions of the app when updating data and printing some information. I have heard instances where the app stopped operating, asking for updates, which could lead to catastrophe in the case of a terminally ill patient.</p><attrib>Health care worker 2</attrib></disp-quote><disp-quote><p>I have been approached by many patients who wanted me to teach them how to use the application since they did not know how it functions. Even after teaching some of them how to use the application, I experience other issues, such as security and privacy and inaccurate results that patients experience. Some of the applications did not function well, and they frustrated the users.</p><attrib>Health care worker 12</attrib></disp-quote></sec><sec id="s3-6"><title>Perceived Benefits of mHealth Apps</title><sec id="s3-6-1"><title>Overview</title><p>It is well established that mHealth apps offer several advantages and benefits, especially during and in the post&#x2013;COVID-19 era. Four subthemes were identified, namely, patient autonomy, remote monitoring, self-care management and medical adherence, and time and cost-saving. These themes encompass both HCWs&#x2019; and patients&#x2019; responses to the interview questions. The following subsection discusses each theme.</p></sec><sec id="s3-6-2"><title>Patient Autonomy</title><p>The term &#x201C;patient autonomy&#x201D; was used by 3 HCWs in this study while describing the personalization of health care access and services for patients. This theme also elucidates patient control over their data. Likewise, 1 user agreed that mHealth apps have enabled them to make personal changes to their medical data, which can be detected only by the health care provider.</p><disp-quote><p>Patients have a higher degree of autonomy. The applications have also helped many patients to save money and time while quickly accessing medical help.</p><attrib>Health care worker 5</attrib></disp-quote><disp-quote><p>Mobile health applications are an essential tool that has enabled me to personalise my healthcare access. It is a time-saving tool that helps me quickly get the necessary healthcare services. I can easily book appointments and manage my prescriptions and other healthcare services.</p><attrib>US 6</attrib></disp-quote><disp-quote><p>There is a tendency for patients to perceive that their data are secure once they experience the benefits of mHealth apps in terms of treatment and management of their health conditions. This is what I have noticed over time since we introduced these apps to clients.</p><attrib>Health care worker 4</attrib></disp-quote></sec><sec id="s3-6-3"><title>Self-Care Management and Medication Adherence</title><p>This theme was among the most recurring information provided by health care professionals (n=6) and users (n=5) of mHealth apps in this study. Apart from improving patient awareness of the functions and importance of mHealth apps, several users relayed that the technology has assisted them in adhering to various clinicians&#x2019; recommendations and disease management modalities. This includes adhering to recommended diet, medication, and lifestyle activities, therefore culminating in self-care management. Most importantly, the users with this view posited that their health has improved significantly due to the self-care management features provided on the app. The following statements reflect the present theme:</p><disp-quote><p>The mHealth app has proven to be an invaluable tool in my journey towards better health. It has allowed me to adhere to a strict diet, keep track of doctors&#x2019; appointments and medication schedules, and monitor my metabolism and heart rate.</p><attrib>US 7</attrib></disp-quote><disp-quote><p>The Mhealth application provided me with timely medication, which led to the improvement of my health condition. I was able to attend to my health using the application easily.</p><attrib>US 9</attrib></disp-quote></sec><sec id="s3-6-4"><title>Remote Monitoring</title><p>The fact that mHealth apps provide the opportunity for patients and health care professionals to communicate without physical visits was mentioned as a key benefit by both parties. Stakeholders reported that this benefit contributed to the increasing trend of mHealth adoption and usage following the COVID-19 pandemic. Thus, clinicians were able to monitor and track their patients irrespective of their locations. Patients also benefit from communicating directly with clinicians without hospital visits.</p><disp-quote><p>The app has helped me to stick to certain routines, allowing efficiency. The app has also helped me to monitor patients, such as those at home, without having to visit them. The app has also allowed me to keep my record by downloading history easily without having to ask the patient.</p><attrib>Health care worker 3</attrib></disp-quote><disp-quote><p>The mHealth app has helped me to monitor the progress of the patient without having to be there. The app allows sending suggestions and prescriptions, and the recording of data more dynamically and easily.</p><attrib>Health care worker 2</attrib></disp-quote><disp-quote><p>The application kept my health in check while reducing my re-visits. I also saved time costs related to physical visits to the hospital.</p><attrib>US 4</attrib></disp-quote></sec><sec id="s3-6-5"><title>Time-Saving and Cost-Saving</title><p>In line with the provisions for remote monitoring and self-care management, mHealth apps offered a crucial benefit by facilitating real-time information access without any physical interaction between the health care professional and patients. These events save both parties from expending time and resources associated with hospital visits. According to health care professionals, this provision of mHealth apps is crucial in the management of patients with chronic diseases and those requiring home-based therapy.</p><disp-quote><p>The application kept my health in check while reducing my re-visits. I also saved time costs related to physical visits to the hospital.</p><attrib>US 4</attrib></disp-quote><disp-quote><p>The app has also provided a convenient way for me to track my progress, and my doctor has been able to monitor my health remotely, saving me both time and money.</p><attrib>US 9</attrib></disp-quote></sec></sec><sec id="s3-7"><title>Suggestions to Improve the Security of mHealth Apps</title><sec id="s3-7-1"><title>Overview</title><p>Based on the diverse issues raised by users and stakeholders regarding the challenges faced in using mHealth apps, the respondents were probed on the features that need to be integrated into these advanced health technologies to address the identified issues. Resultantly, 4 subthemes emerged from the thematic analysis as follows: improved security features; user-friendly features and tailoring toward patient needs; online consultation for emergencies, tailoring toward patient needs; and remote monitoring features. Each of these themes is presented in the following section.</p></sec><sec id="s3-7-2"><title>Improved Security Features</title><p>Several participants (HCWs: n=4, users: n=5, and App developers: n=1) suggested the need to add more security features to enhance the privacy, security, and confidentiality of data collected via mHealth apps. Different security options and features were mentioned by respondents, including IP address, notification, and second-step verification such as OTP, thumbprint, or facial recognition. Some respondents stated that the app notification system should be enhanced such that the notification is received by the doctor and the patient. These positions were held by patients and health care professionals as presented in the following comments.</p><disp-quote><p>The greatest threat to these apps is security and privacy. To ensure that this is checked, the app should have a change of IP address notification whenever a new device is used, seeking verification. The app should also have a second-step verification whenever accessing the app, such as a thumbprint or OTP.</p><attrib>US 6</attrib></disp-quote><disp-quote><p>Let&#x2019;s improve the security of operating these apps by allowing thumbprint or facial recognition as a form of password to manage these apps. The apps should also come with a printing option so the patient can print, for example, a week&#x2019;s data on their progress.</p><attrib>Health care worker 5</attrib></disp-quote><disp-quote><p>We are currently working on how notifications can be sent to the healthcare provider and patient, as a way of enhancing the security system and data shared between both parties.</p><attrib>App developer 2</attrib></disp-quote></sec><sec id="s3-7-3"><title>User-Friendly Features and Tailoring Toward Patient Needs</title><p>Another important theme emerging from the analysis is to make the mHealth app user-friendly. Participants posited that user-friendly features may redirect patients&#x2019; focus to the usability of the mHealth apps rather than focusing on security and privacy issues. This suggestion was presented by 3 users and 4 HCWs who emphasized the features to encourage the usability of the app and shape the users&#x2019; attitudes and perceptions toward the security and privacy of such apps. Examples of the features include font size, navigation icons, language preference, and login procedures. A few verbatim statements reflecting this theme are shown in the following quotations:</p><disp-quote><p>The features I expect to be added include making the app user-friendly. This involves personalising the app depending on the patient&#x2019;s characteristics, such as age, language preference, and technical literacy. This can help advance the usability of the app.</p><attrib>Health care worker 4</attrib></disp-quote><disp-quote><p>A user-friendly interface should be incorporated into the mobile health application. This would help ensure that the system is easy to use.</p><attrib>US 2</attrib></disp-quote><p>This subtheme also reflects the need to consider patient needs when introducing any new feature to the current mHealth apps used in Saudi Arabia. This position was mostly held by HCWs as they suggested tailoring the app to suit users&#x2019; age, language preference, and technical expertise. Home-based health care services were also suggested to be integrated into mHealth apps to accommodate patient needs. In addition, 1 app developer recommended designing specific features to encourage self-care management among patients with chronic diseases. Respondents claimed that these features will not only improve users&#x2019; interactivity and usability but also provide a medium for social support and increase patient control of their data.</p><disp-quote><p>Patients with chronic illness can have their basic pulse and BP readings monitored after integration with their Fitbit app. This feature will allow them to quickly get the assistance they need at any place and at any time. The patients can read their pulse during their regular duties and check their blood pressure.</p><attrib>App Developer 1</attrib></disp-quote></sec><sec id="s3-7-4"><title>Online Consultation for Emergencies</title><p>Three users and 2 HCWs advocated for a feature specifically designed to enable online consultation for emergency patients. This suggestion stemmed from the challenges associated with the usability of the apps, which may be time-consuming and non&#x2013;user-friendly. The corresponding comments are presented in the following quotations:</p><disp-quote><p>An online consultation will be only for emergencies for our registered patients.</p><attrib>US 1</attrib></disp-quote><disp-quote><p>I believe a function in the app should be dedicated to emergency cases, to enable faster response.</p><attrib>Health care worker 5</attrib></disp-quote></sec><sec id="s3-7-5"><title>Remote Monitoring Features</title><p>Respondents (n=4) opined that more features are required to ensure effective remote monitoring via mHealth apps. Some respondents felt that the features are limited probably to reduce the risk of data security and privacy issues. This theme also emerged from respondents who had negative perceptions of current mHealth apps used in the country. Apart from improving data security and preventing data breaches, this group of respondents suggested better features to monitor both admitted patients and outpatients, as well as motivating patients to engage in self-care management.</p><disp-quote><p>Maybe it is because of the concerns regarding the security of these apps, but I think it does not really help for online communication with healthcare providers. The apps need to be improved for real-time tracking of outpatients and follow-up without exposing our data to unauthorised channels.</p><attrib>US 3</attrib></disp-quote><disp-quote><p>I am using the NahdiCare apps, which are mainly for monitoring care. There is no provision for detailed interaction with the clinician. Most times, I have to visit the hospital for issues that should be resolved via the app.</p><attrib>US 10</attrib></disp-quote></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This study constitutes the first attempt to explore users&#x2019; perspectives on issues relating to the privacy and security of data collected via mHealth apps in Saudi Arabia. Besides, there is limited information on how these challenges may affect the adoption and utilization of digital health technologies. In this study, we focused on the users and nonusers of mHealth apps, as well as HCWs and app developers who constitute the predominant stakeholders of these advanced digital technologies in Saudi Arabia.</p></sec><sec id="s4-2"><title>Awareness and Understanding of mHealth Apps</title><p>Regarding the awareness and understanding of mHealth apps, stakeholders in the health care sector, such as HCWs and app developers, demonstrated a good understanding of issues relating to data security and privacy, whereas users and patients were perceived to lack such knowledge. Moreover, patients also demonstrated a diverse understanding of mHealth apps, which aligns with several studies reporting users&#x2019; concerns about the security and privacy of sensitive data, including images of body parts and those revealing their identity [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. A systematic review by Aljohani and Chandran [<xref ref-type="bibr" rid="ref13">13</xref>] reported that the ease of access and operation of mHealth apps were among the reasons for hospitalized patients&#x2019; concerns about unauthorized access to their health data [<xref ref-type="bibr" rid="ref13">13</xref>]. However, some patients were not worried about these issues either because of their confidence in data safety and features to prevent data breaches, or they were completely unaware of the potential risks involved. This constitutes an important finding, given that most users in this study were highly educated, indicating possible disturbing levels of ignorance and awareness among medium to noneducated users in the general public. Users who are unaware of data privacy and security features and provisions in mHealth apps may be unable to differentiate between risky behaviors, depending on the type of private data collected by various technologies [<xref ref-type="bibr" rid="ref27">27</xref>].</p><p>On the contrary, the understanding and awareness shown by HCWs are expected since they are more conversant with mHealth apps. They are also more exposed and educated, thereby increasing their perception of the risks and benefits associated with digital health technologies. In order to address the low awareness level among patients, most HCWs suggested the need for patient education and enlightening them on pertinent areas. Numerous studies have taken the same stand by emphasizing brief training or education on data security and assuring data confidentiality and privacy [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. Both Nurgalieva et al [<xref ref-type="bibr" rid="ref30">30</xref>] and Lewis and Wyatt [<xref ref-type="bibr" rid="ref31">31</xref>] recommended that patients should be trained and educated to address the external risk factors associated with the violation of users&#x2019; privacy and security in mHealth apps.</p></sec><sec id="s4-3"><title>Recommendations to Improve mHealth Apps&#x2019; Data Privacy and Security</title><p>All the groups of participants in this study provided insights into measures to improve the privacy and security of data used in mHealth apps. Examples include features to improve data security and remote monitoring, making the app more user-friendly and tailored toward the patients&#x2019; needs, and providing online consultation for emergencies. Specific security features such as 2-step verification and authentication, as well as the use of thumbprints and strong password requirements, were mentioned by health care professionals and end users. In the same vein, Alwashmi et al [<xref ref-type="bibr" rid="ref32">32</xref>] opined for the use of an alphanumeric passcode to ensure the protection of mHealth apps rather than using a 4-digit pin, as well as wiping data from the mobile device after a specific number of failed passcode attempts. Nurgalieva et al [<xref ref-type="bibr" rid="ref30">30</xref>] also emphasized the frequency of notifications and alerts programmed into mHealth apps.</p><p>As observed in this study, participants recommended sending notifications to both the health care provider and the patient to ensure extensive review of login attempts or data sharing. A discreet or private notification was advised to prevent any distress to users, particularly in situations where someone mistakenly views the icon. Overall, these recommendations reecho the need for users to have complete control in using their smartphone for mHealth and avoid any intrusion into their daily lives. This event coincides with the personalization and tailoring of newly added features according to patient needs, as mentioned by some respondents. Certain adjustments to the security and privacy features of mHealth apps need to be incorporated by the app developers upon considering patients&#x2019; and users&#x2019; demographics, as evident in previous studies [<xref ref-type="bibr" rid="ref4">4</xref>]. However, given the low number of studies reporting the underlying factors influencing patients&#x2019; views on data privacy, confidentiality, and security issues in mHealth apps, more research is needed to elucidate the relationships.</p><p>Another key recommendation, especially by users, was the need for real-time online consultations for emergency cases. This suggestion stems from the challenges faced in navigating through mHealth apps, which may be time-consuming and ineffective for health care service delivery. Therefore, a specific platform on mHealth apps to facilitate easy and prompt communication with the health care provider&#x2019;s emergency unit was advocated. Such an intervention will come with several benefits and challenges, particularly in terms of educating users. Regarding the benefits and experience garnered from using mHealth apps, participants mentioned diverse ways in which they have benefited from mHealth apps. It is well established that mHealth apps offer several advantages and benefits, especially during and in the post&#x2013;COVID-19 era. The subthemes included patient autonomy, remote monitoring, self-care management and medical adherence, and time and cost-saving.</p><p>Patient autonomy refers to equipping patients or users, as the case may be, with substantial control of their data. Several users and health care professionals highlighted this view either by using personalization of patient data or by giving them unlimited access. On the other hand, remote monitoring entails online interaction and examination between patients and health care professionals. Consequently, patients were motivated to engage in self-care management and medication adherence, ranging from assessing physical parameters to restricting diet. These events contributed significantly to efficient disease progress monitoring, good communication between patients and health care professionals, and better patient outcomes. Our results corroborate the reports from previous studies, whereby improved health status [<xref ref-type="bibr" rid="ref33">33</xref>] and better patient-health care professional relationships [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>] were stated as the main benefits of using mHealth apps.</p><p>In terms of participants&#x2019; experiences with mHealth, although encouraging comments were highlighted by several users, important barriers were mentioned that require further discussion. These barriers ranged from poor usability to data security and privacy issues, data breaches, and technical difficulties. Concerns about data privacy and confidentiality may discourage patients and end users from using mHealth apps [<xref ref-type="bibr" rid="ref35">35</xref>]. Likewise, the low levels of privacy and security of patient data contributed significantly to the low adoption rate among the intended users [<xref ref-type="bibr" rid="ref13">13</xref>]. Past reviews also reported security incidents associated with mHealth apps, such as vulnerabilities to data breaches and malware attacks. The concerns raised by the participants are plausible based on the extensive usage of mobile devices with location sensors in Saudi Arabia, which has facilitated easy access to location-based services [<xref ref-type="bibr" rid="ref33">33</xref>]. Given the extensive privacy and security issues raised by the stakeholders in this study, cyberspace security can be further explored to improve the security of mHealth environments [<xref ref-type="bibr" rid="ref4">4</xref>].</p><p>Surprisingly, the challenges faced appeared not to deter participants from using the technology, as all the respondents who shared their concerns were active users of mHealth apps. A recent study conducted among mature adults also shared a similar view, as none of the participants stopped using the technology despite their data privacy concerns [<xref ref-type="bibr" rid="ref27">27</xref>]. This aligns with the widely discussed privacy paradox [<xref ref-type="bibr" rid="ref36">36</xref>], whereby people engage with technology even when they acknowledge its potential privacy loss issues. Research involving social media, e-commerce, and mobile apps has also demonstrated this phenomenon [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]. This paradoxical behavior is likely driven by users&#x2019; perception that the immediate benefits of using mHealth apps outweigh their potential or hypothetical risks [<xref ref-type="bibr" rid="ref27">27</xref>].</p></sec><sec id="s4-4"><title>Strengths and Limitations</title><p>This study represents the first attempt to qualitatively explore patients&#x2019; and stakeholders&#x2019; perspectives regarding the privacy and security of data collected via mHealth apps in Saudi Arabia. Our findings offer insights on possible strategies to improve end users&#x2019; and patients&#x2019; adoption of mHealth apps and addressing concerns relating to data privacy and security. In terms of sampling, purposive sampling was used to recruit participants with diverse backgrounds (age, gender, app experience, and multiple hospitals). This approach aligns with qualitative research goals of capturing variation and depth. Moreover, qualitative studies are not designed to achieve representativeness or collect data from a representative sample.</p><p>Nevertheless, this study has several limitations that need to be acknowledged and considered when extrapolating the findings. We developed the interview guide and conducted the interviews in English, and only a slight translation was performed during the data transcription. Based on this criterion, most of the respondents were highly educated. As for the HCWs and app developers, this procedure is unlikely to introduce a selection bias since these professionals are expected to hold a higher educational level. However, most users and patients also had at least a university degree, indicating that their views on mHealth and privacy may not be representative of the general Saudi population. Nevertheless, it is interesting to note that several users were still unaware and had a limited understanding of privacy and security of mHealth apps&#x2014;possibly reflecting a more serious problem in the general population.</p><p>Despite our plan to include nonusers in the study, all the participants were either active or passive users of mHealth apps. The patients recruited were from hospitals in which mHealth apps are actively used for consultation and follow-up, making it difficult to identify those who are yet to adopt these digital health apps. Therefore, our findings present limited perspectives on barriers among nonusers. This limitation narrows the study scope and insights. Future studies may consider recruiting nonusers of mHealth apps from the Saudi community or hospitals where patients are not compelled to use such apps.</p><p>Our interview guide was limited in terms of exploring security issues, which led to the superficial technical aspects raised by the app developers and HCWs. While patients were less aware of these technical aspects, as evidenced from the interviews, app developers and HCWs occasionally mentioned the need for more comprehensive access controls, whereas other critical aspects, such as data storage, encryption, and server-side protection, did not emerge from their responses. Apart from the limited questions that may trigger deeper insights into security-related issues, only 2 app developers were recruited, and HCWs may have limited technical awareness while focusing on health-related data and care delivery when using mHealth apps. Future studies may bridge this research gap by recruiting a larger number of stakeholders comprising HCWs and app developers who are technologically savvy for a nuanced understanding of technical and security issues associated with these digital health technologies.</p></sec><sec id="s4-5"><title>Research and Practical Implications</title><p>The results from this study have important implications for mHealth app stakeholders in Saudi Arabia. Both HCWs and developers of mHealth apps have vital roles in addressing the challenges identified in this study, particularly issues relating to data privacy, confidentiality, and security that may affect the adoption and usage of digital health technologies.</p><p>Since HCWs acknowledge patients&#x2019; low awareness and understanding of mHealth apps and the data collected in the process, they can assist by educating patients to address such knowledge deficits. Patients could be briefed during routine consultations by highlighting the need for recording sensitive data and the purpose of collecting such information. Regarding unauthorized third-party access and potential data breaches, users may benefit from information on the privacy requirements and meeting the standards set by the GDPR and HIPAA, which are designed to ensure that such privacy issues and data breaches are prevented.</p><p>Another important aspect is training and educating end users on the existing features and measures to ensure that their data remain secure and confidential. Nevertheless, educational interventions need to be effectively tailored toward the user&#x2019;s level of awareness and understanding. As evident from this study, users&#x2019; less concern about their data privacy and security may arise from being completely ignorant of these potential challenges, or they may perceive that the benefits of using mHealth outweigh the potential risks.</p><p>mHealth app developers can also benefit from the research findings, as the concerns raised by patients and end users may culminate in low adoption and usage of mHealth apps [<xref ref-type="bibr" rid="ref18">18</xref>]. While users are expected to express concerns regarding data privacy and security, it remains unclear whether such concerns influence their behavior and actual use of such apps. This gray area needs more understanding and research. mHealth app developers, particularly in Saudi Arabia, have the opportunity to digest the issues raised by users and strategize on how to improve their current security and privacy measures. Such strategies should be designed and implemented to meet the requirements of HIPAA.</p><p>Finally, policymakers can use the research findings in identifying the areas to focus on when developing policies and strategies to facilitate the wide adoption of mHealth apps and achieve the desired outcomes. Accordingly, policymakers can emphasize features to enhance better patient&#x2013;health care professional relationships, trust, and personal data protection and ensure that health status or medical conditions are not disclosed, as well as brief training or education on data security. Although these points can be relayed to users, trust is a feature that has to be earned, which has to be driven by HCWs and the government.</p></sec></sec></body><back><ack><p>Generative artificial intelligence was not used to draft any portion of this manuscript.</p></ack><notes><sec><title>Funding</title><p>This research did not receive any specific grant from funding agencies in the public, commercial, or not-for-profit sectors.</p></sec><sec><title>Data Availability</title><p>The full data extraction sheet is available from the corresponding author upon request.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: NA, TA, GE (equal)</p><p>Formal analysis: NA (lead), MA, AA (supporting)</p><p>Investigation: NA (lead), MA, AA (supporting)</p><p>Methodology: NA, TA, GE (equal)</p><p>Data curation: NA (lead), MA, AA (supporting)</p><p>Project administration: NA (lead), TA, GE, MA (supporting)</p><p>Writing &#x2013; original draft: NA (lead), MA, AA (supporting)</p><p>Writing &#x2013; review &#x0026; editing: NA, TA, GE, MA, AA</p><p>Supervision: TA, GE (equal)</p><p>Funding acquisition: NA, TA, GE (equal)</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">CIS</term><def><p>clinical information system</p></def></def-item><def-item><term id="abb2">GDPR</term><def><p>General Data Protection Regulation</p></def></def-item><def-item><term id="abb3">HCW</term><def><p>health care worker</p></def></def-item><def-item><term id="abb4">HIPAA</term><def><p>Health Insurance Portability and Accountability Act</p></def></def-item><def-item><term id="abb5">mHealth</term><def><p>mobile health</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Lieffers</surname><given-names>J</given-names> </name><name name-style="western"><surname>Bauman</surname><given-names>A</given-names> </name><name name-style="western"><surname>Hanning</surname><given-names>R</given-names> </name><name name-style="western"><surname>Allman-Farinelli</surname><given-names>M</given-names> </name></person-group><article-title>The use of smartphone health apps and other mobile health (mHealth) technologies in dietetic practice: a three country study</article-title><source>J Hum Nutr Diet</source><year>2017</year><month>08</month><volume>30</volume><issue>4</issue><fpage>439</fpage><lpage>452</lpage><pub-id pub-id-type="doi">10.1111/jhn.12446</pub-id><pub-id pub-id-type="medline">28116773</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>Hussain</surname><given-names>M</given-names> </name><name name-style="western"><surname>Zaidan</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Zidan</surname><given-names>BB</given-names> </name><etal/></person-group><article-title>Conceptual framework for the security of mobile health applications on Android platform</article-title><source>Telematics Inform</source><year>2018</year><month>08</month><volume>35</volume><issue>5</issue><fpage>1335</fpage><lpage>1354</lpage><pub-id pub-id-type="doi">10.1016/j.tele.2018.03.005</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>Fagherazzi</surname><given-names>G</given-names> </name><name name-style="western"><surname>Goetzinger</surname><given-names>C</given-names> </name><name name-style="western"><surname>Rashid</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Aguayo</surname><given-names>GA</given-names> </name><name name-style="western"><surname>Huiart</surname><given-names>L</given-names> </name></person-group><article-title>Digital health strategies to fight COVID-19 worldwide: challenges, recommendations, and a call for papers</article-title><source>J Med Internet Res</source><year>2020</year><month>06</month><day>16</day><volume>22</volume><issue>6</issue><fpage>e19284</fpage><pub-id pub-id-type="doi">10.2196/19284</pub-id><pub-id pub-id-type="medline">32501804</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>Zhou</surname><given-names>L</given-names> </name><name name-style="western"><surname>Bao</surname><given-names>J</given-names> </name><name name-style="western"><surname>Watzlaf</surname><given-names>V</given-names> </name><name name-style="western"><surname>Parmanto</surname><given-names>B</given-names> </name></person-group><article-title>Barriers to and facilitators of the use of mobile health apps from a security perspective: mixed-methods study</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>04</month><day>16</day><volume>7</volume><issue>4</issue><fpage>e11223</fpage><pub-id pub-id-type="doi">10.2196/11223</pub-id><pub-id pub-id-type="medline">30990458</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>Kao</surname><given-names>CK</given-names> </name><name name-style="western"><surname>Liebovitz</surname><given-names>DM</given-names> </name></person-group><article-title>Consumer mobile health apps: current state, barriers, and future directions</article-title><source>PM R</source><year>2017</year><month>05</month><volume>9</volume><issue>5S</issue><fpage>S106</fpage><lpage>S115</lpage><pub-id pub-id-type="doi">10.1016/j.pmrj.2017.02.018</pub-id><pub-id pub-id-type="medline">28527495</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>Li</surname><given-names>J</given-names> </name><name name-style="western"><surname>Silvera-Tawil</surname><given-names>D</given-names> </name><name name-style="western"><surname>Varnfield</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hussain</surname><given-names>MS</given-names> </name><name name-style="western"><surname>Math</surname><given-names>V</given-names> </name></person-group><article-title>Users&#x2019; perceptions toward mHealth technologies for health and well-being monitoring in pregnancy care: qualitative interview study</article-title><source>JMIR Form Res</source><year>2021</year><month>12</month><day>2</day><volume>5</volume><issue>12</issue><fpage>e28628</fpage><pub-id pub-id-type="doi">10.2196/28628</pub-id><pub-id pub-id-type="medline">34860665</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>S. Bhuyan</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>H</given-names> </name><name name-style="western"><surname>Isehunwa</surname><given-names>OO</given-names> </name><etal/></person-group><article-title>Privacy and security issues in mobile health: current research and future directions</article-title><source>Health Policy Technol</source><year>2017</year><month>06</month><volume>6</volume><issue>2</issue><fpage>188</fpage><lpage>191</lpage><pub-id pub-id-type="doi">10.1016/j.hlpt.2017.01.004</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>Sampat</surname><given-names>BH</given-names> </name><name name-style="western"><surname>Prabhakar</surname><given-names>B</given-names> </name></person-group><article-title>Privacy risks and security threats in mHealth apps</article-title><source>J Int Technol Inform Manage</source><year>2017</year><volume>26</volume><issue>4</issue><fpage>126</fpage><lpage>153</lpage><pub-id pub-id-type="doi">10.58729/1941-6679.1353</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Asiri</surname><given-names>E</given-names> </name><name name-style="western"><surname>Asiri</surname><given-names>H</given-names> </name><name name-style="western"><surname>Househ</surname><given-names>M</given-names> </name></person-group><article-title>Exploring the concepts of privacy and the sharing of sensitive health information</article-title><source>Integrating Information Technology and Management for Quality of Care</source><year>2014</year><publisher-name>IOS Press</publisher-name><fpage>161</fpage><lpage>164</lpage><pub-id pub-id-type="other">10.3233/978-1-61499-423-7-161</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>Esposito</surname><given-names>M</given-names> </name><name name-style="western"><surname>Minutolo</surname><given-names>A</given-names> </name><name name-style="western"><surname>Megna</surname><given-names>R</given-names> </name><name name-style="western"><surname>Forastiere</surname><given-names>M</given-names> </name><name name-style="western"><surname>Magliulo</surname><given-names>M</given-names> </name><name name-style="western"><surname>De Pietro</surname><given-names>G</given-names> </name></person-group><article-title>A smart mobile, self-configuring, context-aware architecture for personal health monitoring</article-title><source>Eng Appl Artif Intell</source><year>2018</year><month>01</month><volume>67</volume><fpage>136</fpage><lpage>156</lpage><pub-id pub-id-type="doi">10.1016/j.engappai.2017.09.019</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Alanzi</surname><given-names>T</given-names> </name></person-group><article-title>mHealth for diabetes self-management in the Kingdom of Saudi Arabia: barriers and solutions</article-title><source>J Multidiscip Healthc</source><year>2018</year><volume>11</volume><fpage>535</fpage><lpage>546</lpage><pub-id pub-id-type="doi">10.2147/JMDH.S174198</pub-id><pub-id pub-id-type="medline">30349285</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>Young</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Alharthy</surname><given-names>A</given-names> </name><name name-style="western"><surname>Hosler</surname><given-names>AS</given-names> </name></person-group><article-title>Transformation of Saudi Arabia&#x2019;s health system and its impact on population health: what can the USA learn?</article-title><source>Saudi J Health Syst Res</source><year>2021</year><month>10</month><day>5</day><volume>1</volume><issue>3</issue><fpage>93</fpage><lpage>102</lpage><pub-id pub-id-type="doi">10.1159/000517488</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>Aljohani</surname><given-names>N</given-names> </name><name name-style="western"><surname>Chandran</surname><given-names>D</given-names> </name></person-group><article-title>The adoption of mobile health applications by patients in developing countries: a systematic review</article-title><source>Int J Adv Comput Sci Appl</source><year>2021</year><volume>12</volume><issue>4</issue><fpage>4</fpage><pub-id pub-id-type="doi">10.14569/IJACSA.2021.0120403</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>Alharthi</surname><given-names>SA</given-names> </name></person-group><article-title>mHealth Applications in Saudi Arabia: current features and future opportunities</article-title><source>Healthcare (Basel)</source><year>2025</year><month>06</month><day>11</day><volume>13</volume><issue>12</issue><fpage>1392</fpage><pub-id pub-id-type="doi">10.3390/healthcare13121392</pub-id><pub-id pub-id-type="medline">40565422</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>Aljedaani</surname><given-names>B</given-names> </name><name name-style="western"><surname>Ahmad</surname><given-names>A</given-names> </name><name name-style="western"><surname>Zahedi</surname><given-names>M</given-names> </name><name name-style="western"><surname>Babar</surname><given-names>MA</given-names> </name></person-group><article-title>End-users&#x2019; knowledge and perception about security of clinical mobile health apps: a case study with two Saudi Arabian mHealth providers</article-title><source>J Syst Softw</source><year>2023</year><month>01</month><volume>195</volume><fpage>111519</fpage><pub-id pub-id-type="doi">10.1016/j.jss.2022.111519</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>Kassem</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Alhabib</surname><given-names>B</given-names> </name><name name-style="western"><surname>Alzunaydi</surname><given-names>K</given-names> </name><name name-style="western"><surname>Farooqui</surname><given-names>M</given-names> </name></person-group><article-title>Understanding patient needs regarding adverse drug reaction reporting smartphone applications: a qualitative insight from Saudi Arabia</article-title><source>Int J Environ Res Public Health</source><year>2021</year><month>04</month><day>7</day><volume>18</volume><issue>8</issue><fpage>3862</fpage><pub-id pub-id-type="doi">10.3390/ijerph18083862</pub-id><pub-id pub-id-type="medline">33917014</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>Thapa</surname><given-names>S</given-names> </name><name name-style="western"><surname>Nielsen</surname><given-names>JB</given-names> </name><name name-style="western"><surname>Aldahmash</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Qadri</surname><given-names>FR</given-names> </name><name name-style="western"><surname>Leppin</surname><given-names>A</given-names> </name></person-group><article-title>Willingness to use digital health tools in patient care among health care professionals and students at a university hospital in Saudi Arabia: quantitative cross-sectional survey</article-title><source>JMIR Med Educ</source><year>2021</year><month>02</month><day>19</day><volume>7</volume><issue>1</issue><fpage>e18590</fpage><pub-id pub-id-type="doi">10.2196/18590</pub-id><pub-id pub-id-type="medline">33605896</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>Alzahrani</surname><given-names>A</given-names> </name><name name-style="western"><surname>Gay</surname><given-names>V</given-names> </name><name name-style="western"><surname>Alturki</surname><given-names>R</given-names> </name></person-group><article-title>Exploring Saudi individuals&#x2019; perspectives and needs to design a hypertension management mobile technology solution: qualitative study</article-title><source>Int J Environ Res Public Health</source><year>2022</year><month>10</month><day>10</day><volume>19</volume><issue>19</issue><fpage>12956</fpage><pub-id pub-id-type="doi">10.3390/ijerph191912956</pub-id><pub-id pub-id-type="medline">36232254</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>Wang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Wu</surname><given-names>T</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>Z</given-names> </name></person-group><article-title>Active usage of mobile health applications: cross-sectional study</article-title><source>J Med Internet Res</source><year>2021</year><month>12</month><day>22</day><volume>23</volume><issue>12</issue><fpage>e25330</fpage><pub-id pub-id-type="doi">10.2196/25330</pub-id><pub-id pub-id-type="medline">34941545</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Leedy</surname><given-names>PD</given-names> </name><name name-style="western"><surname>Ormrod</surname><given-names>JE</given-names> </name></person-group><source>Practical Research: Planning and Design</source><year>2010</year><edition>9</edition><publisher-name>Pearson Education, Inc, Upper Saddle River</publisher-name><fpage>67</fpage></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>Dhagarra</surname><given-names>D</given-names> </name><name name-style="western"><surname>Goswami</surname><given-names>M</given-names> </name><name name-style="western"><surname>Kumar</surname><given-names>G</given-names> </name></person-group><article-title>Impact of trust and privacy concerns on technology acceptance in healthcare: an Indian perspective</article-title><source>Int J Med Inform</source><year>2020</year><month>09</month><volume>141</volume><fpage>104164</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104164</pub-id><pub-id pub-id-type="medline">32593847</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>Liu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Lu</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhao</surname><given-names>G</given-names> </name><name name-style="western"><surname>Li</surname><given-names>C</given-names> </name><name name-style="western"><surname>Shi</surname><given-names>J</given-names> </name></person-group><article-title>Adoption of mobile health services using the unified theory of acceptance and use of technology model: self-efficacy and privacy concerns</article-title><source>Front Psychol</source><year>2022</year><volume>13</volume><fpage>944976</fpage><pub-id pub-id-type="doi">10.3389/fpsyg.2022.944976</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Natsiavas</surname><given-names>P</given-names> </name><name name-style="western"><surname>Kakalou</surname><given-names>C</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><name name-style="western"><surname>Koutkias</surname><given-names>V</given-names> </name><etal/></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Ohno-Machado</surname><given-names>L</given-names> </name><name name-style="western"><surname>S&#x00E9;roussi</surname><given-names>B</given-names> </name></person-group><article-title>Citizen perspectives on cross-border eHealth data exchange: a European survey</article-title><source>MEDINFO 2019: Health and Wellbeing e-Networks for All</source><year>2019</year><publisher-name>IOS Press</publisher-name><fpage>719</fpage><lpage>723</lpage><pub-id pub-id-type="doi">10.3233/SHTI190317</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Guo</surname><given-names>S</given-names> </name><name name-style="western"><surname>Guo</surname><given-names>X</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>M</given-names> </name><name name-style="western"><surname>Xie</surname><given-names>K</given-names> </name></person-group><article-title>Privacy concerns about health information disclosure in mobile health: questionnaire study investigating the moderation effect of social support</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>02</month><day>8</day><volume>9</volume><issue>2</issue><fpage>e19594</fpage><pub-id pub-id-type="doi">10.2196/19594</pub-id><pub-id pub-id-type="medline">33555266</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Braun</surname><given-names>V</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name></person-group><article-title>Using thematic analysis in psychology</article-title><source>Qual Res Psychol</source><year>2006</year><month>01</month><volume>3</volume><issue>2</issue><fpage>77</fpage><lpage>101</lpage><pub-id pub-id-type="doi">10.1191/1478088706qp063oa</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>Atienza</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Zarcadoolas</surname><given-names>C</given-names> </name><name name-style="western"><surname>Vaughon</surname><given-names>W</given-names> </name><etal/></person-group><article-title>Consumer attitudes and perceptions on mHealth privacy and security: findings from a mixed-methods study</article-title><source>J Health Commun</source><year>2015</year><volume>20</volume><issue>6</issue><fpage>673</fpage><lpage>679</lpage><pub-id pub-id-type="doi">10.1080/10810730.2015.1018560</pub-id><pub-id pub-id-type="medline">25868685</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>Schroeder</surname><given-names>T</given-names> </name><name name-style="western"><surname>Haug</surname><given-names>M</given-names> </name><name name-style="western"><surname>Gewald</surname><given-names>H</given-names> </name></person-group><article-title>Data privacy concerns using mHealth apps and smart speakers: comparative interview study among mature adults</article-title><source>JMIR Form Res</source><year>2022</year><month>06</month><day>13</day><volume>6</volume><issue>6</issue><fpage>e28025</fpage><pub-id pub-id-type="doi">10.2196/28025</pub-id><pub-id pub-id-type="medline">35699993</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>Fern&#x00E1;ndez-Alem&#x00E1;n</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Se&#x00F1;or</surname><given-names>IC</given-names> </name><name name-style="western"><surname>Lozoya</surname><given-names>P&#x00C1;O</given-names> </name><name name-style="western"><surname>Toval</surname><given-names>A</given-names> </name></person-group><article-title>Security and privacy in electronic health records: a systematic literature review</article-title><source>J Biomed Inform</source><year>2013</year><month>06</month><volume>46</volume><issue>3</issue><fpage>541</fpage><lpage>562</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2012.12.003</pub-id><pub-id pub-id-type="medline">23305810</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>Zhou</surname><given-names>L</given-names> </name><name name-style="western"><surname>Parmanto</surname><given-names>B</given-names> </name><name name-style="western"><surname>Alfikri</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Bao</surname><given-names>J</given-names> </name></person-group><article-title>A mobile app for assisting users to make informed selections in security settings for protecting personal health data: development and feasibility study</article-title><source>JMIR Mhealth Uhealth</source><year>2018</year><month>12</month><day>11</day><volume>6</volume><issue>12</issue><fpage>e11210</fpage><pub-id pub-id-type="doi">10.2196/11210</pub-id><pub-id pub-id-type="medline">30538088</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>Nurgalieva</surname><given-names>L</given-names> </name><name name-style="western"><surname>O&#x2019;callaghan</surname><given-names>D</given-names> </name><name name-style="western"><surname>Doherty</surname><given-names>G</given-names> </name></person-group><article-title>Security and privacy of mHealth applications: a scoping review</article-title><source>IEEE Access</source><year>2016</year><volume>4</volume><fpage>10433</fpage><lpage>10446</lpage><pub-id pub-id-type="doi">10.1109/ACCESS.2016.2637622</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>Lewis</surname><given-names>TL</given-names> </name><name name-style="western"><surname>Wyatt</surname><given-names>JC</given-names> </name></person-group><article-title>mHealth and mobile medical apps: a framework to assess risk and promote safer use</article-title><source>J Med Internet Res</source><year>2014</year><month>09</month><day>15</day><volume>16</volume><issue>9</issue><fpage>e210</fpage><pub-id pub-id-type="doi">10.2196/jmir.3133</pub-id><pub-id pub-id-type="medline">25223398</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>Alwashmi</surname><given-names>MF</given-names> </name><name name-style="western"><surname>Fitzpatrick</surname><given-names>B</given-names> </name><name name-style="western"><surname>Farrell</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Perceptions of patients regarding mobile health interventions for the management of chronic obstructive pulmonary disease: mixed methods study</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>07</month><day>23</day><volume>8</volume><issue>7</issue><fpage>e17409</fpage><pub-id pub-id-type="doi">10.2196/17409</pub-id><pub-id pub-id-type="medline">32706697</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>Zhang</surname><given-names>D</given-names> </name><name name-style="western"><surname>Lim</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhou</surname><given-names>L</given-names> </name><name name-style="western"><surname>Dahl</surname><given-names>AA</given-names> </name></person-group><article-title>Breaking the data value-privacy paradox in mobile mental health systems through user-centered privacy protection: a web-based survey study</article-title><source>JMIR Ment Health</source><year>2021</year><month>12</month><day>24</day><volume>8</volume><issue>12</issue><fpage>e31633</fpage><pub-id pub-id-type="doi">10.2196/31633</pub-id><pub-id pub-id-type="medline">34951604</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kayyali</surname><given-names>R</given-names> </name><name name-style="western"><surname>Peletidi</surname><given-names>A</given-names> </name><name name-style="western"><surname>Ismail</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hashim</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Bandeira</surname><given-names>P</given-names> </name><name name-style="western"><surname>Bonnah</surname><given-names>J</given-names> </name></person-group><article-title>Awareness and use of mHealth apps: a study from England</article-title><source>Pharmacy (Basel)</source><year>2017</year><month>06</month><day>14</day><volume>5</volume><issue>2</issue><fpage>33</fpage><pub-id pub-id-type="doi">10.3390/pharmacy5020033</pub-id><pub-id pub-id-type="medline">28970445</pub-id></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>Korpershoek</surname><given-names>YJG</given-names> </name><name name-style="western"><surname>Vervoort</surname><given-names>S</given-names> </name><name name-style="western"><surname>Trappenburg</surname><given-names>JCA</given-names> </name><name name-style="western"><surname>Schuurmans</surname><given-names>MJ</given-names> </name></person-group><article-title>Perceptions of patients with chronic obstructive pulmonary disease and their health care providers towards using mHealth for self-management of exacerbations: a qualitative study</article-title><source>BMC Health Serv Res</source><year>2018</year><month>10</month><day>4</day><volume>18</volume><issue>1</issue><fpage>757</fpage><pub-id pub-id-type="doi">10.1186/s12913-018-3545-4</pub-id><pub-id pub-id-type="medline">30286761</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>Norberg</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Horne</surname><given-names>DR</given-names> </name><name name-style="western"><surname>Horne</surname><given-names>DA</given-names> </name></person-group><article-title>The privacy paradox: personal information disclosure intentions versus behaviors</article-title><source>J Consum Aff</source><year>2007</year><month>06</month><volume>41</volume><issue>1</issue><fpage>100</fpage><lpage>126</lpage><pub-id pub-id-type="doi">10.1111/j.1745-6606.2006.00070.x</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>Sutanto</surname><given-names>J</given-names> </name><name name-style="western"><surname>Palme</surname><given-names>E</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>CH</given-names> </name><name name-style="western"><surname>Phang</surname><given-names>CW</given-names> </name></person-group><article-title>Addressing the personalization&#x2013;privacy paradox: an empirical assessment from a field experiment on smartphone users1</article-title><source>MIS Q</source><year>2013</year><month>12</month><day>1</day><volume>37</volume><issue>4</issue><fpage>1141</fpage><lpage>1164</lpage><pub-id pub-id-type="doi">10.25300/MISQ/2013/37.4.07</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>Kokolakis</surname><given-names>S</given-names> </name></person-group><article-title>Privacy attitudes and privacy behaviour: a review of current research on the privacy paradox phenomenon</article-title><source>Comput Secur</source><year>2017</year><month>01</month><volume>64</volume><fpage>122</fpage><lpage>134</lpage><pub-id pub-id-type="doi">10.1016/j.cose.2015.07.002</pub-id></nlm-citation></ref></ref-list></back></article>