Medivators DSD-201 / DSD Edge Series

Channel Blockage or Flow Error Alarms

On this page

Asset Type

Endoscope Reprocessor (AER)

Manufacturer

Medivators

Model

DSD-201 / DSD Edge Series

What This Guide Helps With

Troubleshooting channel blockage or flow-related alarms caused by scope connections, tubing issues, filters, or flow restrictions preventing proper reprocessing.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Verify the Reported Alarm and Behavior

Check Scope Channel Connections (Most Common Cause)

Inspect Channel Tubing for Kinks or Occlusions

Check for Internal or External Blockage in the Scope

Inspect Water Supply and Pressure

Check Filters and Strainers

Inspect Drain Line for Restrictions

Restart Cycle After Corrections

If the Problem Persists

If all external causes have been ruled out, the issue is likely internal (flow sensors, valves, or pump failure).

Remove the unit from service, label it Out of Service, and send for repair or bench evaluation.

Knowing when to stop prevents unnecessary risk and protects equipment integrity.

Clinical Use Tip

Do not attempt to troubleshoot flow errors with a contaminated scope or during active clinical workflow. Always use a cleaned or test scope when verifying operation.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"AER displaying channel blockage alarm and stopping mid-cycle during reprocessing."

Cause

What was observed during troubleshooting.

Example:
"Kinked channel tubing restricting flow to scope lumen."

Resolution

What action was taken.

Example:
"Tubing repositioned and verified unobstructed; system tested and returned to service."

Helpful Details to Include (If Known)

Final Thought

Flow-related alarms are often caused by simple external restrictions rather than internal failure. A structured approach—starting with connections, tubing, and supply—ensures safe and efficient troubleshooting. Always prioritize infection control and recognize when escalation is appropriate.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide