Saturday, December 15, 2012

Heparin Label Changes Aimed at Reducing Dosing Errors

By , About.com GuideDecember 14, 2012
One of the most commonly used intravenous drugs will soon have a new, potentially lifesaving, look.

By May 1, 2013, every vial of the blood-thinning medication heparin sold in the United States must bear a label clearly showing the drug dose, solution strength and dose per milliliter. Here is an illustration of what pharmacists,pharmacy technicians and other health care providers can expect to see.

The U.S. Food and Drug Administration announced the labeling change for the clot-busting drug on Dec. 6, 2012. All production runs of Heparin Lock Flush Solution, USP and Heparin Sodium Injection, USP are subject to the new requirement.

According to the agency, and following from recommendations of U.S. Pharmacopeia workgroups, the aim is to simplify and reduce the need for complicated calculations of doses of a prescription drug that must be dosed by each individual patient's weight. Some pharmacy calculations will almost surely continue being needed for most heparin orders, but the variables should be easier to find and input.

Heparin is most often used to break up clots in stroke victims, prevent clotting following surgery and keep clots from forming around continuously open I.V. injection sites. Giving too much heparin can cause internal bleeding.

The Institute for Safe Medication Practices has developed many best practices for preventing errors involving heparin. To those, pharmacy professionals -- especially those practicing in hospitals, long-term care and home health settings -- should add these two from the FDA regarding how to handle vials with pre-2013 labels and vials with post-2013 labels:

  • Consider separating the supplies of "current" and "revised" labeled heparin.
  • Use all of the supplies of the "current" heparin before using products with the "revised" container label.
Source found herehttp://pharmacy.about.com/b/2012/12/14/heparin-label-changes-aimed-at-reducing-dosing-errors.htm

No comments: