On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting high airway pressure alarms caused by circuit obstruction, condensate, filters, accessories, alarm settings, test-lung resistance, or ventilator malfunction.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not troubleshoot a persistent high airway pressure alarm while the Servo-i is actively supporting a patient.
Notify respiratory therapy and the clinical team. Transfer the patient to another verified ventilator or approved ventilation method before continuing. Provide manual ventilation when clinically required and performed by qualified personnel.
Expected outcome: The patient is safely supported without relying on a ventilator that may be unable to deliver ventilation correctly.
Continue Clinical Engineering troubleshooting only after the Servo-i has been removed from patient use.
2. Confirm the Reported Alarm
Review the displayed alarm message and determine:
- Whether the alarm occurs continuously or intermittently
- Whether it occurs during inspiration, expiration, or both
- The displayed peak airway pressure
- The selected ventilation mode and pressure settings
- Whether the issue began after a circuit, filter, humidifier, or accessory change
Review the alarm history when available. The Servo-i provides alarm-history access through the Menu functions.
Expected outcome: The alarm pattern and operating conditions are clearly documented.
3. Inspect the Patient Circuit Externally
With the ventilator in standby and disconnected from the patient, inspect the entire breathing circuit for:
- Kinked or compressed tubing
- Tubing trapped beneath equipment
- Internally collapsed circuit sections
- Incorrect circuit assembly
- Closed clamps or caps
- Obstructed connectors
- Excessive circuit length or unsupported tubing
Straighten or replace any questionable circuit component.
Expected outcome: The circuit is open, correctly assembled, and free of visible restrictions.
If the alarm is resolved during subsequent testing, stop troubleshooting.
4. Check for Condensate or Fluid Obstruction
Inspect the inspiratory and expiratory limbs, water traps, humidifier chamber, filters, and connectors for accumulated condensation.
Drain or replace components according to facility infection-control procedures. Do not allow fluid to enter the ventilator connections.
Expected outcome: Gas can move freely through the circuit without fluid-related restriction.
5. Inspect Filters, HMEs, and Accessories
Remove the patient circuit from service and inspect externally installed components, including:
- Heat-and-moisture exchangers
- Bacterial or viral filters
- Nebulizer adapters
- Closed-suction adapters
- Flow sensors
- Catheter mounts
- Humidification accessories
Replace any component that is wet, contaminated, damaged, occluded, or incorrectly installed. Test using approved components appropriate for the Servo-i configuration.
Expected outcome: No accessory creates excessive resistance or an obstructed gas pathway.
6. Inspect the Expiratory Path
Check the expiratory limb and expiratory cassette connection for:
- Kinks or blocked tubing
- Condensation
- Occluded filters
- Improper seating
- Cracked or damaged connectors
- Contamination around accessible ports
Confirm the expiratory cassette is fully seated and latched. Do not disassemble the cassette beyond approved cleaning or inspection procedures.
Expected outcome: The expiratory pathway is unobstructed and the cassette is properly installed.
7. Verify Alarm Limits and Ventilation Settings
Have qualified respiratory therapy personnel verify that the high-pressure alarm limit is appropriate for the selected mode, patient category, and intended test conditions.
Confirm that pressure-related settings were not accidentally changed. The Servo-i alarm window is accessed through the Alarm Profile control, and alarm limits should be adjusted before ventilation begins.
Do not raise the alarm limit merely to prevent an alarm without identifying the cause.
Expected outcome: Settings and alarm limits are clinically appropriate and not responsible for a false or premature alarm.
8. Test with a Known-Good Circuit and Test Lung
Install a verified compatible circuit and test lung. Keep the ventilator off a patient.
Select controlled test settings appropriate for the test lung and observe:
- Peak airway pressure
- Pressure waveform
- Delivered tidal volume
- Inspiratory and expiratory flow
- Whether the alarm occurs immediately or after several breaths
Avoid squeezing, folding, or restricting the test lung during evaluation.
Expected outcome: The ventilator operates without an unexplained high-pressure alarm when connected to a known-good circuit and unrestricted test lung.
If the issue disappears, replace the original circuit, accessory, filter, or test lung identified as the cause.
9. Run the Pre-Use Check
Place the Servo-i in standby and perform the complete pre-use check using the required test tube and on-screen instructions. The manufacturer’s setup sequence includes a patient-circuit test as part of the pre-use check.
Do not return the ventilator to service if the check fails or cannot be completed.
Expected outcome: The ventilator and installed circuit successfully complete the pre-use check.
10. Evaluate for an Internal Ventilator Fault
If the alarm persists with:
- A known-good circuit
- New filters and accessories
- An unrestricted test lung
- Correct settings
- A properly seated expiratory cassette
- A successful or repeated pre-use evaluation
Document the measured pressure behavior, alarm timing, waveforms, and any pre-use check error.
Possible internal causes may involve pressure sensing, flow measurement, inspiratory control, expiratory control, or internal pneumatic components. Do not proceed with internal disassembly unless authorized, trained, and following current manufacturer service documentation.
Expected outcome: External causes have been ruled out and sufficient information is available for bench repair or manufacturer support.
If the Problem Persists
When the high airway pressure alarm continues with a known-good circuit and test lung, common external causes have been ruled out and the problem is likely internal.
The ventilator should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or qualified bench evaluation
- Tested according to the manufacturer’s performance-verification requirements before return to clinical use
Knowing when to stop and escalate is proper troubleshooting, particularly when airway pressure regulation may be unreliable.
Clinical Use Tip
Never troubleshoot recurring high-pressure alarms on an active patient. Move the patient to another verified ventilator first. Do not increase the pressure alarm limit simply to silence the alarm.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Respiratory therapy reported that the Getinge Servo-i repeatedly generated a high airway pressure alarm during ventilation."
Cause
What was observed during troubleshooting.
Example:
"Inspection found a water-saturated expiratory filter creating excessive circuit resistance and elevated measured airway pressure."
Resolution
What action was taken.
Example:
"Replaced the expiratory filter, installed a verified circuit and test lung, completed the pre-use check, and confirmed normal ventilation without recurring alarms."
Helpful Details to Include (If Known)
- Exact alarm message recorded
- Peak airway pressure observed
- Alarm limit and ventilation mode
- Circuit inspected or replaced
- Filters and HME replaced
- Condensate found or ruled out
- Expiratory cassette seating checked
- Known-good test lung used
- Pressure and flow waveform behavior
- Pre-use check results
- Unusual sounds, heat, odor, or vibration
- Final device status
Final Thought
High airway pressure alarms require a safety-first and restriction-first approach. Check the circuit, moisture, filters, accessories, expiratory pathway, and settings before suspecting the ventilator. Escalate persistent pressure-control problems and document the findings clearly.
That is successful troubleshooting.