Perseus A500 medical device reports that FDA received
- Name type
- Device brand name, as written on reports
- Generic name
- Anesthesia units
- Device type
- Gas-machine, anesthesia (product code BSZ)
What a report is
A report is not proof that the device was the cause of the event.
FDA says:
Adverse event reports submitted to FDA do not undergo extensive validation or verification. Therefore, a causal relationship cannot be established between product and reactions listed in a report. While a suspected relationship may exist, it is not medically validated and should not be the sole source of information for clinical decision making or other assumptions about the safety or efficacy of a product. Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product.
Source: openFDA, Device Adverse Event Overview, section "Responsible use of the data". The site read the page on . The data have the reports that FDA received through .
FDA also says:
Although MDRs are a valuable source of information, this passive surveillance system has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data. In addition, the incidence or prevalence of an event cannot be determined from this reporting system alone due to potential under-reporting of events and lack of information about frequency of device use.
Source: openFDA, Device Adverse Event Overview. The site read the page on .
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
Do not rely on openFDA to make decisions regarding medical care. While we make every effort to ensure that data is accurate, you should assume all results are unvalidated.
Source: openFDA, Response of the drug event API (meta.disclaimer). The site read the page on .
Not medical advice. This site counts what was reported to FDA. Questions about a medicine or device belong with a pharmacist or clinician.
Reports on file
From May 2015 to August 2026, FDA received 236 medical device reports that name the brand Perseus A500. A brand name is as the reporter or the manufacturer wrote it, so one product can have more than one spelling.
FDA received 41 reports in the 12 months to September 2026 and 20 in the 12 months before. FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.
Of the 3,444,740 device reports that FDA received in the 12 months to September 2026, 41 (under 0.1%) name the brand Perseus A500. Manufacturer reports were 93.2% of the reports that name this brand and 94.9% of all device reports.
The number of people who use the product is not in the data. A count is not a rate. A count of reports is not a count of events or of patients, because one event can have more than one report.
What an MDR is
A medical device report: one submission to FDA about one event. It has the brand name, the generic name, the manufacturer, the product code, the event type and coded problems. Manufacturers and user facilities must send reports.
Data version
openFDA MAUDE release of 23 Oct 2026. Reports received through 30 Sep 2026.
Since the last update
FDA says:
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
The latest update of the FDA data, recorded on , changed no count of this page.
- In April to June 2026, FDA received 15 reports that name the brand Perseus A500.
- In January to March 2026, FDA received 11.
- In April to June 2025, FDA received 3.
April to June 2026 is the latest closed quarter in the data. A closed quarter is a quarter for which the FDA files have most of the reports.
Event types by year
The event type is the classification that the reporter gave. The four terms are FDA's.
FDA says:
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
Reports that name Perseus A500, by event type and by the year in which FDA received them
The table continues to the right.
| Year | Reports | Death | Injury | Malfunction | Other | Not given |
|---|---|---|---|---|---|---|
| 2015 | 4 | 0 | 0 | 4 | 0 | 0 |
| 2016 | 7 | 0 | 2 | 5 | 0 | 0 |
| 2017 | 13 | 0 | 0 | 13 | 0 | 0 |
| 2018 | 13 | 0 | 3 | 10 | 0 | 0 |
| 2019 | 24 | 1 | 1 | 22 | 0 | 0 |
| 2020 | 28 | 0 | 1 | 27 | 0 | 0 |
| 2021 | 21 | 0 | 2 | 19 | 0 | 0 |
| 2022 | 20 | 1 | 1 | 18 | 0 | 0 |
| 2023 | 31 | 1 | 6 | 24 | 0 | 0 |
| 2024 | 16 | 1 | 1 | 14 | 0 | 0 |
| 2025 | 30 | 1 | 2 | 27 | 0 | 0 |
| 2026 | 29 | 0 | 3 | 26 | 0 | 0 |
An event type in a report is not proof that the device was the cause. FDA does not verify the event type.
Malfunction
A malfunction report says that the device did not do what it was made to do. It can be with or without harm to a person.
Reports by month
FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.
Event type and report source
| Event type | Reports | Share | Share as a bar |
|---|---|---|---|
| Death | 5 | 2.1% | |
| Injury | 22 | 9.3% | |
| Malfunction | 209 | 88.6% | |
| Other | 0 | 0% | |
| Not given | 0 | 0% |
| Report source | Reports | Share | Share as a bar |
|---|---|---|---|
| Manufacturer report | 220 | 93.2% | |
| Voluntary report | 1 | 0.4% | |
| User facility report | 0 | 0% | |
| Distributor report | 0 | 0% | |
| Not given | 15 | 6.4% |
Each share is of the 236 reports that name this brand, not of the devices in use.
Device problems coded
| Device problem (FDA code) | Reports | Share |
|---|---|---|
| Gas output problem | 121 | 51.3% |
| Failure to deliverthe device did not deliver the dose or item | 113 | 47.9% |
| Decrease in pressure | 83 | 35.2% |
| Intermittent communication failure | 71 | 30.1% |
| Circuit failure | 25 | 10.6% |
| Inaccurate delivery | 21 | 8.9% |
| Inappropriate or unexpected reset | 20 | 8.5% |
| Gas/air leak | 15 | 6.4% |
| No pressure | 12 | 5.1% |
| Computer system security problem | 9 | 3.8% |
| Device displays incorrect message | 9 | 3.8% |
| Device operates differently than expectedthe device behaved unexpectedly | 6 | 2.5% |
| Failure to analyze signal | 6 | 2.5% |
| Protective measures problem | 6 | 2.5% |
| Reset problem | 5 | 2.1% |
| Device sensing problem | 4 | 1.7% |
| No display/image | 4 | 1.7% |
| Unexpected shutdown | 4 | 1.7% |
| Activation failure | 3 | 1.3% |
| Complete loss of power | 3 | 1.3% |
These are the device problem codes of FDA, as written on the report. One report can have more than one code. The table leaves out general codes such as "no apparent adverse event".
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Low oxygen saturation | 6 | 2.5% |
| Awareness during anesthesia | 2 | 0.8% |
| Bradycardiaslow heart rate | 2 | 0.8% |
| Cardiac arrestthe heart stopped | 2 | 0.8% |
| Deaththe patient died; cause not stated by this term | 2 | 0.8% |
| Respiratory arrestbreathing stopped | 2 | 0.8% |
| Apnea | 1 | 0.4% |
| Bronchospasmtightening of the airways | 1 | 0.4% |
| Coughcough | 1 | 0.4% |
| Cyanosis | 1 | 0.4% |
| Emotional changes | 1 | 0.4% |
| Hypoxialow oxygen | 1 | 0.4% |
| Pneumothoraxa collapsed lung | 1 | 0.4% |
| Respiratory distressdifficulty breathing | 1 | 0.4% |
Patient problem codes are mainly in reports sent since 2019, and the field is often empty.
Pages near this one
- Narkomed same device type
- Primus same device type
- Kion same device type
- Flow-i C20 same device type
- Flow-I same device type
- Peroxiclear Hydrogen Peroxide Solution next in the A to Z list
- Persona FEMORAL CR IMPACTOR PAD next in the A to Z list
- Permanent Pacemaker Electrode next in the A to Z list
- Persona Tibial Articular Surface Provisional next in the A to Z list
- Permanent Defibrillator Electrodes next in the A to Z list
- Persona Tibial Articular Surface Provisional Shim next in the A to Z list
- Permanent Cautery Spatula Instrument next in the A to Z list
These links are for navigation. No count selected them. The page of the device type lists each brand name with product code BSZ.
Official pages
- Medical Device Reporting (MDR): How to Report Medical Device ProblemsThe FDA page that tells how to report a problem with a medical device.
- MedWatch Online Voluntary Reporting FormThe online form of FDA for a voluntary report.
- Manufacturer and User Facility Device Experience (MAUDE) DatabaseThe search page of FDA for the device reports.
The site checked these addresses on . The links open in a new tab.
Cite this page
Reported Reactions. Perseus A500: medical device reports that FDA received. https://reportedreactions.com/device/perseus-a500/ Source: U.S. Food and Drug Administration, openFDA Device Adverse Event (MAUDE) files, release of . Reports received through .
Where the data come from
The counts come from the openFDA Device Adverse Event (MAUDE) bulk files, release of 23 Oct 2026. The files have the reports that FDA received through 30 Sep 2026. Brand names, generic names and manufacturer names are as written on the reports. The names of the product codes come from the device classification of FDA.
A report is in the count when a device in it has this brand name, after the site removes differences of punctuation and capital letters. The site does not publish a report narrative, a lot number, a detail of a patient or the identity of a reporter. The record of FDA is the authority. See how the site counts reports, the data sources and the corrections page.
Questions
Do these reports show that Perseus A500 was at fault?
No. FDA says:
The submission of an MDR itself does not necessarily demonstrate that the device caused or contributed to the adverse outcome or event.
Source: FDA Center for Devices and Radiological Health, About Manufacturer and User Facility Device Experience (MAUDE) Database. Content current as of . The site read the page on .
Confirming whether a device actually caused a specific event can be difficult based solely on information provided in a given report.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
What event types do the reports record?
Death (5), injury (22) and malfunction (209). The event type is the classification that the reporter gave: death, injury, malfunction or other. FDA does not verify it.
Who sent these reports?
Manufacturer reports (93.2%) and voluntary reports (0.4%). These are the sources of the reports that name this brand.
Some reports come directly from user facilities (like hospitals) or device importers (distributors), while others come directly from manufacturers.
Source: openFDA, Device Adverse Event Overview. The site read the page on .
How does a person report a problem with a medical device?
FDA runs MedWatch, a program that takes voluntary reports about medical devices. The guide on how to report has the links.