Skip to content

Genesys HTA SystemRecalls & reported problems across all models

Boston Scientific Corporation · 2 models in the FDA device registry

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

Adverse event reports
37
Deaths reported
0
Injuries reported
4
Recalls
0

We found 2 models of Genesys HTA System by Boston Scientific Corporation in the FDA's device registry (GUDID). Together they are named in 37 adverse event reports in the FDA's MAUDE database, received between Nov 22, 2016 and Nov 11, 2022 — classified as 4 injuries, 33 malfunctions.

The most frequently reported specific device problem is “Device Displays Incorrect Message” (18 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. 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

Most reported Genesys HTA System problems

Device problems

  • Appropriate Device Problem Term/Code Not Available28
  • Device Displays Incorrect Message18
  • Device Alarm System7
  • Adverse Event Without Identified Device or Use Problem3
  • Device Operates Differently Than Expected3
  • Power Problem3
  • Failure to Power Up2
  • Smoking2

Patient problems

  • No Consequences Or Impact To Patient23
  • No Known Impact Or Consequence To Patient8
  • Burn(s)4
  • No Patient Involvement1
  • Superficial (First Degree) Burn1

Genesys HTA System models

2 models, most reported first. Each model has its own page with its reports, recalls and device details.

Recent Genesys HTA System adverse event reports

The 15 most recent reports across all models, in the reporter's own words as published by the FDA.

Other Boston Scientific Corporation products

All Boston Scientific Corporation devices →

Sources and updates

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