Devices › Mesh, surgical, polymeric
Device brand name · Surgical mesh
SepraMesh IP: medical device reports filed with FDA
1,891 reports name it, 2005–2026. Manufacturer given most often on reports: Davol Sub C R Bard. Product code FTL.
- 1,891
- device reports naming the brand
- 0% of all MAUDE reports · about 90 a year
- 43
- reports, 12 months to August 2026
- 31 in the 12 months before
- 0.6%
- classified as malfunction
- 2.5% across the product code
- 0.8%
- classified as death, as reported
- 16 reports · not verified by FDA
FDA's MAUDE database holds 1,891 reports that name the brand "SepraMesh IP" (surgical mesh), received between June 2005 and August 2026; the manufacturer given most often on reports is Davol Sub C R Bard. Spellings of one product vary from report to report.
43 reports arrived in the 12 months to August 2026, up 39% from 31 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 (98.5%), death (0.8%) and malfunction (0.6%); across all mesh, surgical, polymeric reports (product code FTL) death is recorded in 0.5% and malfunction in 2.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are defective device (93%), insufficient device problem information (54.9%) and patient device interaction problem (42.9%). The patient problems coded most often are injury, pain and disability. 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 170,304 reports carrying product code FTL. 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 |
|---|---|---|---|
| Defective devicethe device was defective | 1,759 | 93% | 34.3% |
| Insufficient device problem information | 1,039 | 54.9% | 26.3% |
| Patient device interaction problem | 811 | 42.9% | 18.9% |
| Patient-device incompatibilitythe device did not suit the patient | 328 | 17.3% | 7.2% |
| Migrationthe device moved from where it was placed | 94 | 5% | 1.6% |
| Material deformation | 69 | 3.6% | 2.3% |
| Device appears to trigger rejection | 16 | 0.8% | 0.2% |
| Detachment of device or device componentpart of the device came off | 3 | 0.2% | 0.3% |
| Expiration date error | 3 | 0.2% | 0% |
| Material protrusion/extrusion | 2 | 0.1% | 0.2% |
| Material split, cut or torn | 2 | 0.1% | 0.7% |
| Unsealed device packaging | 2 | 0.1% | 0% |
| Device damaged by another device | 1 | 0.1% | 0% |
| Extrusion | 1 | 0.1% | 0.8% |
| Folded | 1 | 0.1% | 0.2% |
| Material erosion | 1 | 0.1% | 5.4% |
| Material separation | 1 | 0.1% | 0.2% |
| Migration or expulsion of device | 1 | 0.1% | 4% |
| Torn material | 1 | 0.1% | 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 |
|---|---|---|
| Injurya physical injury | 980 | 51.8% |
| Painpain, site not specified | 959 | 50.7% |
| Disability | 675 | 35.7% |
| Adhesion(s) | 430 | 22.7% |
| Hernia | 413 | 21.8% |
| Obstruction/occlusion | 85 | 4.5% |
| Abdominal painstomach or belly pain | 81 | 4.3% |
| Fistula | 73 | 3.9% |
| Scar tissue | 73 | 3.9% |
| Abscessa collection of pus | 68 | 3.6% |
| Seromaa collection of fluid under the skin | 36 | 1.9% |
| Inflammationinflammation | 28 | 1.5% |
| Purulent discharge | 23 | 1.2% |
| Bowel perforation | 20 | 1.1% |
| Erosion | 19 | 1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | SepraMesh IP | Product code FTL | All MAUDE reports |
|---|---|---|---|
| Reports | 1,891 | 170,304 | 26,136,888 |
| Share of that pool | — | 1.1% | 0% |
| Classified as death, per 1,000 reports | 8 | 5 | 9 |
| Classified as injury | 98.5% | 96.5% | 36.2% |
| Classified as malfunction | 0.6% | 2.5% | 62.3% |
| Filed by the manufacturer | 99.9% | 97.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 FTL
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Bard Flat Mesh | 8,299 | 110 | 0.5% |
| PerFix Plug | 8,256 | 167 | 0.3% |
| Parietex | 6,304 | 320 | 1% |
| Ventralight ST Mesh | 5,813 | 106 | 0.5% |
| Obtryx System | 6,031 | 1 | 0% |
| Ventralex ST | 5,365 | 101 | 0.4% |
| Tension Free Vaginal Tape | 9,355 | 0 | 0.1% |
| Mesh Ventralex | 4,661 | 5 | 0.4% |
| 3DMax | 3,971 | 155 | 0.1% |
| ProGrip | 3,820 | 412 | 0.8% |
| Proceed Surg Mesh/Multi Lyr | 3,199 | 29 | 0% |
| Mesh Sofradim - Parietex Composite Mesh | 2,946 | 16 | 1.5% |
| Advantage? System | 3,537 | 13 | 0% |
| Ventrio ST | 2,751 | 51 | 0.7% |
| Symbotex | 2,741 | 190 | 1.2% |
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 SepraMesh IP reports
How many FDA reports name SepraMesh IP?
1,891 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 43 in the latest 12 months.
What kinds of events are reported?
injury (98.5%), death (0.8%) and malfunction (0.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
defective device (93%), insufficient device problem information (54.9%), patient device interaction problem (42.9%), patient-device incompatibility (17.3%) and migration (5%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.9%) and voluntary reports (0.1%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that SepraMesh IP 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.