Device brand name · Forceps ophthalmic
GRIESHABER REVOLUTION DSP Forceps: medical device reports filed with FDA
410 reports name it, 2016–2026. Manufacturer given most often on reports: Alcon Grieshaber. Product code HNR.
- 410
- device reports naming the brand
- 0% of all MAUDE reports · about 40 a year
- 39
- reports, 12 months to August 2026
- 41 in the 12 months before
- 92.7%
- classified as malfunction
- 84.7% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
410 medical device reports received by FDA name the brand "GRIESHABER REVOLUTION DSP Forceps" (forceps ophthalmic); the manufacturer given most often on reports is Alcon Grieshaber; received from May 2016 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
39 reports arrived in the 12 months to August 2026, close to the 41 of 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 (92.7%) and injury (7.3%); across all forceps, ophthalmic reports (product code HNR) death is recorded in 0% and malfunction in 84.7%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are difficult to open or close (64.6%), activation problem (8.5%) and break (4.1%). The patient problems coded most often are no patient involvement, retinal tear and appropriate clinical signs, symptoms and conditions term/code not available. 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 888 reports carrying product code HNR. 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 |
|---|---|---|---|
| Difficult to open or close | 265 | 64.6% | 44.4% |
| Activation problem | 35 | 8.5% | 6.1% |
| Breakthe device broke | 17 | 4.1% | 17.1% |
| Mechanical jam | 13 | 3.2% | 3.3% |
| Physical resistance/sticking | 13 | 3.2% | 2.4% |
| Activation failure | 6 | 1.5% | 1% |
| Device-device incompatibility | 5 | 1.2% | 0.8% |
| Fitting problem | 4 | 1% | 0.7% |
| Mechanical problema mechanical problem | 3 | 0.7% | 0.9% |
| Positioning problem | 3 | 0.7% | 0.3% |
| Defective component | 2 | 0.5% | 0.2% |
| Difficult to open or remove packaging material | 2 | 0.5% | 0.2% |
| Product quality problem | 2 | 0.5% | 0.2% |
| Unintended movement | 2 | 0.5% | 0.2% |
| Contamination | 1 | 0.2% | 0.2% |
| Defective devicethe device was defective | 1 | 0.2% | 0.6% |
| Detachment of device component | 1 | 0.2% | 0.5% |
| Device difficult to setup or prepare | 1 | 0.2% | 0.1% |
| Device dislodged or dislocated | 1 | 0.2% | 0.7% |
| Device fell | 1 | 0.2% | 0.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 |
|---|---|---|
| No patient involvement | 16 | 3.9% |
| Retinal tear | 14 | 3.4% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 12 | 2.9% |
| Retinal detachmentthe retina separated from the back of the eye | 12 | 2.9% |
| Hemorrhage/blood loss/bleeding | 4 | 1% |
| Visual impairmentreduced vision | 3 | 0.7% |
| Vitreous hemorrhage | 3 | 0.7% |
| Irritabilityirritability | 2 | 0.5% |
| Itching sensation | 2 | 0.5% |
| Macular edema | 2 | 0.5% |
| Red eye(s) | 2 | 0.5% |
| Retinal degeneration | 2 | 0.5% |
| Loss of vision | 1 | 0.2% |
| Optical nerve damage | 1 | 0.2% |
| Phototoxicity | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | GRIESHABER REVOLUTION DSP Forceps | Product code HNR | All MAUDE reports |
|---|---|---|---|
| Reports | 410 | 888 | 26,136,888 |
| Share of that pool | — | 46.2% | 0% |
| Classified as death, per 1,000 reports | 0 | 0 | 9 |
| Classified as injury | 7.3% | 14.6% | 36.2% |
| Classified as malfunction | 92.7% | 84.7% | 62.3% |
| Filed by the manufacturer | 100% | 95.9% | 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."
Questions about GRIESHABER REVOLUTION DSP Forceps reports
How many FDA reports name GRIESHABER REVOLUTION DSP Forceps?
410 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 39 in the latest 12 months.
What kinds of events are reported?
malfunction (92.7%) and injury (7.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
difficult to open or close (64.6%), activation problem (8.5%), break (4.1%), mechanical jam (3.2%) and physical resistance/sticking (3.2%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that GRIESHABER REVOLUTION DSP Forceps 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.