| Literature DB >> 32839755 |
Isobel Braithwaite1, Thomas Callender2, Miriam Bullock3, Robert W Aldridge1.
Abstract
Evidence for the use of automated or partly automated contact-tracing tools to contain severe acute respiratory syndrome coronavirus 2 is scarce. We did a systematic review of automated or partly automated contact tracing. We searched PubMed, EMBASE, OVID Global Health, EBSCO Medical COVID Information Portal, Cochrane Library, medRxiv, bioRxiv, arXiv, and Google Advanced for articles relevant to COVID-19, severe acute respiratory syndrome, Middle East respiratory syndrome, influenza, or Ebola virus, published from Jan 1, 2000, to April 14, 2020. We also included studies identified through professional networks up to April 30, 2020. We reviewed all full-text manuscripts. Primary outcomes were the number or proportion of contacts (or subsequent cases) identified. Secondary outcomes were indicators of outbreak control, uptake, resource use, cost-effectiveness, and lessons learnt. This study is registered with PROSPERO (CRD42020179822). Of the 4036 studies identified, 110 full-text studies were reviewed and 15 studies were included in the final analysis and quality assessment. No empirical evidence of the effectiveness of automated contact tracing (regarding contacts identified or transmission reduction) was identified. Four of seven included modelling studies that suggested that controlling COVID-19 requires a high population uptake of automated contact-tracing apps (estimates from 56% to 95%), typically alongside other control measures. Studies of partly automated contact tracing generally reported more complete contact identification and follow-up compared with manual systems. Automated contact tracing could potentially reduce transmission with sufficient population uptake. However, concerns regarding privacy and equity should be considered. Well designed prospective studies are needed given gaps in evidence of effectiveness, and to investigate the integration and relative effects of manual and automated systems. Large-scale manual contact tracing is therefore still key in most contexts.Entities:
Mesh:
Year: 2020 PMID: 32839755 PMCID: PMC7438082 DOI: 10.1016/S2589-7500(20)30184-9
Source DB: PubMed Journal: Lancet Digit Health ISSN: 2589-7500
FigurePreferred Reporting Items for Systematic Reviews and Meta-Analyses flow diagram
Summary of study designs, settings, diseases under study, and characteristics of populations, interventions, and comparators
| Bulchandani et al (2020) | Modelling study | Branching-tree mathematical model with derivations of mean-field equations for transitions to so-called digital herd immunity (ie, R0<1 because of automated contact tracing) | N/A | COVID-19 | Hypothetical modelled population | N/A | Automated | Not specified | Not specified | Not specified | None |
| Ferretti et al (2020) | Modelling study | Estimated the proportion of transmission from presymptomatic (from a series of 40 case pairs), asymptomatic, and symptomatic individuals and the environment; and quantified the effect of intervention (case isolation, contact tracing, and quarantine) at different delay periods and for different intervention success rates | N/A | COVID-19 | Hypothetical population network and contact structures, detailed in Fraser et al (2004) | N/A | Automated | Not specified | Smartphone app (standalone) | Location or proximity based | Non-automated contact tracing (comparisons based on delay to case isolation and contact quarantine) |
| Hinch et al (2020) | Modelling study | Multiple outcomes under different scenarios involving app-based contact tracing alongside non-targeted interventions, such as lockdowns and physical distancing | UK | COVID-19 | Hypothetical population network and contact structures selected to match age-stratified data reported in Mossong et al (2008) | N/A | Automated | Bluetooth | Smartphone app (standalone) | Proximity based | Other non-pharmaceutical outbreak control intervention |
| Kim and Paul (2020) | Modelling study | Effect of automated contact tracing to establish the minimum fraction of the population that needs to participate for R0<1 | Not specified | COVID-19 | Hypothetical population | N/A | Automated | Not specified | Not specified | Proximity based | Not specified |
| Kucharski et al (2020) | Modelling study | Effect of multiple interventions (eg, app-based contact tracing, limiting daily contacts to different extents [eg, four contacts per day] in settings other than work or school, and >1 intervention in parallel) on individual-level transmission events | UK | COVID-19 | Hypothetical population with contact structure based on data from the BBC Pandemic study of 40 162 UK participants | N/A | Automated | Not specified | Smartphone app (standalone) | Social contacts (conversational or physical contact), as per the contact definition of the BBC Pandemic study | >1 comparison (including with no contact tracing and manual contact tracing) |
| Xia and Lee (2020) | Modelling study | Effect of automated proximity-based contact tracing; derived formulae to estimate lower and upper bounds on the minimum adoption rate required for R0<1 | N/A | COVID-19 | Hypothetical population | N/A | Automated | Proximity-based GPS data | Smartphone app or standalone wearable device | Proximity based | None |
| Yasaka et al (2020) | Modelling study | Description of TrackCOVID, a decentralised Bluetooth-based contact-tracing app, including modelling of the population infected at different levels of uptake | N/A | COVID-19 | Hypothetical population | N/A | Automated | Checkpoints based on QR codes | Smartphone app (standalone) | Face to face with manual code scanning | Compared with no contact tracing |
| Danquah et al (2019) | Proof of concept study with phased introduction | Observational study regarding the introduction of the Ebola Contact Tracing app; detailed the number of contacts identified compared with previous system | Sierra Leone | Ebola | Contact tracers and contact-tracing coordinators | 86 contact tracers, 26 contact-tracing coordinators | Partly automated | Manual data entry | Smartphone app (standalone) | Recall based | Other (paper-based system) |
| Li et al (2017) | Case study | Automated identification of contacts within an inpatient setting (lists generated based on user-defined parameters) | Singapore | Multiple, including influenza A | Hospital inpatients at Changi General Hospital; system used by infection control team | Not specified | Partly automated | Real-time integration of patient movement and laboratory data | Computer-based infection control management system | Shared room, concurrent contact, and duration of contact | Non-automated contact tracing |
| Schafer et al (2016) | Case study | App-supported contact tracing using Epi Info Viral Hemorrhagic Fever app; automation of tasks (eg, generation of daily follow-up lists); calculation of follow-up window; production of transmission chain diagrams | Seven African countries, two US states | Ebola | Used by contact tracers and contact-tracing coordinators in eight countries | Not specified | Partly automated | Manual data entry | Computer based | Recall based | Paper-based contact-tracing systems and Field Information Management System (programme developed by WHO) |
| Sacks et al (2015) | Case study | Introduction of, use of, and lessons learned from the CommCare contact-tracing system in Guinea (compared with previous paper-based and Excel-based systems) | Guinea | Ebola | Used by contact tracers | Used by 210 contact tracers (of 366 who were trained) to collectively monitor 9162 contacts | Partly automated | Manual data entry | Smartphone app (standalone) | Recall based | Paper-based contact-tracing system (used in parallel within Guinea by other contact tracers) |
| Tom-Aba et al (2015) | Case study | Use of Open Data Kit Collect app developed by use of Open Data Kit and FormHub to support contact tracing in Nigeria; automated alerting and SMS if any contact met the probable case definition; also refers to Ebola Sense app (supports follow-up of identified contacts, includes automated search functionality to assign contact tracers) | Nigeria | Ebola | Used by contact tracers | Not specified; all public health personnel carrying out contact tracing for Ebola cases | Partly automated | GPS (for accountability of contact tracers rather than directly within tracing efforts) | Smartphone (or tablet) app (standalone) | Recall based | Paper-based contact-tracing systems (data manually entered onto a single computer) |
| Aiello et al (2016; iEpi substudy) | Substudy (descriptive observational study) within a cluster randomised controlled trial | iEpi substudy within a university-based trial; participants given smartphones that were used to detect other study devices and nearby Bluetooth-enabled devices to map proximity to contacts | USA | Influenza | Students aged ≥18 years | 103 (iEpi substudy) | Automated contact detection only | Bluetooth | Smartphone app (standalone) | Proximity based | None |
| Al Qathrady et al (2016) | Observational and modelling (simulation) study | Simulation of disease spread and contact tracing by use of a contact network recreated from WiFi traces; explored different approaches to prioritising investigation or follow-up of contacts at risk | Not specified | Hospital-based outbreaks | University faculty and students (contact data based on WiFi use on a university campus across six buildings) | WiFi trace data from 34 225 users of six university buildings | Automated contact detection only | WiFi network traces | Mobile devices (further detail not specified) | Proximity based | None |
| Voirin et al (2015) | Proof of concept observational study | Pilot study that combined micro-contact data from wearable proximity sensors and virological data to investigate influenza transmission within an elderly care unit of a hospital | France | Influenza A and B | Median ages in years were 24 (doctors), 30 (nurses), and 89 (patients); proportions of women were 67% (doctors), 78% (nurses), and 73% (patients) | Total 84 (32 nurses, 15 doctors, and 37 patients) | Automated contact detection only | Radio frequency identification | Radio frequency identification proximity sensors | Proximity based | None |
GPS=Global Positioning System. N/A=not applicable.
Summary of outcomes and other key findings
| Number or proportion of contacts identified (observed or required for outbreak control) | Number or proportion of subsequently diagnosed cases identified | Impact on R0 (or other indicators of outbreak control) | Uptake | Resource requirements or cost-effectiveness | Other ethical issues | Lessons learnt from implementation of the intervention | |
|---|---|---|---|---|---|---|---|
| Bulchandani et al (2020) | Not reported | Not reported | Estimated that approximately 90% app ownership required for epidemic control if 50% of transmission is asymptomatic but no presymptomatic transmission; multiple input parameter values assessed | Not reported | Not reported | Not reported | Not reported |
| Ferretti et al (2020) | Multiple values; related to delay to intervention (eg, if 60% of cases are isolated, >65% of contacts need to be identified and quarantined to bring R0<1) | Not reported | High uptake and compliance, and decreased delays to notification (presented in a 1 day increments, from 3 days down to no delay) and quarantine improve the likelihood of reaching R0<1 | Not reported | Not reported | Propose that such a scheme should fulfil eight requirements in order to be ethical | N/A (modelling study) |
| Hinch et al (2020) | Baseline scenario of 3 day doubling time and 80% app uptake among smartphone owners means approximately 10–15 million people would be quarantined (at any given time, with variation over time); in addition to the population over 70 years who were assumed to practise shielding | Not reported | All app configurations showed a substantial reduction in new cases and hospital and intensive care unit admissions, and a substantial number of lives saved over a 150 day period from the start of a 35 day lockdown, increasing incrementally as uptake increases from 0% to 80% of smartphone owners; direct contact tracing (only first-order contacts quarantined) suppressed the epidemic only under optimistic epidemic growth assumptions (3·5 day doubling time, 5·0 day generation time); recursive tracing (with first-order contacts’ household members also quarantined) reached epidemic control under pessimistic assumptions but leads to only a 50% reduction in numbers quarantined compared with full lockdown; the authors estimate that test-based quarantine release would require approximately 100 000–200 000 tests per day | 80% usage to reach suppression under scenarios 3 and 5 with epidemic doubling time of 3·5 days; lower uptake rates reduced incidence | Not reported | Not reported | N/A (modelling study) |
| Kim and Paul (2020) | Not reported | Not reported | Under a range of assumptions, the percentage of the population needed to be enrolled in automated contact tracing for outbreak control (Re<1) was estimated (eg, 40–60% uptake required for Re<1, assuming a 30% mean transmission probability per contact event, if 75–95% actively confirm when they get infected; | Not reported | Not reported | Not reported | N/A (modelling study) |
| Kucharski et al (2020) | Median number of (physical and conversational) contacts successfully traced and quarantined (assuming 90% of those traced are quarantined) per case (modelled results) was 4 (mean 14) via automated contact tracing, 21 (mean 32) via manual contact tracing (acquaintances only), 28 (mean 39) with all contacts traced manually | Not reported | App-based contact tracing would require a high level of coverage to ensure Re<1; smaller relative reduction in Re than manual contact tracing for either all contacts or acquaintances only, varying with proportion symptomatic and relative role of asymptomatic transmission; automated tracing alone was estimated to reduce Re by 44%, whereas manual tracing of all contacts reduced Re by 61% (assuming transmission occurs only through physical or conversational contacts that can be recalled) | Estimated 53% uptake (as an input parameter) across UK population in baseline optimistic scenario, on the basis of 75% uptake × 71% smartphone ownership | Not reported | Not reported | N/A (modelling study) |
| Xia and Lee (2020) | Not specified; assumes 100% identification of contacts | Not reported | Assessment of the minimum uptake required to reach R0<1; estimated at 95–100% (if only 2–10% of cases are detected because of a large proportion being mild or asymptomatic) | Not reported | Not reported | Not reported | N/A (modelling study) |
| Yasaka et al (2020) | Not specified | Not reported | No summary estimates presented; based on results presented graphically, an estimated 65–90% of the population would be infected at the epidemic curve peak with 0% uptake of the automated contact-tracing app, and 15–50% infected with an adoption rate of 75% | Speculated that absence of a user registration process will improve adoption rates | Suggested that because of decreased data sharing, overheads for government agencies would be minimal | Not reported | N/A (modelling study) |
| Danquah et al (2019) | Mean 36 per case with app-based system; 16 per case with paper-based system | 69% (384 of 556) of registered contacts for 16 confirmed cases were documented as visited under the app-based system compared with 39% (157 of 407) of contacts for nine confirmed cases for whom paper forms were returned under the paper-based system (out of 25 confirmed cases in this system; paper forms were not returned for the other 16 cases) | Not reported | Training contact tracers took 3 days; contact tracers reported that the app-based system was faster and more accurate; reduced travel time (by 5–6 h per coordinator per day); battery charging and technical support were both important | Not reported | Technical issues included poor network coverage, battery life, and quality of phones; further training on syncing data between phone and server needed; compensation and planning for phone charging, including travel to charging booths; and more refresher training for contact tracing and monitoring | |
| Li et al (2017) | Not reported | Reduced delay to intervention by the hospital infection control team by 0·5–4·0 h | Not reported | Not reported | 230–476 h of contact tracing time saved per annum (baseline unclear) | Not reported | Authors stated that implementation of system took substantial time and effort from users; and workflow changes needed when specific data analytics were not available within the software |
| Schafer et al (2016) | More than 50 000 contacts recorded on system for >100 000 cases by end of 2015 | Not reported | Not reported | Widely used by contact tracers in these settings, percentage not specified | Resources required included technical expertise for training provision, data management staff who were technically skilled and trained (the authors noted that these skills were often scarce locally), and time and expertise required for set-up and maintenance of the database and network; network connectivity and electricity supply were also important resources, and recurrent outages made data entry and transmission challenging | Not reported | Successful use of app required organised flow of contact information between data managers and contact tracers, and a concerted effort to use the app (often not the case); Epi Info Viral Hemorrhagic Fever app designed to require minimal IT support but multiuser data entry expanded complexity and support requirements (minimal, if any, IT support was available); accommodating many countries’ needs within one software was challenging, particularly as it was not possible to customise the software for each country |
| Sacks et al (2015) | 210 contact tracers monitoring 9162 contacts | Not reported | Not reported | 210 of 366 who were trained on CommCare actively used it | Total time to establish programme was 10–13 weeks (training contact tracers took 2–3 days); smartphones, SIM cards, 500 MB data per month, and solar phone chargers donated for staff use; need for technical support | Focused on the ethical issues around adopting new technology during complex emergency; authors argue this disruption might be required, but that feasibility and risks should be carefully considered and, where implemented, accompanied with close managerial oversight | Availability and cost of expertise for specific software used; recruitment of local technology expert youth volunteers helped to accelerate phone configuration; actual use of data by government staff members to inform action was low; clearer initial standards (for contact-tracing protocols and metrics) could have accelerated the design process |
| Tom-Aba et al (2015) | Not reported | Not reported | Reduced delay to evacuation of symptomatic contacts from their homes to an isolation facility from 3–6 h to 1 h, and the proportion of contacts followed up increased from a variable baseline of between 90% and 99% (before the partly automated system was introduced) to consistently 100% afterwards, with associated benefits for outbreak control | Not reported | Costs of android phones, tablets, laptops, data plans, and high-speed internet; time costs of trained personnel | Not reported | Not reported |
| Aiello et al (2016) | 453 281 total Bluetooth contacts between iEpi substudy smartphones only (62·5 contacts per phone per day) and 1 591 741 with other devices (219·4 contacts per phone per day) over 78 days | N/A | Not reported | Not reported | Availability and training of a large study staff (size not specified); system required mapping, debugging, data cleaning, and verification | Not reported | 95% (281 of 295) of participants who completed the exit survey reported joining the study because of the cash incentive |
| Al Qathrady et al (2016) | 353 458 encounter records from 34 225 users in 1 week | Not reported | All contacts within the simulated institutional outbreak could be traced on the basis of one infectious case having been identified (for an infection with a latent period of 1 day and infectious period of 2 days); further detail not provided | Not reported | Not reported | Not reported | Accuracy of the contact-tracing system in some buildings decreased with coverage, but increased in others, because of differences in the encounter patterns within each building, and the source node chosen |
| Voirin et al (2015) | 18 765 contact events recorded among 84 individuals over 11 days (cumulative duration 251 h) | N/A | Not reported | Not reported | Not reported | Not reported | Most contacts between nurses or between nurses and a patient; influenza transmission is difficult to predict from contact data alone |
Additional details can be found in the appendix (appendix pp 8–10). N/A=not applicable. R0=basic reproduction number. Re=effective reproduction number.