Skip to content
Lower risk Medical device recall · FDA · Published February 1, 2024

BD Pyxis MedStation ES Software Freezes: Risk of Medication Delays

BD Pyxis MedStation ES models with software versions 1.4.x, 1.5.x, or 1.6.x may freeze, causing medication delays and data loss. Affected units include MedStation ES (REF 323), Anesthesia Station ES (REF 327), and MedStation ES Tower (REF 352).

🇺🇸 FDA recall #Z-1223-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 freeze unexpectedly, leading to medication access delays and potential data loss. This affects healthcare facilities using these devices for medication storage and dispensing. Read more at govinfonow.com/recall/56206-bd-pyxis-medstation-es-software-freezes-risk-of-medication-delays.

Source Summary by GovInfoNow · govinfonow.com/recall/56206-bd-pyxis-medstation-es-software-freezes-risk-of-medication-delays · Updated August 19, 2026 · FDA enforcement record: FDA #Z-1223-2024

Cite this page

“BD Pyxis MedStation ES Software Freezes: Risk of Medication Delays.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/56206-bd-pyxis-medstation-es-software-freezes-risk-of-medication-delays. Based on FDA recall #Z-1223-2024 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1223-2024%22&limit=1).

CareFusion 303, Inc. is voluntarily recalling BD Pyxis automated dispensing cabinets worldwide due to software issues that may cause application hangs or crashes, potentially delaying medication access and causing data loss, the FDA said on Feb. 1, 2024.

How to tell if you have it

  • BD Pyxis: MedStation ES, REF: 323
  • Anesthesia Station ES, REF: 327
  • MedStation ES Tower, REF: 352
  • REF/UDI-DI: 323/10885403512667, 327/10885403477836, 352/10885403512674
  • Software Version ES System Release 1.4.x, 1.5.x and 1.6.x

The hazard

The affected automated dispensing cabinets running the specified software and Windows 10 operating system may experience random application hangs, freezes, or crashes. These technical failures may result in delays in medication access and potential data loss.

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 BD Pyxis MedStation ES REF 323 Medication Cabinet Recall (April 30, 2026), CareFusion labeling recall (Feb. 11, 2026), and BD Pyxis ES Enterprise Server Software Update Issue Recall (Dec. 3, 2025). Other recent recalls of similar products include Philips PIC iX Essentials Software Freezes (July 31, 2026), Philips Patient Information Center iX Software Freezes (July 31, 2026), and Fresenius Medical Care 5008X CAREsystem Recall (Oct. 25, 2025).

How to tell if you have this one

Check for the model name and reference number on the device label. Affected units include MedStation ES (REF 323), Anesthesia Station ES (REF 327), and MedStation ES Tower (REF 352) with software versions 1.4.x, 1.5.x, or 1.6.x.

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

What to do — step by step

  1. Check Software Version

    Review the software version on the device to see if it is 1.4.x, 1.5.x, or 1.6.x.

Where it went and when

Where it was distributed

Distributed nationwide and abroad; the notice names 50 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: named in the noticeRIMassachusetts: 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: named in the noticeDEArizona: 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 noticeFLPuerto Rico: named in the noticePR

FDA distribution: “Worldwide distribution - US Nationwide distribution including in the states of VA, SC, IL, AL, KS, LA, GA, FL, CA, PR, PA, WV, WA, HI, NC, MD, AR, NY, ND, TX, NM, GU, MS, AZ, DC, AK, NE, DE, CO, SD, MO, NJ, OK, NV, OH, KY, WY, MT, UT, ID,…” 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, Delaware, 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, Puerto Rico, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, Wyoming.

Recall timeline

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

1. Firm started the recall: Feb 1, 202412. FDA classified it Class II: Mar 1, 202423. Published in FDA’s Enforcement Report: Mar 13, 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

Do I need to stop using my BD Pyxis device immediately?

No, the recall does not require immediate stop use. The issue is a software freeze that may cause delays, but the device can continue to be used with caution.

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-1223-2024 (February 1, 2024) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1223-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