<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article article-type="brief-report" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="EN">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Digit. Health</journal-id>
<journal-title>Frontiers in Digital Health</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Digit. Health</abbrev-journal-title>
<issn pub-type="epub">2673-253X</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/fdgth.2024.1382507</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Digital Health</subject>
<subj-group>
<subject>Brief Research Report</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Exploring the digital divide: results of a survey informing mobile application development</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name><surname>Claudio</surname><given-names>Maira Corinne</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="corresp" rid="cor1">&#x002A;</xref>
<xref ref-type="author-notes" rid="an1"><sup>&#x2020;</sup></xref><uri xlink:href="https://loop.frontiersin.org/people/2185133/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author" equal-contrib="yes"><name><surname>Rehany</surname><given-names>Zachary</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="author-notes" rid="an1"><sup>&#x2020;</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author"><name><surname>Stachtari</surname><given-names>Katerina</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author"><name><surname>Guadagno</surname><given-names>Elena</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author"><name><surname>Osmanlliu</surname><given-names>Esli</given-names></name>
<xref ref-type="aff" rid="aff3"><sup>3</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author"><name><surname>Poenaru</surname><given-names>Dan</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref><uri xlink:href="https://loop.frontiersin.org/people/1654811/overview" />
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
</contrib-group>
<aff id="aff1"><label><sup>1</sup></label><institution>Faculty of Medicine and Health Sciences, McGill University</institution>, <addr-line>Montreal, QC</addr-line>, <country>Canada</country></aff>
<aff id="aff2"><label><sup>2</sup></label><institution>Harvey E. Beardmore Division of Pediatric Surgery, The Montreal Children&#x2019;s Hospital, McGill University Health Center</institution>, <addr-line>Montreal, QC</addr-line>, <country>Canada</country></aff>
<aff id="aff3"><label><sup>3</sup></label><institution>Division of Pediatric Emergency Medicine, Department of Pediatrics, The Montreal Children&#x2019;s Hospital, McGill University Health Centre</institution>, <addr-line>Montreal, QC</addr-line>, <country>Canada</country></aff>
<author-notes>
<fn fn-type="edited-by"><p><bold>Edited by:</bold> Saskia M. Kelders, University of Twente, Netherlands</p></fn>
<fn fn-type="edited-by"><p><bold>Reviewed by:</bold> Tessa Dekkers, University of Twente, Netherlands</p>
<p>Gianvincenzo Zuccotti, University of Milan, Italy</p></fn>
<corresp id="cor1"><label>&#x002A;</label><bold>Correspondence:</bold> Maira Corinne Claudio <email>maira.claudio@mail.mcgill.ca</email></corresp>
<fn fn-type="equal" id="an1"><label><sup>&#x2020;</sup></label><p>These authors share first authorship</p></fn>
</author-notes>
<pub-date pub-type="epub"><day>10</day><month>05</month><year>2024</year></pub-date>
<pub-date pub-type="collection"><year>2024</year></pub-date>
<volume>6</volume><elocation-id>1382507</elocation-id>
<history>
<date date-type="received"><day>05</day><month>02</month><year>2024</year></date>
<date date-type="accepted"><day>24</day><month>04</month><year>2024</year></date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2024 Claudio, Rehany, Stachtari, Guadagno, Osmanlliu and Poenaru.</copyright-statement>
<copyright-year>2024</copyright-year><copyright-holder>Claudio, Rehany, Stachtari, Guadagno, Osmanlliu and Poenaru</copyright-holder><license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License (CC BY)</ext-link>. The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p></license>
</permissions>
<abstract>
<sec><title>Introduction</title>
<p>Mobile health apps risk widening health disparities if they overlook digital inclusion. The digital divide, encompassing access, familiarity, and readiness, poses a significant barrier to medical interventions. Existing literature lacks exploration of the digital divide&#x0027;s contributing factors. Hence, data are needed to comprehend the challenges in developing inclusive health apps.</p>
</sec>
<sec><title>Methods</title>
<p>We created a survey to gauge internet and smartphone access, smartphone familiarity, and readiness for using mobile health apps among caregivers of pediatric patients in tertiary care. Open-ended questions solicited feedback and suggestions on mobile health applications. Responses were categorized by similarity and compared. Developed with patient partners, the survey underwent cognitive testing and piloting for accuracy.</p>
</sec>
<sec><title>Results</title>
<p>Data from 209 respondents showed that 23&#x0025; were affected by the digital divide, mainly due to unfamiliarity with digital skills. Among 49 short text responses about health app concerns, 31 mentioned security and confidentiality, with 7 mentioning the impersonal nature of such apps. Desired features included messaging healthcare providers, scheduling, task reminders, and simplicity.</p>
</sec>
<sec><title>Conclusions</title>
<p>This study underscores a digital divide among caregivers of pediatric patients, with nearly a quarter affected primarily due to a lack of digital comfort. Respondents emphasized user-friendliness and online security for health apps. Future apps should prioritize digital inclusion by addressing the significant barriers and carefully considering patient and family concerns.</p>
</sec>
</abstract>
<kwd-group>
<kwd>digital divide</kwd>
<kwd>pediatric</kwd>
<kwd>mobile applications</kwd>
<kwd>telemedicine</kwd>
<kwd>health equity</kwd>
</kwd-group>
<counts>
<fig-count count="1"/>
<table-count count="4"/><equation-count count="0"/><ref-count count="32"/><page-count count="0"/><word-count count="0"/></counts><custom-meta-wrap><custom-meta><meta-name>section-at-acceptance</meta-name><meta-value>Health Technology Implementation</meta-value></custom-meta></custom-meta-wrap>
</article-meta>
</front>
<body>
<sec id="s1" sec-type="intro"><title>Introduction</title>
<p>Mobile health applications (&#x201C;apps&#x201D;) are gaining popularity for patient services due to their practicality in enabling remote patient contact and reducing the need for in-person follow-up, thereby alleviating medical or operative complications and improving overall care outcomes (<xref ref-type="bibr" rid="B1">1</xref>, <xref ref-type="bibr" rid="B2">2</xref>). By prioritizing inclusivity, mobile health innovations can effectively address the diverse needs of users and promote equitable healthcare outcomes (<xref ref-type="bibr" rid="B3">3</xref>, <xref ref-type="bibr" rid="B4">4</xref>).</p>
<p>The <italic>digital divide</italic> refers to the gap that exists between individuals who have adequate digital access and those who do not (<xref ref-type="bibr" rid="B5">5</xref>). The digital divide also extends to include those who lack the necessary proficiency or motivation to use digital tools (<xref ref-type="bibr" rid="B6">6</xref>, <xref ref-type="bibr" rid="B7">7</xref>). We have categorized the factors causing the digital divide into three main categories based on recurring themes in the literature, which are digital access, familiarity, and readiness. We then explain the relevance these categories have concerning mobile health apps.</p>
<sec id="s1a"><title>Access</title>
<p>Access to mobile health apps is a critical aspect of addressing disparities in healthcare delivery. Limited access to smartphones and reliable internet can impede individuals from using health apps, particularly those from marginalized communities or underserved regions. Although trends show that the level of smartphone and internet ownership is rapidly increasing, there is still a portion of the population who still face barriers to access (<xref ref-type="bibr" rid="B8">8</xref>, <xref ref-type="bibr" rid="B9">9</xref>).</p>
</sec>
<sec id="s1b"><title>Familiarity</title>
<p>Health disparities can also increase if individuals lack the proficiency to use these tools. The usability of an app is therefore very important when implementing mobile health apps. Studies find that health apps with poor rated usability were much less commonly adhered to and therefore would have little impact on the level of care (<xref ref-type="bibr" rid="B2">2</xref>, <xref ref-type="bibr" rid="B10">10</xref>). In many cases, health apps have caused stress or frustration among patients because of design or navigational issues thereby causing reluctance to use them (<xref ref-type="bibr" rid="B10">10</xref>, <xref ref-type="bibr" rid="B11">11</xref>). Another study revealed that around 1 in 3 adults are not aware of in-app customizations leading many to feel that the apps did not fit their needs (<xref ref-type="bibr" rid="B12">12</xref>).</p>
</sec>
<sec id="s1c"><title>Readiness</title>
<p>A person&#x0027;s willingness to use a mobile health app also plays a critical role in the digital divide. Having a poor understanding of the value of mobile interventions lead users to have a lower motivation in deciding to use them (<xref ref-type="bibr" rid="B7">7</xref>). A study analyzing the factors impacting the use of mobile health apps found that usability alone isn&#x0027;t sufficient to motivate patients in using them (<xref ref-type="bibr" rid="B12">12</xref>). There are numerous hesitations people may have that prevent them from engaging in health apps such as lacking confidence in the benefits, finding them tedious, and having data privacy or confidentiality concerns (<xref ref-type="bibr" rid="B7">7</xref>, <xref ref-type="bibr" rid="B13">13</xref>, <xref ref-type="bibr" rid="B14">14</xref>). Meanwhile, greater patient engagement has been found to be improved by raising awareness of health apps through more clinical endorsements and physician recommendations (<xref ref-type="bibr" rid="B12">12</xref>, <xref ref-type="bibr" rid="B15">15</xref>, <xref ref-type="bibr" rid="B16">16</xref>).</p>
<p>The objective of this study is to examine the digital divide by measuring the extent of the major contributing factors. This was done by administering a survey at our site with multiple-choice questions for access, familiarity and readiness categories. To further assess the quality of patients&#x0027; readiness, we introduced the concept of a health app and asked open-ended questions about their concerns or what they would find valuable in such an app. Consequently, the survey results will yield an overall picture of the digital divide&#x0027;s characteristic nature and barriers, which will inform the development and implementation of health apps in ensuring inclusivity. We have not found a study in the literature that has integrated all three factors in order to examine the overall impact of the divide. By doing so, similar institutions can gauge the level of effort needed to address each barrier and enhance these tools accordingly for broader accessibility.</p>
</sec>
</sec>
<sec id="s2" sec-type="methods"><title>Methods</title>
<p>A cross-sectional survey was conducted at the Montreal Children&#x0027;s Hospital (MCH), an urban tertiary pediatric hospital that serves a multicultural population, encompassing patients from multiple cultural backgrounds and ethnicities typically cared for at our institution. In the context of this study, we aimed to identify constraints that may limit patients&#x0027; ability to use digital health interventions. Eligible participants for the study were caregivers (including parents and guardians) of children under 18 years old who had visited the MCH Pediatric Surgery outpatient clinic or Emergency Department. Participants were required to be able to complete the survey in either English or French. The study recruited a convenience sample of caregivers at the locations between January and May 2022. The surveys were accessible either through stands placed in these locations or by being distributed by department staff members. Additionally, participants had the choice to complete either a paper survey or an online version by scanning a QR code. Respectively, the decision to collect survey responses via both QR code and paper format stemmed from a recognition of the varying digital literacy levels among respondents. Specifically, it is important to acknowledge that individuals proficient in digital technologies may be less likely to utilize the paper version of the survey. As a result, presenting responses from both groups becomes informative and enhances the comprehensiveness of the study. Ethical approval for the study was obtained from the McGill University Health Centre&#x0027;s Research Ethics Board (REB 2022-8127).</p>
<p>The survey instrument was developed by adapting questions from two validated instruments: Canadian Internet Use Survey (CIUS) and eHealth Literacy Questionnaire (eHLQ) (<xref ref-type="bibr" rid="B17">17</xref>, <xref ref-type="bibr" rid="B18">18</xref>).</p>
<p>The Canadian Internet Use Survey (CIUS) is intended to examine the Canadian population over the age of 15 to better understand how digital technology affects people&#x0027;s lives (<xref ref-type="bibr" rid="B17">17</xref>). It encompasses internet-connected smart devices, digital skills, and security elements such as privacy and trust, among others. Furthermore, it assesses barriers to internet access and the usage of digital technology. The survey is meant to inform evidence-based policymaking on digital technology among the Canadian population. The eHealth Literacy Questionnaire (eHLQ) is a developed validated tool that is based on the eHLF framework (<xref ref-type="bibr" rid="B18">18</xref>). The eHLQ takes into consideration health literacy and the need to assess that the rapid advancement of digital health literacy is meeting user needs and unique experiences. As a result, both tools were chosen based on their reliability and alignment with our priorities to study the digital divide at the MCH, which are to reduce access obstacles and better understand the use of digital and internet access, alongside concerns among users.</p>
<p>To ensure the study&#x0027;s quality, feedback from team interactions was incorporated, following the experience-based co-design method, which is an approach aimed at improving healthcare services by involving both the stakeholders (patients/caregivers) and physicians in the design process (<xref ref-type="bibr" rid="B19">19</xref>). In our study, this included a group of patient research partners with whom we discussed each step of the project proposal, survey development and the analysis of the collected data. In the cognitive testing stage, five patient partners reviewed and assessed the survey for question interpretation ambiguities, leading to modifications for improved comprehensibility. A pilot test of the survey was also conducted with ten individuals, and the final draft was discussed in sessions with small groups of patient partners. The patient partners were members of the lab&#x0027;s Patient Advisory Committee, composed of parents/caretakers of children treated in the Department of Surgery.</p>
<p>The structured questionnaire comprised three domains: digital access, familiarity, and readiness. The digital access domain assessed participants&#x0027; level of home or mobile internet, as well as smartphone access. The digital familiarity domain measured participants&#x0027; comfort or skill level in using a smartphone, including their knowledge of downloading smartphone apps and familiarity with common smartphone features. The readiness domain sought patient perspectives/attitudes on mobile healthcare apps. A respondent was deemed affected by the digital divide if they showed vulnerability in at least one domain. To further assess the respondents&#x0027; attitudes toward mobile health apps, a concept test of a pediatric health app was presented, including questions about features they would find valuable in such an app and any concerns they may have (viewable in <xref ref-type="app" rid="app1">Appendix 1</xref>). Cohort characteristics were measured, including age, education, employment status and preferred language, but were deliberately kept separate from the survey data to prioritize respondent privacy.</p>
<p>In order to quantify the significance of each of the 3 domains, we selected specific questions within each category that provided a clear indication of impact, while excluding those with potential for ambiguous interpretation. Lack of access was determined by whether participants lacked adequate home internet or smartphone ownership (Q1 &#x0026; 3). Lack of digital familiarity by considering participants who expressed discomfort using smartphones or were unsure how to download smartphone apps (Q6 &#x0026; 7). Lastly, a lack of readiness by identifying participants who expressed unwillingness to use mobile apps for their health (Q9). When classifying the total affected individuals into the three domains (shown in <xref ref-type="fig" rid="F1">Figure&#x00A0;1</xref>), an individual was counted once per domain to prevent overlapping in the results. This approach ensured that the final count accurately represented the number of individuals affected by the digital divide, without inflating the numbers due to overlapping categories or double counting.</p>
<fig id="F1" position="float"><label>Figure 1</label>
<caption><p>The classification of different reasons for being affected by the digital divide. Individuals affected by a combination of factors were accounted for once and overlaps were resolved.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="fdgth-06-1382507-g001.tif"/>
</fig>
<p>Descriptive analysis was performed on the multiple-choice results, while analyses of short-text answers involved grouping similar responses into themes and comparing the number of responses within each theme. This analysis was done manually, without utilizing automated coding techniques. This approach ensured a meticulous examination of the data. An example of classing two responses into the same theme would be: &#x201C;the privacy of information given and protection from hackers&#x201D; and &#x201C;personal information being shared &#x0026; security concerns&#x201D; were both classified into the theme of security &#x0026; confidentiality.</p>
</sec>
<sec id="s3" sec-type="results"><title>Results</title>
<p>There were 209 completed surveys (104 on paper, 105 online). Out of the 185 participants who provided their primary language information, 103 (56&#x0025;) identified as anglophone, while 76 (41&#x0025;) identified as francophone (<xref ref-type="table" rid="T1">Table&#x00A0;1</xref>). We did not collect information regarding the sex of respondents. Additionally, respondents were only asked to indicate their age from the provided age ranges, as seen in <xref ref-type="table" rid="T1">Table&#x00A0;1</xref>. Further demographic data can also be found in <xref ref-type="table" rid="T1">Table&#x00A0;1</xref>.</p>
<table-wrap id="T1" position="float"><label>Table 1</label>
<caption><p>Summary of respondents&#x2019; demographics.</p></caption>
<table frame="hsides" rules="groups">
<colgroup>
<col align="left"/>
<col align="center"/>
<col align="center"/>
<col align="center"/>
</colgroup>
<thead>
<tr>
<th valign="top" align="left"/>
<th valign="top" align="center">Digital</th>
<th valign="top" align="center">Paper</th>
<th valign="top" align="center">Count</th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Age</td>
<td valign="top" align="center"/>
<td valign="top" align="center"/>
<td valign="top" align="center"><italic>n</italic>&#x2009;&#x003D;&#x2009;186</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;14&#x2013;17</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1 (1&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;18&#x2013;24</td>
<td valign="top" align="center">16</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">16 (9&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;25&#x2013;34</td>
<td valign="top" align="center">17</td>
<td valign="top" align="center">20</td>
<td valign="top" align="center">37 (20&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;35&#x2013;44</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">41</td>
<td valign="top" align="center">76 (41&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;45&#x2013;54</td>
<td valign="top" align="center">16</td>
<td valign="top" align="center">33</td>
<td valign="top" align="center">49 (26&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;55&#x2013;64</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">3 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;65&#x2013;74</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2 (1&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;75 or over</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2 (1&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Education completed</td>
<td valign="top" align="center"/>
<td valign="top" align="center"/>
<td valign="top" align="center"><italic>n</italic>&#x2009;&#x003D;&#x2009;184</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;High school certificate or equivalent</td>
<td valign="top" align="center">22</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">57 (31&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Undergraduate</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">41</td>
<td valign="top" align="center">76 (41&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Postgraduate</td>
<td valign="top" align="center">16</td>
<td valign="top" align="center">14</td>
<td valign="top" align="center">30 (16&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;No certificate, diploma, degree</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">9 (5&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;I prefer not to answer</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">5 (3&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Other</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">7 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Employment status</td>
<td valign="top" align="center"/>
<td valign="top" align="center"/>
<td valign="top" align="center"><italic>n</italic>&#x2009;&#x003D;&#x2009;186</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Full-time (over 30&#x2005;h/week)</td>
<td valign="top" align="center">50</td>
<td valign="top" align="center">68</td>
<td valign="top" align="center">118 (63&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Part-time (under 30&#x2005;h/week)</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">23 (12&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Unemployed</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">12 (6&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Retired</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">3 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Student</td>
<td valign="top" align="center">17</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">17 (9&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;I prefer not to answer</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">5 (3&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Other</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">8 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Preferred language of communication</td>
<td valign="top" align="center"/>
<td valign="top" align="center"/>
<td valign="top" align="center"><italic>n</italic>&#x2009;&#x003D;&#x2009;185</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;English</td>
<td valign="top" align="center">42</td>
<td valign="top" align="center">61</td>
<td valign="top" align="center">103 (56&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;French</td>
<td valign="top" align="center">41</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">76 (41&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">&#x2003;Other</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">6 (3&#x0025;)</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="table-fn1"><p>Non-respondents for each question were excluded from the data.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Five respondents (2&#x0025;) reported not having internet access at home. Among those with internet access, 7 respondents (3&#x0025;) rated their connectivity as &#x201C;bad&#x201D; or &#x201C;very bad&#x201D;. Eight respondents (4&#x0025;) reported not having a mobile internet plan while 4 (2&#x0025;) were unaware whether they did or not. Five participants (2&#x0025;) did not own a smartphone, all of whom were above the age of 45. The primary reasons for not having internet access or a smartphone were expenses and/or lack of interest. Of the five individuals without a smartphone, three had a household member who did own one. Among smartphone owners, 29 respondents (13&#x0025;) reported discomfort in using their smartphones, and 9 respondents (4&#x0025;) were unaware of how to download an app. Additionally, 15 respondents (7&#x0025;) expressed a lack of knowledge regarding any of the most common smartphone apps or features.</p>
<p>When participants were presented with the concept of a healthcare app, 183 participants (96&#x0025;) affirmed that they would use the app if it was available and valuable to them and their families. The majority of respondents expressed willingness to communicate with their healthcare providers (94&#x0025;) and to share their medical information through an app (92&#x0025;). A detailed summary of all the findings is presented in <xref ref-type="table" rid="T2">Table&#x00A0;2</xref>.</p>
<table-wrap id="T2" position="float"><label>Table 2</label>
<caption><p>Summary of respondent answers.</p></caption>
<table frame="hsides" rules="groups">
<colgroup>
<col align="left"/>
<col align="left"/>
<col align="left"/>
<col align="center"/>
<col align="center"/>
<col align="center"/>
</colgroup>
<thead>
<tr>
<th valign="top" align="left">Theme</th>
<th valign="top" align="center">Survey question (<italic>n</italic>&#x2009;&#x003D;&#x2009;total responses)</th>
<th valign="top" align="center">Response option</th>
<th valign="top" align="center">Digital</th>
<th valign="top" align="center">Paper</th>
<th valign="top" align="center">Count</th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" rowspan="25">Digital access</td>
<td valign="top" align="left" rowspan="2">Q1 Internet access at home (<italic>n</italic>&#x2009;&#x003D;&#x2009;209)</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="center">105</td>
<td valign="top" align="center">99</td>
<td valign="top" align="center">204 (98&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">5 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="4">Q2 Internet connectivity rating (<italic>n</italic>&#x2009;&#x003D;&#x2009;203)</td>
<td valign="top" align="left">Very Bad</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Bad</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">3 (1&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Good</td>
<td valign="top" align="center">47</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">82 (40&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Very Good</td>
<td valign="top" align="center">54</td>
<td valign="top" align="center">60</td>
<td valign="top" align="center">114 (56&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="4">Q2.1 <xref ref-type="table-fn" rid="table-fn4">&#x002A;</xref>Reasons for not owning internet connectivity (<italic>n</italic>&#x2009;&#x003D;&#x2009;5)</td>
<td valign="top" align="left">Too expensive</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">4 (80&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Too difficult to use</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0 (0&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No need or interest</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1 (20&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Other</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0 (0&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="2">Q3 Access to a smartphone (<italic>n</italic>&#x2009;&#x003D;&#x2009;209)</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="center">105</td>
<td valign="top" align="center">99</td>
<td valign="top" align="center">204 (98&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">5 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="3">Q4.0 Mobile internet on smartphone plan (<italic>n</italic>&#x2009;&#x003D;&#x2009;203)</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="center">101</td>
<td valign="top" align="center">90</td>
<td valign="top" align="center">191 (94&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">8 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Unsure</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="8">Q4.1 <xref ref-type="table-fn" rid="table-fn4">&#x002A;</xref>Reasons for not owning a smartphone (<italic>n</italic>&#x2009;&#x003D;&#x2009;5)</td>
<td valign="top" align="left">To expensive</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2 (40&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Safety and privacy concerns</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1 (20&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Unaware how to use a smartphone when needed</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1 (20&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">When needed</td>
<td valign="top" align="left"/>
<td valign="top" align="left"/>
<td valign="top" align="center"/>
</tr>
<tr>
<td valign="top" align="left">Access to another smartphone</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1 (20&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">When needed</td>
<td valign="top" align="left"/>
<td valign="top" align="left"/>
<td valign="top" align="center"/>
</tr>
<tr>
<td valign="top" align="left">No need or interest</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">4 (80&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Other</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0 (0&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="2">Q5 Members in household familiar with using smartphones (<italic>n</italic>&#x2009;&#x003D;&#x2009;209)</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="center">104</td>
<td valign="top" align="center">92</td>
<td valign="top" align="center">196 (94&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">13 (6&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="15">Digital familiarity</td>
<td valign="top" align="left" rowspan="4">Q6 Level of comfort using a smartphone (<italic>n</italic>&#x2009;&#x003D;&#x2009;204)</td>
<td valign="top" align="left">Very uncomfortable</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">23 (11&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Uncomfortable</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">6 (3&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Comfortable</td>
<td valign="top" align="center">24</td>
<td valign="top" align="center">35</td>
<td valign="top" align="center">59 (29&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Very comfortable</td>
<td valign="top" align="center">67</td>
<td valign="top" align="center">49</td>
<td valign="top" align="center">116 (57&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="2">Q7 Awareness on how to download an app (<italic>n</italic>&#x2009;&#x003D;&#x2009;201)</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="center">104</td>
<td valign="top" align="center">88</td>
<td valign="top" align="center">192 (96&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">No</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">9 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="9">Q8 <xref ref-type="table-fn" rid="table-fn4">&#x002A;</xref>Smartphone uses in the last month (<italic>n</italic>&#x2009;&#x003D;&#x2009;203)</td>
<td valign="top" align="left">Daily news</td>
<td valign="top" align="center">77</td>
<td valign="top" align="center">69</td>
<td valign="top" align="center">146 (72&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Social media</td>
<td valign="top" align="center">91</td>
<td valign="top" align="center">85</td>
<td valign="top" align="center">176 (87&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Video calls</td>
<td valign="top" align="center">90</td>
<td valign="top" align="center">78</td>
<td valign="top" align="center">168 (83&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Directions</td>
<td valign="top" align="center">86</td>
<td valign="top" align="center">82</td>
<td valign="top" align="center">168 (83&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Email</td>
<td valign="top" align="center">82</td>
<td valign="top" align="center">79</td>
<td valign="top" align="center">161 (79&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Banking</td>
<td valign="top" align="center">71</td>
<td valign="top" align="center">67</td>
<td valign="top" align="center">138 (68&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Internet Searches</td>
<td valign="top" align="center">89</td>
<td valign="top" align="center">87</td>
<td valign="top" align="center">176 (87&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Movies</td>
<td valign="top" align="center">67</td>
<td valign="top" align="center">52</td>
<td valign="top" align="center">119 (59&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">None of the above</td>
<td valign="top" align="center">14</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">15 (7&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="16">Patient readiness</td>
<td valign="top" align="left" rowspan="4">Q9 If this app was available to me, I would likely use it (<italic>n</italic>&#x2009;&#x003D;&#x2009;191)</td>
<td valign="top" align="left">Strongly disagree</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Disagree</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Agree</td>
<td valign="top" align="center">24</td>
<td valign="top" align="center">36</td>
<td valign="top" align="center">60 (31&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Strongly agree</td>
<td valign="top" align="center">63</td>
<td valign="top" align="center">60</td>
<td valign="top" align="center">123 (64&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="4">Q10 This app would be important to my family and I (<italic>n</italic>&#x2009;&#x003D;&#x2009;191)</td>
<td valign="top" align="left">Strongly disagree</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Disagree</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">5 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Agree</td>
<td valign="top" align="center">36</td>
<td valign="top" align="center">46</td>
<td valign="top" align="center">82 (43&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Strongly agree</td>
<td valign="top" align="center">49</td>
<td valign="top" align="center">51</td>
<td valign="top" align="center">100 (62&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="4">Q11 I would be willing to communicate with my doctor online through a mobile health app like this one (<italic>n</italic>&#x2009;&#x003D;&#x2009;191)</td>
<td valign="top" align="left">Strongly disagree</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4 (2&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Disagree</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">7 (4&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Agree</td>
<td valign="top" align="center">28</td>
<td valign="top" align="center">34</td>
<td valign="top" align="center">62 (32&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Strongly agree</td>
<td valign="top" align="center">57</td>
<td valign="top" align="center">61</td>
<td valign="top" align="center">118 (62&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left" rowspan="4">Q12 I would be comfortable with sharing information with my doctor on this mobile health app (<italic>n</italic>&#x2009;&#x003D;&#x2009;191)</td>
<td valign="top" align="left">Strongly disagree</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">6 (3&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Disagree</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">10 (5&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Agree</td>
<td valign="top" align="center">27</td>
<td valign="top" align="center">46</td>
<td valign="top" align="center">73 (38&#x0025;)</td>
</tr>
<tr>
<td valign="top" align="left">Strongly agree</td>
<td valign="top" align="center">53</td>
<td valign="top" align="center">49</td>
<td valign="top" align="center">102 (53&#x0025;)</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="table-fn3"><p>Non-respondents for each question were excluded from the data. For purposes of this table, questions were simplified.</p></fn>
<fn id="table-fn4"><label>&#x002A;</label><p>Multiple responses were permitted</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Overall, 23&#x0025; of respondents were affected by the digital divide to some extent. This was based on 10 people being affected by access, 38 affected by familiarity, and 8 affected by readiness, from the 5 selected questions. There were a total of 10 individuals who belonged to multiple groups, and therefore were only counted once to avoid overlapping results. Consequently, as seen on <xref ref-type="fig" rid="F1">Figure&#x00A0;1</xref>, the classification of the total is as follows: 17&#x0025; due to a lack of access, 68&#x0025; due to a lack of familiarity, and 15&#x0025; based on readiness.</p>
<p>With regards to open-ended questions, the most frequently mentioned concerns related to app usage were security and confidentiality, as identified in 31 out of the 49 short-text responses. For instance, a comment regarding confidentiality is the &#x201C;<italic>Concern over cybersecurity and the app&#x0027;s ability to safeguard private and personal information</italic>&#x201D;. The next most popular concern was the potential impersonal nature of the app, which was included in 7 of the short answer responses. One such comment made regarding this aspect was &#x201C;<italic>I would still always like to have human contact. A machine cannot replace a doctor.</italic>&#x201D; Finally, common participant suggestions for app features included efficient communication with physicians, appointment scheduling, task reminders, access to medical results and, most commonly, user-friendliness and app simplicity. Respectively, some comments made are as follows: suggestions for communication were made, with one participant suggesting: &#x201C;<italic>Being able to send my Doctor messages about changes or updates. Being able to ask questions and have the doctor&#x0027;s responses&#x201D;. Additionally</italic>, concerns regarding digital literacy were raised, with another participant mentioning, &#x201C;<italic>Providing direct access is crucial, especially considering that these apps can become complex for older adults and non-tech savy users</italic>.&#x201D; Moreover, participants stressed the significance of user comfort and ease, as indicated by a comment suggesting that &#x201C;<italic>The app&#x0027;s interface should prioritize clarity and brevity to enhance user experience</italic>.&#x201D; Finally, for features, participants recommended a range of suggestions, including &#x201C;<italic>Offering appointment planning and reminders, providing preparation information, offering condition-specific insights, and including prescription details and instructions on medication usage.</italic>&#x201D;</p>
</sec>
<sec id="s4" sec-type="discussion"><title>Discussion</title>
<p>Digital technologies, such as mobile health apps, may exacerbate health disparities if they overlook digital inclusion in their design. Our study evaluated the digital divide in terms of digital access, familiarity and readiness at a tertiary care institution, particularly regarding mobile health apps, which has not been previously addressed in the literature. We discovered that at least 23&#x0025; of the institution&#x0027;s patient population faces the digital divide. A lack of digital familiarity was the principle barrier measured in this percentage, while the vast majority of respondents had access and had ready attitudes to use mobile health apps. Having this understanding of the extent of each of these barriers will help guide future app developers on where to focus their efforts to improve inclusivity.</p>
<p>In terms of digital access, most families at our pediatric institution had a greater proportion of internet and smartphone access compared to the overall North American population. Specifically, our site had 98&#x0025; access to both internet and smartphones, while the North American average ranged from 85&#x0025; to 95&#x0025; in 2021 (<xref ref-type="bibr" rid="B8">8</xref>, <xref ref-type="bibr" rid="B20">20</xref>). A study in the U.S. revealed that 16&#x0025; of Americans aren&#x0027;t digitally literate, while 19&#x0025; of respondents at our institution reported discomfort in using their smartphones or being unaware of how to download an app (<xref ref-type="bibr" rid="B21">21</xref>). Statistics Canada data showed that 97&#x0025; of individuals between the ages of 25&#x2013;44 have access to a smartphone, whereas 87&#x0025; of those aged 45&#x2013;65 do not (<xref ref-type="bibr" rid="B22">22</xref>). In our study, those who did not own a smartphone in our population were predominantly above the age of 45, similarly indicating that older age is a likely factor for not having access to a smartphone. Additionally, our study found that over half of the individuals without a smartphone had a household member who possessed one, suggesting a potential compensatory approach for the lack of personal access to a smartphone. The results above reveal that our patient population had a high level of digital access, especially compared to the general population. We therefore consider digital access as a minor barrier to health app inclusion.</p>
<p>In our findings, the most remarkable factor, potentially preventing those to benefit from health apps, is the lack of smartphone familiarity. Apps ought to be easy to use, as we find in the literature that health apps with low usability ratings are linked to poor adherence, limiting their impact on patient care, and design issues often lead to patient frustration, reducing their benefit to users (<xref ref-type="bibr" rid="B10">10</xref>, <xref ref-type="bibr" rid="B11">11</xref>). Among the short text responses, the importance of ease of use in health apps was strongly emphasized by our participants, suggesting that simplicity should take precedence over multi-functionality in app development. This also suggests the need for technical onboarding and app tutorials for first time users as well as piloting the app to assess its perceived ease of use.</p>
<p>In order to address the lack of digital familiarity among users, app usability should be properly assessed. In a systematic review of 33 studies evaluating the usability of mHealth apps, it has been found that current app reviews for usability are substandard (<xref ref-type="bibr" rid="B2">2</xref>). Many surveys focus on assessing satisfaction rather than usability. Methodologies of assessing the usability were considered poor, using self-made questionnaires, and having conflict of interests. An example of a reliable validated tool to evaluate health app usability is the mHealth App Usability Questionnaire (MAUQ) (<xref ref-type="bibr" rid="B23">23</xref>).</p>
<p>In order to characterize users&#x0027; level of comfort, another study in the literature used an interesting method where participants were inquired about their expectations of health apps (<xref ref-type="bibr" rid="B24">24</xref>). This specifically included asking about desired features, intentions to use, perceived aesthetics, ease of use, and usefulness of health apps, all of which can be dependent on a person&#x0027;s digital skills or comfort. They were then presented with apps that varied in similarity to their expectations, ranging from low to high. The study found that health apps that matched user expectations increased their willingness to adopt them and their perception of value during actual use. This underscores the importance for app developers to evaluate the expectations of their target audiences in order to meet their needs effectively in the design considerations.</p>
<p>Despite facing various barriers related to digital access and familiarity, nearly all respondents expressed their willingness to use a mobile health app if it were available, as evident from their responses in the readiness domain. This observation highlights that individuals affected by the digital divide display a strong inclination toward digital health participation. However, this finding is assumed to be on the premise of an ideal mobile health app perceived by the responders, with the app&#x0027;s usability and functions meeting their expectations. It is therefore important to understand the concerns and suggestions patients made regarding such apps.</p>
<p>In our study, we collected interests and concerns related to health apps from respondents at our tertiary care institution in order to tailor future apps to their needs and increase overall app use. Comparing our results to previous studies, we found similar perspectives/attitudes among participants regarding the engagement with mobile health apps. In our study, concerns related to security, privacy, and ease of use were consistently mentioned, reflecting the importance of addressing these aspects in app development. Studies have shown that patients often lack trust in health apps and other online portals (<xref ref-type="bibr" rid="B12">12</xref>). Digital literacy also plays a crucial role in understanding security policy complexities (<xref ref-type="bibr" rid="B22">22</xref>, <xref ref-type="bibr" rid="B25">25</xref>). A systematic review of factors contributing to limited patient use of health apps suggests that a lack of trust and clinical support for mobile apps pose significant barriers to patient engagement (<xref ref-type="bibr" rid="B6">6</xref>). Meanwhile, physician recommendations and clinical endorsements of health apps have been shown to increase patient interest and confidence in using them (<xref ref-type="bibr" rid="B12">12</xref>, <xref ref-type="bibr" rid="B15">15</xref>, <xref ref-type="bibr" rid="B16">16</xref>). App developers should be totally aware of this potential barrier for users. Ultimately, strengthening app security, addressing user safety during recruitment, and seeking healthcare provider endorsements can help overcome confidence barriers and narrow the digital divide.</p>
<p>A study measuring factors impacting the use of health apps found that patients reported that their likelihood of using such apps is also influenced by their perceived benefits or risks and not solely by usability (<xref ref-type="bibr" rid="B12">12</xref>). In our study, we gathered patient recommendations for what they believe are important app features. These included having a communication platform with their physicians, the option for appointment booking, task reminders such as for their treatments, and access to their medical results. We found that patients most commonly requested the apps be user-friendly and simple. In order to maximize the use and perceived importance of a health app, it is important to consider the value it has for patients, otherwise, it can be considered a burden to use.</p>
<p>In the context of pediatrics, mobile health apps have successfully shown to help preoperative and postoperative stress in pediatric patients (<xref ref-type="bibr" rid="B26">26</xref>). Meanwhile, these apps often prioritize caregivers over pediatric patients (<xref ref-type="bibr" rid="B27">27</xref>). This approach aligns with efforts to promote digital inclusion, recognizing that a child&#x0027;s access to health apps is heavily influenced by socio-economic factors, including internet access and device availability (<xref ref-type="bibr" rid="B26">26</xref>). Consequently, minors typically rely on caregivers&#x0027; devices and internet access for app usage.</p>
<p>In our study, respondents emphasized their concern regarding the impersonal nature that health apps may introduce. This concern is particularly significant in pediatrics, where the doctor-patient relationship plays a crucial role in improving pediatric health outcomes (<xref ref-type="bibr" rid="B28">28</xref>). Health app developers ought to be mindful of this aspect, ensuring that their apps facilitate personal connections between physicians and patients, rather than replacing or diminishing the importance of this relationship.</p>
<p>Although our study did not inspect epidemiological correlations, it is worth noting that a recent systematic review of digital disparities during the COVID-19 pandemic highlighted lower digital skill sets among minority groups and the elderly (<xref ref-type="bibr" rid="B29">29</xref>). Disparities in digital access were also found to be influenced by factors such as race, minority status, and income group (<xref ref-type="bibr" rid="B30">30</xref>).</p>
<p>There are several limitations to our study. Firstly, being a survey-based study, it had a limited sample size and was susceptible to selection bias, as those who chose to fill out the survey may not be representative of the entire study population, especially outside urban tertiary care facilities. Furthermore, the survey was only offered in English and French, which may have excluded individuals who are not proficient in either of these languages. Further research is needed to identify the digital inclusion needs of families who face language barriers, as they may already experience disparities in traditional healthcare access.</p>
<p>It is worth acknowledging that the actual number of people affected by the digital divide may be higher than our estimation. This discrepancy can arise because we selected questions with unambiguous responses when estimating the number of people affected. For example, our calculations include only individuals with no access to the internet, while in reality, those with very poor connectivity may also be impacted by the digital divide but were not accounted for in our estimation.</p>
<p>In conclusion, this study evaluated the digital divide based on access to digital technologies, familiarity with their use, and willingness to use them for health purposes. As a result, we found that nearly a quarter of patrons at our tertiary care pediatric institution face at least one barrier to using a mobile app for health. Additionally, the study identified the values and preferences of parents or caregivers of pediatric patients when deciding to use a health app, including the desire for a simple and secure app with specific features. Being informed with this information, health app developers can better understand how to enhance the usability and relevance of their apps, ultimately bridging the digital divide and promoting equitable healthcare access.</p>
</sec>
</body>
<back>
<sec id="s6" sec-type="data-availability"><title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/Supplementary Material, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec id="s7" sec-type="author-contributions"><title>Author contributions</title>
<p>MC: Methodology, Project administration, Writing &#x2013; original draft, Writing &#x2013; review &#x0026; editing. ZR: Methodology, Project administration, Writing &#x2013; original draft, Writing &#x2013; review &#x0026; editing. KS: Methodology, Project administration, Writing &#x2013; review &#x0026; editing. EG: Methodology, Project administration, Writing &#x2013; review &#x0026; editing. EO: Methodology, Project administration, Writing &#x2013; review &#x0026; editing. DP: Methodology, Project administration, Supervision, Writing &#x2013; review &#x0026; editing.</p>
</sec>
<sec id="s8" sec-type="funding-information"><title>Funding</title>
<p>The authors declare that no financial support was received for the research, authorship, and/or publication of this article.</p>
</sec>
<sec id="s9" sec-type="COI-statement"><title>Conflict of interest</title>
<p>DP and EG are co-founders of Children&#x0027;s Journey. This is a non-financially incentivized start-up that is indirectly associated with our study.</p>
<p>The remaining authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec id="s10" sec-type="disclaimer"><title>Publisher&#x0027;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<ref-list><title>References</title>
<ref id="B1"><label>1.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Timmers</surname><given-names>T</given-names></name><name><surname>Janssen</surname><given-names>L</given-names></name><name><surname>Kool</surname><given-names>RB</given-names></name><name><surname>Kremer</surname><given-names>JA</given-names></name></person-group>. <article-title>Educating patients by providing timely information using smartphone and tablet apps: systematic review</article-title>. <source>J Med Internet Res</source>. (<year>2020</year>) <volume>22</volume>(<issue>4</issue>):<fpage>e17342</fpage>. <pub-id pub-id-type="doi">10.2196/17342</pub-id><pub-id pub-id-type="pmid">32281936</pub-id></citation></ref>
<ref id="B2"><label>2.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Patel</surname><given-names>B</given-names></name><name><surname>Thind</surname><given-names>A</given-names></name></person-group>. <article-title>Usability of mobile health apps for postoperative care: systematic review</article-title>. <source>JMIR Perioper Med</source>. (<year>2020</year>) <volume>3</volume>(<issue>2</issue>):<fpage>e19099</fpage>. <pub-id pub-id-type="doi">10.2196/19099</pub-id><pub-id pub-id-type="pmid">33393925</pub-id></citation></ref>
<ref id="B3"><label>3.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Veinot</surname><given-names>TC</given-names></name><name><surname>Mitchell</surname><given-names>H</given-names></name><name><surname>Ancker</surname><given-names>JS</given-names></name></person-group>. <article-title>Good intentions are not enough: how informatics interventions can worsen inequality</article-title>. <source>J Am Med Inform Assoc</source>. (<year>2018</year>) <volume>25</volume>(<issue>8</issue>):<fpage>1080</fpage>&#x2013;<lpage>8</lpage>. <pub-id pub-id-type="doi">10.1093/jamia/ocy052</pub-id><pub-id pub-id-type="pmid">29788380</pub-id></citation></ref>
<ref id="B4"><label>4.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mackert</surname><given-names>M</given-names></name><name><surname>Mabry-Flynn</surname><given-names>A</given-names></name><name><surname>Champlin</surname><given-names>S</given-names></name><name><surname>Donovan</surname><given-names>EE</given-names></name><name><surname>Pounders</surname><given-names>K</given-names></name></person-group>. <article-title>Health literacy and health information technology adoption: the potential for a new digital divide</article-title>. <source>J Med Internet Res</source>. (<year>2016</year>) <volume>18</volume>(<issue>10</issue>):<fpage>e264</fpage>. <pub-id pub-id-type="doi">10.2196/jmir.6349</pub-id><pub-id pub-id-type="pmid">27702738</pub-id></citation></ref>
<ref id="B5"><label>5.</label><citation citation-type="other"><comment>Dictionary.com. Digital divide definition &#x0026; meaning. (2022). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www.dictionary.com/browse/digital-divide">https://www.dictionary.com/browse/digital-divide</ext-link> <comment>(Accessed November 8, 2022)</comment>.</citation></ref>
<ref id="B6"><label>6.</label><citation citation-type="other"><comment>Benton Institute for Broadband &#x0026; Society. The Digital Skill Divide. (2023). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www.benton.org/blog/digital-skill-divide#:~:text=The%20digital%20skill%20divide%20is,and%20those%20who%20do%20not">https://www.benton.org/blog/digital-skill-divide#:~:text=The%20digital%20skill%20divide%20is,and%20those%20who%20do%20not</ext-link> <comment>(Accessed March 22, 2024)</comment>.</citation></ref>
<ref id="B7"><label>7.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>O&#x0027;Connor</surname><given-names>S</given-names></name><name><surname>Hanlon</surname><given-names>P</given-names></name><name><surname>O&#x0027;Donnell</surname><given-names>CA</given-names></name><name><surname>Garcia</surname><given-names>S</given-names></name><name><surname>Glanville</surname><given-names>J</given-names></name><name><surname>Mair</surname><given-names>FS</given-names></name></person-group>. <article-title>Understanding factors affecting patient and public engagement and recruitment to digital health interventions: a systematic review of qualitative studies</article-title>. <source>BMC Med Inform Decis Mak</source>. (<year>2016</year>) <volume>16</volume>(<issue>1</issue>):<fpage>120</fpage>. <pub-id pub-id-type="doi">10.1186/s12911-016-0359-3</pub-id></citation></ref>
<ref id="B8"><label>8.</label><citation citation-type="other"><person-group person-group-type="author"><name><surname>Greenwood</surname><given-names>S</given-names></name></person-group>. <comment>&#x201C;Mobile technology and home broadband 2021,&#x201D; (2021). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www.pewresearch.org/internet/2021/06/03/mobile-technology-and-home-broadband-2021/">https://www.pewresearch.org/internet/2021/06/03/mobile-technology-and-home-broadband-2021/</ext-link> <comment>(Accessed June 22, 2021)</comment>.</citation></ref>
<ref id="B9"><label>9.</label><citation citation-type="other"><collab>Pew Research Center</collab>. <comment>Mobile fact sheet. Washington, DC (2017). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="http://www.pewinternet.org/fact-sheet/mobile/">http://www.pewinternet.org/fact-sheet/mobile/</ext-link> <comment>(Accessed January 15, 2017)</comment>.</citation></ref>
<ref id="B10"><label>10.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Sarkar</surname><given-names>U</given-names></name><name><surname>Gourley</surname><given-names>GI</given-names></name><name><surname>Lyles</surname><given-names>CR</given-names></name><name><surname>Tieu</surname><given-names>L</given-names></name><name><surname>Clarity</surname><given-names>C</given-names></name><name><surname>Newmark</surname><given-names>L</given-names></name><etal/></person-group> <article-title>Usability of commercially available mobile applications for diverse patients</article-title>. <source>J Gen Intern Med</source>. (<year>2016</year>) <volume>31</volume>(<issue>12</issue>):<fpage>1417</fpage>&#x2013;<lpage>26</lpage>. <pub-id pub-id-type="doi">10.1007/s11606-016-3771-6</pub-id><pub-id pub-id-type="pmid">27418347</pub-id></citation></ref>
<ref id="B11"><label>11.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Meirte</surname><given-names>J</given-names></name><name><surname>Hellemans</surname><given-names>N</given-names></name><name><surname>Anthonissen</surname><given-names>M</given-names></name><name><surname>Denteneer</surname><given-names>L</given-names></name><name><surname>Maertens</surname><given-names>K</given-names></name><name><surname>Moortgat</surname><given-names>P</given-names></name><etal/></person-group> <article-title>Benefits and disadvantages of electronic patient-reported outcome measures: systematic review</article-title>. <source>JMIR Perioper Med</source>. (<year>2020</year>) <volume>3</volume>(<issue>1</issue>):<fpage>e15588</fpage>. <pub-id pub-id-type="doi">10.2196/15588</pub-id><pub-id pub-id-type="pmid">33393920</pub-id></citation></ref>
<ref id="B12"><label>12.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Scott</surname><given-names>AR</given-names></name><name><surname>Alore</surname><given-names>EA</given-names></name><name><surname>Naik</surname><given-names>AD</given-names></name><name><surname>Berger</surname><given-names>DH</given-names></name><name><surname>Suliburk</surname><given-names>JW</given-names></name></person-group>. <article-title>Mixed-Methods analysis of factors impacting use of a postoperative mHealth app</article-title>. <source>JMIR Mhealth Uhealth</source>. (<year>2017</year>) <volume>5</volume>(<issue>2</issue>):<fpage>e11</fpage>. <pub-id pub-id-type="doi">10.2196/mhealth.6728</pub-id><pub-id pub-id-type="pmid">28179215</pub-id></citation></ref>
<ref id="B13"><label>13.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Semple</surname><given-names>JL</given-names></name><name><surname>Armstrong</surname><given-names>KA</given-names></name></person-group>. <article-title>Mobile applications for postoperative monitoring after discharge</article-title>. <source>CMAJ</source>. (<year>2017</year>) <volume>189</volume>(<issue>1</issue>):<fpage>E22</fpage>&#x2013;<lpage>4</lpage>. <pub-id pub-id-type="doi">10.1503/cmaj.160195</pub-id><pub-id pub-id-type="pmid">27920015</pub-id></citation></ref>
<ref id="B14"><label>14.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Nielsen</surname><given-names>AS</given-names></name><name><surname>Kidholm</surname><given-names>K</given-names></name><name><surname>Kayser</surname><given-names>L</given-names></name></person-group>. <article-title>Patients&#x2019; reasons for non-use of digital patient-reported outcome concepts: a scoping review</article-title>. <source>Health Inform J</source>. (<year>2020</year>) <volume>26</volume>(<issue>4</issue>):<fpage>1460458220942649</fpage>. <pub-id pub-id-type="doi">10.1177/1460458220942649</pub-id></citation></ref>
<ref id="B15"><label>15.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Szinay</surname><given-names>D</given-names></name><name><surname>Jones</surname><given-names>A</given-names></name><name><surname>Chadborn</surname><given-names>T</given-names></name><name><surname>Brown</surname><given-names>J</given-names></name><name><surname>Naughton</surname><given-names>F</given-names></name></person-group>. <article-title>Influences on the uptake of and engagement with health and well-being smartphone apps: systematic review</article-title>. <source>J Med Internet Res</source>. (<year>2020</year>) <volume>22</volume>(<issue>5</issue>):<fpage>e17572</fpage>. <pub-id pub-id-type="doi">10.2196/17572</pub-id><pub-id pub-id-type="pmid">32348255</pub-id></citation></ref>
<ref id="B16"><label>16.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Peacock</surname><given-names>S</given-names></name><name><surname>Reddy</surname><given-names>A</given-names></name><name><surname>Leveille</surname><given-names>SG</given-names></name><name><surname>Walker</surname><given-names>J</given-names></name><name><surname>Payne</surname><given-names>TH</given-names></name><name><surname>Oster</surname><given-names>NV</given-names></name><etal/></person-group> <article-title>Patient portals and personal health information online: perception, access, and use by US adults</article-title>. <source>J Am Med Inform Assoc</source>. (<year>2017</year>) <volume>24</volume>(<issue>e1</issue>):<fpage>e173</fpage>&#x2013;<lpage>7</lpage>. <pub-id pub-id-type="doi">10.1093/jamia/ocw095</pub-id><pub-id pub-id-type="pmid">27413120</pub-id></citation></ref>
<ref id="B17"><label>17.</label><citation citation-type="other"><collab>Statistics Canada</collab>. <comment>Canadian internet use survey (2020). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www23.statcan.gc.ca/imdb/p3Instr.pl?Function=assembleInstr&#x0026;lang=en&#x0026;Item_Id=1289522#qb1290345">https://www23.statcan.gc.ca/imdb/p3Instr.pl?Function&#x003D;assembleInstr&#x0026;lang&#x003D;en&#x0026;Item_Id&#x003D;1289522&#x0023;qb1290345</ext-link> <comment>(Accessed July 15, 2021)</comment>.</citation></ref>
<ref id="B18"><label>18.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kayser</surname><given-names>L</given-names></name><name><surname>Karnoe</surname><given-names>A</given-names></name><name><surname>Furstrand</surname><given-names>D</given-names></name><name><surname>Batterham</surname><given-names>R</given-names></name><name><surname>Christensen</surname><given-names>K</given-names></name><name><surname>Elsworth</surname><given-names>G</given-names></name><etal/></person-group> <article-title>&#x201C;A multidimensional tool based on the eHealth literacy framework: development and initial validity testing of the eHealth literacy questionnaire&#x201D; (eHLQ)</article-title>. <source>J Med Internet Res</source>. (<year>2018</year>) <volume>20</volume>(<issue>2</issue>):<fpage>e36</fpage>. <pub-id pub-id-type="doi">10.2196/jmir.8371</pub-id><pub-id pub-id-type="pmid">29434011</pub-id></citation></ref>
<ref id="B19"><label>19.</label><citation citation-type="other"><collab>EBCD: Experience-based co-design toolkit</collab>. <comment>(n.d). The point of care foundation. Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www.pointofcarefoundation.org.uk/resource/experience-based-co-design-ebcd-toolkit/">https://www.pointofcarefoundation.org.uk/resource/experience-based-co-design-ebcd-toolkit/</ext-link> <comment>(Accessed March 22, 2024).</comment></citation></ref>
<ref id="B20"><label>20.</label><citation citation-type="other"><collab>Government of Canada, Statistics Canada</collab>. <comment>&#x201C;Access to the internet in Canada, 2020,&#x201D; (2021). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://www150.statcan.gc.ca/n1/daily-quotidien/210531/dq210531d-eng.htm">https://www150.statcan.gc.ca/n1/daily-quotidien/210531/dq210531d-eng.htm</ext-link> <comment>(Accessed June 29, 2021)</comment>.</citation></ref>
<ref id="B21"><label>21.</label><citation citation-type="other"><person-group person-group-type="author"><name><surname>Pawlowski</surname><given-names>E</given-names></name><name><surname>Hudson</surname><given-names>L</given-names></name></person-group>. <comment>&#x201C;A description of US adults who are not digitally literate,&#x201D; NCES stats in brief, no. 2018-161, Washington: National Center for Education Statistics (2018). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://nces.ed.gov/pubsearch/pubsinfo.asp?pubid=2018161">https://nces.ed.gov/pubsearch/pubsinfo.asp?pubid&#x003D;2018161</ext-link> <comment>(Accessed June 15, 2021)</comment>.</citation></ref>
<ref id="B22"><label>22.</label><citation citation-type="other"><collab>Statistics Canada</collab>. <comment>Table 22-10-0113-01, use of internet services and technologies by age group and household income quartile (2019). (Accessed July 15, 2021).</comment> <pub-id pub-id-type="doi">10.25318/2210011301-eng</pub-id></citation></ref>
<ref id="B23"><label>23.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zhou</surname><given-names>L</given-names></name><name><surname>Bao</surname><given-names>J</given-names></name><name><surname>Setiawan</surname><given-names>IMA</given-names></name><name><surname>Saptono</surname><given-names>A</given-names></name><name><surname>Parmanto</surname><given-names>B</given-names></name></person-group>. <article-title>The mHealth app usability questionnaire (MAUQ): development and validation study</article-title>. <source>JMIR Mhealth Uhealth</source>. (<year>2019</year>) <volume>7</volume>(<issue>4</issue>):<fpage>e11500</fpage>. <pub-id pub-id-type="doi">10.2196/11500</pub-id><pub-id pub-id-type="pmid">30973342</pub-id></citation></ref>
<ref id="B24"><label>24.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lazard</surname><given-names>AJ</given-names></name><name><surname>Babwah Brennen</surname><given-names>JS</given-names></name><name><surname>Belina</surname><given-names>SP</given-names></name></person-group>. <article-title>App designs and interactive features to increase mHealth adoption: user expectation survey and experiment</article-title>. <source>JMIR Mhealth Uhealth</source>. (<year>2021</year>) <volume>9</volume>(<issue>11</issue>):<fpage>e29815</fpage>. <pub-id pub-id-type="doi">10.2196/29815</pub-id><pub-id pub-id-type="pmid">34734829</pub-id></citation></ref>
<ref id="B25"><label>25.</label><citation citation-type="other"><person-group person-group-type="author"><name><surname>Pawlowski</surname><given-names>E</given-names></name><name><surname>Hudson</surname><given-names>L</given-names></name></person-group>. <comment>&#x201C;A description of US adults who are not digitally literate.&#x201D; NCES stats in brief, no. 2018-161. Washington: National Center for Education Statistics (2018). Available online at:</comment> <ext-link ext-link-type="uri" xlink:href="https://nces.ed.gov/pubsearch/pubsinfo.asp?pubid=2018161">https://nces.ed.gov/pubsearch/pubsinfo.asp?pubid&#x003D;2018161</ext-link> <comment>(Accessed June 29, 2021)</comment>.</citation></ref>
<ref id="B26"><label>26.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rantala</surname><given-names>A</given-names></name><name><surname>Pikkarainen</surname><given-names>M</given-names></name><name><surname>Miettunen</surname><given-names>J</given-names></name><name><surname>He</surname><given-names>H-G</given-names></name><name><surname>P&#x00F6;lkki</surname><given-names>T</given-names></name></person-group>. <article-title>The effectiveness of web-based mobile health interventions in paediatric outpatient surgery: a systematic review and meta-analysis of randomized controlled trials</article-title>. <source>J Adv Nurs</source>. (<year>2020</year>) <volume>76</volume>(<issue>8</issue>):<fpage>1949</fpage>&#x2013;<lpage>60</lpage>. <pub-id pub-id-type="doi">10.1111/jan.14381</pub-id><pub-id pub-id-type="pmid">32281673</pub-id></citation></ref>
<ref id="B27"><label>27.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Nguyen</surname><given-names>N</given-names></name><name><surname>Leveille</surname><given-names>E</given-names></name><name><surname>Guadagno</surname><given-names>E</given-names></name><name><surname>Kalisya</surname><given-names>LM</given-names></name><name><surname>Poenaru</surname><given-names>D</given-names></name></person-group>. <article-title>Use of mobile health technologies for postoperative care in paediatric surgery: a systematic review</article-title>. <source>J Telemed Telecare</source>. (<year>2020</year>) <volume>28</volume>(<issue>5</issue>):<fpage>1357633X20934682</fpage>. <pub-id pub-id-type="doi">10.1177/1357633X20934682</pub-id></citation></ref>
<ref id="B28"><label>28.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rackley</surname><given-names>S</given-names></name><name><surname>Bostwick</surname><given-names>JM</given-names></name></person-group>. <article-title>The pediatric surgeon-patient relationship</article-title>. <source>Semin Pediatr Surg</source>. (<year>2013</year>) <volume>22</volume>(<issue>3</issue>):<fpage>124</fpage>&#x2013;<lpage>8</lpage>. <pub-id pub-id-type="doi">10.1053/j.sempedsurg.2013.04.002</pub-id><pub-id pub-id-type="pmid">23870204</pub-id></citation></ref>
<ref id="B29"><label>29.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Litchfield</surname><given-names>I</given-names></name><name><surname>Shukla</surname><given-names>D</given-names></name><name><surname>Greenfield</surname><given-names>S</given-names></name></person-group>. <article-title>Impact of COVID-19 on the digital divide: a rapid review</article-title>. <source>BMJ Open</source>. (<year>2021</year>) <volume>11</volume>(<issue>8</issue>):<fpage>e053440</fpage>. <pub-id pub-id-type="doi">10.1136/bmjopen-2021-053440</pub-id><pub-id pub-id-type="pmid">34642200</pub-id></citation></ref>
<ref id="B30"><label>30.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kan</surname><given-names>K</given-names></name><name><surname>Heard-Garris</surname><given-names>N</given-names></name><name><surname>Bendelow</surname><given-names>A</given-names></name><name><surname>Morales</surname><given-names>L</given-names></name><name><surname>Lewis-Thames</surname><given-names>MW</given-names></name><name><surname>Davis</surname><given-names>MM</given-names></name><etal/></person-group> <article-title>Examining access to digital technology by race and ethnicity and child health Status among Chicago families</article-title>. <source>JAMA Netw Open</source>. (<year>2022</year>) <volume>5</volume>(<issue>8</issue>):<fpage>e2228992</fpage>. <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2022.28992</pub-id><pub-id pub-id-type="pmid">36018593</pub-id></citation></ref></ref-list>
<app-group><app id="app1"><title>Appendix 1. Administered Questionnaire</title>
<sec id="s11">
<title/>
<sec id="s11a"><title>Internet access and smartphone use of patient caretakers</title>
<p>The purpose of this survey is to understand your readiness and access to digital devices, such as with the internet and cell phones. Your participation will help create a tool that improves the communication between families and pediatric care teams. We value your involvement as a patient or caregiver at the Montreal Children&#x0027;s Hospital.</p>
<p>The questionnaire is anonymous and voluntary: we will not know which responses are yours and you may stop responding at any time. <italic>By completing this questionnaire, you acknowledge that you have read, understood, and agreed with the above information. Your choice to participate or not will not affect the care that you or your child(ren) receive at this hospital</italic>.</p>
<p>If you have any questions about this research project, please contact the lead clinician: Dr. Dan Poenaru&#x2014;<email>dan.poenaru@mcgill.ca</email>. The survey has 19 questions and should take 10&#x2005;min to complete.</p>
<p>You may choose to complete this questionnaire online. To do so, open the Camera app on your phone and point the camera towards this image:</p>
<p><inline-graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="fdgth-06-1382507-i001.tif"/></p>
<p>Useful terms:</p>
<p>A <bold>Cell or Mobile Phone</bold> is a handheld device that can make and receive calls. These phones have a number pad or keyboard (for example: flip phone or Nokia).</p>
<p>A <bold>Smartphone</bold> is a type of cell phone that has a touch screen, is able to use the internet for looking things up online and that you can watch videos or play games (for example: iPhone, Android, Google Phone).</p>
<p>A <bold>Mobile Health App</bold> is a health related service offered on a smartphone. It can be used for communicating with a doctor, recording diets, measuring heart rate or blood sugar, fitness/exercising and medication reminders.</p>
<p><bold>A. Digital Access&#x2014;We would like to know about your access to the internet and to a smartphone.</bold></p>
<p>1. Do you have internet access at home?</p>
<table-wrap id="T3" position="float">
<table frame="hsides" rules="groups">
<colgroup>
<col align="left"/>
<col align="left"/>
</colgroup>
<tbody>
<tr>
<td valign="top" align="left">&#x25A2; Yes</td>
<td valign="top" align="left">&#x25A2; No</td>
</tr>
<tr>
<td valign="top" align="left">2. <italic>If Yes:</italic> How would you rate your internet connectivity (speed, stability, etc.)?<break/>&#x25A2; Very bad<break/>&#x25A2; Bad<break/>&#x25A2; Good<break/>&#x25A2; Very good</td>
<td valign="top" align="left">2. <italic>If No:</italic> What are the reasons for not having access to the internet? <italic>Check all that apply:</italic><break/>&#x25A2; Too expensive<break/>&#x25A2; Too difficult to use<break/>&#x25A2; No need or interest<break/>&#x25A2; Other: _____________</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>3. Do you have a smartphone (example: iPhone, Android, Samsung Galaxy, Google Phone, etc.)?</p>
<table-wrap id="T4" position="float">
<table frame="hsides" rules="groups">
<colgroup>
<col align="left"/>
<col align="left"/>
</colgroup>
<tbody>
<tr>
<td valign="top" align="left">&#x25A2; Yes</td>
<td valign="top" align="left">&#x25A2; No</td>
</tr>
<tr>
<td valign="top" align="left"><italic>4. If Yes:</italic> Do you have Mobile Internet (cellular data) on your smartphone plan?<break/>&#x25A2; Yes<break/>&#x25A2; No<break/>&#x25A2; I am unsure</td>
<td valign="top" align="left"><italic>4. If No:</italic> What are the reasons for not owning a smartphone? <italic>Check all that apply:</italic><break/>&#x25A2; Too expensive<break/>&#x25A2; I&#x2019;m concerned about data safety and privacy<break/>&#x25A2; I don&#x2019;t know how to use a smartphone<break/>&#x25A2; I use someone else&#x0027;s smartphone if needed<break/>&#x25A2; No need or interest<break/>&#x25A2; Other: _________________</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>5. Do you have other members in your household who are familiar with using smartphones?</p>
<p>&#x25A2; Yes &#x25A2; No</p>
<p><bold>B. Digital Skills &#x0026; Familiarity&#x2014;We would like to know how well you can use a smartphone.</bold></p>
<p><italic>If you do not own a smartphone, continue to Section C</italic>.</p>
<p>6. How comfortable do you feel when you use a smartphone? <italic>Mark your answer on the scale below:</italic></p>
<p>&#x25A2; 1 - Very uncomfortable &#x25A2; 2 - Uncomfortable &#x25A2; 3 - Comfortable &#x25A2; 4 - Very comfortable</p>
<p>7. Do you know how to download an App on a smartphone?</p>
<p>&#x25A2; Yes &#x25A2; No</p>
<p>8. In the last month, what have you used your smartphone for? <italic>Check off all that apply:</italic></p>
<p>&#x25A2; Daily news &#x25A2; Social media &#x25A2; Video calls &#x25A2; Directions &#x25A2; Email</p>
<p>&#x25A2; Banking &#x25A2; Internet searches &#x25A2; Movies &#x25A2; None of the above</p>
<p><bold>C. Patient perspectives&#x2014;We would like to know your opinions on the following:</bold></p>
<p>The Department of Pediatrics at Montreal Children&#x0027;s Hospital is developing a smartphone App to improve communication around the experience of medical or surgical care. We hope that it will decrease anxiety and increase the comfort of patients and their caregivers.</p>
<p>The app will:
<list list-type="simple">
<list-item><label>1)</label><p>Give parents/caregivers access to communicate directly with their medical or surgical team</p></list-item>
<list-item><label>2)</label><p>Help with planning and providing reminders for appointments</p></list-item>
<list-item><label>3)</label><p>Provide educational information on relevant medical/surgical conditions</p></list-item>
</list><italic>Please rate your level of agreement with the sentences below, using a scale from 1 to 4:</italic></p>
<p>9. If this app was available to me, I would likely use it.</p>
<p>&#x25A2; 1 - Strongly disagree &#x25A2; 2 - Disagree &#x25A2; 3 - Agree &#x25A2; 4 - Strongly agree</p>
<p>10. This app would be important to me or my family.</p>
<p>&#x25A2; 1 - Strongly disagree &#x25A2; 2 - Disagree &#x25A2; 3 - Agree &#x25A2; 4 - Strongly agree</p>
<p>11. I would be willing to communicate with my doctor online through a mobile health app like this one.</p>
<p>&#x25A2; 1 - Strongly disagree &#x25A2; 2 - Disagree &#x25A2; 3 - Agree &#x25A2; 4 - Strongly agree</p>
<p>12. I would be comfortable sharing medical information with my doctor on this mobile health app.</p>
<p>&#x25A2; 1 - Strongly disagree &#x25A2; 2 - Disagree &#x25A2; 3 - Agree &#x25A2; 4 - Strongly agree</p>
<p>13. Are there any concerns you have about this app?</p>
<p><inline-graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="fdgth-06-1382507-i002.tif"/></p>
<p>14. What features would you like to see in this app?</p>
<p><inline-graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="fdgth-06-1382507-i003.tif"/></p>
<p><bold>D. Personal Information&#x2014;We would like to know more about you.</bold></p>
<p><italic>We&#x0027;d like to remind you that this survey is anonymous. We will not know which responses are yours</italic>.</p>
<p>15. Which age group do you belong to?</p>
<p>&#x25A2; 14&#x2013;17 &#x25A2; 18&#x2013;24 &#x25A2; 25&#x2013;34 &#x25A2; 35&#x2013;44 &#x25A2; 45&#x2013;54 &#x25A2; 55&#x2013;64 &#x25A2; 65&#x2013;74 &#x25A2; 75 or over</p>
<p>16. Which of the following best describes your employment status at the present time? <italic>If you are on sabbatical, maternity leave, sick leave or work-related accident leave, indicate whether you usually work full-time or part-time</italic>.</p>
<p>&#x25A2; I work full-time (over 30&#x2005;h/week) &#x25A2; I work part-time (under 30&#x2005;h/week)</p>
<p>&#x25A2; I am unemployed &#x25A2; I am retired</p>
<p>&#x25A2; I am a student &#x25A2; I prefer not to answer</p>
<p>&#x25A2; Other: ________________</p>
<p>17. What is the highest level of education you have completed?</p>
<p>&#x25A2; High School Certificate or Equivalent</p>
<p>&#x25A2; Undergraduate Degree (BA, BSc, etc.)</p>
<p>&#x25A2; Postgraduate Degree (Masters, PhD, MD, etc.)</p>
<p>&#x25A2; No certificate, diploma, or degree</p>
<p>&#x25A2; I prefer not to answer</p>
<p>&#x25A2; Other: _____________</p>
<p>18. What is your preferred language of communication?</p>
<p>&#x25A2; English &#x25A2; French &#x25A2; Other: __________</p>
<p>19. What are the first three characters of your postal code? _____________</p>
<p><italic>Thank you for taking the time to complete this survey! We truly value the information you have provided&#x2014;your responses will help improve surgeons&#x0027; communication with children and their close ones</italic>.</p>
<p>Would you like to be part of the team by sharing your expertise as a patient or caregiver? If so, we will invite you to meet with our team and help us design a user-friendly app for patients using the results of this survey.</p>
<p>If so, please enter your email address or phone number for us to contact you: ______________________________.</p>
</sec>
</sec></app>
</app-group>
</back>
</article>