states_info
Data source: Big Local News · About: big-local-datasette
3 rows where totalTestResultsField = "Total PCR Tests (People)"
This data as json, copyable, CSV (advanced)
Suggested facets: pui
| Link | rowid ▼ | state | notes | covid19Site | covid19SiteSecondary | covid19SiteTertiary | covid19SiteQuaternary | covid19SiteQuinary | covid19SiteOld | covidTrackingProjectPreferredTotalTestUnits | covidTrackingProjectPreferredTotalTestField | totalTestResultsField | pui | pum | name | fips | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 2 | AL | Alabama combines PCR and antigen tests in the total tests figure reported on the state's dashboard.Negative test results reported in our API and CSVs are calculated by subtracting **Confirmed cases** from **Total PCR tests (specimens)** in the absence of better data.On February 6, 2021, Alabama's **Total antibody tests (people)** decreased from 140,376 to 108,818 without explanation.On February 5, 2021, Alabama announced that they were experiencing a technical issue with their testing data. As a result, we were unable to update their Total antibody tests (people), Total PCR tests (people), and Negative PCR tests (people), which is calculated as Total PCR tests (people) minus Confirmed cases.On February 02, 2021, Alabama reported a large increase in Total antibody tests (people) of approximately 33,000 without explanation. Additionally, **Total PCR tests (people)** decreased by approximately 11,000 without explanation, resulting in a decrease in Negative PCR tests (people).On January 30, 2021, Alabama noted on their data dashboard that due to maintenance and upgrades, the Alabama NEDSS Base System did not run on the evening of January 29, 2021, and as as result there would be no update to their dashboard on January 30, 2021. We were only able to update their Currently hospitalized and Ever hospitalized on January 30, 2021.On January 22, 2021, Alabama noted that the Alabama Department of Public Health processed a backlog of 409 positive PCR tests dating back to November 19, 2020 through January 20, 2021, and that these tests would be included in their Confirmed cases and Cases (confirmed + probable) for January 22, 2021. As a result, not all new cases reported on January 22, 2021 were reported within the previous 24 hour period.On January 13, 2021, Alabama reported that it is reviewing a large number of deaths from the Alabama Center for Health Statistics (ACHS), an endeavor which began on November 11, 2020 and will continue until further notice. As a result, death numbers during this time period reported may inclu… | https://alpublichealth.maps.arcgis.com/apps/opsdashboard/index.html#/6d2771faa9da4a2786a509d82c8cf0f7 | https://alpublichealth.maps.arcgis.com/apps/opsdashboard/index.html#/6d2771faa9da4a2786a509d82c8cf0f7 | https://services7.arcgis.com/4RQmZZ0yaZkGR1zy/arcgis/rest/services/HospitalizedPatientTemporal_READ_ONLY/FeatureServer/1/query?where=1%3D1&orderbyfields=DateTxt+desc&outFields=%2A&resultRecordCount=1 | @alpublichealth | http://www.alabamapublichealth.gov/infectiousdiseases/2019-coronavirus.html | People | totalTestsPeopleViral | Total PCR Tests (People) | No data | false | Alabama | 1 | ||
| 16 | 16 | ID | Idaho's data is on a 1 day lag in our timeseries due to consistently updating after 7:30 pm Eastern Time, when we publish our daily update. Negative test results reported in our API and CSVs are calculated by subtracting **Confirmed cases** from **Total PCR tests (people)** in the absence of better data. As of January 31, 2021, Idaho does not update their COVID-19 data on Sundays, and data reported on Mondays includes data for both Sunday and Monday. Because their data is on a one day lag in our timeseries due to late updates, we will be unable to update their data on Mondays, and data reported on Tuesdays will include two days of data. On February 12, 2021, Idaho [announced](https://twitter.com/IDHW/status/1360362916973744131) via the official Idaho Department of Health and Welfare Twitter that there would be no update to their data on February 15, 2021 due to the President’s day holiday. Because Idaho’s data is on a one day lag in our timeseries, we were unable to update their data on February 16, 2021.On January 20, 2021, Idaho [announced](https://twitter.com/IDHW/status/1352057437608583168) that two deaths had been removed from their total after updated records indicated that they were not due to COVID-19. Because Idaho’s data is on a one day lag due to late updates, this affects our Deaths (confirmed + probable) and Deaths (confirmed) for January 21, 2021On January 18, 2021, Idaho [announced](https://twitter.com/IDHW/status/1351318456206032903) via the official Idaho Department of Health and Welfare twitter that there would be no update to their data due to the Martin Luther King Jr. Day holiday. Additionally, they noted that the data published on January 19, 2021 would include two days of data. Because Idaho’s data is on a one day lag in our timeseries this affects our data for January 19, 2021 and January 20, 2021.On January 12, 2021, Idaho reported 10 cumulative probable deaths on their dashboard, a decrease from the 179 probable deaths reported the day before. We suspect that this is an error, and in or… | https://coronavirus.idaho.gov/ | https://public.tableau.com/views/DPHIdahoCOVID-19Dashboard/Testing?%3Aembed=y&%3AshowVizHome=no&%3Adisplay_count=y | https://public.tableau.com/views/DPHIdahoCOVID-19Dashboard/Demographics?%3Aembed=y&%3AshowVizHome=no&%3Adisplay_count=y | https://public.tableau.com/views/DPHIdahoCOVID-19Dashboard/Hospitalizations?%3Aembed=y&%3Aembed=y&%3AshowVizHome=no&%3AshowVizHome=n&%3Adisplay_count=y&%3Adisplay_static_image=y&%3Alanguage=en&%3AapiID=host0#navType=0&navSrc=Parse | On February 13, 2021, the District of Columbia reported 426,830 **Total Test Encounters**, which is a decrease of 751 from the figure reported for the previous day. No explanation was available for this decrease.On February 12, 2021, the District of Columbia announced that their testing data for the day would be delayed. As a result, we were unable to update their Total PCR tests (test encounters) or Total PCR tests (people).On December 25, 2020, the District of Columbia announced on their [COVID-19 page](https://coronavirus.dc.gov/data) that there would be no update to their data on December 25, 2020 due to the Christmas holiday. Additionally, they noted that the data reported on December 26, 2020 will include numbers from December 24, 2020 and the data reported on December 27, 2020 will include numbers from December 25, 2020 and December 26, 2020.As of September 18, 2020, District of Columbia's total test results are drawn from our total`TestEncountersViral` field instead of calculated via positive+negative.As of August 29, 2020, we store the “total overall tested” timeseries in our **Total Test Encounters (PCR)** field despite the following: According to our outreach, the District of Columbia’s “total overall tested” figure on its dashboard represents test encounters, the number of unique individuals tested per day, with one exception, if an individual receives a positive and a negative test on the same day, they are counted twice rather than once. On May 25, 2020, the District of Columbia decreased the district's **total tests** number by 11,000 to reflect only DC residents.On February 12, 2021, the District of Columbia announced that their testing data for the day would be delayed. As a result, we were unable to update their Total PCR tests (test encounters) or Total PCR tests (people). | @IDHW | https://coronavirus.idaho.gov/ | People | totalTestsPeopleViral | Total PCR Tests (People) | All data | false | Idaho | 16 |
| 46 | 46 | SD | On February 11, 2021, South Dakota [announced](https://twitter.com/SDDOH/status/1359925746219814916?s=20) on the official South Dakota Department of Health twitter that “a large number of COVID-19 test results are reported in today’s update due to IT system updates completed on one of several reporting methods”. As a result, not all new tests reported on February 11, 2021 were reported in the previous 24 hour period.On December 24, 2020, South Dakota [announced](https://twitter.com/SDDOH/status/1342173217918746626) via the official South Dakota Department of Health twitter that there would be no update to their data on December 25, 2020 due to the holiday. Additionally, they noted that the data reported on December 26, 2020, would be the data which normally would have been reported on December 25, 2020, and the data reported on December 27, 2020 would include two days of data. On December 31, 2020, they noted that there would be no update to their data on January 1, 2021 due to the New Years holiday, and that the data reported on January 2, 2021, would be the data which normally would have been reported on January 1, 2021, and the data reported on January 3, 2021 would include two days of data.On November 26, 2020, South Dakota [announced](https://twitter.com/SDDOH/status/1332017785560576001?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Etweet) via the official South Dakota Department of Health twitter that there would be no update to their data on November 26, 2020. Additionally, data for both November 26, 2020 and November 27, 2020, will be published on November 27, 2020.On October, 7, 2020 South Dakota started reporting **Probable cases**. This added 473 new cases to South Dakota's **Total cases** number.As of September 18, 2020, South Dakota's total test results are drawn from our `totalTestsPeopleViral` field instead of calculated via positive+negative.On August 27, the South Dakota Department of Health included cases from August 25 and 26 in their update due to a reporting aberration, resulting in a 343 ca… | https://doh.sd.gov/COVID/Dashboard.aspx | @SDDOH | https://doh.sd.gov/news/Coronavirus.aspx | People | totalTestsPeopleViral | Total PCR Tests (People) | All data | false | South Dakota | 46 |
Advanced export
JSON shape: default, array, newline-delimited
CREATE TABLE [states_info] ( [state] TEXT, [notes] TEXT, [covid19Site] TEXT, [covid19SiteSecondary] TEXT, [covid19SiteTertiary] TEXT, [covid19SiteQuaternary] TEXT, [covid19SiteQuinary] TEXT, [twitter] TEXT, [covid19SiteOld] TEXT, [covidTrackingProjectPreferredTotalTestUnits] TEXT, [covidTrackingProjectPreferredTotalTestField] TEXT, [totalTestResultsField] TEXT, [pui] TEXT, [pum] TEXT, [name] TEXT, [fips] INTEGER );