<?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">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</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">v8i1e15329</article-id>
      <article-id pub-id-type="pmid">32012090</article-id>
      <article-id pub-id-type="doi">10.2196/15329</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>Quality Assurance of Health Wearables Data: Participatory Workshop on Barriers, Solutions, and Expectations</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>West</surname>
            <given-names>Peter</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Salisbury</surname>
            <given-names>Joseph</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Abdolkhani</surname>
            <given-names>Robab</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Health and Biomedical Informatics Centre</institution>
            <institution>The University of Melbourne</institution>
            <addr-line>Level 13</addr-line>
            <addr-line>305 Grattan St</addr-line>
            <addr-line>Melbourne, Victoria, 3000</addr-line>
            <country>Australia</country>
            <phone>61 390358703</phone>
            <email>rabdolkhani@student.unimelb.edu.au</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6741-7543</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Gray</surname>
            <given-names>Kathleen</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1616-2170</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Borda</surname>
            <given-names>Ann</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3884-2978</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>DeSouza</surname>
            <given-names>Ruth</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3862-5375</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Health and Biomedical Informatics Centre</institution>
        <institution>The University of Melbourne</institution>
        <addr-line>Melbourne, Victoria</addr-line>
        <country>Australia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Robab Abdolkhani <email>rabdolkhani@student.unimelb.edu.au</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>1</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>22</day>
        <month>1</month>
        <year>2020</year>
      </pub-date>
      <volume>8</volume>
      <issue>1</issue>
      <elocation-id>e15329</elocation-id>
      <history>
        <date date-type="received">
          <day>1</day>
          <month>7</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>15</day>
          <month>8</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>4</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>23</day>
          <month>10</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Robab Abdolkhani, Kathleen Gray, Ann Borda, Ruth DeSouza. Originally published in JMIR mHealth and uHealth (http://mhealth.jmir.org), 22.01.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 mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://mhealth.jmir.org/2020/1/e15329" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The ubiquity of health wearables and the consequent production of patient-generated health data (PGHD) are rapidly escalating. However, the utilization of PGHD in routine clinical practices is still low because of data quality issues. There is no agreed approach to PGHD quality assurance; therefore, realizing the promise of PGHD requires in-depth discussion among diverse stakeholders to identify the data quality assurance challenges they face and understand their needs for PGHD quality assurance.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This paper reports findings from a workshop aimed to explore stakeholders’ data quality challenges, identify their needs and expectations, and offer practical solutions.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A qualitative multi-stakeholder workshop was conducted as a half-day event on the campus of an Australian University located in a major health care precinct, namely the Melbourne Parkville Precinct. The 18 participants had experience of PGHD use in clinical care, including people who identified as health care consumers, clinical care providers, wearables suppliers, and health information specialists. Data collection was done by facilitators capturing written notes of the proceedings as attendees engaged in participatory design activities in written and oral formats, using a range of whole-group and small-group interactive methods. The collected data were analyzed thematically, using deductive and inductive coding.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The participants’ discussions revealed a range of technical, behavioral, operational, and organizational challenges surrounding PGHD, from the time when data are collected by patients to the time data are used by health care providers for clinical decision making. PGHD stakeholders found consensus on training and engagement needs, continuous collaboration among stakeholders, and development of technical and policy standards to assure PGHD quality.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Assuring PGHD quality is a complex process that requires the contribution of all PGHD stakeholders. The variety and depth of inputs in our workshop highlighted the importance of co-designing guidance for PGHD quality guidance.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>remote sensing technology</kwd>
        <kwd>data quality assurance</kwd>
        <kwd>patient-generated health data</kwd>
        <kwd>wearable devices</kwd>
        <kwd>participatory research</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The health care industry is rapidly moving toward patient-centered care, in which patients actively contribute to their health care [<xref ref-type="bibr" rid="ref1">1</xref>]. An example of a patient-centered care model, remote patient monitoring keeps patients outside the clinical setting while monitoring their health status. In these interventions, patients actively engaged in their health care and played an increasingly important role in sharing responsibilities with health care providers [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      <sec>
        <title>Background</title>
        <p>Health wearables are a key component of remote patient monitoring. These devices have the capability to continuously collect, process, and display health data automatically in real time, which may improve patients’ awareness of their health outside the clinical setting and enhance self-management [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
        <p>Health wearables in the market are of 2 types: medical grade and consumer wearables. Medical wearables are designed to collect data relevant to specific health conditions, such as continuous glucose monitoring (CGM), to monitor blood glucose levels in people with diabetes. However, consumer wearables are often designed to collect general wellness data, such as fitness trackers that are used by patients to be aware of their physical activity level, sleep quality, mood, and heart rate. Some types of wearables connect to an associated mobile app to display real-time processed data, as well as to a patient portal where both patients and health care providers access passive data. Depending on the wearable platform, patients may also be required to manually enter other data types into the mobile app, in addition to the automatic data captured by the sensors in the wearable device.</p>
        <p>Data produced by wearables are usually called patient-generated health data (PGHD), as the data collection relies on patients’ (rather than clinicians’) control and occurs outside the clinical environment [<xref ref-type="bibr" rid="ref4">4</xref>]—a highly complex process. Large volumes of data collected from disparate wearables on an ongoing basis and under various situations bring possibilities for PGHD to be impacted by various technical, behavioral, operational, and organizational issues at the time of storage, transmission, analysis, or access for shared decision making that can lead to poor quality data. For example, wearable dysfunctionality [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref8">8</xref>], inaccurate calibration [<xref ref-type="bibr" rid="ref6">6</xref>], incorrect manual inputs [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref9">9</xref>], complex data visualization [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>], or not collecting data for a period of time [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref12">12</xref>] result in lack of trust in PGHD for clinical decision making. During the PGHD transmission stage, patients may share their data through a home network, their mobile wireless network, or a public wireless network, all of which might affect data transmission [<xref ref-type="bibr" rid="ref5">5</xref>]. In addition, some of the platforms used during PGHD flow operate outside health information systems and may not be trusted because of concerns about their security and data privacy [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. It is still challenging to define and implement solutions for integrating existing data in electronic medical records (EMRs) with PGHD from patients’ own wearables and develop widely accepted interoperability standards for PGHD exchange [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. Moreover, concerns exist regarding consumer wearables, as they are not yet regulated, and there is uncertainty about their promise in achieving the quality required in optimal PGHD collection [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. Regarding human factors, an individual’s intention to use wearables for general wellness tracking or for monitoring a specific health condition can strongly affect the quality of PGHD that these devices collect [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>].</p>
        <p>Health care providers may face large volumes of inaccurate, incomplete, irrelevant, and nonunderstandable PGHD, without solid principles for dealing with these data. The result is concerns about reliability and no confidence in using PGHD in routine clinical practice [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</p>
        <p>These issues of PGHD quality make it difficult to understand PGHD’s usefulness for health care, and these hinder adoption of these data as a systematic part of clinical practices [<xref ref-type="bibr" rid="ref18">18</xref>]. Owing to this, remote patient monitoring is often initiated on a small scale for a short time and focuses on a single disease. A 2018 survey of over 20,000 health care consumers in 28 countries revealed nonsignificant adoption of PGHD [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>There is little evidence in the research and industry literature that the quality of PGHD from wearables is sufficiently well managed to enable them to be trusted as health data or that such data can be used safely and effectively in clinical care. Furthermore, health care organizations lack awareness about PGHD quality from wearable devices [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>Assuring PGHD quality requires efforts not only from health care providers but also from patients, their caregivers, and health consumers in general. Consumers, for example, have different needs from health care providers; therefore, their attitudes toward PGHD will differ, as well as the impact on data quality [<xref ref-type="bibr" rid="ref21">21</xref>]. However, PGHD stakeholders are not limited to consumers and providers; other stakeholders, such as wearable manufacturers, contribute to PGHD transmission from outside the clinical setting, and their activities may similarly impact PGHD quality [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
        <p>Therefore, it is critical to enhance general awareness of the quality of PGHD from wearables.</p>
        <p>The objective of this study was to identify current challenges stakeholders face with various attributes of PGHD quality, define potential solutions to overcome those challenges, and facilitate a process where they could workshop their data quality needs and expectations with other stakeholders.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>We conducted a half-day workshop in May 2019 on the campus of an Australian University located in a major health care precinct. This was part of a larger project using a range of inputs to develop PGHD quality assurance guidance. The workshop received human research ethics approval from the University of Melbourne (Ethics ID: 18532521).</p>
      </sec>
      <sec>
        <title>Participant Recruitment</title>
        <p>Participants were eligible to attend the workshop, who were at least 18 years old and had experience of PGHD use in clinical care, including people who identified as health care consumers, clinical care providers, wearables suppliers, health information specialists, PGHD integration service providers, data analysts, and health service managers. Expressions of interest were sought via an open call and a Web-based registration form distributed via internal and public news and media channels, as well as professional organizations for digital health in Australia. At the point of recruitment or before, as needed, gaps were filled with personal invitations and via snowball sampling, for example, via key contacts in specific organizations where the researchers had existing relationships.</p>
      </sec>
      <sec>
        <title>Participants</title>
        <p>In total, 18 participants took part in the workshop. The participants included 8 health consumers and consumer advocates, 5 clinicians, 3 health information professionals, and 2 wearable and data integration company representatives.</p>
      </sec>
      <sec>
        <title>Workshop Structure</title>
        <sec>
          <title>On-Site Registration</title>
          <p>Each participant was given a package of stationery materials, the consent form, the Plain Language Statement, and a copy of the presentation slides.</p>
        </sec>
        <sec>
          <title>Researcher’s Presentation</title>
          <p>Participants were informed about the workshop purpose and its structure. In addition, findings from previous parts of the project [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref14">14</xref>] were elucidated. The concept of PGHD quality and its 7 aspects—accessibility, accuracy, completeness, consistency, interpretability, relevancy, and timeliness—adapted from a comprehensive data quality framework developed for clinical data quality assurance by the Australian Capital Territory [<xref ref-type="bibr" rid="ref22">22</xref>] were explained through scenarios (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) to enable the participants to identify the various circumstances that might impact each PGHD quality aspect and identify the data management stage in which the quality aspect might require consideration. We used CGM devices as a medical wearable example, and we used fitness trackers as a consumer wearable example in this workshop.</p>
        </sec>
        <sec>
          <title>Group Discussion 1</title>
          <p>The facilitators directed participants into 4 groups, each with a cross section of different stakeholders (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Groups discussed problems related to PGHD quality. Participants contributed verbally, wrote ideas on sticky notes, and placed these on their group worksheet (<xref rid="figure2" ref-type="fig">Figure 2</xref>). A total of 1 facilitator managed each group to direct discussions and assist in timekeeping. Small group discussions ran for 30 min. Thereafter, in a 15-min session, each facilitator took turns presenting to the whole room the consolidated deliberations of the facilitator’s small group. The facilitators wrote the key findings on whiteboards to be available during the break.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Participants’ discussions in 4 groups of patient-generated health data stakeholders.</p>
            </caption>
            <graphic xlink:href="mhealth_v8i1e15329_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Worksheets of patient-generated health data quality problems and ideas.</p>
            </caption>
            <graphic xlink:href="mhealth_v8i1e15329_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Break</title>
          <p>Participants walked around the workshop room to view the discussion findings on whiteboards and exchange further ideas with participants, in preparation for the next part.</p>
        </sec>
        <sec>
          <title>Group Discussion 2</title>
          <p>The facilitators directed participants into 4 differently configured groups. Each group took on a <italic>role</italic> of a key stakeholder—health care consumer, health care provider, health information professional, or wearables manufacturer. Groups discussed and translated their ideas into a set of their expectations of other stakeholder groups, on worksheets (<xref rid="figure3" ref-type="fig">Figure 3</xref>). This task took 30 min, followed by 15 min in which each facilitator set out and spoke to the respective group’s expectations on whiteboards.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Worksheets of patient-generated health data stakeholder’s expectations.</p>
            </caption>
            <graphic xlink:href="mhealth_v8i1e15329_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Conclusion</title>
          <p>The researchers pointed out the outcomes and future work implications. Participants were informed about the next steps of the research project and how they may stay engaged if they are interested.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Collection and Analysis</title>
        <p>Data collection was done by facilitators capturing written notes of the proceedings as attendees engaged in participatory design activities in written and oral formats, using a range of whole-group and small-group interactive methods. The group facilitators’ summing up presentations on boards and sticky notes were photographed. Deductive analysis based on 7 PGHD quality aspects (accessibility, accuracy, completeness, consistency, interpretability, relevancy, and timeliness) and inductive thematic content analysis were used as the primary data analysis methods. The initial data analysis was conducted by the PhD researcher, which was then reviewed by 3 supervisors. Thereafter, all of the 4 researchers discussed the results together in several meetings until consensus was achieved.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>The workshop findings are organized thematically as problems and solutions related to each health data quality dimension, as well as stakeholders’ expectations of each other, to assure PGHD quality.</p>
      <sec>
        <title>Data Quality Challenges and Solutions</title>
        <p><xref ref-type="table" rid="table1">Table 1</xref> illustrates the current problems and potential solutions that mixed-stakeholder small groups raised for each data quality aspect.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Patient-generated health data quality problems and potential solutions.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="238"/>
            <col width="422"/>
            <col width="340"/>
            <thead>
              <tr valign="top">
                <td>Definition</td>
                <td>Problems</td>
                <td>Potential solutions</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Patient-generated health data accessibility (authorized users can access data)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Lack of transparency on who owns the data</p>
                    </list-item>
                    <list-item>
                      <p>Lack of consent for continuous data collection and use</p>
                    </list-item>
                    <list-item>
                      <p>Lack of health consumers’ access to raw data</p>
                    </list-item>
                    <list-item>
                      <p>Data hacking</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Develop data ownership principles</p>
                    </list-item>
                    <list-item>
                      <p>Design notifications in the wearable platform to alert consumers once data are accessed by others</p>
                    </list-item>
                    <list-item>
                      <p>Provide dynamic data authorization</p>
                    </list-item>
                    <list-item>
                      <p>Provide access to raw data by health consumers</p>
                    </list-item>
                    <list-item>
                      <p>Define wearable cybersecurity standards</p>
                    </list-item>
                    <list-item>
                      <p>Create data encryption techniques</p>
                    </list-item>
                    <list-item>
                      <p>Consider privacy in the wearable design</p>
                    </list-item>
                    <list-item>
                      <p>Develop layered consent for various data from different devices</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Accuracy (data are free from errors)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Inaccurate data because of the use of different wearables with different accuracy standard levels</p>
                    </list-item>
                    <list-item>
                      <p>Errors in wearable functionality</p>
                    </list-item>
                    <list-item>
                      <p>Mistakes in manual data entry</p>
                    </list-item>
                    <list-item>
                      <p>Lack of data editing functionalities</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Define accurate levels of measurements</p>
                    </list-item>
                    <list-item>
                      <p>Wearable manufacturers adopt accuracy-related feedback given by consumers and clinicians</p>
                    </list-item>
                    <list-item>
                      <p>Enable data edit functionality in the wearable platforms</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Completeness (there are no data missing)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Lack of access to internet to send the collected data</p>
                    </list-item>
                    <list-item>
                      <p>Battery problems</p>
                    </list-item>
                    <list-item>
                      <p>Incompleteness of data entered manually</p>
                    </list-item>
                    <list-item>
                      <p>Lack of data synchronization during change of time zones</p>
                    </list-item>
                    <list-item>
                      <p>Incompleteness of data because of the wearable dysfunction</p>
                    </list-item>
                    <list-item>
                      <p>Deliberate data omissions</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Design notification to provide an alert for missing data</p>
                    </list-item>
                    <list-item>
                      <p>Consumers’ education and engagement</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Consistency (data from different devices convey the same meaning)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Lack of awareness of data flow and data management</p>
                    </list-item>
                    <list-item>
                      <p>Data inconsistency because of using various wearables with different platforms</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Develop data consistency checking mechanisms to correlate with other data sources</p>
                    </list-item>
                    <list-item>
                      <p>Incorporate data with the clinical workflow</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Interpretability (the data presentation highlights the key message)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Presentation of large volumes of data</p>
                    </list-item>
                    <list-item>
                      <p>Lack of contextual data from consumer wearables to supplement medical wearables data to be easily understood</p>
                    </list-item>
                    <list-item>
                      <p>Data presentations vary among different wearables</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Collect contextual data</p>
                    </list-item>
                  </list>
                  <list list-type="bullet">
                    <list-item>
                      <p>Design standardized data presentation formats for clinicians, despite the variety of wearables used</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Relevancy (the data being collected are pertinent to the standard of care)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Different clinical judgement on data relevancy</p>
                    </list-item>
                    <list-item>
                      <p>Cyberchondria; overthinking of relevancy of collected data to a specific health condition</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Improve health literacy to understand the relevance of data to the standards of care</p>
                    </list-item>
                    <list-item>
                      <p>Provide shared understanding of data relevancy among consumers and clinicians</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Timeliness (up-to-date data are available when needed)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>High volume of unfiltered data to be timely</p>
                    </list-item>
                    <list-item>
                      <p> Lack of consensus among patient-generated health data stakeholders about the definition of timeliness depending on the patient’s status (stable or unstable and at risk)</p>
                    </list-item>
                    <list-item>
                      <p>Wearable design often determines when data are available</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Automation and artificial intelligence to accelerate data filtering so that important data can be available in a timely manner</p>
                    </list-item>
                    <list-item>
                      <p>Enable consumers to take responsibility for deciding when health issues need to be escalated</p>
                    </list-item>
                    <list-item>
                      <p>Design alerts for critical indicators to patients and clinicians</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The findings in <xref ref-type="table" rid="table1">Table 1</xref> show the dynamic situations in which patients collect PGHD through wearables and associated components, including mobile apps and portals. Situations are also subject to various technical, environmental, operational, and behavioral factors. These factors largely involve the design and performance of the wearable platforms, the fragmentation in clinical setting infrastructure to utilize PGHD from disparate wearables, and the stakeholders’ literacy levels in their engagement with PGHD collection and use.</p>
        <p>The participants offered solutions for each PGHD quality attribute, which can be categorized into 5 overall ideas, namely (1) concerning redesign and development of wearables in a way to allow meeting PGHD quality requirements; (2) creation of clinical and administrative policies to address data quality assurance, such as policies on PGHD ownership, standard measurements, and data management policies; (3) stakeholders’ engagement and education; (4) integration of PGHD with clinical workflows and electronic health record systems, which demands creation of terminologies, data exchange protocols, and data analytics; and (5) defining who in the workforce is responsible for PGHD quality assurance procedures.</p>
      </sec>
      <sec>
        <title>Patient-Generated Health Data Stakeholders’ Expectations</title>
        <p>During the second group discussion, participants from each of the 4 stakeholder groups—consumers, clinicians, health information professionals, and wearable manufacturers—stated their expectations of what each of the other PGHD stakeholder groups could do to assure PGHD quality. The groups’ expectations are explained in <xref ref-type="table" rid="table2">Tables 2</xref>-<xref ref-type="table" rid="table5">5</xref>. There were no expectations of health information professionals expressed by consumers and wearable manufacturers.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Consumers’ expectations of other patient-generated health data stakeholder groups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="230"/>
            <col width="770"/>
            <thead>
              <tr valign="top">
                <td>Consumers’ expectations of PGHD<sup>a</sup> stakeholders</td>
                <td>Details</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Clinicians</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Consent:</italic> Consumers expect that clinicians provide informed consent, addressing how consumers and other users can access and use PGHD securely and transparently</p>
                    </list-item>
                    <list-item>
                      <p><italic>Flexibility:</italic> Clinicians are expected to adopt PGHD from new wearable platforms that consumers use and undertake processes to evaluate quality of their data</p>
                    </list-item>
                    <list-item>
                      <p><italic>PGHD collection strategies:</italic> Clinicians can educate consumers on the best practices of PGHD collection and sharing</p>
                    </list-item>
                    <list-item>
                      <p><italic>Collaboration with wearable manufacturers:</italic> Effective collaboration and shared responsibilities among clinicians and wearable manufacturers can lead to clear instructions for consumers in PGHD collection and sharing</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Wearable manufacturers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Code of conduct:</italic> Wearable manufacturers are expected to provide a transparent code of conduct to consumers to identify their rights in using the products</p>
                    </list-item>
                    <list-item>
                      <p><italic>Cost:</italic> Consumers want to access their data from wearable manufacturers for free</p>
                    </list-item>
                    <list-item>
                      <p><italic>Transparency:</italic> Build transparency around the purpose and use of PGHD to enable consumers to have more governance of their data</p>
                    </list-item>
                    <list-item>
                      <p><italic>Person-centered design:</italic> Wearables can be developed on the basis of person-centered care models</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>PGHD: patient-generated health data.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Clinicians’ expectations of other patient-generated health data stakeholder groups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="191"/>
            <col width="809"/>
            <thead>
              <tr valign="top">
                <td>Clinicians’ expectations of PGHD<sup>a</sup> stakeholders</td>
                <td>Details</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Consumers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Trust:</italic> Understanding of PGHD integration into electronic medical records and combination with other clinical data, enhances honesty and enthusiasm among consumers toward the collection of accurate and complete PGHD</p>
                    </list-item>
                    <list-item>
                      <p><italic>Partnership:</italic> Consumers should realize their essential partnership with clinicians in remote patient monitoring. They need to trust their clinicians’ competencies as the first point of decision making for their care</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Health information professionals</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Collaborative participation:</italic> Owing to lack of time and burnout on the clinical staff team, clinicians suggest the involvement of health information professionals to analyze and process PGHD. This step should come before PGHD are made available to the clinicians to provide meaningful information for decision making during the clinical consultation</p>
                    </list-item>
                    <list-item>
                      <p><italic>Data governance:</italic> Health information professionals within health care settings should take part in developing PGHD governance strategies and inform clinicians on the best practices for PGHD use</p>
                    </list-item>
                    <list-item>
                      <p><italic>Consumer wearable evaluation:</italic> Health information professionals can assess the contextual data provided by consumer wearables and inform clinicians on PGHD quality from these devices</p>
                    </list-item>
                    <list-item>
                      <p><italic>Technical infrastructure development:</italic> Health information professionals can potentially invest in appropriate information technology infrastructure that enables PGHD integration with electronic medical record systems at scale</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Wearable manufacturers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Dynamic wearable testing:</italic> Need for routine device testing and to collaborate with clinicians to develop strategies for continuous wearable assessment through various clinical studies</p>
                    </list-item>
                    <list-item>
                      <p><italic>Integrity with standards of care:</italic> Wearables should be exclusively designed for the intended purpose of use, and they should align with the standards of care in health care settings</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>PGHD: patient-generated health data.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Health information professionals’ expectations of other patient-generated health data stakeholder groups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="301"/>
            <col width="699"/>
            <thead>
              <tr valign="top">
                <td>Health information professionals’ expectations of PGHD<sup>a</sup> stakeholders</td>
                <td>Details</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Consumers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Consistent data sharing:</italic> Consumers can discuss their preferred wearables and associated platforms with the remote monitoring team to identify ways to share PGHD consistently.</p>
                    </list-item>
                    <list-item>
                      <p><italic>Data sharing authorization:</italic> consumers are expected to authorize their data to be shared.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Clinicians</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>PGHD incorporation with other clinical data:</italic> Clinicians can help in incorporating PGHD with other clinical data, as part of the patient record.</p>
                    </list-item>
                    <list-item>
                      <p><italic>Digital health literacy:</italic> Clinicians are expected to undertake training on PGHD and wearable use.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Wearable manufacturers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Data exchange standards:</italic> Wearable manufacturers should develop devices that comply with defined data exchange standards in health care settings.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>PGHD: patient-generated health data.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Health wearables’ manufacturers’ expectations of other patient-generated health data stakeholder groups.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="313"/>
            <col width="687"/>
            <thead>
              <tr valign="top">
                <td>Health wearables’ manufacturers’ expectations of PGHD<sup>a</sup> stakeholders</td>
                <td>Details</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Consumers</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>Wearable usability feedback:</italic> Consumers are expected to provide continuous feedback about the technical and operational issues they face in the duration of PGHD use.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Clinicians</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p><italic>New wearables adoption:</italic> Clinicians should be less afraid to try new technologies and test various wearables via trials.</p>
                    </list-item>
                    <list-item>
                      <p><italic>Collaboration:</italic> Clinicians should expand relationships with wearable manufacturers and be open to conduct research to evaluate the wearables.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>PGHD: patient-generated health data.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Current health data quality assurance approaches are now disrupted by PGHD challenges. Given the potential value of PGHD in health care decision support, their adoption requires an in-depth understanding of data quality.</p>
        <p>The investigation of PGHD quality is in its infancy, and few studies have explored it [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Therefore, our workshop provided the participants with an opportunity to carefully investigate PGHD quality in future remote patient monitoring interventions. It was acknowledged by the participants that the process of thinking about PGHD quality and translating into solutions could enhance collaboration among PGHD stakeholders, within and outside clinical settings.</p>
      </sec>
      <sec>
        <title>Diversity of Patient-Generated Health Data Quality Challenges and Potential Solutions</title>
        <p>Mixed-stakeholder participant groups raised divergent problems of PGHD quality. Technical factors related to wearable design and functionality affect most of the aforementioned aspects of data quality at the PGHD collection stage. The participants recognized that a cohesive platform to integrate PGHD with current EMR systems has the potential to collect automatic and manual data entries from various wearables and associated apps, to ideally facilitate dynamic data transmission. However, more practically, operational and organizational problems are likely to occur during data transmission from the patient to the clinical setting, such as internet access, time zone, distinct data transfer protocols, and lack of data integration. Behavioral habits of consumers, as well as digital health literacy among key PGHD stakeholders, such as consumers and clinicians, are among the factors that participants identified, which can influence PGHD quality. The participant discussions further highlighted the need to create a patient-centered care model that includes defined technical standards, policies, rights, and responsibilities to ensure PGHD quality and make these data useful for clinical care.</p>
      </sec>
      <sec>
        <title>Convergence in Patient-Generated Health Data Stakeholders’ Expectations</title>
        <p>The 4 groups of PGHD stakeholders in our workshop raised different expectations about each of the other stakeholders, whereas all participants reached consensus on the importance of promoting collaboration among stakeholders. Furthermore, participants emphasized the need for transparency on the redistribution of tasks and responsibilities given to consumers, as well as to the clinicians. Participants also stated that wearables should be designed in a way to reconcile the needs of both patients and clinicians. Another key discussion point focused on hearing the consumer’s voice in improving PGHD collection. Without this voice, it may result in the consumer’s lack of understanding on how to optimally contribute to PGHD collection and management processes, thus leading to poor quality data.</p>
        <p>The scope of remote monitoring services is still limited to single programs for single diseases, and it has not yet broadened to multiple health conditions. Moreover, in current remote monitoring scenarios, PGHD flow mainly occurs among consumers, clinicians, and wearable manufacturers, without further actions entering EMR systems or without the involvement of other specialist clinical or nonclinical staff. Presently, health information professionals within clinical settings are not full participants in the PGHD process, primarily because of the lack of integrated infrastructure, which could optimally incorporate PGHD into the health care system. This particular gap points to the need to broaden the team of stakeholders involved in the process and better define tasks for ensuring PGHD quality across the flow.</p>
        <p>Critically, there was consensus by the stakeholder groups that PGHD management should occur in a standardized way. Different types of PGHD could become part of clinical terminology standards, made possible through national efforts. For example, specific metadata could be standardized to codify patients as source data generators.</p>
      </sec>
      <sec>
        <title>Relation to Other Works</title>
        <p>As stated, there is a paucity of research investigating PGHD quality for use in routine clinical practice [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. This study included a wider range of PGHD stakeholders: consumers, clinicians, and wearable vendors, as well as health information professionals whose roles in PGHD management and quality assurance have not been investigated in previous research.</p>
        <p>This is the first study of its kind, which brings various groups of PGHD stakeholders together to share their concerns and expectations with each other, with regard to ensuring PGHD quality. This process helped to reach a consensus among participants on clear responsibilities they could take to effectively collaborate for better patient care.</p>
      </sec>
      <sec>
        <title>Limitations and Future Work</title>
        <p>The workshop participants were not representing an exhaustive range of PGHD stakeholders to explore quality issues from other perspectives. Further stages of this project will involve more groups of stakeholders. The workshop was focused on PGHD quality assurance for primary use of data, which falls within clinical care. Therefore, quality issues around secondary use of PGHD, such as utilization of PGHD in biomedical research, shared care plans, and mobile health surveillance, were not discussed.</p>
        <p>In addition, the full spectrum of consumer and medical wearables was not represented among the participants. We purposely chose CGM devices as a medical wearable example, and we chose fitness trackers as a consumer wearable example in this workshop. CGM wearables are complex devices that require both automatic and manual data entry, calibration by using conventional glucometers, and a reliable connection to mobile apps and patient portals. Patients may also need to collect lifestyle data from consumer wearables, beside the CGM data, to provide a more comprehensive picture of their health status to their clinicians.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study used a participatory research method to identify (1) the problems of PGHD quality, (2) potential solutions to overcome the challenges, and (3) the PGHD stakeholders’ expectations toward PGHD quality assurance. Our approach to codevelop challenges, solutions, and expectations enabled us to engage various stakeholders to jointly share experience and concerns. Active and continuous collaboration among PGHD stakeholders, from wearable development to data production and use in patient care, is vital not only to ensure the quality of the data but also the quality of the consumer’s health care experience and clinical outcomes. The findings from this workshop will contribute to the development of practical recommendations toward PGHD quality assurance, which can be adopted by a wide range of PGHD stakeholders.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Workshop presentation slides.</p>
        <media xlink:href="mhealth_v8i1e15329_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 22245 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CGM</term>
          <def>
            <p>continuous glucose monitoring</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PGHD</term>
          <def>
            <p>patient-generated health data</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors wish to thank all the participants for their valuable time and contribution. The authors wish to especially thank Ms Cecily Gilbert, a research assistant, and Mr Gerardo Luis Dimaguila, a PhD student, at Health and Biomedical Informatics Centre at the University of Melbourne for their help in facilitating the workshop.</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="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Santana</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenzetti</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jolley</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Manalili</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zelinsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Quan</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Measuring patient-centred system performance: a scoping review of patient-centred care quality indicators</article-title>
          <source>BMJ Open</source>
          <year>2019</year>
          <month>01</month>
          <day>7</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e023596</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://bmjopen.bmj.com/cgi/pmidlookup?view=long&#38;pmid=30617101"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2018-023596</pub-id>
          <pub-id pub-id-type="medline">30617101</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2018-023596</pub-id>
          <pub-id pub-id-type="pmcid">PMC6326310</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>World Health Organisation</collab>
          </person-group>
          <article-title>Chronic disease management and remote patient monitoring</article-title>
          <source>Eurohealth</source>
          <year>2009</year>
          <volume>15</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.lse.ac.uk/lse-health/assets/documents/eurohealth/issues/eurohealth-v15n1.pdf"/>
          </comment>
        </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>Vegesna</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tran</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Angelaccio</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Arcona</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Remote patient monitoring via non-invasive digital technologies: a systematic review</article-title>
          <source>Telemed J E Health</source>
          <year>2017</year>
          <month>01</month>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27116181"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/tmj.2016.0051</pub-id>
          <pub-id pub-id-type="medline">27116181</pub-id>
          <pub-id pub-id-type="pmcid">PMC5240011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shapiro</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Johnston</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wald</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mon</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>HealthIT</source>
          <year>2012</year>
          <access-date>2019-11-19</access-date>
          <comment>Patient-generated Health Data: White Paper Prepared for the Office of the National Coordinator for Health IT by RTI International 2012. <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/rti_pghd_whitepaper_april_2012.pdf">https://www.healthit.gov/sites/default/files/rti_pghd_whitepaper_april_2012.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sriram</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kotz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rajan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sastry</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yarvis</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Challenges in data quality assurance in pervasive health monitoring systems</article-title>
          <source>Future of Trust in Computing</source>
          <year>2009</year>
          <publisher-loc>Wiesbaden</publisher-loc>
          <publisher-name>Vieweg+Teubner</publisher-name>
          <fpage>129</fpage>
          <lpage>42</lpage>
        </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>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>DeSouza</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Patient-generated health data management and quality challenges in remote patient monitoring</article-title>
          <source>JAMIA Open</source>
          <year>2019</year>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1093/jamiaopen/ooz036"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooz036</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>Chung</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Dew</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cole</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zia</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fogarty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kientz</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Munson</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Boundary negotiating artifacts in personal informatics: patient-provider collaboration with patient-generated data</article-title>
          <source>CSCW Conf Comput Support Coop Work</source>
          <year>2016</year>
          <month>12</month>
          <day>27</day>
          <volume>2016</volume>
          <fpage>770</fpage>
          <lpage>86</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28516171"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/2818048.2819926</pub-id>
          <pub-id pub-id-type="medline">28516171</pub-id>
          <pub-id pub-id-type="pmcid">PMC5432205</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>West</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kleek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shadbolt</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>The Quantified Patient in the Doctor's Office: Challenges &#38; Opportunities</article-title>
          <source>Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems</source>
          <year>2016</year>
          <conf-name>CHI'16</conf-name>
          <conf-date>May 7 - 12, 2016</conf-date>
          <conf-loc>San Jose, California, USA</conf-loc>
          <fpage>3066</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.1145/2858036.2858445</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>Zhu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Colgan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Choe</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Sharing patient-generated data in clinical practices: an interview study</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2016</year>
          <volume>2016</volume>
          <fpage>1303</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28269928"/>
          </comment>
          <pub-id pub-id-type="medline">28269928</pub-id>
          <pub-id pub-id-type="pmcid">PMC5333267</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>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="ref11">
        <label>11</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Puentes</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Montagner</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lecornu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lähteenmäki</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bali</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Troshani</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Goldberg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wickramasinghe</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Quality analysis of sensors data for personal health records on mobile devices</article-title>
          <source>Pervasive Health Knowledge Management</source>
          <year>2013</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>103</fpage>
          <lpage>33</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hernández</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Favela</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Michán</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Arnrich</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zomaya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abbas</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Data quality in mobile sensing datasets for pervasive healthcare</article-title>
          <source>Handbook of Large-Scale Distributed Computing in Smart Healthcare</source>
          <year>2017</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>217</fpage>
          <lpage>38</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>West</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>van Kleek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Weal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shadbolt</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Information quality challenges of patient-generated data in clinical practice</article-title>
          <source>Front Public Health</source>
          <year>2017</year>
          <volume>5</volume>
          <fpage>284</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fpubh.2017.00284"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpubh.2017.00284</pub-id>
          <pub-id pub-id-type="medline">29209601</pub-id>
          <pub-id pub-id-type="pmcid">PMC5701635</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Cummings</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schaper</surname>
              <given-names>L</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>Connecting the System to Enhance the Practitioner and Consumer Experience in Healthcare</source>
          <year>2018</year>
          <publisher-loc>Amsterdam, Netherlands</publisher-loc>
          <publisher-name>Ios Press</publisher-name>
        </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>Codella</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Partovian</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Data quality challenges for person-generated health and wellness data</article-title>
          <source>IBM J Res Dev</source>
          <year>2018</year>
          <volume>62</volume>
          <issue>1</issue>
          <fpage>3:1</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/8269766"/>
          </comment>
          <pub-id pub-id-type="doi">10.1147/jrd.2017.2762218</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <source>HealthIT</source>
          <year>2018</year>
          <month>01</month>
          <access-date>2019-11-19</access-date>
          <comment>Conceptualizing a Data Infrastructure for the Capture, Use, and Sharing of Patient-generated Health Data in Care Delivery and Research Through 2024. <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/onc_pghd_practical_guide.pdf">https://www.healthit.gov/sites/default/files/onc_pghd_practical_guide.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <source>HIMSS Media</source>
          <access-date>2019-11-19</access-date>
          <comment>Healthcare Coaching: Multiplying the Value of Wearables and Patient-generated Health Data 2018. <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://2nwchq3a3ags2kj7bq20e3qv-wpengine.netdna-ssl.com/wp-content/uploads/FINAL_HIMSS_FitBit_WP_10.01.20181.pdf">https://2nwchq3a3ags2kj7bq20e3qv-wpengine.netdna-ssl.com/wp-content/uploads/FINAL_HIMSS_FitBit_WP_10.01.20181.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>West</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>van Kleek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Weal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shadbolt</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Common Barriers to the Use of Patient-Generated Data Across Clinical Settings</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.3174058</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <source>Ipsos Healthcare</source>
          <year>2018</year>
          <month>10</month>
          <day>31</day>
          <access-date>2019-11-19</access-date>
          <comment>Connected Health Trends 2018. <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ipsos.com/en/connected-health-trends-2018">https://www.ipsos.com/en/connected-health-trends-2018</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Piwek</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ellis</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Andrews</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Joinson</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The rise of consumer health wearables: promises and barriers</article-title>
          <source>PLoS Med</source>
          <year>2016</year>
          <month>02</month>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>e1001953</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pmed.1001953"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pmed.1001953</pub-id>
          <pub-id pub-id-type="medline">26836780</pub-id>
          <pub-id pub-id-type="pii">PMEDICINE-D-15-00616</pub-id>
          <pub-id pub-id-type="pmcid">PMC4737495</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bansler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kensing</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Moll</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Alignment of Concerns: A Design Rationale for Patient Participation in eHealth</article-title>
          <source>2014 47th Hawaii International Conference on System Sciences</source>
          <year>2014</year>
          <conf-name>HICSS'14</conf-name>
          <conf-date>January 6-9, 2014</conf-date>
          <conf-loc>Waikoloa, HI, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/hicss.2014.327</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <source>ACT Health</source>
          <comment>Data Quality Frameworknterprise Business Intelligence Solutions. <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://health.act.gov.au/sites/default/files/Policy_and_Plan/Data%20Quality%20Framework.pdf">http://health.act.gov.au/sites/default/files/Policy_and_Plan/Data%20Quality%20Framework.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
