Skip to content
Use caution Medical device recall · FDA · Published February 6, 2025

BD Pyxis Anesthesia Station ES: Sync Errors May Cause Incorrect Medication

CareFusion recalls BD Pyxis Anesthesia Station ES models with specific software versions due to sync errors that could lead to incorrect medication dispensing. Affected units may need software updates to prevent safety issues.

🇺🇸 FDA recall #Z-1375-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 is recalling BD Pyxis Anesthesia Station ES models that have software versions prone to sync errors. This could cause dispensing devices to disconnect from the server, leading to incorrect medication administration or delays in accessing critical drugs. Read more at govinfonow.com/recall/52958-bd-pyxis-anesthesia-station-es-sync-errors-may-cause-incorrect.

Source Summary by GovInfoNow · govinfonow.com/recall/52958-bd-pyxis-anesthesia-station-es-sync-errors-may-cause-incorrect · Updated August 18, 2026 · FDA enforcement record: FDA #Z-1375-2025

Cite this page

“BD Pyxis Anesthesia Station ES: Sync Errors May Cause Incorrect Medication.” GovInfoNow, updated August 18, 2026. https://govinfonow.com/recall/52958-bd-pyxis-anesthesia-station-es-sync-errors-may-cause-incorrect. Based on FDA recall #Z-1375-2025 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1375-2025%22&limit=1).

The FDA announced on Feb. 6, 2025, that CareFusion 303, Inc. is recalling BD Pyxis automated dispensing devices due to a server software error causing sync timeouts. This hazard may lead to incorrect therapy or delays in accessing medication.

How to tell if you have it

  • BD Pyxis Anesthesia Station ES, REF: 327
  • BD Pyxis MedStation ES, REF: 323
  • BD Pyxis MedStation ES Tower, REF: 352
  • BD Pyxis CII Safe ES, REF: 1116-00
  • BD Pyxis CII Safe ES Desktop PC, REF: 1156-00
  • BD Pyxis CII Safe ES Desktop PC, Wired SCNR, REF: 107-254-01
  • BD Pyxis CII Safe ES Desktop PC, W-less SCNR, REF: 107-255-01
  • BD Pyxis Enterprise Server (ES), REF: 1115-00
  • BD Pyxis Enterprise Server software versions: 1.7.4.128, 1.7.4.134, 1.7.4.136, 1.7.4.137, All 1.7.1, All 1.7.2, All 1.7.3

The hazard

According to the FDA, a server software error may cause sync timeouts between the server and automated dispensing devices if syncing large amounts of data takes excessive time. This issue may disconnect the devices from the ES server, preventing them from receiving updated information. Consequently, this may lead to incorrect therapy and delays in accessing medication.

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 Baxter Novum IQ Syringe Pump Recall (2026-08-11), Datex-Ohmeda Aisys CS2 Anesthesia System Recall (2026-07-30), and Medtronic SynchroMed Flex Infusion Software Issue (2026-04-08).

How to tell if you have this one

Check if your BD Pyxis Anesthesia Station ES model has the specific software versions listed: 1.7.4.128, 1.7.4.134, 1.7.4.136, 1.7.4.137, All 1.7.1, All 1.7.2, or All 1.7.3. The affected models include Anesthesia Station ES (REF: 327), MedStation ES (REF: 323), and others as detailed in the recall notice.

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

What to do — step by step

  1. Check Software Version

    Verify your device's software version against the list of affected versions provided in the recall notice.

Where it went and when

Where it was distributed

Distributed nationwide and abroad; the notice names 47 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: nationwideRIMassachusetts: 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: nationwideWVVirginia: named in the noticeVAMaryland: named in the noticeMDDelaware: nationwideDEArizona: 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 KY, OH, NY, MO, NC, PA, FL, TN, CT, LA, MN, VA, MD, CA, TX, NE, IA, OK, MI, PR, SD, IN, ME, KS, IL, NM, WA, AR, HI, MS, GA, WY, WI, VT, AL, NV, NJ, DC, AZ, MT, AK, OR, CO,…” 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, 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, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, Wisconsin, Wyoming.

Recall timeline

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

1. Firm started the recall: Feb 6, 202512. FDA classified it Class II: Mar 17, 202523. Published in FDA’s Enforcement Report: Mar 26, 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-1375-2025 (February 6, 2025) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1375-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.