<?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">v9i12e31618</article-id>
      <article-id pub-id-type="pmid">34941540</article-id>
      <article-id pub-id-type="doi">10.2196/31618</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>Identifying Data Quality Dimensions for Person-Generated Wearable Device Data: Multi-Method Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Buis</surname>
            <given-names>Lorraine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Burns</surname>
            <given-names>Kara</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Sagi</surname>
            <given-names>Tomer</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Cho</surname>
            <given-names>Sylvia</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Biomedical Informatics</institution>
            <institution>Columbia University</institution>
            <addr-line>622 West 168th Street PH20</addr-line>
            <addr-line>New York, NY, 10032</addr-line>
            <country>United States</country>
            <phone>1 212 305 5334</phone>
            <email>sc3901@cumc.columbia.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0263-0343</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Weng</surname>
            <given-names>Chunhua</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9624-0214</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Kahn</surname>
            <given-names>Michael G</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4786-6875</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Natarajan</surname>
            <given-names>Karthik</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9066-9431</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Biomedical Informatics</institution>
        <institution>Columbia University</institution>
        <addr-line>New York, NY</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Pediatrics</institution>
        <institution>University of Colorado Anschutz Medical Campus</institution>
        <addr-line>Aurora, CO</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Sylvia Cho <email>sc3901@cumc.columbia.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>12</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>12</month>
        <year>2021</year>
      </pub-date>
      <volume>9</volume>
      <issue>12</issue>
      <elocation-id>e31618</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>6</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>28</day>
          <month>8</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>27</day>
          <month>9</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>11</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Sylvia Cho, Chunhua Weng, Michael G Kahn, Karthik Natarajan. Originally published in JMIR mHealth and uHealth (https://mhealth.jmir.org), 23.12.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on https://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://mhealth.jmir.org/2021/12/e31618" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>There is a growing interest in using person-generated wearable device data for biomedical research, but there are also concerns regarding the quality of data such as missing or incorrect data. This emphasizes the importance of assessing data quality before conducting research. In order to perform data quality assessments, it is essential to define what data quality means for person-generated wearable device data by identifying the data quality dimensions.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to identify data quality dimensions for person-generated wearable device data for research purposes.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>This study was conducted in 3 phases: literature review, survey, and focus group discussion. The literature review was conducted following the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) guideline to identify factors affecting data quality and its associated data quality challenges. In addition, we conducted a survey to confirm and complement results from the literature review and to understand researchers’ perceptions on data quality dimensions that were previously identified as dimensions for the secondary use of electronic health record (EHR) data. We sent the survey to researchers with experience in analyzing wearable device data. Focus group discussion sessions were conducted with domain experts to derive data quality dimensions for person-generated wearable device data. On the basis of the results from the literature review and survey, a facilitator proposed potential data quality dimensions relevant to person-generated wearable device data, and the domain experts accepted or rejected the suggested dimensions.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>In total, 19 studies were included in the literature review, and 3 major themes emerged: device- and technical-related, user-related, and data governance–related factors. The associated data quality problems were incomplete data, incorrect data, and heterogeneous data. A total of 20 respondents answered the survey. The major data quality challenges faced by researchers were completeness, accuracy, and plausibility. The importance ratings on data quality dimensions in an existing framework showed that the dimensions for secondary use of EHR data are applicable to person-generated wearable device data. There were 3 focus group sessions with domain experts in data quality and wearable device research. The experts concluded that intrinsic data quality features, such as conformance, completeness, and plausibility, and contextual and fitness-for-use data quality features, such as completeness (breadth and density) and temporal data granularity, are important data quality dimensions for assessing person-generated wearable device data for research purposes.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>In this study, intrinsic and contextual and fitness-for-use data quality dimensions for person-generated wearable device data were identified. The dimensions were adapted from data quality terminologies and frameworks for the secondary use of EHR data with a few modifications. Further research on how data quality can be assessed with respect to each dimension is needed.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>patient-generated health data</kwd>
        <kwd>data accuracy</kwd>
        <kwd>data quality</kwd>
        <kwd>wearable device</kwd>
        <kwd>fitness trackers</kwd>
        <kwd>qualitative research</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Use of Person-Generated Wearable Device Data for Research Purposes</title>
        <p>The growing interest in quantified self along with the routine use of consumer wearables is generating substantial amounts of person-generated wearable device data [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. These passively and objectively collected data hold great potential for use in biomedical research as they capture data that occur outside the clinic, without having to rely on patient recall [<xref ref-type="bibr" rid="ref3">3</xref>]. An example of using wearable device data for biomedical research is a study by Lim et al [<xref ref-type="bibr" rid="ref4">4</xref>] in which consumer-grade fitness tracker data (Fitbit Charge HR) was used along with survey and electronic health record (EHR) data. In addition, wearable device data can be reused in multiple studies to answer many different research questions. The investigators of the Lim et al [<xref ref-type="bibr" rid="ref4">4</xref>] study made their data publicly available for other researchers, expanding the opportunity to generate and validate medical evidence. McDonald et al [<xref ref-type="bibr" rid="ref5">5</xref>] used these data to investigate the relationship between sleep time and BMI in a Chinese population. This study was conducted to confirm the results of Xu et al [<xref ref-type="bibr" rid="ref6">6</xref>], who examined the relationship between sleep duration and BMI. One of the limitations of the Xu et al [<xref ref-type="bibr" rid="ref6">6</xref>] study was that their data primarily consisted of Europeans, and thus the study results needed further investigation to be generalizable. McDonald et al [<xref ref-type="bibr" rid="ref5">5</xref>] added further evidence to the association between sleep and BMI by examining the same research question using a data set comprising Asian individuals. This type of evidence generation is expected to become more widespread with the All of Us Research Program, a precision medicine initiative by the National Institutes of Health, which is collecting, integrating, and providing wearable device data (eg, Fitbit) to the public for research purposes [<xref ref-type="bibr" rid="ref7">7</xref>]. Considering that there is a lack of publicly available data sets generated from consumer wearable devices with a large number of participants and long-term observation, the All of Us data are expected to become a promising resource for many researchers interested in analyzing wearable device data.</p>
      </sec>
      <sec>
        <title>Significance of Data Quality Assessment</title>
        <p>Although person-generated wearable device data are a promising new source of biomedical data, there are concerns regarding the quality of data. For example, missing data owing to users not wearing the device or incorrect data owing to device malfunction are a few data quality problems that could occur [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. As these data anomalies could lead to various challenges when analyzing wearable device data, data quality assessment is a critical step that should be implemented before any analyses [<xref ref-type="bibr" rid="ref8">8</xref>]. In this setting, data quality assessment is not only about whether the wearable device captures valid and reliable data but also whether a data set is fit-for-use for a specific research purpose, ensuring valid results [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. However, the question about what data quality means, more specifically, how data quality is defined for the use of person-generated wearable device data for research purposes still remains.</p>
      </sec>
      <sec>
        <title>Data Quality Dimensions</title>
        <p>Data quality dimensions are criteria or aspects of data quality that are considered essential for a specific user’s task and are constructs used when assessing data [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. For example, the quality of data could be assessed in terms of its completeness (“Are data values present?”), conformance (“Do data values adhere to specified standards and formats?”), and plausibility (“Are data values believable?”) [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Various methods have been previously used to derive the data quality dimensions for biomedical data sets. First, Weiskopf et al [<xref ref-type="bibr" rid="ref13">13</xref>] and Johnson et al [<xref ref-type="bibr" rid="ref15">15</xref>] used systematic reviews to derive data quality dimensions. They both abstracted data quality attributes from studies on EHR data quality and then derived broad dimensions of data quality [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Second, stakeholder meetings are another method used by Kahn et al [<xref ref-type="bibr" rid="ref14">14</xref>]. Stakeholders reviewed the literature on data quality, publications on best practices, operational manuals, and data quality rules from several EHR-based research networks. Data quality terms were then integrated into categories through an iterative process [<xref ref-type="bibr" rid="ref14">14</xref>]. Finally, surveys have also been used as a method to identify data quality dimensions [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. For example, Huang et al [<xref ref-type="bibr" rid="ref17">17</xref>] investigated important data quality dimensions for genome annotation by asking genomic researchers to rank the importance of 17 data quality dimensions. The strength of these empirical methods is that it captures the perspective of data users and reveals data quality dimensions that may not have been considered by data quality researchers [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. This is important as data quality is a concept that depends on the data users and their research tasks.</p>
        <p>Currently, there is a lack of studies that derive dimensions for person-generated wearable device data using empirical methods. To our knowledge, the study by Codella et al [<xref ref-type="bibr" rid="ref19">19</xref>] is the most relevant study on data quality dimensions for person-generated wearable device data. The study [<xref ref-type="bibr" rid="ref19">19</xref>] first reviewed the literature to identify stakeholders’ concerns regarding person-generated health data (PGHD) and mapped the concerns to the corresponding data quality dimensions in the Wang and Strong [<xref ref-type="bibr" rid="ref16">16</xref>] framework. However, the Wang and Strong [<xref ref-type="bibr" rid="ref16">16</xref>] framework was derived by surveying business data consumers, which might not include important data quality dimensions for PGHD. Therefore, there is a great need to investigate the essential challenges and dimensions for assessing the quality of person-generated wearable device data for biomedical research because it is a growing, new data type.</p>
      </sec>
      <sec>
        <title>Objective</title>
        <p>The aim of this study is to identify important data quality dimensions for using person-generated wearable device data for research purposes. The focus of this study is on intrinsic (data quality features inherent to the data) and contextual and fitness-for-use data quality dimensions (features that are task-dependent). Extrinsic and operational data quality features, such as data accessibility, security, or privacy, are not the focus of this study.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>Owing to the lack of literature or experts in the data quality field for person-generated wearable device data, a multi-method approach was used to complement and validate information found by each method. A combination of literature review and survey was used to improve reliability through constant data comparison [<xref ref-type="bibr" rid="ref20">20</xref>]. In addition, focus group discussions were conducted to derive data quality dimensions from the collected data.</p>
      </sec>
      <sec>
        <title>Part 1: Literature Review</title>
        <p>The goal of the literature review was to identify (1) factors affecting the quality of person-generated wearable device data and (2) associated intrinsic data quality challenges that could potentially occur when conducting research. Studies were examined from scholarly databases using a combination of search terms related to data quality and wearable devices. One reviewer (SC) screened the titles and abstracts of the studies based on a set of selection criteria. For example, studies containing any content on the data quality of wearable device data or sensor data when used for research purposes were included, but studies on clinicians wearing devices for patient care were excluded because the focus was on person-generated data being used for research purposes. The full text was screened using the same criteria by 2 reviewers (SC and KN). Sentences on data quality challenges and factors affecting those challenges were annotated, and semantically similar challenges and factors were grouped into the same category. The categorization process was performed by 3 researchers (SC, KN, and Ipek Ensari), including the 2 reviewers (SC and KN). Details of the literature review process are described in a previously published manuscript [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      </sec>
      <sec>
        <title>Part 2: Survey</title>
        <sec>
          <title>Survey Development</title>
          <p>The survey was developed with a mixture of multiple-choice, open-ended, and Likert-type scale questions. The survey was iteratively refined based on feedback from 6 experts—3 in data quality, 2 in wearable devices, and 1 in survey development. The experts were recruited through the professional network of the research team, and the experts were those who actively conducted research in either data quality, wearable devices, or survey development. A web-based survey was created using Qualtrics (Qualtrics; version August 2019), which is a web-based survey software [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        </sec>
        <sec>
          <title>Data Collection and Analysis</title>
          <p>The eligibility criteria for survey participation included the following: (1) an individual with experience in analyzing passively collected wearable device data for their research and (2) an individual with knowledge of data quality challenges when dealing with wearable device data. Potential survey participants were identified by searching the authors of research studies that used wearable device data and through referrals. The survey link was sent via email to the candidate respondents. In addition, a link to the survey was posted on the Observational Health Data Sciences and Informatics forum [<xref ref-type="bibr" rid="ref22">22</xref>]. This forum was chosen because it focuses on observational health data, and individuals with diverse research backgrounds including PGHD and data quality frequently visit the forum. Participation was voluntary, and the survey was self-administered and anonymous.</p>
          <p>Answers to multiple-choice questions were analyzed using descriptive statistics, and thematic analysis was conducted to identify themes from answers to open-ended questions. Responses to Likert-type scale questions were analyzed by comparing mean (importance of the dimensions) with SD (reliability) of the importance ratings of the dimensions. Dimensions with high mean (importance) and low SD (less variability in ratings among respondents) were determined as important.</p>
        </sec>
      </sec>
      <sec>
        <title>Part 3: Focus Group Discussion</title>
        <p>Domain experts in data quality or wearable device data were recruited through a professional network of authors. The facilitator (SC) combined the results of the literature review and survey and proposed potential dimensions to domain experts. Domain experts discussed the information provided and determined whether to accept or reject the suggested data quality dimensions. The importance ratings on dimensions in the harmonized intrinsic data quality framework (HIDQF) were also used as a reference to determine its relevance to wearable device data [<xref ref-type="bibr" rid="ref14">14</xref>]. The discussion continued until consensus was reached among the experts.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>An overview of the results is depicted in <xref rid="figure1" ref-type="fig">Figure 1</xref> followed by further details regarding the results.</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>An overview of study processes and results. HIDQF: harmonized intrinsic data quality framework.</p>
        </caption>
        <graphic xlink:href="mhealth_v9i12e31618_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <sec>
        <title>Part 1: Literature Review</title>
        <p>In total, 1290 studies were retrieved and screened, resulting in 1.47% (19/1290) studies being selected for analysis. Data extracted from the studies were categorized into 3 groups of factors affecting data quality, that is, device- and technical-related, user-related, and data governance–related factors, and 3 data quality challenges, that is, incompleteness, incorrectness, and heterogeneity. Most studies have discussed device- and human-related factors that influence data quality. For example, device malfunction, network and connectivity, and users not wearing the device can lead to incomplete or missing data, whereas poor quality of sensor or algorithms and users’ incorrect use of the device may lead to incorrect data. In addition, lack of data standardization, such as different data formats, measurement units, and different algorithms, for the same parameter may cause difficulty in making a direct comparison between data from different devices. The full results of the literature review have been published [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      </sec>
      <sec>
        <title>Part 2: Survey</title>
        <sec>
          <title>Survey Design and Participant Recruitment</title>
          <p>The survey was designed in 3 parts: (1) questions on the respondents’ research background, (2) questions on the research that the participants have conducted, and (3) questions on participants’ perception and knowledge of data quality. The survey included a Likert-type scale question that asked to rate the data quality dimensions from the HIDQF regarding their importance [<xref ref-type="bibr" rid="ref14">14</xref>]. The HIDQF harmonizes 9 existing data quality terminologies and frameworks that are applicable to the secondary use of EHR data [<xref ref-type="bibr" rid="ref14">14</xref>]. The harmonized framework involved a consensus among various stakeholders and experts in data quality; thus, it made sense to leverage the framework as a basis for the data quality dimensions of wearable devices. The full survey can be found in the link cited in the reference [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
          <p>Emails were sent out to 100 researchers from August 2019 to September 2019. The exact number of survey recipients is unknown because the email recipients forwarded the email to other eligible individuals, and the survey was posted on a public online forum. In total, 20 responses were collected—most respondents were from the United States, but there were also a few respondents from the United Kingdom, France, and Singapore. Using 100 as a proxy for the number of eligible researchers, there was a 20% (20/100) response rate for the survey.</p>
        </sec>
        <sec>
          <title>Background of Respondents</title>
          <p><xref ref-type="table" rid="table1">Table 1</xref> shows the background of the survey respondents based on the responses collected from part 1 and part 2 of the survey.</p>
          <p>Most respondents published 1-3 peer-reviewed articles (12/20, 60%), and 3 respondents (3/20, 15%) published &#62;10 articles. The most common types of studies previously conducted by respondents were device validation or reliability studies (11/20, 55%), modeling to predict health state (10/20, 50%), and tracking behavioral changes (8/20, 40%). Other research types, such as pattern analysis on activity data and tracking body movement or stress, were also mentioned.</p>
          <p>Nearly half of the respondents (9/20, 45%) used research-grade and consumer-grade devices with similar frequency, and 8 respondents (8/20, 40%) had only used consumer-grade devices. The respondents gave multiple answers regarding the brand and model of the devices they had used before. Among consumer-grade devices, the most frequently mentioned brand was Fitbit (19/20, 95%), followed by Garmin, Withings, Jawbone, and Apple Watch. Research-grade devices, especially accelerometers, such as ActiGraph, GENEactiv, and Actical, were mentioned 6 times. Other devices were mentioned, such as the Huawei Watch 2, Samsung Gear 2, and Misfit Shine 2.</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Background of respondents (N=20).</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="700"/>
              <col width="270"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Characteristic</td>
                  <td>Value</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Number of peer-reviewed articles using wearable device data, n (%)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>None</td>
                  <td>1 (5)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>1 to 3</td>
                  <td>12 (60)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>3 to 5</td>
                  <td>2 (10)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>5 to 10</td>
                  <td>2 (10)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>10 or more</td>
                  <td>3 (15)</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Type of research conducted (multiple choice possible), n (%)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Device validation or reliability studies</td>
                  <td>11 (55)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Modeling to predict health state</td>
                  <td>10 (50)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Modeling to inform treatment decisions</td>
                  <td>2 (10)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Tracking behavioral changes</td>
                  <td>8 (40)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Other</td>
                  <td>3 (15)</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Type of devices used for research, n (%)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consumer-grade wearable</td>
                  <td>8 (40)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Research-grade wearable</td>
                  <td>3 (15)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Used both with similar frequency</td>
                  <td>9 (45)</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Brand of devices used (multiple choice possible), n (%)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Fitbit (Charge HR, Alta HR, Ultra, etc)</td>
                  <td>19 (95)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Garmin (Vivofit, Vivosmart, Fenix, etc)</td>
                  <td>6 (30)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Withings (Go, Pulse, or BP cuff)</td>
                  <td>4 (20)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Jawbone (UP)</td>
                  <td>2 (10)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Apple Watch</td>
                  <td>1 (5)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accelerometer (ActiGraph, GENEactiv, etc)</td>
                  <td>6 (30)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Other (Huawei, Samsung gear, Misfit, etc)</td>
                  <td>14 (70)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Data Quality Challenges</title>
          <p>In total 3 main themes and 1 minor issue were derived from the open-ended question on data quality challenges: (1) completeness, (2) accuracy, (3) plausibility, and (4) data access and semantics.</p>
          <sec>
            <title>Completeness</title>
            <p>One of the major themes was the completeness. Missing data were a concern for the respondents because of the uncertainty involved in dealing with missingness as it can have a negative effect on the analysis results. Many respondents wrote about missing data caused by various reasons, such as device error or users not wearing devices, which aligns with the results from the literature review. One respondent specifically talked about a different aspect of missing data, which is the lack of a certain variable that they needed for their research (<italic>“</italic>Lack of availability of heart rate variability<italic>”</italic>).</p>
          </sec>
          <sec>
            <title>Accuracy</title>
            <p>Another major theme was accuracy—<italic>Do the data represent the true value?</italic> Respondents talked about their doubts about whether the data correctly capture the true physiological measure they are supposed to represent. For example, steps might not be counted if one does not wear the device during exercise owing to discomfort. On the other hand, other activities, such as motorcycle rides, could falsely increase the step counts. In addition, a respondent mentioned the problem of GPS devices only recording known locations rather than the actual route, affecting distance traveled. There could also be inaccuracies in the sleep data. For instance, activities that are performed while lying on the bed (eg, using phones) could be counted as sleep mode, and sleep or wake time could be recognized inaccurately. These concerns match the challenges found in the literature review.</p>
          </sec>
          <sec>
            <title>Plausibility</title>
            <p>Plausibility was another major theme—<italic>Do the data make sense?</italic> One of the issues mentioned was that the data did not agree with their common knowledge. For example, there are problems in inconsistency between variables (“large spikes or drops in activity that are highly inconsistent with their surrounding measured values”). Respondents also stated that outliers in the data made them question the validity of that data point (“knowing whether unusual data are real”).</p>
            <p>There were also time-related plausibility issues. For example, even though the data for 2 different variables are captured at the same time, the recorded timestamp on the server could be different between the 2 variables because of problems with data upload (“lag between device and data server—some variables are collected at slightly different time due to problems with wifi connection, data uploading”). In addition, people traveling between different time zones may produce implausible time patterns when the device does not recognize the change in time zone (“Subjects may travel between different time zones during study period. Some devices don't recognize a different time zone and the recorded data has weird time pattern that is hard to understand”). These challenges were not explicitly mentioned in the literature but are implied by incorrect data problems.</p>
          </sec>
          <sec>
            <title>Data Access and Semantics</title>
            <p>There were data quality challenges related to data access and semantics. For example, the difficulty in accessing raw data and minute-level data was mentioned by a few respondents. In addition, a few respondents mentioned that interpreting the data may be a challenge because of the lack of information on context and provenance (eg, no documentation of exposures). Lack of transparency owing to consumer devices being proprietary was also mentioned. These challenges were not mentioned in our literature review study on data quality challenges because the scope of research was only on intrinsic data quality challenges, but there were studies mentioning these challenges.</p>
          </sec>
        </sec>
        <sec>
          <title>Ratings of Data Quality Dimensions</title>
          <p>Respondents’ importance ratings on dimensions from the HIDQF are presented in <xref rid="figure2" ref-type="fig">Figures 2</xref> and <xref rid="figure3" ref-type="fig">3</xref> [<xref ref-type="bibr" rid="ref14">14</xref>].</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Importance ratings on dimensions from harmonized intrinsic data quality framework.</p>
            </caption>
            <graphic xlink:href="mhealth_v9i12e31618_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Importance versus reliability of ratings on data quality dimensions in the harmonized intrinsic data quality framework.</p>
            </caption>
            <graphic xlink:href="mhealth_v9i12e31618_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>Adopting the cutoffs used in a previously published study, dimensions with mean ratings&#62;3 were determined to be important, and ratings with SD &#60;1.2 were considered reliable [<xref ref-type="bibr" rid="ref24">24</xref>]. Overall, respondents considered dimensions from the HIDQF as important data quality features for wearable device data. A follow-up question on the most important dimension identified completeness as the most important dimension (n=7), followed by relational conformance (n=4), computational conformance (n=4), value conformance (n=1), temporal plausibility (n=1), and atemporal plausibility (n=1).</p>
          <p>A few respondents answered the free-response question on additional data quality dimensions that need to be added. Various problems were mentioned, including the importance of a consistent sampling rate when dealing with multiple device data and the need for contextual information about the data set. For instance, metadata on whether the data set is raw data or processed using proprietary algorithms and whether the users brought their own device or whether it was provided was considered important information to respondents. Furthermore, information on the wearing status of users was considered important.</p>
        </sec>
      </sec>
      <sec>
        <title>Part 3: Deriving Dimensions Through Focus Group Discussion</title>
        <p>The potential data quality dimensions proposed by the facilitator (SC) are presented in <xref ref-type="table" rid="table2">Table 2</xref> (the full version of this table can be found in Table S1 of <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Conformance was included as a potential data quality dimension based on the factors related to data heterogeneity found in the literature review and survey responses on the importance of data conformance. Completeness was one of the most frequently mentioned data quality challenge in both the literature review and survey. It was also selected as the most important data quality dimension by the survey respondents and thus was included in the list of potential data quality dimensions. Data quality challenges related to accuracy (data incorrectness) were frequently mentioned in both the literature and the survey. In addition, plausibility, which has a similar context with accuracy, was mentioned by survey respondents (eg, “large spikes or drops in activity that are highly inconsistent with their surrounding measured values”). Both challenges were presented to the experts for further discussion. The difficulty of accessing minute- or second-level data was mentioned as a challenge in both the literature and the survey (this is more of an extrinsic data quality challenge, which was why it was not reported in the previously published literature review study). As the objective of this study was to focus on intrinsic and contextual and fitness-for-use data quality dimensions, not extrinsic data quality dimensions, data accessibility was not included as a potential data quality dimension. Instead, the challenge of accessing minute- or second-level data was interpreted as the researchers’ need for more temporally granular data. Thus, temporal data granularity was added as a potential data quality dimension. Finally, data interpretability was proposed to domain experts based on survey responses on the need for contextual information and metadata.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>List of data quality dimensions suggested based on findings from literature review and survey.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="190"/>
            <col width="310"/>
            <col width="320"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Dimensions suggested to experts</td>
                <td>Corresponding content from the literature review</td>
                <td>Corresponding content from survey responses</td>
                <td>Importance rating (only for HIDQF<sup>a</sup>)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Conformance</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Value conformance</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Different devices may use a different measurement unit.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Data set not conforming to data dictionary will be hard to fix”</p>
                    </list-item>
                  </list>
                </td>
                <td>4.32</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Relational conformance</td>
                <td>—<sup>b</sup></td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Without relational conformance you can't link one wearable device to another or to health outcomes”</p>
                    </list-item>
                  </list>
                </td>
                <td>4.11</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Computational conformance</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Companies do not always reveal whether or when they update their device algorithms or whether or when the users install the provided software updates.</p>
                    </list-item>
                    <list-item>
                      <p>Lack of standardization: (for multi-device studies) different devices may use different algorithms, a different definition for the same parameter, different sampling rate.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“I don’t know a way to proceed with the data analyses if the computational conformance isn’t met with satisfaction. it suggests that the data collected cannot be trusted.”</p>
                    </list-item>
                  </list>
                </td>
                <td>4.11</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Completeness</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Missing data due to various reasons: device malfunction, connectivity issues, nonadherence to the device, quality of skin contact of the device.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Missing data is a large issue for our research, especially because we are trying to identify patterns or subsequences of activity. Missing data has to either be interpolated or treated as a zero value, and either of these methods can have a large negative effect on the results of our pattern mining techniques.”</p>
                    </list-item>
                  </list>
                </td>
                <td>4.16</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Breadth completeness</td>
                <td>—</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Lack of availability of HRV<sup>c</sup>”</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Plausibility</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Uniqueness plausibility</td>
                <td>—</td>
                <td>—</td>
                <td>3.56</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Atemporal plausibility</td>
                <td>—</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Large spikes or drops in activity that are highly inconsistent with their surrounding measured values”</p>
                    </list-item>
                  </list>
                </td>
                <td>3.72</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Temporal plausibility</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Companies do not always reveal whether or when they update their device algorithms, or whether or when the users install the provided software updates.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Devices might cause problem with recording different time zone or time during traveling: Subjects may travel between different time zones during study period. Some devices don't recognize a different time zone and the recorded data has weird time pattern that is hard to understand”</p>
                    </list-item>
                  </list>
                </td>
                <td>4.11</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Temporal data granularity</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Fitbit only provides access to day-level data unless the minute-level or second-level data is requested and approved.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Access to minute level data.”</p>
                    </list-item>
                  </list>
                </td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Accuracy</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Poor data accuracy caused by device malfunction, unknown limitations of proprietary algorithms, user error in device use.</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Other activities generating step counts (eg, motorcycle ride, vibration)”</p>
                    </list-item>
                    <list-item>
                      <p>“Inaccurate sleep and wake time recognition”</p>
                    </list-item>
                  </list>
                </td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Interpretability</td>
                <td>—</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“Trying to nail down exactly what a participant was doing when data was being collected offsite.”</p>
                    </list-item>
                  </list>
                </td>
                <td>—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>HIDQF: harmonized intrinsic data quality framework.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>No available data.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>HRV: heart rate variability.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>In total, 3 separate discussion sessions were conducted in January, May, and September 2020. All sessions were conducted with 2-3 domain experts and 1 facilitator. In all, 2 data quality experts and 1 wearable device expert participated in the first discussion session. To continue the discussion on the relevance of dimensions to wearable device data, the second and third discussion sessions were conducted with 3 and 2 data quality experts, respectively. The domain experts agreed that all dimensions in the HIDQF were applicable to person-generated wearable device data. In addition, it was suggested to add contextual and fitness-for-use data quality dimensions that consider data quality in the context of a given research task [<xref ref-type="bibr" rid="ref16">16</xref>]. Although the dimensions of the HIDQF are for research purposes as well, they focused on intrinsic data quality that assesses data quality in terms of the structure and presence of the data itself, independent of research tasks [<xref ref-type="bibr" rid="ref14">14</xref>]. Considering that our focus was on using wearable device data for research purposes, aspects of data quality that can be determined once the research task is known were considered important. The final list of dimensions is shown in <xref rid="figure4" ref-type="fig">Figure 4</xref>.</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Data quality dimensions for assessing person-generated wearable device data for research purposes. HIDQF: harmonized intrinsic data quality framework.</p>
          </caption>
          <graphic xlink:href="mhealth_v9i12e31618_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>There was substantial discussion on <italic>completeness</italic>. The completeness dimension in the HIDQF is defined as “Are data values present?” which measures completeness based on the presence of data without referring to research tasks [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. However, determining missing data could be complicated for wearable device data when conducting research, especially for activity or step count data, because missing data could appear as null but more often as zero values [<xref ref-type="bibr" rid="ref9">9</xref>]. Interpreting zero values is not easy because it could mean that a person was not wearing the device (true missingness) or was sedentary (a valid zero value). Zero values generated from being sedentary are not simply missing data, as they provide information on device users’ physical activity [<xref ref-type="bibr" rid="ref26">26</xref>]. As it is impossible to know the cause of zero values, researchers typically make assumptions on thresholds for the inactivity period to determine nonwear time (eg, 60 minutes of inactivity [zero step count] is considered as a user not wearing the device) [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Thus, data completeness for activity-related data can be assessed based on the measures and thresholds that researchers set to define what is or is not missing data. This was why the fitness-for-use data completeness dimensions were considered important by domain experts. There were 2 fitness-for-use completeness dimensions determined as applicable to wearable device data, which were breadth and density completeness. Breadth completeness assesses whether a data set contains all types of data that are required for a specific task. For example, to investigate the association between activity and heart rate, a data set that does not provide heart rate data would not be suitable for use. Density completeness assesses whether a data set contains sufficient amount of data in terms of density, regularity, and duration. For instance, examining the association between step count and blood pressure might require the data set to have ≥10 days of step count data per month for 2 months [<xref ref-type="bibr" rid="ref28">28</xref>]. The 2 subcategories of completeness, which are breadth and density completeness, were adopted from Weiskopf et al [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
        <p>There was also a significant debate on whether accuracy (<italic>Do the data reflect the true value?</italic>) should be included as a dimension. On one hand, accuracy was considered a dimension that can be easily understood by stakeholders and the ultimate goal of data quality. On the other hand, accuracy was viewed as a vague term that could be interpreted in many different ways. For example, inaccuracy could be an umbrella term that incorporates invalid data, missing data, or data not conforming to data dictionaries. In addition, accuracy was considered inapplicable for assessing data quality from the secondary use of the data perspective. This is because it is impossible to know whether the data are correct or incorrect in the absence of a known truth. For instance, although the data indicated that an individual took 8 steps at 9 AM on April 5, 2020, there would be no way for a researcher to assess whether that is right or wrong when they retrospectively assess the accuracy of that value. The accuracy of the data values can only be assessed by comparing the device to a gold standard device. In reality, this is not feasible as people rarely wear more than one device in their daily lives, which restricts the ability to assess the accuracy of values in a longitudinal and continuously collected wearable device data. This was why the dimension <italic>plausibility</italic> (<italic>Do the data make sense?</italic>) was eventually included rather than <italic>accuracy</italic>.</p>
        <p>Temporal data granularity was another fitness-for-use dimension considered important. As wearable device data are time-series data, the granularity of time points was deemed as an essential aspect. Temporal data granularity is about how frequently the data are documented (eg, every second, minute, or hour) and whether it fits the purpose of the research task. For example, a data set with timestamps every hour would not be suitable for research requiring data points every minute.</p>
        <p>Other minor issues mentioned in the literature review and survey were not included as a dimension. For example, survey respondents mentioned the difficulty of interpreting data values, understanding what was really happening while data were being collected, or knowing how the data were collected. This was considered a metadata quality problem rather than a quality metric for the data. The definitions and examples of the final set of dimensions derived from focus group discussions are presented in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Data quality dimensions for person-generated wearable device data identified by domain experts.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="30"/>
            <col width="260"/>
            <col width="0"/>
            <col width="340"/>
            <col width="0"/>
            <col width="340"/>
            <thead>
              <tr valign="bottom">
                <td colspan="4">Type and dimension</td>
                <td colspan="2">Definition<sup>a</sup></td>
                <td>Example</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="7">
                  <bold>Intrinsic</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Conformance: Do data values adhere to specified standards and formats?</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Value conformance</td>
                <td colspan="2">Data values conform to internal formatting constraints, allowable values, or ranges.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Unit of distance is “miles.”</p>
                    </list-item>
                    <list-item>
                      <p>“Sleep stages” only has values “deep,” “light,” “rem,” and “wake,” which conform to the data dictionary.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Relational conformance</td>
                <td colspan="2">Assuming there are multiple tables or files, recorded data elements agree with structural constraints imposed by the physical database structures that store data values.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Participant ID number links to other tables as required.</p>
                    </list-item>
                    <list-item>
                      <p>The wearable device identifier is appropriately linked for all observations.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Computational conformance</td>
                <td colspan="2">Computations used to create derived values from existing variables yield the intended results either within a data set or between data sets.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Sleep duration conforms to the difference between start time and end time of sleep.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">Completeness: Are data values present?</td>
                <td colspan="2">Missing data is determined based on the presence of data. Typically, absence of data is expected if the device is not worn, but this could sometimes be difficult to know retrospectively.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>There is no NA (Not Available) in the step count data.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Plausibility: Are data values believable?</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Uniqueness plausibility</td>
                <td colspan="2">Objects do not appear multiple times in settings where they should not be duplicated or cannot be distinguished within a database or when compared with an external reference.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>A single participant only has one participant ID number.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Atemporal plausibility</td>
                <td colspan="2">Observed data values, distributions, or densities agree with local or “common” knowledge or from comparisons with external sources that are deemed to be trusted or relative gold standards.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Step count and distance values are positive.</p>
                    </list-item>
                    <list-item>
                      <p>Trends of step counts and distance agree with each other.</p>
                    </list-item>
                    <list-item>
                      <p>Step counts do not show a sudden spike during sleep or during sedentary time.</p>
                    </list-item>
                    <list-item>
                      <p>The range of heart rate values is biologically plausible.</p>
                    </list-item>
                    <list-item>
                      <p>Heart rate is higher when active compared with when sedentary.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Temporal plausibility</td>
                <td colspan="2">Time-varying variables change values as expected based on known temporal properties or across one or more external comparators or gold standards.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Start time of sleep occurs before end time of sleep.</p>
                    </list-item>
                    <list-item>
                      <p>Aggregate step count is higher during daytime than nighttime.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Contextual and fitness-for-use</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Completeness: Are data values present fit for intended use?</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Breadth completeness</td>
                <td colspan="2">All data types required for intended use exist.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Heart rate data are essential for studies analyzing the relationship between physical activity and heart rate.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Density completeness</td>
                <td colspan="2">Data set contains a specified number of data values or occurs regularly over a certain period.</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Heart rate should be measured at least once a day.</p>
                    </list-item>
                    <list-item>
                      <p>Sleep data should be recorded every day consecutively for a 6-week period to be considered complete.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">Temporal data granularity: does the device collect data granular enough for intended use?</td>
                <td colspan="2">Granularity of time stamps are sufficient for the task at hand.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Data values are recorded every second, which is appropriate for marathon research studies (the exact start and end time of the marathon for each runner is important for marathon-related studies).</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>Definitions were adopted and adapted from the studies by Weiskopf et al [<xref ref-type="bibr" rid="ref25">25</xref>] and Kahn et al [<xref ref-type="bibr" rid="ref14">14</xref>].</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In this study, data quality dimensions for person-generated wearable device data were identified using multiple methods. A literature review and survey was conducted to understand the data quality challenges of researchers and their perceptions on data quality dimensions. On the basis of this information, domain experts determined the appropriate dimensions. Experts agreed that the data quality dimensions from the HIDQF are applicable to person-generated wearable device data, and fitness-for-use dimensions were also considered important, especially for research purposes. The final data quality dimensions deemed important were intrinsic data quality dimensions, such as conformance, completeness, and plausibility, and fitness-for-use data quality dimensions, such as breadth and density completeness and temporal data granularity.</p>
      </sec>
      <sec>
        <title>Data Quality Assessment Guidelines for Researchers</title>
        <sec>
          <title>Completeness</title>
          <p>In this study, breadth and density completeness, which are contextual and fitness-for-use data quality dimensions, were considered important for conducting research. Assessing breadth completeness is important, especially for data sets collected in a bring-your-own-device research setting [<xref ref-type="bibr" rid="ref9">9</xref>]. This is because different brands and models that users bring may collect different data types, which means that not all individuals in the data set would have all the data types that are needed to answer a research question.</p>
          <p>Density completeness is also an essential fitness-for-use dimension for wearable device data because the amount of data sufficient and valid for a specific research task is determined by researchers. Researchers first need to determine how wear versus nonwear of the device is defined. Typically, consumer wearables do not provide information on the wear status; thus, researchers need to make decisions based on existing data. The recorded zero step counts could be due to nonwear (missing data) or it could mean inactivity, and thus researchers need to determine thresholds to define nonwear. An alternative method to determine the wearing status could be based on the existence of heart rate data or the values of heart rate data. For example, Lim et al [<xref ref-type="bibr" rid="ref4">4</xref>] used the confidence values of heart rate data points as surrogate measures for which <italic>−1</italic> indicates invalid data because the device is not worn or incorrectly worn. This approach opens up the discussion on missing data, whether it should be simply based on the absence of data values or whether the default values for missing data and their semantic meaning should be considered. This was the reason why the fitness-for-use completeness dimensions were considered important.</p>
          <p>On the basis of decisions made on wear versus nonwear, researchers can determine the appropriate level of data density for their research. Researchers can first determine the thresholds for how much health behavior data are sufficient for a day. For example, Tang et al [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] systematically addressed the incompleteness of physical activity data by presenting heuristic criteria for the definition of a valid day: a day is valid (1) if the step count is above a certain threshold, (2) if the number of hours with data is above a certain threshold, (3) if there are data within 3 periods. Researchers can also define completeness based on the number of valid days needed within a certain data collection period, or how regularly the data should be present for the individual data to be included in the analysis [<xref ref-type="bibr" rid="ref9">9</xref>]. As recently released devices have the ability to examine various data types and collect data seamlessly for years, further investigation is needed to determine how completeness is characterized in research studies.</p>
        </sec>
        <sec>
          <title>Conformance</title>
          <p>Value, relational, and computational conformance are all considered important dimensions for wearable device data, but there are challenges in data management and quality assessment. Value and relational conformance can only be assessed in terms of the data dictionary and relational model specific to the brand, model, and version of the device but only if this information is publicly available. In addition, computational conformance can be assessed for values that can be calculated using generic equations, such as sleep duration, which is the difference between the start and end of sleep time. However, it can be difficult to assess computational conformance for variables calculated using proprietary algorithms, as these are not disclosed to data users. Another challenge related to data conformance is the lack of a common data standard for wearable device data. A common data standard would be crucial for a data set collected from disparate devices (eg, Apple Watch and Fitbit Charge HR), such as data collected under a bring-your-own-device protocol. There is a movement in the mobile health community, called Open mHealth, to create a common data schema that explicitly states the format and data definitions for patient-generated data [<xref ref-type="bibr" rid="ref30">30</xref>]. Adopting these standards for wearable device data might solve the discrepancy between the definition of data values among multi-device data. For example, currently there is no industry standard for defining activity intensity (eg, light, moderate, and vigorous). These challenges indicate that facilitating the use of consumer wearables for research purposes would not be feasible without the support of device companies and the research community.</p>
        </sec>
        <sec>
          <title>Plausibility</title>
          <p>Plausibility aligns with the needs of researchers for accurate data values. For instance, data may be deemed implausible when step counts are higher than normal, but the corresponding heart rate values are lower than usual. Typically, researchers arbitrarily come up with their own rules to assess the plausibility of data before proceeding with the analysis. However, domain knowledge and a considerable amount of experts’ time are required to formulate a set of potential data quality rules. Thus, creating a knowledge base of data quality rules for person-generated wearable device data would not only save time for future researchers but also prevent the use of ad hoc data quality rules [<xref ref-type="bibr" rid="ref9">9</xref>]. Another challenge for plausibility is that there are few known external benchmarks that can be used to validate or triangulate the data (data quality validation per the HIDQF). For example, the summary statistics of steps, active minutes, and BMI have been compared with the corresponding values in the Centers for Disease Control and Prevention survey (eg, Behavioral Risk Factor Surveillance System) [<xref ref-type="bibr" rid="ref31">31</xref>]. Further discussion among the researcher community would be needed to find potential methods or data sources to check the plausibility of data.</p>
          <p>Although plausibility was chosen over accuracy as a data quality dimension, it is true that many people are concerned about whether data values are trustworthy. Even though accuracy cannot be assessed in the secondary use of data scenarios, it could be indirectly verified through the results of device validation studies [<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>]. Thus, it is important to provide metadata information on the device brand, model, and version that generated the data set as each element can change device validity [<xref ref-type="bibr" rid="ref35">35</xref>]. However, knowing the validity and reliability of a device is insufficient to understand the accuracy of data because there are other factors that affect data quality such as incorrect device use by the user. In addition, device validation studies are generally conducted in a controlled setting for a short period.</p>
        </sec>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study has a few limitations. First, the study focuses only on intrinsic and fitness-for-use data quality dimensions and thus does not include extrinsic data quality features, that is, features that affect the data but are not about the data values themselves (eg, security, privacy, or data accessibility). There might be contextual information or metadata that are considered important when determining the fitness-for-use of a data set. For example, some researchers might want to know the process or operational aspects of data collection (eg, Were the data collected under the bring-your-own-device policy or were devices provided?) [<xref ref-type="bibr" rid="ref36">36</xref>]. These factors were not captured as a data quality dimension, but it is an aspect that might need to be considered when assessing the fitness-for-use of a data set. Second, the study was conducted with a small number of survey respondents and domain experts. Therefore, survey responses and experts’ opinions may not be representative and comprehensive. As survey responses match the results of the literature review, it is likely that the survey was able to capture most of the data quality challenges despite the small number of respondents. Furthermore, the intrinsic data quality dimensions identified in this study leveraged the dimensions of the HIDQF. The HIDQF was determined through iterative meetings with stakeholders and data quality experts; thus, it is highly likely that most intrinsic data quality dimensions were included in our final list of dimensions. In future studies, contextual and fitness-for-use data quality dimensions could be further investigated with a larger group of stakeholders of person-generated wearable device data.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Person-generated wearable device data are an emerging data type for biomedical research because of the growing use of wearable devices in people’s daily lives. However, there is a lack of agreement on how data quality should be assessed for person-generated wearable device data. As the first step to solve this challenge, data quality dimensions were identified specifically for person-generated wearable device data. We found that data quality dimensions for secondary use of EHR data are applicable to person-generated wearable device data. The identified dimensions will be able to provide guidance to researchers on how data quality is defined and what aspects of data quality should be assessed for person-generated wearable device data. Further research on how data quality can be assessed with regard to dimensions is needed.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Dimensions suggested by facilitator and final decision by domain experts.</p>
        <media xlink:href="mhealth_v9i12e31618_app1.docx" xlink:title="DOCX File , 18 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">HIDQF</term>
          <def>
            <p>harmonized intrinsic data quality framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PGHD</term>
          <def>
            <p>person-generated health data</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank all the respondents who participated in the survey to provide their knowledge and experience. They also thank Carol E Garber for her input on wearable device data. This research was supported by the National Center for Advancing Translational Sciences grant 1U01TR002062-01 and the National Institute of Health’s All of Us Research Program grant 1U2COD023196-01.</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>Henriksen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Haugen Mikalsen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Woldaregay</surname>
              <given-names>AZ</given-names>
            </name>
            <name name-style="western">
              <surname>Muzny</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hartvigsen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hopstock</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Grimsgaard</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Using fitness trackers and smartwatches to measure physical activity in research: analysis of consumer wrist-worn wearables</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>03</month>
          <day>22</day>
          <volume>20</volume>
          <issue>3</issue>
          <fpage>e110</fpage>
          <pub-id pub-id-type="doi">10.2196/jmir.9157</pub-id>
          <pub-id pub-id-type="medline">29567635</pub-id>
          <pub-id pub-id-type="pii">v20i3e110</pub-id>
          <pub-id pub-id-type="pmcid">PMC5887043</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fawcett</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Mining the quantified self: personal knowledge discovery as a challenge for data science</article-title>
          <source>Big Data</source>
          <year>2015</year>
          <month>12</month>
          <volume>3</volume>
          <issue>4</issue>
          <fpage>249</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1089/big.2015.0049</pub-id>
          <pub-id pub-id-type="medline">27441406</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>Izmailova</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Perakslis</surname>
              <given-names>ED</given-names>
            </name>
          </person-group>
          <article-title>Wearable devices in clinical trials: hype and hypothesis</article-title>
          <source>Clin Pharmacol Ther</source>
          <year>2018</year>
          <month>07</month>
          <volume>104</volume>
          <issue>1</issue>
          <fpage>42</fpage>
          <lpage>52</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29205294"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/cpt.966</pub-id>
          <pub-id pub-id-type="medline">29205294</pub-id>
          <pub-id pub-id-type="pmcid">PMC6032822</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>Lim</surname>
              <given-names>WK</given-names>
            </name>
            <name name-style="western">
              <surname>Davila</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Teo</surname>
              <given-names>JX</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pua</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Blöcker</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>JQ</given-names>
            </name>
            <name name-style="western">
              <surname>Ching</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yap</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Sahlén</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chin</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Teh</surname>
              <given-names>BT</given-names>
            </name>
            <name name-style="western">
              <surname>Rozen</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Yeo</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Beyond fitness tracking: the use of consumer-grade wearable data from normal volunteers in cardiovascular and lipidomics research</article-title>
          <source>PLoS Biol</source>
          <year>2018</year>
          <month>02</month>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>e2004285</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pbio.2004285"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pbio.2004285</pub-id>
          <pub-id pub-id-type="medline">29485983</pub-id>
          <pub-id pub-id-type="pii">pbio.2004285</pub-id>
          <pub-id pub-id-type="pmcid">PMC5828350</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>McDonald</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mehmud</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ramagopalan</surname>
              <given-names>SV</given-names>
            </name>
          </person-group>
          <article-title>Sleep and BMI: do (Fitbit) bands aid?</article-title>
          <source>F1000Res</source>
          <year>2018</year>
          <month>4</month>
          <day>27</day>
          <volume>7</volume>
          <fpage>511</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://f1000research.com/articles/10.12688/f1000research.14774.2/doi"/>
          </comment>
          <pub-id pub-id-type="doi">10.12688/f1000research.14774.2</pub-id>
          <pub-id pub-id-type="medline">30271578</pub-id>
          <pub-id pub-id-type="pmcid">PMC6144946</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>Xu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Conomos</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Manor</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Rohwer</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Magis</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Lovejoy</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Habitual sleep duration and sleep duration variation are independently associated with body mass index</article-title>
          <source>Int J Obes (Lond)</source>
          <year>2018</year>
          <month>04</month>
          <volume>42</volume>
          <issue>4</issue>
          <fpage>794</fpage>
          <lpage>800</lpage>
          <pub-id pub-id-type="doi">10.1038/ijo.2017.223</pub-id>
          <pub-id pub-id-type="medline">28895585</pub-id>
          <pub-id pub-id-type="pii">ijo2017223</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <article-title>All of us research program overview</article-title>
          <source>National Institutes of Health</source>
          <access-date>2021-12-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://allofus.nih.gov/about/about-all-us-research-program">https://allofus.nih.gov/about/about-all-us-research-program</ext-link>
          </comment>
        </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>Hicks</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Althoff</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Sosic</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bostjancic</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>King</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Leskovec</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Delp</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Best practices for analyzing large-scale health data from wearables and smartphone apps</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <volume>2</volume>
          <fpage>45</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0121-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0121-1</pub-id>
          <pub-id pub-id-type="medline">31304391</pub-id>
          <pub-id pub-id-type="pii">121</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550237</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>Cho</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ensari</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kahn</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Natarajan</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting the quality of person-generated wearable device data and associated challenges: rapid systematic review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2021</year>
          <month>03</month>
          <day>19</day>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>e20738</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/3/e20738/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/20738</pub-id>
          <pub-id pub-id-type="medline">33739294</pub-id>
          <pub-id pub-id-type="pii">v9i3e20738</pub-id>
          <pub-id pub-id-type="pmcid">PMC8294465</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DiazVasquez</surname>
              <given-names>JF</given-names>
            </name>
          </person-group>
          <article-title>DataGauge: a model-driven framework for systematically assessing the quality of clinical data for secondary use</article-title>
          <source>UT School of Biomedical Informatics</source>
          <year>2016</year>
          <access-date>2021-12-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digitalcommons.library.tmc.edu/uthshis_dissertations/33/">https://digitalcommons.library.tmc.edu/uthshis_dissertations/33/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karkouch</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mousannif</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Al Moatassime</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Noel</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Data quality in internet of things: a state-of-the-art survey</article-title>
          <source>J Netw Comput Applications</source>
          <year>2016</year>
          <month>09</month>
          <volume>73</volume>
          <fpage>57</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2016.08.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Guarascio</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Dimensions of data quality: toward quality data by design</article-title>
          <source>Massachusetts Institute of Technology</source>
          <year>1991</year>
          <month>08</month>
          <access-date>2021-12-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.semanticscholar.org/paper/Dimensions-of-Data-Quality%3A-Toward-Quality-Data-by-Wang-Guarascio/9b2c2ef2ecf24a2f721fbb9173355673c18aca06">https://tinyurl.com/ynh4j4</ext-link>
          </comment>
        </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>Weiskopf</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Methods and dimensions of electronic health record data quality assessment: enabling reuse for clinical research</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>01</month>
          <day>01</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>144</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22733976"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000681</pub-id>
          <pub-id pub-id-type="medline">22733976</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000681</pub-id>
          <pub-id pub-id-type="pmcid">PMC3555312</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>Kahn</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Barnard</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bauck</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Davidson</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Estiri</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Goerg</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Holve</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Liaw</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hamilton-Lopez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meeker</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Shang</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Weiskopf</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zozus</surname>
              <given-names>MN</given-names>
            </name>
            <name name-style="western">
              <surname>Schilling</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A harmonized data quality assessment terminology and framework for the secondary use of electronic health record data</article-title>
          <source>EGEMS (Wash DC)</source>
          <year>2016</year>
          <month>9</month>
          <day>11</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>1244</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27713905"/>
          </comment>
          <pub-id pub-id-type="doi">10.13063/2327-9214.1244</pub-id>
          <pub-id pub-id-type="medline">27713905</pub-id>
          <pub-id pub-id-type="pii">egems1244</pub-id>
          <pub-id pub-id-type="pmcid">PMC5051581</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>Johnson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Speedie</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Westra</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A data quality ontology for the secondary use of EHR data</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2015</year>
          <month>11</month>
          <day>5</day>
          <volume>2015</volume>
          <fpage>1937</fpage>
          <lpage>46</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26958293"/>
          </comment>
          <pub-id pub-id-type="medline">26958293</pub-id>
          <pub-id pub-id-type="pmcid">PMC4765682</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Strong</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Beyond accuracy: what data quality means to data consumers</article-title>
          <source>J Manag Inf Syst</source>
          <year>2015</year>
          <month>12</month>
          <day>11</day>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>5</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1080/07421222.1996.11518099</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Stvilia</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jörgensen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>HW</given-names>
            </name>
          </person-group>
          <article-title>Prioritization of data quality dimensions and skills requirements in genome annotation work</article-title>
          <source>J Am Soc Inf Sci</source>
          <year>2011</year>
          <month>10</month>
          <day>04</day>
          <volume>63</volume>
          <issue>1</issue>
          <fpage>195</fpage>
          <lpage>207</lpage>
          <pub-id pub-id-type="doi">10.1002/asi.21652</pub-id>
        </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>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chi</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Evolutional data quality: a theory-specific view</article-title>
          <source>Proceedings of the Seventh International Conference on Information Quality (ICIQ 2002)</source>
          <year>2002</year>
          <conf-name>Seventh International Conference on Information Quality (ICIQ 2002)</conf-name>
          <conf-date>Jan 2002</conf-date>
          <conf-loc>Cambridge, MA, USA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>
          <month>1</month>
          <day>1</day>
          <volume>62</volume>
          <issue>1</issue>
          <fpage>3:1</fpage>
          <lpage>3:8</lpage>
          <pub-id pub-id-type="doi">10.1147/jrd.2017.2762218</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Silverman</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>Doing Qualitative Research</source>
          <year>2010</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <article-title>Qualtrics homepage</article-title>
          <source>Qualtrics</source>
          <access-date>2021-12-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.qualtrics.com/">https://www.qualtrics.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>OHDSI Forums</article-title>
          <source>Observational Health Data Sciences and Informatics (OHDSI)</source>
          <access-date>2021-12-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://forums.ohdsi.org/">https://forums.ohdsi.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>Full survey on data quality challenges and dimensions of wearable device data</article-title>
          <source>Columbia University</source>
          <access-date>2021-12-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cumc.co1.qualtrics.com/jfe/preview/SV_bNlmgCekd9FC3Gd?Q_CHL=preview&#38;Q_SurveyVersionID=current">https://cumc.co1.qualtrics.com/jfe/preview/SV_bNlmgCekd9FC3Gd?Q_CHL=preview&#38;Q_SurveyVersionID=current</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zozus</surname>
              <given-names>MN</given-names>
            </name>
            <name name-style="western">
              <surname>Pieper</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Franklin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting accuracy of data abstracted from medical records</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <month>10</month>
          <day>20</day>
          <volume>10</volume>
          <issue>10</issue>
          <fpage>e0138649</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0138649"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0138649</pub-id>
          <pub-id pub-id-type="medline">26484762</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-29205</pub-id>
          <pub-id pub-id-type="pmcid">PMC4615628</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>Weiskopf</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Swaminathan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Defining and measuring completeness of electronic health records for secondary use</article-title>
          <source>J Biomed Inform</source>
          <year>2013</year>
          <month>10</month>
          <volume>46</volume>
          <issue>5</issue>
          <fpage>830</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(13)00085-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2013.06.010</pub-id>
          <pub-id pub-id-type="medline">23820016</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(13)00085-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC3810243</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>Mailey</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Gothe</surname>
              <given-names>NP</given-names>
            </name>
            <name name-style="western">
              <surname>Wójcicki</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Szabo</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Olson</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Mullen</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Fanning</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Motl</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>McAuley</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Influence of allowable interruption period on estimates of accelerometer wear time and sedentary time in older adults</article-title>
          <source>J Aging Phys Act</source>
          <year>2014</year>
          <month>04</month>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>255</fpage>
          <lpage>60</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23752299"/>
          </comment>
          <pub-id pub-id-type="doi">10.1123/japa.2013-0021</pub-id>
          <pub-id pub-id-type="medline">23752299</pub-id>
          <pub-id pub-id-type="pii">2013-0021</pub-id>
          <pub-id pub-id-type="pmcid">PMC3875619</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>Evenson</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Terry</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>Assessment of differing definitions of accelerometer nonwear time</article-title>
          <source>Res Q Exerc Sport</source>
          <year>2009</year>
          <month>06</month>
          <volume>80</volume>
          <issue>2</issue>
          <fpage>355</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/19650401"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/02701367.2009.10599570</pub-id>
          <pub-id pub-id-type="medline">19650401</pub-id>
          <pub-id pub-id-type="pmcid">PMC3321743</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>Menai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brouard</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vegreville</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chieh</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Oppert</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lelong</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Loprinzi</surname>
              <given-names>PD</given-names>
            </name>
          </person-group>
          <article-title>Cross-sectional and longitudinal associations of objectively-measured physical activity on blood pressure: evaluation in 37 countries</article-title>
          <source>Health Promot Perspect</source>
          <year>2017</year>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>190</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29085795"/>
          </comment>
          <pub-id pub-id-type="doi">10.15171/hpp.2017.34</pub-id>
          <pub-id pub-id-type="medline">29085795</pub-id>
          <pub-id pub-id-type="pmcid">PMC5647353</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Bragg</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Engelen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bauman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kay</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Defining adherence: making sense of physical activity tracker data</article-title>
          <source>Proc ACM Interact Mob Wearable Ubiquitous Technol</source>
          <year>2018</year>
          <month>03</month>
          <day>26</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1145/3191769</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Estrin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sim</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Open mHealth architecture: an engine for health care innovation</article-title>
          <source>Science</source>
          <year>2010</year>
          <month>11</month>
          <day>05</day>
          <volume>330</volume>
          <issue>6005</issue>
          <fpage>759</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1126/science.1196187</pub-id>
          <pub-id pub-id-type="medline">21051617</pub-id>
          <pub-id pub-id-type="pii">330/6005/759</pub-id>
        </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>Evenson</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Furberg</surname>
              <given-names>RD</given-names>
            </name>
          </person-group>
          <article-title>Assessing validity of the Fitbit indicators for U.S. public health surveillance</article-title>
          <source>Am J Prev Med</source>
          <year>2017</year>
          <month>12</month>
          <volume>53</volume>
          <issue>6</issue>
          <fpage>931</fpage>
          <lpage>2</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28755981"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.amepre.2017.06.005</pub-id>
          <pub-id pub-id-type="medline">28755981</pub-id>
          <pub-id pub-id-type="pii">S0749-3797(17)30304-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5696087</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>Alsubheen</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>George</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rohr</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Basset</surname>
              <given-names>FA</given-names>
            </name>
          </person-group>
          <article-title>Accuracy of the vivofit activity tracker</article-title>
          <source>J Med Eng Technol</source>
          <year>2016</year>
          <month>08</month>
          <volume>40</volume>
          <issue>6</issue>
          <fpage>298</fpage>
          <lpage>306</lpage>
          <pub-id pub-id-type="doi">10.1080/03091902.2016.1193238</pub-id>
          <pub-id pub-id-type="medline">27266422</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>Cadmus-Bertram</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gangnon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wirkus</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Thraen-Borowski</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Gorzelitz-Liebhauser</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The accuracy of heart rate monitoring by some wrist-worn activity trackers</article-title>
          <source>Ann Intern Med</source>
          <year>2017</year>
          <month>04</month>
          <day>11</day>
          <volume>166</volume>
          <issue>8</issue>
          <fpage>610</fpage>
          <lpage>2</lpage>
          <pub-id pub-id-type="doi">10.7326/L16-0353</pub-id>
          <pub-id pub-id-type="medline">28395305</pub-id>
          <pub-id pub-id-type="pii">2618339</pub-id>
          <pub-id pub-id-type="pmcid">PMC5564399</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>Kaewkannate</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A comparison of wearable fitness devices</article-title>
          <source>BMC Public Health</source>
          <year>2016</year>
          <month>05</month>
          <day>24</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>433</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpublichealth.biomedcentral.com/articles/10.1186/s12889-016-3059-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12889-016-3059-0</pub-id>
          <pub-id pub-id-type="medline">27220855</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12889-016-3059-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC4877805</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>Collins</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Woolley</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Oniani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pires</surname>
              <given-names>IM</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Ledger</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pandyan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Version reporting and assessment approaches for new and updated activity and heart rate monitors</article-title>
          <source>Sensors (Basel)</source>
          <year>2019</year>
          <month>04</month>
          <day>10</day>
          <volume>19</volume>
          <issue>7</issue>
          <fpage>1705</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s19071705"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s19071705</pub-id>
          <pub-id pub-id-type="medline">30974755</pub-id>
          <pub-id pub-id-type="pii">s19071705</pub-id>
          <pub-id pub-id-type="pmcid">PMC6480461</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>Reynolds</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Bourke</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dreyer</surname>
              <given-names>NA</given-names>
            </name>
          </person-group>
          <article-title>Considerations when evaluating real-world data quality in the context of fitness for purpose</article-title>
          <source>Pharmacoepidemiol Drug Saf</source>
          <year>2020</year>
          <month>10</month>
          <volume>29</volume>
          <issue>10</issue>
          <fpage>1316</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32374042"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/pds.5010</pub-id>
          <pub-id pub-id-type="medline">32374042</pub-id>
          <pub-id pub-id-type="pmcid">PMC7687257</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
