Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Empfangszähler für Kontaktids auf der Oberfläche der Anwendung #280

Open
SchwertAs opened this issue Nov 27, 2020 · 18 comments
Open

Empfangszähler für Kontaktids auf der Oberfläche der Anwendung #280

SchwertAs opened this issue Nov 27, 2020 · 18 comments
Assignees
Labels
feature request A new feature proposal for the app mirrored-to-jira This item is also tracked internally in JIRA

Comments

@SchwertAs
Copy link

SchwertAs commented Nov 27, 2020

Feature description

Display dayly and weekly Contact-Amount of user on base of received IDs (infected or not).

I would like to have a broadly visible counter of contact Ids per day, and summed up for a week. The user can use this as personal feedback of his/her own behaviour in having various and extended contacts, which all increase the risk of infection nevertheless the contacts are infected or not. So every scan for nearby Ids should count and sum up the received Ids for a day and for the currend and the last week. This counter i call it Contact-Amount would be a measure for the amount of contacts a person has had.

So further contact regulations could demand a dayly or weekly border for this Contact-Amount for any person, depending on their professional circumstances. This could be a new way to get infections controllable and to supervise contact behaviour of the citizens.

Pseudocode:
Während eines Abfragescans:
__Wenn neuer Tag:
____setzte Tageszähler auf 0
__Wenn neue Woche:
____übertrage Wochenzähler auf Vorwochenzähler
____setze Wochenzähler auf 0
__Für jede empfangene Id (neu oder bekannt ist egal)
____erhöhe aktuellen Wochenzähler
____erhöhe aktuellen Tageszähler
__Zeige neuen Tageszähler an
__Zeige neuen Wochenzähler an
__Zeige Vorwochenzähler an

Problem and motivation

Mit dieser Zählweise bildet man eine generelle RIsikozahl, die sowohl Kontaktdauer, als auch Anzahl der Kontakte beinhaltet. Diese kann für den User ein wertvolles Feedback sein, wie hoch sein persönliches Risiko aufgrund seines eigenen Verhaltens bereits gestiegen ist. Durch Vorweisen einer entsprechend niedrigen Contact-Amount Zahl gegenüber Anderen ließe sich vorbildliches Verhalten und damit Vertrauen in verantwortliches Verhalten aufbauen.

Is this something you're interested in working on

Yes


Internal Tracking ID: EXPOSUREAPP-4056

@SchwertAs SchwertAs added the feature request A new feature proposal for the app label Nov 27, 2020
@Ein-Tim
Copy link
Contributor

Ein-Tim commented Nov 27, 2020

Just a small remark:
The number of non positive contacts is not revealed by the ENF (the underlying API from Apple/Google).
Also CWA does never touch RPIs or similar things, this is all done by the ENF...
But since this is the Wishlist this Issue should definitely stay open, since I also think this is a good request 👍


Related Issue: #205 & #124

@SchwertAs This is also nearly a duplicate of #5, so maybe also take a look there 👍

@dl1chb
Copy link

dl1chb commented Nov 27, 2020

For me this counter could also act as a technical feedback: I do not know if everyone here has the app when going to the supermarked. I also cannot proof everything here is somehow working. So for me it would have the advantage to see, okay, it sees others using the app or it does not. Or even nobody else is using the app. Then I can see how much I can trust this "low risk" statement. Or maybe there is another way to do this (would be another feature request then). I honestly don't believe I never came in contact with no infected person during these days...

I am against having this as a proof of good behaviour. Sometimes I need food and need to go to the supermarked. Also there are people who cannot avoid contacts during their work (think for example of those who are working in supermarkets). Therefor it should need some passphrase to see this number.

[EDIT]: I got a comment mail (but don't see it since over an hour here) that live could lead to some other problem: you see who is using the app or who doesn't. This also would be bad. So a free-to-click-button to activate this feature for testing purposes or another way should be considered. So if you meet people at work and know already they are using the app, this can help. And of course I would switch it on when going to a supermarket, for example....

@heinezen
Copy link
Member

Related: #262

@heinezen heinezen added the mirrored-to-jira This item is also tracked internally in JIRA label Nov 29, 2020
@heinezen
Copy link
Member

Hello @SchwertAs ,

Thank you for the request. We have submitted your proposal to our internal Jira system (ticket ID: EXPOSUREAPP-4056) and forwarded it to the development team. The developers and the RKI will now decide if this feature can be implemented and how it would work with the other related requests. We will notify everyone on Github when we have something new to report about the status of the request.

Best Regards,
CH


Corona-Warn-App Open Source Team

@SchwertAs
Copy link
Author

SchwertAs commented Nov 30, 2020 via email

@SchwertAs
Copy link
Author

SchwertAs commented Nov 30, 2020 via email

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Nov 30, 2020

You did misunderstand my suggestion. I wanted to sum up ALL Contacts not only the positive ones.

Yes I understood you @SchwertAs, but inside the ENF this is not possible because the Corona-Warn App only knows about the positive encounters, how many (or if you had) non-positive encounters is only known by the ENF, which does not tell this number to CWA.

@SchwertAs
Copy link
Author

SchwertAs commented Nov 30, 2020 via email

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Nov 30, 2020

I f ENF does not tell maybe there is a way to ask it?

No, it's not that easy. The ENF (Exposure Notification Framework) is developed by Apple & Google and also maintained by them.
The German Corona-Warn App is talking to it to get the information you see in the App.
There is some information which is told to CWA by ENF, but is not shown to the user (for privacy reasons).
How many contacts (positive+negative encounters) the phone recorded is not even told to CWA by ENF.
So for your proposal Apple/Google would have to update the ENF.

But since this is the Wishlist, this can stay open, I just wanted to clarify that this is at the moment not possible to introduce.

@sapcoder123 sapcoder123 assigned maugst and unassigned JoachimFritsch Dec 18, 2020
@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 16, 2021

The next versions will contain some statistics (corona-warn-app/cwa-app-ios#1807 & corona-warn-app/cwa-app-android#2043).

@di-sc
Copy link

di-sc commented Apr 11, 2021

Mit dieser Zählweise bildet man eine generelle RIsikozahl, die sowohl Kontaktdauer, als auch Anzahl der Kontakte beinhaltet. Diese kann für den User ein wertvolles Feedback sein, wie hoch sein persönliches Risiko aufgrund seines eigenen Verhaltens bereits gestiegen ist. Durch Vorweisen einer entsprechend niedrigen Contact-Amount Zahl gegenüber Anderen ließe sich vorbildliches Verhalten und damit Vertrauen in verantwortliches Verhalten aufbauen.

If at some time Apple and/or Google will extend the ENF to provide the necessary data I would suggest to think about a real risk calculation. Because of the infection rate everyone on his/her own has a risk to be infected when meeting a person, independent of an existing positive test (sounds strange but unfortunately it's a fact). Using the current 7 day infection rate (best would be the local infection rate of the county) provided by the RKI, the infection rate seven days ago, the current R value, and the R value 7 days ago and the number of higher risk contacts of the CWA a probability value can be calculated to be infected (has to be proved and optimized by experts, epidemiologists and statisticians, for sure).

E.g.: (IR7 * R7 + IR7_7 * R7_7) * number_of_high_risk_contacts_over_last_14_days

This probability value can then be shown as a slider on the main page of the CWA or, what I would prefer shown as a yellow notification, indicating a high activity risk, when it is above a to be defined threshhold.
The advantage of this method is the dependence on the infection rate. The allowed Activity can be higher if the infection rate is low and Activity has to be reduced if the infection rate is high. This is what we want to be able to control the pandemic!
The "yellow notification" should then be accompanied with the hint to reduce contacts, not necessarily to make a test.

(@Vineet-Bhola: I would then change your notification color of issue #431 2nd Level Contact tracing (#24) to orange.)

@ndegendogo
Copy link

@di-sc nice idea your formula.

The allowed Activity can be higher if the infection rate is low

Of course this reasoning is true. However, measuring the contact rate through cwa could give users a false sense of safety, as long as the adoption rate of cwa is not so high.
Currently the ratio of people sharing their keys to new infections is only about 1:5 or 1:6. So at the moment you can safely assume that several (or even most?) of your contacts will not be detectable with this method.

@di-sc
Copy link

di-sc commented Apr 11, 2021

@ndegendogo You mean some users could misuse the tool to check how far they can go with their activity until it shows the yellow notifiction? Good point, absolutely!

Some thoughts:

  • The adoption rate could compensated by including it into the calculation or the threshold.
  • The feature (as all features that make the app more responsive to the user) may make it more attractive for the user to install the app and increase the adoption rate.
  • If the CWA green status would be made required to attend to events it would be not so attractive to reach the limit of a yellow status. As a side effect this would also increase the adoption rate, I think.

@ndegendogo
Copy link

@di-sc yes, you are right.
No matter what feature, there will always be silly people who misunderstand the purpose and misuse it. Hopefully only very few such silly people. And I think the majority indeed behaves prudent and will understand a high contact counter as a warning to re-think their behaviour and change it if possible.

@di-sc
Copy link

di-sc commented Apr 14, 2021

Until the ENF will support providing such contact statistic data it might be considered to use the Event Registration feature as a start. As I understand Event Registration will be released shortly and does not have these ENF restrictions!?

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 14, 2021

@di-sc

Could you clarify what you would like to show from the event registration?
Since it's part of the Corona-Warn-App, this feature is also restricted to the restrictions mentioned in https://developer.apple.com/contact/request/download/Exposure_Notification_Addendum.pdf.

If it would break the rules, the update would risk to get blocked form the Stores, see https://www.bbc.com/news/technology-56713017

@di-sc
Copy link

di-sc commented Apr 14, 2021

@Ein-Tim It was only an idea. I never thought that having anonymous statistic data about my contacts would be a problem. But okay then that's not the way to go.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 14, 2021

@di-sc I think nothing speaks about anonymous statistic data about your contacts, but not sure to what extend the even registration feature could help here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request A new feature proposal for the app mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests

8 participants