<?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">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v21i5e10318</article-id>
      <article-id pub-id-type="pmid">31094334</article-id>
      <article-id pub-id-type="doi">10.2196/10318</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 Human-Centered Design to Build a Digital Health Advisor for Patients With Complex Needs: Persona and Prototype Development</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>Zhang</surname>
            <given-names>Wenhui</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Blondon</surname>
            <given-names>Katie</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="author" id="contrib1" corresp="yes">
          <name name-style="western">
            <surname>Bhattacharyya</surname>
            <given-names>Onil</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Women's College Hospital</institution>
            <institution>Institute for Health Systems Solutions and Virtual Care</institution>
            <institution>University of Toronto</institution>
            <addr-line>WCH, 6th Fl</addr-line>
            <addr-line>76 Grenville St</addr-line>
            <addr-line>Toronto, ON,</addr-line>
            <country>Canada</country>
            <phone>1 416 323 6400 ext 5217</phone>
            <fax>1 416 323 7323</fax>
            <email>onil.bhattacharyya@wchospital.ca</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-5219-7288</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib2">
          <name name-style="western">
            <surname>Mossman</surname>
            <given-names>Kathryn</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-4898-1659</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib3">
          <name name-style="western">
            <surname>Gustafsson</surname>
            <given-names>Lovisa</given-names>
          </name>
          <degrees>MBA</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-4734-1956</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib4">
          <name name-style="western">
            <surname>Schneider</surname>
            <given-names>Eric C</given-names>
          </name>
          <degrees>MSc, MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1132-5084</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
      <label>1</label>
      <institution>Institute for Health Systems Solutions and Virtual Care</institution>  
      <institution>Women's College Hospital</institution>
      <institution>University of Toronto</institution>  
      <addr-line>Toronto, ON</addr-line>
      <country>Canada</country></aff>
      <aff id="aff2">
      <label>2</label>
      <institution>Department of Family and Community Medicine</institution>
      <institution>University of Toronto</institution>  
      <addr-line>Toronto, ON</addr-line>
      <country>Canada</country></aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Commonwealth Fund</institution>
        <addr-line>New York City, NY</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Onil Bhattacharyya 
        <email>onil.bhattacharyya@wchospital.ca</email></corresp>
      </author-notes>
      <pub-date pub-type="collection"><month>05</month><year>2019</year></pub-date>
      <pub-date pub-type="epub">
        <day>09</day>
        <month>05</month>
        <year>2019</year>
      </pub-date>
      <volume>21</volume>
      <issue>5</issue>
      <elocation-id>e10318</elocation-id>
      <!--history from ojs - api-xml-->
      <history>
        <date date-type="received">
          <day>6</day>
          <month>3</month>
          <year>2018</year>
        </date>
        <date date-type="rev-request">
          <day>5</day>
          <month>8</month>
          <year>2018</year>
        </date>
        <date date-type="rev-recd">
          <day>28</day>
          <month>11</month>
          <year>2018</year>
        </date>
        <date date-type="accepted">
          <day>28</day>
          <month>12</month>
          <year>2018</year>
        </date>
      </history>
      <copyright-statement>©Onil Bhattacharyya, Kathryn Mossman, Lovisa Gustafsson, Eric C Schneider. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 09.05.2019.</copyright-statement>
      <copyright-year>2019</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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2019/5/e10318/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Twenty years ago, a “Guardian Angel” or comprehensive digital health advisor was proposed to empower patients to better manage their own health. This is now technically feasible, but most digital applications have narrow functions and target the relatively healthy, with few designed for those with the greatest needs.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The goal of the research was to identify unmet needs and key features of a general digital health advisor for frail elderly and people with multiple chronic conditions and their caregivers.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>In-depth interviews were used to develop personas and use cases, and iterative feedback from participants informed the creation of a low-fidelity prototype of a digital health advisor. Results were shared with developers, investors, regulators, and health system leaders for suggestions on how this could be developed and disseminated.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Patients highlighted the following goals: “live my life,” “love my life,” “manage my health,” and “feel understood.” Patients and caregivers reported interest in four functions to address these goals: tracking and insights, advice and information, providing a holistic picture of the patient, and coordination and communication. Experts and system stakeholders felt the prototype was technically feasible, and that while health care delivery organizations could help disseminate such a tool, it should be done in partnership with consumer-focused organizations.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study describes the key features of a comprehensive digital health advisor, but to spur its development, we need to clarify the business case and address the policy, organizational, and cultural barriers to creating tools that put patients and their goals at the center of the health system.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>chronic disease</kwd>
        <kwd>user-centered design</kwd>
        <kwd>medical applications</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Twenty years ago, Peter Szolovits and colleagues proposed a digital “Guardian Angel” built on the notion that information systems designers might shift focus from serving health institutions to empowering the individual patient [<xref ref-type="bibr" rid="ref1">1</xref>]. The Guardian Angel (or digital health advisor) would collect individual patient data, monitor health conditions, interpret health information for patients, help customize treatment plans, share information with the care team, and provide reminders and alerts about medications and appointments. With recent technological advances, the capacity to create a digital health advisor is now within reach, but it has yet to emerge. One barrier to the development of a digital health advisor might be the lack of a clear set of requirements to inform its design. Although there are a range of tools that perform some related functions and a few studies that cover some needs, they have not been presented in a way that is actionable for developers [<xref ref-type="bibr" rid="ref2">2</xref>]. The Commonwealth Fund, a foundation whose goal is to improve access to health care, has been exploring this opportunity through its program on the information technology (IT)-enabled consumer. The fund has a particular interest in models of care for high-need, high-cost (HNHC) patients and ways to enhance coordination as well as patient and caregiver engagement [<xref ref-type="bibr" rid="ref3">3</xref>]. We sought to determine how the concerns of HNHC patients and their caregivers might be met through digital tools in order to communicate this to the stakeholders who can create and distribute these tools. This paper describes this strategy, highlighting the use of persona development and an illustrative prototype to engage key stakeholders in order to promote the creation of a digital health advisor for the people who could derive the most benefit.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Solutions to Improve the Care of High-Need, High-Cost Patients</title>
        <p>Information and communication technologies (ICTs) have transformed many industries, often by reconfiguring services around the needs of consumers. But health care has lagged behind. Many of the current consumer-facing applications target people who are relatively healthy [<xref ref-type="bibr" rid="ref4">4</xref>]. There has been less focus on the 5% of the population who account for nearly 50% of all system costs in the United States and in other regions [<xref ref-type="bibr" rid="ref5">5</xref>]. These HNHC individuals often have multiple chronic conditions and are more likely to be lower income and face housing and food insecurity [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. They are poorly served by a health system built around diseases and institutions that often results in fragmented and competing care [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Among population segments, frail elderly are the most likely (46.2%) to be high cost, followed by adults under 65 years with disability and adults with major complex chronic disease [<xref ref-type="bibr" rid="ref12">12</xref>]. They all have to engage in a variety of activities to improve their health [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>], and digital technologies may be able to assist. As the largest subgroup, seniors are increasingly adopting technology, with 76% using cell phones, 64% using computers, 43% using the internet, and 40% using email and texting [<xref ref-type="bibr" rid="ref15">15</xref>]. They are already engaging with some of these new approaches in health care: 16% of seniors search the internet to obtain health information, 8% to fill prescriptions, 7% to contact physicians, and 5% to handle insurance matters [<xref ref-type="bibr" rid="ref15">15</xref>]. However, while there are more than 165,000 health apps currently available, a 2016 review found that most available digital tools for chronic disease are piecemeal, have limited functionality, and do not address the needs of patients with complex chronic conditions [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Furthermore, a review of evaluations of apps for conditions associated with higher needs found that most studies were small and few assessed process or outcome measures [<xref ref-type="bibr" rid="ref17">17</xref>]. Another review compiled proposed functions from different studies and highlighted that tools should be developed with user needs in mind [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      </sec>
      <sec>
        <title>Understanding and Communicating User Needs</title>
        <p>Human-centered design (HCD) has been used to develop many transformative ICT solutions, is routine in a range of industries, and is increasingly applied in health care [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref27">27</xref>]. HCD is a problem-focused method that emerged from the fields of industrial design and (more recently) software development [<xref ref-type="bibr" rid="ref28">28</xref>-<xref ref-type="bibr" rid="ref30">30</xref>]. Strengths of design thinking include rapidly developing a deep understanding of user needs and then communicating them in ways that are emotionally engaging and actionable. This approach often involves interviews, observation, and immersion in a user’s context to develop user personas, or archetypes, and use cases [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. A persona is a detailed description of a fictional person (often a composite of real individuals) used to communicate the key motivations, concerns, and interests of a user group [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Related to the persona is a use case or user story, which is a story with a plot describing the actions and decisions of a user in a particular context [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. These representations can help designers foster empathy, better understand user needs, and develop new service options and tools [<xref ref-type="bibr" rid="ref26">26</xref>]. Persona development has been used in a number of studies, but they have focused on specific chronic conditions (eg, older adults with diabetes [<xref ref-type="bibr" rid="ref31">31</xref>], heart disease [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>], or multiple sclerosis [<xref ref-type="bibr" rid="ref34">34</xref>]) or groups like high users of the emergency department [<xref ref-type="bibr" rid="ref35">35</xref>]. One study created personas of the “oldest old” but focused on implications for the design of computer interfaces [<xref ref-type="bibr" rid="ref27">27</xref>]. None of these studies looked at a range of HNHC patients, and none were focused on designing a general tool to help achieve patient goals like the digital health advisor.</p>
      </sec>
      <sec>
        <title>Designing a Prototype for a Digital Health Advisor</title>
        <p>The Commonwealth Fund was interested in developing a vision of a digital health advisor that could meet the needs of HNHC patients and using this to encourage its development in the health care marketplace by developers, entrepreneurs, investors, health system providers, funders, and regulators. The Fund worked with the design firm gravitytank to identify the needs of HNHC patients and their caregivers and create a low-fidelity prototype, which simulates key features of interest to this group without building out any of the functions [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. This involved interviews with experts, 8 patient-caregiver pairs of people with multiple chronic conditions or frail elderly, and mapping the workflow of 3 care managers with similar patients [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. Based on analysis of these data, a rough prototype of a digital health advisor was created and shared with patients and caregivers so they could provide feedback on the usability and functionality of the tool. This informed different outputs to make the insights more actionable.</p>
        
          </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
        <p>First, the needs of patients with multiple chronic conditions and the frail elderly and their caregivers were characterized, focusing on the intersection of functional and emotional needs with medical and personal needs (see <xref ref-type="fig" rid="figure1">Figure 1</xref>). Patients felt that a tool that addressed functional needs could improve health outcomes, but if a tool addressed emotional needs they would be more likely to use it on an ongoing basis. One link between the functional and emotional was having a tool that could connect goals to functions and orient care so that it can better manage their conditions in order to increase their ability to do the things that make life worthwhile. They highlighted the challenges of communicating with family members about end of life, sharing goals, navigating apps, and approval processes. They also had difficulty understanding the wide range of uncoordinated advice they receive and following through on the subset of recommendations that address their needs. Based on these interviews, 4 patient personas and 2 caregiver personas were developed (see <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>) along with 4 use cases (see <xref ref-type="fig" rid="figure2">Figure 2</xref> for an example). Last, a low-fidelity prototype of a digital health advisor was developed with a number of key features (see <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, with screenshots in <xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>) [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
        
        
         <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Key themes regarding patient needs.</p>
          </caption>
          <graphic xlink:href="jmir_v21i5e10318_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        
        
        
        
        
        <boxed-text id="box1" position="float">
          <title>Overview of patient and caregiver personas.</title>
          <p><bold>Patient personas</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>“John”</p>
              <list list-type="bullet">
                <list-item>
                  <p>An 87-year-old frail elderly man dealing with arthritis, hypertension, and mild cognitive impairment</p>
                </list-item>
                <list-item>
                  <p>He needs a tool to reach out to loved ones when he needs help, communicate his goals and current level of function, and give prompts for key health behaviors</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>“Elizabeth”</p>
              <list list-type="bullet">
                <list-item>
                  <p>A 70-year-old elderly patient with multiple chronic conditions</p>
                </list-item>
                <list-item>
                  <p>She needs help managing her medications, tracking her health status, and learning about activities to improve her health</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>“Karen”</p>
              <list list-type="bullet">
                <list-item>
                  <p>A 65-year-old patient with multiple chronic conditions</p>
                </list-item>
                <list-item>
                  <p>She needs help coordinating her care with her providers, managing her conditions, and accessing relevant health and social services</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>“Jasmine”</p>
              <list list-type="bullet">
                <list-item>
                  <p>A 44-year-old patient with a major chronic condition</p>
                </list-item>
                <list-item>
                  <p>She needs help communicating with her family about her health, managing ongoing symptoms, and learning about new treatments</p>
                </list-item>
              </list>
            </list-item>
          </list>
          <p><bold>Caregiver personas</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>“Beth”</p>
              <list list-type="bullet">
                <list-item>
                  <p>A 79-year-old caregiving spouse</p>
                </list-item>
                <list-item>
                  <p>She needs help managing her spouse’s medications and appointments and connecting with medical and community resources</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>“Lisa”</p>
              <list list-type="bullet">
                <list-item>
                  <p>A 45-year-old caregiver for her elderly mother</p>
                </list-item>
                <list-item>
                  <p>She needs help coordinating her mother’s care, remotely monitoring her health status, and communicating with family members regarding her mother’s health</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
        
        
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Sample use case for digital health advisor: John is an 87-year-old man living in San Mateo, California, with hypertension, arthritis, and mild cognitive impairment. He has been feeling more tired, anxious, and clumsy recently. He lives with his wife, who is his primary caregiver, and gets help from his daughter. He has an upcoming appointment with a geriatrician and he’s concerned whether this new doctor will understand what his needs are. He would like to update his doctors and highlight his activities and goals to share a more holistic picture of his life with the care team. He also wants to manage his doctor appointments and keep track of what his doctor tells him.</p>
          </caption>
          <graphic xlink:href="jmir_v21i5e10318_fig2.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        
        
        
        
        <boxed-text id="box2" position="float">
          <title>Key features of a digital health advisor for high-need, high-cost patients and their caregivers.</title>
          <p><bold>Tracking and insights:</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>Metrics dashboard collects health data such as blood pressure, oxygen levels, and gait from sensors and connected devices or receives manual input on symptoms</p>
            </list-item>
            <list-item>
              <p>Tracks current state before a medical visit or patterns over time, provides recommendations to patients, and informs the care team of changes in health status</p>
            </list-item>
            <list-item>
              <p>Highlights patient’s functional status and summarizes current symptom and risk factor control for different diseases so that care can focus on improving key functions</p>
            </list-item>
          </list>
          <p><bold>Advice and information:</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>Personalized advice on health-related questions either through integration with a digital assistant or by connecting to a medical practitioner by text, voice, or video</p>
            </list-item>
            <list-item>
              <p>This advice would draw on information from medical records, personal metrics, insurance coverage, and available community resources</p>
            </list-item>
            <list-item>
              <p>The advice would either elicit or incorporate known preferences into recommendations</p>
            </list-item>
          </list>
          <p><bold>Holistic picture:</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>A care journal and patient profile where patients can provide a brief image, a written summary of their story, and a set of goals and milestones they want to track</p>
            </list-item>
            <list-item>
              <p>This would include a checklist of care preferences to help create a comprehensive picture of their life to share with practitioners and foster deeper connections with their medical team and caregivers</p>
            </list-item>
          </list>
          <p><bold>Coordination and communication:</bold></p>
          <list list-type="bullet">
            <list-item>
              <p>A shared calendar with all appointments, a document center, and a task manager to improve coordination and communication between patients and their care team, including help with scheduling and transportation</p>
            </list-item>
            <list-item>
              <p>This would also include transparent communications between providers about a patient’s care to highlight areas of ambiguity and ensure agreement between members of the team</p>
            </list-item>
          </list>
        </boxed-text>
       
        
    
      <p>The personas and prototypes of the digital health advisor were presented to a group of policymakers; regulators; clinicians; experts in informatics, advertising, and health services; patient advocates; technology industry executives; and health system leaders. They felt that most components are technically feasible using current technology, although further development is needed in decision support. Patients and participants from the advertising industry highlighted the need for relatability of the tool and a “stickiness” that made it the first thing patients turn to when they have a question about their health. They highlighted the need for a simple visual interface and opportunities for voice activation to benefit those with low literacy or cognitive challenges. Health system leaders highlighted how a dashboard with trends and the current state could make visits more efficient for people with complex conditions, by reducing the time needed to collect this information, leaving more time to discuss how to advance particular goals of care. They also mentioned how a tool to share detailed but actionable information on goals, functional status, physiologic parameters, and current burden of treatment could facilitate challenging therapeutic decisions involving multiple providers. Representatives from health care delivery organizations were felt to be critical to the development of a digital health advisor but stressed that it would also need to foster support in target communities, including patients, caregivers, families, and social networks. They stated that extensive collaboration is needed to develop a robust digital health advisor, which should be an integrated suite of tools. They also highlighted that novel analytics are not sufficient; data must be made available in a usable format, and the necessary data for real-time decision making (eg, cost, quality, availability of services) are currently held by many different groups in different formats. They suggested a useful digital health advisor is more likely to emerge in response to partnerships with organizations focused on consumer needs, such as consumer advocacy groups and large retail companies. Business cases and policy incentives need to be developed to encourage broad data sharing among community, government, and commercial initiatives.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Designing Tools and Systems That Will Meet Patient Needs</title>
        <p>The concept of a comprehensive digital health advisor for patients, which was proposed more than 20 years ago, is now technically feasible and attractive to HNHC patients in the United States. The patients highlight a range of functional, emotional, medical, and personal needs that might be addressed by this tool. They also list a series of key functions such as tracking, advice, providing a holistic picture of themselves, and coordination and communication. The use of human-centered design helps overcome the limitation that new designs in health care are often dreamed up by providers to be easy to implement but not necessarily use by people who rarely use health services and don’t resemble the people they are trying to help. Personas can promote stakeholder engagement by providing detailed information on patient needs and how a tool might address those needs, making it easier to understand key functions, possible interactions with the health system, data requirements, and potential regulatory concerns.</p>
        <p>While some studies have employed human-centered design to develop tools for patients with multiple chronic conditions [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>], this approach tends to be applied to specific populations (eg, people with diabetes) [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>] or specific uses (eg, communication, monitoring) [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. Our work supplements the findings of a recent review of mobile technologies for older adults that summarized the following design features from different articles: graphs; notification systems; text and video messaging; scheduling; and vision, hearing, and memory aids [<xref ref-type="bibr" rid="ref2">2</xref>]. Even though there are many digital health tools on the market, few comprehensively address the needs of HNHC patients and even those tend to focus on medically defined needs rather than act as general advisors. To go from an understanding of needs to a functioning tool that meets those needs in the context of someone’s life is a stretch and it involves testing different use cases, functions, and target groups before finding a good fit. The personas and prototype helped elicit specific advice from providers, payers, regulators, developers, and investors by making the problems and options more tangible. This highlighted the range of challenges with trust, uptake, integration with workflows, value proposition for different stakeholders, and potential business models, going beyond a narrow focus on end user needs and features of the technology.</p>
        <p>The learnings from this project about current HNHC patients could be applied to vulnerable populations at risk of becoming HNHC patients (another target group for the Commonwealth Fund) and even the general public. We found the highest users of the health system are interested in tools that can help them manage their health challenges but even more in helping them live their lives to the fullest. This is likely to be true of all patients, who not only value disease management but also see health as a means to identify and work toward their life goals. An individual’s health is intertwined with their psychological, social, and economic context, and truly useful digital tools will help people manage their needs in a comprehensive and integrated way rather than focus on a disease or issue in isolation. This has not been a major goal for health systems or a major focus of quality improvement efforts; however, it could be supported by consumer-facing tools that engage and empower individuals.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>Characterizing the needs of target users is essential to designing a comprehensive digital health advisor, but to realize this vision we need to address broader system and policy constraints that will impact its development. User-centered design can help draw attention to something that is technically feasible but has no business model and may not be compatible with many current regulations. It helps reframe problems and suggest solutions that may be independent of existing services or processes. In the area of models of care for HNHC patients, the Commonwealth Fund has commissioned rigorous evaluations of new models, synthesized evidence from the scientific literature, and created a playbook for health systems to help implement promising models and improve care for this group. We have also started using design thinking as a tool to generate a pipeline of new options that might constitute a breakthrough. We move this future-oriented work forward through our role as a convener and advocate for improving access to care. For the IT-enabled consumer, the next steps include exploring the type of collaboration needed between stakeholders such as health care delivery organizations, patients, caregivers, technology companies, government, and consumer advocacy groups. We also need to examine the incentives and business models needed to attract entrepreneurs and developers to work in this area and for health systems to engage with consumer-facing IT tools. System change is unlikely to come from those who already run it, so the Commonwealth Fund is working to address the policy and regulatory, business model, and cultural barriers to creating tools that put patients and their goals at the center of the health system.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>Patient and caregiver personas.</p>
        <media xlink:href="jmir_v21i5e10318_app1.pdf" xlink:title="PDF File (Adobe PDF File), 852KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">HCD</term>
          <def>
            <p>human-centered design</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">HNHC</term>
          <def>
            <p>high-need, high-cost</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ICT</term>
          <def>
            <p>information and communication technologies</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">IT</term>
          <def>
            <p>information technology</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors wish to acknowledge the following individuals at gravitytank (now Salesforce) for their contributions to this research: Susie Kang, Treanndis Hurst, Stephanie Szabo, and Dave Saunders. This research was conducted with financial support from the Commonwealth Fund and the Gordon and Betty Moore Foundation. The authors of this article are responsible for its contents. No statement in this article should be construed as an official position of The Commonwealth Fund, the Moore Foundation, or gravitytank (now Salesforce).</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Szolovits</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Doyle</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Long</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <source>Guardian Angel: patient-centered health information systems. Technical report MIT/LCS/TR-604</source>  
        <year>1994</year>  
        <access-date>2019-03-01</access-date>
        <publisher-name>Massachusetts Institute of Technology Laboratory for Computer Science</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://groups.csail.mit.edu/medg/projects/ga/manifesto/GAtr.pdf">http://groups.csail.mit.edu/medg/projects/ga/manifesto/GAtr.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76YU4UkPH"/>
        </comment> </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>Matthew-Maich</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Harris</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Ploeg</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Markle-Reid</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Valaitis</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Ibrahim</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Gafni</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Isaacs</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Designing, implementing, and evaluating mobile health technologies for managing chronic conditions in older adults: a scoping review</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2016</year>  
        <month>06</month>  
        <day>09</day>  
        <volume>4</volume>  
        <issue>2</issue>  
        <fpage>e29</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2016/2/e29/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.5127</pub-id>
        <pub-id pub-id-type="medline">27282195</pub-id>
        <pub-id pub-id-type="pii">v4i2e29</pub-id>
        <pub-id pub-id-type="pmcid">PMC4919548</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
        <source>Designing a high-performing health care system for patients with complex needs: ten recommendations for policymakers—expanded and revised edition</source>  
        <year>2018</year>  
        <access-date>2018-01-08</access-date>
        <publisher-name>The Commonwealth Fund</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.commonwealthfund.org/sites/default/files/documents/___media_files_publications_fund_report_2017_aug_roland_10_recommendations_for_complex_patients_revisedexpanded.pdf">https://www.commonwealthfund.org/sites/default/files/documents/___media_files_publications_fund_report_2017_aug_roland_10_recommendations_for_complex_patients_revisedexpanded.pdf</ext-link>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Aitken</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Lyle</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Patient Adoption of mHealth: Use, Evidence and Remaining Barriers to Mainstream Acceptance</source>  
        <year>2015</year>  
        <publisher-loc>Parsippany</publisher-loc>
        <publisher-name>IMS Institute for Healthcare Informatics</publisher-name></nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Cohen</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Yu</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <source>The concentration and persistence in the level of health expenditures over time: estimates for the US population, 2008-2009</source>  
        <access-date>2019-02-19</access-date>
        <publisher-name>Agency for Healthcare Research and Quality</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://meps.ahrq.gov/data_files/publications/st354/stat354.shtml">https://meps.ahrq.gov/data_files/publications/st354/stat354.shtml</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76JKBVtzc"/>
        </comment> </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>Reid</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Evans</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Barer</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Sheps</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Kerluke</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>McGrail</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Hertzman</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Pagliccia</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>Conspicuous consumption: characterizing high users of physician services in one Canadian province</article-title>
        <source>J Health Serv Res Policy</source>  
        <year>2003</year>  
        <month>10</month>  
        <volume>8</volume>  
        <issue>4</issue>  
        <fpage>215</fpage>  
        <lpage>224</lpage>  
        <pub-id pub-id-type="doi">10.1258/135581903322403281</pub-id>
        <pub-id pub-id-type="medline">14596756</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>Guilcher</surname>
            <given-names>SJT</given-names>
          </name>
          <name name-style="western">
            <surname>Bronskill</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Guan</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Wodchis</surname>
            <given-names>WP</given-names>
          </name>
        </person-group>
        <article-title>Who are the high-cost users? A method for person-centred attribution of health care spending</article-title>
        <source>PLoS One</source>  
        <year>2016</year>  
        <volume>11</volume>  
        <issue>3</issue>  
        <fpage>e0149179</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0149179"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1371/journal.pone.0149179</pub-id>
        <pub-id pub-id-type="medline">26937955</pub-id>
        <pub-id pub-id-type="pii">PONE-D-15-32254</pub-id>
        <pub-id pub-id-type="pmcid">PMC4777563</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>Lemstra</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Mackenbach</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Neudorf</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Nannapaneni</surname>
            <given-names>U</given-names>
          </name>
        </person-group>
        <article-title>High health care utilization and costs associated with lower socio-economic status: results from a linked dataset</article-title>
        <source>Can J Public Health</source>  
        <year>2009</year>  
        <volume>100</volume>  
        <issue>3</issue>  
        <fpage>180</fpage>  
        <lpage>183</lpage>  
        <pub-id pub-id-type="medline">19507718</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>Fitzpatrick</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Rosella</surname>
            <given-names>LC</given-names>
          </name>
          <name name-style="western">
            <surname>Calzavara</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Petch</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Pinto</surname>
            <given-names>AD</given-names>
          </name>
          <name name-style="western">
            <surname>Manson</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Goel</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Wodchis</surname>
            <given-names>WP</given-names>
          </name>
        </person-group>
        <article-title>Looking beyond income and education: socioeconomic status gradients among future high-cost users of health care</article-title>
        <source>Am J Prev Med</source>  
        <year>2015</year>  
        <month>08</month>  
        <volume>49</volume>  
        <issue>2</issue>  
        <fpage>161</fpage>  
        <lpage>171</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://linkinghub.elsevier.com/retrieve/pii/S0749-3797(15)00082-3"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.amepre.2015.02.018</pub-id>
        <pub-id pub-id-type="medline">25960393</pub-id>
        <pub-id pub-id-type="pii">S0749-3797(15)00082-3</pub-id></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Vaillancourt</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Shahin</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Aggarwal</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Pomedli</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Hayden</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Pus</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Bhattacharyya</surname>
            <given-names>O</given-names>
          </name>
        </person-group>
        <article-title>Using archetypes to design services for high users of healthcare</article-title>
        <source>Healthc Pap</source>  
        <year>2014</year>  
        <volume>14</volume>  
        <issue>2</issue>  
        <fpage>37</fpage>  
        <lpage>41</lpage>  
        <pub-id pub-id-type="medline">25880862</pub-id></nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zulman</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Asch</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Martins</surname>
            <given-names>SB</given-names>
          </name>
          <name name-style="western">
            <surname>Kerr</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Hoffman</surname>
            <given-names>BB</given-names>
          </name>
          <name name-style="western">
            <surname>Goldstein</surname>
            <given-names>MK</given-names>
          </name>
        </person-group>
        <article-title>Quality of care for patients with multiple chronic conditions: the role of comorbidity interrelatedness</article-title>
        <source>J Gen Intern Med</source>  
        <year>2014</year>  
        <month>03</month>  
        <volume>29</volume>  
        <issue>3</issue>  
        <fpage>529</fpage>  
        <lpage>537</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24081443"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s11606-013-2616-9</pub-id>
        <pub-id pub-id-type="medline">24081443</pub-id>
        <pub-id pub-id-type="pmcid">PMC3930789</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>Joynt</surname>
            <given-names>KE</given-names>
          </name>
          <name name-style="western">
            <surname>Figueroa</surname>
            <given-names>JF</given-names>
          </name>
          <name name-style="western">
            <surname>Beaulieu</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Wild</surname>
            <given-names>RC</given-names>
          </name>
          <name name-style="western">
            <surname>Orav</surname>
            <given-names>EJ</given-names>
          </name>
          <name name-style="western">
            <surname>Jha</surname>
            <given-names>AK</given-names>
          </name>
        </person-group>
        <article-title>Segmenting high-cost Medicare patients into potentially actionable cohorts</article-title>
        <source>Healthc (Amst)</source>  
        <year>2017</year>  
        <month>03</month>  
        <volume>5</volume>  
        <issue>1-2</issue>  
        <fpage>62</fpage>  
        <lpage>67</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.hjdsi.2016.11.002</pub-id>
        <pub-id pub-id-type="medline">27914968</pub-id>
        <pub-id pub-id-type="pii">S2213-0764(16)30228-7</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>May</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Montori</surname>
            <given-names>VM</given-names>
          </name>
          <name name-style="western">
            <surname>Mair</surname>
            <given-names>FS</given-names>
          </name>
        </person-group>
        <article-title>We need minimally disruptive medicine</article-title>
        <source>BMJ</source>  
        <year>2009</year>  
        <volume>339</volume>  
        <fpage>b2803</fpage>  
        <pub-id pub-id-type="medline">19671932</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>Pefoyo</surname>
            <given-names>AJK</given-names>
          </name>
          <name name-style="western">
            <surname>Bronskill</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Gruneir</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Calzavara</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Thavorn</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Petrosyan</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Maxwell</surname>
            <given-names>CJ</given-names>
          </name>
          <name name-style="western">
            <surname>Bai</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Wodchis</surname>
            <given-names>WP</given-names>
          </name>
        </person-group>
        <article-title>The increasing burden and complexity of multimorbidity</article-title>
        <source>BMC Public Health</source>  
        <year>2015</year>  
        <volume>15</volume>  
        <fpage>415</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://bmcpublichealth.biomedcentral.com/articles/10.1186/s12889-015-1733-2"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12889-015-1733-2</pub-id>
        <pub-id pub-id-type="medline">25903064</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12889-015-1733-2</pub-id>
        <pub-id pub-id-type="pmcid">PMC4415224</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>Levine</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Lipsitz</surname>
            <given-names>SR</given-names>
          </name>
          <name name-style="western">
            <surname>Linder</surname>
            <given-names>JA</given-names>
          </name>
        </person-group>
        <article-title>Trends in seniors' use of digital health technology in the United States, 2011-2014</article-title>
        <source>JAMA</source>  
        <year>2016</year>  
        <month>08</month>  
        <day>2</day>  
        <volume>316</volume>  
        <issue>5</issue>  
        <fpage>538</fpage>  
        <lpage>540</lpage>  
        <pub-id pub-id-type="doi">10.1001/jama.2016.9124</pub-id>
        <pub-id pub-id-type="medline">27483069</pub-id>
        <pub-id pub-id-type="pii">2540389</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>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>LP</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Faxvaag</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rozenblum</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Pabo</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Landman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Klinger</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Bates</surname>
            <given-names>DW</given-names>
          </name>
        </person-group>
        <article-title>Many mobile health apps target high-need, high-cost populations, but gaps remain</article-title>
        <source>Health Aff (Millwood)</source>  
        <year>2016</year>  
        <month>12</month>  
        <day>01</day>  
        <volume>35</volume>  
        <issue>12</issue>  
        <fpage>2310</fpage>  
        <lpage>2318</lpage>  
        <pub-id pub-id-type="doi">10.1377/hlthaff.2016.0578</pub-id>
        <pub-id pub-id-type="medline">27920321</pub-id>
        <pub-id pub-id-type="pii">35/12/2310</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>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>LP</given-names>
          </name>
          <name name-style="western">
            <surname>Filkins</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Silvers</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Bain</surname>
            <given-names>PA</given-names>
          </name>
          <name name-style="western">
            <surname>Zulman</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Rozenblum</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Pabo</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Landman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Klinger</surname>
            <given-names>EV</given-names>
          </name>
          <name name-style="western">
            <surname>Bates</surname>
            <given-names>DW</given-names>
          </name>
        </person-group>
        <article-title>Patient-facing mobile apps to treat high-need, high-cost populations: a scoping review</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2016</year>  
        <month>12</month>  
        <day>19</day>  
        <volume>4</volume>  
        <issue>4</issue>  
        <fpage>e136</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2016/4/e136/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.6445</pub-id>
        <pub-id pub-id-type="medline">27993761</pub-id>
        <pub-id pub-id-type="pii">v4i4e136</pub-id>
        <pub-id pub-id-type="pmcid">PMC5206484</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>Sy</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Adapting usability investigations for agile user-centered design</article-title>
        <source>J Usability Stud</source>  
        <year>2007</year>  
        <volume>2</volume>  
        <issue>3</issue>  
        <fpage>112</fpage>  
        <lpage>132</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://uxpajournal.org/wp-content/uploads/sites/8/pdf/JUS_Sy_May2007.pdf"/>
        </comment> </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>Olson</surname>
            <given-names>GM</given-names>
          </name>
          <name name-style="western">
            <surname>Olson</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>User‐centered design of collaboration technology</article-title>
        <source>J Organ Comput</source>  
        <year>1991</year>  
        <month>01</month>  
        <volume>1</volume>  
        <issue>1</issue>  
        <fpage>61</fpage>  
        <lpage>83</lpage>  
        <pub-id pub-id-type="doi">10.1080/10919399109540150</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>Hassenzahl</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Tractinsky</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>User experience: a research agenda</article-title>
        <source>Behav Inf Technol</source>  
        <year>2006</year>  
        <month>03</month>  
        <volume>25</volume>  
        <issue>2</issue>  
        <fpage>91</fpage>  
        <lpage>97</lpage>  
        <pub-id pub-id-type="doi">10.1080/01449290500330331</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>Corry</surname>
            <given-names>MD</given-names>
          </name>
          <name name-style="western">
            <surname>Frick</surname>
            <given-names>TW</given-names>
          </name>
          <name name-style="western">
            <surname>Hansen</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>User-centered design and usability testing of a web site: an illustrative case study</article-title>
        <source>Educ Technol Res Dev Dec</source>  
        <year>1997</year>  
        <month>12</month>  
        <volume>45</volume>  
        <issue>4</issue>  
        <fpage>65</fpage>  
        <lpage>76</lpage>  
        <pub-id pub-id-type="doi">10.1007/BF02299683</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>Maguire</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Methods to support human-centred design</article-title>
        <source>Int J Hum Comput Stud</source>  
        <year>2001</year>  
        <month>10</month>  
        <volume>55</volume>  
        <issue>4</issue>  
        <fpage>587</fpage>  
        <lpage>634</lpage>  
        <pub-id pub-id-type="doi">10.1006/ijhc.2001.0503</pub-id></nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Robert</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Cornwell</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Locock</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Purushotham</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sturmey</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Gager</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Patients and staff as codesigners of healthcare services</article-title>
        <source>BMJ</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>350</volume>  
        <fpage>g7714</fpage>  
        <pub-id pub-id-type="medline">25670179</pub-id></nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zuckerman</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Margolis</surname>
            <given-names>PA</given-names>
          </name>
          <name name-style="western">
            <surname>Mate</surname>
            <given-names>KS</given-names>
          </name>
        </person-group>
        <article-title>Health services innovation: the time is now</article-title>
        <source>JAMA</source>  
        <year>2013</year>  
        <month>03</month>  
        <day>20</day>  
        <volume>309</volume>  
        <issue>11</issue>  
        <fpage>1113</fpage>  
        <lpage>1114</lpage>  
        <pub-id pub-id-type="doi">10.1001/jama.2013.2007</pub-id>
        <pub-id pub-id-type="medline">23512055</pub-id>
        <pub-id pub-id-type="pii">1669828</pub-id></nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Eckman</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Gorski</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Mehta</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Leveraging design thinking to build sustainable mobile health systems</article-title>
        <source>J Med Eng Technol</source>  
        <year>2016</year>  
        <volume>40</volume>  
        <issue>7-8</issue>  
        <fpage>422</fpage>  
        <lpage>430</lpage>  
        <pub-id pub-id-type="doi">10.1080/03091902.2016.1218560</pub-id>
        <pub-id pub-id-type="medline">27535325</pub-id></nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>LeRouge</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Ma</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Sneha</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Tolle</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>User profiles and personas in the design and development of consumer health technologies</article-title>
        <source>Int J Med Inform</source>  
        <year>2013</year>  
        <month>11</month>  
        <volume>82</volume>  
        <issue>11</issue>  
        <fpage>e251</fpage>  
        <lpage>e268</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2011.03.006</pub-id>
        <pub-id pub-id-type="medline">21481635</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(11)00072-4</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Turner</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Reeder</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Ramey</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Scenarios, personas and user stories: user-centered evidence-based design representations of communicable disease investigations</article-title>
        <source>J Biomed Inform</source>  
        <year>2013</year>  
        <month>08</month>  
        <volume>46</volume>  
        <issue>4</issue>  
        <fpage>575</fpage>  
        <lpage>584</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://linkinghub.elsevier.com/retrieve/pii/S1532-0464(13)00049-X"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2013.04.006</pub-id>
        <pub-id pub-id-type="medline">23618996</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(13)00049-X</pub-id>
        <pub-id pub-id-type="pmcid">PMC4077047</pub-id></nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Design thinking</article-title>
        <source>Harv Bus Rev</source>  
        <year>2008</year>  
        <month>06</month>  
        <volume>6</volume>  
        <fpage>1</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://hbr.org/2008/06/design-thinking"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Abras</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Maloney-Krichmar</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Preece</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Bainbridge</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <article-title>User-centered design</article-title>
        <source>Encyclopedia of Human-Computer Interaction</source>  
        <year>2004</year>  
        <publisher-loc>Thousand Oaks</publisher-loc>
        <publisher-name>Sage Publications</publisher-name></nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Norman</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Draper</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>User centered system design</article-title>
        <source>New Perspectives on Human-Computer Interaction</source>  
        <year>1986</year>  
        <publisher-loc>Hillsdale</publisher-loc>
        <publisher-name>L. Erlbaum Associates Inc</publisher-name></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>van der Molen</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Maas</surname>
            <given-names>AH</given-names>
          </name>
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>van Pul</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Cottaar</surname>
            <given-names>EJ</given-names>
          </name>
          <name name-style="western">
            <surname>van Riel</surname>
            <given-names>NA</given-names>
          </name>
          <name name-style="western">
            <surname>Hilbers</surname>
            <given-names>PA</given-names>
          </name>
          <name name-style="western">
            <surname>Haak</surname>
            <given-names>HR</given-names>
          </name>
        </person-group>
        <article-title>Identifying user preferences for a digital educational solution for young seniors with diabetes</article-title>
        <source>Diabetes Spectr</source>  
        <year>2017</year>  
        <month>02</month>  
        <day>09</day>  
        <volume>30</volume>  
        <issue>3</issue>  
        <fpage>182</fpage>  
        <lpage>187</lpage>  
        <pub-id pub-id-type="doi">10.2337/ds16-0023</pub-id></nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Holden</surname>
            <given-names>RJ</given-names>
          </name>
          <name name-style="western">
            <surname>Kulanthaivel</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Purkayastha</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Goggins</surname>
            <given-names>KM</given-names>
          </name>
          <name name-style="western">
            <surname>Kripalani</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Know thy eHealth user: development of biopsychosocial personas from a study of older adults with heart failure</article-title>
        <source>Int J Med Inform</source>  
        <year>2017</year>  
        <month>12</month>  
        <volume>108</volume>  
        <fpage>158</fpage>  
        <lpage>167</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.10.006</pub-id>
        <pub-id pub-id-type="medline">29132622</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(17)30364-7</pub-id>
        <pub-id pub-id-type="pmcid">PMC5793874</pub-id></nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Serio</surname>
            <given-names>CD</given-names>
          </name>
          <name name-style="western">
            <surname>Hessing</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Reed</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Hess</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Reis</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>The effect of online chronic disease personas on activation: within-subjects and between-groups analyses</article-title>
        <source>JMIR Res Protoc</source>  
        <year>2015</year>  
        <month>02</month>  
        <day>25</day>  
        <volume>4</volume>  
        <issue>1</issue>  
        <fpage>e20</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.researchprotocols.org/2015/1/e20/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/resprot.3392</pub-id>
        <pub-id pub-id-type="medline">25720676</pub-id>
        <pub-id pub-id-type="pii">v4i1e20</pub-id>
        <pub-id pub-id-type="pmcid">PMC4376159</pub-id></nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Giunti</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Kool</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Rivera</surname>
            <given-names>RO</given-names>
          </name>
          <name name-style="western">
            <surname>Dorronzoro</surname>
            <given-names>ZE</given-names>
          </name>
        </person-group>
        <article-title>Exploring the specific needs of persons with multiple sclerosis for mhealth solutions for physical activity: mixed-methods study</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2018</year>  
        <month>02</month>  
        <day>09</day>  
        <volume>6</volume>  
        <issue>2</issue>  
        <fpage>e37</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/2/e37/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.8996</pub-id>
        <pub-id pub-id-type="medline">29426814</pub-id>
        <pub-id pub-id-type="pii">v6i2e37</pub-id>
        <pub-id pub-id-type="pmcid">PMC5889817</pub-id></nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Jacob</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Wong</surname>
            <given-names>ML</given-names>
          </name>
          <name name-style="western">
            <surname>Hayhurst</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Watson</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Morrison</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Designing services for frequent attenders to the emergency department: a characterisation of this population to inform service design</article-title>
        <source>Clin Med (Lond)</source>  
        <year>2016</year>  
        <month>08</month>  
        <volume>16</volume>  
        <issue>4</issue>  
        <fpage>325</fpage>  
        <lpage>329</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27481374"/>
        </comment>  
        <pub-id pub-id-type="doi">10.7861/clinmedicine.16-4-325</pub-id>
        <pub-id pub-id-type="medline">27481374</pub-id>
        <pub-id pub-id-type="pii">16/4/325</pub-id>
        <pub-id pub-id-type="pmcid">PMC6280207</pub-id></nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Shah</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Gustafsson</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Bhattacharyya</surname>
            <given-names>O</given-names>
          </name>
        </person-group>
        <source>How a digital health advisor could help high-need, high-cost patients and their caregivers</source>  
        <year>2016</year>  
        <access-date>2019-02-19</access-date>
        <publisher-loc>New York</publisher-loc>
        <publisher-name>The Commonwealth Fund</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.commonwealthfund.org/publications/blog/2016/dec/digital-health-advisor">http://www.commonwealthfund.org/publications/blog/2016/dec/digital-health-advisor</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76JKkeNUp"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bhattacharyya</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Shah</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Gusafsson</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>A digital health advisor for high-need, high-cost patients; exploring needs, functions and system constraints</article-title>
        <year>2017</year>  
        <conf-name>AMIA Annual Symposium</conf-name>
        <conf-date>2017</conf-date>
        <conf-loc>Washington</conf-loc></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
        <source>Experience Sage</source>  
        <access-date>2019-02-19</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://sage-dha.squarespace.com/index/">http://sage-dha.squarespace.com/index/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="76JL85uzR"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Steele</surname>
            <given-names>GC</given-names>
          </name>
          <name name-style="western">
            <surname>Khan</surname>
            <given-names>AI</given-names>
          </name>
          <name name-style="western">
            <surname>Kuluski</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>McKillop</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Sharpe</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Bierman</surname>
            <given-names>AS</given-names>
          </name>
          <name name-style="western">
            <surname>Lyons</surname>
            <given-names>RF</given-names>
          </name>
          <name name-style="western">
            <surname>Cott</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Improving patient experience and primary care quality for patients with complex chronic disease using the electronic patient-reported outcomes tool: adopting qualitative methods into a user-centered design approach</article-title>
        <source>JMIR Res Protoc</source>  
        <year>2016</year>  
        <volume>5</volume>  
        <issue>1</issue>  
        <fpage>e28</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.researchprotocols.org/2016/1/e28/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/resprot.5204</pub-id>
        <pub-id pub-id-type="medline">26892952</pub-id>
        <pub-id pub-id-type="pii">v5i1e28</pub-id></nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Lyles</surname>
            <given-names>CR</given-names>
          </name>
          <name name-style="western">
            <surname>Altschuler</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Chawla</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Kowalski</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>McQuillan</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Bayliss</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Heisler</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Grant</surname>
            <given-names>RW</given-names>
          </name>
        </person-group>
        <article-title>User-centered design of a tablet waiting room tool for complex patients to prioritize discussion topics for primary care visits</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2016</year>  
        <month>09</month>  
        <day>14</day>  
        <volume>4</volume>  
        <issue>3</issue>  
        <fpage>e108</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2016/3/e108/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.6187</pub-id>
        <pub-id pub-id-type="medline">27627965</pub-id>
        <pub-id pub-id-type="pii">v4i3e108</pub-id>
        <pub-id pub-id-type="pmcid">PMC5040865</pub-id></nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ahern</surname>
            <given-names>DK</given-names>
          </name>
          <name name-style="western">
            <surname>Parker</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Eaton</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Rafferty</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Wroblewski</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Goldman</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Patient-facing technology for identification of COPD in primary care</article-title>
        <source>J Innov Health Inform</source>  
        <year>2016</year>  
        <month>07</month>  
        <day>15</day>  
        <volume>23</volume>  
        <issue>2</issue>  
        <fpage>824</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.14236/jhi.v23i2.824"/>
        </comment>  
        <pub-id pub-id-type="medline">27869583</pub-id></nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>De Vito Dabbs</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Myers</surname>
            <given-names>BA</given-names>
          </name>
          <name name-style="western">
            <surname>McCurry</surname>
            <given-names>KR</given-names>
          </name>
          <name name-style="western">
            <surname>Dunbar-Jacob</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Hawkins</surname>
            <given-names>RP</given-names>
          </name>
          <name name-style="western">
            <surname>Begey</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Dew</surname>
            <given-names>MA</given-names>
          </name>
        </person-group>
        <article-title>User-centered design and interactive health technologies for patients</article-title>
        <source>Comput Inform Nurs</source>  
        <year>2009</year>  
        <volume>27</volume>  
        <issue>3</issue>  
        <fpage>175</fpage>  
        <lpage>183</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/19411947"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1097/NCN.0b013e31819f7c7c</pub-id>
        <pub-id pub-id-type="medline">19411947</pub-id>
        <pub-id pub-id-type="pii">00024665-200905000-00011</pub-id>
        <pub-id pub-id-type="pmcid">PMC2818536</pub-id></nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>van der Weegen</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Verwey</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Spreeuwenberg</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Tange</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>The development of a mobile monitoring and feedback tool to stimulate physical activity of people with a chronic disease in primary care: a user-centered design</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2013</year>  
        <volume>1</volume>  
        <issue>2</issue>  
        <fpage>e8</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2013/2/e8/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.2526</pub-id>
        <pub-id pub-id-type="medline">25099556</pub-id>
        <pub-id pub-id-type="pii">v1i2e8</pub-id>
        <pub-id pub-id-type="pmcid">PMC4114510</pub-id></nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ferreira</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Almeida</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Rosa</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Oliveira</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Casimiro</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Silva</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Teixeira</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Elderly centered design for interaction: the case of the S4S medication assistant</article-title>
        <source>Procedia Comput Sci</source>  
        <year>2014</year>  
        <volume>27</volume>  
        <fpage>398</fpage>  
        <lpage>408</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.procs.2014.02.044</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
