On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting missing network connectivity, failed bed-status reporting, intermittent communication, or absent data caused by power, location, configuration, or external network issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not interrupt essential bed functions, reposition the bed, or perform troubleshooting that could affect patient support while the bed is occupied.
- Notify the responsible clinical staff.
- Confirm the patient is safely positioned.
- Maintain required bed-exit, siderail, brake, and low-position precautions.
- Transfer the patient to another verified bed if the communication problem affects a required safety workflow.
- Do not assume central monitoring or remote bed-status displays accurately reflect the bed’s current condition during a communication failure.
Expected outcome: The patient remains safely supported without dependence on inaccurate or unavailable network information.
If the bed’s local controls, alarms, or therapeutic functions are also malfunctioning, remove it from clinical use and evaluate it separately.
2. Confirm the Exact Communication Failure
Determine what information is not communicating:
- The bed does not appear on the facility network.
- The bed appears offline in the monitoring or asset-management application.
- Bed-exit, brake, siderail, head-angle, or low-bed status is not updating.
- The displayed room or bed assignment is incorrect.
- Communication is intermittent.
- The bed communicates in one room but not another.
- The problem began after the bed was moved, serviced, replaced, or reassigned.
Record any displayed network symbol, communication message, error code, or central-system alert.
Expected outcome: The failure is narrowed to the bed, its location, a specific data type, or the receiving system.
3. Verify the Bed’s Local Operation
Test the bed’s basic functions from its local controls:
- Power indicators operate normally.
- Bed positioning responds correctly.
- Brake and siderail indicators reflect the actual bed condition.
- Bed-exit functions operate locally when tested according to facility policy.
- The touchscreen or caregiver controls are responsive.
- No unrelated system errors are displayed.
The Progressa is a smart ICU bed platform, but network communication should be evaluated separately from its essential local bed functions.
Expected outcome: Local operation is normal, confirming that the reported issue is primarily related to communication.
If local status indicators are also incorrect, stop and escalate for bed control or sensor evaluation.
4. Confirm AC Power and Battery Condition
Verify that:
- The power cord is fully inserted into the bed.
- The plug is secure in a known-good hospital-grade outlet.
- The outlet has power.
- The bed indicates that it is operating from AC power.
- No damaged plug, cord, strain relief, or unusual heat is present.
- The battery is not fully depleted.
If permitted, disconnect and reconnect the AC plug after confirming the patient will remain safe.
Some network components may require the bed to be powered and fully operational before communication resumes.
Expected outcome: The bed has stable power and any temporary power-related communication interruption clears.
If communication returns, verify correct reporting at the receiving system and stop.
5. Allow Time for Reconnection After Power-Up or Movement
If the bed was recently:
- Powered on
- Unplugged
- Transported
- Moved between units
- Returned from repair
- Assigned to a new room
Allow the approved connection period for the bed to rejoin the wireless network and update the receiving application.
Do not repeatedly power-cycle the bed, as this may restart the connection process.
Expected outcome: The bed reconnects and its current location and status populate correctly.
6. Check the Bed’s Physical Location
Determine whether the failure occurs:
- In one patient room only
- Near elevators, imaging equipment, utility spaces, or shielded walls
- At the edge of a wireless coverage area
- Only while the bed is in a hallway or transport route
- After relocation to another floor or building area
Move the unoccupied bed, or safely test it during a controlled service evaluation, in a location where another Progressa bed is known to communicate.
Expected outcome: Communication behavior helps distinguish a bed-specific problem from a wireless coverage or infrastructure problem.
If multiple beds fail in the same area, escalate to the network or clinical systems team rather than replacing bed components.
7. Compare With a Known-Good Bed
Check whether another appropriately configured Progressa bed communicates from the same room or network area.
- If neither bed communicates, suspect wireless coverage, access-point, server, interface, or receiving-system problems.
- If the known-good bed communicates normally, continue troubleshooting the affected bed.
- Do not move an occupied bed solely for testing unless the move is clinically approved.
Expected outcome: The problem is isolated to either the individual bed or the facility infrastructure.
8. Verify Bed Identity and Assignment
Confirm that the identifiers used by the connected system match the physical bed:
- Asset number
- Serial number
- Network or device identifier
- Room and bed assignment
- Facility or unit assignment
- Hostname or equipment record, if visible to Clinical Engineering
Look for duplicate records, retired-device entries, incorrect room assignments, or a recently replaced communication module.
Expected outcome: The physical bed is correctly associated with its network and application record.
If correcting the assignment restores communication, verify several status changes and stop.
9. Inspect Accessible Communication Components
Without opening covers or performing internal disassembly, inspect accessible areas for:
- Loose or damaged external communication accessories
- Missing covers or antennas, when externally visible
- Evidence of liquid intrusion
- Impact damage near the head-end electronics
- Pinched cables
- Damaged connectors
- Signs that an accessory was removed during cleaning or repair
Do not probe internal connectors or remove electronic assemblies unless authorized by the applicable service procedure.
Expected outcome: No visible external damage or disconnected accessory is present.
If damage is found, remove the bed from service and arrange repair.
10. Review Available Network Indicators
If the installed configuration provides network or connection indicators, record:
- Connected, disconnected, or searching status
- Wireless signal indication
- Communication error messages
- Last-connected time
- Software or configuration warnings
- Whether the identifier shown matches the bed
Do not change protected network settings without approved values and coordination with the responsible network team.
Expected outcome: The displayed state identifies whether the bed is failing to join the network or whether data is failing farther downstream.
11. Confirm the Receiving System Is Operational
Check the appropriate central application, middleware, nurse-call interface, remote-management platform, or bed-status dashboard.
Determine whether:
- Other beds are updating normally.
- The affected bed is shown as offline.
- Data is delayed rather than completely absent.
- Only one type of status is missing.
- The server or interface is under maintenance.
- A facility-wide outage has been reported.
Hillrom offers connected-device and remote-management capabilities for supported bed configurations, so a communication problem may involve systems outside the bed itself.
Expected outcome: The receiving system is verified as available, or the issue is referred to the team responsible for that system.
12. Coordinate With the Network or Clinical Systems Team
Provide the responsible team with:
- Bed asset and serial numbers
- Device or network identifier
- Current room
- Time the failure was observed
- Whether the bed ever connects
- Results from a known-good-room test
- Whether other beds are affected
- Relevant screenshots or error messages
Request confirmation that the bed is:
- Authorized on the wireless network
- Associated with an access point
- Receiving the correct network configuration
- Reaching the required server or interface
- Properly enrolled in the applicable management system
Expected outcome: Infrastructure, enrollment, and application-side causes are either corrected or ruled out.
13. Perform an Approved Restart When Safe
Only after confirming patient safety and facility policy:
- Remove the bed from patient use, if necessary.
- Record current settings and displayed errors.
- Perform the manufacturer-approved shutdown or restart process.
- Restore AC power.
- Allow the bed to complete initialization.
- Recheck network and central-system status.
Do not repeatedly cycle power or disconnect internal batteries as a troubleshooting shortcut.
Expected outcome: A temporary software or connection state clears and normal communication returns.
If communication returns, verify multiple bed-status changes before returning the bed to service.
14. Verify Communication With a Functional Test
Before closing the work order, confirm that the receiving system correctly reports several safe, controlled status changes, as supported by the installed configuration:
- Brake applied or released
- Bed raised or lowered
- Siderail position
- Head-of-bed angle
- Bed-exit monitoring state
- Room or bed assignment
Return each feature to the clinically appropriate condition after testing.
Expected outcome: Local bed status and remote system status agree without unusual delay.
If all tested data updates correctly, return the bed to service and stop.
If the Problem Persists
If power, location, assignments, accessible components, wireless coverage, and receiving systems have been checked, the common external causes have been ruled out.
The failure may involve an internal communication module, antenna, wiring harness, controller, software configuration, or another protected component.
The bed should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or manufacturer-authorized repair
- Escalated to the network or clinical systems team when infrastructure remains suspect
Do not leave a bed in service when required safety information cannot be communicated reliably.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
Never troubleshoot on an active patient. Move the patient to a backup device first and maintain therapy continuity.
Never rely on a remote dashboard as the only confirmation of brake, siderail, low-bed, or bed-exit status. Verify safety conditions directly at the bed before patient use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Hillrom Progressa bed appeared offline and its brake, siderail, and bed-exit status were not updating at the central display."
Cause
What was observed during troubleshooting.
Example:
"Bed functions operated normally, but the device failed to communicate in multiple known-good wireless locations while other Progressa beds remained online."
Resolution
What action was taken.
Example:
"Removed the bed from service, labeled it Out of Service, documented its network identifier and error behavior, and sent it for communication-module evaluation."
Helpful Details to Include (If Known)
- AC outlet tested
- Power cord and plug inspected
- Bed battery condition checked
- Exact communication message recorded
- Network indicator status documented
- Asset and serial numbers confirmed
- Device or network identifier confirmed
- Room assignment verified
- Known-good location tested
- Known-good bed compared
- Other affected beds identified
- Receiving application checked
- Network or clinical systems team contacted
- Visible damage or liquid intrusion noted
- Approved restart performed
- Final communication test completed
- Alarm behavior documented
- Accessories swapped or inspected
- Power behavior documented
- Environmental factors documented
- Indicator lights documented
- Final device status documented
Final Thought
Safe troubleshooting separates local bed operation from network communication, rules out power and infrastructure causes logically, and escalates suspected internal failures appropriately. Complete documentation helps Clinical Engineering, IT, and clinical systems teams resolve the issue efficiently.
That is successful troubleshooting.