<?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="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</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">v12i1e51560</article-id>
      <article-id pub-id-type="pmid">38446534</article-id>
      <article-id pub-id-type="doi">10.2196/51560</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Frameworks, Dimensions, Definitions of Aspects, and Assessment Methods for the Appraisal of Quality of Health Data for Secondary Use: Comprehensive Overview of Reviews</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Courvoisier</surname>
            <given-names>Delphine</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wang</surname>
            <given-names>Zhan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Declerck</surname>
            <given-names>Jens</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Public Health and Primary Care</institution>
            <institution>Unit of Medical Informatics and Statistics</institution>
            <institution>Ghent University</institution>
            <addr-line>Campus UZ-Ghent, Entrance 42, 6th Floor</addr-line>
            <addr-line>Corneel Heymanslaan 10</addr-line>
            <addr-line>Ghent, 9000</addr-line>
            <country>Belgium</country>
            <phone>32 93323628</phone>
            <email>jens.declerck@ugent.be</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9743-9188</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Kalra</surname>
            <given-names>Dipak</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2998-9882</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Vander Stichele</surname>
            <given-names>Robert</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9118-9651</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Coorevits</surname>
            <given-names>Pascal</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6515-7514</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Public Health and Primary Care</institution>
        <institution>Unit of Medical Informatics and Statistics</institution>
        <institution>Ghent University</institution>
        <addr-line>Ghent</addr-line>
        <country>Belgium</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>The European Institute for Innovation through Health Data</institution>
        <addr-line>Ghent</addr-line>
        <country>Belgium</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Faculty of Medicine and Health Sciences</institution>
        <institution>Heymans Institute of Pharmacology</institution>
        <addr-line>Ghent</addr-line>
        <country>Belgium</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Jens Declerck <email>jens.declerck@ugent.be</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>6</day>
        <month>3</month>
        <year>2024</year>
      </pub-date>
      <volume>12</volume>
      <elocation-id>e51560</elocation-id>
      <history>
        <date date-type="received">
          <day>3</day>
          <month>8</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>16</day>
          <month>9</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>7</day>
          <month>11</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>9</day>
          <month>1</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Jens Declerck, Dipak Kalra, Robert Vander Stichele, Pascal Coorevits. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 06.03.2024.</copyright-statement>
      <copyright-year>2024</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 Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2024/1/e51560" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Health care has not reached the full potential of the secondary use of health data because of—among other issues—concerns about the quality of the data being used. The shift toward digital health has led to an increase in the volume of health data. However, this increase in quantity has not been matched by a proportional improvement in the quality of health data.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This review aims to offer a comprehensive overview of the existing frameworks for data quality dimensions and assessment methods for the secondary use of health data. In addition, it aims to consolidate the results into a unified framework.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A review of reviews was conducted including reviews describing frameworks of data quality dimensions and their assessment methods, specifically from a secondary use perspective. Reviews were excluded if they were not related to the health care ecosystem, lacked relevant information related to our research objective, and were published in languages other than English.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 22 reviews were included, comprising 22 frameworks, with 23 different terms for dimensions, and 62 definitions of dimensions. All dimensions were mapped toward the data quality framework of the European Institute for Innovation through Health Data. In total, 8 reviews mentioned 38 different assessment methods, pertaining to 31 definitions of the dimensions.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The findings in this review revealed a lack of consensus in the literature regarding the terminology, definitions, and assessment methods for data quality dimensions. This creates ambiguity and difficulties in developing specific assessment methods. This study goes a step further by assigning all observed definitions to a consolidated framework of 9 data quality dimensions.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>data quality</kwd>
        <kwd>data quality dimensions</kwd>
        <kwd>data quality assessment</kwd>
        <kwd>secondary use</kwd>
        <kwd>data quality framework</kwd>
        <kwd>fit for purpose</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>To face the multiple challenges within our health care system, the secondary use of health data holds multiple advantages: it could increase patient safety, provide insights into person-centered care, and foster innovation and clinical research. To maximize these benefits, the health care ecosystem is investing rapidly in primary sources, such as electronic health records (EHRs) and personalized health monitoring, as well as in secondary sources, such as health registries, health information systems, and digital health technologies, to effectively manage illnesses and health risks and improve health care outcomes [<xref ref-type="bibr" rid="ref1">1</xref>]. These investments have led to large volumes of complex real-world data. However, health care is not obtaining the full potential of the secondary use of health data [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>] because of—among other issues—concerns about the quality of the data being used [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Errors in the collection of health data are common. Studies have reported that at least half of EHR notes may contain an error leading to low-quality data [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. The transition to digital health has produced more health data but not to the same extent as an increase in the quality of health data [<xref ref-type="bibr" rid="ref12">12</xref>]. This will impede the potentially positive impact of digitalization on patient safety [<xref ref-type="bibr" rid="ref13">13</xref>], patient care [<xref ref-type="bibr" rid="ref14">14</xref>], decision-making [<xref ref-type="bibr" rid="ref15">15</xref>], and clinical research [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
      <p>The literature is replete with various definitions of data quality. One of the most used definitions for data quality comes from Juran et al [<xref ref-type="bibr" rid="ref17">17</xref>], who defined data quality as “data that are fit for use in their intended operational, decision-making, planning, and strategic roles.” According to the International Organization for Standardization (ISO) definition, quality is “the capacity of an ensemble of intrinsic characteristics to satisfy requirements” (ISO 9000-2015). DAMA International (The Global Data Management Community: a leading international association involving both business and technical data management professionals) adapts this definition to a data context: “data quality is the degree to which the data dimensions meet requirements.” These definitions emphasize the subjectivity and context dependency of data quality [<xref ref-type="bibr" rid="ref18">18</xref>]. Owing to this “fit for purpose” principle, the quality of data may be adequate when used for one specific task but not for another.</p>
      <p>For example, when health data collected for primary use setting, such as blood pressure, are reused for different purposes, the adequacy of their quality can vary. For managing hypertension, the data’s accuracy and completeness may be considered adequate. However, if the same data are reused for research, for example, in a clinical trial evaluating the effectiveness of an antihypertensive, more precise and standardized measurements methods are needed. From the perspective of secondary use, data are of sufficient quality when they serve the needs of the specific goals of the reuser [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
      <p>To ensure that the data are of high quality, they must meet some fundamental measurable characteristics (eg, data must be complete, correct, and up to date). These characteristics are called data quality dimensions, and several authors have attempted to formulate a complex multidimensional framework of data quality. Kahn et al [<xref ref-type="bibr" rid="ref19">19</xref>] developed a data quality framework containing conformance, completeness, and plausibility as the main data quality dimensions. This framework was the result of 2 stakeholder meetings in which data quality terms and definitions were grouped into an overall conceptual framework. The i~HD (European Institute for Innovation through Health Data) prioritized 9 data quality dimensions as most important to assess the quality of health data [<xref ref-type="bibr" rid="ref20">20</xref>]. These dimensions were selected during a series of workshops with clinical care, clinical research, and ICT leads from 70 European hospitals. In addition, it is well known that there are several published reviews in which the results of individual quality assessment studies were collated into a new single framework of data quality dimensions. However, the results of these reviews have not yet been evaluated. Therefore, answering the “fit for purpose” question and establishing effective methods to assess data quality remain a challenge [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      <p>The primary objective of this review is to provide a thorough overview of data quality frameworks and their associated assessment methods, with a specific focus on the secondary use of health data, as presented in published reviews. As a secondary aim, we seek to align and consolidate the findings into a unified framework that captures the most crucial aspects of quality with a definition along with their corresponding assessment methods and requirements for testing.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>We conducted a review of reviews to gain insights into data quality related to the secondary use of health data. In this review of reviews, we applied the Equator recommendations from the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) guidelines proposed by Page et al [<xref ref-type="bibr" rid="ref22">22</xref>]. As our work is primarily a review of reviews, we included only the items from these guidelines that were applicable. Abstracts were sourced by searching the PubMed, Embase, Web of Science, and SAGE databases. The search was conducted in April 2023, and only reviews published between 1995 and April 2023 were included. We used specific search terms that were aligned with the aim of our study. To ensure comprehensiveness, the search terms were expanded by searching for synonyms and relevant key terms. The following concepts were used: “data quality” or “data accuracy,” combined with “dimensions,” “quality improvement,” “data collection,” “health information interoperability,” “health information systems,” “public health information,” “quality assurance,” and “delivery of health care.” <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> illustrates an example of the search strategy used in PubMed. To ensure the completeness of the review, the literature search spanned multiple databases. All keywords and search queries were adapted and modified to suit the requirements of these various databases (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <boxed-text id="box1" position="float">
          <title>Search query used.</title>
          <p>(“data quality” OR “Data Accuracy”[Mesh]) AND (dimensions OR “Quality Improvement”[Mesh] OR “Data Collection/standards”[Mesh] OR “Health Information Interoperability/standards”[Mesh] OR “Health Information Systems/standards”[Mesh] OR “Public Health Informatics/standards” OR “Quality Assurance, Health Care/standards”[Mesh] OR “Delivery of Health Care/standards”[Mesh]) Filters: Review, Systematic Review</p>
        </boxed-text>
      </sec>
      <sec>
        <title>Inclusion and Exclusion Criteria</title>
        <p>We included review articles that described and discussed frameworks of data quality dimensions and their assessment methods, especially from a secondary use perspective. Reviews were excluded if they were (1) not specifically related to the health care ecosystem, (2) lacked relevant information related to our research objective (no definition of dimensions), or (3) published in languages other than English.</p>
      </sec>
      <sec>
        <title>Selection of Articles</title>
        <p>One reviewer (JD) screened the titles and abstracts of 982 articles from the literature searches and excluded 940 reviews. Two reviewers (RVS and JD) independently performed full-text screening of the remaining 42 reviews. Disagreements between the 2 reviewers were resolved by consulting a third reviewer (DK). After full-text screening, 20 articles were excluded because they did not meet the inclusion criteria. A total of 22 articles were included in this review.</p>
      </sec>
      <sec>
        <title>Data Extraction</title>
        <p>All included articles were imported into EndNote 20 (Clarivate). Data abstraction was conducted independently by 2 reviewers (RVS and JD). Disagreements between the 2 reviewers were resolved by consulting a third reviewer (DK). The information extracted from the reviews included various details, including the authors, publication year, research objectives, specific data source used, scope of secondary use, terminology used for the data quality dimensions, their corresponding definitions, and the measurement methods used.</p>
      </sec>
      <sec>
        <title>Data Synthesis</title>
        <p>To bring clarity to the diverse dimensions and definitions scattered throughout the literature, we labeled the observed definitions of dimensions from the reviews as “aspects.” We then used the framework of the i~HD. This framework underwent extensive validation through a large-scale exercise and was published [<xref ref-type="bibr" rid="ref20">20</xref>]. It will now serve as a reference framework for mapping the diverse literature in the field. This overarching framework comprised 9 loosely delineated data quality dimensions (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, [<xref ref-type="bibr" rid="ref20">20</xref>]). Each observed definition of a data quality dimension was mapped onto a dimension of this reference framework. This mapping process was collaborative and required consensus among the reviewers. This consolidation is intended to offer a more coherent and unified perspective on data quality for secondary use.</p>
        <boxed-text id="box2" position="float">
          <title>Consolidated data quality framework of the European Institute for Innovation through Health Data [<xref ref-type="bibr" rid="ref20">20</xref>].</title>
          <p>
            <bold>Data quality dimension and definition</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Completeness: the extent to which data are present</p>
            </list-item>
            <list-item>
              <p>Consistency: the extent to which data satisfy constraints</p>
            </list-item>
            <list-item>
              <p>Correctness: the extent to which data are true and unbiased</p>
            </list-item>
            <list-item>
              <p>Timeliness: the extent to which data are promptly processed and up to date</p>
            </list-item>
            <list-item>
              <p>Stability: the extent to which data are comparable among sources and over time</p>
            </list-item>
            <list-item>
              <p>Contextualization: the extent to which data are annotated with acquisition context</p>
            </list-item>
            <list-item>
              <p>Representativeness: the extent to which data are representative of intended use</p>
            </list-item>
            <list-item>
              <p>Trustworthiness: the extent to which data can be trusted based on the owner’s reputation</p>
            </list-item>
            <list-item>
              <p>Uniqueness: the extent to which data are not duplicated</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Search Process</title>
        <p><xref rid="figure1" ref-type="fig">Figure 1</xref> summarizes the literature review process and the articles included and excluded at every stage of the review using the PRISMA guidelines. It is important to note that this was not a systematic review of clinical trials; rather, it was an overview of existing reviews. As such, it synthesizes and analyzes the findings from multiple reviews on the topic of interest. A total of 22 articles were included in this review. The 22 reviews included systematic reviews (4/22, 18%) [<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref26">26</xref>], scoping reviews (2/22, 9%) [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], and narrative reviews (16/22, 73%) [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref43">43</xref>]. All the reviews were published between 1995 and 2023. Of the 20 excluded reviews, 5 (25%) were excluded because they were not specific to the health care ecosystem [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref44">44</xref>-<xref ref-type="bibr" rid="ref47">47</xref>], 13 (65%) lacked relevant information related to our research objective [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref18">18</xref>], and 2 (10%) were published in a language other than English [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>].</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>The process of selecting articles.</p>
          </caption>
          <graphic xlink:href="medinform_v12i1e51560_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Sources</title>
        <p>Of the 22 reviews, 10 (45%) discussed data quality pertaining to a registry [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref34">34</xref>-<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref43">43</xref>] and 4 (18%) to a network of EHRs [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Of the 22 reviews, 4 (18%) discussed the quality of public health informatics systems [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref38">38</xref>], real-world data repositories [<xref ref-type="bibr" rid="ref31">31</xref>], and clinical research informatics tools [<xref ref-type="bibr" rid="ref30">30</xref>]. Of the 22 reviews, 4 (18%) did not specify their data source [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>].</p>
      </sec>
      <sec>
        <title>Observed Frameworks for Data Quality Dimensions</title>
        <p>In the initial phase of our study, we conducted a comprehensive review of 22 selected reviews, each presenting a distinct framework for understanding data quality dimensions. Across these reviews, the number of dimensions varied widely, ranging from 1 to 14 (median 4, IQR 2-5). The terminology used was diverse, yielding 23 different terms for dimensions and 62 unique definitions. A detailed overview, including data sources, data quality dimensions, and definitions, is provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref43">43</xref>]. Figure S1 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> presents the frequency of all dimensions in each review along with the variety of definitions associated with each dimension.</p>
      </sec>
      <sec>
        <title>Data Synthesis: Constructing a Consolidated Data Quality Framework For Secondary Use</title>
        <sec>
          <title>Overview</title>
          <p><xref ref-type="table" rid="table1">Table 1</xref> presents all dimensions mentioned in the included reviews, with their definitions, mapped toward each of the 9 data quality dimensions in the framework of i~HD.</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Mapping of data quality aspects toward i~HD (European Institute for Innovation through Health Data) data quality framework.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="280"/>
              <col width="690"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">i~HD data quality dimensions and aspects as mentioned in the reviews</td>
                  <td>Definition</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Completeness</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>The extent to which information is not missing and is of sufficient breadth and depth for the task at hand.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>This focuses on features that describe the frequencies of data attributes present in a data set without reference to data values.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]</td>
                  <td>The extent to which all necessary data that could have been registered have been registered.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td>
                  <td>The extent to which all the incident cases occurring in the population are included in the registry database.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>The completeness of data values can be divided between mandatory and optional data fields.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td>The absence of data at a single moment over time or when measured at multiple moments over time.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref4">4</xref>]</td>
                  <td>Is a truth of a patient present in the EHR<sup>a</sup>?</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>All necessary data are provided.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completeness [<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td>Defined as the presence of recorded data points for each variable.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Plausibility [<xref ref-type="bibr" rid="ref31">31</xref>]</td>
                  <td>Focuses on features that describe the frequencies of data attributes present in a data set without reference to data values.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Capture [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]</td>
                  <td>The extent to which all necessary cases that could have been registered have been registered.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Consistency</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>The accuracy of data values can be divided into syntactic and semantic values.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>Data inconsistencies occur when values in ≥2 data fields are in conflict.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>Representation of data values is the same in all cases.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>Data are logical across data points.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                  <td>The degree to which data have attributes that are free from contradiction and are coherent with other data in a specific content of use.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td>Absence of differences between data items representing the same objects based on specific information requirements.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref30">30</xref>]</td>
                  <td>Refers to the extent to which data are applicable and helpful to the task at hand.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Correctness [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>Data are within the specified value domains.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Comparability [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]</td>
                  <td>The extent to which coding and classification procedures at a registry, together with the definitions of recoding and reporting specific data terms, adhere to the agreed international guidelines.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Validity [<xref ref-type="bibr" rid="ref30">30</xref>]</td>
                  <td>Refers to information that does not conform to a specific format or does not follow business rules.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Concordance [<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                  <td>The data are concordant when there was agreement or comparability between data elements.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Conformance [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]</td>
                  <td>Focuses on data quality features that describe the compliance of the representation of data against internal or external formatting, relational, or computational definitions.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Conformance [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>Whether the values that are present meet syntactic or structural constraints.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Correctness</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]</td>
                  <td>The extent to which registered data are in conformity to the truth.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]</td>
                  <td>The extent to which data are correct and reliable.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td>The degree to which data reveal the truth about the event being described.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>Data conform to a verifiable source.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accuracy [<xref ref-type="bibr" rid="ref30">30</xref>]</td>
                  <td>Refers to the degree to which information accurately reflects an event or object described.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Correctness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>Is an element that is present in the EHR true?</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Correctness [<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>The free-of-error dimension.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Plausibility [<xref ref-type="bibr" rid="ref4">4</xref>]</td>
                  <td>Does an element in the EHR makes sense in the light of other knowledge about what that element is measuring?</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Plausibility [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>This focuses on actual values as a representation of a real-world object or conceptual construct by examining the distribution and density of values or by comparing multiple values that have an expected relationship with each other.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Plausibility [<xref ref-type="bibr" rid="ref29">29</xref>]</td>
                  <td>Focuses on features that describe the believability or truthfulness of data values.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Validity [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]</td>
                  <td>Defined as the proportion of cases in a data set with a given characteristic which truly have the attribute.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Uniqueness</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Redundancy [<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                  <td>Data contain no redundant values.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Stability</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref33">33</xref>]</td>
                  <td>Representations of data values remain the same in multiple data items in multiple locations.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Consistency [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>Refers to the consistency of data at the specified level of detail for the study’s purpose, both within individual databases and across multiple data sets.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Currency [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>Data currency is important for those data fields that involve information that may change over time.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Comparability [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>This is the similarity in data quality and availability for specific data elements used in measure across different entities, such as health plans, physicians, or data sources.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Concordance [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>Is there agreement between elements in the EHR or between the EHR and another data source?</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Information loss and degradation [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>The loss and degradation of information content over time.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Timeliness</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Timeliness [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>The extent to which information is up to date for the task at hand.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Timeliness [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]</td>
                  <td>Related to the rapidity at which a registry can collect, process, and report sufficiently reliable and complete data.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Timeliness [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>Data are available when needed.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Currency [<xref ref-type="bibr" rid="ref4">4</xref>]</td>
                  <td>Is an element in the EHR a relevant representation of the patient’s state at a given point in time?</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Currency [<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                  <td>The degree to which data have attributes that are of the right age in a specific context of use.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Currency [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>Data were considered current if they were recorded in the EHR within a reasonable period following a measurement or if they were representative of the patient’s state at a desired time of interest.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Currency [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td>The degree to which data represent reality from the required point in time.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Accessibility [<xref ref-type="bibr" rid="ref33">33</xref>]</td>
                  <td>The extent to which data are available or easily and quickly retrievable.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Contextualization</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Understandability [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>The ease with which a user can understand the data.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Understandability [<xref ref-type="bibr" rid="ref30">30</xref>]</td>
                  <td>Refers to the degree to which the data can be comprehended.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Contextual validity [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td>Assessment of data quality is dependent on the task at hand.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Flexibility [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td>The extent to which data are expandable, adaptable, and easily applied to many tasks.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Trustworthiness</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Security [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>Personal data are not corrupted, and access is suitably controlled to ensure privacy and confidentiality.</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <bold>Representation</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Relevance [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                  <td>The extent to which information is applicable and helpful for the task at hand.</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Precision [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                  <td>Data value is specific.</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table1fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Completeness</title>
          <p>The first data quality dimension relates to the completeness of data. Among the 22 reviews included, 20 (91%) highlighted the significance of completeness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref43">43</xref>]. Of these 20 reviews, 17 (85%) used the term completeness to refer to this dimension [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref43">43</xref>], whereas the remaining 3 (15%) used the terms plausibility [<xref ref-type="bibr" rid="ref31">31</xref>] and capture [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref35">35</xref>].</p>
          <p>On the basis of the definitions of completeness, we can conclude that this dimension contains 2 main aspects. First, completeness related to the data level. The most used definition related to this aspect is the extent to which information is not missing [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Other reviews focused more on features that describe the frequencies of data attributes present in a data set without reference to data values [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Shivasabesan et al [<xref ref-type="bibr" rid="ref25">25</xref>], for example, defined completeness as the presence of recorded data points for each variable. A second aspect for completeness relates more to a case level, in which all the incident cases occurring in the population are included [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref41">41</xref>].</p>
        </sec>
        <sec>
          <title>Consistency</title>
          <p>The second data quality dimension concerns the consistency of the data. Among the 22 selected reviews, 11 (50%) highlighted the importance of consistency [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Although various frameworks acknowledge this as a crucial aspect of data quality, achieving a consensus on terminology and definition has proven challenging. Notably, some reviews used different terminologies to describe identical concepts associated with consistency [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Of the 11 reviews, 6 (55%) used the term consistency to describe this dimension [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref43">43</xref>], whereas 3 (27%) used conformance [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>] and 2 (18%) referred to comparability [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Of the 11 reviews, 3 (27%) used distinct terms: accuracy [<xref ref-type="bibr" rid="ref43">43</xref>], validity [<xref ref-type="bibr" rid="ref30">30</xref>], and concordance [<xref ref-type="bibr" rid="ref32">32</xref>]. Most definitions focus on data quality features that describe the compliance of the representation of data with internal or external formatting, relational, or computational definitions [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Of the 11 reviews, 2 (18%) provided a specific definition of consistency concerning registry data, concentrating on the extent to which coding and classification procedures, along with the definitions or recording and reporting of specific data terms, adhere to the agreed international guidelines [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Furthermore, Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>] concentrated on whether the values present meet syntactic or structural constraints in their definition, whereas Liaw et al [<xref ref-type="bibr" rid="ref39">39</xref>] defined consistency as the extent to which the representation of data values is consistent across all cases.</p>
        </sec>
        <sec>
          <title>Correctness</title>
          <p>The third data quality dimension relates to the correctness of the data. Of the 22 reviews, 14 (64%) highlighted the importance of correctness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Of the 14 reviews, 2 (14%) used 2 different dimensions to describe the same concept of correctness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Accuracy was the most frequently used term within these frameworks [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. In addition, other terms used included correctness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>], plausibility [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>], and validity [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. In general, this dimension assesses the degree to which the recorded data align with the truth [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], ensuring correctness and reliability [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Of the 14 reviews, 2 (14%) provided a specific definition of correctness concerning EHR data, emphasizing that the element collected is true [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Furthermore, of the 14 reviews, 2 (14%) defined correctness more at a data set level, defining it as the proportion of cases in a data set with a given characteristic that genuinely possess the attribute [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. These reviews specifically referred to this measure as validity. Nevertheless, the use of the term validity was not consistent across the literature; it was also used to define consistency. For instance, AbuHalimeh [<xref ref-type="bibr" rid="ref30">30</xref>] used validity to describe the degree to which information adheres to a predefined format or complies with the established business rules.</p>
        </sec>
        <sec>
          <title>Timeliness</title>
          <p>The fourth data quality dimension concerns the timeliness of the data. Among the 22 selected reviews, 11 (50%) underscored the importance of this data quality dimension [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Of the 11 reviews, 7 (64%) explicitly used the term timeliness [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>], whereas 4 (36%) referred to it as currency [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. Mashoufi et al [<xref ref-type="bibr" rid="ref33">33</xref>] used the terms accessibility and timeliness to explain the same concept. Broadly, timeliness describes how promptly information is processed or how up to date the information is. Most reviews emphasized timeliness as the extent to which information is up to date for the task at hand [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. For instance, Weiskopf and Weng [<xref ref-type="bibr" rid="ref4">4</xref>] provided a specific definition for EHR data, stating that an element should be a relevant representation of the patient’s state at a given point in time. Other reviews defined timeliness as the speed at which data can be collected, processed, and reported [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Similarly, Porgo et al [<xref ref-type="bibr" rid="ref26">26</xref>] defined timeliness as the extent to which data are available when needed.</p>
        </sec>
        <sec>
          <title>Stability</title>
          <p>The fifth data quality dimension concerns the stability of the data. Among the 22 included reviews, 4 (18%) acknowledged the significance of stability [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. The most frequently used terms for this dimension are consistency [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref33">33</xref>] and concordance [<xref ref-type="bibr" rid="ref24">24</xref>]. In addition, other terms used include currency [<xref ref-type="bibr" rid="ref43">43</xref>], comparability [<xref ref-type="bibr" rid="ref24">24</xref>], and information loss and degradation [<xref ref-type="bibr" rid="ref24">24</xref>]. Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>] explored this aspect of data quality by using multiple terminologies to capture its multifaceted nature: stability, consistency, concordance, and information loss and degradation. This dimension, in general, encompasses 2 distinct aspects. First, it underscores the importance of data values that remain consistent across multiple sources and locations [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Alternatively, as described by Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>], it refers to the similarity in data quality for specific data elements used in measurements across different entities, such as health plans, physicians, or other data sources. Second, it addresses temporal changes in data that are collected over time. For instance, Lindquist [<xref ref-type="bibr" rid="ref43">43</xref>] highlighted the importance of stability in data fields that involve information that may change over time. The term consistency is used across different data quality dimensions, but it holds different meanings depending on the context. When discussing the dimension of stability, consistency refers to the comparability of data across different sources. This ensures that information remains uniform when aggregated or compared. Compared with the consistency dimension, the term relates to the internal coherence of data within a single data set, which relates to the absence of contradiction and compliance with certain constraints. The results indicate the same ambiguity in terms of currency. When associated with stability, currency refers to the longitudinal aspect of variables. In contrast, within the dimension of timeliness, currency is concerned with the aspect if data are up to date.</p>
        </sec>
        <sec>
          <title>Contextualization</title>
          <p>The sixth data quality dimension revolves around the context of the data. Of the 22 reviews analyzed, 3 (14%) specifically addressed this aspect within their framework [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. The most used term was understandability [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. In contrast, Syed et al [<xref ref-type="bibr" rid="ref23">23</xref>] used the term contextual validity, and Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>] referred to flexibility and understandability for defining the same concept. Broadly speaking, contextualization pertains to whether the data are annotated with their acquisition context, which is a crucial factor for the correct interpretation of results. As defined by Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>], this dimension relates to the ease with which a user can understand data. In addition, AbuHalimeh [<xref ref-type="bibr" rid="ref30">30</xref>] refers to the degree to which data can be comprehended.</p>
        </sec>
        <sec>
          <title>Representation</title>
          <p>The seventh dimension of data quality focuses on the representation of the data. Of the 22 reviews examined, 3 (14%) specifically highlighted the importance of this dimension [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Of the 3 reviews, 2 (67%) used the term relevance [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>], whereas Porgo et al [<xref ref-type="bibr" rid="ref26">26</xref>] used the term precision. Broadly speaking, representativeness assesses whether the information is applicable and helpful for the task at hand [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. In more specific terms, as defined by Porgo et al [<xref ref-type="bibr" rid="ref26">26</xref>], representativeness relates to the extent to which data values are specific to the task at hand.</p>
        </sec>
        <sec>
          <title>Trustworthiness</title>
          <p>The eighth dimension of data quality relates to the trustworthiness of the data. Of the 22 reviews, only 2 (9%) considered this dimension in their review [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. In both cases, trustworthiness was defined as the extent to which data are free from corruption, and access was appropriately controlled to ensure privacy and confidentiality.</p>
        </sec>
        <sec>
          <title>Uniqueness</title>
          <p>The final dimension of data quality relates to the uniqueness of the data. Of the 22 reviews, only 1 (5%) referred to this aspect [<xref ref-type="bibr" rid="ref32">32</xref>]. Uniqueness is evaluated based on whether there are no duplications or redundant data present in a data set.</p>
        </sec>
      </sec>
      <sec>
        <title>Observed Data Quality Assessment Methods</title>
        <sec>
          <title>Overview</title>
          <p>Of the 22 selected reviews, only 8 (36%) mentioned data quality assessment methods [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>-<xref ref-type="bibr" rid="ref41">41</xref>]. Assessment methods were defined for 15 (65%) of the 23 data quality dimensions. The number of assessment methods per dimension ranged from 1 to 15 (median 3, IQR 1-5). There was no consensus on which method to use for assessing data quality dimensions. Figure S2 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> presents the frequency of the dimensions assessed in each review, along with the number of different data quality assessment methods.</p>
          <p>In the following section, we harmonize these assessment methods with our consolidated framework. This provides a comprehensive overview linking the assessment methods to the primary data quality dimensions from the previous section. <xref ref-type="table" rid="table2">Table 2</xref> provides an overview of all data quality assessment techniques and their definitions. <xref ref-type="boxed-text" rid="box3">Textbox 3</xref> presents an overview of all assessment methods mentioned in the literature and mapped toward the i~HD data quality framework.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Overview of all data quality assessment methods with definitions.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="130"/>
              <col width="260"/>
              <col width="610"/>
              <thead>
                <tr valign="bottom">
                  <td>Assessment M<sup>a</sup></td>
                  <td>Assessment technique in reviews</td>
                  <td>Explanation</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>M1</td>
                  <td>Linkages—other data sets</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Percentage of eligible population included in the data set.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M2</td>
                  <td>Comparison of distributions</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Difference in means and other statistics.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M3</td>
                  <td>Case duplication</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Number and percentage or cases with &#62;1 record.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M4</td>
                  <td>Completeness of variables</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Percentage of cases with complete observations of each variable.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M5</td>
                  <td>Completeness of cases</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Percentage of cases with complete observations for all variables.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M6</td>
                  <td>Distribution comparison</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Distributions or summary statistics of aggregated data from the data set are compared with the expected distributions for the clinical concepts of interest.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M7</td>
                  <td>Gold standard</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>A data set drawn from another source or multiple sources is used as a gold standard.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M8</td>
                  <td>Historic data methods</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Stability of incidence rates over time.</p>
                      </list-item>
                      <list-item>
                        <p>Comparison of incidence rates in different populations.</p>
                      </list-item>
                      <list-item>
                        <p>Shape of age-specific curves.</p>
                      </list-item>
                      <list-item>
                        <p>Incidence rates of childhood curves.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M9</td>
                  <td>M:I<sup>b</sup></td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Comparing the number of deaths, sourced independently from the registry, with the number of new cases recorded for a specific period.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M10</td>
                  <td>Number of sources and notifications per case</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Using many sources reduces the possibility of diagnoses going unreported, thus increasing the completeness of cases.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M11</td>
                  <td>Capture-recapture method</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>A statistical method using multiple independent samples to estimate the size of an entire population.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M12</td>
                  <td>Death certificate method</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>This method requires that death certificate cases can be explicitly identified by the data set and makes use of the M:I ratio to estimate the proportion of the initially unregistered cases.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M13</td>
                  <td>Histological verification of diagnosis</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>The percentage of cases morphologically verified is a measure of the completeness of the diagnostic information.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M14</td>
                  <td>Independent case ascertainment</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Rescreening the sources used to detect any case missing during the registration process.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M15</td>
                  <td>Data element agreement</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Two or more elements within a data set are compared to check if they report the same or compatible information.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M16</td>
                  <td>Data source agreement</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Data from the data set are cross-referenced with another source to check for agreement.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M17</td>
                  <td>Conformance check</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Check the uniqueness of objects that should not be duplicated; the data set agreement with prespecified or additional structural constraints, and the agreement of object concepts and formats granularity between ≥2 data sources.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M18</td>
                  <td>Element presence</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>A determination is made as to whether or not desired or expected data elements are present.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M19</td>
                  <td>Not specified</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Number of consistent values and number of total values.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M20</td>
                  <td>International standards for classification and coding</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>For example, neoplasms, the International Classification of Diseases for Oncology provides coding of topography, morphology, behavior, and grade.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M21</td>
                  <td>Incidence rate</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Not specified</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M22</td>
                  <td>Multiple primaries</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>The extent that a distinction must be made between those that are new cases and those that represent an extension or recurrence of an existing one.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M23</td>
                  <td>Incidental diagnosis</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Screening aims to detect cases that are asymptomatic.</p>
                      </list-item>
                      <list-item>
                        <p>Autopsy diagnosis without any suspicion of diagnosed case before death.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M24</td>
                  <td>Not specified</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>1=ratio of violations of specific consistency type to the total number of consistency checks.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M25</td>
                  <td>Validity check</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Data in the data set are assessed using various techniques that determine of the values “make sense.”</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M26</td>
                  <td>Reabstracting and recoding</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Reabstracting describes the process of independently reabstracting records from a given source, coding the data, and comparing the abstracted and coded data with the information recorded in the database. For each reabstracted data item, the auditor’s codes are compared with the original codes to identify discrepancies.</p>
                      </list-item>
                      <list-item>
                        <p>Recoding involves independently reassigning codes to abstracted text information and evaluating the level of agreement with records already in the database.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M27</td>
                  <td>Missing information</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>The proportion of registered cases with unknown values for various data items.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M28</td>
                  <td>Internal consistency</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>The proportion of registered cases with unknown values for various data items.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M29</td>
                  <td>Domain check</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Proportion of observations outside plausible range (%).</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M30</td>
                  <td>Interrater variability</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Proportion of observations in agreement (%).</p>
                      </list-item>
                      <list-item>
                        <p>Kappa statistics.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M31</td>
                  <td>Log review</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Information on the actual data entry practices (eg, dates, times, and edits) is examined.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M32</td>
                  <td>Syntactic accuracy</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Not specified.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M33</td>
                  <td>Log review</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Information on the actual data entry practices (eg, dates, times, and edits) is examined.</p>
                      </list-item>
                      <list-item>
                        <p>Time at which data are stored in the system.</p>
                      </list-item>
                      <list-item>
                        <p>Time of last update.</p>
                      </list-item>
                      <list-item>
                        <p>User survey.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M34</td>
                  <td>Not specified</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Ratio: number of reports sent on time divided by total reports.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M35</td>
                  <td>Not specified</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Ratio: number of data values divided by the overall number of values.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M36</td>
                  <td>Time to availability</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>The interval between date of diagnosis (or date of incidence) and the date the case was available in the registry or data set.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M37</td>
                  <td>Security analyses</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Analyses of access reports.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>M38</td>
                  <td>Not specified</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Descriptive qualitative measures with group interviews and interpreted with grounded theory.</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>M: method.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>M:I: mortality:incidence ratio.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <boxed-text id="box3" position="float">
            <title>Mapping of assessment methods (Ms) toward data quality framework of the European Institute for Innovation through Health Data.</title>
            <p>
              <bold>Completeness</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Capture [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M1: linkages—other data sets</p>
                  </list-item>
                  <list-item>
                    <p>M2: comparison of distributions</p>
                  </list-item>
                  <list-item>
                    <p>M3: case duplication</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M4: completeness of variables</p>
                  </list-item>
                  <list-item>
                    <p>M5: completeness of cases</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M4: completeness of variables</p>
                  </list-item>
                  <list-item>
                    <p>M6:distribution comparison</p>
                  </list-item>
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M5: completeness of cases</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref34">34</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M8: historic data methods</p>
                  </list-item>
                  <list-item>
                    <p>M9: mortality:incidence ratio (M:I)</p>
                  </list-item>
                  <list-item>
                    <p>M10: number of sources and notifications per case</p>
                  </list-item>
                  <list-item>
                    <p>M11: capture-recapture method</p>
                  </list-item>
                  <list-item>
                    <p>M12: death certificate method</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref41">41</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M8: historic data methods</p>
                  </list-item>
                  <list-item>
                    <p>M9: M:I</p>
                  </list-item>
                  <list-item>
                    <p>M10: number of sources and notifications per case</p>
                  </list-item>
                  <list-item>
                    <p>M11: capture-recapture method</p>
                  </list-item>
                  <list-item>
                    <p>M12: death certificate method</p>
                  </list-item>
                  <list-item>
                    <p>M13: histological verification of diagnosis</p>
                  </list-item>
                  <list-item>
                    <p>M14: independent case ascertainment</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref4">4</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M4: completeness of variables</p>
                  </list-item>
                  <list-item>
                    <p>M6: distribution comparison</p>
                  </list-item>
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M15: data element agreement</p>
                  </list-item>
                  <list-item>
                    <p>M16: data source agreement</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Completeness [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M4: completeness of variables</p>
                  </list-item>
                  <list-item>
                    <p>M6: distribution comparison</p>
                  </list-item>
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M17: conformance check</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Consistency</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Conformance [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M18: element presence</p>
                  </list-item>
                  <list-item>
                    <p>M17: conformance check</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Concordance [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M15: data element agreement</p>
                  </list-item>
                  <list-item>
                    <p>M19: not specified</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Consistency [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M16: data source agreement</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Comparability [<xref ref-type="bibr" rid="ref40">40</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M20: international standards for classification and coding</p>
                  </list-item>
                  <list-item>
                    <p>M21: incidence rate</p>
                  </list-item>
                  <list-item>
                    <p>M22: multiple primaries</p>
                  </list-item>
                  <list-item>
                    <p>M23: incidental diagnosis</p>
                  </list-item>
                  <list-item>
                    <p>M24: not specified</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Comparability [<xref ref-type="bibr" rid="ref34">34</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M20: international standards for classification and coding</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Consistency [<xref ref-type="bibr" rid="ref39">39</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M24: not specified</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Correctness</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Correctness [<xref ref-type="bibr" rid="ref4">4</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M15: data element agreement</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Plausibility [<xref ref-type="bibr" rid="ref4">4</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M6: distribution comparison</p>
                  </list-item>
                  <list-item>
                    <p>M25: validity check</p>
                  </list-item>
                  <list-item>
                    <p>M31: log review</p>
                  </list-item>
                  <list-item>
                    <p>M16: data source agreement</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Validity [<xref ref-type="bibr" rid="ref40">40</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M26: reabstracting and recoding</p>
                  </list-item>
                  <list-item>
                    <p>M13: histological verification of diagnosis</p>
                  </list-item>
                  <list-item>
                    <p>M27: missing information</p>
                  </list-item>
                  <list-item>
                    <p>M28: internal consistency</p>
                  </list-item>
                  <list-item>
                    <p>M12: death certificate method</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Validity [<xref ref-type="bibr" rid="ref34">34</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M13: histological verification of diagnosis</p>
                  </list-item>
                  <list-item>
                    <p>M12: death certificate method</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Accuracy [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M28: internal consistency</p>
                  </list-item>
                  <list-item>
                    <p>M29: domain check</p>
                  </list-item>
                  <list-item>
                    <p>M30: interrater variability</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Correctness [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M25: validity check</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Accuracy [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M7: gold standard</p>
                  </list-item>
                  <list-item>
                    <p>M32: syntactic accuracy</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Stability</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Concordance [<xref ref-type="bibr" rid="ref4">4</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M15: data element agreement</p>
                  </list-item>
                  <list-item>
                    <p>M16: data source agreement</p>
                  </list-item>
                  <list-item>
                    <p>M6: distribution comparison</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Comparability [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M18: element presence</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Consistency [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M17: conformance check</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Consistency [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M15: data element agreement</p>
                  </list-item>
                  <list-item>
                    <p>M16: data source agreement</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Timeliness</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Currency [<xref ref-type="bibr" rid="ref32">32</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M33: log review</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Currency [<xref ref-type="bibr" rid="ref4">4</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M33: log review</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Timeliness [<xref ref-type="bibr" rid="ref39">39</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M34: not specified</p>
                  </list-item>
                  <list-item>
                    <p>M35: not specified</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Currency [<xref ref-type="bibr" rid="ref24">24</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M18: element presence</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Timeliness [<xref ref-type="bibr" rid="ref40">40</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M36: time to availability</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Trustworthiness</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Security [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M37: security analyses</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Representation</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Relevance [<xref ref-type="bibr" rid="ref39">39</xref>]</p>
                <list list-type="bullet">
                  <list-item>
                    <p>M38: not specified</p>
                  </list-item>
                </list>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>Completeness</title>
          <p>Among the 20 reviews that defined data quality dimensions related to completeness, 6 (30%) incorporated data quality assessment methods into their framework [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. These 6 reviews collectively introduced 17 different data quality assessment methods. Some reviews (4/6, 67%) mentioned multiple methods to evaluate completeness, which highlights the absence of a consensus within the literature regarding the most suitable approach. The most frequently used method in the literature for assessing completeness was the examination of variable completeness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. This method involved calculating the percentage of cases that had complete observations for each variable within the data set. In 3 reviews [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>], researchers opted to compare the distributions or summary statistics of aggregated data from the data set with the expected distributions for the clinical concepts of interest. Another approach found in 3 reviews involved the use of a gold standard to evaluate completeness [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. This method relied on external knowledge and entailed comparing the data set under examination with data drawn from other sources or multiple sources.</p>
        </sec>
        <sec>
          <title>Consistency</title>
          <p>Among the 15 reviews highlighting the significance of consistency, 6 (40%) defined data quality assessment methods [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. In these 6 reviews, a total of 10 distinct data quality assessment methods were defined. The most used method involved calculating the ratio of violations of specific consistency types to the total number of consistency checks [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. There were 2 categories established for this assessment. First, internal consistency, which focuses on the most commonly used data type, format, or label within the data set. Second, external consistency, which centered on whether data types, formats, or labels could be mapped to a relevant reference terminology or data dictionary. Another common assessment method was the implementation of international standards for classification and coding standards [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. This addressed specific oncology and suggested coding for topography, morphology, behavior, and grade. Liaw et al [<xref ref-type="bibr" rid="ref39">39</xref>] defined an assessment method in which ≥2 elements within a data set are compared to check if they report compatible information.</p>
        </sec>
        <sec>
          <title>Correctness</title>
          <p>Among the 16 reviews underscoring the importance of correctness, 6 (38%) detailed data quality assessment methods [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Collectively, these 6 reviews proposed 15 different techniques. Prominent among these were histological verification [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>], where the percentage of morphologically verified values served as an indicator of diagnosis correctness. Another frequently used technique was the use of validity checks [<xref ref-type="bibr" rid="ref4">4</xref>], involving various methods to assess whether the data set values “make sense.” Three additional reviews opted for a comparative approach, benchmarking data against a gold standard and calculating the sensitivity, specificity, and accuracy scores [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Interestingly, there is an overlap between consistency and completeness as data quality dimensions in the assessment of correctness. For instance, Weiskopf and Weng [<xref ref-type="bibr" rid="ref4">4</xref>] defined data element agreement as an assessment for this dimension, whereas Bray and Parkin [<xref ref-type="bibr" rid="ref40">40</xref>] evaluated the proportion of registered cases with unknown values for specific items as a correctness assessment method.</p>
        </sec>
        <sec>
          <title>Stability</title>
          <p>Among the 7 reviews emphasizing the importance of stability of the data, only 3 (43%) discussed assessment techniques that address this dimension [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. These 3 reviews collectively outlined 5 different techniques. Notably, there was no predominant technique. Specifically, Weiskopf and Weng [<xref ref-type="bibr" rid="ref4">4</xref>] used several techniques to assess data stability, including an overlap with other dimensions, by using data element agreement. Another technique introduced in the same review was data source agreement, involving the comparison of data from different data sets from distinct sources.</p>
        </sec>
        <sec>
          <title>Timeliness</title>
          <p>Of the 12 reviews focusing on the timeliness of data, 5 (42%) delved into assessment techniques for this data quality dimension [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Across these reviews, 5 distinct assessment techniques were discussed. The most commonly used technique was the use of a log review [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. This method involved collecting information that provides details on data entry, the time of data storage, the last update of the data, or when the data were accessed. In addition, Bray and Parkin [<xref ref-type="bibr" rid="ref40">40</xref>] assessed timeliness by calculating the interval between the date of diagnosis (or date of incidence) and the date the case was available in the registry or data set.</p>
        </sec>
        <sec>
          <title>Trustworthiness</title>
          <p>In the 2 reviews that considered trustworthiness as a data quality dimension, both used the same assessment technique [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. This method involves the analysis of access reports as a security analysis, providing insight into the trustworthiness of the data.</p>
        </sec>
        <sec>
          <title>Representation</title>
          <p>In 1 review that addressed the representation dimension as a data quality aspect, only 1 assessment method was mentioned. Liaw et al [<xref ref-type="bibr" rid="ref39">39</xref>] introduced descriptive qualitative measures through group interviews to determine whether the data accurately represented the intended use.</p>
        </sec>
        <sec>
          <title>Uniqueness and Contextualization</title>
          <p>No assessment methods were mentioned for these data quality dimensions.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This first review of reviews regarding the quality of health data for secondary use offers an overview of the frameworks of data quality dimensions and their assessment methods, as presented in published reviews. There is no consensus in the literature on the specific terminology and definitions of terms. Similarly, the methodologies used to assess these terms vary widely and are often not described in sufficient detail. Comparability, plausibility, validity, and concordance are the 4 aspects classified under different consolidated dimensions, depending on their definitions. This variability underscores the prevailing discrepancies and the urgent need for harmonized definitions. Almost none of the reviews explicitly refer to requirements of quality for the context of the data collection. Building on the insights gathered from these reviews, our consolidated framework organizes the numerous observed definitions into 9 main data quality dimensions, aiming to bring coherence to the fragmented landscape.</p>
        <p>Health data in primary sources refer to data produced in the process of providing real-time and direct care to an individual [<xref ref-type="bibr" rid="ref50">50</xref>], with the purpose of improving the care process. A secondary source captures data collected by someone other than the primary user and can be used for other purposes (eg, research, quality measurement, and public health) [<xref ref-type="bibr" rid="ref50">50</xref>]. The included reviews discussed data quality for secondary use. However, the quality of health data in secondary systems is a function of the primary sources from which they originate, the quality of the process to transfer and transform the primary data to the secondary source, and the quality of the secondary source itself. The transfer and transformation of primary data to secondary sources implies the standardization, aggregation, and streamlining of health data. This can be considered as an export-transform-load (ETL) process with its own data quality implications. When discussing data quality dimensions and assessment methods, research should consider these different stages within the data life cycle, a distinction seldom made in the literature. For example, Prang et al [<xref ref-type="bibr" rid="ref27">27</xref>] defined completeness within the context of a registry, which can be regarded as a secondary source. In this context, completeness was defined as the degree to which all potentially registrable data had been registered. The definition for completeness by Bian et al [<xref ref-type="bibr" rid="ref24">24</xref>] pertains to an EHR, which is considered a primary source. Here, the emphasis was on describing the frequencies of data attributes. Both papers emphasized the importance of completeness, but they approached this dimension from different perspectives within the data life cycle.</p>
        <p>This fragmented landscape regarding terminology and definition of data quality dimensions, the lack of distinction between quality in primary and secondary data and in the ETL process, and the lack of consideration for the context allows room for interpretation, leading to difficulties in developing assessment methods. In our included articles, only 8 (36%) out of 22 reviews mentioned and defined assessment methods [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>-<xref ref-type="bibr" rid="ref41">41</xref>]. However, the results showed that the described assessment methods are limited by a lack of well-defined and standardized metrics that can quantitatively or qualitatively measure the quality of data across various dimensions and often suffer from inadequate translation of these dimensions into explicit requirements for primary and secondary data and the ETL process, considering the purpose of the data collection of the secondary source. Both the DAMA and ISO emphasize in their definition of data quality that requirements serve as the translation of dimensions. Data quality dimensions refer to a broad context or characteristics of data that are used to assess the quality of data. Data quality requirements are derived from data quality dimensions and specify the specific criteria or standards that data must meet to be considered high-quality data. These requirements define the specific thresholds that need to be achieved for each dimension. However, our results show that the focus of the literature lies in defining dimensions and frameworks, rather than adequately developing these essential data quality requirements.</p>
        <p>To avoid further problems and ambiguities, it is important to understand the purpose, context, and limitations of the data and data sources to establish a comprehensive view on the quality of the data. Rather than pursuing an elusive quest in the literature for a rigid framework defined by a fixed number of dimensions and precise definitions, future research should shift its focus toward defining and developing specific data quality requirements tailored to each use case. This approach should consider various stages within the data life cycle. For example, when defining a specific completeness requirement for a secondary use case, it will impact the way data are generated at the primary source and how they are transformed and transferred between the primary and secondary sources. Creating explicit requirements that align with the purpose of each use case along with well-defined criteria and thresholds can foster the development of precise assessment methods for each dimension. Moreover, formulating these use case requirements will facilitate addressing the fundamental question of whether health data are fit for purpose, thus determining if they are of a sufficient quality.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The strength of a review of reviews methodology is to provide a comprehensive overview of the current state of knowledge. However, it is important to acknowledge that this approach may have limitations, particularly in identifying new studies that have not yet undergone review or inclusion in the existing body of literature. Terms such as “information quality,” “error check,” “data check,” “data validation,” and “data cleaning” are commonly associated with the concept of data quality, particularly in older research papers. However, we did not include these terms in our search query because subsequent checking using these terms did not reveal any additional reviews that met our inclusion criteria. Furthermore, this overview focused on published reviews. Important information can also be found in grey literature [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>] and in studies that collect stakeholders’ opinions on the quality of health data [<xref ref-type="bibr" rid="ref20">20</xref>]. Finally, none of the included reviews discussed patient-generated data or data generated by wearables. Given the increasing adoption and use of these sources in health care, it is becoming important to consider their impact on data quality. Developing assessment methods that are applicable to these emerging data sources is an important area for further research.</p>
        <p>Although having a consolidated reference framework of data quality dimensions and aspects is valuable, it is also of great importance to define specific data quality requirements for each relevant aspect within a single quality dimension. These requirements should specify the desired quality level to be achieved in a given percentage of the primary sources, based on the purpose of the data collection or a particular real-world data study. Once these requirements are clearly articulated, appropriate measurement methods can be determined, thereby ensuring the comprehensive analysis of secondary data collection for its suitability for a specific purpose.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The absence of a consensus in the literature regarding the precise terminology and definitions of data quality dimensions has resulted in ambiguity and challenges in creating specific assessment methods. This review of reviews offers an overview of data quality dimensions, along with the definitions and assessment methods used in these reviews. This study goes a step further by assigning all observed definitions to a consolidated framework of 9 data quality dimensions. Further research is needed to complete the collection of aspects within each quality dimension, with the elaboration of a full set of assessment methods, and the establishment of specific requirements to evaluate the suitability for the purpose of secondary data collection systems.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Search items by database.</p>
        <media xlink:href="medinform_v12i1e51560_app1.docx" xlink:title="DOCX File , 21 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Data sources, data quality aspects, and definitions reported in the 22 publications included in the review.</p>
        <media xlink:href="medinform_v12i1e51560_app2.docx" xlink:title="DOCX File , 46 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>The frequency of all dimensions with definitions in each review and assessment methods per dimension.</p>
        <media xlink:href="medinform_v12i1e51560_app3.docx" xlink:title="DOCX File , 169 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) checklist.</p>
        <media xlink:href="medinform_v12i1e51560_app4.pdf" xlink:title="PDF File  (Adobe PDF File), 65 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">ETL</term>
          <def>
            <p>export-transform-load</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">i~HD</term>
          <def>
            <p>European Institute for Innovation through Health Data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">ISO</term>
          <def>
            <p>International Organization for Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <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>Duncan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Eden</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Synthesizing dimensions of digital maturity in hospitals: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>03</month>
          <day>30</day>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>e32994</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/3/e32994/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32994</pub-id>
          <pub-id pub-id-type="medline">35353050</pub-id>
          <pub-id pub-id-type="pii">v24i3e32994</pub-id>
          <pub-id pub-id-type="pmcid">PMC9008527</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>Eden</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Burton-Jones</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Staib</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Effects of eHealth on hospital practice: synthesis of the current literature</article-title>
          <source>Aust Health Rev</source>
          <year>2018</year>
          <month>09</month>
          <volume>42</volume>
          <issue>5</issue>
          <fpage>568</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.1071/AH17255</pub-id>
          <pub-id pub-id-type="medline">29986809</pub-id>
          <pub-id pub-id-type="pii">AH17255</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>Zheng</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Abraham</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Novak</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Reynolds</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Gettinger</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A survey of the literature on unintended consequences associated with health information technology: 2014–2015</article-title>
          <source>Yearb Med Inform</source>
          <year>2018</year>
          <month>03</month>
          <day>06</day>
          <volume>25</volume>
          <issue>01</issue>
          <fpage>13</fpage>
          <lpage>29</lpage>
          <pub-id pub-id-type="doi">10.15265/iy-2016-036</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>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="https://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="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Feder</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Data quality in electronic health records research: quality domains and assessment methods</article-title>
          <source>West J Nurs Res</source>
          <year>2018</year>
          <month>05</month>
          <volume>40</volume>
          <issue>5</issue>
          <fpage>753</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1177/0193945916689084</pub-id>
          <pub-id pub-id-type="medline">28322657</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>Bell</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Delbanco</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Elmore</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzgerald</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Fossa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Harcourt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Leveille</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Stametz</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>DesRoches</surname>
              <given-names>CM</given-names>
            </name>
          </person-group>
          <article-title>Frequency and types of patient-reported errors in electronic health record ambulatory care notes</article-title>
          <source>JAMA Netw Open</source>
          <year>2020</year>
          <month>06</month>
          <day>01</day>
          <volume>3</volume>
          <issue>6</issue>
          <fpage>e205867</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32515797"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2020.5867</pub-id>
          <pub-id pub-id-type="medline">32515797</pub-id>
          <pub-id pub-id-type="pii">2766834</pub-id>
          <pub-id pub-id-type="pmcid">PMC7284300</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weir</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Hurdle</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Felgar</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffman</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Roth</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nebeker</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>Direct text entry in electronic progress notes. An evaluation of input errors</article-title>
          <source>Methods Inf Med</source>
          <year>2003</year>
          <volume>42</volume>
          <issue>1</issue>
          <fpage>61</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="medline">12695797</pub-id>
          <pub-id pub-id-type="pii">03010061</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Suresh</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Don't believe everything you read in the patient's chart</article-title>
          <source>Pediatrics</source>
          <year>2003</year>
          <month>05</month>
          <volume>111</volume>
          <issue>5 Pt 1</issue>
          <fpage>1108</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1542/peds.111.5.1108</pub-id>
          <pub-id pub-id-type="medline">12728099</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>Kaboli</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>McClimon</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hoth</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Barnett</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Assessing the accuracy of computerized medication histories</article-title>
          <source>Am J Manag Care</source>
          <year>2004</year>
          <month>11</month>
          <volume>10</volume>
          <issue>11 Pt 2</issue>
          <fpage>872</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ajmc.com/pubMed.php?pii=2762"/>
          </comment>
          <pub-id pub-id-type="medline">15609741</pub-id>
          <pub-id pub-id-type="pii">2762</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Staroselsky</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Volk</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Tsurikova</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Newmark</surname>
              <given-names>LP</given-names>
            </name>
            <name name-style="western">
              <surname>Lippincott</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Litvak</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kittler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wald</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>An effort to improve electronic health record medication list accuracy between visits: patients' and physicians' response</article-title>
          <source>Int J Med Inform</source>
          <year>2008</year>
          <month>03</month>
          <volume>77</volume>
          <issue>3</issue>
          <fpage>153</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2007.03.001</pub-id>
          <pub-id pub-id-type="medline">17434337</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(07)00047-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yadav</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kazanji</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Paudel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Falatko</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shoichet</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Maddens</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Narayan</surname>
              <given-names>KC</given-names>
            </name>
          </person-group>
          <article-title>Comparison of accuracy of physical examination findings in initial progress notes between paper charts and a newly implemented electronic health record</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>01</month>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>140</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27357831"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw067</pub-id>
          <pub-id pub-id-type="medline">27357831</pub-id>
          <pub-id pub-id-type="pii">ocw067</pub-id>
          <pub-id pub-id-type="pmcid">PMC7654088</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Darko-Yawson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ellingsen</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Assessing and improving EHRs data quality through a socio-technical approach</article-title>
          <source>Procedia Comput Sci</source>
          <year>2016</year>
          <volume>98</volume>
          <fpage>243</fpage>
          <lpage>50</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2016.09.039</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Penning</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zozus</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Analysis of anesthesia screens for rule-based data quality assessment opportunities</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <volume>257</volume>
          <fpage>473</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30741242"/>
          </comment>
          <pub-id pub-id-type="medline">30741242</pub-id>
          <pub-id pub-id-type="pmcid">PMC6692112</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>Puttkammer</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Baseman</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Devine</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Valles</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Hyppolite</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Garilus</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Honoré</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Matheson</surname>
              <given-names>AI</given-names>
            </name>
            <name name-style="western">
              <surname>Zeliadt</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yuhas</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sherr</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cadet</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Zamor</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Pierre</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Barnhart</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>An assessment of data quality in a multi-site electronic medical record system in Haiti</article-title>
          <source>Int J Med Inform</source>
          <year>2016</year>
          <month>02</month>
          <volume>86</volume>
          <fpage>104</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.11.003</pub-id>
          <pub-id pub-id-type="medline">26620698</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(15)30055-1</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>Wiebe</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shaheen</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Eastwood</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Boussat</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Quan</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Indicators of missing Electronic Medical Record (EMR) discharge summaries: a retrospective study on Canadian data</article-title>
          <source>Int J Popul Data Sci</source>
          <year>2020</year>
          <month>12</month>
          <day>11</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>1352</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34007880"/>
          </comment>
          <pub-id pub-id-type="doi">10.23889/ijpds.v5i3.1352</pub-id>
          <pub-id pub-id-type="medline">34007880</pub-id>
          <pub-id pub-id-type="pii">S239949082001352X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8104063</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>von Lucadou</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ganslandt</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Prokosch</surname>
              <given-names>HU</given-names>
            </name>
            <name name-style="western">
              <surname>Toddenroth</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Feasibility analysis of conducting observational studies with the electronic health record</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>10</month>
          <day>28</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>202</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-019-0939-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0939-0</pub-id>
          <pub-id pub-id-type="medline">31660955</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0939-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC6819452</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Juran</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Gryna</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Bingham</surname>
              <given-names>RS</given-names>
            </name>
          </person-group>
          <source>Quality Control Handbook</source>
          <year>1974</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>McGraw-Hill</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ehrlinger</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wöß</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>A survey of data quality measurement and monitoring tools</article-title>
          <source>Front Big Data</source>
          <year>2022</year>
          <volume>5</volume>
          <fpage>850611</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35434611"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdata.2022.850611</pub-id>
          <pub-id pub-id-type="medline">35434611</pub-id>
          <pub-id pub-id-type="pmcid">PMC9009315</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>1244</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://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="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aerts</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kalra</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Saez</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ramírez-Anguita</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Mayer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia-Gomez</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hernández</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Thienpont</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Coorevits</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Is the quality of hospital EHR data sufficient to evidence its ICHOM outcomes performance in heart failure? A pilot evaluation</article-title>
          <source>medRxiv. Preprint posted online February 5, 2021</source>
          <year>2021</year>
          <pub-id pub-id-type="doi">10.1101/2021.02.04.21250990</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ge</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Helfert</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A review of information quality research - develop a research agenda</article-title>
          <source>Proceedings of the 2007 MIT International Conference on Information Quality</source>
          <year>2007</year>
          <conf-name>MIT ICIQ '07</conf-name>
          <conf-date>November 9-11, 2007</conf-date>
          <conf-loc>Cambridge, MA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mitiq.mit.edu/iciq/pdf/a%20review%20of%20information%20quality%20research.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Bossuyt</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Mulrow</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Shamseer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Glanville</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grimshaw</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hróbjartsson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lalu</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loder</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo-Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Welch</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Whiting</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title>
          <source>BMJ</source>
          <year>2021</year>
          <month>03</month>
          <day>29</day>
          <volume>372</volume>
          <fpage>n71</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33782057"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.n71</pub-id>
          <pub-id pub-id-type="medline">33782057</pub-id>
          <pub-id pub-id-type="pmcid">PMC8005924</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Syed</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Eden</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Makasi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Chukwudi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Mamudu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kamalpour</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kapugama Geeganage</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sadeghianasl</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Leemans</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Goel</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Andrews</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wynn</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Ter Hofstede</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Myers</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Digital health data quality issues: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>03</month>
          <day>31</day>
          <volume>25</volume>
          <fpage>e42615</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e42615/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/42615</pub-id>
          <pub-id pub-id-type="medline">37000497</pub-id>
          <pub-id pub-id-type="pii">v25i1e42615</pub-id>
          <pub-id pub-id-type="pmcid">PMC10131725</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lyu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loiacono</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Viramontes</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Lipori</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Prosperi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>George</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Harle</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Shenkman</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Assessing the practice of data quality evaluation in a national clinical data research network through a systematic scoping review in the era of real-world data</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>12</month>
          <day>09</day>
          <volume>27</volume>
          <issue>12</issue>
          <fpage>1999</fpage>
          <lpage>2010</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33166397"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa245</pub-id>
          <pub-id pub-id-type="medline">33166397</pub-id>
          <pub-id pub-id-type="pii">5964088</pub-id>
          <pub-id pub-id-type="pmcid">PMC7727392</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>Shivasabesan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>O'Reilly</surname>
              <given-names>GM</given-names>
            </name>
          </person-group>
          <article-title>Missing data in trauma registries: a systematic review</article-title>
          <source>Injury</source>
          <year>2018</year>
          <month>09</month>
          <volume>49</volume>
          <issue>9</issue>
          <fpage>1641</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.injury.2018.03.035</pub-id>
          <pub-id pub-id-type="medline">29678306</pub-id>
          <pub-id pub-id-type="pii">S0020-1383(18)30164-5</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>Porgo</surname>
              <given-names>TV</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tardif</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Evidence of data quality in trauma registries: a systematic review</article-title>
          <source>J Trauma Acute Care Surg</source>
          <year>2016</year>
          <month>04</month>
          <volume>80</volume>
          <issue>4</issue>
          <fpage>648</fpage>
          <lpage>58</lpage>
          <pub-id pub-id-type="doi">10.1097/TA.0000000000000970</pub-id>
          <pub-id pub-id-type="medline">26881490</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>Prang</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Karanatsios</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Verbunt</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Yeung</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kelaher</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gibbs</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Clinical registries data quality attributes to support registry-based randomised controlled trials: a scoping review</article-title>
          <source>Contemp Clin Trials</source>
          <year>2022</year>
          <month>08</month>
          <volume>119</volume>
          <fpage>106843</fpage>
          <pub-id pub-id-type="doi">10.1016/j.cct.2022.106843</pub-id>
          <pub-id pub-id-type="medline">35792338</pub-id>
          <pub-id pub-id-type="pii">S1551-7144(22)00169-0</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>Nesca</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lix</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A scoping review of preprocessing methods for unstructured text data to assess data quality</article-title>
          <source>Int J Popul Data Sci</source>
          <year>2022</year>
          <month>10</month>
          <day>05</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ijpds.org/article/view/1757/4104"/>
          </comment>
          <pub-id pub-id-type="doi">10.23889/ijpds.v7i1.1757</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>Ozonze</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hopgood</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Automating electronic health record data quality assessment</article-title>
          <source>J Med Syst</source>
          <year>2023</year>
          <month>02</month>
          <day>13</day>
          <volume>47</volume>
          <issue>1</issue>
          <fpage>23</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36781551"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-022-01892-2</pub-id>
          <pub-id pub-id-type="medline">36781551</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-022-01892-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC9925537</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>AbuHalimeh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Improving data quality in clinical research informatics tools</article-title>
          <source>Front Big Data</source>
          <year>2022</year>
          <volume>5</volume>
          <fpage>871897</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35574572"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdata.2022.871897</pub-id>
          <pub-id pub-id-type="medline">35574572</pub-id>
          <pub-id pub-id-type="pmcid">PMC9102971</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>Liaw</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Ansari</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jonnagaddala</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Godinho</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Borelli</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>de Lusignan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Capurro</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liyanage</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattal</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kahn</surname>
              <given-names>MG</given-names>
            </name>
          </person-group>
          <article-title>Quality assessment of real-world data repositories across the data life cycle: a literature review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <month>07</month>
          <day>14</day>
          <volume>28</volume>
          <issue>7</issue>
          <fpage>1591</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33496785"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa340</pub-id>
          <pub-id pub-id-type="medline">33496785</pub-id>
          <pub-id pub-id-type="pii">6120399</pub-id>
          <pub-id pub-id-type="pmcid">PMC8475229</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>Rajan</surname>
              <given-names>NS</given-names>
            </name>
            <name name-style="western">
              <surname>Gouripeddi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Madsen</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Facelli</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Towards a content agnostic computable knowledge repository for data quality assessment</article-title>
          <source>Comput Methods Programs Biomed</source>
          <year>2019</year>
          <month>08</month>
          <volume>177</volume>
          <fpage>193</fpage>
          <lpage>201</lpage>
          <pub-id pub-id-type="doi">10.1016/j.cmpb.2019.05.017</pub-id>
          <pub-id pub-id-type="medline">31319948</pub-id>
          <pub-id pub-id-type="pii">S0169-2607(18)30625-4</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>Mashoufi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ayatollahi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Khorasani-Zavareh</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A review of data quality assessment in emergency medical services</article-title>
          <source>Open Med Inform J</source>
          <year>2018</year>
          <month>05</month>
          <day>31</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29997708"/>
          </comment>
          <pub-id pub-id-type="doi">10.2174/1874431101812010019</pub-id>
          <pub-id pub-id-type="medline">29997708</pub-id>
          <pub-id pub-id-type="pii">TOMINFOJ-12-19</pub-id>
          <pub-id pub-id-type="pmcid">PMC5997849</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>Fung</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>SBL</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ho</surname>
              <given-names>WY</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>BG</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>KY</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>HP</given-names>
            </name>
          </person-group>
          <article-title>Data quality at the Singapore cancer registry: an overview of comparability, completeness, validity and timeliness</article-title>
          <source>Cancer Epidemiol</source>
          <year>2016</year>
          <month>08</month>
          <volume>43</volume>
          <fpage>76</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1016/j.canep.2016.06.006</pub-id>
          <pub-id pub-id-type="medline">27399312</pub-id>
          <pub-id pub-id-type="pii">S1877-7821(16)30077-7</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>O'Reilly</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Gabbe</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Classifying, measuring and improving the quality of data in trauma registries: a review of the literature</article-title>
          <source>Injury</source>
          <year>2016</year>
          <month>03</month>
          <volume>47</volume>
          <issue>3</issue>
          <fpage>559</fpage>
          <lpage>67</lpage>
          <pub-id pub-id-type="doi">10.1016/j.injury.2016.01.007</pub-id>
          <pub-id pub-id-type="medline">26830127</pub-id>
          <pub-id pub-id-type="pii">S0020-1383(16)00009-7</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>Stausberg</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nasseh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nonnemacher</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Measuring data quality: a review of the literature between 2005 and 2013</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2015</year>
          <volume>210</volume>
          <fpage>712</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">25991245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hailey</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Methods for assessing the quality of data in public health information systems: a critical review</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2014</year>
          <volume>204</volume>
          <fpage>13</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">25087521</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hailey</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A review of data quality assessment methods for public health information systems</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2014</year>
          <month>05</month>
          <day>14</day>
          <volume>11</volume>
          <issue>5</issue>
          <fpage>5170</fpage>
          <lpage>207</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph110505170"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph110505170</pub-id>
          <pub-id pub-id-type="medline">24830450</pub-id>
          <pub-id pub-id-type="pii">ijerph110505170</pub-id>
          <pub-id pub-id-type="pmcid">PMC4053886</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liaw</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Rahimi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ray</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Taggart</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dennis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>de Lusignan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jalaludin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Yeo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Talaei-Khoei</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Towards an ontology for data quality in integrated chronic disease management: a realist review of the literature</article-title>
          <source>Int J Med Inform</source>
          <year>2013</year>
          <month>01</month>
          <volume>82</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2012.10.001</pub-id>
          <pub-id pub-id-type="medline">23122633</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(12)00193-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bray</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Parkin</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of data quality in the cancer registry: principles and methods. Part I: comparability, validity and timeliness</article-title>
          <source>Eur J Cancer</source>
          <year>2009</year>
          <month>03</month>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>747</fpage>
          <lpage>55</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ejca.2008.11.032</pub-id>
          <pub-id pub-id-type="medline">19117750</pub-id>
          <pub-id pub-id-type="pii">S0959-8049(08)00920-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parkin</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Bray</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of data quality in the cancer registry: principles and methods Part II. Completeness</article-title>
          <source>Eur J Cancer</source>
          <year>2009</year>
          <month>03</month>
          <volume>45</volume>
          <issue>5</issue>
          <fpage>756</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ejca.2008.11.033</pub-id>
          <pub-id pub-id-type="medline">19128954</pub-id>
          <pub-id pub-id-type="pii">S0959-8049(08)00919-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arts</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>De Keizer</surname>
              <given-names>NF</given-names>
            </name>
            <name name-style="western">
              <surname>Scheffer</surname>
              <given-names>GJ</given-names>
            </name>
          </person-group>
          <article-title>Defining and improving data quality in medical registries: a literature review, case study, and generic framework</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2002</year>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>600</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/12386111"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.m1087</pub-id>
          <pub-id pub-id-type="medline">12386111</pub-id>
          <pub-id pub-id-type="pmcid">PMC349377</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lindquist</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Data quality management in pharmacovigilance</article-title>
          <source>Drug Saf</source>
          <year>2004</year>
          <volume>27</volume>
          <issue>12</issue>
          <fpage>857</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.2165/00002018-200427120-00003</pub-id>
          <pub-id pub-id-type="medline">15366974</pub-id>
          <pub-id pub-id-type="pii">27123</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haug</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Understanding the differences across data quality classifications: a literature review and guidelines for future research</article-title>
          <source>Ind Manag Data Syst</source>
          <year>2021</year>
          <month>08</month>
          <day>24</day>
          <volume>121</volume>
          <issue>12</issue>
          <fpage>2651</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.1108/imds-12-2020-0756</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Triki</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Bshary</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A proposal to enhance data quality and FAIRness</article-title>
          <source>Ethol</source>
          <year>2022</year>
          <month>08</month>
          <day>02</day>
          <volume>128</volume>
          <issue>9</issue>
          <fpage>647</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1111/eth.13320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Šlibar</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Oreški</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Begičević Ređep</surname>
              <given-names>NB</given-names>
            </name>
          </person-group>
          <article-title>Importance of the open data assessment: an insight into the (meta) data quality dimensions</article-title>
          <source>SAGE Open</source>
          <year>2021</year>
          <month>06</month>
          <day>15</day>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>215824402110231</fpage>
          <pub-id pub-id-type="doi">10.1177/21582440211023178</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Verma</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Data quality and clinical audit</article-title>
          <source>Intensive Care Med</source>
          <year>2012</year>
          <month>8</month>
          <volume>13</volume>
          <issue>8</issue>
          <fpage>397</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/j.mpaic.2012.05.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lima</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Schramm</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Coeli</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>[Review of data quality dimensions and applied methods in the evaluation of health information systems]</article-title>
          <source>Cad Saude Publica</source>
          <year>2009</year>
          <month>10</month>
          <volume>25</volume>
          <issue>10</issue>
          <fpage>2095</fpage>
          <lpage>109</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scielo.br/scielo.php?script=sci_arttext&#38;pid=S0102-311X2009001000002&#38;lng=en&#38;nrm=iso&#38;tlng=en"/>
          </comment>
          <pub-id pub-id-type="doi">10.1590/s0102-311x2009001000002</pub-id>
          <pub-id pub-id-type="medline">19851611</pub-id>
          <pub-id pub-id-type="pii">S0102-311X2009001000002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Correia</surname>
              <given-names>LO</given-names>
            </name>
            <name name-style="western">
              <surname>Padilha</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Vasconcelos</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>[Methods for assessing the completeness of data in health information systems in Brazil: a systematic review]</article-title>
          <source>Cien Saude Colet</source>
          <year>2014</year>
          <month>11</month>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>4467</fpage>
          <lpage>78</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scielo.br/scielo.php?script=sci_arttext&#38;pid=S1413-81232014001104467&#38;lng=en&#38;nrm=iso&#38;tlng=en"/>
          </comment>
          <pub-id pub-id-type="doi">10.1590/1413-812320141911.02822013</pub-id>
          <pub-id pub-id-type="medline">25351313</pub-id>
          <pub-id pub-id-type="pii">S1413-81232014001104467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Safran</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bloomrosen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hammond</surname>
              <given-names>WE</given-names>
            </name>
            <name name-style="western">
              <surname>Labkoff</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Markel-Fox</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Detmer</surname>
              <given-names>DE</given-names>
            </name>
            <collab>Expert Panel</collab>
          </person-group>
          <article-title>Toward a national framework for the secondary use of health data: an American Medical Informatics Association white paper</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2007</year>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/17077452"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M2273</pub-id>
          <pub-id pub-id-type="medline">17077452</pub-id>
          <pub-id pub-id-type="pii">M2273</pub-id>
          <pub-id pub-id-type="pmcid">PMC2329823</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>European health data space data quality framework</article-title>
          <source>European Union's 3rd Health Programme</source>
          <year>2022</year>
          <access-date>2024-01-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tehdas.eu/app/uploads/2022/05/tehdas-european-health-data-space-data-quality-framework-2022-05-18.pdf">https://tehdas.eu/app/uploads/2022/05/tehdas-european-health-data-space-data-quality-framework-2022-05-18.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <article-title>Data quality framework for EU medicines regulation</article-title>
          <source>European Medicines Agency</source>
          <year>2023</year>
          <access-date>2024-01-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/data-quality-framework-eu-medicines-regulation_en.pdf">https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/data-quality-framework-eu-medicines-regulation_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
