<?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">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v4i7e17373</article-id>
      <article-id pub-id-type="pmid">32716310</article-id>
      <article-id pub-id-type="doi">10.2196/17373</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>A Companion App to Support Rheumatology Patients Treated with Certolizumab Pegol: Results From a 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>Contreras</surname>
            <given-names>Ismael</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ji</surname>
            <given-names>Xiaojian</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Heynsbergh</surname>
            <given-names>Natalie</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Domańska</surname>
            <given-names>Barbara</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>UCB Pharma</institution>
            <addr-line>208 Bath Road</addr-line>
            <addr-line>Slough</addr-line>
            <country>United Kingdom</country>
            <phone>44 1615 197676</phone>
            <email>barbara.domanska@UCB.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7424-1726</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Vansant</surname>
            <given-names>Stijn</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2604-4776</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Mountian</surname>
            <given-names>Irina</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1510-6428</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>UCB Pharma</institution>
        <addr-line>Slough</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>UCB Pharma</institution>
        <addr-line>Brussels</addr-line>
        <country>Belgium</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Barbara Domańska <email>barbara.domanska@UCB.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>27</day>
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <volume>4</volume>
      <issue>7</issue>
      <elocation-id>e17373</elocation-id>
      <history>
        <date date-type="received">
          <day>10</day>
          <month>12</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>10</day>
          <month>3</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>5</day>
          <month>5</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>3</day>
          <month>6</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Barbara Domańska, Stijn Vansant, Irina Mountian. Originally published in JMIR Formative Research (http://formative.jmir.org), 27.07.2020.</copyright-statement>
      <copyright-year>2020</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 Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on http://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://formative.jmir.org/2020/7/e17373/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Certolizumab pegol (CZP) is an anti-tumor necrosis factor drug approved for the treatment of multiple moderate to severe chronic inflammatory diseases. In the European Union, CZP is approved for administration by subcutaneous self-injection using a prefilled syringe, prefilled pen, or reusable electromechanical auto-injector (electronic device). CimplyMe is a companion app for use alongside CZP self-injection devices, designed to support CZP-treated patients self-managing their treatment and disease.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to validate the usability of the companion app by demonstrating that tasks required for use can be performed successfully by intended end users.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We recruited 15 patients with moderate to severe rheumatoid arthritis, currently prescribed biologic treatment, and using apps on a smart phone. Patients were assessed on their ability to use the companion app in a setting designed to simulate a location where patients regularly administer biologic treatment. To assess the usability of the key features of the app, 8 critical and 3 noncritical tasks were designed. Patients’ success on each task was recorded through observations or knowledge-based questions. Successes with difficulty and use errors were also recorded. If a patient made a use error at the first attempt, a second attempt was allowed. Second-attempt use errors were recorded as a task failure.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 207 first attempts at the 14 components of the 8 critical tasks were evaluated (3 patients failed to complete one component); 178 (86.0%) critical tasks were successfully completed at the first attempt. The remaining first attempts comprised 16 (7.7%) successes with difficulty and 13 (6.3%) use errors, which had to be repeated. One critical task was not re-attempted by one patient due to time constraints; however, there were no use errors in the 12 completed second attempts. A total of 107 first attempts at the 3 noncritical tasks were made, all of which (107/107, 100.0%) were completed without use errors.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>In simulated testing, patients were able to successfully use the companion app without formal training. This study suggests the companion app is easy to use and could help patients prescribed CZP better manage their treatment and disease.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>rheumatology</kwd>
        <kwd>internet</kwd>
        <kwd>digital health</kwd>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>smartphone</kwd>
        <kwd>mobile phone</kwd>
        <kwd>validation human factors study</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Anti-tumor necrosis factors (TNFs) are established and effective treatments for moderate to severe chronic inflammatory diseases [<xref ref-type="bibr" rid="ref1">1</xref>]. The use of anti-TNFs alongside conventional disease-modifying antirheumatic drugs has been proven to result in better long-term disease control and reduced functional impairment [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
      <p>Certolizumab pegol (CZP) is an Fc-free, PEGylated anti-TNF approved for use in 66 countries [<xref ref-type="bibr" rid="ref2">2</xref>]. CZP is approved to treat adults with moderate to severe rheumatoid arthritis (RA), axial spondyloarthritis (including both radiographic and nonradiographic axial spondyloarthritis), psoriatic arthritis, and plaque psoriasis in European Union (EU) countries and is also indicated for Crohn’s disease in the United States [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. In the EU, CZP treatment is administered via prefilled syringe or prefilled pen [<xref ref-type="bibr" rid="ref5">5</xref>]. Recently, an electromechanical autoinjection device (electronic device [e-Device]), ava, has also been approved for use [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. All CZP-injection devices were designed with patient input. The e-Device aims to provide patients with customizable features to improve patient satisfaction and overall self-injection experience [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>Subcutaneous self-injection is associated with several specific challenges that can lead to reduced treatment adherence. Increasing use of smartphones and tablets provides a unique opportunity to address some of these challenges. For example, mobile phone apps can be designed to support patients and provide a means to overcome challenges such as forgetfulness [<xref ref-type="bibr" rid="ref6">6</xref>]. Previous studies looking into the effectiveness of mobile phone health apps suggest that if well designed, they may provide an effective tool, empowering patients with long-term chronic conditions to self-manage their own health [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. CimplyMe is a new mobile technology companion app designed to be used alongside any CZP self-injection device to further support and engage CZP-treated patients throughout their disease journey. By providing additional support, the companion app aims to improve patient satisfaction, treatment adherence, and resulting clinical outcomes.</p>
      <p>The aim of this study was to validate the usability of the companion app by demonstrating that critical tasks can be performed successfully by a group of patients diagnosed with RA, representative of the intended end users.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>This study assessed the usability of CimplyMe, a new mobile technology companion app designed to be used alongside any CZP self-injection device to further support and engage CZP-treated patients throughout their disease journey. The app provides step-by-step guidance through its timeline feature, providing information on the disease and CZP treatment. Guidance is focused on the initial 12 weeks of treatment but continues to support patients throughout their disease journey. Patients can track their pain, energy levels, mood, and activities using the Health Metrics Tracking feature. This is incorporated into the Health Summary that provides patients with an overview of their progress, including treatment adherence tracking, which they can choose to share with health care practitioners and their family. Milestones are included in the app and were designed to help patients acknowledge important moments in their disease journey and motivate patients to continue treatment. Additionally, injection and clinic appointment reminders aim to improve patient outcomes by supporting treatment adherence and disease monitoring.</p>
        <p>This study was designed in line with ANSI/AAMI/IEC62366-1:2015 on applying human factors and usability engineering to medical devices [<xref ref-type="bibr" rid="ref10">10</xref>]. Each participant gave informed consent before attending a single session; all sessions took place in London, United Kingdom. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the study design. Patients were not given any formal training but had some time to familiarize themselves with the app. They were also able to use an instruction manual if requested, although the app was designed to be used without this document. Patients were asked to complete 11 use scenarios that were designed to simulate the intended use of the app. A moderator asked all patients to behave in the way they thought they would if the scenario was real. During the session, a moderator recorded all observations and patient feedback in a workbook. The sessions were also video recorded.</p>
        <p>The primary study objective was to validate that the user interface of CimplyMe is intuitive, easy, and safe to use by intended users so as not to cause injury or harm. The secondary objective was to confirm that the risk of errors was reduced as far as reasonably possible through risk-mitigation methods implemented in the user interface (UI) of the beta version of the app used in this study.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Study design flowchart.</p>
          </caption>
          <graphic xlink:href="formative_v4i7e17373_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Procedures and Evaluations</title>
        <p>Patients were assessed on their ability to complete 8 critical tasks composed of 14 component tasks and 3 noncritical tasks composed of 8 component tasks (<xref ref-type="table" rid="table1">Table 1</xref>). All participants were observed and timed while completing each task by study personnel. Each test session was scheduled to last for 105 minutes (1.75 hours); the moderator divided the time allocated between each task (between approximately 3 and 10 minutes depending on the task) to ensure that the participants could at least attempt each task once. Each component task had to be completed correctly; otherwise, a use error was recorded. If a patient struggled to complete the component tasks but avoided a use error, the task was recorded as a “success with difficulty.” If a patient made a use error on their first attempt, they could attempt the task a second time. If a use error was made at the second attempt, it was recorded as a task failure. All patient actions that led to, or resulted from, successes with difficulty or use errors were recorded. Detailed root cause analysis was carried out on all tasks completed with difficulty or recorded as a use error to determine whether the cause was a result of the user interface.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Critical and noncritical tasks.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="320"/>
            <col width="650"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Tasks</td>
                <td>Use scenarios</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Critical tasks</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. Download companion app</td>
                <td>Patients were asked to explain how they would go about downloading an app.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. Jailbroken phone<sup>a</sup></td>
                <td>Patients were shown the app terms and conditions and asked to explain what the message means. They were then asked if the app can be used on a jailbroken phone.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. Set up user profile (change language)</td>
                <td>Patients were asked to change the language of the app.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>4. Set and adjust medication reminder</td>
                <td>Patients were asked to explain how they would set up medication reminders. They were asked to schedule an injection reminder and edit it, following instructions. Finally, they were asked to delete the injection reminder.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5. Manually enter injection dates</td>
                <td>Patients were told to imagine they wanted to perform their injection ahead of schedule. They were given the date and locations of the injection they had just made and were asked to register the injection in the app.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>6. Log CZP<sup>b</sup> injection date</td>
                <td>Patients were asked to log an injection date that was outside of the logging time frame and asked if they understood the confirmation screen informing them that CZP was not logged within the correct time frame.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>7. Add or edit a CZP medication schedule</td>
                <td>Patients were asked to imagine their treatment plan has changed and asked to change their dose regimen.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>8. Download app updates</td>
                <td>Patients were asked what they would do if they opened the app and an “Updates Available” screen appeared.</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Noncritical tasks</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1. Edit or delete clinical appointments</td>
                <td>Patients were asked to imagine they wanted to schedule a physician appointment and given information to input. They were then asked to edit the information they just inputted and finally to delete the reminder.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2. Error messages</td>
                <td>Several error messages from the app were presented. The patient was asked to explain what they thought the different messages mean.</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>3. Remove profile from the app</td>
                <td>Patients were asked to remove their user profile from the app.</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>A jailbroken phone is one that has bypassed restrictions to allow the user to download apps from websites other than the official app store.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>CZP: certolizumab pegol.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Participants</title>
        <p>Adult patients (≥18 years) diagnosed with moderate to severe RA were invited to participate in the study. To ensure at least 97% of potential use errors were identified [<xref ref-type="bibr" rid="ref11">11</xref>], a minimum of 15 intended users were recruited. To verify their RA diagnosis, patients were asked to provide a confirmation letter from their physician. In addition, patients had to have been prescribed biologic treatment at the time of enrollment. Patients must have been using a smart phone and had experience using apps, of any type, on their phone. Patients must also have stated that they would use a medical mobile app to assist with their disease treatment. The study aimed to recruit at least 7 patients with impaired vision, either correctable or not correctable with glasses or contact lenses.</p>
        <p>Patients were excluded if they had participated in medical device research for a medical app in the previous 6 months, were app developers, or had stated that they would not use a mobile app to assist with their disease treatment. Patients were also excluded if they experienced &#60;10 minutes of joint stiffness in the morning without treatment.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Patient Disposition and Baseline Characteristics</title>
        <p>Of the 30 patients who were screened to take part in the study, 15 patients completed the study. Of the 15 patients that did not take part, 8 were unable to provide a physician’s letter, 4 were not able to take part due to scheduling, and 2 patients self-withdrew. One patient was excluded as they were known to the sponsor. Familiarity with the use of mobile apps was a stated requirement; therefore, there were no screen failures relating to this.</p>
        <p>Patient baseline characteristics are shown in <xref ref-type="table" rid="table2">Table 2</xref>. The mean patient age was 53.5 years (SD 12.0 years), and 66.7% (10/15) patients were female. All patients were using either a prefilled syringe or prefilled pen to administer their current biologic medication.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Patient baseline characteristics.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="720"/>
            <col width="250"/>
            <thead>
              <tr valign="bottom">
                <td colspan="2">Parameter</td>
                <td>RA<sup>a</sup> patients (n=15)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">Age (years), mean (SD)</td>
                <td>53.5 (12.0)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Gender (female), n (%)</td>
                <td>10 (66.7)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Ethnicity, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="3">
                  <break/>
                </td>
                <td>White British</td>
                <td>11 (73.3)</td>
              </tr>
              <tr valign="top">
                <td>Black British</td>
                <td>2 (13.3)</td>
              </tr>
              <tr valign="top">
                <td>British Asian</td>
                <td>2 (13.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Dominant hand (right), n (%)</td>
                <td>14 (93.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Highest education level achieved, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="6">
                  <break/>
                </td>
                <td>Early years</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Primary</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Secondary</td>
                <td>4 (26.7)</td>
              </tr>
              <tr valign="top">
                <td>A-Level</td>
                <td>1 (6.7)</td>
              </tr>
              <tr valign="top">
                <td>College/university</td>
                <td>6 (40.0)</td>
              </tr>
              <tr valign="top">
                <td>Postgraduate/vocational</td>
                <td>4 (26.7)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Vision (self-reported), n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="5">
                  <break/>
                </td>
                <td>Nearly perfect</td>
                <td>4 (26.7)</td>
              </tr>
              <tr valign="top">
                <td>Need glasses to read</td>
                <td>3 (20.0)</td>
              </tr>
              <tr valign="top">
                <td>Need glasses to see into the distance</td>
                <td>2 (13.3)</td>
              </tr>
              <tr valign="top">
                <td>Need glasses to read and see into the distance</td>
                <td>6 (40.0)</td>
              </tr>
              <tr valign="top">
                <td>Impaired vision and not correctable with glasses</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Disease severity (moderate to severe), n (%)<sup>b</sup></td>
                <td>15 (100.0)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Morning joint stiffness (minutes in the morning), n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="4">
                  <break/>
                </td>
                <td>0<sup>c</sup></td>
                <td>1 (6.7)</td>
              </tr>
              <tr valign="top">
                <td>≤30</td>
                <td>4 (26.7)</td>
              </tr>
              <tr valign="top">
                <td>30-60</td>
                <td>6 (40.0)</td>
              </tr>
              <tr valign="top">
                <td>&#62;60</td>
                <td>4 (26.7)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Joints affected by RA, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="4">
                  <break/>
                </td>
                <td>Fingers</td>
                <td>12 (80.0)</td>
              </tr>
              <tr valign="top">
                <td>Hands</td>
                <td>11 (73.3)</td>
              </tr>
              <tr valign="top">
                <td>Wrists</td>
                <td>8 (53.3)</td>
              </tr>
              <tr valign="top">
                <td>Elbow</td>
                <td>5 (33.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Current biologic medication, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="4">
                  <break/>
                </td>
                <td>Etanercept</td>
                <td>6 (40.0)</td>
              </tr>
              <tr valign="top">
                <td>Certolizumab pegol</td>
                <td>2 (13.3)</td>
              </tr>
              <tr valign="top">
                <td>Adalimumab</td>
                <td>6 (40.0)</td>
              </tr>
              <tr valign="top">
                <td>Tocilizumab</td>
                <td>1 (6.7)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Type of self-injection device used, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="2">
                  <break/>
                </td>
                <td>PFS<sup>d</sup></td>
                <td>7 (46.7)</td>
              </tr>
              <tr valign="top">
                <td>PFP<sup>e</sup></td>
                <td>8 (53.3)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>RA: rheumatoid arthritis.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>Physician-determined.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>When medicated; when unmedicated, stiffness ≥10 mins.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>PFS: prefilled syringe.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>PFP: prefilled pen.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Critical Task Successes and Use Errors</title>
        <p>Throughout the study, 207 first attempts at critical component tasks were completed. Of these, 86.0% (178/207) tasks were successful; 7.7% (16/207) were successes with difficulty; and 6.3% (13/207) were use errors (<xref ref-type="table" rid="table3">Table 3</xref>). Twelve second attempts at critical tasks were completed in the study; one task was not re-attempted due to time constraints. No use errors were encountered when performing tasks for a second time, although 4 tasks were recorded as successes with difficulty (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        <p>Reasons for patient difficulties and use errors during first and second attempts at critical tasks are shown in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. Several (6/13, 46.2%) first attempts classed as use errors were cases of patients not completing the task in the allotted session time. Patients were not given a set amount of time to complete each task; however, the total time of each session was limited to 110 minutes so not all patients were able to complete all tasks within this time frame.</p>
        <p>Difficulties at the first attempt were due to various reasons; however, most (10/16, 62.5%) resulted from patients getting confused by the app terms, organization, or process (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Additionally, one difficulty was caused by an app fault. There were 4 successes with difficulty during the 12 second attempts at the critical tasks. As with those observed at first attempt, most (3/4, 75.0%) of these difficulties were due to patients getting confused by the app terms or organization (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Critical and noncritical task outcomes. </p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="280"/>
            <col width="190"/>
            <col width="220"/>
            <col width="280"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Task and attempt</td>
                <td>Success</td>
                <td>Success with difficulty</td>
                <td>Use error</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Critical tasks</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td rowspan="2">
                  <break/>
                </td>
                <td>First (n=207)</td>
                <td>178</td>
                <td>16</td>
                <td>13</td>
              </tr>
              <tr valign="bottom">
                <td>Second (n=12)<sup>a</sup></td>
                <td>8</td>
                <td>4</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Noncritical tasks</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>First (n=107)</td>
                <td>104</td>
                <td>3</td>
                <td>0</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>Only 12 patients re-attempted critical task 6, “log an injection date,” due to time constraints.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Root Cause Analysis of Critical Task Errors</title>
        <p>The root cause analysis of all use errors is shown in <xref ref-type="table" rid="table4">Table 4</xref>. The UI contributed to 61.5% (8/13) of use errors. Of these, 42.9% (3/8) were attributable to the small font size in the instructions for use (IFU). In 37.5% (3/8) of the use errors, patients did not see or were not prompted to scroll to the necessary button(s). The remaining errors associated with the UI (2/8, 25.0%) were attributed to app complexity or lack of clarity.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Root cause analysis of all use errors.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="370"/>
            <col width="300"/>
            <col width="300"/>
            <thead>
              <tr valign="bottom">
                <td colspan="2">Task and patient actions</td>
                <td>Root cause</td>
                <td>Did the UI<sup>a</sup> contribute to the use error?</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>4. Set and adjust medication reminder</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P09: did not save the reminder; opened IFU<sup>b</sup> but did not read it after realizing it was 120 pages</td>
                <td>Perception/cognition: expected the app to have a more assistive role in setting up a reminder</td>
                <td>Yes: expected the app to do more and did not read the IFU</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P02: tried to edit the reminder but deleted it; confused tracking reminder and injection reminder</td>
                <td>Cognition: did not understand what “Tracking Reminder” meant</td>
                <td>Yes: unsure what tracking reminder meant</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>5. Manually enter injection dates</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P03: did not register second injection</td>
                <td>Perception/cognition: did not see the “Add Another” button and thought they would add both injections to the same image</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P04: took a long time to understand the task</td>
                <td>Perception/cognition: could not see or understand where to register an injection</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P05: only registered one injection</td>
                <td>Perception: did not see the “Add Another” button</td>
                <td>Yes: did not see the “Add Another” button, only “Done”</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P06: kept trying to register injections through health tracking</td>
                <td>Cognition: did not know where to go to register injections</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P10: did not scroll down to see “register injection”</td>
                <td>Perception/cognition: did not see the button and did not think to continue scrolling</td>
                <td>Yes: “Register Injection” was not visible on the screen, and there was nothing on the screen to suggest scrolling down</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P12: registered an injection but could not register a second injection</td>
                <td>Cognition: expected to add both injections on the same image</td>
                <td>Yes: text was very small in the IFU, which led to the patient skimming the text</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>7. Add or edit a CZP<sup>c</sup> medication schedule</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P02: expected “Change Treatment Plan” to be on the timeline</td>
                <td>Cognition: thought they were looking in the obvious place to look</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P04: took a long time to complete the task</td>
                <td>Cognition: struggled with the terminology of the app</td>
                <td>No: patient struggled with the terminology throughout</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P09: expected to edit their dose regimen through the calendar</td>
                <td>Perception: did not see the section in profile</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P11: not able to find where to edit the medication schedule</td>
                <td>Perception/cognition: not able to find where to complete the task</td>
                <td>Yes: patient said the complexity of the app made it more difficult</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>P04: thought the app was faulty when the confirmation screen appeared</td>
                <td>Cognition: patient found it difficult to understand the language and reasoning behind the confirmation screen</td>
                <td>Yes: text could have been bigger and use of colors clearer</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>UI: user interface.</p>
            </fn>
            <fn id="table4fn2">
              <p><sup>b</sup>IFU: instructions for use.</p>
            </fn>
            <fn id="table4fn3">
              <p><sup>c</sup>CZP: certolizumab pegol.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Noncritical Task Successes and Use Errors</title>
        <p>A total of 107 first attempts at the 3 noncritical tasks were performed in the study. Of these, 97.2% (104/107) were successful, 2.8% (3/107) were successes with difficulty, and none were use errors (<xref ref-type="table" rid="table3">Table 3</xref>). Reasons for patient difficulties when completing noncritical tasks are shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Reasons for noncritical task difficulties and use errors at first attempt. The number of patients who completed noncritical tasks was &#60;15 as some patients did not have time to complete all tasks during the session.</p>
          </caption>
          <graphic xlink:href="formative_v4i7e17373_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>No failures were observed for any of the attempted tasks; all patients were able to successfully complete both critical and noncritical tasks using the companion app on their first or second attempt without any formal training.</p>
        <p>There were several instances where use errors could be attributed to the UI; these can all be resolved by small changes to the app. For example, patients did not realize that they needed to scroll further down the page to find the correct information or buttons in multiple instances. To minimize this problem, the scaling of the app could be optimized to ensure that most buttons are always on the screen. If future feedback suggests patients still have difficulties, a small note or animation could be added to indicate the need to scroll down on first use. Additionally, patients found the font size in the IFU and app too small or did not read the IFU because it was too long. However, the font size on the app is dependent on the default font size settings on the patient’s phone and can be changed by the patient, if necessary. Two patients did not understand the terminology used in the app, or struggled with the complexity of the app itself, resulting in confusion and error in completing tasks and navigating the app. However, this was likely due to the short amount of time patients were given to familiarize themselves with the app. It is anticipated that patient understanding of the app’s terminology and layout would improve with use, as indicated by the reduction in errors when tasks were attempted for a second time in this study.</p>
        <p>Mobile technology apps have been developed to provide information and patient education, facilitate lifestyle changes as a strategy to ameliorate disease, provide medication reminders to promote treatment adherence, and record patient metrics for disease monitoring [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Previous research suggests that mobile technology apps can help patients feel supported and improve patient satisfaction [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. For example, compared to usual care, a mobile health technology–supported disease management model for atrial fibrillation resulted in improvements in patient quality of life [<xref ref-type="bibr" rid="ref17">17</xref>]. Patient adherence and disease management may also be improved with the support of treatment management apps [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. For example, a 2019 systematic literature review of studies investigating mobile apps as a method to improve treatment adherence identified 11 studies of patients with a variety of diseases [<xref ref-type="bibr" rid="ref18">18</xref>]. Of these, 7 studies reported an increase in treatment adherence with use of a mobile app [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>One of the key challenges associated with the use of mobile apps is the high user attrition rate, with the level of mobile app engagement dropping off over time [<xref ref-type="bibr" rid="ref20">20</xref>]. Understanding the features and characteristics most valued by patients may improve app engagement. Users appreciate features that save time over current methods and identify an app as valuable when it is simple and intuitive to use, provides specific instructions to better manage a condition, shares data with designated individuals, and incorporates motivational “push” factors [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Increasing age is also associated with reduced use of smartphones for internet browsing, social media, and apps [<xref ref-type="bibr" rid="ref22">22</xref>]. Consequently, mobile app attrition is likely to be increasingly challenging in the population of patients likely to use mobile apps such as CimplyMe; patients with chronic inflammatory diseases are likely to be older and so are likely to be less comfortable using mobile apps. Designing apps with the user in mind and assessing usability in human factors studies will help ensure successful patient engagement.</p>
      </sec>
      <sec>
        <title>Study Limitations</title>
        <p>Human factors studies only simulate use in an everyday environment. Patients were asked to behave in the way they thought they would if the scenario was real; however, this may be difficult to judge accurately. Each session was limited to 105 minutes, and, as a result, patients may have felt under some time pressure to complete each task. Time constraints also restricted patients’ ability to familiarize themselves with the app. Additionally, each task was completed discretely, which may have interfered with their familiarization of the app, owing to the lack of continuity between tasks. Patients were selected based on their willingness to use mobile apps, which may limit the generalizability of the results; however, the app will be provided as an additional support component and so use by patients will be voluntary. Therefore, the study population is reflective of the final population of patients who would likely use this in clinical practice. Finally, the number of patients participating in the study was small; therefore, the results may not represent the app’s usability in a wider patient group or capture all potential use errors and difficulties when using the app.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In a simulated setting, patients were able to use the companion app successfully. No critical task failures were observed; all patients were able to successfully complete both critical and noncritical tasks within two attempts without any formal training. This study demonstrates that the companion app UI is generally intuitive and easy to use among patients familiar with using apps. The app could support CZP patients to self-manage their treatment.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Reasons for critical task difficulties and use errors. Only 12 patients completed critical task 6 (“log an injection date”) due to time constraints.</p>
        <media xlink:href="formative_v4i7e17373_app1.png" xlink:title="PNG File , 267 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CZP</term>
          <def>
            <p>certolizumab pegol</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">e-Device</term>
          <def>
            <p>electronic device</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">IFU</term>
          <def>
            <p>instructions for use</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">RA</term>
          <def>
            <p>rheumatoid arthritis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">TNF</term>
          <def>
            <p>tumor necrosis factor</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">UI</term>
          <def>
            <p>user interface</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors thank the patients, the investigators, and their teams who took part in this study. The authors also acknowledge Susanne Wiegratz, UCB Pharma, Monheim am Rhein, Germany, for publication coordination and Oliver Palmer, BSc (Hons), Emma Phillips, PhD, and Simon Foulcer, PhD, from Costello Medical, United Kingdom, for medical writing and editorial assistance based on the authors’ input and direction; their support was funded by UCB Pharma in accordance with Good Publication Practice (GPP3) guidelines (http://www.ismpp.org/gpp3). The development of the CimplyMe app and this study were sponsored by UCB Pharma. </p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>BD, SV, and IM contributed substantially to study conception and design as well as the analysis and interpretation of the data; drafted the article or revised it critically for important intellectual content; and approved the final version of the article to be published.</p>
      </fn>
      <fn fn-type="conflict">
        <p>BD, SV, and IM are employees of UCB Pharma.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Udalova</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Monaco</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Nanchahal</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Feldmann</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Anti-TNF Therapy</article-title>
          <source>Microbiol Spectr</source>
          <year>2016</year>
          <month>08</month>
          <volume>4</volume>
          <issue>4</issue>
          <pub-id pub-id-type="doi">10.1128/microbiolspec.MCHD-0022-2015</pub-id>
          <pub-id pub-id-type="medline">27726761</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Mariette</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Gaujoux-Viala</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Blauvelt</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kvien</surname>
              <given-names>TK</given-names>
            </name>
            <name name-style="western">
              <surname>Sandborn</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Winthrop</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>de Longueville</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Huybrechts</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Bykerk</surname>
              <given-names>VP</given-names>
            </name>
          </person-group>
          <article-title>Long-term safety of certolizumab pegol in rheumatoid arthritis, axial spondyloarthritis, psoriatic arthritis, psoriasis and Crohn's disease: a pooled analysis of 11 317 patients across clinical trials</article-title>
          <source>RMD Open</source>
          <year>2019</year>
          <month>05</month>
          <day>31</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>e000942</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://rmdopen.bmj.com/cgi/pmidlookup?view=long&#38;pmid=31245056"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/rmdopen-2019-000942</pub-id>
          <pub-id pub-id-type="medline">31245056</pub-id>
          <pub-id pub-id-type="pii">rmdopen-2019-000942</pub-id>
          <pub-id pub-id-type="pmcid">PMC6560674</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>Cimzia Summary of Product Characteristics</article-title>
          <source>European Medicines Agency</source>
          <year>2018</year>
          <access-date>2020-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ema.europa.eu/docs/en_GB/document_library/EPAR_-_Product_Information/human/001037/WC500069763.pdf">http://www.ema.europa.eu/docs/en_GB/document_library/EPAR_-_Product_Information/human/001037/WC500069763.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Cimzia Prescribing Information</article-title>
          <source>United Stated Food and Drug Administration</source>
          <year>2018</year>
          <access-date>2020-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.accessdata.fda.gov/drugsatfda_docs/label/2018/125160s283lbl.pdf">https://www.accessdata.fda.gov/drugsatfda_docs/label/2018/125160s283lbl.pdf</ext-link>
          </comment>
        </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>Domańska</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Stumpp</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Poon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Oray</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mountian</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Pichon</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Using Patient Feedback to Optimize the Design of a Certolizumab Pegol Electromechanical Self-Injection Device: Insights from Human Factors Studies</article-title>
          <source>Adv Ther</source>
          <year>2017</year>
          <month>12</month>
          <day>8</day>
          <volume>35</volume>
          <issue>1</issue>
          <fpage>100</fpage>
          <lpage>115</lpage>
          <pub-id pub-id-type="doi">10.1007/s12325-017-0645-1</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>Singh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Drouin</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Newmark</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rozenblum</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Landman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pabo</surname>
              <given-names>Erika</given-names>
            </name>
            <name name-style="western">
              <surname>Klinger</surname>
              <given-names>Elissa V</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>David W</given-names>
            </name>
          </person-group>
          <article-title>Developing a Framework for Evaluating the Patient Engagement, Quality, and Safety of Mobile Health Applications</article-title>
          <source>Issue Brief (Commonw Fund)</source>
          <year>2016</year>
          <month>02</month>
          <volume>5</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="medline">26934758</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>Salimzadeh</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Damanabi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kalankesh</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ferdousi</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Mobile Applications for Multiple Sclerosis: a Focus on Self-Management</article-title>
          <source>Acta Inform Med</source>
          <year>2019</year>
          <month>03</month>
          <volume>27</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31213737"/>
          </comment>
          <pub-id pub-id-type="doi">10.5455/aim.2019.27.12-18</pub-id>
          <pub-id pub-id-type="medline">31213737</pub-id>
          <pub-id pub-id-type="pii">AIM-27-12</pub-id>
          <pub-id pub-id-type="pmcid">PMC6511265</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mahmood</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kedia</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wyant</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Ahn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bhuyan</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>Use of mobile health applications for health-promoting behavior among individuals with chronic medical conditions</article-title>
          <source>Digit Health</source>
          <year>2019</year>
          <month>10</month>
          <day>10</day>
          <volume>5</volume>
          <fpage>2055207619882181</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31656632"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2055207619882181</pub-id>
          <pub-id pub-id-type="medline">31656632</pub-id>
          <pub-id pub-id-type="pii">10.1177_2055207619882181</pub-id>
          <pub-id pub-id-type="pmcid">PMC6791047</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Effective behavioral intervention strategies using mobile health applications for chronic disease management: a systematic review</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2018</year>
          <month>02</month>
          <day>20</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-018-0591-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-018-0591-0</pub-id>
          <pub-id pub-id-type="medline">29458358</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-018-0591-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC5819153</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Medical devices Part 1: Application of usability engineering to medical devices</article-title>
          <source>ANSI/AAMI/IEC 62366-1</source>
          <year>2015</year>
          <access-date>2020-04-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://my.aami.org/aamiresources/previewfiles/6236601_1503_preview.pdf">https://my.aami.org/aamiresources/previewfiles/6236601_1503_preview.pdf</ext-link>
          </comment>
        </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>Faulkner</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Beyond the five-user assumption: Benefits of increased sample sizes in usability testing</article-title>
          <source>Behavior Research Methods, Instruments, &#38; Computers</source>
          <year>2003</year>
          <month>8</month>
          <volume>35</volume>
          <issue>3</issue>
          <fpage>379</fpage>
          <lpage>383</lpage>
          <pub-id pub-id-type="doi">10.3758/bf03195514</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cahn</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Akirov</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Raz</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Digital health technology and diabetes management</article-title>
          <source>Journal of Diabetes</source>
          <year>2017</year>
          <month>11</month>
          <day>06</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.1111/1753-0407.12606</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Santo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>CK</given-names>
            </name>
            <name name-style="western">
              <surname>Thiagalingam</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chalmers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Redfern</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>MEDication reminder APPs to improve medication adherence in Coronary Heart Disease (MedApp-CHD) Study: a randomised controlled trial protocol</article-title>
          <source>BMJ Open</source>
          <year>2017</year>
          <month>10</month>
          <day>08</day>
          <volume>7</volume>
          <issue>10</issue>
          <fpage>e017540</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://bmjopen.bmj.com/cgi/pmidlookup?view=long&#38;pmid=28993388"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2017-017540</pub-id>
          <pub-id pub-id-type="medline">28993388</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2017-017540</pub-id>
          <pub-id pub-id-type="pmcid">PMC5640083</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tabi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Randhawa</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Mithani</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Albers</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Schnieder</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nikoo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vigo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Demlova</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Krausz</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile Apps for Medication Management: Review and Analysis</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>09</month>
          <day>11</day>
          <volume>7</volume>
          <issue>9</issue>
          <fpage>e13608</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/9/e13608/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13608</pub-id>
          <pub-id pub-id-type="medline">31512580</pub-id>
          <pub-id pub-id-type="pii">v7i9e13608</pub-id>
          <pub-id pub-id-type="pmcid">PMC6786858</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Santo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Singleton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Thiagalingam</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chalmers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>CK</given-names>
            </name>
            <name name-style="western">
              <surname>Redfern</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Medication reminder applications to improve adherence in coronary heart disease: a randomised clinical trial</article-title>
          <source>Heart</source>
          <year>2018</year>
          <month>08</month>
          <day>27</day>
          <volume>105</volume>
          <issue>4</issue>
          <fpage>323</fpage>
          <lpage>329</lpage>
          <pub-id pub-id-type="doi">10.1136/heartjnl-2018-313479</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Torbjørnsen</surname>
              <given-names>Astrid</given-names>
            </name>
            <name name-style="western">
              <surname>Ribu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rønnevig</surname>
              <given-names>Marit</given-names>
            </name>
            <name name-style="western">
              <surname>Grøttland</surname>
              <given-names>Astrid</given-names>
            </name>
            <name name-style="western">
              <surname>Helseth</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Users' acceptability of a mobile application for persons with type 2 diabetes: a qualitative study</article-title>
          <source>BMC Health Serv Res</source>
          <year>2019</year>
          <month>09</month>
          <day>06</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>641</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-019-4486-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-019-4486-2</pub-id>
          <pub-id pub-id-type="medline">31492176</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-019-4486-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC6729081</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>Guo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lane</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lip</surname>
              <given-names>GY</given-names>
            </name>
          </person-group>
          <article-title>Mobile Health Technology for Atrial Fibrillation Management Integrating Decision Support, Education, and Patient Involvement: mAF App Trial</article-title>
          <source>The American Journal of Medicine</source>
          <year>2017</year>
          <month>12</month>
          <volume>130</volume>
          <issue>12</issue>
          <fpage>1388</fpage>
          <lpage>1396.e6</lpage>
          <pub-id pub-id-type="doi">10.1016/j.amjmed.2017.07.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pérez-Jover</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Sala-González</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Guilabert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mira</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>Mobile Apps for Increasing Treatment Adherence: Systematic Review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>06</month>
          <day>18</day>
          <volume>21</volume>
          <issue>6</issue>
          <fpage>e12505</fpage>
          <pub-id pub-id-type="doi">10.2196/12505</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>Faridi</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liberti</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shuval</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Northrup</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>DL</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the impact of mobile telephone technology on type 2 diabetic patients’ self-management: the NICHE pilot study</article-title>
          <source>J Eval Clin Pract</source>
          <year>2008</year>
          <month>06</month>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>465</fpage>
          <lpage>469</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1365-2753.2007.00881.x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Druce</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Dixon</surname>
              <given-names>WG</given-names>
            </name>
            <name name-style="western">
              <surname>McBeth</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Maximizing Engagement in Mobile Health Studies</article-title>
          <source>Rheumatic Disease Clinics of North America</source>
          <year>2019</year>
          <month>05</month>
          <volume>45</volume>
          <issue>2</issue>
          <fpage>159</fpage>
          <lpage>172</lpage>
          <pub-id pub-id-type="doi">10.1016/j.rdc.2019.01.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mendiola</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Kalnicki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lindenauer</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Valuable Features in Mobile Health Apps for Patients and Consumers: Content Analysis of Apps and User Ratings</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2015</year>
          <month>05</month>
          <day>13</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>e40</fpage>
          <pub-id pub-id-type="doi">10.2196/mhealth.4283</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hemmige</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Kallen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Arya</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile phones may not bridge the digital divide: a look at mobile phone literacy in an underserved patient population</article-title>
          <source>Cureus</source>
          <year>2019</year>
          <month>02</month>
          <day>20</day>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>e4104</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31057998"/>
          </comment>
          <pub-id pub-id-type="doi">10.7759/cureus.4104</pub-id>
          <pub-id pub-id-type="medline">31057998</pub-id>
          <pub-id pub-id-type="pmcid">PMC6476614</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
