<?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">
<?covid-19-tdm?>
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</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">v10i1e43819</article-id>
      <article-id pub-id-type="pmid">36696270</article-id>
      <article-id pub-id-type="doi">10.2196/43819</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Web-Based COVID-19 Dashboards and Trackers in the United States: Survey Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mussavi Rizi</surname>
            <given-names>Seyed</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Few</surname>
            <given-names>Stephen</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kapsetaki</surname>
            <given-names>Marianna</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Clarkson</surname>
            <given-names>Melissa D</given-names>
          </name>
          <degrees>MDes, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Division of Biomedical Informatics</institution>
            <institution>University of Kentucky</institution>
            <addr-line>725 Rose Street</addr-line>
            <addr-line>Lexington, KY, 40536</addr-line>
            <country>United States</country>
            <phone>1 859 323 7232</phone>
            <email>mclarkson@uky.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9979-176X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Division of Biomedical Informatics</institution>
        <institution>University of Kentucky</institution>
        <addr-line>Lexington, KY</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Melissa D Clarkson <email>mclarkson@uky.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>20</day>
        <month>3</month>
        <year>2023</year>
      </pub-date>
      <volume>10</volume>
      <elocation-id>e43819</elocation-id>
      <history>
        <date date-type="received">
          <day>25</day>
          <month>10</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>12</day>
          <month>11</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>2</day>
          <month>1</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>24</day>
          <month>1</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Melissa D Clarkson. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 20.03.2023.</copyright-statement>
      <copyright-year>2023</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 Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2023/1/e43819" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The SARS-CoV-2 pandemic provided an opportunity to use public-facing web data visualization tools to help citizens understand the evolving status of the outbreak. Given the heterogeneity of data sources, developers, tools, and designs used in this effort, it raised questions about how visualizations were constructed during a time when daily batches of data were available, but issues of data quality and standardization were unresolved.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This paper surveyed web-based COVID-19 dashboards and trackers that are likely to be used by the residents of the United States to monitor the spread of infection on a local, national, and global scale. This study is intended to provide insights that will help application developers increase the usefulness, transparency, and trustworthiness of dashboards and trackers for public health data in the future.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Websites of coronavirus dashboards and trackers were identified in August 2020 using the Google search engine. They were examined to determine the data sources used, types of data presented, types of data visualizations, characteristics of the visualizations, and issues with messy data. The websites were surveyed 3 more times for changes in design and data sources with the final survey conducted in June 2022. Themes were developed to highlight the issues concerning challenges in presenting COVID-19 data and techniques of effective visualization.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>In total, 111 websites were identified and examined (84 state focused, 11 nationwide, and 16 with global data), and this study found an additional 17 websites providing access to the state vaccination data. This study documents how data aggregators have played a central role in making data accessible to visualization developers. The designs of dashboards and tracker visualizations vary in type and quality, with some well-designed displays supporting the interpretation of the data and others obscuring the meaning of the data and potentially misleading the viewers. Five themes were identified to describe challenges in presenting COVID-19 data and techniques of effective visualization.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This analysis reveals the extent to which dashboards and trackers informing the American public about the COVID-19 pandemic relied on an ad hoc pipeline of data sources and data aggregators. The dashboards and trackers identified in this survey offer an opportunity to compare different approaches for the display of similar data.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>COVID-19</kwd>
        <kwd>data visualization</kwd>
        <kwd>data dashboard</kwd>
        <kwd>public health reporting</kwd>
        <kwd>human information interaction</kwd>
        <kwd>transparency</kwd>
        <kwd>trust</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>SARS-CoV-2, a novel coronavirus, was first detected in the United States in mid-January 2020 [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>], and eventually, many states enacted stay-at-home orders in early March. The SARS-CoV-2 pandemic challenged the public health system in the United States in many ways, including a lack of laboratory testing capacity early in the pandemic, evolving data standards for reporting positive test results and deaths owing to COVID-19, and a lack of coordination among state and federal agencies. In addition, approximately half of all nonfederal hospitals lacked the capacity to electronically exchange information with public health agencies at the beginning of the pandemic [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
        <p>The pandemic also presented challenges in communicating with the public the evolving status of the outbreak and the reasoning behind public health measures, such as stay-at-home orders and masking. As the pandemic progressed, waves of infection rose and fell in the regions of the United States at different times owing to the presence of <italic>superspreader events</italic>, differences in public health responses among states, and the rise of variants [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      </sec>
      <sec>
        <title>Data Visualization</title>
        <p>Data visualization has the potential to modify the course of a pandemic by bringing together information about the state of the pandemic, public policy, and individual behavior in ways that are actionable. However, for the visualizations to have this impact, they must be easily accessible, based on accurate and timely data, and carefully developed with an understanding of both the data and the principles of visual design.</p>
        <p>Visualizations have been easily accessible during the pandemic owing to the availability of numerous software tools and platforms for creating graphics and mapping data. Because data sets are available to anyone with an internet connection, early in the pandemic, a number of visualization experts wrote about the need to responsibly use tools and data when creating visualizations [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. Misrepresented and misinterpreted COVID-19 visualizations have inspired one study to use them to help students develop statistical literacy [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>The large number of visualizations developed and deployed rapidly by public health authorities and data analysts during the pandemic is of interest to visualization and communication researchers. They provide insights and lessons about the process of rapidly designing and developing visualizations [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]; efforts to curate global data [<xref ref-type="bibr" rid="ref16">16</xref>]; the types of visualizations created and who they are for [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]; conceptual models linking tools, data, visualizations, and users [<xref ref-type="bibr" rid="ref20">20</xref>]; and what it means for a visualization to be actionable [<xref ref-type="bibr" rid="ref21">21</xref>]. In addition, studies have used pandemic data to understand how the users perceive the risk and severity of the pandemic [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>] and their reactions to the designs of dashboards [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
      </sec>
      <sec>
        <title>Purpose of This Study</title>
        <p>This study complements earlier work by taking a US-focused look at COVID-19 dashboards from August 2020 to June 2022. It documents data sources and data aggregation efforts, identifies themes relevant to designing dashboards for outbreaks, and highlights issues with data availability and standardization. The goals of this work were to provide insights that will help application developers increase the usefulness, transparency, and trustworthiness of dashboards and trackers for public health data in the future and to document the variety of dashboards and trackers used by the residents of the United States and the evolution of these tools for approximately 2 years.</p>
        <p>This study encompassed the following 2 broad categories of data visualization: dashboards and trackers. The term <italic>dashboard</italic> generally refers to a set of dynamically updated data visualizations placed in proximity to one another and is used to monitor conditions for the purpose of understanding a system or event. Because several COVID-19 data visualizations took other forms, such as visualizations arranged sequentially with accompanying text, I used the term <italic>tracker</italic> to more broadly refer to these types of dynamically updated displays.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>This survey began in August 2020, which was approximately 5 months after stay-at-home orders generated widespread public interest in the state of the pandemic and all states were providing data on the web about the pandemic for a public audience.</p>
      <sec>
        <title>Identification of Dashboards and Tracker Websites</title>
        <p>To identify web-based dashboards and trackers, I performed a web search using Google on August 12, 2020. Searches were formatted as “coronavirus COVID dashboard tracker” combined with either a state name, “United States,” or “global.” The first 15 results for each keyword combination were examined for their relevance. On the basis of test searches, I determined that the relevant search results were generally in the first 10 results, and results ranked lower than the 15th search result were either links to the dashboards and trackers from other web pages or news or commentary about the pandemic. The websites that were determined to be relevant to this study are listed in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. Dashboards and trackers were categorized as state focused, nationwide, or global. This study focused on visualizations that are the most likely to be viewed by people in the United States to understand the local and regional status of the pandemic, with less emphasis on global visualizations.</p>
        <p>By the end of January 2021, many states had incorporated vaccine dashboards into their state dashboards. To locate vaccine dashboards not integrated into state websites, I performed a Google search for “covid vaccine dashboard tracker” and examined the first 20 results for relevance. <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> lists the websites determined to be relevant to this study.</p>
      </sec>
      <sec>
        <title>Inclusion and Exclusion Criteria</title>
        <p>Websites were included in this survey if they displayed up-to-date information, appeared to be updated daily (or nearly daily), and relied mainly on graphs or maps (rather than tables or text) to convey information. Websites were excluded if they showed data limited to regions smaller than a state (such as a single county or city), were specific to a type of setting (such as prisons), or displayed only trackers or dashboards that had been embedded from other websites. The District of Columbia was included in this survey, but the US territories were not. This survey included only publicly available websites accessible on a laptop. Apps developed specifically for smartphones were not included.</p>
        <p>The focus of this study was the display of information concerning diagnosed cases of COVID-19, deaths attributed to COVID-19, testing for COVID-19, and vaccination. Visualizations of risk levels, hospital bed availability, and hospital admissions were not central to this study, but designs for these types of data may benefit from these findings.</p>
      </sec>
      <sec>
        <title>Methods of Review</title>
        <p>All websites were examined on a MacBook Pro laptop (Mac OS version 10.11) using a Firefox web browser. The data sources used by each dashboard or tracker were documented based on statements from the website itself [<xref ref-type="bibr" rid="ref26">26</xref>], and for one dashboard, the development team was contacted. Some websites included a statement stating that their data sources have changed as the pandemic has developed, suggesting that their list of sources may not be complete or current. The software tool or method used to create visualizations was also determined. If the name of the software brand was not displayed with the visualization, the <italic>Inspector</italic> tool within Firefox was used to examine the webpage’s HTML and determine the tool or method used.</p>
        <p>Each website was examined to determine the following:</p>
        <list list-type="order">
          <list-item>
            <p>Does the website credit a data source or sources?</p>
            <list list-type="alpha-lower">
              <list-item>
                <p>What sources are credited? How are they credited?</p>
              </list-item>
              <list-item>
                <p>When more than one data source is credited, is it clear which measures come from which source?</p>
              </list-item>
            </list>
            <list list-type="bullet">
              <list-item>
                <p>Rationale: Citing data sources increases the trustworthiness of visualizations; however, there is no established best practice for how to do this. Listing the name of an organization that provided the data may not be sufficient if the data set from that organization cannot be identified with certainty. However, members of the public may not expect data sources to be cited.</p>
              </list-item>
            </list>
          </list-item>
          <list-item>
            <p>What types of data are presented?</p>
            <list list-type="alpha-lower">
              <list-item>
                <p>What measures are provided? (such as number of cases, number of tests performed, and number of hospitalizations)</p>
              </list-item>
              <list-item>
                <p>What is the level of granularity? (county level or state level)</p>
              </list-item>
            </list>
            <list list-type="bullet">
              <list-item>
                <p>Rationale: Many different measurements relating to COVID-19 were collected by different organizations and public health authorities, with new measures introduced and others discontinued. Differences in granularity are important both for describing the pandemic with more precision and for making the data more relevant to viewers (who have an interest in knowing about COVID-19 in their own area).</p>
              </list-item>
            </list>
          </list-item>
          <list-item>
            <p>What graphical forms of visualizations are used? (bar charts, line charts, choropleth maps, etc)</p>
            <list list-type="bullet">
              <list-item>
                <p>Rationale: Surveying graphical forms provides information on which forms designers believe are appropriate for public-facing visualizations and the variety of forms available in visualization tools.</p>
              </list-item>
            </list>
          </list-item>
          <list-item>
            <p>Do the visualizations clearly display the data? Might any visualizations lead viewers to make inappropriate conclusions?</p>
            <list list-type="bullet">
              <list-item>
                <p>Rationale: Drawing on my experience as an information designer and instructor for a data visualization course, I examined the designs for issues involving color, size, and labeling; misleading use of space or positioning; and mismatches between the type of data and the chosen graphical form. These present opportunities to increase awareness of good design in data visualization.</p>
              </list-item>
            </list>
          </list-item>
          <list-item>
            <p>How do the designers deal with <italic>messy</italic> data, such as lags in reporting and discontinuities in definitions of measures?</p>
            <list list-type="bullet">
              <list-item>
                <p>Rationale: Identifying effective methods for accommodating messy data will help establish best practices.</p>
              </list-item>
            </list>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Capturing Changes in the Design of Visualizations Over Time</title>
        <p>To understand how the dashboards and trackers evolved over the course of the pandemic, the survey of websites was repeated 3 more times. This survey spanned from approximately 7 months after the novel coronavirus was first detected in the United States to nearly 2-and-a-half years after detection. The second review of each website was conducted between January 2021 and March 2021. The third review of each website was conducted in either December 2021 or January 2022. The final review was conducted in June 2022. By the end of the survey period, &#62;1 million deaths in the United States were attributed to COVID-19, with deaths decreasing to &#60;400 per day by June 2022.</p>
        <p><xref ref-type="supplementary-material" rid="app1">Multimedia Appendices 1</xref> and <xref ref-type="supplementary-material" rid="app2">2</xref> list the information for the websites and any changes to the URLs are noted in the appendices. This review covers only the dashboards and trackers identified in August 2020 and vaccine-focused websites identified from January 2021. Therefore, websites launched after that time were not included.</p>
      </sec>
      <sec>
        <title>Developing Themes</title>
        <p>On the basis of a review of the websites, 5 sets of themes were developed to highlight issues concerning challenges in presenting COVID-19 data and techniques of effective visualization.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Dashboards and Trackers Identified</title>
        <sec>
          <title>State Focused</title>
          <p>A total of 84 dashboards and trackers focusing on COVID-19 cases in a state (or region composed of several states) were identified. These are listed in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>, with each assigned an identifier in the format <italic>S-x</italic>. (This paper will refer to dashboards and trackers using square brackets with the identifier from the appendix, for example, [S-1] for the dashboard from the Alabama Department of Public Health). At least one dashboard or tracker website was provided by the public health authorities in each state and the District of Columbia as of August 2020. The Massachusetts Department of Public Health originally provided only a downloadable PDF document before switching to a dashboard created with Tableau. An additional 20 dashboards and trackers were developed by newspapers and television news organizations. The remaining websites were associated with nonprofit organizations (n=2), web-based media and marketing companies (n=2), individuals (n=2), a university-associated team, and a health care–related trade organization. All state-focused websites identified in this survey provided data at the county or parish level. As of June 2022, a total of 23 of the 84 dashboards and trackers were removed or no longer updated with new data. Of these, the Florida Department of Health discontinued its dashboard but replaced it with weekly reports that could be downloaded as PDF documents.</p>
        </sec>
        <sec>
          <title>Nationwide Coverage</title>
          <p>In total, 11 websites that displayed data for the entire United States were identified. These are listed in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>, with identifiers in the format <italic>N-x</italic>. Of these, 5 websites displayed data at the state level, whereas 6 provided more granular data at the county level. The Centers for Disease Control and Prevention (CDC) provided 2 trackers [N-1 and N-2]. Other websites were provided by news organizations (n=3), university-associated teams (n=3), technology or web companies (n=2), and a nonprofit organization. As of June 2022, a total of 2 of the 11 websites were discontinued.</p>
        </sec>
        <sec>
          <title>Global Coverage</title>
          <p>An additional 16 websites were identified that displayed worldwide COVID-19 data. These are listed in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>, with identifiers in the format <italic>G-x</italic>. These websites were provided by news organizations (n=3), university-associated teams (n=4), nonprofit organizations (n=3), and technology or web-based businesses (n=6). As of June 2022, a total of 4 of the 16 websites were removed or no longer updated.</p>
        </sec>
        <sec>
          <title>Vaccine Distribution</title>
          <p><xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> lists the additional dashboards and trackers for vaccine distribution. This survey identified 17 state-focused sites with county-level data, 4 with nationwide coverage at the state level, and 3 with global coverage.</p>
        </sec>
      </sec>
      <sec>
        <title>Visualization Tools and Methods</title>
        <p>The most popular software platforms used for state-focused dashboards and trackers, particularly among public health authorities, were Tableau, ArcGIS, and Microsoft Power BI. Some dashboards presented all the information in a single page, but it was common for dashboards to have multiple pages to accommodate maps and new types of data that became available during the pandemic. News organizations were more likely to provide trackers arranged as a series of data visualizations with textual explanations and use scalable vector graphics embedded in their web pages. See <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> for information on the visualization tools or methods used for each dashboard and tracker.</p>
      </sec>
      <sec>
        <title>Data Sources and Data Aggregators</title>
        <sec>
          <title>Overview</title>
          <p>As with all data visualizations, it is important for the viewers of COVID-19 dashboards and trackers to know the data sources. A visualization could display data collected by the organization that created the visualization (in the case of public health authorities), data obtained directly from one or more public health authorities, or data from a data aggregator service. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> documents the data sources stated on the websites. <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> provides a list of data aggregators and prominent dashboard developers with URLs for details on their methodologies and data sources.</p>
        </sec>
        <sec>
          <title>State Focused</title>
          <p>None of the websites provided by state-level public health authorities provided details about data sources or methodology, but it is likely that the data were submitted by local public health departments that received reports from diagnostic laboratories, health clinics, and hospitals. Of the nongovernmental state-focused websites, most stated that the data were from the state public health authority (or, in some cases, a combination of state and local public health authorities), but it is unclear whether these websites were drawing data directly from the public health authorities they credited or if they used a data stream from a data aggregator service. Two nongovernmental websites did not state a source of data or removed the statement [S-30] and [S-54]. One website’s data source [S-77] was credited to a data aggregator.</p>
        </sec>
        <sec>
          <title>Nationwide Coverage</title>
          <p>Throughout the fall of 2020, the CDC provided only state-level COVID-19 case counts to the public rather than county-level data. Therefore, any website displaying county-level case counts for the United States relied on data aggregated from local and state sources by a nonfederal data aggregator. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the major data aggregation pathways for case counts and testing data for the United States as of August 2020. It was created by examining data sources and methodology information for the websites and consulting additional reports [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. The following are the 4 major data aggregators used to independently aggregate nationwide data:</p>
          <list list-type="bullet">
            <list-item>
              <p><italic>USAFacts:</italic> A nonprofit civic initiative that gathers government data [<xref ref-type="bibr" rid="ref28">28</xref>]. County-level data available for download.</p>
            </list-item>
            <list-item>
              <p><italic>1Point3Acres (CovidNet):</italic> A volunteer group founded by first-generation Chinese immigrants in the United States [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. County-level data available for download.</p>
            </list-item>
            <list-item>
              <p><italic>The New York Times:</italic> County-level data available for download.</p>
            </list-item>
            <list-item>
              <p><italic>The COVID Tracking Project:</italic> A volunteer organization launched by <italic>The Atlantic</italic> [<xref ref-type="bibr" rid="ref30">30</xref>]. State-level data available for download or through an application programming interface (API). It includes data for case counts and total number of tests. This project ended in March 2021, one year after it began.</p>
            </list-item>
          </list>
          <p>As shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>, in August 2020, only state-level data and not county-level data were available to developers by API. During this survey, several additional resources that claimed to provide APIs for county-level data scraped from the websites of data aggregators were noticed; however, this was in violation of the terms of the service set by those data aggregators.</p>
          <p>No nationwide website appeared to use CDC as their only data source. Instead, websites relied on an independent data aggregator or a combination of use of data from the CDC and a data aggregator. Of particular interest is that the county-level tracker provided by the CDC [N-2] credited the USAFacts aggregator as its source of county-level data. In August 2020, a footnote stated “Data courtesy of USAFacts.org downloaded each day at 4:00 pm EST or when earliest update is available” [<xref ref-type="bibr" rid="ref31">31</xref>]. The web page redesign in November 2020 provided more extensive details on data sources, including the statement “The COVID-19 case and death metrics are generated using data from USAFacts that CDC modifies.” The use of USAFacts was later discontinued and county-level data were obtained directly from the states [<xref ref-type="bibr" rid="ref32">32</xref>].</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Major data aggregation pathways for the United States’ cases and testing data as of August 2020. References in blue correspond to dashboards and trackers. API: application programming interface; CDC: Centers for Disease Control and Prevention; CSSE: Center for Systems Science and Engineering; G: global; N: nationwide.</p>
            </caption>
            <graphic xlink:href="humanfactors_v10i1e43819_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Global Coverage</title>
          <p>The dashboard developed by the Johns Hopkins University (JHU) Centers for Civic Impact displays data from the JHU Center for Systems Science and Engineering (CSSE). JHU CSSE acts as an aggregator of aggregators for worldwide data, relying on a large number of sources, including The COVID Tracking Project and 1Point3Acres for the US data [<xref ref-type="bibr" rid="ref26">26</xref>]. The complete list of data sources used by the JHU CSSE since January 2020 is provided in their data repository [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Issues in Trust and Transparency</title>
        <p>Trust and transparency are emphasized in the guidelines the World Health Organization has assembled for communicating with the public about disease outbreaks [<xref ref-type="bibr" rid="ref34">34</xref>]. Dashboards and trackers may inform viewers of visualizations about the sources of the data in several ways. The most direct approach is to provide the data source within a caption for each map or graph; however, this may not be feasible for dashboards combining several visualizations. Websites using data aggregators often simply state one or more sources for the entire collection of visualizations. One nationwide dashboard [N-11] was particularly vague about the relationship between the visualizations displayed and the sources of data, crediting <italic>CDC, WHO, The New York Times, JHU, Corona Data Scraper, and official state and county health agencies</italic> without providing further details. When websites list sources in this manner, it raises the following questions:</p>
        <list list-type="bullet">
          <list-item>
            <p>Is this website using a data aggregator, but crediting the sources used by the aggregator rather than the aggregator?</p>
          </list-item>
          <list-item>
            <p>Which measures from which data sources are used in a particular visualization?</p>
          </list-item>
          <list-item>
            <p>Are all these sources currently used, or is this a list of all sources ever used?</p>
          </list-item>
          <list-item>
            <p>If only one organization is listed, what is the specific data set from the organization that was used?</p>
          </list-item>
        </list>
        <p>Early in the pandemic, data scientists raised concerns about the quality of COVID-19 data [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. The challenges of collecting global data appropriate for display and analysis have led to questions regarding the methodologies and sources used by some aggregators. For example, Worldometer is a private company known for its web counters that estimate world statistics. It became an aggregator of COVID-19 data and provider of popular COVID-19 trackers [G-12] and has been criticized for having an anonymous curation team and opaque methodology [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
      </sec>
      <sec>
        <title>Visualization Tools and Methods</title>
        <p><xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> presents the tools and methods used to construct the visualizations examined in this survey. With the exception of Massachusetts, all state public health authorities provided a web page displaying a dashboard or tracker in August 2020 (with Massachusetts providing PDF downloads). Websites of state public health authorities were often constructed using ArcGIS, whereas state-focused websites from other types of developers relied on a variety of tools (including Tableau, Datawrapper, Infogram, and Microsoft Power BI). Websites providing nationwide coverage tended to be constructed with frameworks using embedded scalable vector graphics. Global dashboards and trackers were created with a variety of methods.</p>
      </sec>
      <sec>
        <title>Critique of Visualizations</title>
        <sec>
          <title>Overview</title>
          <p>Overall, 5 themes were identified from the data visualizations and designs of the dashboards and trackers. <xref ref-type="supplementary-material" rid="app4">Multimedia Appendices 4</xref>-<xref ref-type="supplementary-material" rid="app18">18</xref> provide screenshots of the websites taken during the 4 rounds of review. Not every page of the website was captured for multipage websites, but the most relevant visualizations are documented.</p>
        </sec>
        <sec>
          <title>Theme 1: Data as Imperfect Representation of Reality</title>
          <p>Although the data presented in COVID-19 visualizations are intended to reflect the state of the pandemic, <xref rid="figure2" ref-type="fig">Figure 2</xref> provides examples in which short-term patterns and trends are owing to the methods of data collection and reporting.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>(A and B) Display of daily deaths in California through August 2020 in 2 different dashboards. Notice line for 14-day rolling average in example B. Example A is from [S-9] on August 20, 2020. Example B is from [S-8] on August 29, 2020. (C) Example of 7-day rolling average for daily vaccinations in Illinois. Low values on weekends likely reflect delays in data reporting. From [Svac-6] on January 31, 2021. (D) Tests per day in Indiana. Notice the gray box marking preliminary data. From [S-29] on June 12, 2022. (E) Deaths per day in Colorado, showing a spike on April 24 owing to the inclusion of probable deaths. From [S-13] on August 29, 2020. (F) Cumulative deaths in Colorado, showing a dip on May 15 owing to the change of definition to include only patients who are recorded as dying from COVID-19, rather than testing positive at time of death. From [S-13] on August 14, 2020.</p>
            </caption>
            <graphic xlink:href="humanfactors_v10i1e43819_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <sec>
            <title>Theme 1a—Temporal Data Reflect a Combination of Reporting Activity and Public Health Reality</title>
            <p>Short-term trends in the data organized by the date of reporting can be misleading. As explained by The COVID Tracking Project:</p>
            <disp-quote>
              <p>...this data displays very strong day-of-week effects and is also extremely vulnerable to predictable rise-and-drop artifacts after holidays or other major disruptions, like storms and natural disasters, that affect the ability of counties and states to report their data.</p>
              <attrib>
                <xref ref-type="bibr" rid="ref38">38</xref>
              </attrib>
            </disp-quote>
            <p>To help viewers disregard day-of-the-week variability, most time series graphs include 3-, 7-, or 14-day rolling averages. As time series graphs will have incomplete data for the most recent days (owing to a lag in reporting), the best designs visually indicate the span of incomplete data.</p>
          </sec>
          <sec>
            <title>Theme 1b—Inconsistent Definitions in Data Collection and Reporting</title>
            <p>In the United States, much of the public health infrastructure is regulated and managed at the state and local levels. Therefore, states have different processes for collecting data and use inconsistent definitions. For example, states vary in how they define deaths attributable to COVID-19, whether the number of tests (and positive and negative results) reflects unique people or number of specimens [<xref ref-type="bibr" rid="ref39">39</xref>], and the diagnosis of asymptomatic cases [<xref ref-type="bibr" rid="ref40">40</xref>]. In the early months of the pandemic, several states combined the counts of polymerase chain reaction tests (a diagnostic test) and antibody tests (which detect an immune response), leading to distortions in the data on infection rates and testing capacity [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. If data aggregators were unaware of this heterogeneity in state-level data, or unable to correct for known differences, visualizations that provide state-to-state comparisons will be inaccurate. In addition, some states have reported a count of recovered patients with COVID-19. Not only did these states use different definitions for recovered, but referring to patients as recovered when the long-term effects of COVID-19 are not known is misleading [<xref ref-type="bibr" rid="ref43">43</xref>]. Another potential source of confusion occurred later in the pandemic as people became reinfected, meaning that case counts no longer represented unique individuals if states followed the national case definition [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. The Iowa Department of Public Health noted this change with the following statement:</p>
            <disp-quote>
              <p>On September 1, 2021, IDPH adopted the updated 2021 COVID-19 national case definition. As part of this case definition, IDPH began including in its total case counts individuals who were previously reported as a confirmed or probable case, but have become infected again.</p>
              <attrib>S-28</attrib>
            </disp-quote>
            <p>Data regarding vaccinations also had inconsistencies early in 2021. As explained by the <italic>Washington Post</italic> in a footnote below the graphs of state vaccination doses administered by day:</p>
            <disp-quote>
              <p>Data before Jan. 12 is inconsistent. On Feb. 19, the CDC altered its reporting of doses administered by federal agencies by adding them to the states where the shots had been given. From Feb. 23 forward, the data reflects doses administered to residents of the states rather than doses administered by the state.</p>
              <attrib>Nvac-3</attrib>
            </disp-quote>
          </sec>
        </sec>
        <sec>
          <title>Theme 2: The Importance of Context for Interpretation</title>
          <p>Data require context for interpretation, and therefore, data visualizations should provide context to help viewers find meaning in a visualization. <xref rid="figure3" ref-type="fig">Figure 3</xref> shows successful and unsuccessful examples of providing context.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>(A) Comparison of vaccination rates in counties of Minnesota against state average. From [Svac-10] on September 25, 2022. (B) Timeline of waves of new cases in California compared with other states. From [S-10] on January 31, 2021. (C) Comparison of vaccination rates in Wisconsin within demographic categories. From [Svac-17] on January 3, 2022. (D) Comparison of vaccination rates in Minnesota within race and ethnicity categories. Graphing on a scale of 100% of the population (rather than proportional to race and ethnicity) makes this design less effective than example C. From [Svac-10] on January 3, 2022. (E) Comparison of percent vaccinated with 1 dose and 2 doses against the eligible population and total population of Florida. From [Nvac-3] on April 30, 2021. (F) Indication of the shelter in place policy as gray band with time series data showing newly reported hospital cases in Georgia. From [S-23] on January 31, 2021. (G) Time points for policy decisions to open or restrict public gathering in Alabama, with time series data showing reported cases. From [N-7] on December 11, 2021.</p>
            </caption>
            <graphic xlink:href="humanfactors_v10i1e43819_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <sec>
            <title>Theme 2a—Supporting Meaningful Comparisons</title>
            <p>Many types of interpretations rely on comparisons. In the context of COVID-19, useful comparisons include differences between regions, differences between demographic groups, differences over time, and differences between vaccinated and unvaccinated populations. It is these comparisons that give meaning to the data.</p>
          </sec>
          <sec>
            <title>Theme 2b—Indicating Changes to Public Health Policy in Time Series Visualizations</title>
            <p>Public health policy affected the trajectory of the pandemic, and policies varied at the state, county, and city levels. Several visualizations superimposed policy changes over time series data.</p>
          </sec>
        </sec>
        <sec>
          <title>Theme 3: Choosing Values to Display</title>
          <sec>
            <title>Overview</title>
            <p>The COVID-19 pandemic has provided web application developers with access to data and public interest in the visualizations of these data. However, creating useful visualizations often requires more than graphing the raw numbers supplied in a data stream. The examples in <xref rid="figure4" ref-type="fig">Figure 4</xref> demonstrate why it is important to consider whether it is most useful to display the data directly as obtained, a transformation of the data, or cumulative values.</p>
            <fig id="figure4" position="float">
              <label>Figure 4</label>
              <caption>
                <p>(A) Graphs of the 3-day average of cases (upper graph) and the cumulative number of cases (lower graph) in Colorado. Note that the decrease in new cases in June is difficult to detect in the cumulative graph. From [S-12] on August 15, 2020. (B) Cumulative number of cases in Maine. From [S-37] on August 15, 2020. (C) Cumulative number of persons by vaccination status in Hawaii. The category initiating refers to the first dose, completing indicates receiving both the first and second dose. From [S-25] on February 27, 2021. (D) Case counts by age group (upper graph) and case rates by age group (lower graph) in Michigan. The lower graph shows that patients aged ≥80 years have a higher case rate than the other groups. From [S-40] on August 15, 2020. (E) The home page of the Florida dashboard, with a map showing case counts per county. A note at the bottom says “Comparison of counties is not possible because case data are not adjusted by population.” A color-coding key was not provided. A map displaying the rates by county is available on another tab. From [S-20] on August 15, 2020. (F) Map showing case counts by county. A color-coding key was not provided, but the intensity of red reflects areas of higher population density (with the location of universities indicated). From [S-17] on August 20, 2020. (G) Case counts per county for New York City Long Island has the highest number of cases but also the highest population density.</p>
              </caption>
              <graphic xlink:href="humanfactors_v10i1e43819_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
          <sec>
            <title>Theme 3a—Limited Usefulness of Cumulative Counts</title>
            <p>Many dashboards state the total number of COVID-19 cases and deaths, and some also display a time series of cumulative counts. The total number of deaths may be of general interest, but graphs of the cumulative number of cases or deaths are less useful because they show only a rising curve without clearly showing trends during the pandemic. However, it may be that showing a time series of the cumulative number of vaccinated people in a region could help persuade others to become vaccinated.</p>
          </sec>
          <sec>
            <title>Theme 3b—Total Counts Are Less Informative Than Population-Based Rates</title>
            <p>The availability of county-level data helps viewers to understand the geographic distribution of COVID-19 cases and deaths. However, to be more meaningful, data should be displayed as rates (eg, number of cases per 100,000 people) rather than as counts. Visualizing count data on a map is likely to simply show areas with a higher population density and give a misleading impression that COVID-19 has not affected rural areas.</p>
          </sec>
        </sec>
        <sec>
          <title>Theme 4: Choosing the Graphical Form of the Visualization</title>
          <p>The graphical forms of the visualizations (including line charts, bar charts, and choropleth maps) and how they were arranged in the dashboards revealed a mixture of effective designs that made good use of perceptual principles as well as less effective designs. Examples are shown in <xref rid="figure5" ref-type="fig">Figure 5</xref>.</p>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>(A-C) Summary visualizations provided by the Ceners for Disease Control and Prevention at the top of their COVID Data Tracker web page [N-2]. Example A was captured on February 1, 2021. This design uses pink shading below the line indicating "Cases in US, last 30 days." This is misleading because the height of the shading does not begin at 0. Example B is the same design captured on February 26, 2021 that deceptively implies that cases have dropped to 0. Example C is the revised design of the summary visualizations captured on December 11, 2021. The shading has been removed and an arrowhead is added. (D) Top-of-page summary provided by the Denver Post [S-14]. The design allows viewers to quickly see and compare trends. Shows data from last 3 months but not from the last 2 days. Captured on August 15, 2020. (E) The first 4 columns and 5 rows of a table comparing each state, ordered by case rates. Sparklines indicate trends over time, but the span of time shown is not defined. Orange bars represent current case rates. From [S-84] on December 11, 2021. (F) Summary for Oregon. This example is less successful in communicating trends because rolling averages are not used. From [S-59] on August 15, 2020. (G) A small portion of a state-by-state comparison provided by the New York Times [N-4] using a small multiples layout. Captured on October 4, 2022. (H) Stacked time series comparing confirmed cases and probable cases in Massachusetts. From [S-39] on January 31, 2021. (I and J) Graphs comparing tests administered and test positivity rate using dual axis graphs. This design is more difficult to interpret than stacked time series. Example I is Colorado data from [S-14] on March 20, 2021. Example J is California data from [S-8] on August 15, 2020.</p>
            </caption>
            <graphic xlink:href="humanfactors_v10i1e43819_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <sec>
            <title>Theme 4a—Simple Graphs for Overview and Comparison</title>
            <p>One challenge is to distill the data into simple but meaningful visualizations. Several websites offered simple summary graphics, often in the form of simple time series graphs or sparklines, to communicate the trajectory of the pandemic. However, these simple overviews are only effective if the rolling averages are displayed. Because the pandemic was not uniform across the United States, visualizations also helped people compare the current status and trajectories of different states. However, the key to making these comparisons meaningful is that the underlying data must be comparable, and this relies on the uniformity in data collection or adjustments by data aggregators.</p>
          </sec>
          <sec>
            <title>Theme 4b—Comparing Different Data Sets Over the Same Timespan</title>
            <p>Data displayed as time series are crucial for communicating about the pandemic, and meaning is often derived from comparing different types of data or data from different regions. Small multiples and stacked time series were effective in aiding comparisons. A number of dashboards provided dual axis graphs, often for comparing the numbers of coronavirus tests administered and the positivity rates over time. However, this dual axis design is difficult to interpret, and alternative designs provide better solutions [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>].</p>
          </sec>
          <sec>
            <title>Theme 4c—Interactivity of Graphs</title>
            <p>Frameworks for developing web visualizations often include functionality for displaying the values of data points when the cursor hovers over points. This method of providing <italic>details-on-demand</italic> is useful for enabling an in-depth exploration of graphs [<xref ref-type="bibr" rid="ref48">48</xref>] and is often used in time series. Another type of interactivity is to enable a viewer to customize a graph by controlling the data or presentation style through drop-down menus or radio buttons. In this survey, I noted options for choosing between case counts and case rates, setting the length of time for a time series, filtering by demographic group, and switching between a linear or logarithmic scale for case counts. When display options are provided, it is important that a default display is chosen that is suitable for the greatest number of users and minimizes misinterpretation. For example, a linear scale should be the default, but advanced users may choose the option of a logarithmic scale [<xref ref-type="bibr" rid="ref49">49</xref>]. One particularly useful option for understanding the global spread of the coronavirus is to align outbreaks in different countries based on days since a country’s outbreak reached a particular threshold of cases rather than by date. The former option is the default for a graph provided by Our World in Data [G-10].</p>
          </sec>
        </sec>
        <sec>
          <title>Theme 5: Pitfalls of Automated Data Display</title>
          <sec>
            <title>Overview</title>
            <p>Dashboards and trackers visualize streams of data that are automatically updated. This combination of dynamic data and the lack of human oversight revealed some pitfalls that should be avoided to build more robust systems. These findings also suggest that dashboards need frequent monitoring to detect problems in the design of displays or the handling of data. <xref rid="figure6" ref-type="fig">Figure 6</xref> demonstrates several of the identified problems.</p>
          </sec>
          <sec>
            <title>Theme 5a—Display of Peculiar Data</title>
            <p>Some anomalies in the displayed data cannot be explained by small adjustments to the data or artifacts such as day-of-the-week variations. Extremely high or negative values of counts indicate problems in recording, processing, or transmitting data. The presence of these anomalies should alert developers (and viewers) that the trustworthiness of the entire data set and visualization is questionable.</p>
          </sec>
          <sec>
            <title>Theme 5b—Designs May Cease to Support Meaningful Comparisons</title>
            <p>A design that works well with a particular range of values or size of data set may lose effectiveness as data are dynamically updated. For example, a method of binning data that is effective early in the pandemic will become much less informative if all the data are represented within a single bin later in the pandemic. However, one drawback of adjusting bins over time is that people who periodically view a graph may assume that changes in the distribution of data in bins reflect changes in the data rather than in the definition of the bins.</p>
            <fig id="figure6" position="float">
              <label>Figure 6</label>
              <caption>
                <p>(A) Deaths per day for Colorado, including peaks of −170 and 841. From [N-10] on April 10, 2021. (B) Newly hospitalized patients per day for Kansas, including peaks of 5417, 7257, −9387, and −5290. From [N-10] on April 10, 2021. (C and D) Color coding of counties in Michigan based on case rate. Captured on August 15, 2020, and March 20, 2021. By March 2021 all counties are in the highest bin. From [S-41]. (E and F) Alternate view of Michigan map captured on the same days that display total case counts (rather than rate). Uses same color-coding key as examples C and D. Notice that the data on the August 2020 map spans 5 bins, whereas the March 2021 map uses only 3. (G and H) Patient status in Oklahoma. Captured on August 15, 2020, and April 10, 2021. By April, the number of recovered cases make the length of the active case bar unreadable. From [S-58].</p>
              </caption>
              <graphic xlink:href="humanfactors_v10i1e43819_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study identified and examined &#62;100 websites providing COVID-19 dashboards and trackers relevant to the residents of the United States and highlighted the multitude of factors that affect these visualizations. The findings reveal the role data aggregators have played in making data accessible to visualization developers as well as lapses in communicating to viewers the provenance of the data. Decisions by public health experts about data collection and data standards have downstream effects on which data are available to be communicated and compared. In addition, each step of this process is impacted by the evolving nature of the pandemic and political and social systems.</p>
        <p>The five themes identified in this work can guide future development of visualizations of public health data for the public: (1) viewers should be made aware that data are an imperfect representation of reality owing to methods of data collection and reporting; (2) viewers need context for interpreting visualizations, such as comparisons with other data or indicators of relevant events on timelines; (3) developers should carefully consider whether plotting a raw data stream, cumulative values, or transformation of values will be the most useful to viewers; (4) the graphical form of a visualization should be chosen to fit the type of data and be designed to make good use of perceptual principles; and (5) visualizations designed to use automated streams of data must be monitored to ensure that the data continue to have reasonable values and that the design of the visualization remains useful with the new data.</p>
      </sec>
      <sec>
        <title>Trust and Transparency Begins With the Data</title>
        <p>One of the persistent challenges faced by data aggregators has been managing disparate data sets for analysis and visualization. In the United States, the collection of public health data is governed at the local and state levels [<xref ref-type="bibr" rid="ref50">50</xref>]. Strategies differ by state, with no central government authority to standardize data collection and reporting. The Council of State and Territorial Epidemiologists published standards for the clinical diagnosis of COVID-19 and data elements to report in April 2020, with updates in August 2020 and August 2021 [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. The Council of State and Territorial Epidemiologists also recommended that states enact laws to make cases of COVID-19 reportable to public health authorities. The CDC has no authority to require reporting, stating “COVID-19 case surveillance data are collected by jurisdictions and reported voluntarily to CDC” [<xref ref-type="bibr" rid="ref52">52</xref>].</p>
        <p>Problems with data quality, standards, and availability have been described by dashboard and aggregator teams [<xref ref-type="bibr" rid="ref53">53</xref>-<xref ref-type="bibr" rid="ref56">56</xref>] and journalists [<xref ref-type="bibr" rid="ref57">57</xref>-<xref ref-type="bibr" rid="ref60">60</xref>]. Problems in data standardization and availability were somewhat alleviated during the first year of the pandemic, but data on case counts became unreliable by early 2022 because of the introduction of rapid at-home test kits [<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>].</p>
        <p>Data that are visualized by a person or an organization that did not originally collect the data is an example of data reuse. The movement around Findable, Accessible, Interoperable, Reusable (FAIR) data includes the responsibility of providing appropriate data citations so that the original source and providence of data are discoverable [<xref ref-type="bibr" rid="ref63">63</xref>]. The disconnect between the vision of the FAIR data and the findings of this survey is important. One challenge is that COVID-19 data are obtained in frequent updates (rather than from archived data sets) and often from data aggregators. This highlights the gap between the real-world need for trustworthy display of data in public health and typical use cases for using FAIR principles.</p>
      </sec>
      <sec>
        <title>Aligning Visualization Goals and Visualized Data</title>
        <p>What are the purposes of public-facing visualizations of pandemic data, and what data are needed to achieve those purposes?</p>
        <p>Dashboards are often described as tools to support decision-making. Visualizations have played an important role in educating citizens about the pandemic and therefore may encourage changes in behavior to mitigate transmission. However, visualizations are likely to have a constellation of purposes. For example, a visualization could help establish trust between public health authorities and citizens. Further, effectively promoting behavior change may depend on first conveying the magnitude of human suffering caused by the pandemic.</p>
        <p>The question of what data are useful for decision-making was addressed early in the pandemic by former CDC Director Dr Tom Frieden. He argued that there is a mismatch between the most commonly available data—counts of cases, hospitalizations, and deaths—and the data that are the most useful for guiding COVID-19 response in communities. He suggested that local decision-making for formulating policies should use data that include the number of unlinked infections, number of health care worker infections, and trends in excess mortality [<xref ref-type="bibr" rid="ref64">64</xref>].</p>
      </sec>
      <sec>
        <title>Visualizations as Arguments</title>
        <p>Data visualizations are often assumed to be neutral and objective mechanisms of communication, but they are not. Designing and developing visualizations require numerous decisions regarding the selection of data and methods of presentation. It has been argued that all visualizations are rhetorical and therefore have the power to influence beliefs and behaviors [<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref66">66</xref>].</p>
        <p>In the context of the COVID-19 pandemic, public health authorities and government officials have made decisions about what data to collect and what data to <italic>not</italic> collect. These decisions constrain the messages that visualizations can send. In addition, the messages from these visualizations may imply a sense of authority and certainty through their association with organizations that have traditionally been respected (public health agencies, universities, and news organizations) and the “clean lines and structured layouts of traditional visualizations” [<xref ref-type="bibr" rid="ref65">65</xref>]. This authority and certainty may obscure the extent of human suffering caused by COVID-19, echoing concerns raised by Dragga and Voss [<xref ref-type="bibr" rid="ref67">67</xref>] in their analysis of graphs depicting fatalities and injuries from causes such as industrial workplaces and baby walkers.</p>
        <p>In the United States, the authority of COVID-19 visualizations and the data behind them have been questioned, with various groups asserting that the severity of the pandemic has been either overplayed or downplayed. As many state and local policies for reopening schools and businesses were commonly tied to metrics about the pandemic, such as the test positivity rate or hospitalization rate, people tired of pandemic restrictions have accused COVID-19 data and dashboards of becoming political tools to prevent a return to normal. Other groups adopted a different perspective. For example, in April 2022, a coalition of public health practitioners, scientists, health care workers, educators, and advocates known as The People’s CDC released a statement criticizing the new definitions for categories of community transmission rates. They wrote the following :</p>
        <disp-quote>
          <p>The resulting shift from a red map to a green one reflected no real reduction in transmission risk. It was a resort to rhetoric: an effort to craft a success story that would explain away hundreds of thousands of preventable deaths and the continued threat the virus poses.</p>
          <attrib>
            <xref ref-type="bibr" rid="ref68">68</xref>
          </attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>The Connection Between Data, Usability, and Understandability</title>
        <p>Public-facing visualizations of pandemic data are useful only if viewers are able to understand and interpret the data displays they see. Dashboard designers might choose to display large amounts of data with the goal of allowing the viewers to come to their own interpretation of the data without the prescriptive guidance of dashboard designers. However, this effort at transparency can backfire if the viewers are overwhelmed by the complexity or arrive at incorrect conclusions [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]. Viewers may assume that websites with more data are more accurate, but the volume of data and visualizations may obscure uncertainties in the data.</p>
        <p>Visualization and communication researchers play crucial roles in determining how to better design public-facing dashboards for infectious disease data. Several studies have used COVID-19 data and dashboards in user studies [<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. Identifying best practices will accelerate the development of effective dashboards and trackers, and the software tools commonly used by public health authorities could incorporate those recommendations into templates. An important area for future investigation is determining if effective design practices for COVID-19 data can be applied to display other types of public health data.</p>
        <p>Current research in the field of visualization seeks to develop software tools to assist nonexpert users in choosing effective visualization techniques to support their specific data sets and goals (as demonstrated in studies by Lavalle and Mate [<xref ref-type="bibr" rid="ref70">70</xref>] and Golfarelli and Lizzi [<xref ref-type="bibr" rid="ref71">71</xref>]). This aligns with 2 of the themes from this study, choosing the values to display and choosing the graphical form of the visualization. These studies are often based in the domain of business analytics; however, future work could focus on the domain of public health.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study was limited to dashboards and trackers available to the public as of August 2020 and therefore does not include dashboards used internally by health care and public health organizations. It excludes visualizations produced exclusively for smartphone apps and visualizations that focus on specific populations, such as nursing homes or prisons, or nontraditional data types, such as wastewater sampling.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This analysis reveals the extent to which dashboards and trackers informing the American public about the COVID-19 pandemic relied on an ad hoc pipeline of data sources and data aggregators. The pandemic has been characterized by disparate and evolving data standards, which has complicated the development of dashboards and trackers that display data over time and across regions. The 128 websites of dashboards and trackers identified in this survey offer an opportunity to compare different approaches to the display of similar data. This work highlights examples that provide clarity in interpreting data, and those that obscure the meaning of the data and may potentially mislead viewers.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>State-focused, nationwide, and global dashboards and trackers were examined. Includes the URL for each site, data sources, and type of visualization tool or method used. Government websites are listed in gray shading.</p>
        <media xlink:href="humanfactors_v10i1e43819_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 336 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>State-focused, nationwide, and global dashboards and trackers for vaccination on websites that are not included in Multimedia Appendix 1. Includes the URL for each site, data sources, and type of visualization tool or method used. Government websites are listed with gray shading.</p>
        <media xlink:href="humanfactors_v10i1e43819_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 176 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Web pages for data sources and technical information provided by prominent data aggregators and dashboard developers.</p>
        <media xlink:href="humanfactors_v10i1e43819_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 49 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Screenshots for state-focused dashboards and trackers, August 29, 2020.</p>
        <media xlink:href="humanfactors_v10i1e43819_app4.pdf" xlink:title="PDF File  (Adobe PDF File), 31218 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Screenshots for nationwide dashboards and trackers, August 29, 2020.</p>
        <media xlink:href="humanfactors_v10i1e43819_app5.pdf" xlink:title="PDF File  (Adobe PDF File), 3896 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Screenshots for global dashboards and trackers, August 29, 2020.</p>
        <media xlink:href="humanfactors_v10i1e43819_app6.pdf" xlink:title="PDF File  (Adobe PDF File), 5443 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>Screenshots for state-focused dashboards and trackers, January 31, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app7.pdf" xlink:title="PDF File  (Adobe PDF File), 80275 KB"/>
      </supplementary-material>
      <supplementary-material id="app8">
        <label>Multimedia Appendix 8</label>
        <p>Screenshots for nationwide dashboards and trackers, February 26, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app8.pdf" xlink:title="PDF File  (Adobe PDF File), 8425 KB"/>
      </supplementary-material>
      <supplementary-material id="app9">
        <label>Multimedia Appendix 9</label>
        <p>Screenshots for global dashboards and trackers, March 1, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app9.pdf" xlink:title="PDF File  (Adobe PDF File), 5918 KB"/>
      </supplementary-material>
      <supplementary-material id="app10">
        <label>Multimedia Appendix 10</label>
        <p>Screenshots for vaccine dashboards and trackers, January 31 or February 27, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app10.pdf" xlink:title="PDF File  (Adobe PDF File), 14014 KB"/>
      </supplementary-material>
      <supplementary-material id="app11">
        <label>Multimedia Appendix 11</label>
        <p>Screenshots for state-focused dashboards and trackers, December 11, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app11.pdf" xlink:title="PDF File  (Adobe PDF File), 80630 KB"/>
      </supplementary-material>
      <supplementary-material id="app12">
        <label>Multimedia Appendix 12</label>
        <p>Screenshots for nationwide dashboards and trackers, December 11, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app12.pdf" xlink:title="PDF File  (Adobe PDF File), 5959 KB"/>
      </supplementary-material>
      <supplementary-material id="app13">
        <label>Multimedia Appendix 13</label>
        <p>Screenshots for global dashboards and trackers, December 11, 2021.</p>
        <media xlink:href="humanfactors_v10i1e43819_app13.pdf" xlink:title="PDF File  (Adobe PDF File), 5297 KB"/>
      </supplementary-material>
      <supplementary-material id="app14">
        <label>Multimedia Appendix 14</label>
        <p>Screenshots for vaccine dashboards and trackers, January 3, 2022.</p>
        <media xlink:href="humanfactors_v10i1e43819_app14.pdf" xlink:title="PDF File  (Adobe PDF File), 15150 KB"/>
      </supplementary-material>
      <supplementary-material id="app15">
        <label>Multimedia Appendix 15</label>
        <p>Screenshots for state-focused dashboards and trackers, June 12, 2022.</p>
        <media xlink:href="humanfactors_v10i1e43819_app15.pdf" xlink:title="PDF File  (Adobe PDF File), 24828 KB"/>
      </supplementary-material>
      <supplementary-material id="app16">
        <label>Multimedia Appendix 16</label>
        <p>Screenshots for nationwide dashboards and trackers, June 16, 2022.</p>
        <media xlink:href="humanfactors_v10i1e43819_app16.pdf" xlink:title="PDF File  (Adobe PDF File), 2986 KB"/>
      </supplementary-material>
      <supplementary-material id="app17">
        <label>Multimedia Appendix 17</label>
        <p>Screenshots for global dashboards and trackers, June 16, 2022.</p>
        <media xlink:href="humanfactors_v10i1e43819_app17.pdf" xlink:title="PDF File  (Adobe PDF File), 2763 KB"/>
      </supplementary-material>
      <supplementary-material id="app18">
        <label>Multimedia Appendix 18</label>
        <p>Screenshots for vaccine dashboards and trackers, June 16, 2022.</p>
        <media xlink:href="humanfactors_v10i1e43819_app18.pdf" xlink:title="PDF File  (Adobe PDF File), 6060 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">API</term>
          <def>
            <p>application programming interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDC</term>
          <def>
            <p>Centers for Disease Control and Prevention</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CSSE</term>
          <def>
            <p>Center for Systems Science and Engineering</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FAIR</term>
          <def>
            <p>Findable, Accessible, Interoperable, Reusable</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">JHU</term>
          <def>
            <p>Johns Hopkins University</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>Holshue</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>DeBolt</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lindquist</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lofy</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Wiesman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bruce</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Spitters</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ericson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkerson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tural</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Diaz</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cohn</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerber</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tong</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Lindstrom</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pallansch</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Weldon</surname>
              <given-names>WC</given-names>
            </name>
            <name name-style="western">
              <surname>Biggs</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Uyeki</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Pillai</surname>
              <given-names>SK</given-names>
            </name>
            <collab>Washington State 2019-nCoV Case Investigation Team</collab>
          </person-group>
          <article-title>First case of 2019 novel coronavirus in the United States</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <month>03</month>
          <day>05</day>
          <volume>382</volume>
          <issue>10</issue>
          <fpage>929</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32004427"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMoa2001191</pub-id>
          <pub-id pub-id-type="medline">32004427</pub-id>
          <pub-id pub-id-type="pmcid">PMC7092802</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>First travel-related case of 2019 novel coronavirus detected in United States</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2020</year>
          <month>1</month>
          <day>21</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/media/releases/2020/p0121-novel-coronavirus-travel-case.html">https://www.cdc.gov/media/releases/2020/p0121-novel-coronavirus-travel-case.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Richwine</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Marshall</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Challenges to public health reporting experienced by non-federal acute care hospitals, 2019</article-title>
          <source>Office of the National Coordinator for Health Information Technology (ONC)</source>
          <year>2021</year>
          <month>9</month>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/data/data-briefs/challenges-public-health-reporting-experienced-non-federal-acute-care-hospitals">https://www.healthit.gov/data/data-briefs/challenges-public-health-reporting-experienced-non-federal-acute-care-hospitals</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leatherby</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>What previous COVID-19 waves tell us about the virus now</article-title>
          <source>The New York Times</source>
          <year>2021</year>
          <month>10</month>
          <day>23</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nytimes.com/interactive/2021/10/23/us/covid-surges.html">https://www.nytimes.com/interactive/2021/10/23/us/covid-surges.html</ext-link>
          </comment>
        </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>Lewis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Superspreading drives the COVID pandemic - and could help to tame it</article-title>
          <source>Nature</source>
          <year>2021</year>
          <month>02</month>
          <volume>590</volume>
          <issue>7847</issue>
          <fpage>544</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1038/d41586-021-00460-x</pub-id>
          <pub-id pub-id-type="medline">33623168</pub-id>
          <pub-id pub-id-type="pii">10.1038/d41586-021-00460-x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Conroy</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>How to make a coronavirus data visualization that counts</article-title>
          <source>Nature Index, Dataviz</source>
          <year>2020</year>
          <month>7</month>
          <day>21</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nature.com/nature-index/news-blog/how-to-make-a-coronavirus-data-visualisation-that-counts-">https://www.nature.com/nature-index/news-blog/how-to-make-a-coronavirus-data-visualisation-that-counts-</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Field</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Mapping coronavirus, responsibly</article-title>
          <source>ArcGIS</source>
          <year>2020</year>
          <month>2</month>
          <day>25</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.esri.com/arcgis-blog/products/product/mapping/mapping-coronavirus-responsibly/">https://www.esri.com/arcgis-blog/products/product/mapping/mapping-coronavirus-responsibly/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Makulec</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>10 considerations before you create another chart about COVID-19</article-title>
          <source>Tableau</source>
          <year>2020</year>
          <month>3</month>
          <day>13</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tableau.com/about/blog/2020/3/ten-considerations-you-create-another-chart-about-covid-19">https://www.tableau.com/about/blog/2020/3/ten-considerations-you-create-another-chart-about-covid-19</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cotgreave</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>After a year of COVID-19 charts, eight data communication lessons learned</article-title>
          <source>Tableau blog</source>
          <year>2021</year>
          <month>4</month>
          <day>19</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tableau.com/about/blog/2021/4/eight-data-lessons-learned-after-year-covid-19-charts">https://www.tableau.com/about/blog/2021/4/eight-data-lessons-learned-after-year-covid-19-charts</ext-link>
          </comment>
        </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>Engledowl</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Weiland</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Data (mis)representation and COVID-19: leveraging misleading data visualizations for developing statistical literacy across grades 6–16</article-title>
          <source>J Stat Data Sci Educ</source>
          <year>2021</year>
          <month>05</month>
          <day>19</day>
          <volume>29</volume>
          <issue>2</issue>
          <fpage>160</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1080/26939169.2021.1915215</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>Peeples</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Lessons from the COVID data wizards</article-title>
          <source>Nature</source>
          <year>2022</year>
          <month>03</month>
          <volume>603</volume>
          <issue>7902</issue>
          <fpage>564</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1038/d41586-022-00792-2</pub-id>
          <pub-id pub-id-type="medline">35322256</pub-id>
          <pub-id pub-id-type="pii">10.1038/d41586-022-00792-2</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>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gaggiano</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Andris</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>AG</given-names>
            </name>
          </person-group>
          <article-title>Visualization design practices in a crisis: behind the scenes with COVID-19 dashboard creators</article-title>
          <source>IEEE Trans Vis Comput Graph</source>
          <year>2023</year>
          <month>1</month>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>1037</fpage>
          <lpage>47</lpage>
          <pub-id pub-id-type="doi">10.1109/TVCG.2022.3209493</pub-id>
          <pub-id pub-id-type="medline">36170401</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Swenson</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Millions track the pandemic on Johns Hopkins’s dashboard. Those who built it say some miss the real story</article-title>
          <source>The Washington Post</source>
          <year>2020</year>
          <month>6</month>
          <day>29</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.washingtonpost.com/local/johns-hopkins-tracker/2020/06/29/daea7eea-a03f-11ea-9590-1858a893bd59_story.html">https://www.washingtonpost.com/local/johns-hopkins-tracker/2020/06/29/daea7eea-a03f-11ea-9590-1858a893bd59_story.html</ext-link>
          </comment>
        </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>Dong</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Gardner</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>An interactive web-based dashboard to track COVID-19 in real time</article-title>
          <source>Lancet Infect Dis</source>
          <year>2020</year>
          <month>05</month>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>533</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32087114"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S1473-3099(20)30120-1</pub-id>
          <pub-id pub-id-type="medline">32087114</pub-id>
          <pub-id pub-id-type="pii">S1473-3099(20)30120-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7159018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zuo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ju</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>CovidNet: to bring data transparency in the era of COVID-19</article-title>
          <source>Proceedings of the 19th International Workshop on Data Mining in Bioinformatics</source>
          <year>2020</year>
          <conf-name>BIOKDD '20</conf-name>
          <conf-date>August 24, 2020</conf-date>
          <conf-loc>San Diego, CA, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://biokdd.org/biokdd20/regular_track.html"/>
          </comment>
          <pub-id pub-id-type="doi">10.48550/arXiv.2005.10948</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>Xu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Gutierrez</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mekaru</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sewalk</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Goodwin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Loskill</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cohn</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Hswen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Cobo</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Zarebski</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Hulland</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Scarpino</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Brownstein</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Pybus</surname>
              <given-names>OG</given-names>
            </name>
            <name name-style="western">
              <surname>Pigott</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Kraemer</surname>
              <given-names>MU</given-names>
            </name>
          </person-group>
          <article-title>Epidemiological data from the COVID-19 outbreak, real-time case information</article-title>
          <source>Sci Data</source>
          <year>2020</year>
          <month>03</month>
          <day>24</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>106</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41597-020-0448-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41597-020-0448-0</pub-id>
          <pub-id pub-id-type="medline">32210236</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41597-020-0448-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC7093412</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Padilla</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Barua</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bertini</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>AG</given-names>
            </name>
          </person-group>
          <article-title>Mapping the landscape of COVID-19 crisis visualizations</article-title>
          <source>Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          <year>2021</year>
          <month>5</month>
          <conf-name>CHI '21</conf-name>
          <conf-date>May 8-13, 2021</conf-date>
          <conf-loc>Yokohama, Japan</conf-loc>
          <fpage>1</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1145/3411764.3445381"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3411764.3445381</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Comba</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Data visualization for the understanding of COVID-19</article-title>
          <source>Comput Sci Eng</source>
          <year>2020</year>
          <month>10</month>
          <day>13</day>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>81</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/mcse.2020.3019834</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>Kamel Boulos</surname>
              <given-names>MN</given-names>
            </name>
            <name name-style="western">
              <surname>Geraghty</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>Geographical tracking and mapping of coronavirus disease COVID-19/severe acute respiratory syndrome coronavirus 2 (SARS-CoV-2) epidemic and associated events around the world: how 21st century GIS technologies are supporting the global fight against outbreaks and epidemics</article-title>
          <source>Int J Health Geogr</source>
          <year>2020</year>
          <month>03</month>
          <day>11</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>8</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ij-healthgeographics.biomedcentral.com/articles/10.1186/s12942-020-00202-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12942-020-00202-8</pub-id>
          <pub-id pub-id-type="medline">32160889</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12942-020-00202-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC7065369</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>Bernasconi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Grandi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A conceptual model for geo-online exploratory data visualization: the case of the COVID-19 pandemic</article-title>
          <source>Information</source>
          <year>2021</year>
          <month>02</month>
          <day>06</day>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>69</fpage>
          <pub-id pub-id-type="doi">10.3390/info12020069</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ivanković</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Barbazza</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bos</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Brito Fernandes</surname>
              <given-names>Ó</given-names>
            </name>
            <name name-style="western">
              <surname>Jamieson Gilmore</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jansen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kara</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Larrain</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Meza-Torres</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mulyanto</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Poldrugovac</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rotar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Willmington</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yelgezekova</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Allin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Klazinga</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kringos</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Features constituting actionable COVID-19 dashboards: descriptive assessment and expert appraisal of 158 public web-based COVID-19 dashboards</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>02</month>
          <day>24</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>e25682</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/2/e25682/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25682</pub-id>
          <pub-id pub-id-type="medline">33577467</pub-id>
          <pub-id pub-id-type="pii">v23i2e25682</pub-id>
          <pub-id pub-id-type="pmcid">PMC7906125</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Padilla</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hosseinpour</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fygenson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chunara</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bertini</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Impact of COVID-19 forecast visualizations on pandemic risk perceptions</article-title>
          <source>Sci Rep</source>
          <year>2022</year>
          <month>02</month>
          <day>07</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>2014</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-022-05353-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-022-05353-1</pub-id>
          <pub-id pub-id-type="medline">35132079</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-022-05353-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC8821632</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>Li</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Visualizing COVID-19 information for public: designs, effectiveness, and preference of thematic maps</article-title>
          <source>Human Behav Emerg Tech</source>
          <year>2021</year>
          <month>01</month>
          <day>05</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>97</fpage>
          <lpage>106</lpage>
          <pub-id pub-id-type="doi">10.1002/hbe2.248</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>Fang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gui</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the effectiveness and efficiency of risk communication for maps depicting the hazard of COVID-19</article-title>
          <source>Trans GIS</source>
          <year>2022</year>
          <month>05</month>
          <volume>26</volume>
          <issue>3</issue>
          <fpage>1158</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34512105"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/tgis.12814</pub-id>
          <pub-id pub-id-type="medline">34512105</pub-id>
          <pub-id pub-id-type="pii">TGIS12814</pub-id>
          <pub-id pub-id-type="pmcid">PMC8420161</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Çay</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nagel</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yantaç</surname>
              <given-names>AE</given-names>
            </name>
          </person-group>
          <article-title>Understanding user experience of COVID-19 maps through remote elicitation interviews</article-title>
          <source>Proceedings of the 2020 IEEE Workshop on Evaluation and Beyond - Methodological Approaches to Visualization</source>
          <year>2020</year>
          <conf-name>BELIV '20</conf-name>
          <conf-date>October 25-30, 2020</conf-date>
          <conf-loc>Salt Lake City, UT, USA</conf-loc>
          <fpage>65</fpage>
          <lpage>73</lpage>
          <pub-id pub-id-type="doi">10.1109/beliv51497.2020.00015</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>‘Every day is a new surprise.' Inside the effort to produce the world's most popular coronavirus tracker</article-title>
          <source>Science</source>
          <year>2020</year>
          <month>4</month>
          <day>6</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencemag.org/news/2020/04/every-day-new-surprise-inside-effort-produce-world-s-most-popular-coronavirus-tracker">https://www.sciencemag.org/news/2020/04/every-day-new-surprise-inside-effort-produce-world-s-most-popular-coronavirus-tracker</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fisher-Hwang</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A comparison of your major COVID-19 data sources</article-title>
          <source>Source</source>
          <year>2020</year>
          <month>5</month>
          <day>5</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://source.opennews.org/articles/comparison-four-major-covid-19-data-sources/">https://source.opennews.org/articles/comparison-four-major-covid-19-data-sources/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>About USAFacts</article-title>
          <source>USAFacts</source>
          <year>2019</year>
          <month>8</month>
          <day>26</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://usafacts.org/about-usafacts/">https://usafacts.org/about-usafacts/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <article-title>About Us</article-title>
          <source>1Point3Acres</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://coronavirus.1point3acres.com/en/about">https://coronavirus.1point3acres.com/en/about</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>About Us</article-title>
          <source>The COVID Tracking Project</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covidtracking.com/about">https://covidtracking.com/about</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>Cases and Deaths by County - Archive</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/coronavirus/2019-ncov/cases-updates/county-map-archived.html?state=AL">https://www.cdc.gov/coronavirus/2019-ncov/cases-updates/county-map-archived.html?state=AL</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>United States COVID-19 county level data sources</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2022</year>
          <month>12</month>
          <day>29</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://data.cdc.gov/Public-Health-Surveillance/United-States-COVID-19-County-Level-Data-Sources/7pvw-pdbr">https://data.cdc.gov/Public-Health-Surveillance/United-States-COVID-19-County-Level-Data-Sources/7pvw-pdbr</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19 Data Repository by the Center for Systems Science and Engineering (CSSE) at Johns Hopkins University</article-title>
          <source>GitHub</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/CSSEGISandData/COVID-19">https://github.com/CSSEGISandData/COVID-19</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <article-title>WHO outbreak communication guidelines</article-title>
          <source>World Health Organization</source>
          <year>2005</year>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/who-outbreak-communication-guidelines">https://www.who.int/publications/i/item/who-outbreak-communication-guidelines</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woodie</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Coming to grips with COVID-19's data quality challenges</article-title>
          <source>Datanami</source>
          <year>2020</year>
          <month>4</month>
          <day>21</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.datanami.com/2020/04/21/coming-to-grips-with-covid-19s-data-quality-challenges">https://www.datanami.com/2020/04/21/coming-to-grips-with-covid-19s-data-quality-challenges</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ritchie</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ortiz-Ospina</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Roser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hasell</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 deaths and cases: how do sources compare?</article-title>
          <source>Our World In Data</source>
          <year>2020</year>
          <month>3</month>
          <day>19</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ourworldindata.org/covid-sources-comparison">https://ourworldindata.org/covid-sources-comparison</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dyer</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The story of Worldometer, the quick project that became one of the most popular sites on the internet</article-title>
          <source>New Statesman</source>
          <year>2020</year>
          <month>5</month>
          <day>8</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.newstatesman.com/science-tech/coronavirus/2020/05/story-worldometer-quick-project-became-one-most-popular-sites">https://www.newstatesman.com/science-tech/coronavirus/2020/05/story-worldometer-quick-project-became-one-most-popular-sites</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kissane</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Where to find simple COVID-19 data for the US</article-title>
          <source>The COVID Tracking Project</source>
          <year>2021</year>
          <month>3</month>
          <day>4</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covidtracking.com/analysis-updates/simple-covid-data">https://covidtracking.com/analysis-updates/simple-covid-data</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>Data definitions</article-title>
          <source>The COVID Tracking Project</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covidtracking.com/about-data/data-definitions">https://covidtracking.com/about-data/data-definitions</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <article-title>Update to the standardized surveillance case definition and national notification for 2019 novel coronavirus disease (COVID-19), Interim-20-ID-02</article-title>
          <source>Council of State and Territorial Epidemiologists</source>
          <year>2020</year>
          <month>8</month>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cste.org/resource/resmgr/ps/positionstatement2020/Interim-20-ID-02_COVID-19_up.pdf">https://www.cste.org/resource/resmgr/ps/positionstatement2020/Interim-20-ID-02_COVID-19_up.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schneider</surname>
              <given-names>GS</given-names>
            </name>
          </person-group>
          <article-title>Virginia says it will stop counting antibody tests as coronavirus tests in daily reports</article-title>
          <source>The Washington Post</source>
          <year>2020</year>
          <month>5</month>
          <day>14</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.washingtonpost.com/local/virginia-antibody-covid-19-tests-northam-reopening/2020/05/14/fa9f62b0-95e4-11ea-82b4-c8db161ff6e5_story.html">https://www.washingtonpost.com/local/virginia-antibody-covid-19-tests-northam-reopening/2020/05/14/fa9f62b0-95e4-11ea-82b4-c8db161ff6e5_story.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>QP</given-names>
            </name>
            <name name-style="western">
              <surname>Kissane</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Position statement on antibody data reporting</article-title>
          <source>The COVID Tracking Project</source>
          <year>2020</year>
          <month>5</month>
          <day>14</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covidtracking.com/analysis-updates/antibody-data-reporting">https://covidtracking.com/analysis-updates/antibody-data-reporting</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tiger</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baba</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Reports on “recovered” COVID-19 cases inconsistent and incomplete; numbers elusive and may mislead on real medical impact of virus</article-title>
          <source>CU-Citizen Access</source>
          <year>2020</year>
          <month>7</month>
          <day>10</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cu-citizenaccess.org/2020/07/definitions-of-recovered-from-covid-19-vary-widely-across-the-u-s/">https://www.cu-citizenaccess.org/2020/07/definitions-of-recovered-from-covid-19-vary-widely-across-the-u-s/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <article-title>Coronavirus Disease 2019 (COVID-19) 2021 case definition</article-title>
          <source>Division of Health Informatics and Surveillance, Centers for Disease Control and Prevention</source>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ndc.services.cdc.gov/case-definitions/coronavirus-disease-2019-2021/">https://ndc.services.cdc.gov/case-definitions/coronavirus-disease-2019-2021/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Update to the standardized surveillance case definition and national notification for 2019 novel coronavirus disease (COVID-19), 21-ID-01</article-title>
          <source>Council of State and Territorial Epidemiologists</source>
          <year>2021</year>
          <month>8</month>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cste.org/resource/resmgr/ps/ps2021/21-ID-01_COVID-19_updated_Au.pdf">https://www.cste.org/resource/resmgr/ps/ps2021/21-ID-01_COVID-19_updated_Au.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Muth</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Why not to use two axes, and what to use instead</article-title>
          <source>Datawrapper</source>
          <year>2018</year>
          <month>5</month>
          <day>8</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blog.datawrapper.de/dualaxis/">https://blog.datawrapper.de/dualaxis/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Few</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dual-scaled axes in graphs: are they ever the best solution?</article-title>
          <source>Perceptual Edge newsletter</source>
          <year>2008</year>
          <month>3</month>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.perceptualedge.com/articles/visual_business_intelligence/dual-scaled_axes.pdf">https://www.perceptualedge.com/articles/visual_business_intelligence/dual-scaled_axes.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schneiderman</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The eyes have it: a task by data type taxonomy for information visualizations</article-title>
          <source>Proceedings 1996 IEEE Symposium on Visual Languages</source>
          <year>1996</year>
          <conf-name>VL '96</conf-name>
          <conf-date>September 3-6, 1996</conf-date>
          <conf-loc>Boulder, CO, USA</conf-loc>
          <fpage>336</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1109/vl.1996.545307</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>Romano</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sotis</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Dominioni</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Guidi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The scale of COVID-19 graphs affects understanding, attitudes, and policy preferences</article-title>
          <source>Health Econ</source>
          <year>2020</year>
          <month>11</month>
          <volume>29</volume>
          <issue>11</issue>
          <fpage>1482</fpage>
          <lpage>94</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32844495"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/hec.4143</pub-id>
          <pub-id pub-id-type="medline">32844495</pub-id>
          <pub-id pub-id-type="pmcid">PMC7461444</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <article-title>ASTHO Profile of State and Territorial Public Health. Volume 4</article-title>
          <source>Association of State and Territorial Health Officials</source>
          <year>2017</year>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.astho.org/Profile/Volume-Four/2016-ASTHO-Profile-of-State-and-Territorial-Public-Health/">https://www.astho.org/Profile/Volume-Four/2016-ASTHO-Profile-of-State-and-Territorial-Public-Health/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>Standardized surveillance case definition and national notification for 2019 novel coronavirus disease (COVID-19), Interim-20-ID-01</article-title>
          <source>Council of State and Territorial Epidemiologists</source>
          <year>2020</year>
          <month>4</month>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cste.org/resource/resmgr/ps/positionstatement2020/Interim-20-ID-01_COVID-19_NO.pdf">https://www.cste.org/resource/resmgr/ps/positionstatement2020/Interim-20-ID-01_COVID-19_NO.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19 Case Surveillance Public Use Data</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2022</year>
          <month>12</month>
          <day>6</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://data.cdc.gov/Case-Surveillance/COVID-19-Case-Surveillance-Public-Use-Data/vbim-akqf">https://data.cdc.gov/Case-Surveillance/COVID-19-Case-Surveillance-Public-Use-Data/vbim-akqf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>Assessment of new CDC COVID-19 data reporting</article-title>
          <source>The COVID Tracking Project</source>
          <year>2020</year>
          <month>5</month>
          <day>18</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covidtracking.com/about-data/cdc-comparison">https://covidtracking.com/about-data/cdc-comparison</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <article-title>How diagnostic tests work in the field — and why only a single date is not gonna work</article-title>
          <source>COVID Mapping Project</source>
          <year>2020</year>
          <month>4</month>
          <day>21</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.covidmappingproject.com/case-study/how-diagnostic-tests-work-in-the-field">https://www.covidmappingproject.com/case-study/how-diagnostic-tests-work-in-the-field</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="web">
          <article-title>How other states are tracking "new" cases. Case Studies</article-title>
          <source>COVID Mapping Project</source>
          <year>2020</year>
          <month>5</month>
          <day>13</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.covidmappingproject.com/case-study/how-other-states-are-tracking-new-cases">https://www.covidmappingproject.com/case-study/how-other-states-are-tracking-new-cases</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Madrigal</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>Why the pandemic experts failed: we’re still thinking about pandemic data in the wrong ways</article-title>
          <source>The Atlantic</source>
          <year>2021</year>
          <month>3</month>
          <day>16</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.theatlantic.com/science/archive/2021/03/americas-coronavirus-catastrophe-began-with-data/618287/[accessed">https://www.theatlantic.com/science/archive/2021/03/americas-coronavirus-catastrophe-began-with-data/618287/[accessed</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fast</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Millions of people are missing from CDC COVID data as states fail to report cases</article-title>
          <source>NPR</source>
          <year>2021</year>
          <month>9</month>
          <day>1</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.npr.org/2021/09/01/1032885251/millions-of-people-are-missing-from-cdc-covid-data-as-states-fail-to-report-case">https://www.npr.org/2021/09/01/1032885251/millions-of-people-are-missing-from-cdc-covid-data-as-states-fail-to-report-case</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>OK public health data exchange hindered COVID-19 case reporting</article-title>
          <source>EHR Intelligence</source>
          <year>2021</year>
          <month>8</month>
          <day>17</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ehrintelligence.com/news/ok-public-health-data-exchange-hindered-covid-19-case-reporting">https://ehrintelligence.com/news/ok-public-health-data-exchange-hindered-covid-19-case-reporting</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McPhillips</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The US still isn’t getting COVID-19 data right</article-title>
          <source>CNN</source>
          <year>2022</year>
          <month>2</month>
          <day>21</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnn.com/2022/02/10/health/covid-data-problems/index.html">https://www.cnn.com/2022/02/10/health/covid-data-problems/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mandavilli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The C.D.C. isn’t publishing large portions of the COVID data it collects</article-title>
          <source>The New York Times</source>
          <year>2022</year>
          <month>2</month>
          <day>20</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nytimes.com/2022/02/20/health/covid-cdc-data.html">https://www.nytimes.com/2022/02/20/health/covid-cdc-data.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kasakove</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>As at-home tests surge, doubts rise about accuracy of public COVID counts</article-title>
          <source>The New York Times</source>
          <year>2021</year>
          <month>12</month>
          <day>30</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nytimes.com/2021/12/30/us/at-home-rapid-covid-tests-cases.html">https://www.nytimes.com/2021/12/30/us/at-home-rapid-covid-tests-cases.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McPhillips</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Undercounted COVID-19 cases leave US with a blind spot as BA.5 variant becomes dominant</article-title>
          <source>CNN</source>
          <year>2022</year>
          <month>7</month>
          <day>11</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnn.com/2022/07/11/health/ba-5-hidden-covid-case-increase/index.html">https://www.cnn.com/2022/07/11/health/ba-5-hidden-covid-case-increase/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cousijn</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>FAIR data reuse – the path through data citation</article-title>
          <source>Data Intell</source>
          <year>2020</year>
          <month>01</month>
          <day>01</day>
          <volume>2</volume>
          <issue>1-2</issue>
          <fpage>78</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1162/dint_a_00030</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="web">
          <article-title>Former CDC Director and Resolve to Save Lives president and CEO, Dr. Tom Frieden, warns of COVID-19 data myths and misuses, outlines metrics that matter</article-title>
          <source>Prevent Epidemics</source>
          <year>2020</year>
          <month>6</month>
          <day>11</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://preventepidemics.org/covid19/press/former-cdc-director-and-resolve-to-save-lives-president-and-ceo-dr-tom-frieden-warns-of-covid-19-data-myths-and-misuses-outlines-metrics-that-matter/">https://tinyurl.com/2p8rb6xb</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Correll</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Ethical dimensions of visualization research</article-title>
          <source>Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems</source>
          <year>2019</year>
          <month>5</month>
          <conf-name>CHI '19</conf-name>
          <conf-date>May 4-9, 2019</conf-date>
          <conf-loc>Glasgow, UK</conf-loc>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1145/3290605.3300418</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pandey</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Manivannan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nov</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Satterthwaite</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bertini</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The persuasive power of data visualization</article-title>
          <source>IEEE Trans Visual Comput Graphics</source>
          <year>2014</year>
          <month>12</month>
          <day>31</day>
          <volume>20</volume>
          <issue>12</issue>
          <fpage>2211</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1109/tvcg.2014.2346419</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dragga</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Voss</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Cruel pies: the inhumanity of technical illustrations</article-title>
          <source>Tech Commun</source>
          <year>2001</year>
          <month>8</month>
          <volume>48</volume>
          <issue>3</issue>
          <fpage>265</fpage>
          <lpage>74</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://writeprofessionally.org/info-design-2017/files/2017/01/cruel_pies_voss_dragga.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>The People's CDC</collab>
          </person-group>
          <article-title>The CDC is beholden to corporations and lost our trust. We need to start our own</article-title>
          <source>The Guardian</source>
          <year>2022</year>
          <month>4</month>
          <day>3</day>
          <access-date>2023-01-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.theguardian.com/commentisfree/2022/apr/03/peoples-cdc-covid-guidelines">https://www.theguardian.com/commentisfree/2022/apr/03/peoples-cdc-covid-guidelines</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Monkman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>SZ</given-names>
            </name>
            <name name-style="western">
              <surname>Minshall</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Lesselroth</surname>
              <given-names>BJ</given-names>
            </name>
          </person-group>
          <article-title>Opportunities to improve COVID-19 dashboard designs for the public</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>11</month>
          <day>08</day>
          <volume>286</volume>
          <fpage>16</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210628</pub-id>
          <pub-id pub-id-type="medline">34755683</pub-id>
          <pub-id pub-id-type="pii">SHTI210628</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lavalle</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Maté</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Trujillo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rizzi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Visualization requirements for business intelligence analytics: a goal-based, iterative framework</article-title>
          <source>Proceedings of the IEEE 27th International Requirements Engineering Conference</source>
          <year>2019</year>
          <conf-name>RE '19</conf-name>
          <conf-date>September 23-27, 2019</conf-date>
          <conf-loc>Jeju, South Korea</conf-loc>
          <fpage>109</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1109/re.2019.00022</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Golfarelli</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rizzi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A model-driven approach to automate data visualization in big data analytics</article-title>
          <source>Inf Vis</source>
          <year>2020</year>
          <month>1</month>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>24</fpage>
          <lpage>47</lpage>
          <pub-id pub-id-type="doi">10.1177/1473871619858933</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
