[Article] Improving CDC Data Practices: Recommendations for Improving the United States Centers for Disease Control (CDC) Data Practices for Pneumonia, Influenza, and COVID-19

This is a preprint of a new academic paper written by Tam Hunt, Josh Mitteldorf, Ph.D. and myself on the US Centers for Disease Control (CDC)’s data practices during the COVID-19 pandemic and for pneumonia and influenza prior to the pandemic. I am the corresponding author.

Abstract

During the pandemic, millions of Americans have become acquainted with the CDC because its reports and the data it collects affect their day-today lives. But the methodology used and even some of the data collected by CDC remain opaque to the public and to the community of academic epidemiology. In this paper, we highlight areas in which CDC methodology might be improved and where greater transparency might lead to broad collaboration. (1) “Excess” deaths are routinely reported, but not “years of life lost”, an easily-computed datum that is important for public policy. (2) What counts as an “excess death”? The method for computing the number of excess deaths does not include error bars and we show a substantial range of estimates is possible. (3) Pneumonia and influenza death data on different CDC pages is grossly contradictory. (4) The methodology for computing influenza deaths is not described in sufficient detail that an outside analyst might pursue the source of the discrepancy. (5) Guidelines for filling out death certificates have changed during the COVID-19 pandemic, preventing the comparison of 2020-21 death profiles with any previous year. We conclude with a series of explicit recommendations for greater consistency and transparency, and ultimately to make CDC data more useful to outside epidemiologists.

John F. McGowan, Ph.D., Tam Hunt, Josh Mitteldorf. Improving CDC Data Practices Recommendations for Improving the United States Centers for Disease Control (CDC) Data Practices for Pneumonia, Influenza, and COVID-19. Authorea. July 19, 2021.
DOI: 10.22541/au.162671168.86830026/v1

Here are the key recommendations from the paper:

Recommendations

In light of the previous discussion, we make a number of recommendations to improve CDC’s data practices, including improved observance of common scientific and engineering practice – such as use of significant figures and reporting of statistical and systematic errors. Common scientific and engineering practice is designed to prevent serious errors and should be followed rigorously in a crisis such as the COVID-19 pandemic.

Note that some of these recommendations may require changes in federal or state laws, federal or state regulations, or renegotiation of contracts between the federal government and states. This is probably the case for making the Deaths Master File (DMF), with names and dates of death of persons reported as deceased to the states and federal government, freely available to the public and other government agencies.

  • All CDC numbers, where possible, should be clearly identified as estimates, adjusted counts, or raw counts, with statistical errors and systematic errors given, using consistent clear standard language in all documents. The errors should be provided as both ninety-five percent (95%) confidence level intervals and the standard deviation – at least for the statistical errors.
  • In the case of adjusted counts, the raw count should be explicitly listed immediately following the adjusted count as well as a brief description of the adjustment and a reference for the adjustment methodology. For example, if the adjusted number of deaths in the United States in 2020 is 3.4 million but the raw count of deaths was 3.3 million with 100,000 deaths added to adjust for unreported deaths of undocumented immigrants, the web pages and reports would say:

Total deaths (2020): 3.4 million (adjusted, raw count 3.3 million, unreported deaths of undocumented immigrants, adjustment methodology citation: Smith et al, MMWR Volume X, Number Y)

  • The distinction between the leading causes of death report “pneumonia and influenza” deaths, ~55,000 per year pre-pandemic, and the FluView website “pneumonia and influenza” deaths, ~188,000 per year pre-pandemic, should be clarified in the labels and legends for the graphics and prominently in the table of leading causes of death or immediately adjacent text. Statistical and systematic errors on these numbers should be provided in graphs and tables.
  • In general, where grossly different raw counts, adjusted counts, or estimates are presented in CDC documents and websites with the same name, semantically equivalent or nearly equivalent names such as “pneumonia and influenza” and “influenza and pneumonia,” clearly distinct names should be used instead, or the reasons for the gross difference in the values should be prominently listed in the graphs and tables or immediately adjacent text. It should be easy for the public, busy health professionals, policy makers and others to recognize and understand the differences.
  • CDC should provide results for different models for the same data with similar R2 values – coefficient of determination – to give the audience a quick sense of the systematic modeling errors – since there is no generally accepted methodology for estimating the 95% confidence level for the systematic modeling errors. See Figure 7 above for an example.
  • All mathematical models should be free and open source with associated data provided using commonly used free open-source scientific programming languages such as Python or R, made available on the CDC website, GitHub, and other popular sources. The models and data should be provided in a package form such that anyone with access to a standard MS Windows, Mac OS X, or Linux/Unix computer can easily download and run the analysis – similar to the package structure used by the GNU project, for example.
  • Specifically, the influenza virus deaths model should be provided to the public as code and data. The justification for the increase in the number of deaths attributed to influenza (~6,000 to ~55,000) should be presented in clear language with supporting numbers, such as the false positive and negative rates for the laboratory influenza deaths and general diagnosis of influenza in the absence of a positive lab test as well as in the code and data.
  • With respect to excess deaths tracking, include all major select causes of death, rather than just the thirteen (13) in the cause-specific excess deaths that CDC tracks, which currently account for about 2/3 of all deaths.
  • Include a Years of Lives Lost (YLL) display for COVID-19 deathsi and non-COVID-19 deaths, as well as excess deaths analysis, due to the higher granularity of YLL analysis when compared to excess deaths analysis. Explain the pros and cons of both analytical tools. Do the same for any future pandemics or health crises.
  • Adopt or develop a different algorithm or algorithms for tracking excess deaths which are mostly attributed to non-infectious causes such as heart attacks, cancer, and strokes. The Farrington/Noufaily algorithms were specifically developed as an early warning for often non-lethal infectious disease outbreaks such as salmonella. A medically-based model or models that incorporates population demographics such as the aging “baby boom” and evolving death rates broken down by age, sex, and possibly other factors where known is probably a better practice rather than simple empirical trend models such as the Noufaily algorithm.
  • Eliminate the zeroing procedure in calculating excess deaths, in which negative excess deaths in some categories are set to zero, rather than being added to the full excess deaths sum over all categories.
  • The anonymized data with causes of death as close to the actual data as possible, e.g. the actual death certificates, should be available on the CDC website in a simple accessible widely used format such as CSV (comma separated values) files. The code used to aggregate the data into summary data such as the FluView website data files should also be public.
  • The full Deaths Master File (DMF) including the actual names of the deceased persons and dates of death should be made available to the general public, independent researchers, and others. This is critical to independent verification of many numbers from the CDC, SSA, and US Census.
  • COVID-19-related deaths figures should be tracked based on year-specific age of death, rather than 10-year age ranges, as is currently the case.
  • CDC frequently changes the structure and layout of the CSV files/spreadsheets on their websites. The CDC should either (1) not do this or (2) provide easy conversion between different file formats with each new format so it is trivial for third parties to quickly adapt to the changes without writing additional code. CDC should provide a program or program in a free and open source language like R to convert between the formats.
  • The CDC and other agencies should be required to announce and solicit public comment for changes to case definitions, data collection rules, etc. for key public policy data such as the COVID-19 case definitions, death certification guidelines, and coding rules. Other government agencies have significantly more public participation than CDC, which is appropriate in a modern democracy.
  • Any practices and policies imposed in a public emergency, such as case definitions, definitions of measured quantities, data reporting practices, etc. imposed without public comment and review, should have an expiration date (e.g. sixty days) beyond which they must be subject to public review. Public comment, reviews, and cost/benefit analyses should happen during this emergency period.

Enacting these reforms should reduce the risk of serious errors, increase the quality and accuracy of CDC data and analyses, as well as any policies or CDC guidelines based on the data and analysis, and strengthen public confidence in the CDC and public health policies.

(C) 2021 by John F. McGowan, Ph.D.

About Me

John F. McGowan, Ph.D. solves problems using mathematics and mathematical software, including developing gesture recognition for touch devices, video compression and speech recognition technologies. He has extensive experience developing software in C, C++, MATLAB, Python, Visual Basic and many other programming languages. He has been a Visiting Scholar at HP Labs developing computer vision algorithms and software for mobile devices. He has worked as a contractor at NASA Ames Research Center involved in the research and development of image and video processing algorithms and technology. He has published articles on the origin and evolution of life, the exploration of Mars (anticipating the discovery of methane on Mars), and cheap access to space. He has a Ph.D. in physics from the University of Illinois at Urbana-Champaign and a B.S. in physics from the California Institute of Technology (Caltech).

[Video] How to Sterilize Groceries with a UV Light and Your Refrigerator

Click on title slide below to see video (on free speech friendly Odysee video platform).

https://odysee.com/@MathematicalSoftware:5/how_to_sterilize_groceries_with_a_uv_light_and_your_refrigerator:a

Alternative Video: NewTube Archive BitChute

Censored Video: YouTube

How to Sterilize Groceries with a UV Light and Your Refrigerator

Video shows how to sterilize groceries (or other items) with a UV light and your refrigerator.

NOTE: UV light can be dangerous. UV light can damage your eyes and skin. Prolonged exposure may cause skin cancer. Wear safety goggles, protective clothing, and minimize any exposure to UV light. Hopefully in future videos I will show how to turn on the UV light only when the refrigerator is completely closed. Wear gloves as shown in the video to protect from viruses and bacteria when handling the groceries or other items to be sterilized and to protect hands from the UV light.

A UV light with an ON/OFF switch on the power cord outside the refrigerator can be turned ON/OFF inside the refrigerator without exposure to the UV light. An RF (radio) remote control may be able to turn a UV light ON/OFF inside the closed refrigerator, unlike a standard IR (infrared) remote control.

Items mentioned:

ROHS UV “Corn Lamp”: https://www.amazon.com/Sanitizer-Disinfection-Germicidal-Restaurant-Supermarket/dp/B08LG9TX48/ref=sr_1_20?crid=1IEXUQM2MVD8O&dchild=1&keywords=uv+light+sanitizer&qid=1625589690&sprefix=uv+light+san%2Caps%2C265&sr=8-20

UV Safety Goggles: https://www.amazon.com/Tool-Klean-Safety-Glasses-Protection/dp/B081BHTJT8/ref=sr_1_2?dchild=1&keywords=uv+safety+goggles&qid=1625589772&sr=8-2

We don’t receive any sponsorship or consideration from the makers of the items demonstrated. There are many UV lights and many brands of UV protective eyewear and clothing. Do your own research and choose the best items for you.

About Us:

Main Web Site: https://mathematical-software.com/
Censored Search: https://censored-search.com/
A search engine for censored Internet content. Find the answers to your problems censored by advertisers and other powerful interests!

Subscribe to our free Weekly Newsletter for articles and videos on practical mathematics, Internet Censorship, ways to fight back against censorship, and other topics by sending an email to: subscribe [at] mathematical-software.com

Avoid Internet Censorship by Subscribing to Our RSS News Feed: http://wordpress.jmcgowan.com/wp/feed/

Legal Disclaimers: http://wordpress.jmcgowan.com/wp/legal/

Support Us:
PATREON: https://www.patreon.com/mathsoft
SubscribeStar: https://www.subscribestar.com/mathsoft

BitChute (Video): https://www.bitchute.com/channel/HGgoa2H3WDac/
Brighteon (Video): https://www.brighteon.com/channels/mathsoft
Odysee (Video): https://odysee.com/@MathematicalSoftware:5
NewTube (Video): https://newtube.app/user/mathsoft
Minds (Video): https://www.minds.com/math_methods/
Locals (Video): https://mathematicalsoftware.locals.com/
Archive (Video): https://archive.org/details/@mathsoft

(C) 2021 by John F. McGowan, Ph.D.

About Me

John F. McGowan, Ph.D. solves problems using mathematics and mathematical software, including developing gesture recognition for touch devices, video compression and speech recognition technologies. He has extensive experience developing software in C, C++, MATLAB, Python, Visual Basic and many other programming languages. He has been a Visiting Scholar at HP Labs developing computer vision algorithms and software for mobile devices. He has worked as a contractor at NASA Ames Research Center involved in the research and development of image and video processing algorithms and technology. He has published articles on the origin and evolution of life, the exploration of Mars (anticipating the discovery of methane on Mars), and cheap access to space. He has a Ph.D. in physics from the University of Illinois at Urbana-Champaign and a B.S. in physics from the California Institute of Technology (Caltech).

[Video] How to Copy Data Tables into Working Python Code with EMACS Hotkey

https://odysee.com/@MathematicalSoftware:5/how_to_copy_data_tables_into_working_python_code_with_emacs_hotkey:5?

Alternative Video: BitChute NewTube ARCHIVE

Censored Video: YouTube

HOW TO COPY AND PASTE DATA TABLES INTO WORKING PYTHON CODE WITH EMACS

Video shows how to select, copy, and paste text data tables into working Python code with the Emacs text and code editor’s rectangle mode and an EMACS hotkey.

EMACS HOTKEY CODE SHOWN: http://wordpress.jmcgowan.com/wp/code-functions-to-convert-a-text-data-table-to-working-python-code-in-emacs/

The Emacs text and code editor has a built in rectangle mode for selecting, copying, pasting, and maniuplating rectangular regions in text since Emacs 24.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Rectangles.html

About Us:

Main Web Site: https://mathematical-software.com/
Censored Search: https://censored-search.com/
A search engine for censored Internet content. Find the answers to your problems censored by advertisers and other powerful interests!

Subscribe to our free Weekly Newsletter for articles and videos on practical mathematics, Internet Censorship, ways to fight back against censorship, and other topics by sending an email to: subscribe [at] mathematical-software.com

Avoid Internet Censorship by Subscribing to Our RSS News Feed: http://wordpress.jmcgowan.com/wp/feed/

Legal Disclaimers: http://wordpress.jmcgowan.com/wp/legal/

Support Us:
PATREON: https://www.patreon.com/mathsoft
SubscribeStar: https://www.subscribestar.com/mathsoft

BitChute (Video): https://www.bitchute.com/channel/HGgoa2H3WDac/
Brighteon (Video): https://www.brighteon.com/channels/mathsoft
Odysee (Video): https://odysee.com/@MathematicalSoftware:5
NewTube (Video): https://newtube.app/user/mathsoft
Minds (Video): https://www.minds.com/math_methods/
Locals (Video): https://mathematicalsoftware.locals.com/
Archive (Video): https://archive.org/details/@mathsoft

(C) 2021 by John F. McGowan, Ph.D.

About Me

John F. McGowan, Ph.D. solves problems using mathematics and mathematical software, including developing gesture recognition for touch devices, video compression and speech recognition technologies. He has extensive experience developing software in C, C++, MATLAB, Python, Visual Basic and many other programming languages. He has been a Visiting Scholar at HP Labs developing computer vision algorithms and software for mobile devices. He has worked as a contractor at NASA Ames Research Center involved in the research and development of image and video processing algorithms and technology. He has published articles on the origin and evolution of life, the exploration of Mars (anticipating the discovery of methane on Mars), and cheap access to space. He has a Ph.D. in physics from the University of Illinois at Urbana-Champaign and a B.S. in physics from the California Institute of Technology (Caltech).

[Code] Functions to Convert a Text Data Table to Working Python Code in EMACS

This is EMACS code and text editor LISP code to convert a space delimited text table into working Python code in EMACS. By default, it binds the python-table function below to the CTRL-= key sequence in EMACS for easy use. Add this code to your dot emacs EMACS startup file (~/.emacs). Restart EMACS to load the new dot emacs startup file.

Select the text data table in EMACS using rectangle-mark-mode — bound to CTRL-SPACEBAR by default — and press CTRL-= to convert the selected text data table to a Python NumPy fast numerical array definition. The emacs LISP function python-table automates the steps shown in the previous post “[Video] How to Copy and Paste Data Tables into Working Python Code with EMACS.”

(defun python-table-rows (inputStr)
  "Convert space delimited text table to working Python fast NumPy array definition code"
  (interactive "e")
  (setq head "table_name = np.array([\n")
  ;; replace thousands separator comma (,) with Python separator underscore (_)
  (setq temp1 (replace-regexp-in-string "," "_" inputStr))
  ;; enclose each row in [ (row) ],
;;  (setq temp2 (replace-regexp-in-string "\\(.*\\)" "[\\1]," temp1))
  (setq temp2 (replace-regexp-in-string "\\([a-zA-Z0-9_ \\.]*\\)" "[\\1]," temp1))
  ;; remove any spurious [],
  (setq temp2b (replace-regexp-in-string "\\[\\]," "" temp2))
  ;; convert repeated space delimeters to (comma)(space)
  (setq temp3 (replace-regexp-in-string " +" ", " temp2b))
  ;;  add ] to close list of lists, close paren ) to convert to numpy array
  (setq tail "])")
  ;; build entire Python code block
  (setq temp4 (concat head temp3))
  (setq temp5 (concat temp4 tail))
  ) ;; end defun python-table

(defun python-table ()
  " convert selected region with space separated text table to python code "
  (interactive)
  (message "running python-table") ;; progress message
  ;; use buffer-substring-no-properties to strip fonts etc.
  ;; get text from selected region and put in tmp variable
  (setq tmp (buffer-substring-no-properties (mark) (point)))
  ;; convert to Python Code and put in table variable
  (setq table (python-table-rows tmp))
  (message table) ;; progress message
  (delete-region (mark) (point))  ;; remove the region contents
  (insert table)  ;; replace with python code table definition
  ) ;; end defun ptable()

(global-set-key (kbd "C-=") 'python-table) ;; bind python-table to hot key

Use CTRL-X CTRL-F ~/.emacs RETURN to read in, display, and edit your dot emacs file in the EMACS editor.

How to Use

Add this code to your dot emacs file. Modify as appropriate if you know what you are doing.

Restart emacs.

Use the EMACS rectangle-mark-mode command — usually bound to CTRL-X SPACEBAR in EMACS — to select a rectangular text table as in the text below. Use Edit Menu | Copy or ESC-W to copy the text data table in EMACS.

This is an example of selecting, copying, and pasting a text table
into Python source code using the Emacs code and text editor.

Python is a popular programming language. With add on packages
such as NumPy, SciPy, and Matplotlib, it is a leading tool
for data analysis, scientific and numerical programming.

Demo Text Table
0.5      276
2.5      328
6.5      134
12.0     139
17.0   1,807 random notes here
22.0   3,342
29.5   5,340 commentary here
39.5   3,316
49.5   2,106
59.5   1,360 doodling here
69.5     562
79.5     270
89.5     120

This data is so great.

Three ways to select a rectangular text region in Emacs:

ESC-x rectangle-mark-mode
CTRL-X SPACE
SHIFT-(mouse drag)

URL: http://www.mathematical-software.com/

Use CTRL-y to paste the selected text table into Python code. Select the table and use CTRL-= to convert to working Python source code — a NumPy fast array definition with the values from the text table. The Python add-on packages NumPy, SciPy and MatPlotLib provide extensive numerical and statistical analysis functions and plotting.

(C) 2021 by John F. McGowan, Ph.D.

About Me

John F. McGowan, Ph.D. solves problems using mathematics and mathematical software, including developing gesture recognition for touch devices, video compression and speech recognition technologies. He has extensive experience developing software in C, C++, MATLAB, Python, Visual Basic and many other programming languages. He has been a Visiting Scholar at HP Labs developing computer vision algorithms and software for mobile devices. He has worked as a contractor at NASA Ames Research Center involved in the research and development of image and video processing algorithms and technology. He has published articles on the origin and evolution of life, the exploration of Mars (anticipating the discovery of methane on Mars), and cheap access to space. He has a Ph.D. in physics from the University of Illinois at Urbana-Champaign and a B.S. in physics from the California Institute of Technology (Caltech).

[Video] How to Copy and Paste Data Tables into Working Python Code with EMACS

https://odysee.com/@MathematicalSoftware:5/how_to_copy_and_paste_data_tables_into_working_python_code_with_emacs:7?

Other Free Video: ARCHIVE NewTube BitChute

Censored Video: YouTube

HOW TO COPY AND PASTE DATA TABLES INTO WORKING PYTHON CODE WITH EMACS

Video shows how to select, copy, and paste text data tables into working Python code with the Emacs text and code editor’s rectangle mode and emacs regular expressions (regexp).

The Emacs text and code editor has a built in rectangle mode for selecting, copying, pasting, and maniuplating rectangular regions in text since Emacs 24.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Rectangles.html

About Us:

Main Web Site: https://mathematical-software.com/
Censored Search: https://censored-search.com/
A search engine for censored Internet content. Find the answers to your problems censored by advertisers and other powerful interests!

Subscribe to our free Weekly Newsletter for articles and videos on practical mathematics, Internet Censorship, ways to fight back against censorship, and other topics by sending an email to: subscribe [at] mathematical-software.com

Avoid Internet Censorship by Subscribing to Our RSS News Feed: http://wordpress.jmcgowan.com/wp/feed/

Legal Disclaimers: http://wordpress.jmcgowan.com/wp/legal/

Support Us:
PATREON: https://www.patreon.com/mathsoft
SubscribeStar: https://www.subscribestar.com/mathsoft

BitChute (Video): https://www.bitchute.com/channel/HGgoa2H3WDac/
Brighteon (Video): https://www.brighteon.com/channels/mathsoft
Odysee (Video): https://odysee.com/@MathematicalSoftware:5
NewTube (Video): https://newtube.app/user/mathsoft
Minds (Video): https://www.minds.com/math_methods/
Locals (Video): https://mathematicalsoftware.locals.com/
Archive (Video): https://archive.org/details/@mathsoft

(C) 2021 by John F. McGowan, Ph.D.

About Me

John F. McGowan, Ph.D. solves problems using mathematics and mathematical software, including developing gesture recognition for touch devices, video compression and speech recognition technologies. He has extensive experience developing software in C, C++, MATLAB, Python, Visual Basic and many other programming languages. He has been a Visiting Scholar at HP Labs developing computer vision algorithms and software for mobile devices. He has worked as a contractor at NASA Ames Research Center involved in the research and development of image and video processing algorithms and technology. He has published articles on the origin and evolution of life, the exploration of Mars (anticipating the discovery of methane on Mars), and cheap access to space. He has a Ph.D. in physics from the University of Illinois at Urbana-Champaign and a B.S. in physics from the California Institute of Technology (Caltech).