COVID-19 pandemic risk analytics: Data mining with reliability engineering methods for analyzing spreading behavior and comparison with infectious diseases
This article has been Reviewed by the following groups
Listed in
- Evaluated articles (ScreenIT)
Abstract
In December 2019, the world was confronted with the outbreak of the respiratory disease COVID-19 (Corona). The first infection (confirmed case) was detected in the City Wuhan, Hubei, China. First, it was an epidemic in China, but in the first quarter of 2020, it evolved into a pandemic, which continues to this day. The COVID-19 pandemic with its incredible speed of spread shows the vulnerability of a globalized and networked world. The first months of the pandemic were characterized by heavy burden on health systems. Worldwide, the population of countries was affected with severe restrictions, like educational system shutdown, public traffic system breakdown or a comprehensive lockdown. The severity of the burden was dependent on many factors, e.g. government, culture or health system. However, the burden happened regarding each country with slight time lags, cf. Bracke et al. (2020). This paper focuses on data analytics regarding infection data of the COVID-19 pandemic. It is a continuation of the research study COVID-19 pandemic data analytics: Data heterogeneity, spreading behavior, and lockdown impact, published by Bracke et al. (2020). The goal of this assessment is the evaluation/analysis of infection data mining considering model uncertainty, pandemic spreading behavior with lockdown impact and early second wave in Germany, Italy, Japan, New Zealand and France. Furthermore, a comparison with other infectious diseases (measles and influenza) is made. The used data base from Johns Hopkins University (JHU) runs from 01/22/2020 until 09/22/2020 with daily data, the dynamic development after 09/22/2020 is not considered. The measles/influenza analytics are based on Robert Koch Institute (RKI) data base 09/22/2020. Statistical models and methods from reliability engineering like Weibull distribution model or trend test are used to analyze the occurrence of infection.
Article activity feed
-
SciScore for 10.1101/2020.11.08.20227322: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
NIH rigor criteria are not applicable to paper type.Table 2: Resources
No key resources detected.
Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section about the limitations of the techniques employed in this study was not found. We encourage authors to address study limitations.Results from TrialIdentifier: No clinical trial numbers were referenced.
Results from Barzooka: We did not find any issues relating to the usage of bar graphs.
Results from JetFighter: We did not find any issues relating to colormaps.
Results from rtransparent:- Thank…
SciScore for 10.1101/2020.11.08.20227322: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
NIH rigor criteria are not applicable to paper type.Table 2: Resources
No key resources detected.
Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section about the limitations of the techniques employed in this study was not found. We encourage authors to address study limitations.Results from TrialIdentifier: No clinical trial numbers were referenced.
Results from Barzooka: We did not find any issues relating to the usage of bar graphs.
Results from JetFighter: We did not find any issues relating to colormaps.
Results from rtransparent:- Thank you for including a conflict of interest statement. Authors are encouraged to include this statement when submitting to a journal.
- Thank you for including a funding statement. Authors are encouraged to include this statement when submitting to a journal.
- No protocol registration statement was detected.
-