On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots no-power, incomplete startup, or repeated boot interruption caused by external power, connections, accessories, controls, or environmental conditions.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Surgical Continuity
Do not troubleshoot the CUSA Clarity while a patient depends on it for active surgical aspiration or tissue fragmentation. Notify the surgical team and transition to an approved alternate method or verified replacement system before removing the unit from clinical use.
Inspect immediately for smoke, unusual odor, fluid intrusion, excessive heat, damaged power components, or visible electrical damage. If present, disconnect AC power when safe and remove the system from service.
Expected outcome: Patient care continues safely using an alternate method, and the console is available for controlled troubleshooting.
2. Confirm the Exact Startup Complaint
Ask staff whether the console was completely dead, powered briefly and shut down, froze during startup, restarted repeatedly, or reached a screen but would not become ready.
Attempt startup only in a controlled environment without a patient connected. Observe indicator lights, display activity, fan noise, audible tones, and where the startup sequence stops.
Expected outcome: The reported condition is reproduced or the console completes startup normally. If startup completes repeatedly without fault, continue with functional verification and troubleshooting may stop if no issue recurs.
3. Verify Facility Power
Confirm the power cord is fully seated at the console and wall receptacle. Inspect the cord, plug, strain relief, and receptacle for damage or looseness.
Verify the outlet using an appropriate electrical tester or known-good device. Avoid extension cords, damaged power strips, or questionable receptacles during testing.
Expected outcome: Verified AC power is available and the console receives stable facility power. If correcting the outlet or connection restores reliable startup, perform final verification and stop troubleshooting.
4. Inspect External Power Components
Examine the console power inlet, cord connection, and accessible power controls for contamination, physical damage, or incomplete engagement.
If an approved known-good compatible power cord is available, substitute it when appropriate.
Expected outcome: External power components are intact and secure. A known-good cord either restores operation or rules out the detachable power cord as the cause.
5. Disconnect Nonessential External Accessories
Power the unit off and disconnect nonessential external accessories that could complicate startup, while leaving only the connections necessary for basic console startup.
Restart the console and compare behavior.
Expected outcome: The console starts normally with nonessential accessories removed, or the startup problem remains independent of accessories. If one accessory causes the failure when reconnected, remove that accessory from use and stop troubleshooting after verification.
6. Check Controls and Physical Condition
Inspect accessible switches, touchscreen surfaces, connectors, vents, and the console housing. Confirm nothing is holding a control continuously activated and that the console is not obstructed or positioned where ventilation is restricted.
Do not open the console or bypass protective circuitry.
Expected outcome: No external obstruction, stuck control, or physical condition explains the startup issue.
7. Allow Environmental Conditions to Normalize
If the console was recently moved from storage, exposed to unusual temperature conditions, or subjected to moisture, allow it to reach the appropriate clinical environment before another startup attempt.
Do not operate equipment with suspected condensation or fluid intrusion.
Expected outcome: The console starts normally after environmental conditions stabilize, or the startup problem persists.
8. Perform Repeated Controlled Startup Checks
With verified AC power and approved external connections, perform controlled power cycles according to normal operating practice. Confirm the console consistently reaches its normal ready state without freezing, restarting, or shutting down.
Expected outcome: The console reliably completes startup. If it does, proceed with applicable functional and electrical safety testing before return to service.
9. Perform Final Functional Verification
Reconnect the normal approved accessories needed for system testing and verify the console recognizes connected components, accepts controls, and remains stable during a nonclinical functional check.
Complete electrical safety or other return-to-service testing required by facility policy and manufacturer documentation.
Expected outcome: The console starts reliably, remains powered, and passes required functional checks. Troubleshooting can stop and the device may be returned to service when all required testing passes.
10. Escalate an Unresolved Startup Failure
If verified power, cord condition, connections, accessories, controls, and environment are satisfactory but the console still does not power on or complete startup, stop external troubleshooting.
Expected outcome: The console is removed from service for qualified bench evaluation rather than subjected to unnecessary internal disassembly.
If the Problem Persists
Common external causes have been ruled out. The remaining problem may involve the console power system, internal startup circuitry, software, internal communication, or another service-level condition.
The device should be:
- Removed from service.
- Labeled Out of Service.
- Sent for repair or bench evaluation.
- Evaluated using appropriate Integra LifeSciences service documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
- Subjected to applicable functional and electrical safety testing before return to service.
Knowing when to stop external troubleshooting and escalate a persistent startup failure is proper troubleshooting.
Clinical Use Tip
Establish an alternate surgical aspiration method before troubleshooting because an unreliable console should never remain part of an active surgical procedure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"OR staff reported the CUSA Clarity console would not power on before a surgical case."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the detachable AC power cord was not fully seated at the console power inlet."
Resolution
What action was taken.
Example:
"Reseated the power cord, verified repeated successful startups and normal functional operation, and returned the system to service."
Helpful Details to Include (If Known)
- Whether the console was completely dead or partially started.
- Point in startup where operation stopped.
- Outlet verification result.
- AC power cord condition.
- Indicator lights or audible startup activity.
- Accessories connected during the failure.
- Evidence of heat, odor, fluid, or physical damage.
- Behavior with nonessential accessories disconnected.
- Results of repeated startup attempts.
- Final functional and electrical safety test status.
Final Thought
Protect the patient first, verify facility power and external conditions before suspecting internal failure, and stop when the problem requires service-level evaluation. Clear CCR documentation should show exactly what was reported, found, corrected, and verified.
That is successful troubleshooting.