Devices › Electrosurgical, cutting & coagulation & accessories
Device brand name · Electrosurgical cutting & coagulation & accessories
Force Fx: medical device reports filed with FDA
780 reports name it, 1999–2026. Manufacturer given most often on reports: Covidien Mfg Dc Boulder. Product code GEI.
- 780
- device reports naming the brand
- 0% of all MAUDE reports · about 28 a year
- 22
- reports, 12 months to August 2026
- 36 in the 12 months before
- 85%
- classified as malfunction
- 80.1% across the product code
- 0.4%
- classified as death, as reported
- 3 reports · not verified by FDA
FDA's MAUDE database holds 780 reports that name the brand "Force Fx" (electrosurgical cutting & coagulation & accessories), received between February 1999 and July 2026; the manufacturer given most often on reports is Covidien Mfg Dc Boulder. Spellings of one product vary from report to report.
22 reports arrived in the 12 months to August 2026, down 39% from 36 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are malfunction (85%), injury (11.8%) and other (0.9%); across all electrosurgical, cutting & coagulation & accessories reports (product code GEI) death is recorded in 0.4% and malfunction in 80.1%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are inaccurate delivery (15.3%), self-activation or keying (11.7%) and connection problem (5.6%). The patient problems coded most often are burn(s), no patient involvement and partial thickness (second degree) burn. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 118,290 reports carrying product code GEI. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Inaccurate delivery | 119 | 15.3% | 0.2% |
| Self-activation or keying | 91 | 11.7% | 2.3% |
| Connection problema connection problem | 44 | 5.6% | 0.7% |
| Fire | 43 | 5.5% | 1.8% |
| Device displays incorrect message | 33 | 4.2% | 2.9% |
| Failure to deliver energy | 26 | 3.3% | 1.3% |
| Failure to calibrate | 21 | 2.7% | 0.1% |
| Insufficient device problem information | 19 | 2.4% | 2.8% |
| Arcing | 18 | 2.3% | 0.9% |
| Failure to align | 17 | 2.2% | 0.3% |
| Energy output problem | 16 | 2.1% | 3.6% |
| Breakthe device broke | 12 | 1.5% | 14% |
| Defective alarm | 12 | 1.5% | 0% |
| Electrical shorting | 12 | 1.5% | 0.5% |
| Flare or flash | 11 | 1.4% | 0.2% |
| Inappropriate/inadequate shock/stimulation | 11 | 1.4% | 0.1% |
| Device operates differently than expectedthe device behaved unexpectedly | 9 | 1.2% | 3.9% |
| Device remains activated | 8 | 1% | 1.3% |
| Failure to cut | 8 | 1% | 1.4% |
| Communication or transmission problemthe device could not communicate or transmit | 7 | 0.9% | 1.2% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Burn(s)a burn | 211 | 27.1% |
| No patient involvement | 78 | 10% |
| Partial thickness (second degree) burn | 37 | 4.7% |
| Superficial (first degree) burn | 33 | 4.2% |
| Burn, thermal | 24 | 3.1% |
| Full thickness (third degree) burn | 19 | 2.4% |
| Hemorrhage/blood loss/bleeding | 16 | 2.1% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 14 | 1.8% |
| Electric shockan electric shock | 10 | 1.3% |
| Tissue damage | 7 | 0.9% |
| Skin discoloration | 5 | 0.6% |
| Treatment with medication(s) | 5 | 0.6% |
| Painpain, site not specified | 4 | 0.5% |
| Therapy/non-surgical treatment, additional | 4 | 0.5% |
| Deformity/ disfigurement | 3 | 0.4% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Force Fx | Product code GEI | All MAUDE reports |
|---|---|---|---|
| Reports | 780 | 118,290 | 26,136,888 |
| Share of that pool | — | 0.7% | 0% |
| Classified as death, per 1,000 reports | 4 | 4 | 9 |
| Classified as injury | 11.8% | 16.7% | 36.2% |
| Classified as malfunction | 85% | 80.1% | 62.3% |
| Filed by the manufacturer | 88.5% | 92.4% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code GEI
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| LigaSure | 8,264 | 879 | 0.2% |
| VasoView Hemopro 2 | 6,633 | 686 | 0% |
| THUNDERBEAT 5 mm, 35 cm, Front-actuated Grip Type S | 4,590 | 403 | 0% |
| HF unit "ESG-400" | 2,698 | 664 | 0.1% |
| Valleylab | 2,010 | 353 | 0.3% |
| Vaso View Hemopro | 1,838 | 0 | 0.1% |
| LigaSure Impact | 1,831 | 72 | 0.3% |
| THUNDERBEAT 5 mm, 35 cm, Front-actuated Grip | 1,505 | 38 | 0.3% |
| Thunderbeat 5mm 35cm Front-Actuated Grip | 1,247 | 0 | 0.2% |
| Valleylab Ft10 | 1,203 | 2 | 0.3% |
| Vasoview Hemopro | 1,187 | 0 | 0% |
| Ligasure Advance Pistol Grip | 970 | 0 | 0% |
| Ligasure Atlas Handswitching 37cm | 924 | 0 | 0.2% |
| Edge | 859 | 171 | 0.1% |
| Conmed | 900 | 89 | 0.2% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Force Fx reports
How many FDA reports name Force Fx?
780 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 22 in the latest 12 months.
What kinds of events are reported?
malfunction (85%), injury (11.8%) and other (0.9%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
inaccurate delivery (15.3%), self-activation or keying (11.7%), connection problem (5.6%), fire (5.5%) and device displays incorrect message (4.2%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (88.5%) and voluntary reports (0.8%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Force Fx was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.