| Model Number |
PT-000559 |
| Medical Device Problem Code |
Insufficient Device Problem Information (3190)
|
| Health Effect - Clinical Codes |
Nausea (1970); Elevated ketones/Diabetic Ketoacidosis (2364)
|
| Date of Event |
04/26/2026
|
|
Type of Reportable Event
|
Serious Injury
|
|
Event or Problem Description
|
|
Patient reported that a pod was not being worn at the time medical attention was sought, as the pod had come off during sleep.The patient reported experiencing nausea and elevated glucose values.The patient was transported to the hospital where diabetic ketoacidosis was diagnosed.Insulin therapy was administered and the patient was hospitalized for three days and being discharged on (b)(6) 2026.Patient stated that the event was not related to receiving insulin after the pod came off and that the system records indicated that the pod reservoir was empty on (b)(6) 2026.It is unknown whether any controller message was displayed, as this information was not reported.Blood glucose values at the time of the event were not available, as the patient was unable to recall.
|
| |
|
Additional Manufacturer Narrative
|
|
In the case description, the user mentioned having high glucose levels while using the system and an empty reservoir alarm being generated.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 confirmed the generation of a pod out of insulin alarm at 03:41 on (b)(6) 2026.The logs showed that a low pod insulin alert was generated at 18:07 on (b)(6) 2026.Review of the patient history buffer (phb) audit logs found that the pod ran for 1821 pulses (approximately 91.05 u) prior to deactivation.Review of the phb data found that the system was used primarily in automated mode and the automated algorithm was able to appropriately adjust the microbolus amounts based on the estimated glucose values and user inputs.The phb data showed that the estimated glucose values increased to urgent high (greater than 400 mg/dl) at 14:44 on (b)(6) 2026 and remained urgent high until the pod was deactivated.The automated algorithm responded appropriately, increasing the microbolus amounts delivered until the maximum was reached.An automated delivery restriction alert was generated at 22:24 on (b)(6) 2026 that was not acknowledged until 03:39 on (b)(6) 2026.While the alert was generating, the system was correctly delivering safe basal, which is the lower of the user's manual basal program and adaptive basal rate.No evidence of issues with insulin delivery was observed in the log files.Without the pod, the initial fill position of the plunger could not be determined and so it could not be determined if the plunger was close to the bottom of the reservoir before the pod out of insulin alarm was generated.The exact cause of the reported early empty reservoir alarm could not be determined from the available log files.Locked down smartphone: phone_control_ios omnipod software app version: 2.1.0 operating system: 26.4 hardware: iphone15.4 cgm sensor type: dexcom 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.
|
| |
|
Search Alerts/Recalls
|