Cwa-wishlist: Show date of Low-Risk encounters

[Ein-Tim]

Current Implementation

Currently, when you had a Low-Risk encounter you just see that you had one (and that the app says it is Low-Risk) and no more information about the encounter.

Suggested Enhancement

Please inlcude the information when the encounter happend ("dd.mm.yy"), how it is done by High-Risk encounters.

Expected Benefits

The user would know what he/she has done on this day and so know if there is anything special to do. (had I many or just a few contacts on that day/were I on a train this day (where the distance measurement is not that good), etc.)

Additional Inforamtion

I know that the RKI denied to show more information about Low-Risk encounters, but could you please bring up exactly this suggestion and let us know what they are thinking?

---

Related Issues

• https://github.com/corona-warn-app/cwa-backlog/issues/23
• https://github.com/corona-warn-app/cwa-wishlist/issues/100

---

Internal Tracking ID: EXPOSUREAPP-2836

[GPclips]

Hello @Ein-Tim,

thanks for sharing your idea. I have created a JIRA ticket and assigned it to @hermesmar .

Thanks,
LMM

Corona-Warn-App Open Source Team

[mweisbach]

Pls. also note issue >Display of "Tage seit letzter Risiko-Begegnung" is irritating< at https://github.com/corona-warn-app/cwa-documentation/issues/433.

[ndegendogo]

Another reason why cwa should show this to the user:
a user that gets such a warning without any details is worried, and trying to find out more details about the time of encounter, he finds the EN log file, and misunderstands these timestamps.

I have seen several such misunderstandings here in the discussions and questions again and again; we may assume that it happens quite often.

cwa showing the times (with day granularity) should prevent such misunderstanding.

[leuchtetgruen]

I agree with what @ndegendogo wrote: I was in that very situation of misinterpreting log data, even going so far to write a little app that takes that log-json and puts the dates of what I thought were matches in a calendar view. When I discussed this idea and the prototype with friends and other people many of them wanted to have this app.

It was only later (luckily - being a responsable person - before providing this app to anybody) that I checked my assumptions more thoroughly. I realized that propably identified the date when an infected person uploaded the keys to the CWA server and not the date of encounter - essentially rendering my app useless.

The takeaway from this little story for me is that people also want to know when they had low risk encounters.

For me personally for example this could be useful to avoid places in which I repeatedly encountered people who later reported an infection even if previous encounters didnt put me at risk (i.e. they were low risk encounters).

[fabboe]

This is only worthwhile if you can see days since last encounter for each of the risk categories.

Currently you might have High Risk 7 days ago, then a day later you have still High Risk but 3 days ago. Was that three days ago now High Risk or Low Risk? Super confusing.

[Ein-Tim]

@fabboe
This Issue is tracked here: https://github.com/corona-warn-app/cwa-documentation/issues/422

[scentury]

While waiting for this change to be implemented. Is my logic correct when saying that the day the "low-risk" warning disappears from the app, is 14 days after the "low-risk" exposure happened?
Since the day the warning disappears is when data from 14 days ago is deleted, hence there is no data there to match the exposure anymore.

[Ein-Tim]

Yes your assumption is correct if the Encounter is more than 14 days old the App will not show the Encounter anymore

[daimpi]

Regarding OP: a possible extension of this in form of a graph which shows contacts over time has been proposed here: https://github.com/corona-warn-app/cwa-wishlist/issues/205 🙂.

[ohobby]

From my own experience, I can report that reporting that you have had one or more low risk encounters, but you don't know when it happened, causes many people to panic and/or brood a lot about when and where it happened.
My partner and some friends are such candidates.
For this reason it would be very important that the date of the encounter is mentioned very quickly, even in the case of low risk encounters. This would help some users not to panic or brood. And prevent many requests to the health department and/or doctor.

[daimpi]

@ohobby

I agree, that displaying this information would be really helpful.

Btw: if you have an Android device you can get this functionality (+more) already now by using @mh-'s corona-warn-companion. You don't even need root, you can simply run it in RaMBLE mode (for future encounters) 🙂.

[ohobby]

@daimpi

Iam on iOS.

[daimpi]

@ohobby

Iam on iOS.

Ok. Under iOS the corona-warn-companion app unfortunately cannot work as iOS is filtering out all the BLE signals containing rolling proximity identifiers (RPIs) already on the OS level. So nothing except for the Exposure Notification Framework (ENF) which is directly integrated into iOS can even see them.

[stefanbode]

From a UI perspective, we can keep the main UI untouched but if the user clicks on the low/high risk, then we open a small list with the dates and color each date with yellow or red to give detailed information. Maybe if there where more than one low risk a day we can also add a counter similar to this:
2020-11-02 - low risk - 1 contact
2020-10-30 - high risk - 2 contacts
2020-10-25 - low risk - 2 contacts

[daimpi]

@stefanbode see those two proposals:

• Encounter/Exposure logbook
• Different information about count and last contact for high and low risk matches

Feel free to upvote 🙂.

[coder66]

This is very important to add, as it will allow the user to "estimate" when to look to symptoms. Eg when I have a low risk encounter and I know the test result date was 1 week ago, I can monitor my health better.

[ehambuch]

I tried to write an app that analyzes the ENF logfile which you can access in your settings. Unfortunately Google has blocked it :-(.
Nevertheless: this functionality must be provided in the original tracking app.

[Ein-Tim]

@ehambuch
Maybe take a look at this: https://felixlen.github.io/ena_log/, is this like what you wanted to build or what did you wanted to analyze with the EN Log? Because more than which is done by @felixlen isn't possible...

[ndegendogo]

@ehambuch please be aware that the timestamps in ENF log file are not the timestamps of the contact, but only the timestamps of check.
Also the ENF log file shows only number of matches, but no risk assessment (like red / green).

[ehambuch]

@ehambuch
Maybe take a look at this: https://felixlen.github.io/ena_log/, is this like what you wanted to build or what did you wanted to analyze with the EN Log? Because more than which is done by @felixlen isn't possible...

Yes, the app covers more or less the same functionality, but with some charts etc.

[webermike]

Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status.

As such contacts might occur only at shopping or eating in a restaurant, one can reconstruct with Date and Time where one habe been and if shopping or queuing anywhere is the risk reason.

This would enhance the analyse and discussion and avoiding of behavior in the future much, when it ia shown if the risk contact was at 8:00 in the bus ir at 12:00 in the McDonalds restaurant or at work at 10:00 o'clock at a certain date/day.

so it is not about "10 days ago" but about exact time and day.

Thanks for implementing that local showup fast.

[webermike]

Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status.

As such contacts might occur only at shopping or eating in a restaurant, one can reconstruct with Date and Time where one habe been and if shopping or queuing anywhere is the risk reason.

This would enhance the analyse and discussion and avoiding of behavior in the future much, when it ia shown if the risk contact was at 8:00 in the bus ir at 12:00 in the McDonalds restaurant or at work at 10:00 o'clock at a certain date/day.

so it is not about "10 days ago" but about exact time and day.

Thanks for implementing that local showup fast.

[skyerjoe]

Im also for publish the Date and the Time only for the User.

This is imho not an Dataprivvacy Problem thus u only know what u have done at this time and no one else.

So than u can react if u want or avoid things if u know okay at this time i was here and here so may i prevent theses locations as good as i can.

best regards

[Ein-Tim]

@skyerjoe

And exactly this is the problem, you know what you've done, where you were, who you met and so can identify the person.
Also the exact time is not revealed by the API, see this comment from @kbobrowski.

The exact date would be possible, see #188

[webermike]

We need to know if - at the exact time - I met with Anke or was at the birthday party or McDonalds. Otherwise i cannot refine my behavior to avoid clusters like Lidl or the bus. Also teachers can warn class 5a instead of 6b.
There is no data protection problem nor a technical reason. Every computer has at any time a time stamp.

[mh-]

Different people come to different conclusions regarding this privacy concern, that's why I wrote this app which does show time (and, when used with the RaMBLE recording app, even position) of the risk encounters:
https://play.google.com/store/apps/details?id=org.tosl.warnappcompanion

My reasoning: It is extremely unlikely that your device only scanned RPIs from one other phone at that time, so you cannot identify the other person. But I understand and accept that other people have different opinions.

[webermike]

The identification of the personbis good and intended. When I met with Anke and she announces tonbe ppsotive via app, she has to tell me anyway. That is what Gesundheitsdienst tries to reseaech via a phone call. Tell me all contacts you remmeber. CWA has them recorded and can give you hints if I was at that time with Anke or at Mcdonalds.

[Ein-Tim]

@webermike But if you get the phone call from the Gesundheitsamt they don't tell you like:
"Yeah Anke Beispielname was tested positive and you met with her at xx:xxh in McDonalds" but they only tell that you met somebody who later tested positive, or do they also tell the Time and Date?

And no, I don't think that the App would have that high of an adoption rate if everybody could identify his contacts...

So or so this is your opinion and what I wrote is mine.
But I can tell you from a technicall aspect that this is not possible with the current implementation.

[webermike]

Have your opinion. Technical allnisbppssiblenor cam be made. When Anke tells Gesundheitsamt my phone number, so that they call me, is she allowed to give my phone number away? Law needs to be adusted that in case of pandemic infection people need =MUST not only to Quarantine, but because of incubation time of 7-14 days all known contacts within that time out of privacy. Otherwise the system is not working..person in private by state order, known contacts of last 14 days in information over public Partner by state order, while the public partner keeps this private and informs only the private person. I am Thankful if any contact or Anke of last 14 days is forced to give me a hint. Only that way I can protect my grandma. And for low risks, i can change my behaviour if I see that tables at mcdonalds are too close to each other screwed at the ground.

[Ein-Tim]

@GPclips
Is there any update about this? Did the Team speak with the RKI about this?

[Blackjacx]

I also want to bring in the suggestion to not show x days ago but to show the exact day including the weekday so we all know immediately which day an encounter happened and we don't have to calculate back in mind.

It makes lives way easier.

[Ein-Tim]

@Blackjacx
See #188

[vaggelisdouros]

Trying to balance privacy vs. revealing some meaningful information, may I suggest/re-iterate that, as a minimum, the app should display whether a low-risk was "old" or it is a "new" one?

Motivation: imagine that today the app shows 1 low-risk encounter, meaning that, during the last 14 days, I had a contact with someone who tested positive.

If the next day the app shows again 1 exposure with low risk, can we at least know whether it corresponds to the previous case (the "old" encounter) or whether that encounter disappeared but a new encounter appeared?

[daimpi]

@vaggelisdouros currently as a workaround you can check the EN log to find out whether this is a new encounter (as log as you're under iOS).
But the situation will improve significantly once the exposure history gets implemented 🙂.

[Ein-Tim]

Starting with v 1.12.0 there will be the exposure history shown in the App (https://github.com/corona-warn-app/cwa-app-ios/pull/1801). This will be shown for "High"- and "Low-Risk" encounters.
This would indirect introduce this too - maybe @dsarkar could update us about this Issue.
Why won't you show the date of "Low-Risk" encounters directly, but only in the exposure history?

[GisoSchroederSAP]

Let me quickly give an answer on-first-shot: When the concept of "red and green only" was established in the very beginning of the CWA, is was quite obvious: Once a warning with "red" risk appears, the user has to take action. A dedicated function was implemented to support this "red" state.
In contrast to the red card, the "green" status doe not require special attention - therefore (with respect to the limited time and resources), there the function to grab the date of the last green encounter was not implemented yet.
Yes, it seems to be inconsistent. Yes the the exposure history will show both types, still it will require two different methods to gather the respective information for red versus green encounters.

I hope, this explains the "Why?" at the current stage.

[Ein-Tim]

Thank you so much for answering @GisoSchroederSAP.❤️

Just btw:
You could get the membership of the Corona-Warn-App Organization here on GitHub (or make it public) so that it is clearer that you are a member (yes your Name is kinda telling this, but I also saw other users with SAP in their names here and it seemed like they had nothing to do with the CWA project at all). 🙂