|
The physical device was not returned for evaluation.Cloud data from the user for the day of 03feb2026 was downloaded and reviewed.Review of the cloud data confirmed that the reported boluses were delivered at the reported times.The cloud showed that none of the boluses were programmed with a carb or glucose entry and that all were manually adjusted to the total bolus volume.Without application log files, it cannot be determined if the controller was interacted with to program, confirm, and start delivery of these boluses, as the cloud data does not contain records of interactions.The exact cause of the reported uncommanded boluses could not be determined from the available cloud data.Locked down smartphone: phone_control_android omnipod software app version: 3.1.6 operating system: ap3a.240905.015.A2.G991usqsjhzaa hardware: sm-g991u cgm sensor type: g7 please note, the device identifiers are captured as reported by the complainant and may not align with the device configuration reported in this section as this data is pulled from our cloud based on the reported date of event.
|
|
It was reported that the patient noticed several uncommanded boluses after a software update on their android phone.The update was done on (b)(6) 2026 and they experienced uncommanded boluses on (b)(6) 2026, (b)(6) 2026, and (b)(6) 2026.The phone had been located in the backpack of the patient in the school nurse's office and the patient was in physical education class.The unexpected boluses reported that occurred on (b)(6) 2026 were as follows: 09:18 = 5 units; 09:39 = 5 units; 09:54 = 5 units; 10:09 = 2 units; 10:31 = 2 units; 10:38 = 3 units; 13:36 = 1 unit.The patient¿s blood glucose was reported to have been less than 54 mg/dl, but exact results and any treatment provided were not specified.The (b)(6) 2026 event is reported in insulet reference number (b)(4) and the (b)(6) 2026 event is reported in insulet reference number (b)(4).
|