-
Notifications
You must be signed in to change notification settings - Fork 224
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into new_device
- Loading branch information
Showing
338 changed files
with
679 additions
and
98 deletions.
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
page-title: "Project Team further improves Corona-Warn-App's risk calculation in response to current coronavirus situation" | ||
page-description: "Project Team further improves Corona-Warn-App's risk calculation in response to current coronavirus situation" | ||
page-name: corona-warn-app-risk-calculation-further-improved | ||
page-name_de: corona-warn-app-risk-calculation-further-improved | ||
author: Hanna Heine | ||
layout: blog | ||
--- | ||
|
||
|
||
The Corona-Warn-App's project team continuously improves the app's performance with regard to the coronavirus situation in Germany. In response to virus mutations, the team members from the Robert Koch-Institut, Deutsche Telekom, SAP and the Fraunhofer Institute for Integrated Circuits (IIS) have therefore further improved the risk calculation and reduced the **duration of a critical encounter** from 13 minutes to 9 minutes. | ||
|
||
|
||
<!-- overview --> | ||
|
||
|
||
For app users, this means: Previously, an encounter between two people had to last at least 13 minutes in order to be considered for an **encounter with an increased risk (red tile)**. Now, the app considers encounters of at least 9 minutes. Thus, encounters that represent an actual relevant contact with COVID-19 infected persons can be detected even more accurately and represented accordingly in the app as a warning about an encounter with increased risk. This **increases the number of warnings** by approximately 16 percent. The parameters are adjusted on the server. Users don't have to do anything. | ||
|
||
Most recently, the project team adjusted the risk calculation at the [end of March](https://www.coronawarn.app/en/blog/2021-03-19-risk-calculation-improvement/) in response to a virus mutation. It continues to work on improving the measurements and the resulting configuration parameters. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
page-title: "Das Projektteam verbessert die Risikoberechnung der Corona-Warn-App in Reaktion auf die Infektionslage" | ||
page-description: "Das Projektteam verbessert die Risikoberechnung der Corona-Warn-App in Reaktion auf die Infektionslage" | ||
page-name: corona-warn-app-risk-calculation-further-improved | ||
page-name_de: corona-warn-app-risk-calculation-further-improved | ||
author: Hanna Heine | ||
layout: blog | ||
--- | ||
|
||
|
||
Mit Blick auf die Corona-Lage in Deutschland verfolgt das Projektteam der Corona-Warn-App kontinuierlich das Ziel, die Leistung der App zu optimieren. In diesem Rahmen haben die Projektbeteiligten aus Robert Koch-Institut, Deutsche Telekom, SAP und Fraunhofer-Institut für Integrierte Schaltungen (IIS) die Risikoberechnung weiter verbessert und die **Dauer einer kritischen Begegnung** von 13 Minuten auf 9 Minuten herabgesetzt. Sie reagieren damit auf die veränderte Infektionslage aufgrund der Virus-Mutationen. | ||
|
||
<!-- overview --> | ||
|
||
Für Nutzer\*innen der Corona-Warn-App bedeutet das: Bisher musste eine Begegnung zwischen zwei Personen mindestens 13 Minuten dauern, um von der App für eine **Begegnung mit erhöhtem Risiko (rote Kachel)** berücksichtigt zu werden. Nun sind bereits Begegnungen von mindestens 9 Minuten ausreichend. So können Begegnungen, die einen tatsächlich relevanten Kontakt mit COVID-19 infizierten Personen darstellen, noch genauer erkannt und in der App entsprechend als Warnung über eine **Begegnung mit erhöhtem Risiko** darstellt werden. Die **Anzahl der Risikowarnungen** erhöht sich damit um circa 16 Prozent. Die Anpassung der Parameter erfolgt serverseitig, sodass Nutzer*innen nichts weiter tun müssen. | ||
|
||
Zuletzt hat das Projektteam die Risikoberechnung [Ende März](https://www.coronawarn.app/de/blog/2021-03-19-risk-calculation-improvement/) angepasst, um mutierte Virusvarianten zu berücksichtigen. Die Projektbeteiligten arbeiten auch weiterhin an einer Verbesserung der Messungen und der daraus resultierenden Konfigurationsparameter. | ||
|
||
|
||
|
||
|
||
|
||
|
10 changes: 6 additions & 4 deletions
10
blog/2021-04-01-facts-and-figures/index.md → blog/2021-04-16-facts-and-figures/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 changes: 7 additions & 5 deletions
12
.../2021-04-01-facts-and-figures/index_de.md → .../2021-04-16-facts-and-figures/index_de.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
--- | ||
page-title: "Project team releases Corona-Warn-App 2.0 with event registration" | ||
page-description: "Project team releases Corona-Warn-App 2.0 with event registration" | ||
page-name: corona-warn-app-version-2-0 | ||
page-name_de: corona-warn-app-version-2-0 | ||
author: Hanna Heine | ||
layout: blog | ||
--- | ||
|
||
Deutsche Telekom and SAP’s project team have released **version 2.0 of the Corona-Warn-App**, which will be available to users within the next 48 hours. The update adds the **event registration feature** to the app, allowing users to check in via a QR code at retail stores, events or private meetings. | ||
|
||
<!-- overview --> | ||
|
||
With the event registration, organizers and retailers can use the Corona-Warn-App to **create a QR code** in which all necessary data about the event is encoded. This includes, for example, the event location and type, the date, and, if applicable, the beginning and ending. Visitors and guests can then **check in for the event by scanning the QR code**. The check-in is stored locally on their smartphones and will be deleted automatically after two weeks. | ||
|
||
<br></br> | ||
<center> <img src="./homescreen.png" title="Homescreen CWA" style="align: center"> <img src="./qr-coden-en.png" title="QR Code" style="align: center"> <img src="./check-in(4)-en.png" title="Persönliche Check-Ins" style="align: center"></center> | ||
<br></br> | ||
|
||
Visitors who later test positive for COVID-19 can **share their check-ins** along with the **diagnostic keys** via the app and thus upload them to the Corona-Warn-App’s server. The server then publishes the corresponding check-ins as alerts. These alerts are downloaded regularly to the users smartphones where they are automatically matched with the local check-ins. Other guests who were at the same event or location then receive a red or green warning. | ||
|
||
This allows potential clusters to be identified and infection chains to be broken efficiently. | ||
|
||
|
||
### Users can receive a red or green warning | ||
|
||
Whether users receive a green or red warning depends on whether their stay overlaps with that of an infected person. If they were on site for **less than 10 minutes**, they will receive a warning about an exposure with low risk on one day (green tile). If their stay overlapped with the person who later tested positive for COVID-19 by **10 minutes or more**, users will receive a warning about an exposure with an increased risk (red tile). | ||
|
||
In the contact diary, users can see whether a low-risk or high-risk exposure refers to an event-based warning. | ||
|
||
<br></br> | ||
<center> <img src="./increased-risk-contact-journal.png" title="Increased risk in contact journal" style="align: center"></center> | ||
<br></br> | ||
|
||
|
||
### How to check in to and out from an event or location | ||
|
||
In version 2.0 of the Corona-Warn-App, users will find a new tab named Check-In at the bottom of the app’s home screen. | ||
|
||
|
||
This takes them to their check-ins, where they can find an overview of existing entries. There, they can also check in to or out from an event or location. To check in, users can **scan the corresponding QR code**. On iOS, this works via the camera; on Android devices, it depends on the respective manufacturer whether the smartphone camera can read QR codes. All check-ins can be automatically transferred to the contact diary. Users can also check themselves out in this area by clicking on Check out now under the event. | ||
|
||
Alternatively, event organizers and operators can also set an automatic check-out after a predefined time. The app notifies users that they’ve been checked out. Users can manually adjust the time afterwards in their Check In area. | ||
|
||
|
||
### How to create a QR code | ||
|
||
Event organizers and retailers can use the new section on the Corona-Warn-App’s home screen to create a QR code that their visitors or guests can scan. | ||
|
||
To do this, they simply choose Create QR Code. Then, they can enter information about the event: After selecting the category (e.g., retail or private party), they can specify an event description, the location, and start and end dates. The Corona-Warn-App uses this information to create a QR code that can be displayed on a smartphone or printed out and posted on site. | ||
|
||
|
||
### Two different event types | ||
|
||
There are two different scenarios in which organizers, retailers, and private individuals can use the new event registration feature. | ||
|
||
**Scenario 1: Ad-hoc event** | ||
|
||
An ad-hoc event can be created at short notice and has a defined start and end time. This includes, for example, private meetings, celebrations or smaller events. | ||
|
||
**Scenario 2: Permanent location** | ||
|
||
In contrast to ad-hoc events, so-called permanent locations do not have a fixed start and end time. In this case, a QR code is typically made available in a room for a longer period of time. Guests re-scan this QR code each time they visit. Examples of a permanent location are hairdressers or restaurants. | ||
|
||
|
||
**Please note: attendees or guests who didn't install the Corona-Warn-App** | ||
|
||
iOS users who scan a QR code but didn't install the Corona-Warn-App will automatically be directed to Apple's App Store. There, they can download the app and then check in. Android users are directed to a website that takes them to the Google Play Store, where they can also download the Corona-Warn-App. | ||
|
||
|
Oops, something went wrong.