Long time frames to detect the impact of changing COVID-19 measures, Canada, March to July 2020
Bibliographic record
Abstract
BackgroundMany countries have implemented population-wide interventions to control COVID-19, with varying extent and success. Many jurisdictions have moved to relax measures, while others have intensified efforts to reduce transmission.AimWe aimed to determine the time frame between a population-level change in COVID-19 measures and its impact on the number of cases.MethodsWe examined how long it takes for there to be a substantial difference between the number of cases that occur following a change in COVID-19 physical distancing measures and those that would have occurred at baseline. We then examined how long it takes to observe this difference, given delays and noise in reported cases. We used a susceptible-exposed-infectious-removed (SEIR)-type model and publicly available data from British Columbia, Canada, collected between March and July 2020.ResultsIt takes 10 days or more before we expect a substantial difference in the number of cases following a change in COVID-19 control measures, but 20-26 days to detect the impact of the change in reported data. The time frames are longer for smaller changes in control measures and are impacted by testing and reporting processes, with delays reaching ≥ 30 days.ConclusionThe time until a change in control measures has an observed impact is longer than the mean incubation period of COVID-19 and the commonly used 14-day time period. Policymakers and practitioners should consider this when assessing the impact of policy changes. Rapid, consistent and real-time COVID-19 surveillance is important to minimise these time frames.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.006 | 0.022 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".