On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting occlusion alarms on the Novum IQ infusion pump. These alarms typically indicate resistance in the fluid path. The goal is to rule out common external causes such as tubing issues, clamps, or setup problems before considering internal sensor or pump mechanism failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not troubleshoot while the pump is actively infusing a patient.
- Ensure the patient is safely transitioned to another functioning device before continuing.
Confirm the Alarm Condition
- Verify the exact alarm message (e.g., upstream vs downstream occlusion).
- This helps determine whether the restriction is before or after the pump mechanism.
Check for Closed or Partially Closed Clamps
- Inspect all roller clamps and slide clamps on the IV tubing.
- A partially closed clamp is one of the most common causes of occlusion alarms.
Inspect the IV Tubing for Kinks or Obstructions
- Trace the tubing from the bag to the patient.
- Look for:
- Kinks or tight bends
- Compression under bed rails or equipment
- Straighten or reposition as needed.
Verify Proper Tubing Installation in the Pump
- Ensure the administration set is:
- Correctly seated in the pump channel
- Fully loaded according to manufacturer guidance
- Misalignment can create artificial resistance.
Check the IV Site (If Applicable)
- Coordinate with clinical staff to assess:
- Infiltration
- Catheter occlusion
- Patient positioning affecting flow
- Resistance at the patient site will trigger downstream occlusion alarms.
Inspect the Fluid Bag and Upstream Flow
- Ensure the fluid bag is not empty.
- Confirm the spike is properly inserted and the drip chamber is correctly filled.
- Check for collapsed bags (especially with non-vented sets).
Verify Correct Administration Set Type
- Ensure the tubing set is compatible with the Novum IQ.
- Incorrect or non-approved sets may cause flow resistance or sensor misinterpretation.
Power Cycle the Pump
- Turn the pump off and back on.
- This can clear temporary sensor or software-related faults.
Test with a Known Good Setup
- Replace tubing with a new, known good administration set.
- Run a controlled test infusion (per policy) to see if the alarm persists.
- This helps isolate whether the issue is setup-related or device-related.
If the Problem Persists
If all external causes have been ruled out and the occlusion alarm continues:
- The issue may be related to:
- Internal pressure sensors
- Pump mechanism resistance
- Calibration drift
- Remove the device from service
- Label it Out of Service
- Send for repair or bench evaluation
Knowing when to stop external troubleshooting is critical to safe and effective Clinical Engineering practice.
Clinical Use Tip
Do not troubleshoot occlusion alarms on an active patient infusion. Always have clinical staff transition the patient to a functioning pump before continuing troubleshooting. This ensures uninterrupted therapy and patient safety.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Nursing reported frequent occlusion alarms during infusion despite proper setup.”
Cause
What was observed during troubleshooting.
Example:
“Kinked tubing found under bed rail causing intermittent downstream occlusion.”
Resolution
What action was taken.
Example:
“Repositioned tubing, verified proper flow, and confirmed pump operation without further alarms.”
Helpful Details to Include
- Tubing inspected and repositioned
- Clamps verified open
- Administration set replaced
- Alarm type (upstream/downstream) noted
- Pump power cycled
- Test infusion performed
- Final device status (returned to service or sent for repair)
Final Thought
Occlusion alarms are often caused by simple, external restrictions in the fluid path. A structured, step-by-step approach ensures quick resolution while protecting patient safety. When external causes are eliminated, timely escalation prevents unnecessary downtime and ensures reliable device performance. Clear documentation supports both patient care and equipment history.
That is successful troubleshooting.