Skip to content

EndoVive Jejunal Feeding Tube M00566330Recalls & reported problems

Boston Scientific Corporation · 3-Port Through-the-PEG J-Tube Kit · Class 2 · Implant

All models of EndoVive Jejunal Feeding Tube (4)

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 08714729789727), received between May 6, 2019 and May 6, 2019 — classified as 1 malfunction.

The most frequently reported specific device problem is “Migration” (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

  • Migration1

Patient problems

  • No Consequences Or Impact To Patient1

Recent adverse event reports

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

  • MalfunctionMay 6, 2019Migration; Migration

    IT WAS REPORTED TO BOSTON SCIENTIFIC CORPORATION THAT AN ENDOVIVE JEJUNAL FEEDING TUBE WAS PLACED DURING AN ESOPHAGOGASTRODUODENOSCOPY (EGD) PROCEDURE PERFORMED ON (B)(6) 2019. ACCORDING TO THE COMPLAINANT, ONE WEEK AFTER THE PROCEDURE, THE PATIENT CAME INTO THE EMERGENCY ROOM SINCE THE TUBE HAD MIGRATED UP INTO THE PATIENT'S THROAT. REPORTEDLY, THE PHYSICIAN HAD TO REMOVE THE DEVICE. THERE WERE NO PATIENT COMPLICATIONS REPORTED AS A RESULT OF THIS EVENT. THE PATIENT'S CONDITION AT THE CONCLUSION OF THE PROCEDURE WAS REPORTED TO BE FINE.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 8581792 ↗

Other TUBES, GASTROINTESTINAL (AND ACCESSORIES) devices

All TUBES, GASTROINTESTINAL (AND ACCESSORIES) devices →

Sources and updates

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