Medivators Advantage Plus

Incoming Water Supply Low or Water Pressure Alarm

On this page

Asset Type

Endoscope Reprocessor (AER)

Manufacturer

Medivators

Model

Advantage Plus

What This Guide Helps With

Addresses low-water-supply alarms, slow chamber filling, or cycle interruption caused by external water, valve, hose, filter, or facility utility problems.

Step-by-Step Troubleshooting

1. Protect Patients and Reprocessing Workflow

Do not use an interrupted or incomplete cycle as proof that an endoscope has been properly reprocessed. Quarantine the affected endoscope and move reprocessing to another verified AER when available.

Do not troubleshoot the unit while a cycle containing a clinically needed endoscope is assumed to be complete.

Expected outcome: Endoscope availability and infection-prevention requirements are maintained while the AER is evaluated.

2. Confirm the Exact Reported Condition

Ask staff when the alarm occurs, which chamber or cycle was involved, whether the chamber began filling, and whether other equipment using the same water supply is affected. Record the exact displayed message without interpreting or clearing it prematurely.

Check whether the problem affects every cycle or is intermittent.

Expected outcome: The failure is confirmed as an incoming-water problem rather than a drain, circulation, or isolated cycle-selection issue.

3. Verify the Facility Water Supply

Confirm the designated water supply valve is fully open and has not been partially closed during cleaning, plumbing work, or filter service. Check for posted utility shutdowns, nearby plumbing repairs, or reports of reduced building water pressure.

Where permitted, compare operation with another AER supplied from the same utility branch.

Expected outcome: A stable facility water supply is available. If restoring the external water supply clears the alarm and a complete verification cycle passes, troubleshooting can stop.

4. Inspect the External Supply Hose and Connections

Inspect the incoming water hose from the wall connection to the AER. Look for:

Correct external routing or connection problems without moving the AER in a way that strains utility lines.

Expected outcome: The hose is secure, leak-free, unobstructed, and properly routed. If flow returns and the cycle fills normally, troubleshooting can stop after verification.

5. Check External Prefilters and Water-Treatment Components

Inspect accessible facility-installed sediment filters, pretreatment assemblies, or other external water-treatment components serving the AER. Look for visible restriction indicators, overdue replacement labels, closed isolation valves, or recent service that may have left valves in the wrong position.

Do not bypass required filtration or treatment components.

Expected outcome: External filtration and treatment components are in service, correctly aligned, and not visibly restricting flow.

6. Check for Shared-Supply Demand

Determine whether the alarm occurs only when another AER, washer, sink, or utility device is operating. Recheck the unit during a lower-demand period when operationally acceptable.

Coordinate with Facilities if pressure appears to drop when multiple devices draw water simultaneously.

Expected outcome: The water supply remains adequate during expected department demand. A shared-utility pressure problem is identified when applicable.

7. Restart Only When Safe and Authorized

After confirming that the interrupted load remains quarantined, perform a normal user-level restart according to approved facility and manufacturer procedures. Do not repeatedly restart the AER if the alarm immediately returns.

Observe whether the chamber begins filling at the expected point in the cycle.

Expected outcome: The AER starts normally and fills without a water-pressure alarm. If the alarm returns, continue troubleshooting.

8. Perform a Controlled Functional Verification

Run the approved empty-cycle or verification process using the correct accessories and utilities. Observe for:

Do not release the AER for clinical use based only on the disappearance of the alarm.

Expected outcome: The verification cycle completes without water-supply alarms. The issue is resolved, and troubleshooting can stop.

9. Stop and Escalate When the Alarm Persists

If facility pressure, valves, hoses, external filtration, and shared-demand conditions are acceptable but the alarm remains, remove the AER from service. Do not access internal plumbing, pressure sensors, inlet valves, pumps, or control assemblies without approved service documentation and authorization.

Expected outcome: An unresolved or unreliable AER is prevented from processing clinical devices.

If the Problem Persists

Common external water-supply causes have been ruled out. The remaining possibilities may include an internal inlet restriction, valve problem, pressure- or flow-sensing fault, control issue, or facility plumbing condition that requires measured evaluation.

The AER should be:

After correction, complete all required functional, leak, alarm, and cycle-performance verification before return to service. Knowing when to stop external troubleshooting is proper troubleshooting.

Clinical Use Tip

Quarantine any endoscope from an interrupted cycle until it has completed a verified reprocessing cycle.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Sterile Processing reported that the Advantage Plus displayed a low incoming water pressure alarm and stopped before the chamber filled."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found the external water supply hose kinked behind the AER after the unit had been repositioned."

Resolution

What action was taken.

Example:
"The hose was rerouted without restriction, connections were inspected, and an approved verification cycle completed without alarms or leaks."

Helpful Details to Include (If Known)

Final Thought

Protect the endoscope workflow first, verify the facility water path before assuming internal failure, test the complete cycle after correction, escalate persistent alarms appropriately, and document the verified cause and resolution clearly.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide