Skip to content
Lower risk Medical device recall · FDA · Published February 18, 2025

BD Alaris Systems Manager Software Recall: Outdated Programming Requests Risk

CareFusion recalls BD Alaris Systems Manager software versions 12.5.1 and 12.5.2 due to potential outdated automated programming requests for infusion units. Affected units may require updates to prevent safety issues.

🇺🇸 FDA recall #Z-1304-2025Medical deviceBD Alaris ›
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 BD Alaris Systems Manager software versions 12.5.1 and 12.5.2 because outdated programming requests could be sent to progressive care units. This might lead to incorrect medication dosing if not fixed. Read more at govinfonow.com/recall/52806-bd-alaris-systems-manager-software-recall-outdated-programming-requests-risk.

Source Summary by GovInfoNow · govinfonow.com/recall/52806-bd-alaris-systems-manager-software-recall-outdated-programming-requests-risk · Updated August 18, 2026 · FDA enforcement record: FDA #Z-1304-2025

Cite this page

“BD Alaris Systems Manager Software Recall: Outdated Programming Requests Risk.” GovInfoNow, updated August 18, 2026. https://govinfonow.com/recall/52806-bd-alaris-systems-manager-software-recall-outdated-programming-requests-risk. Based on FDA recall #Z-1304-2025 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1304-2025%22&limit=1).

The FDA announced on Feb. 18, 2025, that CareFusion 303, Inc. is recalling BD Alaris Systems Manager REF 9601 Infusion Safety Management Software due to a software issue that may result in outdated automated programming requests being sent to progressive care units.

How to tell if you have it

  • BD Alaris
  • REF 9601 Infusion Safety Management Software
  • Software v12.5.1
  • Software v12.5.2
  • prior versions (4.33, 12.0.1, 12.0.2, 12.1, 12.1.2, 12.3)
  • UDIs: 10885403960123
  • 10885403519666 (10885403960116)

The hazard

According to the FDA, a software issue may result in outdated automated programming requests being sent to the progressive care unit. The recall is classified as Class I.

Context

GovInfoNow's records show CareFusion 303, Inc. has had 64 other recalls since 2017-06-12. Other recent recalls of similar products include Fresenius Medical Care 5008X CAREsystem Recall (2025-10-25), Elekta MOSAIQ Oncology System Software Recall (2026-05-21), and GE Medical Systems Portrait Compute V1.2 Software Recall (2026-07-20).

How to tell if you have this one

Check if your software version is 12.5.1, 12.5.2, or any prior versions listed (4.33, 12.0.1, 12.0.2, 12.1, 12.1.2, 12.3). The unique device identifiers (UDIs) 10885403960123, 10885403519666, and 10885403960116 are also associated with this recall.

  • Brand
    BD Alaris
  • Category
    Medical device
FDA recall event · 2 products

All 2 products in this recall

FDA lists each product line separately under one recall event. Check your product description, lot or code numbers against each row. Every row shares the hazard and remedy on this page.

  • Classification
    Class I
  • Status
    Ongoing
  • Distribution
    US: AZ, CA, DC, FL, GA, IL, IN, MI, MO, NC, NJ, NY, OH, OR, PA, SC, TX, UT, VA, WA, WI OUS: None
Recall numberProduct, codes & lotsQuantity
Z-1304-2025BD Alaris Systems Manager , REF 9601 Infusion Safety Management Software; Software v12.5.1 or v12.5.2, and prior versions (4.33, 12.0.1, 12.0.2, 12.1, 12.1.2, 12.3) UDIs: 10885403960123 10885403519666 (10885403960116)—
Z-1305-2025BD Care Coordination Engine (CCE) Infusion Adapter, Safety Management Software; Software: v1.7.2/UDI: 10885403510472—
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Identify your software version by checking the device settings or documentation. Versions 12.5.1, 12.5.2, or prior versions listed (4.33, 12.0.1, 12.0.2, 12.1, 12.1.2, 12.3) are affected.

  2. Update Software

    Contact CareFusion to get the latest software update to fix the outdated programming issue.

Where it went and when

Where it was distributed

Distributed in 20 states and D.C..

Alaska: not listedAKMaine: not listedMEVermont: not listedVTNew Hampshire: not listedNHWashington: yesWAIdaho: not listedIDMontana: not listedMTNorth Dakota: not listedNDMinnesota: not listedMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: not listedRIMassachusetts: not listedMAOregon: yesORNevada: not listedNVWyoming: not listedWYSouth Dakota: not listedSDIowa: not listedIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: not listedCTCalifornia: yesCAUtah: yesUTColorado: not listedCONebraska: not listedNEMissouri: yesMOKentucky: not listedKYWest Virginia: not listedWVVirginia: yesVAMaryland: not listedMDDelaware: not listedDEArizona: yesAZNew Mexico: not listedNMKansas: not listedKSArkansas: not listedARTennessee: not listedTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: not listedOKLouisiana: not listedLAMississippi: not listedMSAlabama: not listedALGeorgia: yesGAHawaii: not listedHITexas: yesTXFlorida: yesFL

FDA distribution: “US: AZ, CA, DC, FL, GA, IL, IN, MI, MO, NC, NJ, NY, OH, OR, PA, SC, TX, UT, VA, WA, WI OUS: None” States read from FDA’s own wording; “not listed” means the notice does not name it.

States: Arizona, California, District of Columbia, Florida, Georgia, Illinois, Indiana, Michigan, Missouri, New Jersey, New York, North Carolina, Ohio, Oregon, Pennsylvania, South Carolina, Texas, Utah, Virginia, Washington, Wisconsin.

Recall timeline

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

1. Firm started the recall: Feb 18, 202512. FDA classified it Class I: Mar 13, 202523. Published in FDA’s Enforcement Report: Mar 19, 202532025
  1. Firm started the recall
  2. FDA classified it Class I
  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 software dangerous for patients?

The recall is for software versions that may send outdated programming requests, which could lead to incorrect dosing. However, the hazard is not described as causing immediate harm, so it's considered 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-1304-2025 (February 18, 2025) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1304-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