Devices › Analyzer, chemistry (photometric, discrete), for clinical use
Device brand name · Immunoassay analyzer
Advia Centaur Cp: medical device reports filed with FDA
511 reports name it, 2007–2024. Manufacturer given most often on reports: Siemens Healthcare Diagnostics. Product code JJE.
- 511
- device reports naming the brand
- 0% of all MAUDE reports · about 27 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 94.7%
- classified as malfunction
- 95.5% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 511 reports that name the brand "Advia Centaur Cp" (immunoassay analyzer), received between June 2007 and May 2024; the manufacturer given most often on reports is Siemens Healthcare Diagnostics. Spellings of one product vary from report to report.
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 (94.7%), other (4.7%) and injury (0.4%); across all analyzer, chemistry (photometric, discrete), for clinical use reports (product code JJE) death is recorded in 0% and malfunction in 95.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are high test results (25%), incorrect or inadequate test results (20.2%) and mechanical problem (16.2%). The patient problems coded most often are dural tear, missing value reason and therapy/non-surgical treatment, additional. 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 79,280 reports carrying product code JJE. 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 |
|---|---|---|---|
| High test results | 128 | 25% | 27.1% |
| Incorrect or inadequate test results | 103 | 20.2% | 12% |
| Mechanical problema mechanical problem | 83 | 16.2% | 2.4% |
| Low test results | 40 | 7.8% | 24.5% |
| Incorrect, inadequate or imprecise result or readings | 23 | 4.5% | 8.9% |
| False positive result | 16 | 3.1% | 2.6% |
| Device issuea problem with the device | 9 | 1.8% | 0.2% |
| False negative result | 6 | 1.2% | 1.1% |
| Device displays incorrect message | 5 | 1% | 2.8% |
| False device output | 5 | 1% | 0% |
| Device operates differently than expectedthe device behaved unexpectedly | 3 | 0.6% | 0.8% |
| Device handling problem | 2 | 0.4% | 0.1% |
| False reading from device non-compliance | 2 | 0.4% | 0.2% |
| Insufficient device problem information | 2 | 0.4% | 0.3% |
| Leak/splashthe device leaked | 2 | 0.4% | 3.1% |
| Component(s), broken | 1 | 0.2% | 0% |
| Computer software problema software problem | 1 | 0.2% | 0.4% |
| Device operational issue | 1 | 0.2% | 0.1% |
| Difficult or delayed activation | 1 | 0.2% | 0% |
| Display difficult to read | 1 | 0.2% | 0% |
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 |
|---|---|---|
| Dural tear | 1 | 0.2% |
| Missing value reason | 1 | 0.2% |
| Therapy/non-surgical treatment, additional | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Advia Centaur Cp | Product code JJE | All MAUDE reports |
|---|---|---|---|
| Reports | 511 | 79,280 | 26,136,888 |
| Share of that pool | — | 0.6% | 0% |
| Classified as death, per 1,000 reports | 0 | 0 | 9 |
| Classified as injury | 0.4% | 1.5% | 36.2% |
| Classified as malfunction | 94.7% | 95.5% | 62.3% |
| Filed by the manufacturer | 100% | 99.6% | 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 JJE
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Access 2 Immunoassay System | 4,719 | 0 | 0% |
| Unicel Dxi 800 Access Immunoassay System | 3,133 | 0 | 0% |
| cobas 6000 c501 module | 2,732 | 194 | 0.1% |
| COBAS 6000 C (501) Module | 2,169 | 129 | 0% |
| UniCel DxC 600i SYNCHRON Access Clinical System | 2,975 | 13 | 0% |
| Unicel Dxc 800 Synchron System | 2,232 | 0 | 0% |
| Architect I2000sr Analyzer | 1,785 | 0 | 0.1% |
| cobas c 503 analytical unit | 1,415 | 541 | 0% |
| Alinity Ci-Series Level Sensor Bulk Solution | 1,339 | 0 | 0% |
| Alinity c Processing Module | 1,311 | 302 | 0.1% |
| Cobas 8000 C 702 Module | 1,283 | 0 | 0% |
| Cobas E 411 Immunoassay Analyzer | 1,158 | 0 | 0.1% |
| AU5800 Clinical Chemistry Analyzer | 1,151 | 69 | 0% |
| Architect Reaction Vessel | 1,124 | 0 | 0% |
| Dimension Vista 1500 | 1,102 | 4 | 0% |
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 Advia Centaur Cp reports
How many FDA reports name Advia Centaur Cp?
511 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 (94.7%), other (4.7%) and injury (0.4%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
high test results (25%), incorrect or inadequate test results (20.2%), mechanical problem (16.2%), low test results (7.8%) and incorrect, inadequate or imprecise result or readings (4.5%). 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 Advia Centaur Cp 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.