Skip to content

Public FDA record

Z-2262-2024: BD Alaris System Manager REF: 9601, compatible with BD Alaris PC Units

Recall record Z-2262-2024 for CareFusion 303, Inc.. View source facts, labeled dates, and the original FDA record.

FDA identifier
Z-2262-2024
Company in FDA record
CareFusion 303, Inc.
FDA classification date
Jul 3, 2024
First observed by MedTech Watch
Nov 16, 2026
Latest observed content change
Nov 16, 2026
Recall classification
Class II

Reason stated in the source

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.

Source facts

Action
On August 22, 2024 a subsidiary of Becton, Dickinson and Company (BD) issued a second "Urgent Medical Device Correction" notification via FedEx and E-Mail to new consignees as well as consignees that previously received the 1st recall notification on June 3, 2024. BD asked consignees to take the following actions: 1. If the PCU is connected to the Server, no further actions are necessary, and PCU will function as intended. 2. If the PCU loses connection to the Server, the wireless network indicator icon on the PCU will be in an OFF state (not illuminated), and the PCU can continue to be used. See scenarios below for next steps. a. Non-interoperability customers: The pump programming workflow does not change. If the PCU does not have the expected Data Set, the clinical end user can utilize manual programming as described in the BD Alaris" System with Guardrails" Suite MX User Manual. In addition, a new Data Set can be uploaded to the PCU using a serial cable (per BD Alaris" System Maintenance User Manual v12.5 or BD Alaris" Guardrails" Editor User Manual). b. Interoperability customers: The clinical end user should follow established Interoperability downtime procedures and manually program the infusion as stated in the BD Alaris" System with Guardrails" Suite MX User Manual. Manual programming includes normal access to the BD Alaris Guardrails" dose error reduction software (DERS) and configurations. In addition, the clinical end user can manually document the infusion in the Electronic Medical Record (EMR). 3. Please promptly complete and return the enclosed Customer Response Form within 15 days to acknowledge receipt of this notification and that you understand the information provided in this letter.
Initiated
2024-05-21
Root cause
Under Investigation by firm
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.
Recall number
Z-2262-2024
Recall status
Open, Classified
CDRH record ID
208106
FDA classified
2024-07-03
Recall event number
94718

Source facts and excerpts are reproduced for research. Dates retain their source meanings. “First observed” describes collection, not FDA publication or product launch.

Recall classification is supplied only when the recall number matches an enforcement record. Recall class and device class are different fields. Several recall records may belong to one recall event.

Useful context

Device classifications

FDA dataset:

Last successful check: Nov 22, 2026

Source classifications may change.

510(k) clearances

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset monthly.

Recall records

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset weekly.

Keep this research moving.

Follow ten competitors and ten product codes. Get matching changes in your dashboard and a weekly brief, for $49/month.

Start a 14-day free trial ↗