|
In the case description, the user mentioned a 20 u bolus being delivered uncommanded.The physical controller was not received for investigation.Android log files from the complaint device were uploaded to the cloud system by the user and downloaded for investigation.Review of the android log files confirmed the delivery of a 20 u bolus.The audit log files showed that a 20 u bolus was confirmed and started based on no blood glucose or carb values entered.The engineering log files showed that the bolus button was pressed to open the bolus calculator.The logs show that the total bolus text was changed one digit at a time from 0 to 2 to 20 though no carbs or blood glucose values were entered.The confirm button was then pressed to bring the controller to the confirm bolus screen and then the start button was pressed to begin bolus delivery.The bolus record for the start bolus confirmed that a 20 u bolus was started and that the bolus was user adjusted from 0 u to 20 u.Review of the log files found evidence of interaction with the controller to program, confirm, and start the reported bolus.No evidence of an uncommanded bolus was observed in the available log files.Locked down smartphone: phone_control_android.Omnipod software app version: 3.1.1.Smartphone operating system: ap3a.240905.015.A2.G991usquehyda.Smartphone hardware: sm-g991u.Cgm sensor type: g6.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.
|
|
It was reported by the patient that they received an uncommanded bolus of 14.5 units of insulin on (b)(6) 2025.After reviewing the bolus history, the patient reported the uncommanded bolus was actually for 20 units, however his pod ran out of insulin and was only able to deliver 14.5 units.The bolus history showed bolus calculation for 0 carbohydrates, and no blood glucose level.Prior iob (insulin on board) showed 1.65 units, but no adjustments were made to the bolus amount for iob as a blood glucose level was not entered.The patient uses the omnipod 5 app, and reported his phone was in a pocket at the time of event and the app opened up on its own.The patient reported his last interaction with the omnipod app prior to the uncommanded bolus was around 12:30pm when he delivered a bolus for lunch.The uncommanded bolus was reported to have occurred at 3:54pm the same day.The patient noted he recently updated the software on his samsung galaxy s21, to android 15.The patient denied programming the bolus.The omnipod 5 app showed iob (insulin on board) of 7.54 units after the omnipod system had started to deliver the uncommanded bolus.The patient's max bolus is set to 20 units.Other omnipod 5 settings are target glucose of 120 mg/dl, corrective factor of 45 mg/dl, insulin to carbohydrate ratio of 1u to 7 grams or 1u to 11 grams, depending on the time of day, and duration of insulin action of 2.5 hours.No adverse events were reported due the uncommanded bolus.Patient did not require any medical attention or treatment.Data logs have been uploaded for lab investigation.
|