Devices › Shunt, central nervous system and components
Device brand name · Shunt central nervous system & comps
Hakim Prog Valve Inline Siphonguard: medical device reports filed with FDA
210 reports name it, 2004–2019. Manufacturer given most often on reports: Codman & Shurtleff / Medos. Product code JXG.
- 210
- device reports naming the brand
- 0% of all MAUDE reports · about 9 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 10.5%
- classified as malfunction
- 31.2% across the product code
- 0.5%
- classified as death, as reported
- 1 reports · not verified by FDA
210 medical device reports received by FDA name the brand "Hakim Prog Valve Inline Siphonguard" (shunt central nervous system & comps); the manufacturer given most often on reports is Codman & Shurtleff / Medos; received from February 2004 to March 2019. 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 injury (89%), malfunction (10.5%) and death (0.5%); across all shunt, central nervous system and components reports (product code JXG) death is recorded in 0.9% and malfunction in 31.2%. 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) (25.7%), occlusion within device (10.5%) and partial blockage (7.6%). The patient problems coded most often are other (for use when an appropriate patient code cannot be identified), surgical procedure, additional 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 Hakim Prog Valve Inline Siphonguard was received in the five years to August 2026; the latest was received in March 2019.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 25,520 reports carrying product code JXG. 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) | 54 | 25.7% | 6% |
| Occlusion within devicethe device blocked | 22 | 10.5% | 3.9% |
| Partial blockage | 16 | 7.6% | 2.4% |
| No flow | 15 | 7.1% | 1.7% |
| Programming issue | 15 | 7.1% | 1.9% |
| Explanted | 14 | 6.7% | 10.6% |
| Obstruction of flow | 12 | 5.7% | 5.8% |
| Breakthe device broke | 9 | 4.3% | 8.4% |
| Replace | 9 | 4.3% | 4.2% |
| Program, failure to | 7 | 3.3% | 2.4% |
| Insufficient device problem information | 6 | 2.9% | 5.2% |
| Pressure problem | 6 | 2.9% | 1.3% |
| Restricted flow rate | 6 | 2.9% | 1.4% |
| Device issuea problem with the device | 3 | 1.4% | 1.7% |
| Excess flow or over-infusion | 3 | 1.4% | 0.7% |
| Decrease in pressure | 2 | 1% | 0.3% |
| Disconnection | 2 | 1% | 2% |
| Improper flow or infusion | 2 | 1% | 0.7% |
| Insufficient flow or under infusion | 2 | 1% | 0.7% |
| Leak/splashthe device leaked | 2 | 1% | 5.8% |
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 |
|---|---|---|
| Other (for use when an appropriate patient code cannot be identified) | 52 | 24.8% |
| Surgical procedure, additional | 46 | 21.9% |
| Headachehead pain | 7 | 3.3% |
| Surgical procedure, repeated | 7 | 3.3% |
| Surgical procedure | 6 | 2.9% |
| Hydrocephalus | 4 | 1.9% |
| Failure of implant | 3 | 1.4% |
| Hematomaa collection of blood under the skin or in tissue | 2 | 1% |
| Vomitingbeing sick | 2 | 1% |
| Clotting | 1 | 0.5% |
| Coma | 1 | 0.5% |
| Deaththe patient died; cause not stated by this term | 1 | 0.5% |
| Dementiadementia | 1 | 0.5% |
| Encephalopathy | 1 | 0.5% |
| Falla fall | 1 | 0.5% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Hakim Prog Valve Inline Siphonguard | Product code JXG | All MAUDE reports |
|---|---|---|---|
| Reports | 210 | 25,520 | 26,136,888 |
| Share of that pool | — | 0.8% | 0% |
| Classified as death, per 1,000 reports | 5 | 9 | 9 |
| Classified as injury | 89% | 64% | 36.2% |
| Classified as malfunction | 10.5% | 31.2% | 62.3% |
| Filed by the manufacturer | 100% | 95.1% | 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 JXG
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Hakim Programmable Valve With Prechamber | 948 | 0 | 0.3% |
| Strata | 817 | 163 | 2.2% |
| Hakim Programmable Valve | 693 | 9 | 0.9% |
| Unknown Strata Valve/Shunt | 515 | 0 | 2.3% |
| Hakim Inline Programmable Valve Sg | 343 | 0 | 0% |
| Certas Inlin Vlv Sphn/Unit Cat | 337 | 0 | 0.6% |
| Hakim Valve | 337 | 0 | 0% |
| Certas Inlin Vlv Only W/Sphngd | 327 | 0 | 0.9% |
| NT821731C, EDS 3, GEN ll, NO CATHETER | 326 | 127 | 0% |
| Unknown Valve/Shunt | 225 | 10 | 5.8% |
| Prog Valve Inline W Sg | 222 | 10 | 0% |
| Programmable Valve In-Line W/Siphonguard | 186 | 0 | 0% |
| Progav 2 0 Valve | 183 | 21 | 0% |
| Unknown Catheter | 270 | 26 | 2.2% |
| Strata 2 Adjustable Valve Regular | 174 | 0 | 0.6% |
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 Hakim Prog Valve Inline Siphonguard reports
How many FDA reports name Hakim Prog Valve Inline Siphonguard?
210 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?
injury (89%), malfunction (10.5%) and death (0.5%). "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) (25.7%), occlusion within device (10.5%), partial blockage (7.6%), no flow (7.1%) and programming issue (7.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 Hakim Prog Valve Inline Siphonguard 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.