On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Alarms not sounding, incorrect alarm limits, or delayed/missing alerts due to configuration, volume, or monitoring setup issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If alarms are not functioning, remove the device from active patient monitoring and transfer the patient to a working monitor.
- Expected: Patient is safely monitored on another device
- Why it matters: Alarm failure removes a critical safety layer for patient deterioration detection
Verify Alarm Condition Exists
- Simulate or observe a condition that should trigger an alarm (e.g., low SpO₂ threshold).
- Action:
- Confirm alarm limits are actually being exceeded
- Observe whether any visual or audible alert occurs
- Expected: Alarm should trigger when limits are exceeded
- Why it matters: Confirms whether this is a configuration issue vs no alarm condition present
Check Alarm Volume and Mute Status (Most Common Issue)
- Inspect the alarm audio settings.
- Action:
- Ensure alarm volume is set above minimum
- Check if alarm is muted or temporarily silenced
- Look for mute indicators on screen
- Expected: Audible alarm is enabled and active
- Why it matters: Muted alarms are a frequent cause of “no alarm” complaints
Verify Alarm Limits and Settings
- Review configured alarm thresholds.
- Action:
- Check SpO₂ high/low limits
- Check pulse rate alarm limits
- Compare against facility standards
- Expected: Alarm limits are appropriately set
- Why it matters: Incorrect limits can prevent alarms from triggering
Check Alarm Delay or Averaging Settings
- Evaluate whether alarm delays or averaging are affecting response.
- Action:
- Review averaging time (long averaging delays alarms)
- Check if alarm delay settings are enabled
- Expected: Alarm responds in a timely manner
- Why it matters: Long averaging or delay settings can make alarms appear non-functional
Inspect Sensor and Signal Quality
- Poor signal may prevent valid alarm detection.
- Action:
- Check sensor placement and condition
- Verify proper patient contact
- Look for low perfusion or motion artifact indicators
- Expected: Stable waveform and accurate readings
- Why it matters: Alarms depend on valid physiological data
Check for Alarm Priority Indicators (Visual Only)
- Determine if alarms are visual but not audible.
- Action:
- Observe screen for flashing indicators or messages
- Confirm if only visual alarms are present
- Expected: Both visual and audible alarms should function
- Why it matters: Helps isolate speaker/audio vs configuration issue
Perform a Power Cycle
- Reset the system to clear potential configuration glitches.
- Action:
- Turn off the unit
- Disconnect from power (if applicable)
- Restart the device
- Expected: Alarm functionality returns if caused by temporary fault
- Why it matters: Clears software-related issues
If the Problem Persists
If alarm settings, volume, and sensor conditions have been verified, the issue is likely internal (speaker failure, alarm circuitry, or software fault).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation. Knowing when to stop prevents unnecessary risk and ensures proper escalation.
Clinical Use Tip
Never troubleshoot alarm functionality on an actively monitored patient. Always transfer the patient to a verified working monitor before testing alarm conditions.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nellcor N-600x pulse oximeter alarms not sounding during low SpO₂ events."
Cause
What was observed during troubleshooting.
Example:
"Alarm volume found muted and low SpO₂ limit set outside normal clinical range."
Resolution
What action was taken.
Example:
"Adjusted alarm limits to facility standard and restored alarm volume; verified proper alarm function."
Helpful Details to Include (If Known)
- Alarm volume level verified
- Alarm mute status checked
- Alarm limits reviewed and corrected
- Sensor condition and placement confirmed
- Visual vs audible alarm behavior observed
- Power cycle performed
- Final device status (returned to service or sent for repair)
Final Thought
Alarm failures are often configuration-related rather than hardware issues. Always start with volume, limits, and signal quality before escalating. Patient safety depends on reliable alarm performance, and proper documentation ensures accountability and continuity.
That is successful troubleshooting.