On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting Spacelabs Qube patient monitors experiencing alarm volume problems or configuration issues. Common signs include:
- Alarm sounds too low, too high, or silent
- Alarm tone inconsistent or not matching programmed limits
- Difficulty accessing or adjusting alarm settings
- Alerts not being triggered at expected thresholds
The focus is on verifying external settings and easily accessible controls before considering internal faults.
Step-by-Step Troubleshooting
Check Master Volume and Device Controls
- Verify the master volume setting on the monitor. Some models have physical knobs or menu-based volume settings.
- Confirm that the mute function is not activated.
Why: Simple misadjustments are the most common cause of “silent” alarms.
Inspect Alarm Configuration Settings
- Navigate to the alarm settings menu. Check high/low limits for vital signs.
- Ensure that alarm levels are properly configured for the intended patient population.
Why: Incorrect limits may prevent audible alarms from triggering as expected.
Confirm Patient-Specific Alarm Settings
- Verify that patient profiles do not have customized alarm suppression or reduced volume.
Why: Individual patient configurations can override default alarm behavior.
Check External Connections
- If external speakers or nurse call systems are connected, ensure cables are secure.
- Verify that the external audio device is powered on and functioning.
Why: Loose or disconnected peripherals can cause alarms to fail externally.
Test Alarm with Simulated Event
- Trigger a test alarm using the monitor’s built-in alarm test function.
- Listen for proper volume, tone, and duration.
Why: Confirms whether the issue is with the monitor itself or user settings.
Software / Firmware Verification
- Confirm the monitor is running the latest approved firmware version.
- Note any software-related alarms or error messages.
Why: Firmware bugs can occasionally affect alarm behavior.
If the Problem Persists
External causes and configuration issues have been ruled out. The device should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or repair by qualified personnel
Knowing when to escalate is proper Clinical Engineering practice.
Clinical Use Tip
Never troubleshoot alarms while the patient is actively relying on them.
- Move the patient to another monitor or ensure backup monitoring is in place before making changes.
- Only perform adjustments in a safe environment.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“User reported that the monitor’s alarms were inaudible or not triggering at set limits.”
Cause
What was observed during troubleshooting.
Example:
“Alarm settings were found muted and patient-specific limits were set incorrectly. External speaker connection confirmed intact.”
Resolution
What action was taken.
Example:
“Master and patient-specific alarm volumes were adjusted. Alarm limits verified. Alarm test successfully triggered audible alerts.”
Helpful Details to Include
- Monitor location and patient type
- Any external speaker or nurse call connections
- Firmware/software version
- Results of alarm test
- Any observed patterns (intermittent silence, only certain alarms affected)
Final Thought
Patient safety relies on audible and timely alarm alerts. Using a logical, stepwise approach avoids unnecessary internal repair and ensures the device functions properly. Proper documentation ensures accurate record-keeping and facilitates future troubleshooting.
That is successful troubleshooting.