<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v4i8e18123</article-id>
      <article-id pub-id-type="pmid">32763884</article-id>
      <article-id pub-id-type="doi">10.2196/18123</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>Clinician Perspectives and Design Implications in Using Patient-Generated Health Data to Improve Mental Health Practices: Mixed Methods Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chih</surname>
            <given-names>Ming Yuan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Blondon</surname>
            <given-names>Katherine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Wu</surname>
            <given-names>Danny T Y</given-names>
          </name>
          <degrees>PhD, MSI</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Biomedical Informatics</institution>
            <institution>College of Medicine</institution>
            <institution>University of Cincinnati</institution>
            <addr-line>231 Albert Sabin Way, ML0840</addr-line>
            <addr-line>Cincinnati, OH, 45229</addr-line>
            <country>United States</country>
            <phone>1 5135586464</phone>
            <email>wutz@ucmail.uc.edu</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7658-3754</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Xin</surname>
            <given-names>Chen</given-names>
          </name>
          <degrees>MDes</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2889-5160</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Bindhu</surname>
            <given-names>Shwetha</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6808-2653</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Xu</surname>
            <given-names>Catherine</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8342-177X</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Sachdeva</surname>
            <given-names>Jyoti</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9588-2541</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>Jennifer L</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6683-0053</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Jung</surname>
            <given-names>Heekyoung</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7745-2086</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Biomedical Informatics</institution>
        <institution>College of Medicine</institution>
        <institution>University of Cincinnati</institution>
        <addr-line>Cincinnati, OH</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Pediatrics</institution>
        <institution>College of Medicine</institution>
        <institution>University of Cincinnati</institution>
        <addr-line>Cincinnati, OH</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>School of Design</institution>
        <institution>College of Design, Architecture, Art, and Planning</institution>
        <institution>University of Cincinnati</institution>
        <addr-line>Cincinnati, OH</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Medical Sciences Baccalaureate Program</institution>
        <institution>College of Medicine</institution>
        <institution>University of Cincinnati</institution>
        <addr-line>Cincinnati, OH</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Psychiatry and Behavioral Neuroscience</institution>
        <institution>College of Medicine</institution>
        <institution>University of Cincinnati</institution>
        <addr-line>Cincinnati, OH</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Danny T Y Wu <email>wutz@ucmail.uc.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>8</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>7</day>
        <month>8</month>
        <year>2020</year>
      </pub-date>
      <volume>4</volume>
      <issue>8</issue>
      <elocation-id>e18123</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>2</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>30</day>
          <month>3</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>5</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>15</day>
          <month>6</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Danny T Y Wu, Chen Xin, Shwetha Bindhu, Catherine Xu, Jyoti Sachdeva, Jennifer L Brown, Heekyoung Jung. Originally published in JMIR Formative Research (http://formative.jmir.org), 07.08.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on http://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2020/8/e18123" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Patient-generated health data (PGHD) have been largely collected through mobile health (mHealth) apps and wearable devices. PGHD can be especially helpful in mental health, as patients’ illness history and symptom narratives are vital to developing diagnoses and treatment plans. However, the extent to which clinicians use mental health–related PGHD is unknown.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>A mixed methods study was conducted to understand clinicians’ perspectives on PGHD and current mental health apps. This approach uses information gathered from semistructured interviews, workflow analysis, and user-written mental health app reviews to answer the following research questions: (1) What is the current workflow of mental health practice and how are PGHD integrated into this workflow, (2) what are clinicians’ perspectives on PGHD and how do they choose mobile apps for their patients, (3) and what are the features of current mobile apps in terms of interpreting and sharing PGHD?</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The study consists of semistructured interviews with 12 psychiatrists and clinical psychologists from a large academic hospital. These interviews were thematically and qualitatively analyzed for common themes and workflow elements. User-posted reviews of 56 sleep and mood tracking apps were analyzed to understand app features in comparison with the information gathered from interviews.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The results showed that PGHD have been part of the workflow, but its integration and use are not optimized. Mental health clinicians supported the use of PGHD but had concerns regarding data reliability and accuracy. They also identified challenges in selecting suitable apps for their patients. From the app review, it was discovered that mHealth apps had limited features to support personalization and collaborative care as well as data interpretation and sharing.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study investigates clinicians’ perspectives on PGHD use and explored existing app features using the app review data in the mental health setting. A total of 3 design guidelines were generated: (1) improve data interpretation and sharing mechanisms, (2) consider clinical workflow and electronic health record integration, and (3) support personalized and collaborative care. More research is needed to demonstrate the best practices of PGHD use and to evaluate their effectiveness in improving patient outcomes.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>patient-generated health data</kwd>
        <kwd>mental health</kwd>
        <kwd>workflow</kwd>
        <kwd>mobile application</kwd>
        <kwd>interview</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background and Significance</title>
        <p>With advances in mobile technology and the pervasive use of wearable devices, a large amount of digital health data have been generated by patients. Patient-generated health data (PGHD) refer to “health-related data created and recorded by or from patients outside of the clinical setting to help address a health concern,” as defined by the Office of the National Coordinator for Health Information Technology (ONC) [<xref ref-type="bibr" rid="ref1">1</xref>]. According to the ONC, the adoption of PGHD can have several benefits, including, but not limited to, enhancing patient experience, alerting care teams for early intervention, and improving patient health outcomes [<xref ref-type="bibr" rid="ref1">1</xref>]. Several projects have piloted these ideas and implemented informatics solutions to collect, use, and share PGHD [<xref ref-type="bibr" rid="ref2">2</xref>], such as in postsurgical surveillance [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. Patients seem to have positive attitudes toward PGHD and are willing to share their data with the care team to support long-term health management. Studies have shown the feasibility of using PGHD to support personalized and effective care management [<xref ref-type="bibr" rid="ref5">5</xref>]. Using PGHD can improve data work for both clinicians and patients. A case study at a cancer rehabilitation clinic showed that the data collection became more distributed, the nurses asked more focused questions during the consultations, and the patients gradually developed competence in managing their own health [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
        <p>Despite the potential benefits of PGHD, it currently remains limited with a focus on health history, verified surveys, and biometric activities [<xref ref-type="bibr" rid="ref7">7</xref>]. Ultimately, PGHD should be seamlessly integrated with electronic health records (EHRs) to support the clinical decision-making process [<xref ref-type="bibr" rid="ref8">8</xref>]. However, several challenges need to be addressed to maximize the benefits of PGHD, as many pertain to its use at the point of care. First, integrating PGHD into a clinical setting necessarily involves considering clinical workflow redesign, data management concerns, patient privacy protections, and ease of PGHD use [<xref ref-type="bibr" rid="ref9">9</xref>]. This is especially important because clinicians spend a significant amount of time (25%-50%) on documentation tasks in their daily work [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. Second, clinicians may have concerns about the impact of PGHD on reimbursement and data reliability, as PGHD are generated by patients in their daily lives and require extra effort to be consumed in clinics [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Third, PGHD use impacts the relationship between both patients and clinicians. Therefore, a collaborative model may be developed to fulfill the desire of both parties: patients’ desire to know more about their health and clinicians’ desire to have better practices [<xref ref-type="bibr" rid="ref15">15</xref>]. With the growing interest in patient-centered health care, there have been studies that investigate patients’ motivation and attitudes toward tracking and sharing personal data [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. However, the extent and methodology behind the use of PGHD and its integration into clinicians’ workflow remain unknown and, therefore, require further investigation into the demonstration of best practices.</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>To provide empirical evidence to address these challenges, this study investigated the current use of PGHD within mental health practices, with a focus on workflow, clinicians’ perspectives, and data interpretation and sharing. The main reason for choosing a mental health practice setting was that clinicians often rely on patient narratives, observations, and patient-reported outcomes (PROs) to assess the efficacy of psychiatric treatment [<xref ref-type="bibr" rid="ref18">18</xref>]. PROs refer to “a measurement of any aspect of a patient's health status that comes directly from the patient” [<xref ref-type="bibr" rid="ref19">19</xref>]. As the purpose of both PROs and PGHD is to collect data from the patients’ perspective, clinicians from a mental health practice are more likely to adopt and use PGHD. A total of 3 research questions arise from this: (1) What is the current workflow of mental health practice and how are PGHD integrated into this workflow, (2) what are the clinicians’ perspectives on PGHD and how do they choose a mobile-based app (mobile app) for their patients, and (3) what are the features of current mobile apps in terms of interpreting and sharing PGHD?</p>
      </sec>
      <sec>
        <title>Literature Review</title>
        <sec>
          <title>PGHD</title>
          <p>Traditionally, clinicians focus on collecting one-time snapshots of patient information in a clinical setting and making decisions based upon them, thereby losing an opportunity to create a thorough understanding of the patient’s health status [<xref ref-type="bibr" rid="ref20">20</xref>]. In these situations, PGHD are a useful tool for continuous monitoring, especially for patients with chronic conditions that require daily management and benefit from effective tracking [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>]. PGHD can also improve disease surveillance by more accurately assigning patients to disease categories rather than solely using national and regional data [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          <p>PGHD can come from multiple data sources, such as family history, medication, and physiological data sensing [<xref ref-type="bibr" rid="ref25">25</xref>]. PGHD, along with other health data, can ultimately form a repository of patient-centered personal health records, which can then be used to store and manage PGHD [<xref ref-type="bibr" rid="ref26">26</xref>]. Clinicians see the potential of PGHD but raise some concerns about its use, such as difficulties in summarizing PGHD patterns across different clinical specialties and concerns regarding data management, patient privacy, and ethical challenges of PGHD generation [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        </sec>
        <sec>
          <title>Opportunities and Challenges of Mobile Technology</title>
          <p>Internet use has been growing steadily since 1990, with approximately 4 billion internet users worldwide, with 15- to 24-year-olds leading the frontier of internet adoption [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. The internet has also become increasingly mobile. An unsurprising result of this trend has been increasingly sophisticated mobile technology and wearable devices, including the development of numerous mobile health (mHealth) apps, all of which have helped generate large amounts of PGHD.</p>
          <p>Wearable devices and mHealth apps can facilitate health behavior improvements if designed with proper engagement strategies and data collection methods [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. Effective mHealth app design has helped users monitor and promote positive health habits, such as physical activity and eating behaviors [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Furthermore, PGHD can help improve clinical trials’ efficiency and output [<xref ref-type="bibr" rid="ref35">35</xref>]. However, these opportunities come with a number of challenges [<xref ref-type="bibr" rid="ref2">2</xref>]. First, the management and interoperability of massive PGHD require standard vocabularies and data models. Consumer health vocabulary (CHV) is one such effort that has been developed since 2007 [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>] and enhanced by several text mining–based projects [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref41">41</xref>]. In addition, frameworks and data models have been proposed to incorporate PGHD into EHRs [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. However, very few projects use both CHV and common data models to facilitate PGHD comprehension. Indeed, to our knowledge, only one position paper proposes an interpretability-aware framework to systematically understand PGHD [<xref ref-type="bibr" rid="ref44">44</xref>]. The second challenge is the lack of guidelines and best practices for integrating PGHD into the clinical workflow [<xref ref-type="bibr" rid="ref15">15</xref>]. In addition, most PGHD are collected through mHealth apps, which should be carefully evaluated in a standardized manner for efficacy and health outcome improvement [<xref ref-type="bibr" rid="ref45">45</xref>]. Finally, there are concerns about the quality and ownership of PGHD gathered by mHealth apps and wearable devices [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. App developers should develop more transparent data ownership policies so that users can make informed decisions regarding their PGHD [<xref ref-type="bibr" rid="ref47">47</xref>]. Guidelines should also be developed to ensure that high-quality data are gathered by users in their daily routines [<xref ref-type="bibr" rid="ref48">48</xref>].</p>
        </sec>
        <sec>
          <title>PGHD Use in Psychiatry</title>
          <p>Psychiatry is a medical specialty focused on “the diagnosis, treatment, and prevention of mental, emotional, and behavioral disorders” [<xref ref-type="bibr" rid="ref49">49</xref>]. Clinicians use a variety of data from patients to determine psychiatric diagnoses. However, these data are often collected solely in clinical settings. Since the 1960s, mental health clinicians have begun to pay more attention to patients’ personal perspectives, including health-related quality of life (HRQoL) outcomes. HRQoL is a type of PRO that includes “symptoms of disease or health condition, treatment side effects, and functional status across physical, social, and mental health life domains” [<xref ref-type="bibr" rid="ref50">50</xref>]. PROs are derived from patients completing standardized questionnaires and cannot guarantee large-scale, continuous data collection [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. However, with the help of mobile technology and wearable devices, PGHD can collect large amounts of patient health data unobtrusively and continuously. Furthermore, because psychiatry has historically depended on PROs and HRQoLs, clinicians in this field should be able to use PGHD without many conceptual barriers.</p>
          <p>For instance, ecological momentary assessment (EMA) was proposed to assist clinical psychologists in monitoring HRQoL changes by tracking patient behaviors in real time and in their natural environment. EMA uses various data collection tools, such as written diaries and telephones, and PGHD gathered by mHealth apps and wearables can further support this approach [<xref ref-type="bibr" rid="ref53">53</xref>]. PGHD can facilitate large-scale environmental psychiatric research in naturalistic settings and create <italic>digital footprints</italic> to measure patients’ health status (eg, mood and sleep) in an unobtrusive and longitudinal fashion [<xref ref-type="bibr" rid="ref54">54</xref>].</p>
          <p>Although studies have shown that wearable devices and mHealth apps help in the treatment of mental health by increasing awareness and giving reinforcement, such as in the study by Ng et al [<xref ref-type="bibr" rid="ref55">55</xref>], research regarding the implementation of mobile technology into the care process is lacking. Studies have only just started to design and develop apps that focus on interface usability and workflow integration. Notably, Bauer et al [<xref ref-type="bibr" rid="ref56">56</xref>] applied Principles for Digital Development to develop a highly usable mHealth app to support collaborative care for patients and generated 4 more principles based on user feedback. Recently, mental health studies have focused on PGHD, showing a transition to participatory and personalized medicine [<xref ref-type="bibr" rid="ref57">57</xref>]. However, other stakeholders, such as consultants, policy makers, and vendors, should also be considered when integrating PGHD into mental health [<xref ref-type="bibr" rid="ref58">58</xref>].</p>
          <p>Clearly, more PGHD will be generated in the coming future through mobile technology and hold the potential to improve mental health practice, which has long relied on patient-reported data. Therefore, we follow this trend and aim to provide empirical evidence regarding the current use of PGHD in mental health practices, clinicians’ attitudes toward PGHD, and the mHealth app features and selection criteria considered by mental health practitioners.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Clinical Setting</title>
        <p>This study was conducted at the Department of Psychiatry and Behavioral Neuroscience in a large academic hospital in the Midwest United States. The department is a nationally recognized leader in advancing the diagnosis and treatment of mental and behavioral disorders. The department has more than 90 faculty members, with half of them trained as psychiatrists with a medical degree (Doctor of Medicine or Doctor of Osteopathic Medicine). Our study targets were faculty members who are actively seeing patients. As there was a significant portion of faculty trained as psychologists (Doctor of Philosophy or Doctor of Psychology), our study participants included clinicians from both groups.</p>
      </sec>
      <sec>
        <title>Study Design</title>
        <p>This study contains a set of semistructured interviews and an mHealth app review. The interviews collected qualitative data from both psychiatrists and clinical psychologists to understand their clinical workflow, attitudes toward PGHD, and the use and sharing of PGHD in clinics. In the app review, a set of mHealth apps was selected and reviewed systematically. The main objective of this review was to understand patients’ experiences of using mental health–related apps and their opinions around it. The review comments were also downloaded from the Google Play Store and the Apple Store using existing application programming interfaces (APIs) [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]. The app review data were summarized in terms of data interpretation and shared features. Data interpretation here is defined as the manner in which PGHD are collected and presented, either qualitatively or quantitatively assessed, and may be subsequently visualized. Qualitative assessment referred to users’ self-reported data on their sleep quality or mood status. Quantitative assessment, on the other hand, relied on the automatically recorded data by an app and its sensors. The clinicians’ perspectives and the app features were then synthesized to generate design recommendations for mHealth app designers and developers. This study was reviewed and approved by the institutional review board of the study site (IRB# 2018-6453).</p>
      </sec>
      <sec>
        <title>Participant Recruitment</title>
        <p>A total of 12 clinicians, including 7 psychiatrists and 5 clinical psychologists, were recruited using convenience sampling and snowball sampling. Two coauthors facilitated the interview invitation to their colleagues; each participant was asked to provide a few names to reach out at the end of the interview. <xref ref-type="table" rid="table1">Table 1</xref> shows the participant subgroups and their average professional experience (number of years). Male psychiatrists were the largest group among the participants (n=5), followed by slightly more female clinical psychologists.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Participant subgroups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="340"/>
            <col width="160"/>
            <col width="260"/>
            <col width="240"/>
            <thead>
              <tr valign="top">
                <td>Characteristics of interviewees</td>
                <td>Male</td>
                <td>Female</td>
                <td>Years of experience, mean (SD)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Psychiatrist, n (%)</td>
                <td>5 (41)</td>
                <td>2 (17)</td>
                <td>13.9 (6.7)</td>
              </tr>
              <tr valign="top">
                <td>Clinical psychologist, n (%)</td>
                <td>2 (17)</td>
                <td>3 (25)</td>
                <td>12.0 (10.3)</td>
              </tr>
              <tr valign="top">
                <td>Years of experience, mean (SD)</td>
                <td>14.5 (9.3)</td>
                <td>11.1 (6.2)</td>
                <td>13.1 (8.0)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Qualitative Interviews and Analysis</title>
        <p>Each semistructured interview was conducted by 2 members in the research team and lasted for 30 to 45 min. The interview questions were organized in 5 areas: (1) job title and responsibility, (2) clinical workflow, (3) PGHD attitudes, (4) the selection and use of mHealth apps, and (5) the use and sharing of PGHD. Although participants’ attitudes toward PGHD were specifically asked, their attitudes toward EHR integration was not prompted. The interviews were audio recorded and transcribed verbatim in 2 steps. First, the audio recordings were transcribed by the Google Cloud Speech-to-Text API. Second, the transcription drafts were reviewed by the research team to ensure high quality and deidentification of the data. The participants were coded from P01 to P12, with the first 7 participants being psychiatrists.</p>
        <p>Interview data were analyzed in multiple rounds. Specifically, the transcriptions were coded using the Work Elements Model with a focus on actors, actions, and artifacts [<xref ref-type="bibr" rid="ref61">61</xref>]. In the first round, a set of swim lane workflow diagrams was generated. In this swim lane chart, the columns (lanes) represent the actors, and the rectangles represent the actions. A workflow diagram was drawn for each psychiatrist. All psychiatric workflow charts were then consolidated into one workflow chart. The same process was repeated for the psychologists. It is worth noting that 3 participants (P09, P10, and P12) had a portion of the workflow that significantly deviated from others because of their job responsibilities. This reflects the variety of mental health practices. The deviation was due to our sampling methods and the relatively small sample size. These portions of workflow were excluded from the consolidated workflow because of their uniqueness.</p>
        <p>Following the steps in thematic analysis [<xref ref-type="bibr" rid="ref62">62</xref>], the transcriptions were analyzed to understand clinicians’ attitudes toward PGHD and the interpretation and sharing of PGHD in clinics. To ensure the coding quality, one researcher independently coded all the transcriptions and extracted themes, which were then reviewed by another researcher. The 2 researchers met and resolved any disagreements.</p>
      </sec>
      <sec>
        <title>Sleep and Mood App Tracking Review</title>
        <p>A total of 31 sleep tracking apps and 25 mood tracking apps in current mobile app markets (App Store and Google Play) were selected and reviewed. Instead of developing our own search keywords, the results of 2 published systematic review papers were used [<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref64">64</xref>], providing a list of 73 and 32 tracking apps for sleep and mood, respectively. The papers were published in 2018 and 2019. The details of the sleep and mood app selection are described in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <p>The 2 types of mHealth apps were selected because of their significant role in tracking and understanding patients’ status and treatment effects. This was indicated through the prevalent use of these 2 types of apps by the participating psychiatrists and clinical psychologists, as shown in our interviews with them. In total, 9 of 12 participants mentioned these apps. Specifically, 3 of them reported using both sleep tracking and mood tracking mobile apps, 3 of them reported using only mood tracking apps, and 3 of them reported using only sleep tracking apps. Biometric or fitness tracking apps were also mentioned but less frequently; therefore, they were not our investigation focus.</p>
        <p>The information of the selected apps was extracted and organized using a spreadsheet in the following 10 columns: (1) app type (either sleep or mood), (2) app ID, (3) source (Apple or Google), (4) app name, (5) rating, (6) advantages from review, (7) hindrance from review, (8) data interpretation features, (9) data sharing features, and (10) review quotes. The app review data were extracted independently by 2 researchers, one of whom reviewed sleep apps and the other who reviewed mood apps. The extracted data were then reviewed by another researcher for quality checks. Information was collected solely from users' comments. Advantages and hindrances were defined as qualities that users predominantly classified as benefiting the user experience or detracting from it, respectively. The details regarding app sharing capabilities (such as social media and exports to other file types) and methods of data display and interpretation were also included. Selected quotes were compiled from users who offered a holistic perspective on the app. It is worth noting that app review data mostly reflected end user experience and highlighted general user satisfaction or complaints with the apps, complementing our interviews with the clinicians.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Qualitative Analysis: Clinical Workflow</title>
        <sec>
          <title>Consolidated Workflow and PGHD Use</title>
          <p><xref rid="figure1" ref-type="fig">Figure 1</xref> shows a simplified version of the consolidated workflow diagram, which includes step-by-step movement from a patient taking an initial assessment, development of diagnosis and treatment plan, meeting with a physician, the influence of PGHD, and subsequent adjustments in the diagnosis and treatment plan. The detailed workflow diagram is included in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Simplified consolidate workflow diagram of psychiatrists and psychologists based on semistructured interviews. EMR: electronic medical record; PGHD: patient-generated health data.</p>
            </caption>
            <graphic xlink:href="formative_v4i8e18123_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>As shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>, a typical clinician workflow in mental health started from gathering patient information and PROs using an intake assessment. Mental health clinicians then reviewed the form along with EHR information, if any, and conducted a clinical interview to establish psychiatric diagnoses and a corresponding treatment plan. Next, patients participated in the treatment (eg, practice assignments and collection of PGHD), following their clinicians’ requirements. The ways to collect PGHD varied depending on the clinicians’ preferences and patient situations. Next, in subsequent clinical encounters, clinicians reviewed the PGHD and assessed the changes in their patients’ symptoms and functioning since the previous session. Clinicians may revise the treatment plan based on the updated patient health status.</p>
          <p>Many participants do not consider themselves as the sole decision maker in developing the treatment plan. Instead, they worked with patients to align their goals with the treatment. Homework is a common term used by clinicians to discuss patients’ efforts to improve their mental health status between clinic visits. PROs and PGHD can assist patients in their homework, demonstrate their achievement, and provide information to clinicians to make evidence-based decisions on the treatment plan and assess treatment progress. However, participants reported no standardized way to collect and manage PGHD.</p>
          <p>Although collecting PROs and PGHD has been part of mental health practices, its use is not optimized. Taking the intake forms as an example, one participant talked about troubles using survey scales when patients wait in the waiting room. This suboptimal data collection may slow down the clinics and reduce the efficiency and quality of care:</p>
          <disp-quote>
            <p>As I mentioned the scales aren't always filled out and they may not have enough time to fill out the scales if they're call[ed] back right away.</p>
            <attrib>P06</attrib>
          </disp-quote>
          <p>Sometimes, PROs can be ambiguous and confusing and require more data to understand patients’ health status change and nuanced differences. In this case, PGHD can be complementary and provide more detailed behavioral data to inform the shared clinical decisions on the treatment plans. One participant explained how PROs may be confusing:</p>
          <disp-quote>
            <p>So, for example, like number three on the PHQ9, in one item, it's assessing “trouble falling asleep,” “staying asleep” or “sleeping too much,” which could mean very different things in terms of planning to do for treatment. And so, I will always ask a follow-up and then I will manually circle the ones that applied for the patient.</p>
            <attrib>P10</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Workflow Comparison Between Psychiatrists and Clinical Psychologists</title>
          <p>All participants followed the simplified consolidated workflow in their practices. However, there were some noticeable differences between psychiatrists and clinical psychologists. Psychiatric appointments, in general, were shorter (30 min), followed by appointments with clinical psychologists (45-60 min). As psychiatrists can prescribe medication, they check medication use and effects in every patient visit. Psychiatrists also conduct psychotherapy and value the therapeutic relationship between patients and themselves. On the other hand, clinical psychologists cannot prescribe medication, so they focus solely on conducting psychological assessments and delivering psychotherapy. Therefore, the workflow for clinical psychologists can be very dynamic and conversational. Clinical psychologists pay significant attention to patients’ narratives of experience to understand their unique health status and changes. The workflow would be more standardized, however, if a clinical psychologist only focuses on psychological assessments, for example, a cognitive evaluation, as the assessments have a validated procedure to follow and tools to use.</p>
        </sec>
      </sec>
      <sec>
        <title>Qualitative Analysis: Clinician Perspectives</title>
        <sec>
          <title>Dual Attitudes Toward PGHD</title>
          <p>All participants had worked with their patients to track their sleep and/or mood behaviors through an mHealth app and/or a wearable device. Overall, 6 participants held a dual attitude toward PGHD use. On the one hand, clinicians had seen the potential of PGHD and looked forward to taking advantage of them, especially the ability to track their patients’ activities between consultations better:</p>
          <disp-quote>
            <p>There is a long history of using mood scales, potentially longitudinal mood scales, basic tracking charts for depression, bipolar disorder—can be really helpful, also can be somewhat tedious. And there are some apps now that do that very well...”</p>
            <attrib>P05</attrib>
          </disp-quote>
          <p>On the other hand, some concerns were raised about data validity and reliability. The participants were being cautious because they identified the need for reliable PGHD to inform evidence-based treatment implementation and evaluation:</p>
          <disp-quote>
            <p>When you're saying hard data from a device that measures sleep, I would need to know for myself how it's measuring sleep... I think I would tend to question the specificity and accuracy of those for actual sleep... I find that patient self-reports of sleep are unreliable.</p>
            <attrib>P04</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Concerns About Integrating PGHD Into Workflow and EHR</title>
          <p>Clinicians’ concerns about integrating PGHD into workflow and EHR systems were a recurring theme in the interviews. One participant indicated that there was no app that seamlessly integrates its data into EHR:</p>
          <disp-quote>
            <p>So... the way things work now [is] very much sort of pen and paper. You show up at a doctor's office. They get handed some of these screeners and somebody must manually enter it into Epic, which is kind of a pain. We would love to be able to send patients a MyChart message or something and say fill this out and send it back to us and have it automatically go into a flow sheet in Epic that we then track over time with the patient. That would be amazing.</p>
            <attrib>P03</attrib>
          </disp-quote>
          <p>A total of 7 participants preferred using paper-based PGHD in their practice because of the patients’ preference or the lack of data sharing mechanisms in the apps. In this case, the data flow is deemed indirect. Clinicians would review the PGHD in the session and put the interpretations in the clinical notes, which can slow down the clinical workflow. Generating data visualization of PGHD to facilitate the interpretation of the data seems to be a preferable method for both clinicians and patients:</p>
          <disp-quote>
            <p>We also graph patient data over time. I do this with all my patients... It would take 20 minutes of the patient session—patient wouldn’t get care for that 20 minutes and it’s literally I’ll have a calculator out, an actual calculator, my graphing calculator, and I’ll sit there and calculate the data and then manually make the graph. So having programs built in that aggregate data and automatically populate graphs are great; and patients like to see the visual, the graph—they do, overall. And generally it’s good discussion even if the graph is not great in terms of what it’s explaining.</p>
            <attrib>P10</attrib>
          </disp-quote>
          <p>Manually transcribing data into electronic medical records is not only time consuming but also interferes with the patient-clinician interaction because the clinicians are distracted by the data entry tasks on their computer. Common concerns found included the difficulties of having to face the computer and type in data during sessions:</p>
          <disp-quote>
            <p>I'm put[ting] in the data in the computer and looking at the questionnaires and if there was a different way of doing that, you know, it would actually make me take my life away from the computer screen and interact with my patient.</p>
            <attrib>P01</attrib>
          </disp-quote>
          <p>Lack of Information for App Selection</p>
          <p>In addition to the challenges in using data from mHealth apps, it can be challenging to identify what apps to use in the first place. In all, 3 participants found that it was difficult to find an app that met all the requirements. Others sometimes found useful apps through patient recommendations. The following 2 quotes exemplify this situation:</p>
          <disp-quote>
            <p>I've not been able to figure out an app that I could actually use [and] that was specific to be able to individualized for patients; that's been a challenge.</p>
            <attrib>P11</attrib>
          </disp-quote>
          <disp-quote>
            <p>There are lots of great apps out there for sure...and sometimes they'll bring stuff to me that I'm unaware of.</p>
            <attrib>P08</attrib>
          </disp-quote>
          <p>When asked about using apps for collecting data, some clinicians responded that they did not know that mobile apps could perform certain data tracking tasks:</p>
          <disp-quote>
            <p>So, we look at this daily measure sheet, which would be perfect for an app that looks at what their moods have been, what kind of sleep they had.</p>
            <attrib>P11</attrib>
          </disp-quote>
          <p>In contrast, the app review (see details given in the section <italic>Sleep and Mood Tracking App Reviews</italic>) showed that mood apps in the current market can offer certain functions, which means there is a lack of information to increase app awareness and support app selection process, especially for clinicians. This suggests that an app recommendation system for the clinician to use would be very helpful.</p>
        </sec>
        <sec>
          <title>Limited App Features to Support Personalization and Collaborative Care</title>
          <p>One factor contributing to the difficulty of finding the right app is the variety in patients’ health statuses and conditions. Clinicians would prefer to personalize treatment and collect data in a personalized manner. However, current apps were not designed with features to support personalization in data collection. One participant elaborated that:</p>
          <disp-quote>
            <p>A psychiatric exam, ugh, depends on a lot offactors actually...Let's say I have a 60-year-old sort of borderline intellectual functioning person, maybe 8th grade education with never seen a psychiatrist and coming in first time... So that exam...maybe take more time there, more explanation, more education, more time to elicit... I may have to offer something, a different questionnaire other than the standard four to five that I sent to every patient.</p>
            <attrib>P01</attrib>
          </disp-quote>
          <p>Another type of feature that current apps may be missing is to support collaborative care. It is beneficial to support collaborative care so that patients can be more engaged in their health and take control of their care, and clinicians can create a treatment plan that is most suitable and effective for the patient’s situation. One clinician further talked about the difficulty in finding an app in current app markets to address his needs of data collection, although they do have data collection features:</p>
          <disp-quote>
            <p>The app would have to collect data on several different domains like nutrition, like sleep, like physical activity, and then maybe sampling mood multiple times a day. So there are apps that look at the individual factors, but I don't know, I'm not aware there may be an app [that can offer all above].</p>
            <attrib>P09</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>Sleep and Mood Tracking App Reviews</title>
        <sec>
          <title>Statistical Summary</title>
          <p><xref ref-type="table" rid="table2">Table 2</xref> shows the statistical summary of the selected apps. The data were retrieved on September 8, 2019. The average number of reviews was around 400, and the average user rating was around 4.0 for both sleep and mood tracking apps.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Statistical summary of the selected sleep and mood tracking apps.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="500"/>
              <col width="250"/>
              <col width="250"/>
              <thead>
                <tr valign="top">
                  <td>App characteristics</td>
                  <td>Sleep</td>
                  <td>Mood</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Number of apps, n (%)</td>
                  <td>31 (55)</td>
                  <td>25 (45)</td>
                </tr>
                <tr valign="top">
                  <td>Number of reviews, mean (SD)</td>
                  <td>346.1 (896.8)</td>
                  <td>387.8 (912.5)</td>
                </tr>
                <tr valign="top">
                  <td>User rating, mean (SD)</td>
                  <td>3.88 (0.78)</td>
                  <td>3.99 (0.54)</td>
                </tr>
                <tr valign="top">
                  <td>Had a data interpretation feature, n (%)</td>
                  <td>31 (55)</td>
                  <td>21 (38)</td>
                </tr>
                <tr valign="top">
                  <td>Had a data sharing feature, n (%)</td>
                  <td>18 (32)</td>
                  <td>16 (29)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Data Interpretation and Sharing Features</title>
          <p>The data interpretation, which includes collection and visualization, and sharing features in the selected apps varied. All 31 sleep tracking apps offered at least one feature for data interpretation, including sleep quantity statistics (n=27) and sleep quality analysis (n=5). Of the 31 sleep tracking apps, 18 (58%) support data sharing in various means, including direct sharing with other people (n=8) and integration with other apps (n=7).</p>
          <p>The major source of data interpretation is through collecting statistics, through recording several days' worth of accumulated data points. These data points are either manually inputted by users or automatically recorded by the app. Overall, 5 apps also offer qualitative assessments of sleep patterns by presenting the sleep cycles that users experience, recording sound files, and/or providing descriptive sleep analyses.</p>
          <p>Many sleep tracking apps also support sharing data. This is usually done by exporting and downloading the data as a comma-separated values (CSV), PDF, etc file (N=8) or via integration with an alternate app, such as Apple Health (n=7). Other sources include social media (n=3) and email (n=4). Many apps also support multiple forms of sharing.</p>
          <p>Many users find accurate sleep tracking to be helpful in improving their sleep quality and daily life:</p>
          <disp-quote>
            <p>I love this app. Pleasing to the eye and so many great features! I love that it keeps stats on your sleep cycles and can be set to accommodate how your sleep may be affected by working out, caffeine, or other factors.</p>
          </disp-quote>
          <p>On the other hand, common complaints of sleep apps included inaccurate tracking, failures in data collection, and difficulty in use due to technical issues. For example, one user expressed frustration in inaccurate tracking:</p>
          <disp-quote>
            <p>This app has been super frustrating. I use it while wearing my watch and it has recorded me in a deep sleep while I was making food.</p>
          </disp-quote>
          <p>The analysis of mood tracking apps shows similar results. Of the 25 mood tracking apps, 21 (84%) offered either a qualitative (n=4) and/or quantitative (n=22) data interpretation feature. Eight mood apps had more than one mode of quantitative data interpretation. Of the 25 mood tracking apps, 16 (64%) had data sharing capabilities, mainly through direct sharing with other users (n=13) or social media (n=5). Three mood apps had more than one mode of data sharing.</p>
          <p>Many apps offer multiple means of data interpretation. The forms of qualitative data interpretation include monthly reports of the moods logged. Forms of quantitative data interpretation include daily, weekly, or monthly graphs or charts of the frequency of moods logged by the user. The modes of sharing data are exporting the data as a spreadsheet, CSV, PDF, etc file (n=6); via email (n=3); or via cloud sharing (n=3).</p>
          <p>Many users find that the ability of the apps to track and reflect on one’s mood trends was very helpful:</p>
          <disp-quote>
            <p>
            I am not exaggerating to say this app has been life changing. This app allows me to customize the settings so I can simultaneously track my moods, medications, activity level, wellness tools, triggers and alternative treatments. All of this info is so important. Daily logging with an easy interface means I can track LOTS OF DATA in an organized way. The visual graphs show the relationships between these various data points. The info gathered is a valuable tool in my wellness and recovery.
          </p>
          </disp-quote>
          <p>The most common complaint was the limited options of mood offered, which caused difficulties for users in tracking their real mood, as indicated in the following review comments:</p>
          <disp-quote>
            <p>More moods. Exactly the kind of app I need. I just wish there were more moods like: anxious, on edge, tearful, sensitive, irritable, exhausted.</p>
          </disp-quote>
          <p>With both mood and sleep apps, the primary method of data visualization was through graphs and charts (n=37). Sleep apps, which recorded quantitative data more frequently than qualitative data, used statistics (such as the length of time slept) to present graphical summaries of sleep over time. These graphs were then analyzed to show the quality of sleep over time, track trends, inconsistencies, and improvements. Similarly, mood apps also used graphical representations to present data summaries. However, these apps typically used qualitative data entries (such as recorded moods on certain days) to provide graphs and charts that showed the number of times certain moods were recorded and how moods fluctuated over the course of weeks or months. The popular usage of graphs across both categories suggests that regardless of the nature of data collection (either quantitative or qualitative), users prefer apps that visualize data through digestible and succinct representations that make trends identifiable and trackable over time.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>We conducted a mixed methods study with 12 clinicians in mental health practice to understand their perspectives on PGHD and the current use and to share features of the mHealth apps on the market. The results show that mental health clinicians had a dual attitude toward PGHD. The advantages and concerns of PGHD use were aligned with those in the literature. It is not surprising that mental health clinicians have seen the potential of PGHD because they have been largely relying on PROs to develop treatment plans [<xref ref-type="bibr" rid="ref18">18</xref>]. Our results also confirmed that mental health clinicians have concerns about data validity and reliability similar to clinicians in other specialties [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Although mental health practices have started to use PGHD, their use has not been optimized in clinical workflow and integrated into EHR. However, limited PGHD integration with EHRs may not be totally native. Clinicians who have concerns with data reliability and ability may prefer to review PGHD before putting them into EHR, rather than including them directly from mHealth apps and/or wearables. Moreover, our findings revealed that there are different ways to make use of PGHD without integrating it into EHR systems, such as using it to check patient conditions and homework in between clinical sessions. However, personalized data tracking and visualization are critical factors in the successful use of PGHD for both patients and clinicians.</p>
        <p>In addition to using PGHD in clinics, we found that mental health clinicians may have a hard time finding the right mHealth apps for their patients to collect PGHD in the first place. There was a lack of information to help them choose the most suitable apps for their patients to use. Part of the reason is that each patient has a unique mental health status and condition, and mHealth apps do not support much personalization. Moreover, most of the mHealth apps were patient centered but may not support collaborative care. As clinicians and patients frequently make shared decisions for the treatment plan, mHealth apps without features to support collaborative care could reduce clinicians' willingness to adopt them or introduce barriers in clinical workflow. In addition, our review on sleep and mood tracking apps confirmed that the current mHealth apps on the market had limited features in data interpretation (eg, visualization) and limited mechanism to share PGHD with other people and EHR systems.</p>
      </sec>
      <sec>
        <title>Design Implications</title>
        <sec>
          <title>Improve Data Interpretation and Sharing Mechanisms</title>
          <p>Current mood or sleep tracking apps are focused on collecting PGHD in a patient-centered manner, which is a critical first step. However, to maximize the value of PGHD, these apps should improve their mechanisms in data interpretation and sharing. Specifically, data visualization can be a viable way to help both mental health clinicians and patients interpret much PGHD and identify patterns and trends regardless of their integration into EHR. On the other hand, mHealth apps should enable data sharing mechanisms with different parties, including, but not limited to, clinicians, families, friends, and other practitioners, as this was a concern noted by both clinicians during interviews and users in the app review [<xref ref-type="bibr" rid="ref58">58</xref>]. It is worth emphasizing the importance of information confidentiality when designing a sharing mechanism. Psychology clinics are considered as a <italic>safe bed</italic> for patients to discuss their mental health status and conditions with clinicians. Hence, data sharing mechanisms should not be one-size-fit-all; they should be designed to allow patients to select which part of PGHD to share and how to share to keep highest data confidentiality based on their psychiatric conditions.</p>
        </sec>
        <sec>
          <title>Consider Clinical Workflow and EHR Integration</title>
          <p>Technology-enabled clinical data capture and documentation should consider the clinical workflow [<xref ref-type="bibr" rid="ref65">65</xref>]. Similarly, we suggest that mHealth apps designed to gather PGHD should consider clinical workflow to improve the quality of patient experience. Although PROs and PGHD have been used in mental health clinics, there are no guidelines for data collection and use. It would be beneficial to conduct observational workflow analysis, such as time and motion studies, to understand when and where PGHD are used and identified bottlenecks. In fact, it is common to conduct such workflow analysis to design and develop any health information technology that will be used in clinics (eg, clinical decision support tools) [<xref ref-type="bibr" rid="ref66">66</xref>].</p>
          <p>On the other hand, mHealth apps should also consider EHR integration. We have discussed the importance of sharing PGHD with various parties in a way to protect information confidentiality. PGHD may be shared with clinicians directly through EHR integration or indirectly through data summarization and electronic reports. We have also seen a working example in our interviews to integrate PGHD with EHR using a Research Electronic Data Capture database [<xref ref-type="bibr" rid="ref67">67</xref>]. As clinicians may have concerns on data reliability and accuracy, having an indirect EHR integration (eg, a dashboard or PDF report demonstrating patterns in PGHD for review) may be a viable way to reduce clinicians’ concerns and increase their PGHD adoption in clinics. As many apps are coming into the market and are also going obsolete at a fast pace, a standardized data management and export system could be proposed to better integrate PGHD into clinical practice regardless of specific kinds of apps.</p>
        </sec>
        <sec>
          <title>Support Personalized and Collaborative Care</title>
          <p>Our results showed that mHealth apps must support both personalization in data collection and collaboration between patients and clinicians during clinics. In terms of personalization, as each patient has a unique mental health status and conditions in various social contexts, it may be difficult to find an app that covers all kinds of needs of PGHD collection. There are 2 ways to approach this issue from a design perspective. First, mHealth apps should maximize their ability to personalize data collection methods to fit different patient needs. Participatory design methods may be helpful in identifying such needs and incorporating them into app features. Second, as clinicians do not always have the information of some existing apps that are potentially useful, an app recommendation system may be developed to assist clinicians in choosing which apps to use to collect PGHD. Currently, some clinicians rely on patients’ recommendations. This app recommendation system may be maintained by both clinicians and patients.</p>
          <p>In addition, mHealth apps should be designed to support collaborative care. It is critical to ensure that PGHD are used effectively and efficiently during clinics. Ethnographic observations may be needed to systematically document the behaviors and interactions between patients and clinicians. The results can help researchers better understand the role that PGHD and mHealth apps play during clinic visits and generate guidelines to redesign mHealth apps and improve the use of PGHD to support shared decision-making and collaborative care.</p>
        </sec>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study has a few limitations. First, it was conducted in one institution using convenience sampling to recruit participants, thereby limiting generalizability. Second, the study only included clinicians, whereas patients’ perspectives were only indirectly approached through our research on app reviews. However, we believe that the clinician perspective on PGHD was sufficiently understood because we continued recruiting the participants until the data reached saturation. Moreover, we compared the interview data with the app review data, which were complementary, to generate the design implications. Third, the app review was conducted using a snapshot of mHealth apps investigated in the past 2 years. The apps may have since then been updated, resulting in fluctuating ratings and different features. However, the efficacy of the app review remains the same, as it helps identify the keep features that users look for in mHealth apps and provides sufficient data to inform app designers. Finally, clinicians can have several subspecialties in mental health, which affects their workflow and how they use PGHD. We were not able to recruit a diverse sample to include all the opinions from the mental health clinicians. However, this study focused on the common workflow components in mental health practices and served as a pilot study to understand clinician perspectives.</p>
      </sec>
      <sec>
        <title>Future Directions</title>
        <p>We will continue investigating the best practices for using PGHD at the point of care, considering clinical workflow and developing informatics solutions to facilitate the development of a collaborative model to make sense of PGHD to inform shared decisions. The PGHD here will not be limited to data gathered from mHealth apps and wearable devices. They can include data from social media (eg, Twitter and forums) to synthesize more information about patients’ opinions on their health [<xref ref-type="bibr" rid="ref68">68</xref>]. Interactive data visualization may be a viable way to achieve the common goals of clinicians and patients. Moreover, we will pay specific attention to the integration between PGHD and EHR and further develop clinical decision support tools with machine intelligence to use this new and valuable dataset to improve patient outcomes.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study demonstrated the clinicians’ perspectives on PGHD and the current features of mHealth apps. The results showed that PGHD have been used in mental health practices but in a suboptimal way without guidelines. Clinicians look forward to the potential benefit of using PGHD but have dual attitudes toward PGHD. That is, clinicians see the potential of PGHD but hesitate to embrace them mainly because of data validity and reliability concerns. Other concerns about workflow and EHR integration exist prevalently. Moreover, clinicians experienced challenges in selecting suitable apps for their patients, partly because of the limited features of mHealth apps in supporting personalized and collaborative care. We identified 3 design implications: (1) improve data interpretation and sharing mechanisms, (2) consider clinical workflow and EHR integration, and (3) support personalized and collaborative care. We will continue our research with a focus on designing and developing informatics solutions to demonstrate the best practices of PGHD use and evaluate their effectiveness in improving patient outcomes.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Sleep and mood app selection process.</p>
        <media xlink:href="formative_v4i8e18123_app1.docx" xlink:title="DOCX File , 67 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Detailed consolidated workflow diagram.</p>
        <media xlink:href="formative_v4i8e18123_app2.docx" xlink:title="DOCX File , 3820 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">API</term>
          <def>
            <p>application programming interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CHV</term>
          <def>
            <p>consumer health vocabulary</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CSV</term>
          <def>
            <p>comma-separated values</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EMA</term>
          <def>
            <p>ecological momentary assessment</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">HRQoL</term>
          <def>
            <p>health-related quality of life</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">ONC</term>
          <def>
            <p>Office of the National Coordinator for Health Information Technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">PGHD</term>
          <def>
            <p>patient-generated health data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PRO</term>
          <def>
            <p>patient-reported outcome</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was conducted using the first (corresponding) author’s start-up funds. The author led and coordinated the effort in study design, data collection and analysis, results interpretation, manuscript writing, and decisions to submit for publication. The authors would like to thank all the participating mental health clinicians in this study. The authors would also like to thank Mr Jason Revalee, Mr Ruthvik Abbu, Ms Shuai Mu, Ms Longwei Li, and Ms Qiyang Zhou for their help in interview data collection and analysis, literature review, and manuscript proofread.</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>Cortez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hsii</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Riehl</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Conceptualizing a Data Infrastructure for the Capture, Use, and Sharing of Patient-Generated Health Data in Care Delivery and Research through 2024</article-title>
          <source>Office of the National Coordinator for Health Information</source>
          <year>2018</year>
          <access-date>2020-07-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/onc_pghd_final_white_paper.pdf">https://www.healthit.gov/sites/default/files/onc_pghd_final_white_paper.pdf</ext-link>
          </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>Lai</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Hsueh</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>YK</given-names>
            </name>
            <name name-style="western">
              <surname>Austin</surname>
              <given-names>RR</given-names>
            </name>
          </person-group>
          <article-title>Present and future trends in consumer health informatics and patient-generated health data</article-title>
          <source>Yearb Med Inform</source>
          <year>2017</year>
          <month>08</month>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>152</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.15265/IY-2017-016"/>
          </comment>
          <pub-id pub-id-type="doi">10.15265/IY-2017-016</pub-id>
          <pub-id pub-id-type="medline">29063559</pub-id>
          <pub-id pub-id-type="pmcid">PMC6239232</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lober</surname>
              <given-names>WB</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>HL</given-names>
            </name>
          </person-group>
          <article-title>Patient-generated health data in surgical site infection: changing clinical workflow and care delivery</article-title>
          <source>Surg Infect (Larchmt)</source>
          <year>2019</year>
          <month>10</month>
          <volume>20</volume>
          <issue>7</issue>
          <fpage>571</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1089/sur.2019.195</pub-id>
          <pub-id pub-id-type="medline">31397635</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Semple</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Lober</surname>
              <given-names>WB</given-names>
            </name>
            <name name-style="western">
              <surname>Lavallee</surname>
              <given-names>DC</given-names>
            </name>
          </person-group>
          <article-title>Implementing mobile health interventions to capture post-operative patient-generated health data</article-title>
          <source>Surg Infect (Larchmt)</source>
          <year>2019</year>
          <month>10</month>
          <volume>20</volume>
          <issue>7</issue>
          <fpage>566</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.1089/sur.2019.151</pub-id>
          <pub-id pub-id-type="medline">31429637</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lv</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Simmons</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Rosas</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Entwistle</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Personalized hypertension management using patient-generated health data integrated with electronic health records (EMPOWER-H): six-month pre-post study</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>09</month>
          <day>19</day>
          <volume>19</volume>
          <issue>9</issue>
          <fpage>e311</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/9/e311/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7831</pub-id>
          <pub-id pub-id-type="medline">28928111</pub-id>
          <pub-id pub-id-type="pii">v19i9e311</pub-id>
          <pub-id pub-id-type="pmcid">PMC5627043</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Islind</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Lindroth</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lundin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Steineck</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Shift in translations: data work with patient-generated health data in clinical practice</article-title>
          <source>Health Informatics J</source>
          <year>2019</year>
          <month>09</month>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>577</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1177/1460458219833097</pub-id>
          <pub-id pub-id-type="medline">30866707</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>Adler-Milstein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nong</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Early experiences with patient generated health data: health system and patient perspectives</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <month>10</month>
          <day>1</day>
          <volume>26</volume>
          <issue>10</issue>
          <fpage>952</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz045</pub-id>
          <pub-id pub-id-type="medline">31329886</pub-id>
          <pub-id pub-id-type="pii">5476189</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>Demiris</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Iribarren</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sward</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Patient generated health data use in clinical practice: a systematic review</article-title>
          <source>Nurs Outlook</source>
          <year>2019</year>
          <volume>67</volume>
          <issue>4</issue>
          <fpage>311</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1016/j.outlook.2019.04.005</pub-id>
          <pub-id pub-id-type="medline">31277895</pub-id>
          <pub-id pub-id-type="pii">S0029-6554(19)30043-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC6697140</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>Cohen</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Keller</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Hayes</surname>
              <given-names>GR</given-names>
            </name>
            <name name-style="western">
              <surname>Dorr</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
          </person-group>
          <article-title>Integrating patient-generated health data into clinical care settings or clinical decision-making: lessons learned from project healthdesign</article-title>
          <source>JMIR Hum Factors</source>
          <year>2016</year>
          <month>10</month>
          <day>19</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>e26</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2016/2/e26/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/humanfactors.5919</pub-id>
          <pub-id pub-id-type="medline">27760726</pub-id>
          <pub-id pub-id-type="pii">v3i2e26</pub-id>
          <pub-id pub-id-type="pmcid">PMC5093296</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>Ammenwerth</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Spötl</surname>
              <given-names>HP</given-names>
            </name>
          </person-group>
          <article-title>The time needed for clinical documentation versus direct patient care. A work-sampling analysis of physicians' activities</article-title>
          <source>Methods Inf Med</source>
          <year>2009</year>
          <volume>48</volume>
          <issue>1</issue>
          <fpage>84</fpage>
          <lpage>91</lpage>
          <pub-id pub-id-type="medline">19151888</pub-id>
          <pub-id pub-id-type="pii">09010084</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>Poissant</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tamblyn</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kawasumi</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>The impact of electronic health records on time efficiency of physicians and nurses: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2005</year>
          <volume>12</volume>
          <issue>5</issue>
          <fpage>505</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/15905487"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M1700</pub-id>
          <pub-id pub-id-type="medline">15905487</pub-id>
          <pub-id pub-id-type="pii">M1700</pub-id>
          <pub-id pub-id-type="pmcid">PMC1205599</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>Sinsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Colligan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Prgomet</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reynolds</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goeders</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tutty</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Blike</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Allocation of physician time in ambulatory practice: a time and motion study in 4 specialties</article-title>
          <source>Ann Intern Med</source>
          <year>2016</year>
          <month>12</month>
          <day>6</day>
          <volume>165</volume>
          <issue>11</issue>
          <fpage>753</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.7326/M16-0961</pub-id>
          <pub-id pub-id-type="medline">27595430</pub-id>
          <pub-id pub-id-type="pii">2546704</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>Chung</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>Potential and challenges of patient-generated health data for high-quality cancer care</article-title>
          <source>J Oncol Pract</source>
          <year>2015</year>
          <month>05</month>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>195</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25852139"/>
          </comment>
          <pub-id pub-id-type="doi">10.1200/JOP.2015.003715</pub-id>
          <pub-id pub-id-type="medline">25852139</pub-id>
          <pub-id pub-id-type="pii">JOP.2015.003715</pub-id>
          <pub-id pub-id-type="pmcid">PMC4438108</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>Nundy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Peek</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Using patient-generated health data from mobile technologies for diabetes self-management support: provider perspectives from an academic medical center</article-title>
          <source>J Diabetes Sci Technol</source>
          <year>2014</year>
          <month>01</month>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>74</fpage>
          <lpage>82</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24876541"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1932296813511727</pub-id>
          <pub-id pub-id-type="medline">24876541</pub-id>
          <pub-id pub-id-type="pii">8/1/74</pub-id>
          <pub-id pub-id-type="pmcid">PMC4454095</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>Reading</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Merrill</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Converging and diverging needs between patients and providers who are collecting and using patient-generated health data: an integrative review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>06</month>
          <day>1</day>
          <volume>25</volume>
          <issue>6</issue>
          <fpage>759</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29471330"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy006</pub-id>
          <pub-id pub-id-type="medline">29471330</pub-id>
          <pub-id pub-id-type="pii">4869761</pub-id>
          <pub-id pub-id-type="pmcid">PMC5978018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelley</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Self-Tracking for Mental Wellness: Understanding Expert Perspectives and Student Experiences</article-title>
          <source>Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems</source>
          <year>2017</year>
          <conf-name>CHI'17</conf-name>
          <conf-date>May 6-11, 2017</conf-date>
          <conf-loc>Denver, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3025453.3025750</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>MindNavigator: Exploring the Stress and Self-Interventions for Mental Wellness</article-title>
          <source>Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems</source>
          <year>2018</year>
          <conf-name>CHI'18</conf-name>
          <conf-date>April 21-26, 2018</conf-date>
          <conf-loc>Montreal, QC, Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3173574.3174146</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>Sartorius</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Patient-reported outcomes in psychiatry</article-title>
          <source>Dialogues Clin Neurosci</source>
          <year>2014</year>
          <month>06</month>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>123</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25152651"/>
          </comment>
          <pub-id pub-id-type="medline">25152651</pub-id>
          <pub-id pub-id-type="pmcid">PMC4140506</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>US Department of Health and Human Services FDA Center for Drug Evaluation and Research</collab>
            <collab>US Department of Health and Human Services FDA Center for Biologics, Evaluation and Research</collab>
            <collab>US Department of Health and Human Services FDA Center for Devices and Radiological Health</collab>
          </person-group>
          <article-title>Guidance for industry: patient-reported outcome measures: use in medical product development to support labeling claims: draft guidance</article-title>
          <source>Health Qual Life Outcomes</source>
          <year>2006</year>
          <month>10</month>
          <day>11</day>
          <volume>4</volume>
          <fpage>79</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hqlo.biomedcentral.com/articles/10.1186/1477-7525-4-79"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1477-7525-4-79</pub-id>
          <pub-id pub-id-type="medline">17034633</pub-id>
          <pub-id pub-id-type="pii">1477-7525-4-79</pub-id>
          <pub-id pub-id-type="pmcid">PMC1629006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Deering</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Issue Brief: Patient-Generated Health Data and Health IT</article-title>
          <source>Office of the National Coordinator for Health Information</source>
          <year>2013</year>
          <access-date>2020-07-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docs.google.com/viewer?url=http%3A%2F%2Fwww.healthit.gov%2Fsites%2Fdefault%2Ffiles%2Fpghd_brief_final122013.pdf.">https://docs.google.com/viewer?url=http%3A%2F%2Fwww.healthit.gov%2Fsites%2Fdefault%2Ffiles%2Fpghd_brief_final122013.pdf.</ext-link>
          </comment>
        </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>Ancker</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Mauer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kalish</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Vest</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Gossey</surname>
              <given-names>JT</given-names>
            </name>
          </person-group>
          <article-title>Early adopters of patient-generated health data upload in an electronic patient portal</article-title>
          <source>Appl Clin Inform</source>
          <year>2019</year>
          <month>03</month>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>254</fpage>
          <lpage>60</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30970383"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0039-1683987</pub-id>
          <pub-id pub-id-type="medline">30970383</pub-id>
          <pub-id pub-id-type="pmcid">PMC6458021</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>Reading</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baik</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Beauchemin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hickey</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Merrill</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing sustained engagement with ECG self-monitoring: perspectives from patients and health care providers</article-title>
          <source>Appl Clin Inform</source>
          <year>2018</year>
          <month>10</month>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>772</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30304745"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1672138</pub-id>
          <pub-id pub-id-type="medline">30304745</pub-id>
          <pub-id pub-id-type="pmcid">PMC6179719</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>Vizer</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Eschler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Koo</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Ralston</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Munson</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>'It's not just technology, it's people': constructing a conceptual model of shared health informatics for tracking in chronic illness management</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>04</month>
          <day>29</day>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>e10830</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/4/e10830/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10830</pub-id>
          <pub-id pub-id-type="medline">31033452</pub-id>
          <pub-id pub-id-type="pii">v21i4e10830</pub-id>
          <pub-id pub-id-type="pmcid">PMC6658298</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>Bourgeois</surname>
              <given-names>FT</given-names>
            </name>
            <name name-style="western">
              <surname>Porter</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Valim</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>EF</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>The value of patient self-report for disease surveillance</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2007</year>
          <volume>14</volume>
          <issue>6</issue>
          <fpage>765</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/17712092"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M2134</pub-id>
          <pub-id pub-id-type="medline">17712092</pub-id>
          <pub-id pub-id-type="pii">M2134</pub-id>
          <pub-id pub-id-type="pmcid">PMC2213481</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>Woods</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>NC</given-names>
            </name>
            <name name-style="western">
              <surname>Frisbee</surname>
              <given-names>KL</given-names>
            </name>
          </person-group>
          <article-title>Integrating patient voices into health information for self-care and patient-clinician partnerships: Veterans Affairs design recommendations for patient-generated data applications</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>05</month>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>491</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv199</pub-id>
          <pub-id pub-id-type="medline">26911810</pub-id>
          <pub-id pub-id-type="pii">ocv199</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>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>WS</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Managing patient-generated health data through mobile personal health records: analysis of usage data</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>04</month>
          <day>9</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e89</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/4/e89/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9620</pub-id>
          <pub-id pub-id-type="medline">29631989</pub-id>
          <pub-id pub-id-type="pii">v6i4e89</pub-id>
          <pub-id pub-id-type="pmcid">PMC5913571</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>Huba</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Designing patient-centered personal health records (PHRs): health care professionals' perspective on patient-generated data</article-title>
          <source>J Med Syst</source>
          <year>2012</year>
          <month>12</month>
          <volume>36</volume>
          <issue>6</issue>
          <fpage>3893</fpage>
          <lpage>905</lpage>
          <pub-id pub-id-type="doi">10.1007/s10916-012-9861-z</pub-id>
          <pub-id pub-id-type="medline">22644130</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>Nittas</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Lun</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ehrler</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Puhan</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Mütsch</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Electronic patient-generated health data to facilitate disease prevention and health promotion: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>10</month>
          <day>14</day>
          <volume>21</volume>
          <issue>10</issue>
          <fpage>e13320</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/10/e13320/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13320</pub-id>
          <pub-id pub-id-type="medline">31613225</pub-id>
          <pub-id pub-id-type="pii">v21i10e13320</pub-id>
          <pub-id pub-id-type="pmcid">PMC6914107</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <article-title>Number of Internet Users Worldwide From 2005 to 2019 (in Millions)</article-title>
          <source>Statista</source>
          <access-date>2019-09-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.statista.com/statistics/273018/number-of-internet-users-worldwide/">https://www.statista.com/statistics/273018/number-of-internet-users-worldwide/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>ICT Fats and Figures</article-title>
          <source>Google Docs</source>
          <year>2017</year>
          <access-date>2019-09-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docs.google.com/viewer?url=https%3A%2F%2Fwww.itu.int%2Fen%2FITU-D%2FStatistics%2FDocuments%2Ffacts%2FICTFactsFigures2017.pdf">https://docs.google.com/viewer?url=https%3A%2F%2Fwww.itu.int%2Fen%2FITU-D%2FStatistics%2FDocuments%2Ffacts%2FICTFactsFigures2017.pdf</ext-link>
          </comment>
        </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>Burns</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>McBride</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>FitzGerald</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mathews</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Drennan</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Creating consumer-generated health data: interviews and a pilot trial exploring how and why patients engage</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>06</month>
          <day>13</day>
          <volume>21</volume>
          <issue>6</issue>
          <fpage>e12367</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/6/e12367/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12367</pub-id>
          <pub-id pub-id-type="medline">31199312</pub-id>
          <pub-id pub-id-type="pii">v21i6e12367</pub-id>
          <pub-id pub-id-type="pmcid">PMC6598415</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>Patel</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Asch</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Volpp</surname>
              <given-names>KG</given-names>
            </name>
          </person-group>
          <article-title>Wearable devices as facilitators, not drivers, of health behavior change</article-title>
          <source>J Am Med Assoc</source>
          <year>2015</year>
          <month>02</month>
          <day>3</day>
          <volume>313</volume>
          <issue>5</issue>
          <fpage>459</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2014.14781</pub-id>
          <pub-id pub-id-type="medline">25569175</pub-id>
          <pub-id pub-id-type="pii">2089651</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>Al Ayubi</surname>
              <given-names>SU</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Branch</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A persuasive and social mhealth application for physical activity: a usability and feasibility study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2014</year>
          <month>05</month>
          <day>22</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e25</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2014/2/e25/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.2902</pub-id>
          <pub-id pub-id-type="medline">25099928</pub-id>
          <pub-id pub-id-type="pii">v2i2e25</pub-id>
          <pub-id pub-id-type="pmcid">PMC4114463</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>Du</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Venkatakrishnan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Youngblood</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Ram</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pirolli</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A group-based mobile application to increase adherence in exercise and nutrition programs: a factorial design feasibility study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2016</year>
          <month>01</month>
          <day>15</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>e4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2016/1/e4/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.4900</pub-id>
          <pub-id pub-id-type="medline">26772910</pub-id>
          <pub-id pub-id-type="pii">v4i1e4</pub-id>
          <pub-id pub-id-type="pmcid">PMC4733222</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>Wood</surname>
              <given-names>WA</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Emerging uses of patient generated health data in clinical research</article-title>
          <source>Mol Oncol</source>
          <year>2015</year>
          <month>05</month>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>1018</fpage>
          <lpage>24</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1574-7891(14)00201-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.molonc.2014.08.006</pub-id>
          <pub-id pub-id-type="medline">25248998</pub-id>
          <pub-id pub-id-type="pii">S1574-7891(14)00201-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC5528746</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keselman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tse</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Crowell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Browne</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ngo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>Assessing consumer health vocabulary familiarity: an exploratory study</article-title>
          <source>J Med Internet Res</source>
          <year>2007</year>
          <month>03</month>
          <day>14</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e5</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2007/1/e5/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9.1.e5</pub-id>
          <pub-id pub-id-type="medline">17478414</pub-id>
          <pub-id pub-id-type="pii">v9i1e5</pub-id>
          <pub-id pub-id-type="pmcid">PMC1874513</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>QT</given-names>
            </name>
            <name name-style="western">
              <surname>Tse</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Divita</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Keselman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Crowell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Browne</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Goryachev</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ngo</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Term identification methods for consumer health vocabulary development</article-title>
          <source>J Med Internet Res</source>
          <year>2007</year>
          <month>02</month>
          <day>28</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2007/1/e4/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9.1.e4</pub-id>
          <pub-id pub-id-type="medline">17478413</pub-id>
          <pub-id pub-id-type="pii">v9i1e4</pub-id>
          <pub-id pub-id-type="pmcid">PMC1874512</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Doing-Harris</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng-Treitler</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>Computer-assisted update of a consumer health vocabulary through mining of social network data</article-title>
          <source>J Med Internet Res</source>
          <year>2011</year>
          <month>05</month>
          <day>17</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>e37</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2011/2/e37/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1636</pub-id>
          <pub-id pub-id-type="medline">21586386</pub-id>
          <pub-id pub-id-type="pii">v13i2e37</pub-id>
          <pub-id pub-id-type="pmcid">PMC3221384</pub-id>
        </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>Gu</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Jian</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lei</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Development of a consumer health vocabulary by mining health forum texts based on word embedding: semiautomatic approach</article-title>
          <source>JMIR Med Inform</source>
          <year>2019</year>
          <month>05</month>
          <day>23</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>e12704</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2019/2/e12704/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12704</pub-id>
          <pub-id pub-id-type="medline">31124461</pub-id>
          <pub-id pub-id-type="pii">v7i2e12704</pub-id>
          <pub-id pub-id-type="pmcid">PMC6552449</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>He</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Oh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Enriching consumer health vocabulary through mining a social Q&#38;A site: a similarity-based approach</article-title>
          <source>J Biomed Inform</source>
          <year>2017</year>
          <month>05</month>
          <volume>69</volume>
          <fpage>75</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30065-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2017.03.016</pub-id>
          <pub-id pub-id-type="medline">28359728</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(17)30065-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5488691</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>Vydiswaran</surname>
              <given-names>VG</given-names>
            </name>
            <name name-style="western">
              <surname>Mei</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Hanauer</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Mining consumer health vocabulary from community-generated text</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2014</year>
          <volume>2014</volume>
          <fpage>1150</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25954426"/>
          </comment>
          <pub-id pub-id-type="medline">25954426</pub-id>
          <pub-id pub-id-type="pmcid">PMC4419967</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>Gollamudi</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wineinger</surname>
              <given-names>NE</given-names>
            </name>
          </person-group>
          <article-title>A framework for smartphone-enabled, patient-generated health data analysis</article-title>
          <source>PeerJ</source>
          <year>2016</year>
          <volume>4</volume>
          <fpage>e2284</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.7717/peerj.2284"/>
          </comment>
          <pub-id pub-id-type="doi">10.7717/peerj.2284</pub-id>
          <pub-id pub-id-type="medline">27547580</pub-id>
          <pub-id pub-id-type="pii">2284</pub-id>
          <pub-id pub-id-type="pmcid">PMC4975026</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>Plastiras</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>O'Sullivan</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Exchanging personal health data with electronic health records: a standardized information model for patient generated health data and observations of daily living</article-title>
          <source>Int J Med Inform</source>
          <year>2018</year>
          <month>12</month>
          <volume>120</volume>
          <fpage>116</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.10.006</pub-id>
          <pub-id pub-id-type="medline">30409336</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30339-3</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>Hsueh</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Dey</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Das</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wetter</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Making sense of patient-generated health data for interpretable patient-centered care: the transition from 'more' to 'better'</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>245</volume>
          <fpage>113</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="medline">29295063</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nilsen</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Abernethy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Atienza</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Patrick</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Pavel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>WT</given-names>
            </name>
            <name name-style="western">
              <surname>Shar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Spring</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Spruijt-Metz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hedeker</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Honavar</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Kravitz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lefebvre</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Mohr</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Quinn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Shusterman</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Swendeman</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Mobile health technology evaluation: the mHealth evidence workshop</article-title>
          <source>Am J Prev Med</source>
          <year>2013</year>
          <month>08</month>
          <volume>45</volume>
          <issue>2</issue>
          <fpage>228</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23867031"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.amepre.2013.03.017</pub-id>
          <pub-id pub-id-type="medline">23867031</pub-id>
          <pub-id pub-id-type="pii">S0749-3797(13)00277-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC3803146</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdolkhani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Borda</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>de Souza</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Patient-generated health data quality for clinical use: human and technology factors</article-title>
          <source>Iproc</source>
          <year>2018</year>
          <month>09</month>
          <day>17</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e11703</fpage>
          <pub-id pub-id-type="doi">10.2196/11703</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>DeMuro</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Legal and regulatory considerations associated with use of patient-generated health data from social media and mobile health (mHealth) devices</article-title>
          <source>Appl Clin Inform</source>
          <year>2015</year>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>16</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25848410"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2014-09-R-0082</pub-id>
          <pub-id pub-id-type="medline">25848410</pub-id>
          <pub-id pub-id-type="pmcid">PMC4377557</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdolkhani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Borda</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Quality management of patient generated health data in remote patient monitoring using medical wearables - a systematic review</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2018</year>
          <volume>252</volume>
          <fpage>1</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="medline">30040674</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>What Is Psychiatry?</article-title>
          <source>American Psychiatric Association</source>
          <access-date>2020-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.psychiatry.org/patients-families/what-is-psychiatry">https://www.psychiatry.org/patients-families/what-is-psychiatry</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Revicki</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Kleinman</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cella</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A history of health-related quality of life outcomes in psychiatry</article-title>
          <source>Dialogues Clin Neurosci</source>
          <year>2014</year>
          <month>06</month>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>127</fpage>
          <lpage>35</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25152652"/>
          </comment>
          <pub-id pub-id-type="medline">25152652</pub-id>
          <pub-id pub-id-type="pmcid">PMC4140507</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bendich</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Patterson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mulvihill</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Barry</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bini</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Changes in prospectively collected longitudinal patient-generated health data are associated with short-term patient-reported outcomes after total joint arthroplasty: a pilot study</article-title>
          <source>Arthroplast Today</source>
          <year>2019</year>
          <month>03</month>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>61</fpage>
          <lpage>3</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2352-3441(19)30007-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.artd.2019.01.005</pub-id>
          <pub-id pub-id-type="medline">31020024</pub-id>
          <pub-id pub-id-type="pii">S2352-3441(19)30007-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC6470351</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cella</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hahn</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Butt</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Nowinski</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rothrock</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lohr</surname>
              <given-names>KN</given-names>
            </name>
          </person-group>
          <article-title>Patient-reported outcomes in performance measurement</article-title>
          <source>Research Triangle Park</source>
          <year>2015</year>
          <fpage>-</fpage>
          <pub-id pub-id-type="medline">28211667</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shiffman</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Hufford</surname>
              <given-names>MR</given-names>
            </name>
          </person-group>
          <article-title>Ecological momentary assessment</article-title>
          <source>Annu Rev Clin Psychol</source>
          <year>2008</year>
          <volume>4</volume>
          <fpage>1</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1146/annurev.clinpsy.3.022806.091415</pub-id>
          <pub-id pub-id-type="medline">18509902</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bidargaddi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Musiat</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Makinen</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Ermes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schrader</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Licinio</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital footprints: facilitating large-scale environmental psychiatric research in naturalistic settings through data from everyday technologies</article-title>
          <source>Mol Psychiatry</source>
          <year>2017</year>
          <month>02</month>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>164</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27922603"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/mp.2016.224</pub-id>
          <pub-id pub-id-type="medline">27922603</pub-id>
          <pub-id pub-id-type="pii">mp2016224</pub-id>
          <pub-id pub-id-type="pmcid">PMC5285463</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zalta</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Schueller</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Veterans' perspectives on FitBit use in treatment for post-traumatic stress disorder: an interview study</article-title>
          <source>JMIR Ment Health</source>
          <year>2018</year>
          <month>06</month>
          <day>15</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e10415</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mental.jmir.org/2018/2/e10415/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10415</pub-id>
          <pub-id pub-id-type="medline">29907556</pub-id>
          <pub-id pub-id-type="pii">v5i2e10415</pub-id>
          <pub-id pub-id-type="pmcid">PMC6026306</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Hodsdon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bechtel</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Fortney</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Applying the principles for digital development: case study of a smartphone app to support collaborative care for rural patients with posttraumatic stress disorder or bipolar disorder</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>06</month>
          <day>6</day>
          <volume>20</volume>
          <issue>6</issue>
          <fpage>e10048</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/6/e10048/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10048</pub-id>
          <pub-id pub-id-type="medline">29875085</pub-id>
          <pub-id pub-id-type="pii">v20i6e10048</pub-id>
          <pub-id pub-id-type="pmcid">PMC6010837</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berrouiguet</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Perez-Rodriguez</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Larsen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baca-García</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Courtet</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Oquendo</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>From ehealth to ihealth: transition to participatory and personalized medicine in mental health</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>01</month>
          <day>3</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>e2</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/1/e2/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7412</pub-id>
          <pub-id pub-id-type="medline">29298748</pub-id>
          <pub-id pub-id-type="pii">v20i1e2</pub-id>
          <pub-id pub-id-type="pmcid">PMC5772066</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>DeMuro</surname>
              <given-names>PR</given-names>
            </name>
          </person-group>
          <article-title>mHealth: don't forget all the stakeholders in the business case</article-title>
          <source>Med 2 0</source>
          <year>2015</year>
          <month>12</month>
          <day>31</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medicine20.com/2015/2/e4/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/med20.4349</pub-id>
          <pub-id pub-id-type="medline">26720310</pub-id>
          <pub-id pub-id-type="pii">v4i2e4</pub-id>
          <pub-id pub-id-type="pmcid">PMC4713907</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Olano</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Google-Play-Scraper</article-title>
          <source>GitHub</source>
          <access-date>2020-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/facundoolano/google-play-scraper">https://github.com/facundoolano/google-play-scraper</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Olano</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>App-Store-Scraper</article-title>
          <source>GitHub</source>
          <access-date>2020-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/facundoolano/app-store-scraper">https://github.com/facundoolano/app-store-scraper</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Unertl</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Novak</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>KB</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenzi</surname>
              <given-names>NM</given-names>
            </name>
          </person-group>
          <article-title>Traversing the many paths of workflow research: developing a conceptual framework of workflow terminology through a systematic literature review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2010</year>
          <volume>17</volume>
          <issue>3</issue>
          <fpage>265</fpage>
          <lpage>73</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20442143"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2010.004333</pub-id>
          <pub-id pub-id-type="medline">20442143</pub-id>
          <pub-id pub-id-type="pii">17/3/265</pub-id>
          <pub-id pub-id-type="pmcid">PMC2995718</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</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>
            <name name-style="western">
              <surname>Delahunt</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Doing a thematic analysis: A practical, step-by-step guide for learning and teaching scholars</article-title>
          <source>All Ireland Journal of Higher Education</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ojs.aishe.org/aishe/index.php/aishe-j/article/view/335">https://ojs.aishe.org/aishe/index.php/aishe-j/article/view/335</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Caldeira</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Mobile apps for mood tracking: an analysis of features and user reviews</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2017</year>
          <volume>2017</volume>
          <fpage>495</fpage>
          <lpage>504</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29854114"/>
          </comment>
          <pub-id pub-id-type="medline">29854114</pub-id>
          <pub-id pub-id-type="pmcid">PMC5977660</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>YK</given-names>
            </name>
            <name name-style="western">
              <surname>Demiris</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Iribarren</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Landis</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>McCurry</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Heitkemper</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Ward</surname>
              <given-names>TM</given-names>
            </name>
          </person-group>
          <article-title>Smartphone applications to support sleep self-management: review and evaluation</article-title>
          <source>J Clin Sleep Med</source>
          <year>2018</year>
          <month>10</month>
          <day>15</day>
          <volume>14</volume>
          <issue>10</issue>
          <fpage>1783</fpage>
          <lpage>90</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.5664/jcsm.7396"/>
          </comment>
          <pub-id pub-id-type="doi">10.5664/jcsm.7396</pub-id>
          <pub-id pub-id-type="medline">30353814</pub-id>
          <pub-id pub-id-type="pii">jc-18-00177</pub-id>
          <pub-id pub-id-type="pmcid">PMC6175783</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cusack</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bloomrosen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Weaver</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mamykina</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The future state of clinical data capture and documentation: a report from AMIA's 2011 policy meeting</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>01</month>
          <day>1</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>134</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22962195"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-001093</pub-id>
          <pub-id pub-id-type="medline">22962195</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-001093</pub-id>
          <pub-id pub-id-type="pmcid">PMC3555335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ozkaynak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>DT</given-names>
            </name>
            <name name-style="western">
              <surname>Hannah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dayan</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Mistry</surname>
              <given-names>RD</given-names>
            </name>
          </person-group>
          <article-title>Examining workflow in a pediatric emergency department to develop a clinical decision support for an antimicrobial stewardship program</article-title>
          <source>Appl Clin Inform</source>
          <year>2018</year>
          <month>04</month>
          <volume>9</volume>
          <issue>2</issue>
          <fpage>248</fpage>
          <lpage>60</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29642247"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1641594</pub-id>
          <pub-id pub-id-type="medline">29642247</pub-id>
          <pub-id pub-id-type="pmcid">PMC5896382</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thielke</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Conde</surname>
              <given-names>JG</given-names>
            </name>
          </person-group>
          <article-title>Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title>
          <source>J Biomed Inform</source>
          <year>2009</year>
          <month>04</month>
          <volume>42</volume>
          <issue>2</issue>
          <fpage>377</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(08)00122-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id>
          <pub-id pub-id-type="medline">18929686</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(08)00122-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC2700030</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Golder</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Macy</surname>
              <given-names>MW</given-names>
            </name>
          </person-group>
          <article-title>Digital footprints: opportunities and challenges for online social research</article-title>
          <source>Annu Rev Sociol</source>
          <year>2014</year>
          <month>07</month>
          <day>30</day>
          <volume>40</volume>
          <issue>1</issue>
          <fpage>129</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1146/annurev-soc-071913-043145</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
