United4Surveillance / signal-detection-tool

A tool for detection of signals in infectious disease surveillance data.
Other
8 stars 0 forks source link

[BUG] signal generated for the wrong week #322

Open efkot opened 1 month ago

efkot commented 1 month ago

Describe the Bug We aimed to check for signals by stratifying for different region levels. In the past month we have added 2 additional region variables. One is the region that each case lives in - smaller administrative unit than county and the other is the region that the case was reported at (region of the sanitary and epidemiological station). In some cases these 2 variables may be different ( when a case is sick and reported in a different region than the one the case lives at). Region of residence is coded as community and region of report is coded as region_level2.

A signal was generated for each of the region variables (total 2 signals) for week 30. After the generation of the signal, we always do a cross-check with surveillance data to check for outbreak status and other details. When we checked the excel file which was uploaded to the tool, there were no cases registered for these two region variables in week 30. on the contrary, cases were registered in week 31. Therefore, there shouldn't have been a signal for week 30 for both region variables, but only for week 31.

To Reproduce

Steps to reproduce the behavior:

1.Upload excel file

  1. No filter; strata for community and region_level2
  2. Check table of signals (there is no map generated in this case; only tables).

Expected Behavior

According to the reported cases, the signal should have been generated for week 31 and not week 30.

Environment (please complete the following information):