Skip to content
Lower risk Medical device recall · FDA · Published May 2, 2024

BD Pyxis MedStation ES Software Error May Delay Medication Access

BD Pyxis MedStation ES devices with specific software versions may prevent medication access if Component Manager is configured to 'installed mode' and software patch KB 5033688 is installed. Affected units include MedStation ES (Main), Tower, Anesthesia Station ES, and CII Safe ES models.

🇺🇸 FDA recall #Z-2374-2024Medical 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 MedStation ES devices with specific software versions may prevent users from accessing medication software if Component Manager is configured to 'installed mode' and software patch KB 5033688 is installed. This could delay critical medication access for healthcare facilities. Read more at govinfonow.com/recall/55285-bd-pyxis-medstation-es-software-error-may-delay-medication-access.

Source Summary by GovInfoNow · govinfonow.com/recall/55285-bd-pyxis-medstation-es-software-error-may-delay-medication-access · Updated August 19, 2026 · FDA enforcement record: FDA #Z-2374-2024

Cite this page

“BD Pyxis MedStation ES Software Error May Delay Medication Access.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/55285-bd-pyxis-medstation-es-software-error-may-delay-medication-access. Based on FDA recall #Z-2374-2024 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2374-2024%22&limit=1).

The FDA announced on May 2, 2024, that CareFusion 303, Inc. is recalling BD Pyxis automated dispensing cabinets due to a software error preventing access to the dispensing application. This issue may delay accessing medication for users.

How to tell if you have it

  • BD Pyxis: MedStation ES (Main), REF: 323
  • MedStation ES Tower, REF: 352
  • Anesthesia Station ES, REF: 327
  • CII Safe ES, REF: 1116-00
  • CII Safe ES, Desktop PC, Wired Scanner, REF: 107-254-01
  • CII Safe ES, Desktop PC, Wireless Scanner, REF: 107-255-01
  • CII Safe ES, Desktop PC, Wired Scanner 1.7.3, REF: 107-256-01
  • CII Safe ES, Desktop PC, Wireless Scanner 1.7.3, REF: 107-257-01

The hazard

If the cabinets have specific software versions and Component Manager was configured to "installed mode" with software patch KB 5033688 installed, an error will prevent access to the dispensing software application. This may delay accessing medication.

Context

GovInfoNow's records show CareFusion 303, Inc. has 64 other recalls on record since 2017-06-12. Other recent recalls include the BD Pyxis MedStation 403 Medication Cabinet Recall (2026-04-30) and the CareFusion ES Enterprise Server Software Update Issue Recall (2025-12-03). Other recent recalls of similar products include the Fresenius Medical Care 5008X CAREsystem Recall (2025-10-25).

How to tell if you have this one

Check if your device has a serial number listed in the provided list (e.g., 13534745, 16220738) or software version ES 1.7.x. The product includes MedStation ES (Main), Tower, Anesthesia Station ES, and CII Safe ES models.

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

What to do — step by step

  1. Check Software Configuration

    Verify if Component Manager is configured to 'installed mode' and software patch KB 5033688 is installed in the production environment.

Where it went and when

Where it was distributed

Distributed nationwide and abroad; the notice names 33 states.

Alaska: named in the noticeAKMaine: nationwideMEVermont: nationwideVTNew Hampshire: nationwideNHWashington: named in the noticeWAIdaho: nationwideIDMontana: nationwideMTNorth Dakota: named in the noticeNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: named in the noticeWIMichigan: nationwideMINew York: named in the noticeNYRhode Island: nationwideRIMassachusetts: named in the noticeMAOregon: named in the noticeORNevada: named in the noticeNVWyoming: nationwideWYSouth Dakota: named in the noticeSDIowa: named in the noticeIAIndiana: named in the noticeINOhio: named in the noticeOHPennsylvania: nationwidePANew Jersey: nationwideNJConnecticut: nationwideCTCalifornia: named in the noticeCAUtah: named in the noticeUTColorado: named in the noticeCONebraska: named in the noticeNEMissouri: named in the noticeMOKentucky: nationwideKYWest Virginia: named in the noticeWVVirginia: named in the noticeVAMaryland: nationwideMDDelaware: nationwideDEArizona: named in the noticeAZNew Mexico: named in the noticeNMKansas: named in the noticeKSArkansas: named in the noticeARTennessee: nationwideTNNorth Carolina: named in the noticeNCSouth Carolina: nationwideSCDistrict of Columbia: nationwideDCOklahoma: named in the noticeOKLouisiana: named in the noticeLAMississippi: nationwideMSAlabama: 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 - US Nationwide distribution including in the states of OR, KS, NE, LA, ND, OK, AL, AK, WI, WV, WA, NV, PR, TX, CO, OH, CA, MO, IA, AZ, IN, AR, IL, MN, HI, NM, FL, SD, UT, NY, VA, GA, MA, NC and the countries of TW, CA.” 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, Florida, Georgia, Hawaii, Illinois, Indiana, Iowa, Kansas, Louisiana, Massachusetts, Minnesota, Missouri, Nebraska, Nevada, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Puerto Rico, South Dakota, Texas, Utah, Virginia, Washington, West Virginia, Wisconsin.

Recall timeline

FDA published this recall 3 months after the firm started it.

1. Firm started the recall: May 2, 202412. FDA classified it Class II: Jul 17, 202423. Published in FDA’s Enforcement Report: Jul 24, 202432024
  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.

✎ GovInfoNow

Questions people ask

Is there a risk of serious injury?

The recall does not indicate a risk of serious injury; the hazard is limited to potential delays in medication access.

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