Skip to content

Coated VICRYL VCP945H (UDI 10705031079755)Recalls & reported problems

Ethicon Inc. · Antibacterial Undyed Braided (Polyglactin 910), Synthetic Absorbable Suture · Class 2 · Implant

All models of Coated VICRYL (114)

Data updated Oct 18, 2026 from official FDA records · Editorial policy

Adverse event reports
4
Deaths reported
0
Injuries reported
0
Recalls naming it
0

Summary

The FDA's MAUDE database contains 4 adverse event reports that list this exact device (DI 10705031079755), received between Sep 19, 2025 and Sep 30, 2026 — classified as 4 malfunctions.

The most frequently reported specific device problem is “Break” (3 reports).

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 1 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 1 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 0 reportsMay 2026: 1 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 1 reportsOct 2026: 0 reports2024202520261
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Break3
  • Defective Component1
  • Material Separation1

Patient problems

  • No Clinical Signs, Symptoms or Conditions4

Recent adverse event reports

The 4 most recent of 4 reports, in the reporter's own words as published by the FDA.

  • MalfunctionSep 30, 2026Break

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 50948759 ↗
  • MalfunctionMay 12, 2026Break

    IT WAS REPORTED THAT A PATIENT UNDERWENT A C-SECTION PROCEDURE ON (B)(6) 2026 AND SUTURE WAS USED. WHEN SUTURE WAS USED TO SUTURE FASCIA DURING SURGERY, THE SUTURE WAS BROKEN, AND THE SUTURE WAS CONTINUED AFTER A NEW SUTURE WAS REPLACED. THERE WERE NO PATIENT CONSEQUENCES REPORTED. ADDITIONAL INFORMATION WAS REQUESTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25148368 ↗
  • MalfunctionDec 3, 2025Break; Material Separation; Break; Material Separation

    IT WAS REPORTED THAT A PATIENT UNDERWENT AN UNKNOWN PROCEDURE ON (B)(6) 2025 AND SUTURE WAS USED. THE PATIENT UNDERWENT SURGERY DUE TO "PLACENTAL ABRUPTION". WHEN SUTURING THE INCISION, THE SUTURE BROKE AFTER THE FIRST STITCH, AND THE SUTURE WAS IMMEDIATELY REPLACED. THERE WERE NO PATIENT CONSEQUENCES REPORTED. ADDITIONAL INFORMATION WAS REQUESTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 23706979 ↗
  • MalfunctionSep 19, 2025Defective Component; Defective Component

    IT WAS REPORTED THAT A PATIENT UNDERWENT A C-SECTION PROCEDURE ON (B)(6)2025 AND SUTURE WAS USED. THE PATIENT WAS ADMITTED TO THE HOSPITAL DUE TO "CERVICAL EDEMA AND DYSTOCIA" AND UNDERWENT SURGERY IN THE EARLY MORNING OF THE NEXT DAY. WHEN PREPARING TO SEW THE WOUND FOR THE PATIENT DURING THE SURGERY, THE NURSE OPENED THE OUTER PACKAGING OF THE SUTURE AND FOUND THAT THE THICKNESS OF THE SUTURE WAS DIFFERENT. IMMEDIATELY REPLACED IT WITH A NEW ONE AND THE SURGERY WAS SUCCESSFULLY COMPLETED. THERE WERE NO PATIENT CONSEQUENCES REPORTED. ADDITIONAL INFORMATION WAS REQUESTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 23095899 ↗

Other SUTURE, ABSORBABLE, SYNTHETIC, POLYGLYCOLIC ACID devices

All SUTURE, ABSORBABLE, SYNTHETIC, POLYGLYCOLIC ACID devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page