On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting nuisance alarms caused by alarm limits, patient type, monitoring setup, or configuration mismatch.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the patient is stable and being properly monitored before changing any alarm settings or setup selections.
Expected outcome: Patient condition is verified before assuming the alarm is false.
Why it matters: Alarm limits exist for patient safety. A nuisance alarm may still be warning about a real clinical condition.
If the alarm reflects a true patient condition, stop troubleshooting and notify clinical staff.
Verify the Reported Alarm Behavior
Ask clinical staff what alarm is occurring, how often it occurs, and whether it happens with one patient, one room, one monitor, or multiple setups.
Expected outcome: The complaint is narrowed to alarm settings, patient type, accessory setup, or repeated false alarm behavior.
Why it matters: Nuisance alarms are often caused by setup mismatch rather than device failure.
Confirm the Correct Patient Type or Patient Category
Check whether the monitor or host system is set for the correct patient type, such as adult, pediatric, or neonatal, if applicable.
Expected outcome: The selected patient type matches the patient being monitored.
Why it matters: Patient type can affect default alarm limits, parameter behavior, and expected respiratory values.
If correcting the patient type resolves the nuisance alarm, document the setup correction and stop.
Review Alarm Limits With Clinical Staff
Check the alarm limits for EtCO2, respiration rate, FiCO2, apnea/no-breath time, or any other active CO2-related alarm.
Do not independently choose clinical alarm limits. Confirm with the responsible clinical staff that the limits are appropriate for the patient and care area.
Expected outcome: Alarm limits are appropriate for the patient condition and clinical environment.
Why it matters: Limits set too tight can cause repeated nuisance alarms. Limits set too wide can delay recognition of patient deterioration.
If alarm limit adjustment by clinical staff resolves the issue, document the finding and stop.
Check Whether Defaults Were Changed or Not Restored
Determine whether the monitor was recently used in another department, on another patient population, or for a different care situation.
Expected outcome: Any unusual alarm limit, patient type, or setup configuration is identified.
Why it matters: A monitor moved between areas may retain settings that are not appropriate for the next patient use.
Inspect the CO2 Sampling Setup
Verify the correct sampling line, airway adapter, cannula, water trap, and connection path are being used for the monitoring situation.
Expected outcome: The sampling setup matches the intended patient application and is fully connected.
Why it matters: Incorrect or partially connected accessories can cause erratic CO2 readings, poor waveforms, and unnecessary alarms.
If correcting the accessory setup resolves the nuisance alarms, document the accessory or setup issue and stop.
Check for Sampling Line Kinks, Moisture, or Obstruction
Inspect the sampling line for kinks, pinching, liquid contamination, blockage, or poor routing near the patient or bed.
Expected outcome: The line is clear, dry, routed safely, and not pulling on the patient connection.
Why it matters: Restricted sampling flow can cause unstable EtCO2 readings, delayed breath detection, or false no-breath alarms.
Evaluate the CO2 Waveform and Numeric Values
Observe whether the waveform is stable, intermittent, weak, distorted, or missing. Compare alarm behavior to the displayed EtCO2 and respiration rate values.
Expected outcome: The displayed alarm matches the waveform and numeric trend.
Why it matters: A clean waveform with inappropriate alarm limits points toward setup/configuration. A poor waveform points toward accessory, sampling, or patient-interface issues.
Check for Patient Movement or Poor Cannula Positioning
If used with a nasal/oral cannula, confirm it is positioned correctly and not displaced by talking, movement, blankets, masks, or oxygen delivery equipment.
Expected outcome: The cannula remains properly positioned during normal patient movement.
Why it matters: Poor cannula placement can cause intermittent breath detection and nuisance respiratory alarms.
Confirm the Monitor Is Connected to the Correct Host or Display System
If the Philips NM3 is being used with a host monitor or central station, confirm the module is seated properly and communicating correctly.
Expected outcome: The CO2 module data displays consistently without intermittent dropouts.
Why it matters: Communication or module seating issues can appear as nuisance alarms or intermittent parameter loss.
Compare With a Known Good Setup
If available, test the NM3 with a known good sampling line, known good host connection, and appropriate test setup or simulator.
Expected outcome: The module performs normally with known good external accessories and setup.
Why it matters: This helps separate a setup/accessory issue from a possible module fault.
Check for Repeatability
Determine whether the same nuisance alarms follow the NM3 module, follow the patient room, follow the sampling accessories, or occur only with one clinical setup.
Expected outcome: The source of the issue is isolated.
Why it matters: A problem that follows the module may need bench evaluation. A problem that follows the setup or room is less likely to be internal device failure.
If the Problem Persists
If patient type, alarm limits, setup configuration, sampling accessories, waveform quality, and host monitor connection have been checked and nuisance alarms continue, common external causes have been ruled out.
Remove the Philips NM3 from service, label it Out of Service, and send it for repair or bench evaluation.
Knowing when to stop is proper troubleshooting. Do not repeatedly return a module to patient use if nuisance alarms cannot be explained or corrected.
Clinical Use Tip
Do not troubleshoot alarm behavior on an active patient unless clinical staff confirm it is safe. If monitoring is needed and alarms are unreliable, move the patient to another working monitor first.
Maintain therapy and monitoring continuity by using a backup device or approved alternate monitoring method before troubleshooting the Philips NM3.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported repeated nuisance CO2 alarms on a Philips NM3 capnography monitor during patient monitoring."
Cause
What was observed during troubleshooting.
Example:
"Patient type and alarm limits were reviewed, and the monitor was found set up with limits not appropriate for the current patient category."
Resolution
What action was taken.
Example:
"Correct patient setup was confirmed with clinical staff, alarm limits were adjusted by clinical staff, CO2 waveform was verified stable, and the monitor was returned to service."
Helpful Details to Include (If Known)
- Patient type selected
- Specific alarm reported
- Alarm limits observed
- Whether limits were changed by clinical staff
- Sampling line condition
- Cannula or airway adapter checked
- Power behavior
- Environmental factors
- Indicator lights
- CO2 waveform quality
- EtCO2 and respiration rate behavior
- Host monitor/module connection status
- Accessories swapped
- Whether issue followed the module, room, patient, or accessories
- Final device status
Final Thought
Nuisance alarms should never be dismissed without first confirming patient safety. For the Philips NM3, many repeated alarms can come from patient type mismatch, tight alarm limits, incorrect setup, or unstable sampling. Clinical Engineering should rule out simple external causes first, involve clinical staff for alarm limit decisions, and escalate when the issue cannot be safely corrected.
That is successful troubleshooting.