Skip to content

VersaCare® Med Surg Bed P3201KRecalls & reported problems

Hill-Rom, Inc. · Hospital Bed · Class 2

All models of VersaCare Med Surg Bed (2)

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

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

Summary

The FDA's MAUDE database contains 7 adverse event reports that list this exact device (DI 00887761000889), received between Oct 15, 2024 and Jul 21, 2026 — classified as 7 malfunctions.

The most frequently reported specific device problem is “Unintended Movement” (5 reports).

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 18, 2026.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 2 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 0 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 2 reportsMay 2026: 1 reportsJun 2026: 0 reportsJul 2026: 2 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520262
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Unintended Movement5
  • Material Split, Cut or Torn1
  • Sparking1

Patient problems

  • No Clinical Signs, Symptoms or Conditions7

Recent adverse event reports

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

  • MalfunctionJul 21, 2026Unintended Movement

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25884903 ↗
  • MalfunctionJul 21, 2026Unintended Movement

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25884836 ↗
  • MalfunctionMay 27, 2026Unintended Movement

    BAXTER RECEIVED A REPORT THAT VERSACARE FRAME HAD BRAKES NOT HOLDING. THERE WAS NO PATIENT/USER INJURY, MEDICAL INTERVENTION, SYMPTOM, OR ADVERSE EVENT REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25311547 ↗
  • MalfunctionApr 16, 2026Unintended Movement

    IT WAS FOUND THAT THE DEVICE HAD UNRELIABLE BRAKE HOLDING CAPACITY. THERE WAS NO PATIENT/USER INJURY, MEDICAL INTERVENTION, SYMPTOM, OR ADVERSE EVENT REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24897450 ↗
  • MalfunctionApr 15, 2026Unintended Movement

    DURING DEA RESULT IT WAS REPORTED THAT VERSACARE FRAME HAD BRAKES NOT HOLDING WHILE ENGAGED. THIS OCCURRED DURING BAXTER SERVICING./TESTING. THERE WAS NO PATIENT/USER INJURY, MEDICAL INTERVENTION, SYMPTOM, OR ADVERSE EVENT REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24889575 ↗
  • MalfunctionOct 29, 2024Material Split, Cut or Torn; Material Split, Cut or Torn

    BAXTER RECEIVED A REPORT FROM A BAXTER TECHNICIAN STATING THE POWER CORD HAD DAMAGE WITH EXPOSED COPPER WIRES. THE BED WAS LOCATED AT THE ACCOUNT. THERE WAS NO PATIENT/USER INJURY REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 20558488 ↗
  • MalfunctionOct 15, 2024Sparking; Sparking

    IT WAS REPORTED THAT SPARKS ARE COMING FROM THE NEAR SIDE OF THE HEAD CASTER. THE BED WAS LOCATED AT THE ACCOUNT. THERE WAS NO PATIENT/USER INJURY REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 20457493 ↗

Other BED, FLOTATION THERAPY, POWERED devices

All BED, FLOTATION THERAPY, POWERED devices →

Sources and updates

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