Reported Reactions

Devices › Catheter, intravascular, therapeutic, short-term less than 30 days

Device brand name · Peripheral iv catheters

BD Nexiva: medical device reports filed with FDA

372 reports name it, 2010–2026. Manufacturer given most often on reports: Becton Dickinson Infusion Therapy Systems. Product code FOZ.

372
device reports naming the brand
0% of all MAUDE reports · about 23 a year
14
reports, 12 months to August 2026
93 in the 12 months before
94.6%
classified as malfunction
83.5% across the product code
0%
classified as death, as reported
0 reports · not verified by FDA

FDA's MAUDE database holds 372 reports that name the brand "BD Nexiva" (peripheral iv catheters), received between June 2010 and August 2026; the manufacturer given most often on reports is Becton Dickinson Infusion Therapy Systems. Spellings of one product vary from report to report.

14 reports arrived in the 12 months to August 2026, down 85% from 93 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.6%), injury (4%) and other (1.3%); across all catheter, intravascular, therapeutic, short-term less than 30 days reports (product code FOZ) death is recorded in 0.3% and malfunction in 83.5%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are leak/splash (15.3%), fluid/blood leak (14.8%) and material puncture/hole (5.1%). The patient problems coded most often are hemorrhage/blood loss/bleeding, blood loss and extravasation. 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

02549Sep 2021: 1Oct 2021: 0Nov 2021: 0Dec 2021: 12022Jan 2022: 0Feb 2022: 3Mar 2022: 0Apr 2022: 0May 2022: 0Jun 2022: 0Jul 2022: 1Aug 2022: 1Sep 2022: 0Oct 2022: 0Nov 2022: 0Dec 2022: 22023Jan 2023: 1Feb 2023: 0Mar 2023: 0Apr 2023: 1May 2023: 1Jun 2023: 1Jul 2023: 0Aug 2023: 1Sep 2023: 4Oct 2023: 1Nov 2023: 49Dec 2023: 222024Jan 2024: 22Feb 2024: 6Mar 2024: 24Apr 2024: 11May 2024: 10Jun 2024: 7Jul 2024: 10Aug 2024: 8Sep 2024: 14Oct 2024: 10Nov 2024: 13Dec 2024: 92025Jan 2025: 15Feb 2025: 9Mar 2025: 3Apr 2025: 7May 2025: 5Jun 2025: 2Jul 2025: 2Aug 2025: 4Sep 2025: 2Oct 2025: 1Nov 2025: 1Dec 2025: 52026Jan 2026: 1Feb 2026: 0Mar 2026: 0Apr 2026: 0May 2026: 1Jun 2026: 0Jul 2026: 2Aug 2026: 1

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

0721442010: 320102012: 52013: 1320132014: 72016: 620162017: 82018: 620182019: 242021: 720212022: 72023: 8120232024: 1442025: 5620252026: 5

Event type and report source

Event type, as classified on the report

Death0%0
Injury4%15
Malfunction94.6%352
Other1.3%5
Not given0%0

Who filed the report

Manufacturer report67.7%252
Voluntary report5.4%20
User facility report0%0
Distributor report0%0
Not given26.9%100

Grey bar: all 49,301 reports carrying product code FOZ. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Leak/splashthe device leaked5715.3%21.4%
Fluid/blood leak5514.8%6.7%
Material puncture/hole195.1%2.3%
Breakthe device broke174.6%10.9%
Defective component154%2.6%
Material separation143.8%4.2%
Difficult or delayed separation123.2%0.2%
Separation failure102.7%0.2%
Device contamination with chemical or other material82.2%5.9%
Separation problem61.6%0.2%
Crackthe device cracked51.3%2.1%
Device misassembled during manufacturing /shipping51.3%0%
Detachment of device or device componentpart of the device came off41.1%1.3%
Difficult or delayed activation41.1%0.6%
Material deformation41.1%2%
Stretched41.1%0.3%
Disconnection30.8%0.7%
Material split, cut or torn30.8%1.5%
Physical resistance/sticking30.8%1%
Retraction problem30.8%9%

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
Hemorrhage/blood loss/bleeding51.3%
Blood loss30.8%
Extravasation30.8%
Swellingswelling30.8%
Abscessa collection of pus20.5%
Appropriate clinical signs, symptoms and conditions term/code not available20.5%
Erythemaskin redness20.5%
Exposure to body fluids20.5%
Needle stick/puncture20.5%
Device embedded in tissue or plaque10.3%
Discomfortdiscomfort10.3%
Failure of implant10.3%
Foreign body embolism10.3%
Hematomaa collection of blood under the skin or in tissue10.3%
Hemolysis10.3%

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

In context

MeasureBD NexivaProduct code FOZAll MAUDE reports
Reports37249,30126,136,888
Share of that pool—0.8%0%
Classified as death, per 1,000 reports039
Classified as injury4%13.1%36.2%
Classified as malfunction94.6%83.5%62.3%
Filed by the manufacturer67.7%89.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 FOZ

BrandReportsLatest 12 monthsClassified as death
Insyte AUTOGUARD1,3141,0500%
BD Insyte Autoguard1,246550%
Introcan Safety1,255450.1%
Bd Insyte Autog Bc69500%
Arrow Cvc Set 3-Lumen 7 Fr X 20 Cm1,1101230.1%
Arrow Cvc Set 2-Lumen 7 Fr X 20 Cm1,4061700.1%
Nexiva3853040%
Mahurkar1,04661.1%
Jelco363340%
Arrow Pi Cvc Kit 3-L 7 Fr X 20 Cm Agb286631%
Arrow Cvc Set 16 Ga X 8 20 Cm55100%
Arrow Cvc Set 3-Lumen 7 Fr X 30 Cm338120%
Bd Nexiva Single Port22400%
Unspecified Bd Catheter25100%
Accu-Chek Tender Infusion Set83900%

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 BD Nexiva reports

How many FDA reports name BD Nexiva?

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

What kinds of events are reported?

malfunction (94.6%), injury (4%) and other (1.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

leak/splash (15.3%), fluid/blood leak (14.8%), material puncture/hole (5.1%), break (4.6%) and defective component (4%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (67.7%) and voluntary reports (5.4%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that BD Nexiva 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.