It is increasingly recognized that policies have played a role in both alleviating and exacerbating the health and economic consequences of the COVID-19 pandemic. Yet there has been limited work to systematically evaluate the substantial variation in local COVID-19-related policies in the U.S. The objective of the U.S. COVID-19 County Policy (UCCP) Database is to systematically gather, characterize, and assess variation in U.S. county-level COVID-19-related policies. The current data upload represents the first wave of data collection, which includes data on over 20 policies gathered across 171 counties in 7 states during January-March 2021. These include county-level COVID-19-related policies within 3 policy domains that are likely to affect a variety of health outcomes: (1) containment/closure, (2) economic support, and (3) public health. In ongoing work, we are conducting retrospective longitudinal weekly data collection for the period 2020-2021 from a larger swath of 300+ U.S. counties in all 50 states and Washington D.C. The current database will be updated with new data as it becomes available, in late 2023 or early 2024.Researchers who use this database for their studies should acknowledge the funders below in all publications.

The New York Times is releasing a series of data files with cumulative counts of coronavirus cases in the United States, at the state and county level, over time. We are compiling this time series data from state and local governments and health departments in an attempt to provide a complete record of the ongoing outbreak.

Since the first reported coronavirus case in Washington State on Jan. 21, 2020, The Times has tracked cases of coronavirus in real time as they were identified after testing. Because of the widespread shortage of testing, however, the data is necessarily limited in the picture it presents of the outbreak.

We have used this data to power our maps and reporting tracking the outbreak, and it is now being made available to the public in response to requests from researchers, scientists and government officials who would like access to the data to better understand the outbreak.

The data begins with the first reported coronavirus case in Washington State on Jan. 21, 2020. We will publish regular updates to the data in this repository.

Abstract

Data collecting by local state and local health agencies. Compiled and visualized by The New York Times.

Documentation

This is the US Coronavirus data repository from The New York Times here U.S. coronavirus interactive site. This data includes COVID-19 cases and deaths reported by state and county. The New York Times compiled this data based on reports from state and local health agencies. More information on the data repository is available. For additional reporting and data visualizations, see The New York Times’ Interactive coronavirus data tool.

Data source: https://github.com/nytimes/covid-19-data

Beginning March 1, 2022, the "COVID-19 Case Surveillance Public Use Data" will be updated on a monthly basis. This case surveillance public use dataset has 12 elements for all COVID-19 cases shared with CDC and includes demographics, any exposure history, disease severity indicators and outcomes, presence of any underlying medical conditions and risk behaviors, and no geographic data. CDC has three COVID-19 case surveillance datasets: COVID-19 Case Surveillance Public Use Data with Geography: Public use, patient-level dataset with clinical data (including symptoms), demographics, and county and state of residence. (19 data elements) COVID-19 Case Surveillance Public Use Data: Public use, patient-level dataset with clinical and symptom data and demographics, with no geographic data. (12 data elements) COVID-19 Case Surveillance Restricted Access Detailed Data: Restricted access, patient-level dataset with clinical and symptom data, demographics, and state and county of residence. Access requires a registration process and a data use agreement. (32 data elements) The following apply to all three datasets: Data elements can be found on the COVID-19 case report form located at www.cdc.gov/coronavirus/2019-ncov/downloads/pui-form.pdf. Data are considered provisional by CDC and are subject to change until the data are reconciled and verified with the state and territorial data providers. Some data cells are suppressed to protect individual privacy. The datasets will include all cases with the earliest date available in each record (date received by CDC or date related to illness/specimen collection) at least 14 days prior to the creation of the previously updated datasets. This 14-day lag allows case reporting to be stabilized and ensures that time-dependent outcome data are accurately captured. Datasets are updated monthly. Datasets are created using CDC’s operational Policy on Public Health Research and Nonresearch Data Management and Access and include protections designed to protect individual privacy. For more information about data collection and reporting, please see https://wwwn.cdc.gov/nndss/data-collection.html For more information about the COVID-19 case surveillance data, please see https://www.cdc.gov/coronavirus/2019-ncov/covid-data/faq-surveillance.html Overview The COVID-19 case surveillance database includes individual-level data reported to U.S. states and autonomous reporting entities, including New York City and the District of Columbia (D.C.), as well as U.S. territories and affiliates. On April 5, 2020, COVID-19 was added to the Nationally Notifiable Condition List and classified as “immediately notifiable, urgent (within 24 hours)” by a Council of State and Territorial Epidemiologists (CSTE) Interim Position Statement (Interim-20-ID-01). CSTE updated the position statement on August 5, 2020 to clarify the interpretation of antigen detection tests and serologic test results within the case classification. The statement also recommended that all states and territories enact laws to make COVID-19 reportable in their jurisdiction, and that jurisdictions conducting surveillance should submit case notifications to CDC. COVID-19 case surveillance data are collected by jurisdictions and reported volun

2019 Novel Coronavirus COVID-19 (2019-nCoV) Visual Dashboard and Map:
https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6

• Confirmed Cases by Country/Region/Sovereignty
• Confirmed Cases by Province/State/Dependency
• Deaths
• Recovered

Downloadable data:
https://github.com/CSSEGISandData/COVID-19

Additional Information about the Visual Dashboard:
https://systems.jhu.edu/research/public-health/ncov

Note: Reporting of new COVID-19 Case Surveillance data will be discontinued July 1, 2024, to align with the process of removing SARS-CoV-2 infections (COVID-19 cases) from the list of nationally notifiable diseases. Although these data will continue to be publicly available, the dataset will no longer be updated.

Authorizations to collect certain public health data expired at the end of the U.S. public health emergency declaration on May 11, 2023. The following jurisdictions discontinued COVID-19 case notifications to CDC: Iowa (11/8/21), Kansas (5/12/23), Kentucky (1/1/24), Louisiana (10/31/23), New Hampshire (5/23/23), and Oklahoma (5/2/23). Please note that these jurisdictions will not routinely send new case data after the dates indicated. As of 7/13/23, case notifications from Oregon will only include pediatric cases resulting in death.

This case surveillance public use dataset has 19 elements for all COVID-19 cases shared with CDC and includes demographics, geography (county and state of residence), any exposure history, disease severity indicators and outcomes, and presence of any underlying medical conditions and risk behaviors.

Currently, CDC provides the public with three versions of COVID-19 case surveillance line-listed data: this 19 data element dataset with geography, a 12 data element public use dataset, and a 33 data element restricted access dataset.

The following apply to the public use datasets and the restricted access dataset:

• Data elements can be found on the COVID-19 case report form located at www.cdc.gov/coronavirus/2019-ncov/downloads/pui-form.pdf.
• Data are considered provisional by CDC and are subject to change until the data are reconciled and verified with the state and territorial data providers.
• Some data are suppressed to protect individual privacy.
• Datasets will include all cases with the earliest date available in each record (date received by CDC or date related to illness/specimen collection) at least 14 days prior to the creation of the current datasets. This 14-day lag allows case reporting to be stabilized and ensure that time-dependent outcome data are accurately captured.
• Datasets are updated monthly.
• Datasets are created using CDC’s Policy on Public Health Research and Nonresearch Data Management and Access and include protections designed to protect individual privacy.
• For more information about data collection and reporting, please see https://www.cdc.gov/coronavirus/2019-ncov/covid-data/about-us-cases-deaths.html.
• For more information about the COVID-19 case surveillance data, please see https://www.cdc.gov/coronavirus/2019-ncov/covid-data/faq-surveillance.html
  

Overview

The COVID-19 case surveillance database includes individual-level data reported to U.S. states and autonomous reporting entities, including New York City and the District of Columbia (D.C.), as well as U.S. territories and affiliates. On April 5, 2020, COVID-19 was added to the Nationally Notifiable Condition List and classified as “immediately notifiable, urgent (within 24 hours)” by a Council of State and Territorial Epidemiologists (CSTE) Interim Position Statement (Interim-20-ID-01). CSTE updated the position statement on August 5, 2020, to clarify the interpretation of antigen detection tests and serologic test results within the case classification (Interim-20-ID-02). The statement also recommended that all states and territories enact laws to make COVID-19 reportable in their jurisdiction, and that jurisdictions conducting surveillance should submit case notifications to CDC. COVID-19 case surveillance data are collected by jurisdictions and reported voluntarily to CDC.

For more information: NNDSS Supports the COVID-19 Response | CDC.

COVID-19 Case Reports COVID-19 case reports are routinely submitted to CDC by public health jurisdictions using nationally standardized case reporting forms. On April 5, 2020, CSTE released an Interim Position Statement with national surveillance case definitions for COVID-19. Current versions of these case definitions are available at: https://ndc.services.cdc.gov/case-definitions/coronavirus-disease-2019-2021/. All cases reported on or after were requested to be shared by public health departments to CDC using the standardized case definitions for lab-confirmed or probable cases. On May 5, 2020, the standardized case reporting form was revised. States and territories continue to use this form.

Data are Considered Provisional

• The COVID-19 case surveillance data are dynamic; case reports can be modified at any time by the jurisdictions sharing COVID-19 data with CDC. CDC may update prior cases shared with CDC based on any updated information from jurisdictions. For instance, as new information is gathered about previously reported cases, health departments provide updated data to CDC. As more information and data become available, analyses might find changes in surveillance data and trends during a previously reported time window. Data may also be shared late with CDC due to the volume of COVID-19 cases.
• Annual finalized data: To create the final NNDSS data used in the annual tables, CDC works carefully with the reporting jurisdictions to reconcile the data received during the year until each state or territorial epidemiologist confirms that the data from their area are correct.

Access Addressing Gaps in Public Health Reporting of Race and Ethnicity for COVID-19, a report from the Council of State and Territorial Epidemiologists, to better understand the challenges in completing race and ethnicity data for COVID-19 and recommendations for improvement.

Data Limitations

To learn more about the limitations in using case surveillance data, visit FAQ: COVID-19 Data and Surveillance.

Data Quality Assurance Procedures

CDC’s Case Surveillance Section routinely performs data quality assurance procedures (i.e., ongoing corrections and logic checks to address data errors). To date, the following data cleaning steps have been implemented:

• Questions that have been left unanswered (blank) on the case report form are reclassified to a Missing value, if applicable to the question. For example, in the question "Was the individual hospitalized?" where the possible answer choices include "Yes," "No," or "Unknown," the blank value is recoded to "Missing" because the case report form did not include a response to the question.
• Logic checks are performed for date data. If an illogical date has been provided, CDC reviews the data with the reporting jurisdiction. For example, if a symptom onset date in the future is reported to CDC, this value is set to null until the reporting jurisdiction updates the date appropriately.
• Additional data quality processing to recode free text data is ongoing. Data on symptoms, race, ethnicity, and healthcare worker status have been prioritized.

Data Suppression

To prevent release of data that could be used to identify people, data cells are suppressed for low frequency (<11 COVID-19 case records with a given values). Suppression includes low frequency combinations of case month, geographic characteristics (county and state of residence), and demographic characteristics (sex, age group, race, and ethnicity). Suppressed values are re-coded to the NA answer option; records with data suppression are never removed.

Additional COVID-19 Data

COVID-19 data are available to the public as summary or aggregate count files, including total counts of cases and deaths by state and by county. These and other COVID-19 data are available from multiple public locations: COVID Data Tracker; United States COVID-19 Cases and Deaths by State; COVID-19 Vaccination Reporting Data Systems; and COVID-19 Death Data and Resources.

Notes:

March 1, 2022: The "COVID-19 Case Surveillance Public Use Data with Geography" will be updated on a monthly basis.

April 7, 2022: An adjustment was made to CDC’s cleaning algorithm for COVID-19 line level case notification data. An assumption in CDC's algorithm led to misclassifying deaths that were not COVID-19 related. The algorithm has since been revised, and this dataset update reflects corrected individual level information about death status for all cases collected to date.

June 25, 2024: An adjustment

For questions or comments about the database please contact:
Alexandra Skinner
skinnera@bu.edu
Research Fellow & Database Manager
Department of Health Law, Policy & Management
Boston University School of Public Health

Database of state policies on closures, shelter-in-place orders, housing protections, changes to Medicaid and SNAP, physical distancing closures, reopening, and more created by researchers at the Boston University School of Public Health. Policies included are state-wide directives or mandates, not guidance or recommendations. In order for a policy to be included, it must apply to the entire state. We are working quickly to go through state government websites to make the policy database as complete and accurate as possible in a rapidly changing policy context. If you use data on a given policy, we encourage you to triangulate based on additional sources of policy data and to review the source documentation to consider the coding decisions that are right for your work. Of course, please email us if you note a discrepancy so we can improve the database for everyone. State policy source documentation can be found at: tinyurl.com/statepolicysources.

The free database mapping COVID-19 treatment and vaccine development based on the global scientific research is available at https://covid19-help.org/.

Files provided here are curated partial data exports in the form of .csv files or full data export as .sql script generated with pg_dump from our PostgreSQL 12 database. You can also find .png file with our ER diagram of tables in .sql file in this repository.

Structure of CSV files

*On our site, compounds are named as substances

compounds.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Name - Name of the Substance/Compound (string)

3. Marketed name - The marketed name of the Substance/Compound (string)

4. Synonyms - Known synonyms (string)

5. Description - Description (HTML code)

6. Dietary sources - Dietary sources where the Substance/Compound can be found (string)

7. Dietary sources URL - Dietary sources URL (string)

8. Formula - Compound formula (HTML code)

9. Structure image URL - Url to our website with the structure image (string)

10. Status - Status of approval (string)

11. Therapeutic approach - Approach in which Substance/Compound works (string)

12. Drug status - Availability of Substance/Compound (string)

13. Additional data - Additional data in stringified JSON format with data as prescribing information and note (string)

14. General information - General information about Substance/Compound (HTML code)

references.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Impact factor - Impact factor of the scientific article (string)

3. Source title - Title of the scientific article (string)

4. Source URL - URL link of the scientific article (string)

5. Tested on species - What testing model was used for the study (string)

6. Published at - Date of publication of the scientific article (Date in ISO 8601 format)

clinical-trials.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Title - Title of the clinical trial study (string)

3. Acronym title - Acronym of title of the clinical trial study (string)

4. Source id - Unique identifier in the source database

5. Source id optional - Optional identifier in other databases (string)

6. Interventions - Description of interventions (string)

7. Study type - Type of the conducted study (string)

8. Study results - Has results? (string)

9. Phase - Current phase of the clinical trial (string)

10. Url - URL to clinical trial study page on clinicaltrials.gov (string)

11. Status - Status in which study currently is (string)

12. Start date - Date at which study was started (Date in ISO 8601 format)

13. Completion date - Date at which study was completed (Date in ISO 8601 format)

14. Additional data - Additional data in the form of stringified JSON with data as locations of study, study design, enrollment, age, outcome measures (string)

compound-reference-relations.csv

1. Reference id - Id of a reference in our DB (unsigned integer)

2. Compound id - Id of a substance in our DB (unsigned integer)

3. Note - Id of a substance in our DB (unsigned integer)

4. Is supporting - Is evidence supporting or contradictory (Boolean, true if supporting)

compound-clinical-trial.csv

1. Clinical trial id - Id of a clinical trial in our DB (unsigned integer)

2. Compound id - Id of a Substance/Compound in our DB (unsigned integer)

tags.csv

1. Id - Unique identifier in our database (unsigned integer)

2. Name - Name of the tag (string)

tags-entities.csv

1. Tag id - Id of a tag in our DB (unsigned integer)

2. Reference id - Id of a reference in our DB (unsigned integer)
   

API Specification

Our project also has an Open API that gives you access to our data in a format suitable for processing, particularly in JSON format.

https://covid19-help.org/api-specification

Services are split into five endpoints:

• Substances - /api/substances

• References - /api/references

• Substance-reference relations - /api/substance-reference-relations

• Clinical trials - /api/clinical-trials

• Clinical trials-substances relations - /api/clinical-trials-substances

Method of providing data

• All dates are text strings formatted in compliance with ISO 8601 as YYYY-MM-DD

• If the syntax request is incorrect (missing or incorrectly formatted parameters) an HTTP 400 Bad Request response will be returned. The body of the response may include an explanation.

• Data updated_at (used for querying changed-from) refers only to a particular entity and not its logical relations. Example: If a new substance reference relation is added, but the substance detail has not changed, this is reflected in the substance reference relation endpoint where a new entity with id and current dates in created_at and updated_at fields will be added, but in substances or references endpoint nothing has changed.

The recommended way of sequential download

• During the first download, it is possible to obtain all data by entering an old enough date in the parameter value changed-from, for example: changed-from=2020-01-01 It is important to write down the date on which the receiving the data was initiated let’s say 2020-10-20

• For repeated data downloads, it is sufficient to receive only the records in which something has changed. It can therefore be requested with the parameter changed-from=2020-10-20 (example from the previous bullet). Again, it is important to write down the date when the updates were downloaded (eg. 2020-10-20). This date will be used in the next update (refresh) of the data.

Services for entities

List of endpoint URLs:

• /api/substances

• /api/references

• /api/substance-reference-relations

• /api/clinical-trials

• /api/clinical-trials-substances

Format of the request

All endpoints have these parameters in common:

• changed-from - a parameter to return only the entities that have been modified on a given date or later.

• continue-after-id - a parameter to return only the entities that have a larger ID than specified in the parameter.

• limit - a parameter to return only the number of records specified (up to 1000). The preset number is 100.

Request example:

/api/references?changed-from=2020-01-01&continue-after-id=1&limit=100

Format of the response

The response format is the same for all endpoints.

• number_of_remaining_ids - the number of remaining entities that meet the specified criteria but are not displayed on the page. An integer of virtually unlimited size.

• entities - an array of entity details in JSON format.

Response example:

{

"number_of_remaining_ids" : 100,

"entities" : [

{

"id": 3,

"url": "https://www.ncbi.nlm.nih.gov/pubmed/32147628",

"title": "Discovering drugs to treat coronavirus disease 2019 (COVID-19).",

"impact_factor": "Discovering drugs to treat coronavirus disease 2019 (COVID-19).",

"tested_on_species": "in silico",

"publication_date": "2020-22-02",

"created_at": "2020-30-03",

"updated_at": "2020-31-03",

"deleted_at": null

},

{

"id": 4,

"url": "https://www.ncbi.nlm.nih.gov/pubmed/32157862",

"title": "CT Manifestations of Novel Coronavirus Pneumonia: A Case Report",

"impact_factor": "CT Manifestations of Novel Coronavirus Pneumonia: A Case Report",

"tested_on_species": "Patient",

"publication_date": "2020-06-03",

"created_at": "2020-30-03",

"updated_at": "2020-30-03",

"deleted_at": null

},

]

}

Endpoint details

Substances

URL: /api/substances

Substances

Data Description

Long-COVID related articles have been manually collected by information specialists.Please find further information here.

  Size

Training Development Test Total

Positive Examples 215 76 70 345

Negative Examples 199 62 68 345

Total 414 238 138 690

  Citation

@article{10.1093/database/baac048,author = {Langnickel, Lisa and Darms, Johannes and Heldt, Katharina and Ducks, Denise and Fluck, Juliane},title = "{Continuous development… See the full description on the dataset page: https://huggingface.co/datasets/llangnickel/long-covid-classification-data.

Serves as clearinghouse for monoclonal antibodies against SARS-CoV-2. Database will catalog contributed antibodies in searchable resource and provide interactive analysis tools for comparisons among them. Most potent antibodies will guide development of vaccines to stop current outbreak and protect against future pandemics.

SPRC19 seeks to document as completely as possible all U.S. state policy responses to the COVID-19 pandemic. This includes all policy actions originating from the executive (governor’s office as well as executive agencies), legislative, and judicial branches. An action represents any change in current COVID-19 policy set at the state level. Actions are identified by reading through source documents collected from state websites and other sources according to their effects on any of over two hundred different policy areas. Each action is coded on a variety of features. These include its policy topic area, the branch that made the action, the announcement date, the effective date, an expiration date (if given), and the relationship to prior actions in the same policy area. To access the data and documentation quickly, search the Table view for "SPRC19" or switch to the Tree view. SPRC19 contains over 40,000 policy actions covering over 200 different policy areas. The current version is completed through December 31, 2020. We are currently in the process of updating through March 2021. The current release extends the previous release by adding actions from September through December 2020. The SPRC19 database was assembled with the support of the National Science Foundation through the following grants (grants #1558509, #1637095, #1558661, #1558781, #1558561, #2028724, #2028675, and #2028674, #2148216) and the NIH (grant #1R21AI164391-01).

Background

The COVID-19 pandemic is a global healthcare emergency. Prediction models for COVID-19 imaging are rapidly being developed to support medical decision making in imaging. However, inadequate availability of a diverse annotated dataset has limited the performance and generalizability of existing models.

Purpose

To create the first multi-institutional, multi-national expert annotated COVID-19 imaging dataset made freely available to the machine learning community as a research and educational resource for COVID-19 chest imaging. The Radiological Society of North America (RSNA) assembled the RSNA International COVID-19 Open Radiology Database (RICORD) collection of COVID-related imaging datasets and expert annotations to support research and education. RICORD data will be incorporated in the Medical Imaging and Data Resource Center (MIDRC), a multi-institutional research data repository funded by the National Institute of Biomedical Imaging and Bioengineering of the National Institutes of Health.

Materials and Methods

This dataset was a collaboration between the RSNA and Society of Thoracic Radiology (STR).

Results

The RSNA International COVID-19 Open Annotated Radiology Database (RICORD) release 1b consists of 120 thoracic computed tomography (CT) scans of COVID negative patients from four international sites.

Patient Selection: Patients at least 18 years in age receiving negative diagnosis for COVID-19.

Data Abstract

1. 120 de-identified Thoracic CT scans from COVID negative patients.

2. Supporting clinical variables: MRN*, Age, Exam Date/Time*, Exam Description, Sex, Study UID*, Image Count, Modality, Symptomatic, Testing Result, Specimen Source (* pseudonymous values).

Research Benefits

As this is a public dataset, RICORD is available for non-commercial use (and further enrichment) by the research and education communities which may include development of educational resources for COVID-19, use of RICORD to create AI systems for diagnosis and quantification, benchmarking performance for existing solutions, exploration of distributed/federated learning, further annotation or data augmentation efforts, and evaluation of the examinations for disease entities beyond COVID-19 pneumonia. Deliberate consideration of the detailed annotation schema, demographics, and other included meta-data will be critical when generating cohorts with RICORD, particularly as more public COVID-19 imaging datasets are made available via complementary and parallel efforts. It is important to emphasize that there are limitations to the clinical “ground truth” as the SARS-CoV-2 RT-PCR tests have widely documented limitations and are subject to both false-negative and false-positive results which impact the distribution of the included imaging data, and may have led to an unknown epidemiologic distortion of patients based on the inclusion criteria. These limitations notwithstanding, RICORD has achieved the stated objectives for data complexity, heterogeneity, and high-quality expert annotations as a comprehensive COVID-19 thoracic imaging data resource.

This is the US Coronavirus data repository from The New York Times . This data includes COVID-19 cases and deaths reported by state and county. The New York Times compiled this data based on reports from state and local health agencies. More information on the data repository is available here . For additional reporting and data visualizations, see The New York Times’ U.S. coronavirus interactive site . This public dataset is hosted in Google BigQuery and is included in BigQuery's 1TB/mo of free tier processing. This means that each user receives 1TB of free BigQuery processing every month, which can be used to run queries on this public dataset. Watch this short video to learn how to get started quickly using BigQuery to access public datasets. What is BigQuery . This dataset has significant public interest in light of the COVID-19 crisis. All bytes processed in queries against this dataset will be zeroed out, making this part of the query free. Data joined with the dataset will be billed at the normal rate to prevent abuse. After September 15, queries over these datasets will revert to the normal billing rate. Users of The New York Times public-use data files must comply with data use restrictions to ensure that the information will be used solely for noncommercial purposes.

The Emergency Use Authorization Database (EUAdb) contains information from the United States Food and Drug Administration (FDA) on emergency use authorizations (EUA) for RT-qPCR (real-time quantitative polymerase chain reaction) molecular testing protocols. The source documentation can be found on the FDA website. To create the EUAdb, information from the authorization letters and EUA summaries were transcribed under standardized variables, which include laboratories, tests, sampling techniques, primer sets, instruments, and manufacturer information.

Sciensano, the Belgian institute for health, is responsible for the epidemiological follow-up of the COVID-19 epidemic in collaboration with its partners and other healthcare actors. The data collected can provide insight into the dynamics of the epidemic, help to anticipate different scenarios and to elaborate possible measures to curb the spread of the virus.
From 31 March, Sciensano will make a set of data available to interested parties on a daily basis. This information is a support for decision making in the control of the epidemic.

The following datasets are published as open data:

• confirmed cases by date, age, sex and province
• confirmed cases by date and municipality
• cumulative number of confirmed cases by municipality
• hospitalizations by date and provinces
• mortality by date, age, sex, and province
• total number of tests performed by date

A description of the variables is available in the codebook. (Version: 2022-09-19)

The COVID-19 Open Research Dataset is an extensive machine-readable resource of over 45,000 scholarly articles, including over 33,000 with full text, about COVID-19 and the coronavirus family of viruses for use by the global research community. This dataset is intended to mobilize researchers to apply recent advances in natural language processing to generate new insights in support of the fight against this infectious disease.

The dataset is updated weekly and contains all COVID-19 and coronavirus-related research (e.g., SARS, MERS) from the following sources: PubMed's PMC open access corpus (using this query: COVID-19 and coronavirus research), additional COVID-19 research articles from a corpus maintained by the World Health Organization (WHO), and bioRxiv and medRxiv pre-prints (using this query: COVID-19 and coronavirus research). Also available is a comprehensive metadata file of 44,000 coronavirus and COVID-19 research articles with links to PubMed, Microsoft Academic, and the WHO COVID-19 database of publications (includes articles without open access full text).

This data from USAFacts provides US COVID-19 case and death counts by state and county. This data is sourced from the CDC, and state and local health agencies. For more information, see the USAFacts site on the Coronavirus. Interactive data visualizations are also available via USAFacts. This public dataset is hosted in Google BigQuery and is included in BigQuery's 1TB/mo of free tier processing. This means that each user receives 1TB of free BigQuery processing every month, which can be used to run queries on this public dataset. Watch this short video to learn how to get started quickly using BigQuery to access public datasets. What is BigQuery . This dataset has significant public interest in light of the COVID-19 crisis. All bytes processed in queries against this dataset will be zeroed out, making this part of the query free. Data joined with the dataset will be billed at the normal rate to prevent abuse. After September 15, queries over these datasets will revert to the normal billing rate.

The COVID Tracking Project collects information from 50 US states, the District of Columbia, and 5 other US territories to provide the most comprehensive testing data we can collect for the novel coronavirus, SARS-CoV-2. We attempt to include positive and negative results, pending tests, and total people tested for each state or district currently reporting that data.

Testing is a crucial part of any public health response, and sharing test data is essential to understanding this outbreak. The CDC is currently not publishing complete testing data, so we’re doing our best to collect it from each state and provide it to the public. The information is patchy and inconsistent, so we’re being transparent about what we find and how we handle it—the spreadsheet includes our live comments about changing data and how we’re working with incomplete information.

From here, you can also learn about our methodology, see who makes this, and find out what information states provide and how we handle it.

A global demographic database of COVID-19 cases, deaths, tests, and vaccines as reported by statistical agencies, standardized and in harmonized age groups.

After May 3, 2024, this dataset and webpage will no longer be updated because hospitals are no longer required to report data on COVID-19 hospital admissions, and hospital capacity and occupancy data, to HHS through CDC’s National Healthcare Safety Network. Data voluntarily reported to NHSN after May 1, 2024, will be available starting May 10, 2024, at COVID Data Tracker Hospitalizations.

The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Sunday to Saturday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities.

The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities.

For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-15 means the average/sum/coverage of the elements captured from that given facility starting and including Sunday, November 15, 2020, and ending and including reports for Saturday, November 21, 2020.

Reported elements include an append of either “_coverage”, “_sum”, or “_avg”.

• A “_coverage” append denotes how many times the facility reported that element during that collection week.
• A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week.
• A “_avg” append is the average of the reports provided for that facility for that element during that collection week.

The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”.

A story page was created to display both corrected and raw datasets and can be accessed at this link: https://healthdata.gov/stories/s/nhgk-5gpv

This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020.

Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect.

For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied.

For recent updates to the dataset, scroll to the bottom of the dataset description.

On May 3, 2021, the following fields have been added to this data set.

• hhs_ids
• previous_day_admission_adult_covid_confirmed_7_day_coverage
• previous_day_admission_pediatric_covid_confirmed_7_day_coverage
• previous_day_admission_adult_covid_suspected_7_day_coverage
• previous_day_admission_pediatric_covid_suspected_7_day_coverage
• previous_week_personnel_covid_vaccinated_doses_administered_7_day_sum
• total_personnel_covid_vaccinated_doses_none_7_day_sum
• total_personnel_covid_vaccinated_doses_one_7_day_sum
• total_personnel_covid_vaccinated_doses_all_7_day_sum
• previous_week_patients_covid_vaccinated_doses_one_7_day_sum
• previous_week_patients_covid_vaccinated_doses_all_7_day_sum

On May 8, 2021, this data set has been converted to a corrected data set. The corrections applied to this data set are to smooth out data anomalies caused by keyed in data errors. To help determine which records have had corrections made to it. An additional Boolean field called is_corrected has been added.

On May 13, 2021 Changed vaccination fields from sum to max or min fields. This reflects the maximum or minimum number reported for that metric in a given week.

On June 7, 2021 Changed vaccination fields from max or min fields to Wednesday reported only. This reflects that the number reported for that metric is only reported on Wednesdays in a given week.

On September 20, 2021, the following has been updated: The use of analytic dataset as a source.

On January 19, 2022, the following fields have been added to this dataset:

• inpatient_beds_used_covid_7_day_avg
• inpatient_beds_used_covid_7_day_sum
• inpatient_beds_used_covid_7_day_coverage

On April 28, 2022, the following pediatric fields have been added to this dataset:

• all_pediatric_inpatient_bed_occupied_7_day_avg
• all_pediatric_inpatient_bed_occupied_7_day_coverage
• all_pediatric_inpatient_bed_occupied_7_day_sum
• all_pediatric_inpatient_beds_7_day_avg
• all_pediatric_inpatient_beds_7_day_coverage
• all_pediatric_inpatient_beds_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_0_4_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_12_17_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_5_11_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_unknown_7_day_sum
• staffed_icu_pediatric_patients_confirmed_covid_7_day_avg
• staffed_icu_pediatric_patients_confirmed_covid_7_day_coverage
• staffed_icu_pediatric_patients_confirmed_covid_7_day_sum
• staffed_pediatric_icu_bed_occupancy_7_day_avg
• staffed_pediatric_icu_bed_occupancy_7_day_coverage
• staffed_pediatric_icu_bed_occupancy_7_day_sum
• total_staffed_pediatric_icu_beds_7_day_avg
• total_staffed_pediatric_icu_beds_7_day_coverage
• total_staffed_pediatric_icu_beds_7_day_sum

On October 24, 2022, the data includes more analytical calculations in efforts to provide a cleaner dataset. For a raw version of this dataset, please follow this link: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/uqq2-txqb

Due to changes in reporting requirements, after June 19, 2023, a collection week is defined as starting on a Sunday and ending on the next Saturday.