Pump Increments Are Not Configurable During Onboarding

[munchyk]

Describe the bug

In the onboarding flow, the Pump Model selector for insulin delivery increments doesn't actually change the available basal rate increments.

Trio Version:

• Version Number: 8.4.60

[trioneer-dev]

You’ll need to be a bit more precise please.

[munchyk]

The pump selection on the “Units & Pump” screen in the onboarding flow is supposed to allow for smaller basal rate delivery increments when the pump supports it. The issue is that the basal rate therapy screen has the same starting rate of 0.05 U/hr irrespective of the pump chosen. See screenshot below for the pump screen referenced.

[trioneer-dev]

That was the wrong way of being more precise 😂
Which pump selection did you choose and which increment did you expect (or not get) in the subsequent therapy settings views @munchyk ?

[munchyk]

@trioneer-dev Lol.

I use omnipod which supports 0.05 u/hr increments. From what i know, a dana or medtronic pump can support 0.01 or 0.025 U/hr increments respectively.

It seems that the Pump Model selector doesnt actually change the available increments for basal delivery during onboarding, despite the explanation there regarding the purpose of the selector. 0.05 u/hr is the only increment available, regardless of the pump model selected.

I wasnt actually trying to use a different increment. Just noticed that this was the case

[trioneer-dev]

@munchyk This is what we provide:

var basalRatePickerSetting: PickerSetting {
  switch selectedPumpOption {
  case .dana:
      return PickerSetting(value: 0.1, step: 0.05, min: 0, max: 3, type: .insulinUnitPerHour)
  case .minimed:
      return PickerSetting(value: 0.1, step: 0.05, min: 0, max: 35, type: .insulinUnitPerHour)
  case .omni:
      return PickerSetting(
          value: 0.1,
          step: 0.05,
          min: 0,
          max: 30,
          type: .insulinUnitPerHour
      )
  case .medtrum:
      return PickerSetting(value: 0.1, step: 0.05, min: 0.05, max: 30, type: .insulinUnitPerHour)
  case .none:
      // same as dash, as that is the fallback
      return PickerSetting(value: 0.1, step: 0.05, min: 0, max: 30, type: .insulinUnitPerHour)
  }
}

We have never offered MDT model-distinct rates, as we are not letting the user discern between all available models and their rates for example. This is more so to control max rates.
Dana can offer 0.01 or 0.10 for basal, but 0.05, 0.1, 0.5, or 1.0 for bolus, so we are going with the “easiest” common denominator here. Same for the other pumps.

So I reckon this works as designed :)

[munchyk]

@trioneer-dev In that case, shouldn't the screen say something along the lines of: "Note: Choosing your pump model determines the range of available basal rates" or "maximum/largest available basal rate"?

"Increments" connotes...increments.

[munchyk]

Or maybe, since the others have (pretty much) the same available ranges, just put a settings description on the actual basal rate selection screen informing user that the max available basal rate for a Dana pump is 3 U/hr?

Another option could be to remove it entirely and to ask the user to select a different basal rate if they choose a Dana pump after onboarding (which i assume would need to be done either way for people who switch to a Dana pump from a different supported pump with a set basal rate that is higher than the Dana supports.)