Devices › Dialyzer, high permeability with or without sealed dialysate system
Device brand name · Hemodialysis equipment
Phoenix: medical device reports filed with FDA
581 reports name it, 1997–2026. Manufacturer given most often on reports: Gambro Dasco. Product code KDI.
- 581
- device reports naming the brand
- 0% of all MAUDE reports · about 20 a year
- 16
- reports, 12 months to August 2026
- 12 in the 12 months before
- 32.9%
- classified as malfunction
- 64.6% across the product code
- 5.5%
- classified as death, as reported
- 32 reports · not verified by FDA
581 medical device reports received by FDA name the brand "Phoenix" (hemodialysis equipment); the manufacturer given most often on reports is Gambro Dasco; received from January 1997 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
16 reports arrived in the 12 months to August 2026, up 33% from 12 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 injury (40.4%), malfunction (32.9%) and other (19.8%); across all dialyzer, high permeability with or without sealed dialysate system reports (product code KDI) death is recorded in 5.9% and malfunction in 64.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are other (for use when an appropriate device code cannot be identified) (8.6%), normal (8.1%) and fluid/blood leak (7.4%). The patient problems coded most often are therapy/non-surgical treatment, additional, hospitalization required and other (for use when an appropriate patient code cannot be identified). 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 43,764 reports carrying product code KDI. 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 |
|---|---|---|---|
| Other (for use when an appropriate device code cannot be identified) | 50 | 8.6% | 0.3% |
| Normal | 47 | 8.1% | 0.2% |
| Fluid/blood leak | 43 | 7.4% | 31.9% |
| Device alarm system | 36 | 6.2% | 0.8% |
| Alarm, audible | 33 | 5.7% | 2.8% |
| Air leak | 24 | 4.1% | 1% |
| Leak/splashthe device leaked | 24 | 4.1% | 3.8% |
| Replace | 22 | 3.8% | 1.3% |
| Device displays incorrect message | 21 | 3.6% | 1.1% |
| Disconnection | 20 | 3.4% | 0.9% |
| Failure to interrogate | 20 | 3.4% | 0% |
| No device output | 15 | 2.6% | 0% |
| Output, high | 14 | 2.4% | 0.1% |
| Incorrect measurementthe device measured wrongly | 13 | 2.2% | 0.1% |
| Loss of powerthe device lost power | 11 | 1.9% | 0.2% |
| Smoking | 11 | 1.9% | 0.5% |
| Bubble(s) | 10 | 1.7% | 0.4% |
| Conductivity | 10 | 1.7% | 0% |
| Failure to sense | 10 | 1.7% | 0% |
| Inaccurate delivery | 10 | 1.7% | 0.1% |
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 |
|---|---|---|
| Therapy/non-surgical treatment, additional | 72 | 12.4% |
| Hospitalization required | 57 | 9.8% |
| Other (for use when an appropriate patient code cannot be identified) | 52 | 9% |
| Deaththe patient died; cause not stated by this term | 50 | 8.6% |
| Treatment with medication(s) | 46 | 7.9% |
| Blood loss | 41 | 7.1% |
| Therapy/non-surgical treatment, aborted/stopped | 32 | 5.5% |
| Surgical procedure | 31 | 5.3% |
| Blood pressure, low | 21 | 3.6% |
| Breathing difficulties | 18 | 3.1% |
| Hemodialysis | 18 | 3.1% |
| Low blood pressure/ hypotension | 18 | 3.1% |
| Loss of consciousnesspassing out | 17 | 2.9% |
| Nauseafeeling sick | 15 | 2.6% |
| Cardiac arrestthe heart stopped | 13 | 2.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Phoenix | Product code KDI | All MAUDE reports |
|---|---|---|---|
| Reports | 581 | 43,764 | 26,136,888 |
| Share of that pool | — | 1.3% | 0% |
| Classified as death, per 1,000 reports | 55 | 59 | 9 |
| Classified as injury | 40.4% | 27.9% | 36.2% |
| Classified as malfunction | 32.9% | 64.6% | 62.3% |
| Filed by the manufacturer | 53.7% | 94.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 KDI
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| MiniCap | 13,806 | 409 | 1.1% |
| NxStage System One | 3,312 | 120 | 5.7% |
| Optiflux 180nre Dialyzer Finished Assy | 3,373 | 69 | 0.6% |
| Optiflux 160nre Dialyzer Finished Assy | 2,840 | 27 | 0.8% |
| Fresenius 2008k | 1,756 | 0 | 76.8% |
| Prismaflex Sets (St) | 1,364 | 466 | 0.4% |
| 2008T HEMODIALYSIS SYS., with CDX | 1,136 | 31 | 4.8% |
| 2008k2 Hemodialysis Sys Olc/Diasafe Pls | 927 | 3 | 3.9% |
| Prismaflex Sets (M) | 917 | 287 | 0.1% |
| OPTIFLUX F180NRe HF 12/CS 1.7SA EBEAM | 800 | 286 | 0.1% |
| Prismaflex | 555 | 4 | 7.7% |
| OPTIFLUX F160NRe HF 12/CS 1.5SA EBEAM | 466 | 203 | 0% |
| 2008t Hd Sys Cdx W/Bibag Blue Star | 460 | 51 | 2.6% |
| Prismaflex M150 | 443 | 0 | 0.7% |
| Mini-Cap Disconnect W/Pvp-1solution | 456 | 0 | 3.5% |
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 Phoenix reports
How many FDA reports name Phoenix?
581 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 16 in the latest 12 months.
What kinds of events are reported?
injury (40.4%), malfunction (32.9%) and other (19.8%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
other (for use when an appropriate device code cannot be identified) (8.6%), normal (8.1%), fluid/blood leak (7.4%), device alarm system (6.2%) and alarm, audible (5.7%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (53.7%), distributor reports (31.5%) and voluntary reports (1.4%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Phoenix 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.