Skip to content
Lower risk Medical device recall · FDA · Published March 11, 2025

BD Pyxis MedBank Mini/Tower and MedFlex: Software bug may cause extra medication doses

BD Pyxis automated dispensing cabinets with software version 2.4 have a bug that can cause incorrect medication counts and extra doses. Affected units include MedBank Mini, Tower, MedFlex, and MedPass models.

🇺🇸 FDA recall #Z-1545-2025Medical deviceBD Pyxis ›
Take action

Contact the company

Recalling firmCareFusion 303, Inc.10020 Pacific Mesa Blvd · San Diego, CA 92121-4386
✎ GovInfoNow plain-language explainer

BD Pyxis automated dispensing cabinets (MedBank Mini, Tower, MedFlex, MedPass) with software version 2.4 have a software bug that can cause incorrect medication counts and potentially give patients more medication than intended. This is a software issue that could lead to over-dosing. Read more at govinfonow.com/recall/52645-bd-pyxis-medbank-mini-tower-and-medflex-software-bug-may.

Source Summary by GovInfoNow · govinfonow.com/recall/52645-bd-pyxis-medbank-mini-tower-and-medflex-software-bug-may · Updated August 17, 2026 · FDA enforcement record: FDA #Z-1545-2025

Cite this page

“BD Pyxis MedBank Mini/Tower and MedFlex: Software bug may cause extra medication doses.” GovInfoNow, updated August 17, 2026. https://govinfonow.com/recall/52645-bd-pyxis-medbank-mini-tower-and-medflex-software-bug-may. Based on FDA recall #Z-1545-2025 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1545-2025%22&limit=1).

CareFusion 303, Inc. recalled BD Pyxis automated dispensing cabinets due to a software bug that may cause patients to receive incorrect medication doses, the FDA said on March 11, 2025.

How to tell if you have it

  • BD Pyxis MedBank Mini
  • BD Pyxis MedBank Tower
  • BD Pyxis MedFlex
  • BD Pyxis MedBank MedPass

The hazard

A software bug prevents the automated dispensing cabinet from calculating countback discrepancies during the issue process, resulting in incorrect transaction quantities being recorded. The bug can also cause the CUBIE to open more times than needed, potentially leading a patient to receive more than the intended dose of medication.

Context

GovInfoNow's records show CareFusion 303, Inc. has 64 other recalls on record since June 12, 2017. Other recent recalls of similar products include Medtronic SynchroMed Flex Infusion Software Issue: Steps May Not Program Correctly (April 8, 2026), Boston Scientific TheraSphere 360 Y-90 Software Anomaly Recall (June 19, 2026) and Baxter Novum IQ Syringe Pump Recall: Software Issue May Cause Infusion Errors (Aug. 11, 2026).

How to tell if you have this one

Check for BD Pyxis MedBank Mini, Tower, MedFlex, or MedPass cabinets with software version 2.4. The software version is listed in the product's reference and unique identification codes.

  • Brand
    BD Pyxis
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Look for the software version in the product's reference and unique identification codes (e.g., 169-143/10885403512568/2.4).

Where it went and when

Where it was distributed

Distributed nationwide; the notice names 48 states.

Alaska: named in the noticeAKMaine: named in the noticeMEVermont: named in the noticeVTNew Hampshire: named in the noticeNHWashington: named in the noticeWAIdaho: named in the noticeIDMontana: named in the noticeMTNorth Dakota: named in the noticeNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: named in the noticeWIMichigan: named in the noticeMINew York: named in the noticeNYRhode Island: nationwideRIMassachusetts: named in the noticeMAOregon: named in the noticeORNevada: named in the noticeNVWyoming: 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: named in the noticeCTCalifornia: named in the noticeCAUtah: named in the noticeUTColorado: named in the noticeCONebraska: named in the noticeNEMissouri: named in the noticeMOKentucky: named in the noticeKYWest Virginia: named in the noticeWVVirginia: 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: named in the noticeNCSouth Carolina: named in the noticeSCDistrict of Columbia: named in the noticeDCOklahoma: named in the noticeOKLouisiana: 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 noticeFL

FDA distribution: “US Nationwide distribution: CA, TX, WI, CO, AK, VA, TN, WA, NC, NY, MS, FL, KS, MI, IN, MN, MT, KY, MO, UT, NJ, OH, PA, ND, OR, NE, SD, NV, OK, GA, MA, IA, HI, ME, AZ, IL, SC, LA, WV, AL, ID, NM, DC, NH, VT, CT, MD, AR, WY.” States read from FDA’s own wording; “not listed” means the notice does not name it.

Named in the notice: Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, District of Columbia, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, Wyoming.

Recall timeline

FDA published this recall 36 days after the firm started it.

1. Firm started the recall: Mar 11, 202512. FDA classified it Class II: Apr 9, 202523. Published in FDA’s Enforcement Report: Apr 16, 202532025
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report

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-1545-2025 (March 11, 2025) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1545-2025 to see it in context.
  • Plain-language summary written by qwen3:4b on August 17, 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