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

Show date of Low-Risk encounters #178

Closed
Ein-Tim opened this issue Sep 5, 2020 · 40 comments
Closed

Show date of Low-Risk encounters #178

Ein-Tim opened this issue Sep 5, 2020 · 40 comments
Assignees
Labels
approved This feature request has been accepted by all project partners and is planned for development enhancement New feature or request Fix 1.13 Fix is planned for 1.13 mirrored-to-jira This item is also tracked internally in JIRA

Comments

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Sep 5, 2020

NEWS

This has been introduced with version 1.13: corona-warn-app/cwa-app-ios#1882

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


Internal Tracking ID: EXPOSUREAPP-2836

@ghost
Copy link

ghost commented Sep 24, 2020

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
Copy link

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

@ndegendogo
Copy link

ndegendogo commented Oct 7, 2020

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
Copy link

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
Copy link

fabboe commented Oct 19, 2020

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
Copy link
Contributor Author

Ein-Tim commented Oct 19, 2020

@fabboe
This Issue is tracked here: corona-warn-app/cwa-documentation#422

@scentury
Copy link

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
Copy link
Contributor Author

Ein-Tim commented Oct 25, 2020

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

@daimpi
Copy link

daimpi commented Oct 26, 2020

Regarding OP: a possible extension of this in form of a graph which shows contacts over time has been proposed here: #205 🙂.

@ohobby
Copy link

ohobby commented Oct 31, 2020

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
Copy link

daimpi commented Oct 31, 2020

@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) 🙂.

@vaggelisdouros
Copy link

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
Copy link

daimpi commented Nov 17, 2020

@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 🙂.

@sapcoder123 sapcoder123 assigned maugst and unassigned JoachimFritsch Dec 18, 2020
@Ein-Tim Ein-Tim changed the title Show "Day(s) since Encounter" also for Low-Risk Encounters Show the date of Risk Encounters also for Low-Risk Encounters Dec 18, 2020
@Ein-Tim Ein-Tim changed the title Show the date of Risk Encounters also for Low-Risk Encounters Show the date of Low-Risk Encounters Dec 18, 2020
@Ein-Tim Ein-Tim changed the title Show the date of Low-Risk Encounters Show date of Low-Risk encounters Dec 26, 2020
@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Jan 14, 2021

Starting with v 1.12.0 there will be the exposure history shown in the App (corona-warn-app/cwa-app-ios#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
Copy link

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
Copy link
Contributor Author

Ein-Tim commented Jan 14, 2021

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). 🙂

@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Feb 26, 2021

This will be introduced with version 1.13: corona-warn-app/cwa-app-ios#1882.

@dsarkar dsarkar added the Fix 1.13 Fix is planned for 1.13 label Feb 26, 2021
@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Mar 5, 2021

Version 1.13 which introduced this has been released to GitHub and is available to all users in the next 48h.

See blog post:

DE: https://www.coronawarn.app/de/blog/2021-03-04-corona-warn-app-version-1-13/
EN: https://www.coronawarn.app/en/blog/2021-03-04-corona-warn-app-version-1-13/

See GitHub release:

iOS: https://github.com/corona-warn-app/cwa-app-ios/releases/tag/v1.13.0
Android: https://github.com/corona-warn-app/cwa-app-android/releases/tag/v1.13.2

This issue will now be closed.

@Ein-Tim Ein-Tim closed this as completed Mar 5, 2021
@dsarkar
Copy link
Member

dsarkar commented Mar 5, 2021

@Ein-Tim Thanks!

@heinezen heinezen added the approved This feature request has been accepted by all project partners and is planned for development label Apr 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved This feature request has been accepted by all project partners and is planned for development enhancement New feature or request Fix 1.13 Fix is planned for 1.13 mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests