Skip to content
Lower risk Medical device recall · FDA · Published November 20, 2025

CareFusion Pyxis MedStation ES Firmware Update Causes Access Issues

CareFusion recalls Pyxis MedStation ES models with firmware 1.48 due to potential access delays for medications. Affected units may need updates to prevent medication delays.

🇺🇸 FDA recall #Z-0962-2026Medical deviceCareFusion ›
Take action

Contact the company

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

CareFusion is recalling Pyxis MedStation ES medical devices that have a specific firmware version. This update can cause errors in accessing stored medications, potentially delaying patient care. Read more at govinfonow.com/recall/50634-carefusion-pyxis-medstation-es-firmware-update-causes-access-issues.

Source Summary by GovInfoNow · govinfonow.com/recall/50634-carefusion-pyxis-medstation-es-firmware-update-causes-access-issues · Updated August 18, 2026 · FDA enforcement record: FDA #Z-0962-2026

Cite this page

“CareFusion Pyxis MedStation ES Firmware Update Causes Access Issues.” GovInfoNow, updated August 18, 2026. https://govinfonow.com/recall/50634-carefusion-pyxis-medstation-es-firmware-update-causes-access-issues. Based on FDA recall #Z-0962-2026 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-0962-2026%22&limit=1).

The FDA announced on Nov. 20, 2025, that CareFusion 303, Inc. is recalling BD Pyxis MedStation ES devices due to a firmware update causing drawer failures that may delay access to medications. The recall affects approximately 53,669 units distributed worldwide.

How to tell if you have it

  • BD Pyxis MedStation ES, REF: 323
  • BD Pyxis MedStation ES 7 Drawer Auxiliary, REF: 324
  • BD Pyxis MedStation ES Tower, REF: 352
  • BD Pyxis Pro 7-Drawer Auxiliary, REF: 1149-00
  • BD Pyxis Pro 7- Drawer Auxiliary with Secure Tower, REF: 1152-00
  • BD Pyxis Pro MedStation Main, REF: 1155-00
  • BD Pyxis CII Safe ES, REF: 1116-00
  • Firmware Version: 1.48

The hazard

The FDA said the Automated Dispensing Cabinets received a Half Height CUBIE drawer firmware update that caused a Cubie Insert event, prompting software to generate a duplicate address. This error causes the drawer to fail, which may lead to an inability or delay in accessing stored items or patient-specific medications.

Context

GovInfoNow's records show CareFusion 303, Inc. has 64 other recalls on record since 2017-06-12. Other recent recalls of similar products include BD Pyxis MedStation ES REF 323 Medication Cabinet Recall (2026-04-30), CareFusion labeling recall (2026-02-11), and BD Pyxis ES Enterprise Server Software Update Issue Recall (2025-12-03). Other recent recalls of similar products include Medtronic Restore CP App Model A71100 Software Issue: Rare Therapy Disruption Risk (2025-11-20), Fresenius Medical Care 5008X CAREsystem Recall: Software Anomalies Risk Treatment Stop (2025-10-25), and GE Medical Systems Portrait Compute V1.2 Software Recall: Patient Monitoring Risk (2026-07-20).

How to tell if you have this one

Check if your device has the model names listed: Pyxis MedStation ES, 7 Drawer Auxiliary, Tower, or Pro models with firmware version 1.48. The unique identifiers (REF/UDI-DI) are provided in the recall notice.

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

What to do — step by step

  1. Check Firmware Version

    Verify your device's firmware version by checking the model and unique identifiers listed in the recall notice.

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 - US Nationwide distribution including in the states of CO, IN, OH, TX, KS, FL, GA, NC, CA, HI, IL, NY, MI, VA, AL, LA, NE, KY, OK, AR, TN, WY, NJ, WI, SD, AZ, NV, MO, MA, ID, WV, DE, PA, WA, MT, CT, IA, MD, PR, MN, NM, OR, VT,…” 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: Nov 20, 202512. FDA classified it Class II: Dec 19, 202523. Published in FDA’s Enforcement Report: Dec 31, 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.

✎ GovInfoNow

Questions people ask

Is this recall dangerous?

The recall addresses potential access delays for medications, not immediate safety risks. The danger level is low risk.

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