Z-1712-2008

U9 Socket Integrated Circuit ("U9 IC") on the display board of the following Alaris System modules built on...

Name: Z-1712-2008 U9 Socket Integrated Circuit ("U9 IC") on the display board of the following Alaris System modules built on...
Creator: Cardinal Health 303 Inc DBA Alaris Products
Published: 2008-03-05
License: https://open.fda.gov/license/

CareFusion 303, Inc / initiated 2008-03-05 / Terminated / root cause: design

FDA source

Cardinal Health 303 Inc DBA Alaris Products began a recall of U9 Socket Integrated Circuit ("U9 IC") on the display board of the following Alaris System modules built on or before October 4, 2005: (1) Alaris Syringe... on 2008-03-05. The reason FDA records is "A channel error on an affected Alaris System module will stop an active infusion (or monitoring) with an audible and visual alarm. Channel errors due to failure of the U9 Socketed Integrated Circuits (U9 IC) on the...". As of 2026-09-10, the recall status on record is Terminated, and MDM tags the root cause as design.

Recall record

Recall number: Z-1712-2008
Status: Terminated
Initiated: 2008-03-05
Posted: 2008-06-10
Terminated: 2011-09-13
Recalling firm: CareFusion 303, Inc
Product: U9 Socket Integrated Circuit ("U9 IC") on the display board of the following Alaris System modules built on or before October 4, 2005: (1) Alaris Syringe module (Model 8110) (a.k.a. Medley Syringe module) (2) Alaris PCA module (Model 8120) (a.k.a. Medley PCA module), CardinalHealth, San Diego, CA 92130
Product code: FRN Pump, Infusion
Reason for recall: A channel error on an affected Alaris System module will stop an active infusion (or monitoring) with an audible and visual alarm. Channel errors due to failure of the U9 Socketed Integrated Circuits (U9 IC) on the display board of the Alaris Syringe Module ("Syringe module") and Alaris PCA module ("PCA module") for modules manufactured on or before October 4, 2005. The user will be required to re
Root cause tag: design
FDA root cause: Device Design
Action: An Urgent Medical Device Recall Notification letter was sent to consignees on April 10, 2008. Four customer letters were issued. The U19 IC issue affects only the Pump module and the U9 IC issue affects only the Syringe and PCA modules. Therefore there will be one letter for customers affected by all three issues Ul9 IC, U9 IC, and the IUI, one letter for affected Ul9 IC and U9 IC customers, one letter for U19 IC-only customers and one letter for U9 IC-only customers. All mailings were conducted through consignees (distributors as well as direct customers for the affected devices). Distributors will be sent multiple copies of the Recall Notification and Customer Response Cards. The Recall letters all includeRequired Actions sections which give their customers specific information about the issue and what the customers are to do and includes a web site link for each specific problem. Each recall letter also has chart of Cardinal Health contacts support.
Quantity in commerce: 8,286 units
Distribution: Class II Recall - Worldwide Distribution --- USA including states of AR, AZ, CA, CT, CO, FL, GA, IA, ID, IL, IN, KS, KY, LA, MA, ME, MD MI, MN, MO, MS, NC, NE, NH, NJ, NY, OH, OK, OR, PA, SC, SD, TN, TX, UT, VA, VT, WA, WI and WY, Guam and country of Canada. ****CDRH Comments: "Note for District Office to follow-up" The firm has not provided a grand total of devices affected by these problems. It is possible that devices suffering from U19 & U9 problems may also experience IUI problems. This recall has 3 problems with 6 modules. One problem affects only 2 modules, one problem affects 6 modules. For simplicity and expediency, CDRH agrees to keep the file as is, rather than separate into 6 products and have complicated explanations of the problems. 77,515 devices affected by IUI problem. 85,286 devices affected by U19 problem. 8,286 devices affected by U9 problem. ****
Product codes and lots: Pending

Product code FRN

MDM coverage of this record lists here, newest first.

About this record

Sourced from the FDA device recall database and the FDA enforcement reports, both ingested from openFDA. The recall record supplies the product, the reason and the product code; the enforcement report supplies the classification. The two datasets are exported by FDA on different days, and the date above is the older of the two, so nothing on this page is newer than it says.

MDM adds the root cause tag, derived from FDA’s own root cause text, and the cross-links to the product code, the clearances named on the record and MDM coverage. Where a recall has not been joined to an enforcement report, no classification is shown.

Data as of 2026-09-30, the FDA export date for this dataset. Page last changed 2026-09-05. View this recall on fda.gov (opens on fda.gov)