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

Serious Low #579

Open
doc77 opened this issue Sep 7, 2018 · 6 comments · May be fixed by #2656
Open

Serious Low #579

doc77 opened this issue Sep 7, 2018 · 6 comments · May be fixed by #2656

Comments

@doc77
Copy link

doc77 commented Sep 7, 2018

Could there be a stat for serious lows, like below 55 mg/dl? There is now % in, % low, % hi, but not the very important statistic of serious low.

@ANDREAPIPPI
Copy link

ANDREAPIPPI commented Sep 7, 2018

I agree with Doc77.
I set xDrip+ Lows at 100, because I wish to have the possibility to correct it-before-reaching dangerous low values, but sometimes it happens anyway.
So my MD is interested to know the exact percentage of -real- Lows in my statistics.
Thanks.
Andrea :-)

@Navid200
Copy link
Collaborator

Navid200 commented Feb 7, 2021

@doc77 Has this or something similar been implemented, or is this still missing?
If not, would you please close this issue?

@Navid200 Navid200 added enhancement type-discussion Issue discussing new features or enhancements labels Feb 16, 2021
@Navid200
Copy link
Collaborator

Navid200 commented Mar 9, 2021

Closing due to inactivity

@Navid200 Navid200 closed this as completed Mar 9, 2021
@Navid200
Copy link
Collaborator

Navid200 commented Aug 3, 2021

@doc77 Does this exist in Dexcom app?
Does this capability exist in any app currently?

@jwoglom
Copy link
Contributor

jwoglom commented Aug 3, 2021

This sounds like something we could fairly easily incorporate into the statistics page of xDrip. I think Dexcom's usual definition of "serious low" is 55 mg/dl -- that's the point at which my Tandem pump doesn't allow you to disable CGM alarms.

However, I wonder what value having a "percentage of serious lows" would provide compared to, e.g., number of occurrences of serious lows, which could be a better metric potentially. It's also a good question of how much functionality we realistically want to provide in the statistics views -- since we're definitely limited by a certain amount of space on a phone like screen that we can fill with data, and we probably don't want to add yet even more indecipherable options for controlling what gets displayed in the statistics.

@Navid200
Copy link
Collaborator

Navid200 commented Aug 3, 2021

The first line of the statistics details page shows Range and has three values of in, high and low.
Now, it will have two additional values of very low and very high.
But, the values for low and high are specified by the user under Settings -> Glucose Units. There will be two new entries on that page called very low and very high.

The value is that a report, for the doctor, can be much more representative of how the control is. For example if you have 5% lower than 4 but only 1% lower than 3.9 versus if you have 5% lower than 4 and 4.5% lower than 3.9, the first case is a much better control, which currently cannot be represented.

But, it's pointless to open a PR, no matter how easy it is to incorporate, if it is going to just sit there as an open PR for years and never be merged.
I'd like to know if the capability exists in other apps. Then, we may have a better chance of convincing the others why we should have this.

@Navid200 Navid200 added status-postponed Features which might be implemented sometimes and removed type-discussion Issue discussing new features or enhancements labels Aug 3, 2021
@Navid200 Navid200 reopened this Oct 19, 2021
@Navid200 Navid200 removed the status-postponed Features which might be implemented sometimes label Oct 19, 2021
@Navid200 Navid200 linked a pull request Feb 1, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants