Skip to content
Use caution Medical device recall · FDA · Published June 15, 2017

ICU Medical Plum 360 Infusion System Recall: Connectivity Module May Disengage

ICU Medical recalls Plum 360 Infusion System Model 30010 due to risk of connectivity module disengaging, causing shutdown without alarm. Affected units may delay therapy or interrupt infusions.

🇺🇸 FDA recall #Z-3031-2017Medical deviceICU Medical ›
Take action

Contact the company

Recalling firmICU Medical Inc600 N Field Dr · Lake Forest, IL 60045-4835
✎ GovInfoNow plain-language explainer

What happened, in plain English

ICU Medical is recalling its Plum 360 Infusion System (Model 30010) because the Connectivity Engine Module can disengage from the main chassis, causing the unit to shut down without warning. This could delay or interrupt critical therapy or infusions. Read more at govinfonow.com/recall/73862-icu-medical-plum-360-infusion-system-recall-connectivity-module-may.

Source Summary by GovInfoNow · govinfonow.com/recall/73862-icu-medical-plum-360-infusion-system-recall-connectivity-module-may · Updated September 23, 2026 · FDA enforcement record: FDA #Z-3031-2017

Cite this page

“ICU Medical Plum 360 Infusion System Recall: Connectivity Module May Disengage.” GovInfoNow, updated September 23, 2026. https://govinfonow.com/recall/73862-icu-medical-plum-360-infusion-system-recall-connectivity-module-may. Based on FDA recall #Z-3031-2017 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-3031-2017%22&limit=1).

Why it’s dangerous

The Connectivity Engine Module may detach from the main chassis during use, causing the unit to shut down without alerting the user. This could interrupt critical therapy or infusions if the patient requires continuous treatment.

Who’s affected

Patients using the Plum 360 Infusion System Model 30010 for medical therapy are affected. Healthcare providers and patients receiving infusion treatments are most at risk.

How to tell if you have this one

Check for the Plum 360 Infusion System with model number 30010. This product was sold by ICU Medical, Inc. for medical use.

  • Brand
    ICU Medical
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check for Disengagement

    Inspect the Connectivity Engine Module to ensure it remains securely attached to the main chassis.

Where it went and when

Where it was distributed

Distributed nationwide and abroad; the notice names 34 states.

Alaska: nationwideAKMaine: named in the noticeMEVermont: nationwideVTNew Hampshire: named in the noticeNHWashington: named in the noticeWAIdaho: nationwideIDMontana: named in the noticeMTNorth Dakota: nationwideNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: named in the noticeWIMichigan: named in the noticeMINew York: named in the noticeNYRhode Island: nationwideRIMassachusetts: nationwideMAOregon: nationwideORNevada: nationwideNVWyoming: named in the noticeWYSouth Dakota: named in the noticeSDIowa: named in the noticeIAIndiana: named in the noticeINOhio: named in the noticeOHPennsylvania: named in the noticePANew Jersey: named in the noticeNJConnecticut: nationwideCTCalifornia: named in the noticeCAUtah: nationwideUTColorado: nationwideCONebraska: named in the noticeNEMissouri: named in the noticeMOKentucky: named in the noticeKYWest Virginia: nationwideWVVirginia: named in the noticeVAMaryland: named in the noticeMDDelaware: nationwideDEArizona: named in the noticeAZNew Mexico: named in the noticeNMKansas: named in the noticeKSArkansas: named in the noticeARTennessee: named in the noticeTNNorth Carolina: nationwideNCSouth Carolina: nationwideSCDistrict of Columbia: named in the noticeDCOklahoma: nationwideOKLouisiana: named in the noticeLAMississippi: named in the noticeMSAlabama: named in the noticeALGeorgia: named in the noticeGAHawaii: named in the noticeHITexas: named in the noticeTXFlorida: named in the noticeFLPuerto Rico: named in the noticePR

FDA distribution: “Worldwide Distribution - USA (nationwide) Distribution to the states of including Puerto Rico : AL, AR, AZ, CA, FL, GA, HI, IA, IL, IN, KS, KY, LA, MD, ME, MI, MN, MO, MS, MT, NE, NH, NJ, NM, NY, OH, PA, SD, TN, TX, VA, WA, WI, WY and…” States read from FDA’s own wording; “not listed” means the notice does not name it.

Named in the notice: Alabama, Arizona, Arkansas, California, District of Columbia, Florida, Georgia, Hawaii, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, New Hampshire, New Jersey, New Mexico, New York, Ohio, Pennsylvania, Puerto Rico, South Dakota, Tennessee, Texas, Virginia, Washington, Wisconsin, Wyoming.

Recall timeline

FDA terminated this recall 2.8 years after the firm started it.

1. Firm started the recall: Jun 15, 201712. FDA classified it Class II: Aug 14, 201723. Published in FDA’s Enforcement Report: Aug 23, 201734. FDA terminated the recall: Apr 17, 2020420172020
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report
  4. FDA terminated the recall

Dates from the agency record only; steps without a date are left out.

Similar recalls

Latest medical device recalls

Keep exploring

Where this comes from

The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.

  • Official source: FDA Recall #Z-3031-2017 (June 15, 2017) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-3031-2017 to see it in context.
  • Plain-language summary written by qwen3:4b on September 23, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
  • GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.
GovInfoNow is an independent guide. We are not FDA or any government agency. Always confirm details with the official recall.Data: CPSC · FDA · NHTSA · USDA