On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots frozen, intermittent, or unresponsive user controls caused by startup state, contamination, external connections, power quality, or system lockup.
Step-by-Step Troubleshooting
1. Protect the Patient Before Testing Controls
If the system is in clinical use and controls cannot reliably adjust or stop intended operation, provide alternate equipment or workflow support before troubleshooting.
Do not manipulate unreliable controls while the device is supporting an active procedure.
Expected outcome: The patient and procedure are no longer dependent on an interface that cannot be trusted.
2. Confirm Which Interface Function Has Failed
Determine whether the problem involves:
- Entire display.
- Touch response.
- Individual button or control.
- Delayed response.
- Frozen display.
- Incorrect displayed information.
- Controls that respond intermittently.
Record any message or frozen screen condition.
Expected outcome: The failure is narrowed to a specific control or overall interface problem.
3. Check System Power and Startup State
Verify the system is fully powered and has completed normal startup. A device that is still starting, faulted, or experiencing unstable AC power may appear to have an interface failure.
Confirm the power cord and receptacle are secure and verified.
Expected outcome: The interface is evaluated only after stable power and complete startup are confirmed.
4. Inspect the Display and Control Surface
Check for:
- Fluid or cleaning residue.
- Adhesive residue.
- Cracked glass or plastic.
- Depressed or stuck controls.
- Damage from impact.
- Foreign material around buttons or edges.
Clean only according to approved facility and manufacturer practices.
Expected outcome: Controls are clean, intact, and unobstructed. If cleaning restores normal response, proceed to functional verification and troubleshooting can stop afterward.
5. Remove External Items That May Interfere
Check whether drapes, accessories, storage items, cables, or other equipment are pressing against controls or interfering with the interface.
Expected outcome: The user interface is physically unobstructed.
6. Isolate Nonessential External Accessories
With the device removed from patient use, disconnect nonessential external accessories or interfaces that can safely be removed. Restart or retest the unit in a basic approved configuration.
Expected outcome: The controls operate normally with external accessories isolated, identifying an accessory or communication-related interaction.
7. Perform One Controlled Restart
If no physical cause is found and the system permits normal shutdown, perform a controlled power cycle using a verified AC source.
Avoid repeated cycling if the system continues to freeze.
Expected outcome: The interface returns to normal operation and remains responsive after startup.
8. Exercise the Controls Without Entering Restricted Functions
Check the normal operator-accessible controls required for clinical use. Verify that inputs produce the expected visible system response.
Do not access unauthorized service menus or alter protected configuration settings.
Expected outcome: Controls respond consistently and correspond correctly with the displayed state.
9. Perform Functional Verification
Verify the display, alarms, normal controls, and intended AirSeal functions according to approved procedures.
Pay particular attention to whether the original control problem returns after several minutes of operation.
Expected outcome: The interface remains responsive and reliable. If so, troubleshooting can stop.
10. Escalate Persistent Interface Failure
If power, cleanliness, physical condition, accessories, and a controlled restart do not restore reliable operation, remove the device from service.
Expected outcome: A persistent interface failure is escalated rather than worked around clinically.
If the Problem Persists
Common external causes have been ruled out. The remaining issue may involve display hardware, touch interface electronics, control circuitry, software, internal communication, or configuration requiring service-level evaluation.
The device should be:
- Removed from service.
- Labeled Out of Service.
- Sent for repair or bench evaluation.
- Evaluated using appropriate CONMED documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Following repair, verify normal control response, alarms, operating functions, and applicable electrical safety requirements before clinical release.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
If the controls cannot reliably change or stop an operating function, exchange the system rather than continuing the procedure with an unreliable interface.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"OR staff reported that the AirSeal iFS touchscreen did not respond consistently to user input."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried cleaning residue on the control surface and verified stable device power."
Resolution
What action was taken.
Example:
"Cleaned the control surface using the approved method, verified consistent control response and normal functional operation, and returned the system to service."
Helpful Details to Include (If Known)
- Which control or screen area was unresponsive.
- Whether the display was frozen or still updating.
- Any displayed alarm or message.
- AC source and power status.
- Evidence of contamination or physical damage.
- Accessories connected.
- Response after controlled restart.
- Whether the failure returned during testing.
- Final functional status.
Final Thought
An unresponsive interface can turn an otherwise functioning system into an unsafe device. Verify power, physical condition, contamination, and external influences first, then escalate persistent failures instead of working around them.
That is successful troubleshooting.