On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Unresponsive buttons, intermittent controls, or error messages caused by power issues, connection faults, or environmental factors.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the stretcher from active patient use before troubleshooting.
- Expected: Patient safely transferred to another device.
Verify Reported Issue
- Attempt to reproduce the problem (unresponsive buttons, incorrect display, intermittent function).
- Expected: Confirmed control panel issue.
- Why it matters: Ensures this is not a user operation error or isolated event.
Check Battery Charge Level
- Observe battery indicator or display status.
- Expected: Adequate battery charge.
- If low → charge fully and retest.
- Why it matters: Low voltage can cause control panel malfunction or erratic behavior.
- If resolved → stop troubleshooting.
Verify Power / Charging Connection
- If plugged in or docked, confirm proper connection and charging indication.
- Expected: Stable power input.
- Why it matters: Inconsistent power can cause control resets or errors.
- If corrected and panel stabilizes → issue resolved.
Perform a Power Cycle
- Turn the stretcher off, wait 10–15 seconds, then power back on.
- Expected: Control panel reboots and functions normally.
- Why it matters: Clears temporary software or communication faults.
- If resolved → stop troubleshooting.
Inspect Control Panel Surface and Buttons
- Check for stuck buttons, fluid ingress, physical damage, or worn overlays.
- Expected: Buttons move freely and respond when pressed.
- Why it matters: Mechanical issues are a common external cause of input failure.
- If damaged or unresponsive → remove from service.
Check for Moisture or Contamination
- Inspect panel for cleaning solution residue or fluid exposure.
- Expected: Dry, clean surface.
- Why it matters: Moisture can cause shorting or false inputs.
- If present → allow to dry completely and retest.
Inspect External Wiring / Harness (If Accessible)
- Check visible connections between control panel and stretcher frame (no disassembly).
- Expected: Secure, undamaged connections.
- Why it matters: Loose or pinched cables can interrupt control signals.
- If issue found → remove from service.
Observe for Error Codes or Indicators
- Note any displayed error messages, blinking lights, or abnormal behavior.
- Expected: No active errors during normal operation.
- Why it matters: Error codes can help identify system-level faults for escalation.
If the Problem Persists
If all external causes have been ruled out, the issue is likely internal (control board, keypad matrix, or wiring fault).
Remove the stretcher from service, label as Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Do not troubleshoot control issues while a patient is on the stretcher. Always transfer the patient first to avoid loss of critical positioning functions.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Control panel unresponsive and intermittently not adjusting stretcher functions."
Cause
What was observed during troubleshooting.
Example:
"Likely control panel failure after ruling out power, battery, and external connection issues."
Resolution
What action was taken.
Example:
"Removed from service and sent for further evaluation and repair."
Helpful Details to Include (If Known)
- Battery level verified
- Power source/dock tested
- Buttons physically inspected
- Presence of moisture or residue checked
- Error messages or indicators noted
- Device power cycled
- Final device status (operational or removed from service)
Final Thought
Control panel issues often appear serious but are frequently caused by simple external factors like low battery, moisture, or stuck buttons. A structured approach ensures patient safety while avoiding unnecessary escalation. When those causes are ruled out, prompt removal from service protects both patients and staff, and clear documentation supports efficient repair.
That is successful troubleshooting.