Device brand name · Aer equipment
Asp Automatic Endoscope Reprocessor With Printer: medical device reports filed with FDA
319 reports name it, 2008–2011. Manufacturer given most often on reports: Minntech.
- 319
- device reports naming the brand
- 0% of all MAUDE reports · about 18 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 93.7%
- classified as malfunction
- 62.3% across all reports
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
319 medical device reports received by FDA name the brand "Asp Automatic Endoscope Reprocessor With Printer" (aer equipment); the manufacturer given most often on reports is Minntech; received from June 2008 to October 2011. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
0 reports arrived in the 12 months to August 2026, and none 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 (93.7%) and injury (5.6%). Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are fluid/blood leak (45.8%), other (for use when an appropriate device code cannot be identified) (23.8%) and residue after decontamination (9.4%). The patient problems coded most often are no patient involvement, irritation and headache. 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
No report naming Asp Automatic Endoscope Reprocessor With Printer was received in the five years to August 2026; the latest was received in October 2011.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 26,136,888 MAUDE reports. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share |
|---|---|---|
| Fluid/blood leak | 146 | 45.8% |
| Other (for use when an appropriate device code cannot be identified) | 76 | 23.8% |
| Residue after decontamination | 30 | 9.4% |
| Leak/splashthe device leaked | 14 | 4.4% |
| Fumes or vapors | 13 | 4.1% |
| Mechanical problema mechanical problem | 10 | 3.1% |
| Function indicator light(s), failure of | 9 | 2.8% |
| Chemical problem | 5 | 1.6% |
| Connection problema connection problem | 3 | 0.9% |
| Device disinfection or sterilization issue | 3 | 0.9% |
| Device issuea problem with the device | 3 | 0.9% |
| Device reprocessing problem | 3 | 0.9% |
| Ventilation problem in device environment | 3 | 0.9% |
| Contamination /decontamination problem | 2 | 0.6% |
| Contamination | 1 | 0.3% |
| Environmental compatibility problem | 1 | 0.3% |
| Failure to disinfect | 1 | 0.3% |
| Smoking | 1 | 0.3% |
| Sparking | 1 | 0.3% |
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 | 26 | 8.2% |
| Irritationirritation | 7 | 2.2% |
| Headachehead pain | 6 | 1.9% |
| Other (for use when an appropriate patient code cannot be identified) | 5 | 1.6% |
| Burning sensationa burning feeling | 3 | 0.9% |
| Diarrhea | 3 | 0.9% |
| Dizzinesslight-headedness or unsteadiness | 3 | 0.9% |
| Excessive tear production | 3 | 0.9% |
| Fever | 3 | 0.9% |
| Itching sensation | 3 | 0.9% |
| Chillschills or shivering | 2 | 0.6% |
| Tachycardiafast heart rate | 2 | 0.6% |
| Bleeding | 1 | 0.3% |
| Dehydrationdehydration | 1 | 0.3% |
| High blood pressure/ hypertension | 1 | 0.3% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Asp Automatic Endoscope Reprocessor With Printer | All MAUDE reports |
|---|---|---|
| Reports | 319 | 26,136,888 |
| Share of that pool | — | 0% |
| Classified as death, per 1,000 reports | 0 | 9 |
| Classified as injury | 5.6% | 36.2% |
| Classified as malfunction | 93.7% | 62.3% |
| Filed by the manufacturer | 100% | 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 Asp Automatic Endoscope Reprocessor With Printer reports
How many FDA reports name Asp Automatic Endoscope Reprocessor With Printer?
319 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (93.7%) and injury (5.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
fluid/blood leak (45.8%), other (for use when an appropriate device code cannot be identified) (23.8%), residue after decontamination (9.4%), leak/splash (4.4%) and fumes or vapors (4.1%). 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 Asp Automatic Endoscope Reprocessor With Printer 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.