|
The case description states that the user believed that too much insulin was being delivered due to the constant clicking sounds from the pod and reported rapid depletion of the "insulin left in pod" information.The physical controller was not received for investigation.Ios log files from the complaint device were uploaded to the cloud system by the user and downloaded for investigation.Review of the ios log files found that the system operated exclusively in automated mode on 13-june-2025 up until the pod was deactivated due to an empty reservoir alarm at 09:33am on 14-june-2025 after delivering roughly a total of 130 u.The user's estimated glucose values (egvs) never dipped below 70 mg/dl while this pod was active.The automated algorithm adapted to the user's egvs appropriately.The user only delivered one bolus over the lifetime of this pod, which was a 4.55u bolus delivered at 20:44 on 13-june-2025.The logs show user interaction in order to program and begin delivery of this bolus.The next pod was activated at 16:16 on 14-june-2025, over 6.5 hours after the previous pod deactivation, and operated exclusively in manual mode for over 16 hours until eventually switching to automated mode.It was noted that the user's egvs dropped below 70 mg/dl at 21:13 on 14-june-2025 and remained below the user's setpoint until it reached the lowest recorded value of 44 mg/dl at 23:28.During this time, the pod correctly delivered the user's input basal rate, which was 10u/hour (200 pulses/hour) until 22:02 when it was decreased to 1u/hour.A basal rate of 10u/hour amounts to 16 or 17 pulses every 5 minutes.It is expected for the pod to have produced "clicking" sounds during this timeframe, since the pod was constantly delivering basal insulin at a rate of 200 pulses per hour.Locked down smartphone: phone_control_ios omnipod software app version: 3.1.1 smartphone operating system: n5004l-am-q-mv01602-06-01.06 smartphone hardware: n5004l cgm sensor type: g7.Please note, that section d is capturing the device identifiers as reported by the complainant.This may not align to the device configuration reported in h11, as this data is pulled from our cloud based on the reported date of event.
|