ERROR 1
ERROR 1
ERROR 2
ERROR 2
ERROR 2
ERROR 2
ERROR 2
Password and Confirm password must match.
If you have an ACS member number, please enter it here so we can link this account to your membership. (optional)
ERROR 2
ACS values your privacy. By submitting your information, you are gaining access to C&EN and subscribing to our weekly newsletter. We use the information you provide to make your reading experience better, and we will never sell your data to third party members.
FDA and Baxter Healthcare announced on March 5 that they have identified a heparin-like contaminant in lots of finished heparin product associated with adverse reactions to the drug. The adverse reactions include anaphylaxis and hypotension; FDA has linked heparin to 19 deaths in the U.S. since Jan. 1, 2007 (C&EN, Feb. 25, page 8).
Heparin, which is used clinically as a blood thinner, is a glycosaminoglycan consisting of repeating units of variably sulfated disaccharide units. The contaminant is similar to heparin, says Janet Woodcock, acting director of FDA's Center for Drug Evaluation & Research, although FDA is still working to fully identify the compound and does not know its source. Scientists pinpointed the contaminant through nuclear magnetic resonance spectroscopy and capillary electrophoresis.
In tests of heparin active pharmaceutical ingredient (API) from Baxter supplier Scientific Protein Laboratories (SPL), some samples contained as much as 20% contaminant, which was not detected in standard regulatory tests. In particular, the contaminant reacts like heparin in potency assays.
Baxter spokeswoman Deborah Spak says the company has ruled out that it is somehow producing the contaminant in its processing of heparin API into final product. The determination focuses suspicion on upstream operations. Baxter receives heparin API from SPL, which processes crude heparin isolated from pig intestines. Meanwhile, German authorities announced on March 6 a recall of heparin not supplied by SPL.
Join the conversation
Contact the reporter
Submit a Letter to the Editor for publication
Engage with us on X