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

Personal risk monitor graph #205

Open
jeschaller opened this issue Oct 17, 2020 · 12 comments
Open

Personal risk monitor graph #205

jeschaller opened this issue Oct 17, 2020 · 12 comments
Assignees
Labels
feature request A new feature proposal for the app mirrored-to-jira This item is also tracked internally in JIRA statistics Issues regarding the statistics feature

Comments

@jeschaller
Copy link

jeschaller commented Oct 17, 2020

Feature description

To monitor the personal risk behavior, it would great the app shows a graph risk contacts vs. date.
CoronaAppIdea

Problem and motivation

The app shows warns or shows only the current value of risk contact. To make the persons more sensitive for rising infection risk, a graph would show an increase of contacts over time. With that, the users can be get a sensor, how his personal risk, that he can optimize by behavior change.


Internal Tracking ID: EXPOSUREAPP-5018 (statistics overview)

@jeschaller jeschaller added the feature request A new feature proposal for the app label Oct 17, 2020
@daimpi
Copy link

daimpi commented Oct 17, 2020

You want to show contacts with ppl who later tested positive, right?

If you have an Android device you can already use @mh-'s corona-warn-companion to get this information, but I agree that it would be nice to also have the option to directly see this in CWA 🙂.

@jeschaller
Copy link
Author

jeschaller commented Oct 18, 2020

@daimpi> You want to show contacts with ppl who later tested positive, right?

This could be one indicator, that is straight forward and shows direct COVID contacts. With a right framing of values into a user understandable message the aim is to raise the awareness of personal risk can be achieved.

Thinking about that, another parameter could be a more statistical parameter calculated from the product of total number of day contacts multiplied by the local current incident rates (getting from the COVID-Dashboard). This maybe limited by the changing id of the phones, but I think this could resolved by statistical methods and assumptions. At the end this results in a parameter of the personal potential statistical corona events per day (ppsce/d).

If the persons opt-in, the app could also send anonymus values of the potential corona events for a region (Landkreis etc.) to a central server to monitor the social distance of the user.
That would help to check if the measures would decrease the social distances and what is the distribution of social distancing users.

If this can be assessed users with higher ppsce/d-values than others in the area can check their behavior in comparassion to the mean population.

@daimpi
Copy link

daimpi commented Oct 18, 2020

The number of non-positive contacts, is something CWA can't assess: #124 (comment)

@informationiskey
Copy link

May I add here to the beautiful Graph idea the request, to see also all negative test results - documented and qualified by test result or as not qualified - also in here - see details in comment #115

@daimpi
Copy link

daimpi commented Oct 23, 2020

@informationiskey

[…] documented and qualified by test result or as not qualified […]

what do you mean by that?

@informationiskey
Copy link

@daimpi If you are just a "user" of the App - assuming no contact so far, it is "negativ, unqualified" but a contact.
If your app is in warning state for a positive contact to you - "positiv, unqualified"
If you have documented your positive Testresult - "positiv,qualified" and
if, as proposed, you have documented your negative Testresult - "negativ, qualified"
qualified as something from a "maturity" level - in this case only with [0;1;2;3]
Thinking further - if a next generation framework/API would support this - it could be extended also to
if you have been positive, but now you are happily convalesced - after let's assume 4 Weeks time after documenting beeing positiv - "negativ, immun, unqualified" - meaning also, no spreader but a blocker for positive contacts.
if you have been happily convalesced and tested negativ - "negativ, immun, qualified" - trustful blocker for positive contacts.
increasing the maturity level to [...;4;5]
Best regards.

@daimpi
Copy link

daimpi commented Oct 23, 2020

@informationiskey
Ah I see… I think I now understand what you mean… I personally still don't think this is a good idea for the reasons desribed over at #115 (comment) but that is o/c debatable.

@daimpi
Copy link

daimpi commented Oct 26, 2020

Just to mirror some info from over at corona-warn-app/cwa-app-android#1438:

Implementation of this feature will require ENF v.1.5+ and ExposureWindow mode and I hope that we see a switch to the new API soon, especially now that Google strongly recommends switching to the new API (CWA is currently still using v1 legacy mode ^^).

Other related issues:

@klaas
Copy link

klaas commented Oct 30, 2020

+💯

This would also help people to see how much social activity they have. Very useful. Especially in times of Kontaktbeschränkungen.

@daimpi
Copy link

daimpi commented Oct 30, 2020

This would also help people to see how much social activity they have.

As stated above: CWA can't know how many non-positive contacts you had, only how many positive ones.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Nov 15, 2020

This will be integrated (only the number of positive contacts), see: #206 (comment)

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 14, 2021

Starting with v 1.12.0 it will be possible to see when you had encounters:
corona-warn-app/cwa-app-ios#1801

@dsarkar dsarkar added the statistics Issues regarding the statistics feature label Feb 2, 2021
@heinezen heinezen added the mirrored-to-jira This item is also tracked internally in JIRA label Feb 7, 2021
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 statistics Issues regarding the statistics feature
Projects
None yet
Development

No branches or pull requests

8 participants