Reported Reactions

Devices › Mesh, surgical, polymeric

Device brand name · Surgical mesh

Mesh - Ventralex: medical device reports filed with FDA

2,028 reports name it, 2006–2026. Manufacturer given most often on reports: Davol Sub C R Bard. Product code FTL.

2,028
device reports naming the brand
0% of all MAUDE reports · about 99 a year
98
reports, 12 months to August 2026
35 in the 12 months before
1.2%
classified as malfunction
2.5% across the product code
0.6%
classified as death, as reported
13 reports · not verified by FDA

FDA's MAUDE database holds 2,028 reports that name the brand "Mesh - Ventralex" (surgical mesh), received between January 2006 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.

98 reports arrived in the 12 months to August 2026, up 180% from 35 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%), malfunction (1.2%) and death (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 (81.1%), insufficient device problem information (68.2%) and patient-device incompatibility (26.9%). The patient problems coded most often are pain, injury 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

01020Sep 2021: 14Oct 2021: 8Nov 2021: 9Dec 2021: 52022Jan 2022: 5Feb 2022: 7Mar 2022: 4Apr 2022: 5May 2022: 12Jun 2022: 4Jul 2022: 1Aug 2022: 2Sep 2022: 0Oct 2022: 0Nov 2022: 0Dec 2022: 02023Jan 2023: 1Feb 2023: 0Mar 2023: 0Apr 2023: 1May 2023: 0Jun 2023: 0Jul 2023: 2Aug 2023: 0Sep 2023: 1Oct 2023: 0Nov 2023: 0Dec 2023: 12024Jan 2024: 2Feb 2024: 2Mar 2024: 0Apr 2024: 1May 2024: 3Jun 2024: 0Jul 2024: 1Aug 2024: 1Sep 2024: 0Oct 2024: 0Nov 2024: 0Dec 2024: 12025Jan 2025: 0Feb 2025: 0Mar 2025: 20Apr 2025: 2May 2025: 0Jun 2025: 3Jul 2025: 5Aug 2025: 4Sep 2025: 3Oct 2025: 7Nov 2025: 7Dec 2025: 22026Jan 2026: 5Feb 2026: 10Mar 2026: 7Apr 2026: 16May 2026: 13Jun 2026: 10Jul 2026: 13Aug 2026: 5

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

02404802006: 1220062007: 82008: 82009: 2020092010: 462011: 522012: 5020122013: 232014: 282015: 2520152016: 112017: 322018: 48020182019: 3722020: 4432021: 22920212022: 402023: 62024: 1120242025: 532026: 79

Event type and report source

Event type, as classified on the report

Death0.6%13
Injury98%1,988
Malfunction1.2%25
Other0%1
Not given0%1

Who filed the report

Manufacturer report100%2,028
Voluntary report0%0
User facility report0%0
Distributor report0%0
Not given0%0

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)ReportsShareShare across product code
Defective devicethe device was defective1,64581.1%34.3%
Insufficient device problem information1,38368.2%26.3%
Patient-device incompatibilitythe device did not suit the patient54526.9%7.2%
Patient device interaction problem45522.4%18.9%
Material deformation21610.7%2.3%
Migrationthe device moved from where it was placed1316.5%1.6%
Migration or expulsion of device291.4%4%
Entrapment of device221.1%0.3%
Device appears to trigger rejection190.9%0.2%
Device operates differently than expectedthe device behaved unexpectedly170.8%1.2%
Material separation100.5%0.2%
Breakthe device broke80.4%0.4%
Explanted70.3%1.6%
Detachment of device or device componentpart of the device came off60.3%0.3%
Extrusion60.3%0.8%
Detachment of device component50.2%0.4%
Folded50.2%0.2%
Deformation due to compressive stress40.2%0%
Defective component30.1%0.1%
Device dislodged or dislocated30.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)ReportsShare
Painpain, site not specified1,22660.5%
Injurya physical injury1,22160.2%
Disability1,01550%
Hernia74736.8%
Adhesion(s)63531.3%
Abdominal painstomach or belly pain1597.8%
Obstruction/occlusion1145.6%
Scar tissue1075.3%
Abscessa collection of pus733.6%
Inflammationinflammation673.3%
Fistula522.6%
Purulent discharge351.7%
Fibrosis311.5%
Seromaa collection of fluid under the skin301.5%
Bacterial infectiona bacterial infection271.3%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureMesh - VentralexProduct code FTLAll MAUDE reports
Reports2,028170,30426,136,888
Share of that pool—1.2%0%
Classified as death, per 1,000 reports659
Classified as injury98%96.5%36.2%
Classified as malfunction1.2%2.5%62.3%
Filed by the manufacturer100%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

BrandReportsLatest 12 monthsClassified as death
Bard Flat Mesh8,2991100.5%
PerFix Plug8,2561670.3%
Parietex6,3043201%
Ventralight ST Mesh5,8131060.5%
Obtryx System6,03110%
Ventralex ST5,3651010.4%
Tension Free Vaginal Tape9,35500.1%
Mesh Ventralex4,66150.4%
3DMax3,9711550.1%
ProGrip3,8204120.8%
Proceed Surg Mesh/Multi Lyr3,199290%
Mesh Sofradim - Parietex Composite Mesh2,946161.5%
Advantage? System3,537130%
Ventrio ST2,751510.7%
Symbotex2,7411901.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 Mesh - Ventralex reports

How many FDA reports name Mesh - Ventralex?

2,028 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 98 in the latest 12 months.

What kinds of events are reported?

injury (98%), malfunction (1.2%) and death (0.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

defective device (81.1%), insufficient device problem information (68.2%), patient-device incompatibility (26.9%), patient device interaction problem (22.4%) and material deformation (10.7%). 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 Mesh - Ventralex 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.