Z-0527-2008

Baxter RenalSoft v.2.0 Patient Management Software Suite - HD Module; clinical data management software...

Name: Z-0527-2008 Baxter RenalSoft v.2.0 Patient Management Software Suite - HD Module; clinical data management software...
Creator: Baxter Healthcare Renal Div
Published: 2007-11-14
License: https://open.fda.gov/license/

Baxter Healthcare Renal Div / initiated 2007-11-14 / Terminated / root cause: software

FDA source

Baxter Healthcare Renal Div began a recall of Baxter RenalSoft v.2.0 Patient Management Software Suite - HD Module; clinical data management software; Baxter Healthcare Corporation, McGaw Park, Illinois... on 2007-11-14. The reason FDA records is "Pre-Treatment/Post-Treatment Report errors: 1) The Heparin Bolus Value is displayed on Pre and Post Treatment Reports for patients with "No Heparin" orders (RenalSoft v2.0, Renal Software Suite v.3.0 and v.3.1), and 2)...". As of 2026-09-10, the recall status on record is Terminated, and MDM tags the root cause as software.

Recall record

Recall number: Z-0527-2008
Status: Terminated
Initiated: 2007-11-14
Posted: 2008-01-26
Terminated: 2010-02-03
Recalling firm: Baxter Healthcare Renal Div
Product: Baxter RenalSoft v.2.0 Patient Management Software Suite - HD Module; clinical data management software; Baxter Healthcare Corporation, McGaw Park, Illinois 60085
Product code: KPF System, Dialysate Delivery, Semi-Automatic, Peritoneal
Reason for recall: Pre-Treatment/Post-Treatment Report errors: 1) The Heparin Bolus Value is displayed on Pre and Post Treatment Reports for patients with "No Heparin" orders (RenalSoft v2.0, Renal Software Suite v.3.0 and v.3.1), and 2) Withheld Medications are incorrectly displayed as Administered on the Pre-Treatment report (RenalSoft v.2.0 only).
Root cause tag: software
FDA root cause: Software design
Action: Baxter Healthcare Corporation sent an Urgent Device Correction letter, dated 11/14/07, to all of the affected customers, informing them of the Heparin Bolus and the Withheld Medication issues and provided them with interim mitigation instructions that they should implement while waiting for a software correction. A Baxter representative will contact the customer to schedule the software update when the upgraded software is released. Customers were requested to complete and return the enclosed Customer Reply Form, indicating that they have disseminated the information to their staff, and indicating if they still have RenalSoft software and require an upgrade. Any questions were directed to Baxter Global Technical Services at 1-800-553-6898, option 4. A follow-up letter dated 3/6/08 was sent to the consignees on the same date, informing them that the upgraded RenalSoft Software v.2.0.1 was now available for installation. The consignees were requested to complete and fax back the customer reply form indicating that they received the letter, and were informed that they would be contacted by a Baxter representative to schedule an installation of the software upgrade at no charge.
Quantity in commerce: 25 units
Distribution: Worldwide Distribution-USA including Puerto Rico, and countries of Australia, Austria, Canada, Chile, Denmark, Finland, Greece, Ireland, Italy, Mexico, The Netherlands, New Zealand, Norway, Panama, Portugal, Spain, Sweden and the United Kingdom
Product codes and lots: Version 2.0 - HD Module, Serial Numbers 17023766 to 17026503

Product code KPF

K061515Class IIRenalsoftBaxter Healthcare Corp / cleared 2006-09-11

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)