Skip to content

GLIDEWIRE RG*ES1818SPRecalls & reported problems

Terumo Corporation · GLIDEWIRE GT Guide Wire · Class 2

All models of GLIDEWIRE (30)

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

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

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 04987350734785), received between Mar 31, 2021 and Mar 31, 2021 — classified as 1 malfunction.

The most frequently reported specific device problem is “Material Separation” (1 report).

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.

Most reported problems

Device problems

  • Material Separation1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1

Recent adverse event reports

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

  • MalfunctionMar 31, 2021Material Separation; Material Separation

    THE USER FACILITY REPORTED THAT THE SHAPEABLE TIP OF THE GT WIRE BROKE OFF BEFORE IT WAS USED PRE-TREATMENT. THE WIRE WAS NOT USED ON THE PATIENT. THE PATIENT'S CONDITION WAS GOOD ND THE PROCEDURE OUTCOME WAS GOOD. THERE WAS NO PATIENT INJURY, MEDICAL/SURGICAL INTERVENTION REQUIRED. THERE WERE NO OTHER DEVICES OR EQUIPMENT USED WITH THE REPORTED PRODUCT. ADDITIONAL INFORMATION WAS RECEIVED ON 25MAR2021. THE WIRE WAS BROKEN BEFORE IT WAS EVER USED ON THE PATIENT. THEY USED A NEW WIRE TO CONTINUE THE PROCEDURE. THE PATIENT WAS UNAFFECTED, THE WIRE WAS NOT USED ON PATIENT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 11594682 ↗

Other Wire, guide, catheter devices

All Wire, guide, catheter devices →

Sources and updates

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