{
  "@context": {
    "schema": "https://schema.org/",
    "au": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/vocab/agent-native#",
    "@vocab": "https://schema.org/",
    "claims": {
      "@id": "au:claims",
      "@container": "@list"
    },
    "epistemicStatus": "au:epistemicStatus",
    "occurred": "au:occurred",
    "supported": "au:supported",
    "adjudged": "au:adjudged",
    "operative": "au:operative",
    "grounding": "au:grounding",
    "groundingType": "au:groundingType",
    "adjudicator": "au:adjudicator",
    "source": "au:source",
    "sourceUrl": "au:sourceUrl",
    "value": "au:value",
    "claimType": "au:claimType",
    "reviewStatus": "au:reviewStatus",
    "commercialInfluence": "au:commercialInfluence",
    "falsifier": "au:falsifier"
  },
  "@id": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/recalls/Z-2618-2023.jsonld",
  "@type": "schema:Dataset",
  "name": "Omnipod 5 Automated Insulin Delivery System",
  "description": "FDA recall Z-2618-2023 — Insulet Corporation is recalling Omnipod 5 Automated Insulin Delivery System (Devices, Class II). The enforcement record is RECORDED; the classification is a DETERMINATION (FDA's regulatory verdict); the boundary is INTERPRETATION (a recall ≠ harm to a specific person). Source: openFDA. CC0.",
  "license": "https://creativecommons.org/publicdomain/zero/1.0/",
  "isAccessibleForFree": true,
  "isPartOf": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/",
  "rdfs:isDefinedBy": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/vocab/agent-native",
  "seeAlso": "https://agenticu.ryanjhunter.workers.dev/commons/the-research-object",
  "dateModified": "2026-06-24T07:02:03.626072+00:00",
  "isBasedOn": {
    "@type": "schema:Dataset",
    "name": "openFDA drug & device enforcement (recall) reports",
    "url": "https://open.fda.gov/apis/drug/enforcement/",
    "creator": {
      "@type": "schema:GovernmentOrganization",
      "name": "U.S. Food & Drug Administration"
    }
  },
  "sameAs": "https://www.accessdata.fda.gov/scripts/enforcement/enforce_rpt-Product-Tabs.cfm?action=select&recall_number=Z-2618-2023&lang=eng",
  "about": {
    "@type": "schema:MedicalDevice",
    "name": "Omnipod 5 Automated Insulin Delivery System",
    "manufacturer": {
      "@type": "schema:Organization",
      "name": "Insulet Corporation"
    }
  },
  "claims": [
    {
      "@id": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/recalls/Z-2618-2023/enforcement-record",
      "@type": "schema:Claim",
      "name": "FDA recall Z-2618-2023: Insulet Corporation is recalling Omnipod 5 Automated Insulin Delivery System",
      "text": "The FDA logged enforcement record Z-2618-2023: Insulet Corporation is voluntarily recalling Omnipod 5 Automated Insulin Delivery System — reason: 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.. Status: Ongoing — the recall is still being carried out.. Initiated 2023-02-28. Affected lots/codes: PT-000559 Omnipod 5 App; all versions of software installed  UDI-DI: 10385081120302. A RECORDED FDA enforcement action (occurred=true).",
      "claimType": "official_fact",
      "reviewStatus": "current",
      "commercialInfluence": false,
      "epistemicStatus": {
        "occurred": true,
        "supported": true,
        "adjudged": true,
        "operative": true
      },
      "grounding": {
        "groundingType": "SourceCitation",
        "source": "openFDA drug & device enforcement (recall) reports — U.S. FDA",
        "sourceUrl": "https://www.accessdata.fda.gov/scripts/enforcement/enforce_rpt-Product-Tabs.cfm?action=select&recall_number=Z-2618-2023&lang=eng",
        "value": "Devices recall, status Ongoing",
        "adjudicator": {
          "name": "openFDA drug & device enforcement (recall) reports — U.S. FDA",
          "url": "https://www.accessdata.fda.gov/scripts/enforcement/enforce_rpt-Product-Tabs.cfm?action=select&recall_number=Z-2618-2023&lang=eng"
        }
      },
      "falsifier": "A RECORD of measured/reported events (occurred=true) from openFDA drug & device enforcement (recall) reports — U.S. FDA; superseded when openFDA drug & device enforcement (recall) reports — U.S. FDA publishes its next release."
    },
    {
      "@id": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/recalls/Z-2618-2023/fda-classification",
      "@type": "schema:Claim",
      "name": "FDA classified recall Z-2618-2023 as Class II",
      "text": "The FDA assigned this recall Class II: Class II — the FDA judged the product may cause temporary or medically reversible harm, with a remote chance of serious harm.. This is the FDA's official risk classification — its regulatory DETERMINATION of the hazard category (a verdict constituted by the FDA's recognition, occurred=FALSE), adjudged=TRUE because the FDA issued it. It is NOT a measurement of harm to any specific person.",
      "claimType": "regulatory_determination",
      "reviewStatus": "current",
      "commercialInfluence": false,
      "epistemicStatus": {
        "occurred": false,
        "supported": true,
        "adjudged": true,
        "operative": true
      },
      "grounding": {
        "groundingType": "AdjudicativeAct",
        "source": "U.S. FDA recall classification (openFDA enforcement)",
        "sourceUrl": "https://www.accessdata.fda.gov/scripts/enforcement/enforce_rpt-Product-Tabs.cfm?action=select&recall_number=Z-2618-2023&lang=eng",
        "value": "Class II",
        "adjudicator": {
          "name": "U.S. FDA recall classification (openFDA enforcement)",
          "url": "https://www.accessdata.fda.gov/scripts/enforcement/enforce_rpt-Product-Tabs.cfm?action=select&recall_number=Z-2618-2023&lang=eng"
        }
      },
      "falsifier": "occurred=FALSE: a regulatory DETERMINATION (an authority's classification/judgment) has NO material truthmaker independent of recognition — it is constituted by U.S. FDA recall classification (openFDA enforcement)'s say-so (a Searle institutional fact), not measured. adjudged=TRUE because U.S. FDA recall classification (openFDA enforcement) (an external authority) issued it. Distinct from a recorded measurement (which has an independent truthmaker) and from a modeled figure (a computed quantity, not a verdict). Challengeable; superseded if the authority reclassifies."
    },
    {
      "@id": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/recalls/Z-2618-2023/boundary",
      "@type": "schema:Claim",
      "name": "What an FDA recall is — and is NOT",
      "text": "A recall is a RECORDED FDA enforcement action — the FDA logged that a firm is removing or correcting a product, classed by the FDA's risk judgment. It does NOT establish that any specific unit is affected or caused harm; causation is not established. This record informs and compares — it is NOT medical advice and does not tell anyone to start or stop a drug or device. For a medical decision, route to the FDA recall record and a licensed pharmacist or prescriber.",
      "claimType": "interpretation",
      "reviewStatus": "current",
      "commercialInfluence": false,
      "epistemicStatus": {
        "occurred": false,
        "supported": true,
        "adjudged": false,
        "operative": true
      },
      "grounding": {
        "groundingType": "Interpretation",
        "source": "Atlas Commons L5 boundary (enforcement-action ≠ harm causation)",
        "sourceUrl": "https://drug-device-safety-atlas.ryanjhunter.workers.dev/",
        "value": "a recorded enforcement action, not proof of harm or causation; not medical advice",
        "adjudicator": null
      },
      "falsifier": "occurred=FALSE (a framing, not an event) and adjudged=FALSE (an in-house reading, not an authority's verdict) — the LOWEST-warrant claim here. A flat representation would render this identically to the official facts; the four-status does not."
    }
  ],
  "hasPart": [
    {
      "@type": "schema:ItemList",
      "name": "FDA recall details — Z-2618-2023",
      "numberOfItems": 9,
      "itemListElement": [
        {
          "@type": "schema:ListItem",
          "position": 1,
          "item": {
            "Field": "Recall number",
            "Value": "Z-2618-2023",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 2,
          "item": {
            "Field": "Product type",
            "Value": "Devices",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 3,
          "item": {
            "Field": "Classification",
            "Value": "Class II",
            "Status": "determination"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 4,
          "item": {
            "Field": "Status",
            "Value": "Ongoing — the recall is still being carried out.",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 5,
          "item": {
            "Field": "Recalling firm",
            "Value": "Insulet Corporation",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 6,
          "item": {
            "Field": "Reason",
            "Value": "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.",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 7,
          "item": {
            "Field": "Initiated",
            "Value": "2023-02-28",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 8,
          "item": {
            "Field": "Lot/code info",
            "Value": "PT-000559 Omnipod 5 App; all versions of software installed  UDI-DI: 10385081120302",
            "Status": "recorded"
          }
        },
        {
          "@type": "schema:ListItem",
          "position": 9,
          "item": {
            "Field": "Distribution pattern",
            "Value": "Distribution throughout the US",
            "Status": "recorded"
          }
        }
      ]
    }
  ]
}