| Model Number |
PT-002343 |
| Medical Device Problem Code |
Failure to Analyze Signal (1539)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
10/22/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Cloud data for the period of 20oct2025-23oct2025 was downloaded for review.Review of the cloud data found that a 4 u bolus was started on the date of occurrence.The cloud data showed that the 4 u bolus was manually adjusted to 4 u and no carbs or blood glucose values were entered.The cloud data also shows a termination record for the 4 u bolus approximately 3 minutes after the start of the bolus.It could not be conclusively determined if the user attempted multiple times unsuccessfully to cancel this bolus before a successful attempt occurred.It also could not be conclusively determined if an attempt was made to enter 0.4 rather than 4, as the cloud data does not contain logging of the interactions with the controller.The exact cause of the reported event could not be determined.Cloud - locked down/smartphone lockdown cloud - omnipod 5 software app version 3.1.1 cloud - operating system n5004l-am-q-mv01602-06-01.06 cloud - hardware n5004l cloud - 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.
|
| |
|
Event or Problem Description
|
|
The patient reported that they accidentally programmed a bolus of 4 units instead of the intended 0.4 units.Upon quickly realizing the mistake, the patient tried to cancel the bolus.However, the patient reported that the bolus could not be canceled.No impact on the patient's glucose levels was reported.
|
| |
|
Search Alerts/Recalls
|