On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting Turn off Awareness - Call Service, indicating iBED Awareness is unreliable due to a scale, load-cell, communication, zeroing, or siderail-switch fault. This condition may prevent dependable bed-condition or siderail-status monitoring and must be addressed before relying on the Awareness system for patient care.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
- Do not rely on iBED Awareness indicators or monitoring while this message is active.
- If the bed is occupied or in clinical use, notify clinical staff and provide alternate fall-prevention and patient-monitoring measures according to facility policy before troubleshooting.
- Turn off iBED Awareness as appropriate for service evaluation only after patient safety has been addressed.
Expected outcome: The patient is not dependent on an Awareness system with an active fault condition.
Why it matters: This message indicates that iBED Awareness may not accurately report bed-condition or siderail-status information.
2. Verify the Reported Error and Behavior
- Confirm that the display shows: Turn off Awareness - Call Service.
- Determine whether the message appears during startup, when iBED Awareness is turned on, after changing siderail position, during scale or Bed Exit operation, or intermittently during normal use.
- Confirm whether iBED Awareness is currently enabled.
- Note associated symptoms such as incorrect or missing siderail-status indication, scale errors, Bed Exit-related issues, additional Error Call Service messages, or Awareness monitoring that cannot be armed or maintained.
Expected outcome: The message is reproducible or clearly observed while iBED Awareness is on.
Why it matters: This confirms a system-reported Awareness fault rather than a misunderstanding of normal bed operation.
3. Check Power and Basic Bed Condition
- Confirm the bed is connected to a known-good power source.
- Inspect the power cord, plug, strain relief, and visible connections for damage.
- Inspect the bed for contamination, fluid intrusion, impact damage, pinched cables, or physical interference around the siderails and weighing structure.
- Check that accessories, linens, cords, or nearby equipment are not pulling on, contacting, or interfering with the bed frame or siderails.
Expected outcome: The bed has stable power and no visible external condition contributing to abnormal Awareness operation.
Why it matters: Physical interference, damage, or contamination can contribute to scale or siderail-status faults affecting iBED Awareness.
4. Confirm Siderail Position and Mechanical Operation
- Manually inspect each siderail and confirm that it raises, lowers, and locks securely.
- Observe whether the display or Awareness indicators correctly recognize each siderail position change.
- Inspect visible siderail switch areas, cable routing, and accessible connectors for loose or disconnected wiring, pinched or damaged harnesses, misalignment, contamination, or incomplete latching.
Expected outcome: Each siderail moves and locks correctly, and its status is accurately recognized by the system.
Why it matters: A siderail-switch fault can trigger this message because iBED Awareness can no longer trust siderail status.
5. Check for Scale or Load-Cell-Related Conditions
- Confirm nothing is trapped beneath or against the bed frame.
- Verify cables, linens, equipment, or wall contact are not loading or interfering with the frame.
- Confirm the casters are positioned normally and the bed is stable.
- Inspect visible load-cell or weighing-structure areas for damage or mechanical interference.
- If safe and appropriate for service evaluation, observe whether scale operation or zeroing produces additional errors.
Expected outcome: No external interference or visible mechanical condition is affecting the scale or load-cell system.
Why it matters: Load-cell, zeroing, or scale communication errors can make iBED Awareness unreliable and trigger this message.
6. Review the Error Log
- Access the appropriate service or maintenance error log according to approved procedure.
- Look specifically for 200-level errors involving load cells, scale zeroing, or scale communication faults.
- Look for 300-level errors involving siderail-switch faults affecting iBED Awareness.
- Document the specific underlying error code and affected location or subsystem.
Expected outcome: A related underlying fault is identified, allowing troubleshooting to focus on the actual failed function.
Why it matters: Turn off Awareness - Call Service is a system-level warning; the logged error identifies whether the issue originates from the scale/load-cell system or a siderail-switch circuit.
7. Isolate the Affected Subsystem
- For a siderail-switch fault, inspect the indicated siderail switch assembly, mechanical actuation, visible wiring, and accessible connectors.
- For a load-cell fault, inspect the identified load-cell area for damage, binding, cable problems, or frame interference.
- For a zeroing fault, confirm the bed is stable and free of external contact or load interference before repeating the applicable check.
- For a communication fault, inspect accessible related harnesses and connectors for damage or poor connection.
- Do not perform internal board-level repair or deep disassembly unless authorized and supported by applicable service procedures.
Expected outcome: The condition is narrowed to mechanical interference, visible wiring or connection damage, an affected component, or a device-internal failure requiring further service.
8. Correct External Causes and Verify Operation
- If an external issue is identified, correct it as appropriate, such as removing interference, correcting siderail engagement, or addressing accessible connection or visible cable issues through approved repair practice.
- Clear or acknowledge the fault as permitted by service procedure.
- Re-enable iBED Awareness for functional verification only after the affected condition has been addressed.
- Operate each siderail and verify accurate status recognition.
- Confirm no related scale or Awareness error returns.
- Perform applicable functional checks before returning the bed to use.
Expected outcome: The message no longer appears, iBED Awareness operates normally, and related bed functions respond correctly.
Stop when resolved: If the fault is corrected and all affected functions pass verification, document the repair and return the bed to service according to facility procedure.
If the Problem Persists
If Turn off Awareness - Call Service remains after power checks, physical inspection, siderail checks, scale or load-cell interference checks, and review of the underlying logged fault, external causes have been ruled out. The condition may indicate a failed siderail-switch component, load-cell component, scale communication circuit, or another internal Awareness-related failure.
- Remove the bed from patient use.
- Label the bed Out of Service.
- Send the bed for repair or bench evaluation.
- Keep the bed out of service until iBED Awareness and all affected functions have been verified.
Do not return the bed to clinical use with an unresolved Turn off Awareness - Call Service message.
Clinical Use Tip
Never troubleshoot on an active patient. Do not evaluate iBED Awareness while relying on the same bed for active fall-risk monitoring. Move the patient to a backup bed or provide approved alternate patient-monitoring and fall-prevention measures before troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Stryker S3 hospital bed displayed Turn off Awareness - Call Service while iBED Awareness was enabled. Awareness indicators could not be considered reliable for patient monitoring."
Cause
What was observed during troubleshooting.
Example:
"Confirmed Turn off Awareness - Call Service message while iBED Awareness was enabled. Reviewed the error log for an Awareness-related scale/load-cell or siderail-switch fault and inspected for external interference, visible damage, connector condition, and abnormal siderail operation."
Resolution
What action was taken.
Example:
"Corrected the identified external condition affecting the Awareness subsystem, verified siderail-status recognition and applicable scale function, re-enabled iBED Awareness, and confirmed the message did not return. Bed passed functional verification and was returned to service."
Helpful Details to Include (If Known)
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
The Turn off Awareness - Call Service message should be treated as a patient-safety concern because the bed is reporting that iBED Awareness cannot be trusted. A safe Clinical Engineering approach protects the patient first, confirms the message, identifies the underlying logged fault, rules out external causes, verifies function after correction, and escalates repair when the system remains unreliable. Clear CCR documentation ensures the clinical risk, findings, and final bed status are captured.
That is successful troubleshooting.