| Literature DB >> 33724920 |
Jan-Patrick Weiß1, Moritz Esdar1, Ursula Hübner1.
Abstract
BACKGROUND: Contact tracing apps are potentially useful tools for supporting national COVID-19 containment strategies. Various national apps with different technical design features have been commissioned and issued by governments worldwide.Entities:
Keywords: COVID-19; app; assessment; contact tracing; design; feature; framework; monitoring; privacy; protocol; review; surveillance; usage
Mesh:
Year: 2021 PMID: 33724920 PMCID: PMC8006898 DOI: 10.2196/27232
Source DB: PubMed Journal: JMIR Mhealth Uhealth ISSN: 2291-5222 Impact factor: 4.773
Figure 1Sequence of methodological steps.
Background information provided by the issuers of the apps.
| App | Country | Open-source repository | Information websites |
| Corona Warn App | Germany | Yes | Yes |
| TousAntiCovid | France | Yes | Yes |
| Immuni | Italy | Yes | Yes |
| Radar COVID | Spain | Yes | Yes |
| Koronavilkku | Finland | Yes | Yes |
| NHSa COVID-19 | England and Wales | Yes | Yes |
| TraceTogether | Singapore | Yes | Yes |
| Self-Diagnosis app | South Korea | No | No |
| Self-Quarantine app | South Korea | No | No |
| Coronavirus-SUSb | Brazil | No | No |
| Various integrated tracing functions in apps (eg, WeChat) | China | No | No |
aNHS: National Health Service.
bSUS: Sistema Único de Saúde.
Technical information of the apps.
| App | Country | Protocol | Tracing technology | GAENa | Interoperable with apps from other countries |
| Corona Warn App | Germany | DP-3Tb and TCNc | Bluetooth | Yes | Yes |
| TousAntiCovid | France | ROBERTd | Bluetooth | No | No |
| Immuni | Italy | DP-3T | Bluetooth | Yes | Yes |
| Radar COVID | Spain | DP-3T | Bluetooth | Yes | Yes |
| Koronavilkku | Finland | —e | Bluetooth | Yes | Yes |
| NHSf COVID-19 | England and Wales | — | Bluetooth | Yes | Yes |
| TraceTogether | Singapore | OpenTrace | Bluetooth | No | No |
| Self-Diagnosis app | South Korea | — | Reported data | No | No |
| Self-Quarantine app | South Korea | — | Reported data and GPS | No | No |
| Coronavirus-SUSg | Brazil | — | Bluetooth | Yes | No |
| Various integrated tracing functions in apps (eg, WeChat) | China | — | Quick response code, sensor data, and metadata | No | No |
aGAEN: Google/Apple Exposure Notification System.
bDP-3T: Decentralized Privacy-Preserving Proximity Tracing.
cTCN: Temporary Contact Numbers.
dROBERT: Robust and Privacy-Preserving Proximity Tracing.
eNot available.
fNHS: National Health Service.
gSUS: Sistema Único de Saúde.
Privacy protection.
| App | Country | Contact tracing approach | Report processing approach | User can opt out | Anonymity (no user registration) |
| Corona Warn App | Germany | Decentralized | Decentralized | Yes | Yes |
| TousAntiCovid | France | Decentralized | Centralized | Yes | Yes |
| Immuni | Italy | Decentralized | Decentralized | Yes | Yes |
| Radar COVID | Spain | Decentralized | Decentralized | Yes | —a |
| Koronavilkku | Finland | Decentralized | Decentralized | Yes | Yes |
| NHSb COVID-19 | England and Wales | Decentralized | Decentralized (tracing)/centralized (check-ins) | Yes | Yes |
| TraceTogether | Singapore | Decentralized | Centralized | Yes | Phone number |
| Self-Diagnosis app | South Korea | — | Centralized | No | Name, address, and phone number |
| Self-Quarantine app | South Korea | — | Centralized | No | Name, address, and phone number |
| Coronavirus-SUSc | Brazil | Decentralized | Decentralized | Yes | Yes |
| Various integrated tracing functions in apps (eg, WeChat) | China | Centralized | Centralized | No | No |
aNot available.
bNHS: National Health Service.
cSUS: Sistema Único de Saúde.
Availability and use.
| App | Country | Release date | Downloads, n (% of population) | Date reported | Source type |
| Corona Warn App | Germany | June 16, 2020 | 25.4 million (30.6%) | February 11, 2021 | Official [ |
| TousAntiCovid | France | June 2, 2020 | 11 million (16.4%) | December 8, 2020 | Official [ |
| Immuni | Italy | June 15, 2020 | 10.3 million (17.06%) | February 22, 2021 | Official [ |
| Radar COVID | Spain | August 2020 | 7.03 million (17%) | February 14, 2021 | Official [ |
| Koronavilkku | Finland | August 31, 2020 | >2.5 million (45.3%) | November 5, 2021 | Official [ |
| NHSa COVID-19 | England and Wales | September 24, 2020 | 21.8 million (36.7%) | February 10, 2021 | Official [ |
| TraceTogether | Singapore | March 20, 2020 | 4.2 million (73.7%) | February 23, 2021 | Official [ |
| Self-Diagnosis app | South Korea | March 2020 | >500,000 (0.96%) | February 23, 2021 | Google Play Store [ |
| Self-Quarantine app | South Korea | March 2020 | >500,000 (0.96%) | February 23, 2021 | Google Play Store [ |
| Coronavirus-SUSb | Brazil | August 1, 2020 | 10 million (4.77%) | December 8, 2020 | Official [ |
| Various integrated tracing functions in apps (eg, WeChat) | China | February 2020 | —c | — | — |
aNHS: National Health Service.
bSUS: Sistema Único de Saúde.
cNot available.
Proposed item set for a monitoring framework.
| Category, subcategory, and item number | Item | |||
|
| ||||
|
|
| |||
|
|
| Q1.1 | What is the name of the app? | |
|
|
| |||
|
|
| Q1.2 | Is there a publicly accessible repository of the source code? | |
|
|
| Q1.3 | Is the published source code up to date? | |
|
|
| |||
|
|
| Q1.4 | Is there some form of material (eg, website, guideline, or Frequently Asked Questions page) for informing the public about the app? | |
|
|
| |||
|
|
| Q1.5 | Which institutions worked together to develop, host, and maintain the app? | |
|
| ||||
|
|
| |||
|
|
| Q2.1 | What is the main mode of action for warning app users? | |
|
|
| |||
|
|
| Q2.2 | What other purposes are the data used for? | |
|
| ||||
|
|
| |||
|
|
| Q3.1 | Which tracing protocols (eg, DP-3Ta, TCNb, ROBERTc, and BlueTrace) are implemented in the app? | |
|
|
| |||
|
|
| Q3.2 | Which tracing technology (eg, Bluetooth, GPS, and barcodes) is used by the app? | |
|
|
| |||
|
|
| Q3.3 | Is the Google/Apple Exposure Notification System used? | |
|
|
| |||
|
|
| Q3.4 | Is the app actively interoperable with apps from other countries? | |
|
| ||||
|
|
| |||
|
|
| Q4.1 | Is the process of contact tracing (eg, tracking each contact event) centralized or decentralized? Provide a short description of the workflow. | |
|
|
| Q4.2 | Is the report processing approach (eg, matching contact events and informing the user) centralized or decentralized? Provide a short description of the workflow. | |
|
|
| Q4.3 | Are app data processed as mandated by data protection regulations? | |
|
|
| Q4.4 | Is the data automatically destroyed after a fixed period of time? | |
|
|
| Q4.5 | Can the user opt out? | |
|
|
| |||
|
|
| Q4.6 | Does the user have to register any information (eg, mobile phone number, name, address, or date of birth)? | |
|
| ||||
|
|
| |||
|
|
| Q5.1 | On which date could the app be downloaded by the public? | |
|
|
| |||
|
|
| Q5.2 | Are there officially reported download numbers? | |
aDP-3T: Decentralized Privacy-Preserving Proximity Tracing.
bTCN: Temporary Contact Numbers.
cROBERT: Robust and Privacy-Preserving Proximity Tracing.