Skip to content
Recall Observatory FDA recall evidence

Exact FDA event identifier

Event 92909

1 recalled-product record grouped only because every row carries this exact official event ID.

Open FDA event record

Event summary

Timeline bucket
February 28, 2023
Product types
Device
Classifications
Class II
Statuses
Ongoing
Recalling firm wording
Insulet Corporation

Dossier provenance

Source snapshots represented here

  • openFDA Device Enforcement Report-date coverage June 20, 2012–July 08, 2026 Known gap: openFDA describes 2004-present coverage, but the current export has no report-date records in this interval.
  • openFDA Device Recall event_date_initiated coverage June 01, 1997–June 30, 2026

Enforcement coverage uses report dates; product initiation dates can precede those bounds. Device-enrichment coverage uses FDA event_date_initiated.

How coverage and grouping work

Complete imported group

Every recalled product in this event

1 official enforcement rows

Product dates, classifications, firms, and source wording remain attached to their individual rows. Opening this dossier never hides products that did not match a prior timeline filter.

device · product 1 of 1

Omnipod 5 Automated Insulin Delivery System

Z-2618-2023
Recall number
Z-2618-2023
Initiated
February 28, 2023
Classification
Class II
Status
Ongoing
Recalling firm
Insulet Corporation
Quantity
11,016 users

App-derived interpretation

Unknown reason.no_named_rule · v1.0.0
An error message was received when using the Omnipod 5 App on compatible smartphones that prevented phone control users from controlling the Omnipod 5 Automated Insulin Delivery System from their Omnipod 5 App which may cause a delay in therapy. To reduce the volume of inquiries Insulet was receiving from customers, an email was sent to all phone control users and the cause of the error message was resolved by reverting to prior certificates on the Insulet cloud to secure communications between the Omnipod 5 App sotware and the Insulet Cloud. This issue was limited to only certain compatible Android smartphones and did not affect the Omnipod 5 Pods or the dedicated locked-down Controller provided by Insulet. All other Omnipod 5 users were still able to manage their insulin with the device without use of the smartphone app and affected users were able to switch to the locked-down control provided to all users when they initiated the device during the time the App was unavailable to them. Further, the Omnipod itself continued to deliver insulin as per its pre-programmed settings so although affected users who did not have the locked-down controller readily available may not have been able to command insulin boluses during this time, they continued to receive basal insulin without interruption. Lastly, users of the Omnipod 5 were advised during training to always have backup supplies ready in the event of a device malfunction which would include alternative means to deliver insulin subcutaneously until the issue is resolved to minimize disruption to their insulin regimen. There were 2,168 complaints received out of 7,838 users with the Android compatible smartphones affected and 9 MDRs were submitted, however, there were no serious injuries reported or reports of erroneous results as the primary issue was a delay in therapy. This defect cannot cause false results that could negatively impact patients.

These labels are deterministic app interpretations, not FDA categories.

Official device-enrichment evidence · Sourced

Software Design Change

Compare all device evidence states

Inspect official wording and provenance

Reason for recall

An error message was received when using the Omnipod 5 App on compatible smartphones that prevented phone control users from controlling the Omnipod 5 Automated Insulin Delivery System from their Omnipod 5 App which may cause a delay in therapy. To reduce the volume of inquiries Insulet was receiving from customers, an email was sent to all phone control users and the cause of the error message was resolved by reverting to prior certificates on the Insulet cloud to secure communications between the Omnipod 5 App sotware and the Insulet Cloud. This issue was limited to only certain compatible Android smartphones and did not affect the Omnipod 5 Pods or the dedicated locked-down Controller provided by Insulet. All other Omnipod 5 users were still able to manage their insulin with the device without use of the smartphone app and affected users were able to switch to the locked-down control provided to all users when they initiated the device during the time the App was unavailable to them. Further, the Omnipod itself continued to deliver insulin as per its pre-programmed settings so although affected users who did not have the locked-down controller readily available may not have been able to command insulin boluses during this time, they continued to receive basal insulin without interruption. Lastly, users of the Omnipod 5 were advised during training to always have backup supplies ready in the event of a device malfunction which would include alternative means to deliver insulin subcutaneously until the issue is resolved to minimize disruption to their insulin regimen. There were 2,168 complaints received out of 7,838 users with the Android compatible smartphones affected and 9 MDRs were submitted, however, there were no serious injuries reported or reports of erroneous results as the primary issue was a delay in therapy. This defect cannot cause false results that could negatively impact patients.

Code information

PT-000559 Omnipod 5 App; all versions of software installed UDI-DI: 10385081120302

Distribution pattern

Distribution throughout the US