-
Notifications
You must be signed in to change notification settings - Fork 14
success statistics for CWA and bluetooth calibration #139
Comments
Dear Ulenrich, thank you very much for your proposal. To give the community a space for discussing new feature ideas or enhancements that might not be taken up immediately by the development teams, we created the cwa-wishlist repository. This idea is one of these feature ideas or enhancements. Consequently, we will move this issue to this repository and allow the community and you to further refine it, discuss pros and cons, and evaluate alternatives. The issue will not be closed in this repository to ensure long-term visibility. All issues in the cwa-wishlist repository will be discussed with our contracting entities. They will decide whether they will be implemented or pursued further. As soon as we have any updates, we will let you know about the details. Best regards, RV Corona-Warn-App Open Source Team |
The next versions will contain some statistics (corona-warn-app/cwa-app-android#2043 & corona-warn-app/cwa-app-ios#1807) |
Some statistics are now (with the release of version 1.11) available in the App: https://www.coronawarn.app/en/blog/2021-01-28-corona-warn-app-version-1-11 |
What is success of CWA:
A success definitely is a positively tested person motivated by the warning status of CWA.
But imagine these extremes:
In the first case the bluetooth calibration was far too sensible. Or the detection of dangerous contacts has missed many of them. Therefore statistics are key!
Simple solution:
Every medical assistent taking a Coronavirus test should ask the patient if he uses CWA and about the warning status. This little questionaire and the result of the test must be transmitted to RKI and the success of the app should be public available in statistics.
Because this statistic is important for public discussion and review of CWA.
Internal Tracking ID: EXPOSUREAPP-5018 (statistics overview)
Internal Tracking ID: EXPOSUREAPP-2033
The text was updated successfully, but these errors were encountered: