Skip to content

SureSigns VSi 863275Recalls & reported problems

Philips Medical Systems Hsg · SureSigns VSi - NBP · Class 2

All models of SureSigns VSi (3)

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

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

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 00884838028364), received between Jun 16, 2021 and Jul 18, 2022 — classified as 2 malfunctions.

The most frequently reported specific device problem is “No Audible Alarm” (1 report).

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. What reports can and can't tell you · How this data works · Data updated Oct 16, 2026.

Most reported problems

Device problems

  • No Audible Alarm1
  • No Audible Prompt/Feedback1

Patient problems

  • No Clinical Signs, Symptoms or Conditions2

Recent adverse event reports

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

  • MalfunctionJul 18, 2022No Audible Prompt/Feedback; No Audible Prompt/Feedback

    THE CUSTOMER REQUESTED A LOUDSPEAKER. ADDITIONAL INFORMATION WAS REQUESTED AS TO WHY A LOUDSPEAKER WAS NEEDED, BUT NO RESPONSE WAS RECEIVED. PATIENT INVOLVEMENT IS UNKNOWN. THERE WAS NO REPORTED PATIENT OR USER IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 15046255 ↗
  • MalfunctionJun 16, 2021No Audible Alarm; No Audible Alarm

    THE CUSTOMER REPORTED THAT THE LOUDSPEAKER IS DEFECTIVE. THE DEVICE WAS NOT IN CLINICAL USE AT THE TIME THE REPORTED ISSUE WAS DISCOVERED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 12008526 ↗

Other COMPUTER, BLOOD-PRESSURE devices

All COMPUTER, BLOOD-PRESSURE devices →

Sources and updates

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