On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots failed leak or process challenge testing caused by setup, connections, accessories, load condition, consumables, or unresolved equipment performance problems.
Step-by-Step Troubleshooting
1. Protect the Device and Do Not Continue Processing
A failed leak or process challenge test can indicate that the endoscope, accessory, processing setup, or reprocessor is not suitable for continued use. Do not advance the affected load as though the test passed.
Expected outcome: The affected device or load remains segregated until the cause is identified. Alternate validated processing is used as necessary.
2. Confirm Which Test Failed
Determine whether the failure involved an endoscope leak test, an equipment process check, or another required challenge test. Record the exact displayed message, test phase, and affected device or load.
Expected outcome: The specific failure is documented. If the test passes on a repeat attempt, the original setup must still be evaluated before the unit is considered reliable.
3. Inspect the Endoscope or Test Article Externally
If an endoscope-specific test failed, inspect the scope, connectors, valves, channels, caps, and accessible surfaces for obvious damage or incorrect setup. Do not continue processing a device with visible damage.
Expected outcome: No obvious device defect or setup problem is present. Visible damage requires the affected endoscope to be removed from clinical use and handled under its service procedure.
4. Verify Test Connections
Confirm leak-test connectors, adapters, tubing, channel connections, and processing accessories are fully seated and appropriate for the device being processed. Check for kinks, loose fittings, or missing required components.
Expected outcome: All external test connections are correct. If reseating a connection allows a successful test, repeat verification and stop once reliability is demonstrated.
5. Inspect Accessories for Damage or Moisture
Check reusable or approved accessories for cracks, damaged seals, contamination, retained moisture, or other visible conditions that could affect testing.
Expected outcome: Accessories appear serviceable. If a damaged accessory is replaced with an approved known-good equivalent and the test passes, complete final verification.
6. Use an Approved Known-Good Comparison
When permitted, test with a known-good compatible accessory or processing setup to determine whether the failure follows the original device/accessory or remains with the SYSTEM 1E.
Expected outcome: The failure is isolated to either the load/accessory or the reprocessor. If a known-good setup passes consistently, address the affected accessory or device separately.
7. Verify Consumables and Utilities
Confirm required chemistry, water, power, and other process supplies are normal. A process challenge may fail because the underlying cycle conditions are not being achieved.
Expected outcome: External process conditions are available and acceptable.
8. Repeat the Test Only After Correcting a Plausible Cause
Do not repeatedly rerun a failed test without intervention. After correcting a connection, accessory, setup, or external condition, repeat the approved test.
Expected outcome: The test passes consistently after a clearly identified correction. If so, proceed to final verification.
9. Perform Final Functional Verification
Verify the test passes using an approved setup and that the associated processing cycle completes without alarms. Confirm test and cycle records are generated as expected.
Expected outcome: The test and subsequent cycle perform reliably. Troubleshooting can stop.
10. Escalate Repeated Test Failure
If setup, device condition, connectors, accessories, consumables, and utilities have been verified but testing still fails, stop external troubleshooting.
Expected outcome: The affected equipment is removed from service and evaluated by qualified personnel.
If the Problem Persists
Common setup, accessory, connection, consumable, and utility causes have been ruled out. Depending on which test failed, the remaining cause may involve the endoscope itself, leak-test circuitry, internal sensing, pumps, fluid pathways, process control, or another service-level condition.
Remove the SYSTEM 1E from service when the failure follows the reprocessor, label it Out of Service, and arrange qualified repair or bench evaluation using appropriate manufacturer documentation and approved test equipment.
Any affected endoscope should also remain segregated if the failure may indicate a scope integrity problem.
Return-to-service testing should confirm reliable completion of the applicable test and full processing cycle.
Knowing when repeated test failures require escalation rather than repeated retries is proper troubleshooting.
Clinical Use Tip
A failed endoscope leak test may indicate potential scope damage; do not continue processing or using the affected scope until handled according to approved procedure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Sterile Processing reported repeated leak-test failures when connecting an endoscope to the SYSTEM 1E."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the external leak-test connection was not fully seated."
Resolution
What action was taken.
Example:
"Corrected the connection, repeated the approved test successfully, and verified completion of a functional processing cycle before returning the reprocessor to service."
Helpful Details to Include (If Known)
- Exact test that failed
- Displayed message
- Endoscope or load identification
- Connector and adapter condition
- Accessory condition
- Known-good comparison result
- Consumable status
- Utility status
- Number of repeated failures
- Result after correction
- Final equipment status
Final Thought
Treat failed integrity or challenge tests as meaningful process failures, isolate the problem through external setup and known-good comparisons, verify the correction, and escalate persistent failures without bypassing safeguards.
That is successful troubleshooting.