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

BD Alaris System Manager 9601 Software Issue: Wireless Data Transmission Problems

CareFusion recalls BD Alaris System Manager REF 9601 software versions 12.5.1 due to wireless data transmission issues with compatible BD Alaris PC Units.

🇺🇸 FDA recall #Z-2262-2024Medical 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 BD Alaris System Manager REF 9601 software versions 12.5.1 that may not connect properly to servers, potentially disrupting wireless data transmission. This could affect medical device operations where reliable data flow is critical. Read more at govinfonow.com/recall/55038-bd-alaris-system-manager-9601-software-issue-wireless-data-transmission.

Source Summary by GovInfoNow · govinfonow.com/recall/55038-bd-alaris-system-manager-9601-software-issue-wireless-data-transmission · Updated August 19, 2026 · FDA enforcement record: FDA #Z-2262-2024

Cite this page

“BD Alaris System Manager 9601 Software Issue: Wireless Data Transmission Problems.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/55038-bd-alaris-system-manager-9601-software-issue-wireless-data-transmission. Based on FDA recall #Z-2262-2024 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2262-2024%22&limit=1).

CareFusion 303, Inc. is recalling BD Alaris System Manager REF: 9601 due to a software issue that may prevent the PC unit from connecting to the server, impacting wireless data transmission. The Food and Drug Administration announced this Class II recall on May 21, 2024.

How to tell if you have it

  • BD Alaris System Manager REF: 9601
  • UDI: 10885403960123
  • Software versions 12.5.1

The hazard

Due to a software issue, the PC unit may not connect to the server which could impact wireless data transmission to and from the server.

Context

GovInfoNow's records show CareFusion 303, Inc. has had 64 other recalls on record since June 12, 2017. Other recent recalls of similar products include BD Pyxis Mini Main REF 349 Medication Cabinet (April 30, 2026) and CareFusion labeling issue (Feb. 11, 2026).

How to tell if you have this one

Check for BD Alaris System Manager REF 9601 software version 12.5.1 on compatible BD Alaris PC Units. The unique device identifier (UDI) is 10885403960123.

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

What to do — step by step

  1. Check Software Version

    Verify the software version on your BD Alaris PC Unit to see if it is 12.5.1.

Where it went and when

Where it was distributed

Distributed nationwide; the notice names 43 states.

Alaska: nationwideAKMaine: named in the noticeMEVermont: nationwideVTNew Hampshire: named in the noticeNHWashington: named in the noticeWAIdaho: named in the noticeIDMontana: named in the noticeMTNorth Dakota: nationwideNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: named in the noticeWIMichigan: named in the noticeMINew 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: 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: nationwideWVVirginia: 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: nationwideHITexas: named in the noticeTXFlorida: named in the noticeFLPuerto Rico: named in the noticePR

FDA distribution: “US Nationwide distribution including in the states of AL, AR, AZ, CA, CO, CT DC, DE, FL, GA, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, NE, NH, NJ, NM, NV, NY, OH, OK, OR, PA, PR, SC, SD, TN, TX, UT, VA, WA, WI.” States read from FDA’s own wording; “not listed” means the notice does not name it.

Named in the notice: Alabama, Arizona, Arkansas, California, Colorado, Connecticut, Delaware, District of Columbia, Florida, Georgia, 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, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, South Carolina, South Dakota, Tennessee, Texas, Utah, Virginia, Washington, Wisconsin.

Recall timeline

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

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

What should I do if I have the recalled software?

The recall does not require immediate action; check your software version to see if it is affected.

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