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

Store PA risk scores in the patient #5998

Closed
ecsalomon opened this issue Oct 3, 2019 · 3 comments
Closed

Store PA risk scores in the patient #5998

ecsalomon opened this issue Oct 3, 2019 · 3 comments
Labels
Type: Feature Add something new Won't fix: Duplicate Covered by a different issue

Comments

@ecsalomon
Copy link

Is your feature request related to a problem? Please describe.
Currently, predictive algorithm risk scores are calculated in the app in both tasks and targets and in the contact summary. This creates duplication of code, is a potential source of technical debt, and leads to unnecessary computation.

Describe the solution you'd like
A better implementation of risk scoring is to set a minimum refresh window (e.g., 1 day, 1 week, 1 month) and store the risk score and its calculation date in the patient to be accessible by tasks, targets, forms, and contact summary. Scores would then be recalculated only when the age of the risk score is greater than the minimum refresh window.

Describe alternatives you've considered
Risk scores loaded to the contact page from the server side are infeasible in an offline-first context where we cannot guarantee that they will reach the phone in time to be of use.

Additional context
Depending on the approach taken in our screening work with PIH, this may be useful for implementation in that project in April 2020.

This is also relevant as we consider expansion and scale-up of our predictive algorithms initiatives through recently launched data science partnerships. These partnerships would be looking to close out in mid-2020, with implementation possibly in late 2020.

@ecsalomon ecsalomon added the Type: Feature Add something new label Oct 3, 2019
@MaxDiz MaxDiz added this to To do in Data Scientists Backlog via automation Oct 4, 2019
@MaxDiz MaxDiz moved this from To do to Needs Triage in Data Scientists Backlog Oct 4, 2019
@yembrick yembrick moved this from Needs Triage to To do in Data Scientists Backlog Mar 12, 2020
@ecsalomon
Copy link
Author

Duplicate of #5708?

@MaxDiz
Copy link
Contributor

MaxDiz commented Mar 12, 2020

@garethbowen please see above ^^ comment. The issues look like duplicates to me, but you're much closer to the work than I am

@garethbowen
Copy link
Member

Yes let's close this as a duplicate. The other one has a little more discussion and is actually scheduled. @ecsalomon Please add any additional information to the other issue so it describes everything you need.

Data Scientists Backlog automation moved this from To do to Done Mar 12, 2020
@garethbowen garethbowen added the Won't fix: Duplicate Covered by a different issue label Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Add something new Won't fix: Duplicate Covered by a different issue
Projects
None yet
Development

No branches or pull requests

3 participants