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

Client side symptom classification algorithm #35

Open
cankisagun opened this issue Mar 30, 2020 · 6 comments
Open

Client side symptom classification algorithm #35

cankisagun opened this issue Mar 30, 2020 · 6 comments

Comments

@cankisagun
Copy link
Contributor

cankisagun commented Mar 30, 2020

This issue builds on Issue #34

Given 40% of Covid19 carriers have only mild symptoms and may not have tested, it's important to identify interactions with these individuals as well.

In order to reduce the data load on SafeTrace API, we propose to run a classification on self reported symptoms (with output high risk symptoms, medium risk symptoms and low risk symptoms) on the client side and pass user status to SafeTrace API

Next step: Determine client side algorithm based on issue #5
Requirements: The algorithm needs to be written in Javascript to run on the client-side

@kistn010
Copy link

kistn010 commented Mar 30, 2020

This issue builds on Issue #34

Given 40% of Covid19 carriers have only mild symptoms and may not have tested, it's important to identify interactions with these individuals as well.

Comment Updated
Data from Wuhan reveal that nearly 80% of infections were spread by patients with mild symptoms or none at all. Citation.

In order to reduce the data load on SafeTrace API, we propose to run a classification on self reported symptoms (with output high risk symptoms, medium risk symptoms and low risk symptoms) on the client side and pass user status to SafeTrace API

Next step: Determine client side algorithm based on issue #5

@cankisagun
Copy link
Contributor Author

@codeanticode this seems is similar to your research. We are trying to classify user reported symptom (fever >38 / 100, Cough, sore throat, shortness of breath) based on risk (high risk symptoms, low .. etc.)
If you have any feedback we'd be very happy to incorporate into our thinking
Cheers

@kistn010
Copy link

kistn010 commented Apr 4, 2020

@cankisagun Apologies. Other obligations prevented me from posting some content. Hopefully things will slow down this weekend and I'll be able to contribute. To be clear, you're looking for hoping to categorize a user's risk based on his/her signs/symptoms (SS), correct?

@cankisagun
Copy link
Contributor Author

@kistn010, yes that's the idea.
@codeanticode is also working on a similar algorithm to classify the risk of symptoms.

The goal of this is to report to individuals not only diagnosed patients around them but also users who show high risk symptoms

@kistn010
Copy link

kistn010 commented Apr 4, 2020 via email

@codeanticode
Copy link

@cankisagun sorry for the slow reply. I have worked on some diagnosis/prognosis prediction models for Ebola with similar sign & symptom data as the input. Logistic regression models are a common choice for kind of prediction tasks.

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

No branches or pull requests

3 participants