Coseal Surgical SealantRecalls & reported problems across all models
Baxter Healthcare Corporation · 2 models in the FDA device registry
Data updated Oct 16, 2026 from official FDA records · Editorial policy
1 open recall names at least one Coseal Surgical Sealant model. Check whether yours is affected in the recall details, and contact the manufacturer or your healthcare provider.
- Adverse event reports
- 2
- Deaths reported
- 0
- Injuries reported
- 2
- Recalls
- 1
We found 2 models of Coseal Surgical Sealant by Baxter Healthcare Corporation in the FDA's device registry (GUDID). Together they are named in 2 adverse event reports in the FDA's MAUDE database, received between Apr 9, 2024 and Jul 2, 2024 — classified as 2 injuries.
1 FDA recall record name at least one of these models by its device identifier, 1 still open.
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event. Widely used products collect more reports, so totals can't be used to compare products or estimate failure rates. Only reports that name a model's exact device identifier are counted. What reports can and can't tell you · How this data works
Reports received per month, all models
Coseal Surgical Sealant recalls
FDA recall records that name at least one of these models by its device identifier, newest first. Each recall usually covers specific models or lots, so check the details.
- Dec 6, 2023Open, Classified
Cardiovascular Surgery marketing brochure (US-AS46-220001) that was distributed for the products listed below contains inaccurate content that does not align with some of the products Instructions for Use (IFU) or Prescribing Information (PI).
Z-0657-2024 · Root cause: Under Investigation by firm · names 2 of these models · Recall details · FDA record ↗
Most reported Coseal Surgical Sealant problems
Device problems
- Adverse Event Without Identified Device or Use Problem2
Patient problems
- Cardiac Tamponade2
- Pericardial Effusion1
Coseal Surgical Sealant models
2 models, most reported first. Each model has its own page with its reports, recalls and device details.
- Coseal Surgical Sealant 934071Sealant,Polymerizing1 recall2 reports
- Coseal Surgical Sealant 934070Sealant,Polymerizing1 recall0 reports
Recent Coseal Surgical Sealant adverse event reports
The 2 most recent reports across all models, in the reporter's own words as published by the FDA.
InjuryJul 2, 2024Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
FIVE DAYS PRIOR TO THE RECEIPT OF THIS REPORT, THE PATIENT UNDERWENT A THORACOTOMY (PULMONARY ARTERY BANDING) PROCEDURE WHEREIN COSEAL SURGICAL SEALANT WAS APPLIED. THREE DAYS LATER THE PATIENT DEVELOPED A TWO-STAGE PULSE ARRHYTHMIA UPON AWAKENING. ANALGESIA WAS ADDED AND THE PATIENT WAS MONITORED. CIRCULATION WAS STABLE. TWO DAYS LATER SEDATION WAS TERMINATED AND THE TWO STAGE PLUSE DID NOT REOCCUR. THE FOLLOWING DAY THE PATIENT WAS TRANSFERRED TO A GENERAL MEDICAL UNIT. AN ECHOCARDIOGRAM WAS PERFORMED, AND A SMALL AMOUNT OF PERICARDIAL FLUID WAS FOUND AROUND THE ENTIRE CIRCUMFERENCE OF THE HEART. DIASTOLIC DIMENSION IS LESS THAN 1MM. TWO DAYS AFTER THAT, A FOLLOW UP ECHOCARDIOGRAM WAS PERFORMED, AND A PERICARDIAL EFFUSION WAS OBSERVED AROUND THE ENTIRE HEART. THE DIASTOLIC DIMENSION WAS ABOUT 7 MM, WHICH HAD RAPIDLY INCREASED COMPARED TO THE DAY BEFORE YESTERDAY. EMERGENCY DRAINAGE WAS PERFORMED. A MEDIAN SUBCUTANEOUS INCISION OF ABOUT 4 CM WAS MADE TO REACH THE PERICARDIAL SAC AT THE DIAPHRAGMATIC PLANE, RESULTING IN A CLEAR RED PALE BLOODY PERICARDIAL EFFUSION. THE PERICARDIAL EFFUSION DRAINED APPROXIMATELY 35 ML. SINCE THERE WAS NO PERSISTENT BLEEDING IN THE PERICARDIAL SAC, A
Patient problems: Cardiac Tamponade
MAUDE report 19657698 ↗InjuryApr 9, 2024Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
THE PATIENT UNDERWENT A PULMONARY ARTERY BANDING WHEREIN COSEAL SURGICAL SEALANT WAS APPLIED UTILIZING EASYSPRAY AND COSEAL SPRAY SET. THE PATIENT WAS ADMITTED TO THE PEDIATRIC INTENSIVE CARE UNIT. FOUR DAYS POSTOPERATIVE (POSTOP) AN ECHOCARDIOGRAM WAS PERFORMED, AND NO ABNORMALITIES WERE NOTED. BOTH THE INTRAPERICARDIAL AND MEDIASTINAL DRAINS WERE REMOVED. THE PATIENT WAS TRANSFERRED TO A GENERAL MEDICAL PEDIATRIC UNIT IN ¿STABLE CONDITION.¿ THE FOLLOWING DAY, AT 0100 SERUM EXUDATE WAS OBSERVED ORIGINATING FROM THE WOUND. TWO HOURS LATER, AN ECHOCARDIOGRAPHY SHOWED A SMALL AMOUNT OF PERICARDIAL FLUID ALL AROUND THE WOUND. THERE WAS A ¿POSSIBILITY OF LEAKING FLUID FROM THE SUTURE GAP IN THE WOUND;¿ HOWEVER, THE WOUND EDGE WAS NOT BROKEN OPEN AND WAS TEMPORARILY PROTECTED WITH A DRESSING AND FILM.¿ PREDONINE WAS STARTED AS ¿PERICARDIAL FLUID THERAPY.¿ SEVEN HOURS LATER, AN ECHOCARDIOGRAPHY SHOWED INCREASED PERICARDIAL EFFUSION AROUND THE ENTIRE CIRCUMFERENCE (DIASTOLIC 1.5-2.0 MM, SYSTOLIC 3.5 MM [UP TO 6 MM IN SOME AREAS]). SIX AND HALF HOURS LATER THE ECHOCARDIOGRAPHY WAS REEVALUATED, AND THE DETERIORATION WAS ASSESSED. THE PATIENT WAS DIAGNOSED WITH CARDIAC TAMPONADE DUE TO PERIC
Patient problems: Cardiac Tamponade; Pericardial Effusion
MAUDE report 19071312 ↗
Other Baxter Healthcare Corporation products
- EXACTAMIX28 models · 6,739 reports · 13 recalls
- MiniCap3 models · 3,423 reports · 7 recalls
- Novum IQ3 models · 1,540 reports · 7 recalls
- CLEARLINK/CONTINU-FLO/DUO-VENT3 models · 873 reports · 3 recalls
- CLEARLINK19 models · 710 reports · 4 recalls
- CLEARLINK/CONTINU-FLO8 models · 416 reports · 4 recalls
- CLEARLINK/DUO-VENT5 models · 282 reports · 1 recall
- REPEATER6 models · 189 reports
Sources and updates
- Models: FDA GUDID, file dated Oct 13, 2026. Models are grouped by the brand name the manufacturer registered.
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 16, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page