Skip to search boxSkip to navigationSkip to main content

Comparing the efficiency of forward and backward contact tracing

  • Technical University of Denmark
    ,
  • Cornell University
Research Output:
Journal Article or Conference Article in Journal
Journal article
Peer-review

Publication Information

Output type

Research Output:
Journal Article or Conference Article in Journal
Journal article
Peer-review

Original language

English

Pages from-to (Number of pages)

Pages 034308 (11 pages)

Journal (Volume, Issue Number)

Physical Review E (Volume 108, Issue 3)

Publication milestones

  • Published - 01/09/2023

Publication status

Published - 01/09/2023

ISSN

2470-0045

Publication IDs

  • Scopus: 85172867073

Abstract

Tracing potentially infected contacts of confirmed cases is important when fighting outbreaks of many infectious diseases. The COVID-19 pandemic has motivated researchers to examine how different contact tracing strategies compare in terms of effectiveness (ability to mitigate infections) and cost efficiency (number of prevented infections per isolation). Two important strategies are so-called forward contact tracing (tracing to whom disease spreads) and backward contact tracing (tracing from whom disease spreads). Recently, Kojaku and colleagues reported that backward contact tracing was “profoundly more effective” than forward contact tracing, that contact tracing effectiveness “hinges on reaching the ‘source’ of infection,” and that contact tracing outperformed case isolation in terms of cost efficiency. Here we show that these conclusions are not true in general. They were based in part on simulations that vastly overestimated the effectiveness and efficiency of contact tracing. Our results show that the efficiency of contact tracing strategies is highly contextual; faced with a disease outbreak, the disease dynamics determine whether tracing infection sources or new cases is more impactful. Our results also demonstrate the importance of simulating disease spread and mitigation measures in parallel rather than sequentially.

Publication metrics

PlumX, opens in new tab

Mentions
1
Captures
5

Access to documents