Skip to content
Lower risk Medical device recall · FDA · Published May 8, 2025

CareFusion Medical Software Recall: Delayed Medication Access Risk

CareFusion recalls specific medical software systems that may delay medication access during cabinet upgrades due to software errors after Microsoft patches. Affected users should contact CareFusion for guidance.

🇺🇸 FDA recall #Z-2017-2025Medical deviceCareFusion ›
Take action

Contact the company

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

CareFusion recalls certain medical software systems that could delay medication access if a Microsoft patch is installed after a cabinet upgrade. This risk affects healthcare facilities using these systems and may impact patient care timing. Read more at govinfonow.com/recall/52323-carefusion-medical-software-recall-delayed-medication-access-risk.

Source Summary by GovInfoNow · govinfonow.com/recall/52323-carefusion-medical-software-recall-delayed-medication-access-risk · Updated August 18, 2026 · FDA enforcement record: FDA #Z-2017-2025

Cite this page

“CareFusion Medical Software Recall: Delayed Medication Access Risk.” GovInfoNow, updated August 18, 2026. https://govinfonow.com/recall/52323-carefusion-medical-software-recall-delayed-medication-access-risk. Based on FDA recall #Z-2017-2025 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2017-2025%22&limit=1).

CareFusion 303, Inc. is recalling BD Pyxis supply server and related software products due to a hazard that may delay access to medications and patient care, the FDA said on May 8, 2025.

How to tell if you have it

  • BD Pyxis MedStation ES Tower 10885403512674
  • BD Pyxis Anesthesia Station ES 10885403477836
  • BD Pyxis MedStation ES (Main) 10885403512667
  • BD Pyxis CII Safe ES Desktop PC [1156-00]
  • BD Pyxis SupplyStation Panel PC V11 [1132-00]
  • Dell 640 Server [1128-00]
  • BD Pyxis Enterprise Server 10885403518348, 10885403520341
  • BD Pyxis CIISafe V9.X SGL IM BIO 10885403512520

The hazard

The FDA said the component manager may remain in installed mode during automated dispensing cabinet upgrades, and subsequent Microsoft patches could prevent user access to the dispensing software. This error may lead to delays in accessing medications or supplies and replenishing patient-specific orders, potentially delaying patient care.

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 Fresenius Medical Care 5008X CAREsystem Recall (2025-10-25), GE Medical Systems Portrait Compute V1.2 Software Recall (2026-07-20), and Philips Patient Information Center iX Software Freezes - Recall (2026-07-31).

How to tell if you have this one

Check if your system includes specific model numbers like BD Pyxis MedStation 4000 Main (10885403512629) or BD Pyxis CII Safe ES Desktop PC (1156-00). The recall was distributed from April 2014 to March 2025.

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

What to do — step by step

  1. Check Device List

    Review the unique list of affected devices provided by CareFusion, which includes specific model numbers and serial codes.

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 PR, DE, GU, MO, IA, IL, CA, MD, MA, VA, PA, NY, WA, NJ, AZ, CO, OH, FL, WI, TX, CT, LA, MI, WY, MN, AR, KY, OR, NM, TN, NC, SC, IN, VT, KS, AL, GA, WV, NV, ID, DC, MS, NE,…” 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 55 days after the firm started it.

1. Firm started the recall: May 8, 202512. FDA classified it Class II: Jun 24, 202523. Published in FDA’s Enforcement Report: Jul 2, 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-2017-2025 (May 8, 2025) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2017-2025 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