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
Comments
I agree with Doc77. |
@doc77 Has this or something similar been implemented, or is this still missing? |
Closing due to inactivity |
@doc77 Does this exist in Dexcom app? |
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. |
The first line of the statistics details page shows Range and has three values of in, high and low. 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. |
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.
The text was updated successfully, but these errors were encountered: