Skip to content

Nexxis ORRecalls & reported problems across all models

Barco NV · 2 models in the FDA device registry

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

1 open recall names at least one Nexxis OR model. Check whether yours is affected in the recall details, and contact the manufacturer or your healthcare provider.

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

We found 2 models of Nexxis OR by Barco NV in the FDA's device registry (GUDID). None of them is named in an adverse event report in our data.

1 FDA recall record name at least one of these models by its device 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. Widely used products collect more reports, so totals can't be used to compare products or estimate failure rates. Only reports that name a model's exact device identifier are counted. What reports can and can't tell you · How this data works

Nexxis OR recalls

FDA recall records that name at least one of these models by its device identifier, newest first. Each recall usually covers specific models or lots, so check the details.

  1. May 9, 2025Open, Classified

    Cathode ray tube display system encoders and decoders have same MAC address; new system setup with two or more affected units can lead to systems not functioning reliably:audio, video and/or control signals might be interrupted or fall away, displays might switch to failover and back multiple times, devices/sources/sinks might not be discovered/available, might lead to delayed/prolonged procedures

    Z-1994-2025 · Root cause: Nonconforming Material/Component · names 2 of these models · Recall details · FDA record ↗

Nexxis OR models

2 models, most reported first. Each model has its own page with its reports, recalls and device details.

Other Barco NV products

All Barco NV devices →

Sources and updates

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