On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting alarm or alert issues on the Avalon FM30, such as alarms not triggering, incorrect alarm limits, muted alarms, or unexpected alert behavior. These issues are often caused by configuration settings, user adjustments, or profile changes rather than device failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Always confirm the patient is on an alternate monitoring device before making any adjustments.
- Do not troubleshoot alarm functionality on an active patient.
Verify the Reported Issue
- Confirm what the user is experiencing (no alarms, constant alarms, incorrect limits, etc.).
- Observe the monitor in operation if possible.
- This helps determine if the issue is configuration-related versus hardware failure.
Check Alarm Volume and Silence Status
- Ensure the alarm volume is turned up and not muted.
- Look for any “Audio Off” or “Alarm Silence” indicators on the display.
- Temporary silencing may be mistaken for alarm failure.
Review Alarm Limits
- Navigate to alarm settings and verify fetal heart rate (FHR) and maternal heart rate (MHR) limits.
- Compare against hospital policy or standard defaults.
- Incorrect limits can prevent alarms from triggering appropriately.
Check Alarm Mode / Profile Settings
- Verify if the monitor is in a specific mode (e.g., demo mode, standby, or custom profile).
- Ensure the correct patient type/profile is selected.
- Profiles may carry different preset alarm configurations.
Confirm Alarm Activation
- Ensure alarms are enabled for all monitored parameters (FHR, MHR, TOCO).
- Some parameters may have alarms individually disabled.
Inspect for Central Monitoring Overrides
- If connected to a central station, verify whether alarm settings are being controlled remotely.
- Central systems may override local alarm behavior.
Cycle Power to Reset Temporary Settings
- Turn the monitor off, wait 10–15 seconds, and power it back on.
- This can clear temporary configuration glitches.
Check for Recent Configuration Changes
- Ask staff if alarm settings were recently adjusted.
- Reset to default settings if misconfiguration is suspected and appropriate.
Test Alarm Functionality
- Simulate a condition (if safe and appropriate) to verify alarms trigger correctly.
- Confirm both visual and audible alarms function as expected.
Inspect User Interface Responsiveness
- Ensure buttons and touchscreen inputs respond correctly when adjusting alarm settings.
- Unresponsive controls may indicate a deeper issue.
If the Problem Persists
If alarm settings are verified and the issue continues:
- Common external and configuration-related causes have been ruled out
- The issue may be due to internal hardware failure or software malfunction
- The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or further bench evaluation
Knowing when to stop prevents unnecessary risk and ensures patient safety.
Clinical Use Tip
Never troubleshoot alarm functionality while the monitor is actively in use on a patient. Always transfer monitoring to another device before testing or adjusting alarm settings to avoid missed critical events.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Alarms not sounding for abnormal fetal heart rate” or “Alarm limits appear incorrect and not alerting staff.”
Cause
What was observed during troubleshooting.
Example:
Alarm volume found muted and FHR limits set outside normal clinical range.
Resolution
What action was taken.
Example:
Adjusted alarm volume, restored default alarm limits per policy, and verified proper alarm function through testing.
Helpful Details to Include
- Alarm volume level verified
- Alarm silence indicator status
- Alarm limits checked and corrected
- Central monitoring connection status
- Device reset performed
- Alarm test results
- Final device status (returned to service or sent for repair)
Final Thought
Alarm systems are critical for patient safety, and many issues stem from simple configuration errors rather than equipment failure. A structured, logical approach helps quickly identify these problems while minimizing downtime. Proper escalation and clear documentation ensure continued safe operation and accountability.
That is successful troubleshooting.