<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JRAT</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Rehabil Assist Technol</journal-id>
      <journal-title>JMIR Rehabilitation and Assistive Technologies</journal-title>
      <issn pub-type="epub">2369-2529</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">v8i1e19519</article-id>
      <article-id pub-id-type="pmid">33734090</article-id>
      <article-id pub-id-type="doi">10.2196/19519</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Using a Web-Based App to Deliver Rehabilitation Strategies to Persons With Chronic Conditions: Development and Usability Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Griffith</surname>
            <given-names>Janessa</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Stara</surname>
            <given-names>Vera</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Navarra</surname>
            <given-names>Ann-Margaret</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Richardson</surname>
            <given-names>Julie</given-names>
          </name>
          <degrees>BSc, MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>School of Rehabilitation Science</institution>
            <institution>Faculty of Health Sciences</institution>
            <institution>McMaster University</institution>
            <addr-line>1400 Main Street West</addr-line>
            <addr-line>IAHS Room 403</addr-line>
            <addr-line>Hamilton, ON, L8S 1C7</addr-line>
            <country>Canada</country>
            <phone>1 905 525 9140 ext 27811</phone>
            <email>jrichard@mcmaster.ca</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6356-0492</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Letts</surname>
            <given-names>Lori</given-names>
          </name>
          <degrees>BSc, MA, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4770-8797</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Sinclair</surname>
            <given-names>Susanne</given-names>
          </name>
          <degrees>BHSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7754-9507</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Chan</surname>
            <given-names>David</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4743-0967</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Miller</surname>
            <given-names>Jordan</given-names>
          </name>
          <degrees>MSc, PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3819-5283</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Donnelly</surname>
            <given-names>Catherine</given-names>
          </name>
          <degrees>BSc, MSc, PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0809-3059</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Smith-Turchyn</surname>
            <given-names>Jenna</given-names>
          </name>
          <degrees>MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5309-2856</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Wojkowski</surname>
            <given-names>Sarah</given-names>
          </name>
          <degrees>MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8103-0281</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Gravesande</surname>
            <given-names>Janelle</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9264-8805</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author">
          <name name-style="western">
            <surname>Loyola Sánchez</surname>
            <given-names>Adalberto</given-names>
          </name>
          <degrees>MSc, MD, PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0082-2907</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Rehabilitation Science</institution>
        <institution>Faculty of Health Sciences</institution>
        <institution>McMaster University</institution>
        <addr-line>Hamilton, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Health Research Methods, Evidence &#38; Impact</institution>
        <institution>Faculty of Health Sciences</institution>
        <institution>McMaster University</institution>
        <addr-line>Hamilton, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Professor Emeritus</institution>
        <institution>Faculty of Health Sciences</institution>
        <institution>McMaster University</institution>
        <addr-line>Hamilton, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>School of Rehabilitation Therapy</institution>
        <institution>Faculty of Health Sciences</institution>
        <institution>Queen's University</institution>
        <addr-line>Kingston, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Cummings School of Medicine</institution>
        <institution>University of Calgary</institution>
        <addr-line>Calgary, AB</addr-line>
        <country>Canada</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Julie Richardson <email>jrichard@mcmaster.ca</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Jan-Mar</season>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>3</month>
        <year>2021</year>
      </pub-date>
      <volume>8</volume>
      <issue>1</issue>
      <elocation-id>e19519</elocation-id>
      <history>
        <date date-type="received">
          <day>21</day>
          <month>4</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>24</day>
          <month>9</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>18</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>12</day>
          <month>2</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Julie Richardson, Lori Letts, Susanne Sinclair, David Chan, Jordan Miller, Catherine Donnelly, Jenna Smith-Turchyn, Sarah Wojkowski, Janelle Gravesande, Adalberto Loyola Sánchez. Originally published in JMIR Rehabilitation and Assistive Technology (http://rehab.jmir.org), 18.03.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Rehabilitation and Assistive Technology, is properly cited. The complete bibliographic information, a link to the original publication on http://rehab.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://rehab.jmir.org/2021/1/e19519" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The global rise in the incidence of chronic conditions and aging is associated with increased disability. Physiotherapists and occupational therapists can mitigate the resulting burden on the health care system with their expertise in optimizing function. Rehabilitation self-management strategies can assist people with chronic conditions to accept, adjust, and manage different aspects of their daily functioning. Interventions delivered using technology have the potential to increase the accessibility, availability, and affordability of rehabilitation self-management support and services.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to describe the development and usability evaluation of iamable, a web-based app created to provide rehabilitation self-management support for people with chronic conditions.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The development and evaluation of iamable were undertaken in several phases. We used user-centered design principles and an iterative process that included consultations with rehabilitation experts; developed a prototype; and conducted usability tests, heuristic evaluations, and a focus group analysis.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The iamable app was developed to provide rehabilitation self-management strategies in the areas of exercise, fall prevention, fatigue management, pain management, physical activity, and stress management. We engaged adults aged ≥45 years with at least one chronic condition (N=11) in usability testing. They identified navigation and the understanding of instructions as the primary issues for end users. During the heuristic evaluation, clinicians (N=6) recommended that some areas of app content should be more succinct and that help should be more readily available. The focus group provided input to help guide clinical simulation testing, including strategies for selecting patients and overcoming barriers to implementation.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>We engaged end users and clinicians in the development and evaluation of the iamable app in an effort to create a web-based tool that was useful to therapists and their patients. By addressing usability issues, we were able to ensure that patients had access to rehabilitation strategies that could be used to help them better manage their health. Our app also provides therapists with a platform that they can trust to empower their patients to be more active in the management of chronic conditions. This paper provides a resource that can be used by others to develop and evaluate web-based health apps.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>rehabilitation</kwd>
        <kwd>physiotherapy</kwd>
        <kwd>occupational therapy</kwd>
        <kwd>self-management</kwd>
        <kwd>function</kwd>
        <kwd>web-based application</kwd>
        <kwd>usability</kwd>
        <kwd>user-centered design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>The global rise in the incidence of noncommunicable chronic diseases will cause an associated rise in the prevalence of disability and will be responsible for 75% of all deaths by 2030, thereby creating the most significant public health problem of the 21st century [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. There is an opportunity to manage this current health care crisis through the introduction of multisector rehabilitation strategies. Physiotherapists and occupational therapists are rehabilitation professionals with expertise in promoting physical function and preventing disability, particularly in the presence of comorbid health conditions. Rehabilitation assists people with chronic conditions to accept, adjust, and manage different aspects of functioning and share similar processes that are advocated in self-management. It has been suggested that by incorporating self-management support, rehabilitation providers could provide a more effective approach to rehabilitation and chronic disease management [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>Self-management is defined as an individual’s ability to manage the symptoms, treatment, physical and psychological consequences, and lifestyle changes inherent in living with a chronic condition [<xref ref-type="bibr" rid="ref6">6</xref>]. It is usually undertaken collaboratively with the support of a health care provider. Rehabilitation principles can be incorporated into self-management support for people with chronic conditions to optimize their physical function. Most chronic conditions and disabilities are long-standing, and it is often challenging to keep people with chronic conditions engaged in long-term self-management [<xref ref-type="bibr" rid="ref7">7</xref>]. Technology could be one way to promote ongoing engagement with rehabilitation clinicians who support self-management because it has the potential to increase the accessibility and availability of rehabilitation services. Web-based apps can ensure that patients have remote access to rehabilitative care when in-person interactions are not possible. In addition, leveraging technology may facilitate more effective self-management of chronic diseases, which may lead to improved health outcomes [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. A recent systematic review that examined the effectiveness of mobile self-management apps in the long-term management of chronic conditions showed that 6 of the 9 apps developed for diabetes, chronic lung disease, and cardiovascular disease demonstrated a statistically significant improvement in the primary measure of clinical outcomes [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>To foster the effectiveness of digital health apps, it is important to ensure their usability. A recent scoping review [<xref ref-type="bibr" rid="ref11">11</xref>] describes the current methods used in the usability testing of eHealth apps. The methods used included questionnaires (n=105), task completion (n=57), think aloud (n=45), interviews (n=37), heuristic testing (n=18), and focus groups (n=13). Most of the studies used 1 (n=45) or 2 (n=46) testing methods. Automated mechanisms such as eye tracking were not reported as a method of assessment to test usability, and the System Usability Scale (SUS) was the most frequently used questionnaire (n=44). Multimodal usability evaluation was used most frequently, used in 67.2% (88/131) of the studies where intended users were patients and/or caregivers. The authors conclude that there is only a small proportion of reported evaluations of digital health apps in peer-reviewed publications, although the number of apps has increased substantially [<xref ref-type="bibr" rid="ref9">9</xref>]. Further research is needed to determine the best testing methods for the usability of eHealth apps, considering their target users and their health conditions [<xref ref-type="bibr" rid="ref11">11</xref>].</p>
      </sec>
      <sec>
        <title>Objective</title>
        <p>This paper describes the development and usability evaluation of iamable, an app that uses rehabilitation strategies to promote self-management of chronic conditions. Specifically, we describe the iterative process of developing the app and conducting usability and heuristic testing. The purpose of this work is to determine whether users (people with chronic conditions) can navigate through a web-based app and access information to facilitate rehabilitation self-management. This project received ethics approval from the Hamilton Integrated Research Ethics Board (Project number: 5160).</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The iamable app was developed and evaluated in stages, with the findings from each stage used to refine the final product. Our phased approach used user-centered design principles similar to those of Peute et al [<xref ref-type="bibr" rid="ref12">12</xref>]. We adopted methods from the Website Developmental Model for the Health Care Consumer framework, which included (1) an information needs analysis and mock-up design, (2) website prototype development, and (3) heuristic evaluation and think-aloud analysis. This phased approach was developed further. It is illustrated as an iterative process in <xref rid="figure1" ref-type="fig">Figure 1</xref>. This paper reports on stages 1 to 6.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Process of iamable app development and evaluation.</p>
          </caption>
          <graphic xlink:href="rehab_v8i1e19519_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Determining App Content</title>
        <p>We undertook a consultation process with physiotherapists and occupational therapistswho were either clinical or research experts in the self-management of chronic conditions to prioritize the topics for module development that formed the content for the app. In creating the self-management modules, we used the concept of clinical concordance to develop rehabilitation strategies used by either physiotherapists or occupational therapistsor both professionals to address issues faced by people with chronic conditions (who frequently have comorbid conditions). Clinical concordance is an approach that uses the concepts of clinical discordance (where conditions are not linked by pathogenesis or management) and concordance (conditions represent an overall pathophysiological risk profile) [<xref ref-type="bibr" rid="ref13">13</xref>]. The unique contributions of physiotherapists and occupational therapiststo self-management interventions target mobility, functional activity, and participation levels [<xref ref-type="bibr" rid="ref5">5</xref>]. Often, the rehabilitation strategies suggested by physiotherapists and occupational therapistshave a high level of therapeutic concordance in that they can be applied (sometimes with some modification) to multiple conditions where there may be clinical discordance, but the functional outcomes are similar.</p>
        <p>Briefly, the consultation was a web-enabled consensus process, whereby specific self-management strategies that could be used to manage mobility, functional activity, and participation issues associated with chronic conditions were identified by the participants. The 6 self-management strategies identified were physical activity, fall prevention, fatigue management, pain management, stress management, and exercise. The concept behind self-management is that people with chronic conditions all experience to a greater or lesser extent some homogenous symptoms, including fatigue, pain, and stress; therefore, the app was designed to provide people with rehabilitation-focused strategies they could use to break the symptom cycle [<xref ref-type="bibr" rid="ref14">14</xref>].</p>
      </sec>
      <sec>
        <title>App Design</title>
        <p>We began by identifying the goals of the project with the design team from Media Production Services at McMaster University. Our primary objective was to develop a web-based app that would benefit both patients and clinicians. We wanted to provide patients with access to a trusted source of health information and rehabilitation strategies that they could use to optimize their function and participation in daily life. We also wanted patients to have a tool that would help them self-monitor their health and communicate with their therapist to better manage their chronic condition. In addition, we wanted to create a resource that busy rehabilitation clinicians could use to support the self-management efforts of their patients. With the design team, we identified the target users as patients receiving rehabilitation services in primary care and discussed web design features that would appeal to this population. We worked together to create wireframes (illustrations of basic page layouts) and detailed mock-ups to visualize the user experience and the information architecture of the app. We used the Drupal Content Management System [<xref ref-type="bibr" rid="ref15">15</xref>], which allowed us flexibility in our design. The app was built to be mobile and responsive, with a focus on tablet and computer use. We focused on maximizing white space with minimalistic design and colors to limit confusion and provide obvious focus points on the page and chose a simple san-serif font face and larger font sizes where possible with increased contrast to support target audiences from an older demographic. We then worked with the design team to develop a prototype and engaged 2 end users and 2 clinicians to review the mock-ups and provide feedback. They were able to comment on the general appearance of the user interface (UI) and provide input regarding basic navigation (moving between screens) and workflow processes (completing forms). <xref rid="figure2" ref-type="fig">Figure 2</xref> shows a sample screenshot of the finalized design for the iamable UI (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides additional screenshots of the UI).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Sample screenshot of the iamable user interface.</p>
          </caption>
          <graphic xlink:href="rehab_v8i1e19519_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Developing App Content</title>
        <p>The content of the iamable app was developed using concepts from social cognitive theory, including goal setting and self-monitoring [<xref ref-type="bibr" rid="ref16">16</xref>]. Users were prompted to identify an activity that was important to them that they were having difficulty performing because of their health problem and to create a long-term goal for that activity. They were asked to identify gaps in their knowledge and explore the information contained in the self-management modules. The development of the modules (pain management, exercising with a chronic condition, physical activity and chronic conditions, stress management, fatigue management, and fall prevention) was undertaken by rehabilitation experts in their respective fields, who used systematic reviews and clinical practice guidelines to convey strategies and recommendations to help users manage their condition(s). Each evidence-informed module was developed in the same format so that users of the app would (1) complete self-assessments to receive feedback about their level of risk for health outcomes and receive advice tailored to their needs, (2) have access to evidence-based self-management strategies, (3) engage in action planning based on activities with which they self-identified, and (4) have the option to consult with a physiotherapist or occupational therapist via secure messaging. All content was reviewed by the research team before it was finalized and before the usability evaluation.</p>
      </sec>
      <sec>
        <title>Usability Testing</title>
        <p>Usability testing was conducted with adults aged ≥45 years (N=11) recruited from a database of previous research participants who consented to future contact and through an advertisement distributed to the network of the Hamilton Council on Aging. All potential participants were screened by telephone to determine if they met the following inclusion criteria: (1) the presence of at least one chronic condition and (2) computer proficiency. To be eligible to participate, people were required to respond “somewhat easily” or “very easily” to all questions on the Computer Proficiency Questionnaire-12 (CPQ-12) [<xref ref-type="bibr" rid="ref17">17</xref>]. Participants were also asked to estimate their daily technology use (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref17">17</xref>] provides a copy of CPQ-12).</p>
        <p>Usability testing was performed in the Advanced Human-Computer Interaction (HCI) Lab, located in the DeGroote School of Business on McMaster University’s main campus in Hamilton, Ontario. The HCI Lab consisted of a participant room and a control room, with one-way mirrors between the rooms to allow for the monitoring of subjects and their interactions. Audiovisual recordings of the test sessions were obtained from 4 video cameras at multiple angles and a recording of the website screen overlaid with eye tracking (Tobii Eye-tracker, Tobii AB; <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> provides a detailed usability test plan).</p>
        <p>We used the concurrent think-aloud method, which is one of the most frequently used tests of usability in health care research [<xref ref-type="bibr" rid="ref18">18</xref>]. Participants were required to verbalize their actions and thoughts, as they completed representative tasks using the app. Users were asked to perform the following tasks: (1) sign in to the app; (2) complete step 1: select 1 activity that you are having difficulty with because of your health problem (The app allows users to select up to 3 activities in step 1. We asked test users to select 1 activity for the usability testing session); (3) step 2: rate your ability to perform the activity on a 10-point scale and set a goal; (4) select the activity goal that you would like to work toward; (5) select one of the self-management modules you identified that would help you reach your goal; (6) complete self-assessment; (7) on the basis of the results of self-assessment, select a topic such as “medications” in the Fall Prevention module to learn more about medications and fall risk; (8) create a 7-day action plan; and (9) ask your therapist a question (send your therapist a message). Participants completed a training task to practice the think-aloud method [<xref ref-type="bibr" rid="ref19">19</xref>] before the testing session began, and the interviewer provided feedback on the participant’s performance. Participants were prompted to continue talking if they were silent for more than 10-15 seconds. Each testing session took approximately 1.5 hours.</p>
        <p>Participants completed the SUS at the conclusion of the test session. The SUS is a tool that quickly and easily evaluates a user’s subjective rating of a product’s usability [<xref ref-type="bibr" rid="ref20">20</xref>]. It consists of 10 statements that are scored on a 5-point Likert scale (1=strongly disagree and 5=strongly agree). Estimates of reliability range from 0.83 to 0.97 [<xref ref-type="bibr" rid="ref21">21</xref>]. Scores for the SUS can range from 0 to 100, where higher scores indicate better usability (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> [<xref ref-type="bibr" rid="ref20">20</xref>] provides an adapted copy of the SUS).</p>
        <p>Audio recordings of the usability test sessions were transcribed to create log files, which were then marked up by a research coordinator who reviewed the video recordings and added annotations about usability issues identified by the user. The transcripts were coded to identify specific types of usability issues, as proposed by Kushniruk et al [<xref ref-type="bibr" rid="ref22">22</xref>] (<xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> [<xref ref-type="bibr" rid="ref22">22</xref>] provides details of the video coding scheme). Qualitative comments were extracted from the log files during the coding procedures if they were illustrative and representative of the usability issue.</p>
      </sec>
      <sec>
        <title>Heuristic Evaluation</title>
        <p>The next phase of the usability assessment involved a heuristic evaluation, which is a usability inspection method used to identify usability problems in the UI design. Evaluators examined the interface and assessed the degree to which it complied with established usability principles (the heuristics) [<xref ref-type="bibr" rid="ref23">23</xref>]. A total of 8 heuristics for evaluation focused on identifying specific usability problems, and 4 heuristics focused on identifying issues related to health literacy<italic>.</italic> The criteria were adapted from the work of Nielsen et al [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]. We recruited clinicians with experience using digital health apps and rehabilitation self-management interventions (N=6) to perform an independent evaluation of the iamable app based on these 12 criteria. The clinicians included a convenience sample of 3 physiotherapists and 3 occupational therapists(female: n=5; male: n=1; clinical experience: mean 14 years; range 3-31 years) who worked in primary care and/or whose practice involved the management of people with chronic conditions who might use the app. The clinicians practiced in both urban and rural primary care settings, and several clinicians provided care to marginalized populations.</p>
        <p>Clinicians were asked to log in to the iamable app remotely and complete six tasks: (1) identify an activity; (2) rate the activity and set a goal; (3) navigate to the self-management module, complete the self-assessment, and review the 2 module topics assigned; and (4) create an action plan. Each clinician evaluated 2 of the self-management modules, so that each module was evaluated by 1 physiotherapist and 1 occupational therapist. They systematically progressed through the screens required to complete the task. When they encountered a usability issue, they recorded it on the heuristic evaluation form, applied a severity rating (1=mild, 2=moderate, and 3=severe), captured a screenshot of the page on which they encountered the problem, and provided comments or recommendations to resolve the issue (<xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref> provides a copy of the heuristic evaluation form). We allowed approximately 1.5 hours for completion of these tasks.</p>
        <p>Clinicians submitted their completed evaluation forms electronically. Heuristic violations were summed and tabulated according to severity, and clinicians’ recommendations were summarized by the research team.</p>
      </sec>
      <sec>
        <title>Focus Group</title>
        <p>We held a focus group using videoconferencing 1 week after the completion of the heuristic evaluation to gather the clinicians’ general impressions of the app and its clinical utility. Specifically, the questions they were asked were as follows: What are the strengths of the app? What are the areas that could be improved? Which patients do you think might benefit from using the app? Which patients would you recommend it to? How do you envisage using the app in your clinical practice?</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Usability Testing</title>
        <p><xref ref-type="table" rid="table1">Table 1</xref> presents the demographic characteristics of the participants. The mean age of the participants was 69.3 years (SD 10.1 years; range 48-84 years), and the majority were retired (8/11, 73%) and used technology for 1-5 hours daily. The chronic conditions they reported included arthritis (7/11, 64%), hypertension (5/11, 45%), diabetes (3/11, 27%), asthma (3/11, 27%), chronic obstructive pulmonary disease (2/11, 18%), heart disease (1/11, 9%), and other (5/11, 45%; included chronic neck or back pain, chronic kidney disease, anxiety, and depression).</p>
        <p><xref ref-type="table" rid="table2">Table 2</xref> provides an example of task duration. Users were asked to complete the self-assessment, and duration was measured as the length of time it took users to read the instructions and click the self-assessment button on the module page. The duration varied considerably between users, ranging from 21 to 264 seconds (average task duration for females: 79.8 seconds; average task duration for males: 108 seconds), indicating that users follow instructions and navigate the app with differing levels of efficiency.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Participant characteristics (N=11).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="700"/>
            <col width="270"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Characteristic</td>
                <td>Values</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">Age (years), mean (SD)</td>
                <td>69.3 (10.1)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Sex, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td>6 (55)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td>5 (45)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Marital status, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Married</td>
                <td>8 (73)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Divorced</td>
                <td>2 (18)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Widowed</td>
                <td>1 (9)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Employment, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Working part-time</td>
                <td>2 (18)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Retired</td>
                <td>8 (73)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>On disability</td>
                <td>1 (9)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Ethnicity, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>European</td>
                <td>11 (100)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Financial situation, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Have just enough to get along</td>
                <td>3 (27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Are comfortable</td>
                <td>8 (73)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Number of chronic diseases, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1</td>
                <td>3 (27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2</td>
                <td>3 (27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3</td>
                <td>3 (27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4</td>
                <td>2 (18)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Daily technology use (hours), n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#60;1</td>
                <td>1 (9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1-3</td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3-5</td>
                <td>4 (36)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#62;5</td>
                <td>2 (18)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Example of task duration.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="80"/>
            <col width="160"/>
            <col width="110"/>
            <col width="360"/>
            <col width="290"/>
            <thead>
              <tr valign="top">
                <td>User</td>
                <td>Age (year)</td>
                <td>Sex</td>
                <td>Number of chronic conditions</td>
                <td>Task duration (seconds)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>84</td>
                <td>Female</td>
                <td>4</td>
                <td>48</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>77</td>
                <td>Female</td>
                <td>1</td>
                <td>141</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>70</td>
                <td>Female</td>
                <td>4</td>
                <td>42</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>56</td>
                <td>Female</td>
                <td>1</td>
                <td>33</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>65</td>
                <td>Female</td>
                <td>3</td>
                <td>135</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>72</td>
                <td>Male</td>
                <td>2</td>
                <td>171</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>77</td>
                <td>Male</td>
                <td>2</td>
                <td>34</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>72</td>
                <td>Male</td>
                <td>2</td>
                <td>68</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>73</td>
                <td>Male</td>
                <td>1</td>
                <td>264</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>48</td>
                <td>Male</td>
                <td>3</td>
                <td>90</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>72</td>
                <td>Male</td>
                <td>3</td>
                <td>21</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In total, 7 usability issues emerged from the think-aloud transcripts. They include navigation, understanding instructions, layout, understanding terminology, workflow issues, accuracy and correctness, and consistency. The usability issues for each of the 9 tasks are illustrated in <xref rid="figure3" ref-type="fig">Figure 3</xref>. The most common usability issue across tasks was related to navigation. Users described difficulty in determining what to do next, uncertainty about which content was clickable, and confusion about the labels on certain buttons and tabs. The task with the greatest number of usability issues was task 6: complete self-assessment. The most common usability issue when asked to complete the self-assessment was related to layout, with some users unable to locate the self-assessment button on the page, whereas others had difficulty finding their self-assessment results. Other usability issues with this task included difficulties with navigation, understanding instructions, workflow, and accuracy. Examples of usability issues by task were extracted from the audio recordings of the think-aloud sessions and are presented in <xref ref-type="table" rid="table3">Tables 3</xref> and <xref ref-type="table" rid="table4">4</xref>.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Summary of usability issues by task. Task 1: log in; task 2: select activity; task 3: rate activity and set goal; task 4: open activity: task 5: select self-management module; task 6: complete self-assessment; task 7: select module topic; task 8: create action plan; task 9: message therapist.</p>
          </caption>
          <graphic xlink:href="rehab_v8i1e19519_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Think-aloud results for tasks 2-6.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="110"/>
            <col width="140"/>
            <col width="270"/>
            <col width="480"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Usability issue</td>
                <td>Description</td>
                <td>Example</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Task 2: Select activity</td>
                <td>Understanding instructions</td>
                <td>Users had difficulty understanding that they should select an activity that they were having difficulty with because of their health.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Like gardening, I’m not that thrilled about gardening and I’m not very good at it. Would that be considered one, or no?” (User 7)</p>
                    </list-item>
                    <list-item>
                      <p>“It’s asking for an activity you are having difficulty doing because of your health.” (RC<sup>a</sup>)</p>
                    </list-item>
                    <list-item>
                      <p>“Oh, I’m sorry. I didn’t even think of that. Ok, because of my health.” (User 7)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 3: Rate activity and set goal</td>
                <td>Understanding instructions</td>
                <td>Users had difficulty determining how many modules they should select.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So, you want me to pick just one?” (User 5)</p>
                    </list-item>
                    <list-item>
                      <p>“No, you can pick as many as you would like.” (RC)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 4: Open activity</td>
                <td>Navigation</td>
                <td>Users did not realize that they needed to click on the icon to open the activity.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So, we’ve done that...I don’t see a ‘next’ to click on, so what should we do about that? How do we move on?” (User 1)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 5: Select self-management module</td>
                <td>Navigation</td>
                <td>Users had difficulty locating the self-management modules on the page.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“That’s this, right? That’s what this is?” (User 3)</p>
                    </list-item>
                    <list-item>
                      <p>“So, that’s to create an action plan…” (RC)</p>
                    </list-item>
                    <list-item>
                      <p>“Oh, over here. Oh, ok. So that’s the module.” (User 3)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 5: Select self-management module</td>
                <td>Understanding instructions</td>
                <td>Users had difficulty with the instructions because they had the option to explore the topics or complete the self-assessment.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So I’m not really sure here.” (User 5)</p>
                    </list-item>
                    <list-item>
                      <p>“So based on the information you read...” (RC)</p>
                    </list-item>
                    <list-item>
                      <p>“Complete the self-assessment, it says. So I guess they want me to do this, right?” (User 5)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 6: Complete self-assessment</td>
                <td>Navigation</td>
                <td>Users suggested that the recommendation provided by the system after completing the self-assessment did not provide adequate direction to help navigate to the next task.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So, should I go back to self-assessment? This is the same page as before, right? I don’t understand where I go from here.” (User 7)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 6: Complete self-assessment</td>
                <td>Understanding instructions</td>
                <td>Users had difficulty following the instruction to complete the self-assessment. Some were drawn to the “Not sure what to do next” box and the instruction to create an action plan instead.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Ok, ‘Start by completing the self-assessment. Based on your answers, you will receive a recommendation to guide you in selecting the topics below that will help you the most.’ Ok, so this is what I’ve got to do, create a 7 Day Action Plan for your goal.” (User 11)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 6: Complete self-assessment</td>
                <td>Layout</td>
                <td>Users had difficulty finding the self-assessment button.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“But if the instruction says ‘Start by completing the self-assessment’, can you see on the page where that might be?” (RC)</p>
                    </list-item>
                    <list-item>
                      <p>“Right here. So [the button] is not in a place that I would have thought to look. It’s in a place where I think to not pay attention.” (User 11)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 6: Complete self-assessment</td>
                <td>Workflow</td>
                <td>Users suggested that questions on the self-assessment were unclear.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“This is a little confusing...there could be an easier way to get the answers.” (User 7)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 6: Complete self-assessment</td>
                <td>Accuracy</td>
                <td>Users identified that one of the self-assessments was not scoring correctly, providing some users with the wrong result.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Yeah, that’s kind of worrying when I read that...I’m thinking, how can I be sedentary when I’m doing something 7 days a week.” (User 2)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>RC: research coordinator.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Think-aloud results for tasks 7-9.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="120"/>
            <col width="140"/>
            <col width="270"/>
            <col width="470"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Usability issue</td>
                <td>Description</td>
                <td>Example</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Task 7: Select module topic</td>
                <td>Navigation</td>
                <td>Users were unsure how to navigate to topics (this task required the user to click on a topic to open it).</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Ok, so I don’t understand what I’m doing next...because am I going to open one of these by clicking?” (User 11)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 7: Select module topic</td>
                <td>Consistency</td>
                <td>Users expressed difficulty because the topic buttons did not appear to be hyperlinks.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Ok, well the first thing is...is that a link? When you look at that, you think that it is just text...so that changes the way that I was thinking.” (User 2)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 8: Create action plan</td>
                <td>Navigation</td>
                <td>Users were confused by the delete action plan button, not sure what to do after creating an action plan.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“I don’t want to delete this. So where else do I want to go? I can either delete it, or I create a 7-Day Action Plan which I already did. I don’t know where to go now. Unless you want to delete this goal.” (User 7)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 7: Select module topic</td>
                <td>Workflow issue</td>
                <td>Users anticipated a menu of action plans to choose from rather than having to create one of their own.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So, would this answer not have...would I not have been led to this, from maybe, from the results of the previous step? Would I not have been given some suggested actions at this point?” (User 9)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 9: Message therapist</td>
                <td>Navigation</td>
                <td>Users were not certain that the ask button should be used to contact the therapist.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Ask...that means ask a therapist? Ok...so you type the question and she’ll get back to you online?” (User 1)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Task 9: Message therapist</td>
                <td>Understanding terminology</td>
                <td>Users were confused about the save and send buttons when attempting to send a message to the therapist.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“So I’m saving it rather than sending it...But I will click send because that’s the only thing I can think of to get it off to the therapist.” (User 11)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>We were not able to fully test the messaging function in the app, as the test user accounts were not linked to therapist accounts. In clinical practice, the user will be able to post a question to the therapist, who will, in turn, receive notification about the message and enter the app to provide a response. Users will be reminded that they can expect to receive a response from their therapist within 2 working days; if they have an urgent issue that requires an immediate response, they will be told to contact their therapist directly.</p>
        <p>The SUS provided a single score that estimated the overall usability of the iamable app. The mean score of the iamable app (N=11) was 71.14 (SD 19.67). Products that are acceptable have SUS scores above 70, with superior products scoring in the high 70s to the high 80s [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
      </sec>
      <sec>
        <title>Heuristic Evaluation</title>
        <p><xref rid="figure4" ref-type="fig">Figure 4</xref> shows the results of the heuristic evaluation performed by the 6 clinicians. Specifically, it shows the overall frequency of heuristic violations identified by clinicians for all tasks that they were required to complete. Violations were rated according to severity: 1=mild, 2=moderate, and 3=severe. The heuristic that resulted in the highest number of violations (n=24) across all 4 tasks was “provide accurate, colloquial, comprehensive, succinct content.” The heuristic that resulted in the fewest violations (N=6) was the “visibility of system status,” where the user is informed as to the state of the system at any given moment (<xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref> provides a frequency table summarizing all heuristic violations).</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Results of heuristic testing. The graph depicts the overall frequency of heuristic violations.</p>
          </caption>
          <graphic xlink:href="rehab_v8i1e19519_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The raters identified 36 heuristic violations for task 2 (complete module self-assessment) with mostly mild to moderate severity ratings (<xref rid="figure5" ref-type="fig">Figure 5</xref>). Violations for the heuristic “help and documentation” indicated that there was no help button or frequently asked question (FAQ) option, and the raters felt that a video or timer should be added to facilitate the self-assessment task (in the fall prevention module). The raters identified severe violations for the heuristic “visibility of system status” because the instructions to complete the self-assessment remained on the screen and the self-assessment button remained active even after the self-assessment was completed. The other severe violation related to the heuristic “leverage interactivity,” where the clinician felt the recommendation following the self-assessment was not sufficiently tailored (exercise module; <xref ref-type="supplementary-material" rid="app8">Multimedia Appendix 8</xref> provides additional details).</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Heuristic violations by task. "A" refers to the visibility of system status. "B" refers to user control and freedom. "C" refers to consistency and standards. "D" refers to error prevention. "E" refers to minimized memory loads. "F" refers to the flexibility and efficiency of use. "G" refers to helping users recognize, diagnose, and recover from errors. "H" refers to help and documentation. "I" refers to leveraging interactivity. "J" refers to providing accurate, colloquial, comprehensive, and succinct content. "K" refers to providing tailored, flexible, and layered content. "L" refers to using visuals to complement text but avoiding tables.</p>
          </caption>
          <graphic xlink:href="rehab_v8i1e19519_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Task 3 (review module topics) generated the greatest number of heuristic violations (n=65) from the raters, the majority of which were mild (<xref rid="figure5" ref-type="fig">Figure 5</xref>). The heuristic “provide accurate, colloquial, comprehensive and succinct content” was identified as a mild violation by all raters for each of the modules they reviewed. Feedback from raters included the need for a more lay-friendly language to avoid using language that labels users (ie, faller vs nonfaller), to provide examples or links to explain more difficult concepts (ie, cognition and corticosteroids), to shorten videos and text in some areas, and to provide emphasis to ensure that users do not take certain actions (ie, stop taking a medication) without first consulting with their physician. Raters identified several severe violations, including (1) the heuristic “use visuals to complement text” where a trip hazard was not identified in a home hazards video (fall prevention module) and the video was not uploaded (stress management module), (2) the heuristic “minimize memory load” because there is no way for users to track their progress through the module (ie, an indicator that a topic had been read or completed), and (3) the heuristic “help and documentation” because there is no topic-specific help or FAQs (<xref ref-type="supplementary-material" rid="app8">Multimedia Appendix 8</xref> provides additional details).</p>
        <p>Raters detected 21 mild or moderate heuristic violations for task 4 (creating an action plan; <xref rid="figure5" ref-type="fig">Figure 5</xref>). Raters noted severe violations in relation to the heuristic “help and documentation” (n=1) because there was no help option available and the heuristic “system provides a clear and easy to understand way of recovering from an error” (n=1) after the system did not save the action plan after prompting that the confidence level was too low (<xref ref-type="supplementary-material" rid="app8">Multimedia Appendix 8</xref> provides additional details).</p>
      </sec>
      <sec>
        <title>Focus Group</title>
        <sec>
          <title>Strengths of the App</title>
          <p>Clinicians identified several positive features of the app. They reported that the videos were particularly helpful, especially because the content was simplified and summarized for the user. For example, they stated that the self-management modules explained concepts using simple, nontechnical language, and when it was not possible to replace technical terms, a simple definition was provided in brackets.</p>
          <p>They appreciated the interactive nature of the app, which enabled the user to set goals, receive tailored information, and check their progress. An example they gave of the tailoring was if a user scored high on the pain catastrophizing scale (the pain self-assessment), they were directed to complete the topics focusing on thoughts, emotions, and pain. They endorsed the self-assessments associated with each module and noted that the information from these would be helpful to both the user and the clinician to have an assessment of baseline functioning and track progress toward goals.</p>
        </sec>
        <sec>
          <title>Areas for Improvement</title>
          <p>Although the clinicians were very positive about the videos, they commented that some were too long, estimating that the maximum time that a video would sustain a user’s attention would be 2 minutes. They suggested that it would be helpful if there was a way for users to mark their progress within the app, so that if they returned, they would know where to resume (ie, by providing a bookmark, by changing the color of the font, or by identifying favorite content). They suggested that more consistent use of the “add to my reminders” feature would help users identify and prioritize tasks that they needed to undertake to help them complete their action plans and reach their goals. They felt that the app might increase engagement in exercise and self-management and adherence in the management of their chronic condition.</p>
          <p>Some therapists felt the recommendation following the self-assessment in the exercise module provided the same information irrespective of the score and that it would be helpful if the exercise prescription was better tailored to the user’s fitness level.</p>
          <p>Several clinicians noted technical issues when using the app on their phone or tablet, where certain buttons did not function, and it was difficult to read the content without having to manually resize the text.</p>
        </sec>
        <sec>
          <title>Suitability for Patient Groups</title>
          <p>Primary care was recommended as the setting in which the app would be the most useful. Clinicians agreed that they would want to introduce the app to patients in a 1:1 consultation to ensure that patients had the ability to use it successfully before engaging with it independently. They reported that there were no contraindications for any patient group, although the level of digital and health literacy required to use the app might prove too advanced for some of the populations seen in primary care, such as new immigrants or people who were homeless. Clinicians thought that an app such as iamable might be especially appealing to users who had social anxiety. They commented that users in rural and remote areas would find the app very helpful because they could use it in a clinical setting and then have it as support to work on their goals from home. Clinicians agreed that the app would help keep patients engaged in their rehabilitation between visits. Finally, the clinicians suggested translating the content of the app to other languages.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study describes the successful development of an app to support the self-management of people with chronic conditions and address symptoms that could be managed using rehabilitation strategies. The approach we used to evaluate the usability of the iamable app included task completion, think-aloud, interviews, heuristic testing, and focus groups, a process similar to that of Peute and endorsed by Maramba [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. iamable is the first app developed and systematically evaluated by rehabilitation professionals that addresses the holistic management of people with chronic conditions using rehabilitation strategies. The 6 areas of self-management targeted by the app align with the self-management skills outlined by Lorig for breaking the symptom cycle [<xref ref-type="bibr" rid="ref14">14</xref>]. The premise of the relationship between these symptoms is that, irrespective of the disease, people with chronic conditions often experience common issues. The modules included within the app are evidence based, and the strategies recommended to address these issues have been developed using best practice guidelines (ie, prescribing multicomponent home-based exercise and promoting home safety assessments to reduce the risk of falls [<xref ref-type="bibr" rid="ref27">27</xref>] and providing pain neuroscience education to help patients manage chronic pain [<xref ref-type="bibr" rid="ref28">28</xref>]). The app requires users to identify the gaps in their knowledge and select modules accordingly. The design of the iamable app was iterative and involved consultation with users from the early stages of development, with revisions and changes based on their feedback and input. Our multistage approach to usability evaluation enabled us to make modifications serially and remediate user problems before the next stage of testing.</p>
      </sec>
      <sec>
        <title>Common Issues Identified by Usability Testing</title>
        <p>The two most frequent issues encountered by users during usability testing were navigation and the understanding of instructions within the app. These issues are well documented in the literature and may result from reduced vision, hearing loss, or psychomotor impairment [<xref ref-type="bibr" rid="ref29">29</xref>]. Barriers related to navigation and instructions on websites and health apps have been reported in other older adult populations, suggesting the need for special considerations and adaptations to improve these and other fundamental aspects of app design [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Our results are not surprising because older people in the United States and Europe report that they are less likely to engage with web-based apps because of the perceived complexity of internet use [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Older people are less likely than younger people to perceive websites as user friendly [<xref ref-type="bibr" rid="ref34">34</xref>]. In an effort to improve the usability of the iamable app, we addressed issues with navigation and understanding instructions that were identified during usability testing. Modifications made to improve navigation included making buttons clearly clickable; using more consistent use of hyperlink colors; modifying button size, color, and location to draw the user’s attention; and relabeling buttons to clarify their meaning. Color and size sensitivity reduce with age, especially blue-green differentiation [<xref ref-type="bibr" rid="ref29">29</xref>]. To clarify the instructions, we added text such as “select all that apply” and “start by completing the self-assessment” to improve usability. These changes will further provide accommodations to older users with diminished abilities in attention, learning, and memory, which manifest in determining where to go next [<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        <p>A study by Bangor et al [<xref ref-type="bibr" rid="ref26">26</xref>] found that there was a small, significant correlation between age and SUS scores (SUS scores decreased with increasing age) but no effect of gender. In our sample, we observed a sex difference where women had higher SUS scores compared with men (women: mean 78.5, SD 17.6; men: mean 65.0, SD 20.7) despite having similar levels of comorbidity and education and slightly older mean age (women: mean 70.4 years, SD 10.8 years; men: mean 68.3 years, SD 10.4 years). A mean SUS score of 71.14 (SD 19.67) suggested that the usability of the iamable app is acceptable. An SUS score of 71.4 (SD 11.6) corresponds with a rating of “good” using an adjective rating scale [<xref ref-type="bibr" rid="ref26">26</xref>]. The SUS was administered to participants at one point in time only; therefore, it is reasonable to assume that with the revisions made to the app following usability testing, SUS scores would likely have improved if the survey had been readministered.</p>
        <p>For the sample task in which we calculated task duration (ie, complete the self-assessment), there were no differences by age or number of chronic conditions. In addition, when the outlier was removed, there were no sex differences in task completion time.</p>
      </sec>
      <sec>
        <title>Most Common Heuristic Violations</title>
        <p>The top heuristic violations identified by the clinicians were related to the provision of accurate, colloquial, comprehensive, succinct content and help and documentation. The heuristic “provide accurate, colloquial, comprehensive, succinct content” targets health literacy and is intended to ensure that written information is brief, relevant, and in the users’ vernacular. Our goal was to engage users in the app content in a way that motivates them to create goals and complete action plans. To do this, we endeavored to create content that was both brief and to the point, actionable, and engaging [<xref ref-type="bibr" rid="ref12">12</xref>]. It is also suitable for users with a range of literacy skills to reflect the types of patients that therapists would see in clinical practice. In response to clinician feedback, the iamable app content was revised to add images to complement text, make the text more concise, simplify instructions, and emphasize safety considerations. In addition, the heuristic “help and documentation” directly impacts the usability and is intended to ensure that help is available to users when needed<italic>.</italic> In response to comments from clinicians, we clarified for users that they should use the “Ask a Therapist” feature for self-management support and added a “Contact Us” page so that users could access technical assistance when required.</p>
      </sec>
      <sec>
        <title>Focus Group</title>
        <p>The focus group with the clinicians provided us with additional information about the app and recommendations for further changes and development that we would not have gathered through heuristic testing alone. Clinicians agreed that some patients would be able to use the app independently. A systematic review reported that self-management apps have been used successfully both with and without clinician input [<xref ref-type="bibr" rid="ref10">10</xref>], but older people are more likely to engage in learning and adopt the use of technology if they live with someone or have assistance [<xref ref-type="bibr" rid="ref35">35</xref>]. In response to concerns about ease of navigation, we are exploring ways to make it easier for users to find where they left off during previous sessions using the app. The focus group also provided us with information to help guide the final stage of the iamable evaluation, the clinical simulation. Participants were able to provide advice about overcoming barriers to implementation from the perspective of both the clinician and the patient. Potential barriers for clinicians included increased workload to support patients using the app and the need to obtain permission from clinic administrators. Patient barriers might include cost, literacy, language, connectivity, and availability or accessibility issues, which are similar to other reports in the literature [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>There were some limitations to this study. The sample recruited for usability testing was not ethnically diverse. All participants were of European heritage and were English speaking. To ensure that the iamable app is accessible to a diverse range of users, a future study that includes a more heterogeneous sample is warranted. Furthermore, we were unable to use eye tracking data to substantiate our results. For reasons related to cost and analyst availability, we were not able to analyze the eye tracking data that we collected. Eye tracking provides an automated method for objectively evaluating usability. Eye tracking analysis would have resulted in a more comprehensive usability evaluation of the iamable app. Combining eye tracking with qualitative data can provide a more holistic understanding of usability issues. For example, Cho et al [<xref ref-type="bibr" rid="ref36">36</xref>] used eye tracking metrics (time to first fixation, time spent, revisits, and total number of fixations) to compare groups with and without task difficulty to help identify barriers to task performance.</p>
        <p>For usability testing, we required that our sample have a high level of computer proficiency, which likely meant that they had access to technology. Overall, 73% (8/11) of our sample reported that they used their computers and mobile devices on average for 1-5 hours per day. With future testing, it will be important to include older people with less access to technology to ensure usability for those with low digital literacy. Finally, we made many revisions to the app in response to the results of usability testing and feedback from the heuristic evaluation but did not repeat either assessment to determine whether these changes resolved the identified issues.</p>
        <p>The final stage of our usability evaluation will be a clinical simulation where we will enlist therapist-patient dyads (n=26) from primary care sites where occupational therapists and physiotherapists engage in rehabilitation self-management. As was recommended in the focus group, the plan will be to have therapists introduce the iamable app in a face-to-face or virtual session with the patient and then to provide support as needed over the course of the trial. This will enable us to determine more specifically the role the app might play in a primary care environment, how the therapists will use the app with patients who have different chronic conditions, and how useful the app is for patients who are currently receiving rehabilitation. This final stage of the usability evaluation is considered important by the study team because the app has not yet been tested as an interactive therapeutic resource where the therapist and patient engage collaboratively in chronic disease self-management.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In conclusion, we have produced an app that closely matches the expectations of both the patient and clinician end users, and although there are usability issues identified from our testing, the app was rated highly on the validity of its evidence-based content. The information contained in the app can provide self-management support to people with chronic conditions with or without the support of a therapist because some users may not be receiving care from a rehabilitation practitioner. The app has the potential to both reinforce information provided during a rehabilitation intervention and provide rehabilitation strategies to users who can engage in self-management independently. It may strengthen the patient’s relationship with the therapist, increase engagement, and enable the patient to proactively address concerns related to their rehabilitation [<xref ref-type="bibr" rid="ref37">37</xref>]. A systematic review reported that self-management apps have been used successfully both with and without clinician input. Although clinicians noted that they would introduce the app to their patients, some patients would be able to use it independently without prior instruction [<xref ref-type="bibr" rid="ref10">10</xref>]. Adoption of the iamable app may face barriers to use such as cost, literacy, language, connectivity, availability and accessibility issues, similar to other health apps reported in the literature [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>To guide the development of the iamable app, we incorporated user-centered design principles [<xref ref-type="bibr" rid="ref12">12</xref>]. We used an iterative process that included consultation with rehabilitation experts to determine app content, app design, usability testing, and heuristic evaluation plus a focus group. This paper provides a resource that can be used by others to develop and evaluate web-based health apps that can benefit both patients and clinicians.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Screenshots of the iamable user interface.</p>
        <media xlink:href="rehab_v8i1e19519_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 422 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Computer Proficiency Questionnaire.</p>
        <media xlink:href="rehab_v8i1e19519_app2.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Usability test plan.</p>
        <media xlink:href="rehab_v8i1e19519_app3.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>System Usability Scale.</p>
        <media xlink:href="rehab_v8i1e19519_app4.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Video coding scheme.</p>
        <media xlink:href="rehab_v8i1e19519_app5.docx" xlink:title="DOCX File , 21 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Heuristic evaluation form.</p>
        <media xlink:href="rehab_v8i1e19519_app6.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>Frequency of heuristic violations.</p>
        <media xlink:href="rehab_v8i1e19519_app7.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
      <supplementary-material id="app8">
        <label>Multimedia Appendix 8</label>
        <p>Examples of heuristic violations by task.</p>
        <media xlink:href="rehab_v8i1e19519_app8.docx" xlink:title="DOCX File , 24 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AGE-WELL</term>
          <def>
            <p>Aging Gracefully Across Environments Using Technology to Support Wellness, Engagement and Long Life</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CPQ-12</term>
          <def>
            <p>Computer Proficiency Questionnaire-12</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">FAQ</term>
          <def>
            <p>frequently asked question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HCI</term>
          <def>
            <p>Human-Computer Interaction</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MIRA</term>
          <def>
            <p>McMaster Institute for Research on Aging</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">UI</term>
          <def>
            <p>user interface</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This project was funded by the Health Research Foundation Interdisciplinary Health Research Team Grant and the Aging Gracefully Across Environments Using Technology to Support Wellness, Engagement and Long Life (AGE-WELL)/McMaster Institute for Research on Aging (MIRA) Catalyst Funding Program. The authors would like to thank the Design and Web Group, Media Production Services at McMaster University for their guidance and expertise in web-based app design and development. The authors would also like to thank the Advanced Health Computer Interaction Lab of the DeGroote School of Business at McMaster University for guidance in developing a usability test plan and conducting usability testing.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>JR is the principal investigator. JR and LL led the conception and design of the study, the web-enabled consensus exercise, and the focus group. JR, LL, SS, JM, and JT contributed their expertise in developing app content. CD, SW, and JT provided feedback about the app from a clinician’s perspective. SS coordinated usability testing and heuristic evaluation. JR and SS wrote the manuscript with input from LL, DC, JM, CD, JT, SW, JG, and AS. All authors read and approved the final manuscript. Other members of the research team included Sarah Sanford, Evelyne Durocher, and Meredith Vanstone.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alwan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Alwan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Global status report on noncommunicable diseases 2010</source>
          <year>2011</year>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>World Health Organization, Geneva</publisher-name>
          <fpage>176</fpage>
        </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>Blair</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Sallis</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Hutber</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Archer</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Exercise therapy - the public health message</article-title>
          <source>Scand J Med Sci Sports</source>
          <year>2012</year>
          <month>03</month>
          <day>19</day>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>e24</fpage>
          <lpage>e28</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1600-0838.2012.01462.x</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>Gutenbrunner</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Commentary on "physical and rehabilitation medicine and self-management education: a comparative analysis of two approaches"</article-title>
          <source>J Rehabil Med</source>
          <year>2010</year>
          <month>10</month>
          <volume>42</volume>
          <issue>9</issue>
          <fpage>815</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medicaljournals.se/jrm/content/abstract/10.2340/16501977-0614"/>
          </comment>
          <pub-id pub-id-type="doi">10.2340/16501977-0614</pub-id>
          <pub-id pub-id-type="medline">20878040</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>Jansma</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Twillert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Postema</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lettinga</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Physical and rehabilitation medicine and self-management education: A comparative analysis of two approaches</article-title>
          <source>J Rehabil Med</source>
          <year>2010</year>
          <month>10</month>
          <volume>42</volume>
          <issue>9</issue>
          <fpage>808</fpage>
          <lpage>814</lpage>
          <pub-id pub-id-type="doi">10.2340/16501977-0606</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>Richardson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Loyola-Sanchez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sinclair</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Letts</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>MacIntyre</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkins</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Burgos-Martinez</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Wishart</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>McBay</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Martin Ginis</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Self-management interventions for chronic disease: a systematic scoping review</article-title>
          <source>Clin Rehabil</source>
          <year>2014</year>
          <month>11</month>
          <day>30</day>
          <volume>28</volume>
          <issue>11</issue>
          <fpage>1067</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.1177/0269215514532478</pub-id>
          <pub-id pub-id-type="medline">24784031</pub-id>
          <pub-id pub-id-type="pii">0269215514532478</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>Barlow</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sheasby</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hainsworth</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Self-management approaches for people with chronic conditions: a review</article-title>
          <source>Patient Education and Counseling</source>
          <year>2002</year>
          <month>10</month>
          <volume>48</volume>
          <issue>2</issue>
          <fpage>177</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1016/s0738-3991(02)00032-0</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>Navarra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Whittemore</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bakken</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cleland</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gwadz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Melkus</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Gormley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bethea</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Adherence self-management and the influence of contextual factors among emerging adults with Human Immunodeficiency Virus</article-title>
          <source>Nurs Res</source>
          <year>2020</year>
          <volume>69</volume>
          <issue>3</issue>
          <fpage>197</fpage>
          <lpage>209</lpage>
        </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>Scott</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Scuffham</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Harch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Borchi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Going digital: a narrative overview of the effects, quality and utility of mobile apps in chronic disease self-management</article-title>
          <source>Australian Health Review</source>
          <year>2018</year>
          <volume>44</volume>
          <issue>1</issue>
          <fpage>62</fpage>
          <lpage>82</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Setiawan</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Alfikri</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Saptono</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fairman</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Dicianno</surname>
              <given-names>BE</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>An adaptive mobile health system to support self-management for persons with chronic conditions and disabilities: usability and feasibility studies</article-title>
          <source>JMIR Form Res</source>
          <year>2019</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>e12982</fpage>
        </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>Whitehead</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Seaton</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The effectiveness of self-management mobile phone and tablet apps in long-term condition management: a systematic review</article-title>
          <source>Journal of medical internet research</source>
          <year>2016</year>
          <volume>18</volume>
          <issue>5</issue>
          <fpage>e97</fpage>
        </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>Maramba</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Newman</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Methods of usability testing in the development of eHealth applications: a scoping review</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <volume>126</volume>
          <fpage>95</fpage>
          <lpage>104</lpage>
        </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>Peute</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Knijnenburg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kremer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A concise and practical framework for the development and usability evaluation of patient information websites</article-title>
          <source>Applied clinical informatics</source>
          <year>2015</year>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>383</fpage>
          <lpage>399</lpage>
        </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>Watcher</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Simplify care by prioritizing comorbidities</article-title>
          <source>In. Internal Medicine News</source>
          <year>2008</year>
          <volume>41</volume>
          <issue>14</issue>
          <fpage>52</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lorig</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Holman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sobel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Laurent</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Minor</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>Living a healthy life with chronic conditions: for ongoing physical and mental health conditions</source>
          <year>2013</year>
          <publisher-loc>Colorado</publisher-loc>
          <publisher-name>Bull Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <source>Drupal Content Management Software</source>
          <access-date>2020-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.drupal.org/">https://www.drupal.org/</ext-link>
          </comment>
        </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>Bandura</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Health promotion by social cognitive means</article-title>
          <source>Health Educ Behav</source>
          <year>2004</year>
          <month>04</month>
          <volume>31</volume>
          <issue>2</issue>
          <fpage>143</fpage>
          <lpage>164</lpage>
          <pub-id pub-id-type="doi">10.1177/1090198104263660</pub-id>
          <pub-id pub-id-type="medline">15090118</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>Boot</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Charness</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Czaja</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Computer proficiency questionnaire: assessing low and high computer proficient seniors</article-title>
          <source>The Gerontologist</source>
          <year>2015</year>
          <volume>55</volume>
          <issue>3</issue>
        </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>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A comparison of usability methods for testing interactive health technologies: methodological aspects and empirical evidence</article-title>
          <source>Int J Med Inform</source>
          <year>2009</year>
          <month>05</month>
          <volume>78</volume>
          <issue>5</issue>
          <fpage>340</fpage>
          <lpage>353</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2008.10.002</pub-id>
          <pub-id pub-id-type="medline">19046928</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(08)00180-9</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>Boren</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ramey</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Thinking aloud:reconciling theory and practice</article-title>
          <source>IEEE transactions on professional communication</source>
          <year>2000</year>
          <volume>43</volume>
          <issue>3</issue>
          <fpage>261</fpage>
          <lpage>278</lpage>
        </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>Brooke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Jordan</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>McLelland</surname>
              <given-names>IL</given-names>
            </name>
            <name name-style="western">
              <surname>Weerdmeester</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>SUS-A quickdirty usability scale</article-title>
          <source>Usability evaluation in industry</source>
          <year>1996</year>
          <publisher-loc>Bristol, PA</publisher-loc>
          <publisher-name>Taylor and Francis</publisher-name>
          <fpage>189</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>Lewis</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The system usability scale: past, present, and future</article-title>
          <source>International Journal of Human Computer Interaction</source>
          <year>2018</year>
          <volume>34</volume>
          <issue>7</issue>
          <fpage>577</fpage>
          <lpage>590</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Borycki</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Development of a video coding scheme for analyzing the usability and usefulness of health information systems</article-title>
          <year>2015</year>
          <conf-name>Context Sensitive Health Informatics Conference</conf-name>
          <conf-date>Aug 14, 2015</conf-date>
          <conf-loc>Brazil</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>10 usability heuristics for user interface design</source>
          <year>2020</year>
          <month>11</month>
          <day>15</day>
          <access-date>2020-12-20</access-date>
          <publisher-name>Nielsen Norman Group</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Monkman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Griffith</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Evidence-based heuristics for evaluating demands on eHealth literacy and usability in a mobile consumer health application</article-title>
          <source>MedInfo</source>
          <year>2015</year>
        </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>Monkman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A health literacy and usability heuristic evaluation of a mobile consumer health application</article-title>
          <source>MedInfo</source>
          <year>2013</year>
          <fpage>22</fpage>
        </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>Bangor</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kortum</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>An empirical evaluation of the system usability scale</article-title>
          <source>Intl Journal of Human Computer Interaction</source>
          <year>2008</year>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>574</fpage>
          <lpage>594</lpage>
        </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>Gillespie</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Robertson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gillespie</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Interventions for preventing falls in older people living in the community</article-title>
          <source>Cochrane database of systematic reviews</source>
          <year>2012</year>
          <volume>9</volume>
        </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>Moseley</surname>
              <given-names>GL</given-names>
            </name>
            <name name-style="western">
              <surname>Butler</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Fifteen years of explaining pain: the past, present, and future</article-title>
          <source>J Pain</source>
          <year>2015</year>
          <month>09</month>
          <volume>16</volume>
          <issue>9</issue>
          <fpage>807</fpage>
          <lpage>813</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jpain.2015.05.005</pub-id>
          <pub-id pub-id-type="medline">26051220</pub-id>
          <pub-id pub-id-type="pii">S1526-5900(15)00682-3</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>Zaphiris</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kurniawan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ghiawadwala</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A systematic approach to the development of research-based web design guidelines for older people</article-title>
          <source>Universal Access in the Information Society</source>
          <year>2007</year>
          <volume>6</volume>
          <issue>1</issue>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <source>Developing websites for older people: how web content accessibility guidelines (WCAG) 2</source>
          <access-date>2020-12-18</access-date>
          <publisher-name>Web Accessibility Initiative</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.w3.org/WAI/older-users/developing/#top">https://www.w3.org/WAI/older-users/developing/#top</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <source>Usability for seniors: challenges and changes</source>
          <year>2020</year>
          <access-date>2020-12-18</access-date>
          <publisher-name>Nielsen Norman Group</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/articles/usability-for-senior-citizens/">https://www.nngroup.com/articles/usability-for-senior-citizens/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Perrin</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Technology use among seniors</source>
          <year>2017</year>
          <publisher-loc>Washington</publisher-loc>
          <publisher-name>Pew Research Center for Internet &#38; Technology</publisher-name>
        </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>Peacock</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Künemund</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Senior citizens and internet technology</article-title>
          <source>European journal of ageing</source>
          <year>2007</year>
          <volume>4</volume>
          <issue>4</issue>
          <fpage>191</fpage>
          <lpage>200</lpage>
        </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>Van</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Stapley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Amaturo</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Revisiting the digital divide: generational differences in technology use in everyday life</article-title>
          <source>North American Journal of Psychology</source>
          <year>2014</year>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>557</fpage>
          <lpage>574</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davidson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schimmele</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <source>Evolving internet use among Canadian seniors</source>
          <year>2019</year>
          <publisher-loc>Ottawa</publisher-loc>
          <publisher-name>Statistics Canada</publisher-name>
        </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>Cho</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pichon</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhns</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Garofalo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Schnall</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Eye-tracking retrospective think-aloud as a novel approach for a usability evaluation</article-title>
          <source>International journal of medical informatics</source>
          <year>2019</year>
          <volume>129</volume>
          <fpage>366</fpage>
          <lpage>373</lpage>
        </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>Dicianno</surname>
              <given-names>BE</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Fairman</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Crytzer</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>DX</given-names>
            </name>
            <name name-style="western">
              <surname>Pramana</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Coughenour</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Petrazzi</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Perspectives on the evolution of mobile (mHealth) technologies and application to rehabilitation</article-title>
          <source>Phys Ther</source>
          <year>2015</year>
          <month>03</month>
          <volume>95</volume>
          <issue>3</issue>
          <fpage>397</fpage>
          <lpage>405</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24925075"/>
          </comment>
          <pub-id pub-id-type="doi">10.2522/ptj.20130534</pub-id>
          <pub-id pub-id-type="medline">24925075</pub-id>
          <pub-id pub-id-type="pii">ptj.20130534</pub-id>
          <pub-id pub-id-type="pmcid">PMC4757639</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
