search

tidepool-org / hub

[DEPRECATED] Central storage for Tidepool planning and issue tracking.
2 stars 2 forks source link

tideline should identify when a suspend is pump-generated #98

Open brandonarbiter opened 10 years ago

brandonarbiter commented 10 years ago

From an email to me, @jebeck, and @cheddar on May 12, 2014, @HowardLook wrote:

Since the CareLink data tells us that this is a pump-initiated suspend event, we should (as a backlog item) show that.

Thanks, Howard

Additionally, Saleh contributed:

Makes it clear that this was a pump driven suspend, not a user 0% basal.

brandonarbiter commented 10 years ago

https://trello.com/c/kCFUI6YM

brandonarbiter commented 10 years ago

While we work to differentiate pump initiated vs person initiated suspends, we should also make it explicit whether this is a temp basal or a suspend.

Cc: @skrugman

cheddar commented 10 years ago

Can we make this issue just for differentiating suspends from temps? Pump initiation versus person initiation is actually not that cut-n-dry. When the pump alarms, it suspends immediately, but then the user has the choice of whether to continue the suspend (effectively making it a "user initiated"?) or to cancel the suspend.

I think we would be better off having a timeline of alarms from the pump, then lining up the alarm with the start of the suspend would make it clear that it was from an alarm.

brandonarbiter commented 10 years ago

@cheddar I created a new issue hub https://github.com/tidepool-org/hub/issues/102 that specifies Blip should differentiate temp basal of 0% from a suspend.

This issue, on the other hand, will remain specific to identifying whether a suspend was initiated by a human or a low glucose suspend.