Skip to content

Bivona 65SP030Recalls & reported problems

Icu Medical, Inc. · Class 2

Data updated Oct 13, 2026 from official FDA records · Editorial policy

1 open recall names this device. See the recall details and contact the manufacturer or your healthcare provider.

Adverse event reports
1
Deaths reported
0
Injuries reported
0
Recalls naming it
1

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 15021312000283), received between Sep 14, 2022 and Sep 14, 2022 — classified as 1 malfunction.

The most frequently reported specific device problem is “Air/Gas in Device” (1 report).

1 FDA recall record name this device's identifier, 1 still open.

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. How this data works · Data updated Oct 13, 2026.

Recalls naming this device

  1. May 29, 2024Open, Classified

    Smiths Medical has identified that the securement flange of specific lots of the Bivona Neonatal/Pediatric and Adult Tracheostomy products may tear because of a manufacturing defect.

    Z-2605-2024 · Root cause: Under Investigation by firm · FDA record ↗

Most reported problems

Device problems

  • Air/Gas in Device1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1

Recent adverse event reports

The 1 most recent of 1 reports, in the reporter's own words as published by the FDA.

  • MalfunctionSep 14, 2022Air/Gas in Device; Air/Gas in Device

    IT WAS REPORTED THAT THE CUFF ON THE TRACH IS ALREADY INFLATED IN THE BOX. IT IS NOT POSSIBLE TO PULL OUT THE AIR FROM THE CUFF. NO PATIENT INJURY WAS REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 15417805 ↗

Other Tube tracheostomy and tube cuff devices

All Tube tracheostomy and tube cuff devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page