Skip to content
Use caution Medical device recall · FDA · Published January 24, 2023

CareFusion Alaris PC Unit 8015: Network Failure Risk in Infusion Systems

CareFusion recalls Alaris PC Units 8015 with specific software and wireless network cards that may fail to connect, risking infusion data transfer issues. Affected units have IP addresses from x.x.x.224 to x.x.x.255.

🇺🇸 FDA recall #Z-1192-2023Medical 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 Alaris PC Units 8015 that use specific wireless network cards and software versions. These units may fail to connect to hospital systems, potentially requiring manual infusion programming. This could disrupt critical patient data transfers in medical settings. Read more at govinfonow.com/recall/59015-carefusion-alaris-pc-unit-8015-network-failure-risk-in-infusion.

Source Summary by GovInfoNow · govinfonow.com/recall/59015-carefusion-alaris-pc-unit-8015-network-failure-risk-in-infusion · Updated August 19, 2026 · FDA enforcement record: FDA #Z-1192-2023

Cite this page

“CareFusion Alaris PC Unit 8015: Network Failure Risk in Infusion Systems.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/59015-carefusion-alaris-pc-unit-8015-network-failure-risk-in-infusion. Based on FDA recall #Z-1192-2023 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1192-2023%22&limit=1).

The FDA announced on Jan. 24, 2023, that CareFusion 303, Inc. is recalling Alaris PC Unit 8015 devices due to potential wireless network connection failures. The agency stated the recall was voluntarily initiated by the firm.

How to tell if you have it

  • Brand: CareFusion
  • Product: Alaris PC Unit 8015
  • Network cards: 802.11 b/g or 802.11 a/b/g
  • IP addresses: x.x.x.224 to x.x.x.255
  • UDI-DI: 10885403801549, 10885403801532
  • Software versions: 12.1.0, 12.1.2, 12.1.3
  • Quantity: 83,185 units

The hazard

According to the FDA, the affected infusion pump PCs may experience network or wireless connection failures. This could cause an inability to receive new datasets and transfer retrospective analytics data to connected systems. Users with interfaces to electronic medication records may be unable to send or receive data, potentially requiring manual programming of infusions.

Context

GovInfoNow's records show CareFusion 303, Inc. has 64 other recalls on record since 2017-06-12. On 2025-12-03, a recall addressed a software issue that may result in equipment not receiving timely updates of patient or medication information from enterprise systems. Other recent recalls of similar products include BD Pyxis ES Enterprise Server Software Update Issue Recall (2025-12-03) and Fresenius Kabi Ivenix Infusion System Software Recall (2025-11-14).

How to tell if you have this one

Check for Alaris PC Unit 8015 models with software versions 12.1.0, 12.1.2, or 12.1.3 using wireless network cards that support 802.11 b/g or 802.11 a/b/g. Affected units have IP addresses from x.x.x.224 to x.x.x.255.

  • 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 Alaris PC Unit 8015; affected versions are 12.1.0, 12.1.2, or 12.1.3.

  2. Confirm Network Card Type

    Ensure your wireless network card supports 802.11 b/g or 802.11 a/b/g, as these are the affected card types.

  3. Review IP Address Range

    Check if your unit's IP address falls within the range x.x.x.224 to x.x.x.255.

Where it went and when

Where it was distributed

Distributed in 49 states and D.C., and outside the U.S.

Alaska: yesAKMaine: yesMEVermont: yesVTNew Hampshire: yesNHWashington: yesWAIdaho: yesIDMontana: yesMTNorth Dakota: yesNDMinnesota: yesMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: not listedRIMassachusetts: yesMAOregon: yesORNevada: yesNVWyoming: yesWYSouth Dakota: yesSDIowa: yesIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: yesCTCalifornia: yesCAUtah: yesUTColorado: yesCONebraska: yesNEMissouri: yesMOKentucky: yesKYWest Virginia: yesWVVirginia: yesVAMaryland: yesMDDelaware: yesDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

FDA distribution: “US: FL, CA, OR, IL, WI, NJ, AZ, NV, CO, WY, NE, TX, MI, VA, OH, NC, LA, NM, AL, TN, AR, PA, CT, IN, KS, GA, SC, MD, UT, MA, DC, OK, IA, NY, WA, SD, ND, MN, KY, MO, WV, MS, DE, ME, MT, ID, NH, HI, AK, VT OUS: Canada, Qatar, Saudi Arabia,,…” States read from FDA’s own wording; “not listed” means the notice does not name it.

States: 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, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, Wyoming.

Recall timeline

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

1. Firm started the recall: Jan 24, 202312. FDA classified it Class II: Mar 1, 202323. Published in FDA’s Enforcement Report: Mar 8, 202332023
  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-1192-2023 (January 24, 2023) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1192-2023 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