Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

isCurrentUserSick is not used properly. #4

Open
seriyvolk83 opened this issue May 7, 2020 · 2 comments
Open

isCurrentUserSick is not used properly. #4

seriyvolk83 opened this issue May 7, 2020 · 2 comments

Comments

@seriyvolk83
Copy link

isCurrentUserSick is never set to true. Hence, even if user will be sick he will receive notifications if someone sick will appear around.

Probably need to isCurrentUserSick:=true when user self reports.

@seriyvolk83
Copy link
Author

seriyvolk83 commented May 7, 2020

Also I have a few questions:

  • Why CurrentUserExposureNotifier needed if it's possible to notify right when report is received from the backend?
  • Why do you need to save self-reports locally and later upload if it's possible to upload them right when they are generated?

@ashellwig
Copy link

  • Why do you need to save self-reports locally and later upload if it's possible to upload them right when they are generated?

I imagine it would have something to do with HIPPA Emergency Access Procedures or Data security restrictions. Anything with ePHI or PHI would need to be accessible in the instance of a power outage or data loss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants