Stryker CrossFlow

Display, Touchscreen, or Controls Are Unresponsive

On this page

Asset Type

Fluid Management System

Manufacturer

Stryker

Model

CrossFlow

What This Guide Helps With

Troubleshoots a CrossFlow display or control interface that is blank, frozen, intermittent, inaccurate, or unresponsive to normal input.

Step-by-Step Troubleshooting

1. Protect the Patient and Stop Dependence on Unreliable Controls

If controls cannot be trusted during a procedure, notify the clinical team and transition to a verified alternate system or safe approved method. Do not continue manipulating an unreliable interface while patient care depends on it.

Expected outcome: Clinical care continues without dependence on the affected controls. If safe control cannot be assured, the CrossFlow remains out of use.

2. Confirm Which Interface Function Has Failed

Determine whether the problem involves:

Expected outcome: The failed function is clearly identified and reproducible. If controls are functioning normally during evaluation, investigate conditions present when the failure occurred.

3. Verify Normal Power and Startup

Confirm the console receives reliable AC power and completes startup normally. A partially completed startup or unstable power source can appear to be an interface problem.

Expected outcome: The system reaches its normal operating state. If restoring stable power corrects the interface, proceed to final functional testing.

4. Inspect the Display and Controls Externally

Inspect for:

Use only approved cleaning methods.

Expected outcome: The interface is clean, unobstructed, and physically intact. If removing an external obstruction restores normal response, the issue is resolved pending verification.

5. Confirm the Report Is Not a Locked or Inactive Control State

Verify the CrossFlow is in an operating state where the requested control should be available. Some controls may not respond when a function is inactive, an accessory is absent, or the system is waiting for another required condition.

Do not change protected settings solely to make a control active.

Expected outcome: The control is evaluated under the correct operating condition. If normal response returns, no hardware repair is indicated.

6. Disconnect Suspect External Accessories

Power down the system and disconnect nonessential external accessories or interfaces. Restart the console and evaluate the display and controls in the simplest appropriate configuration.

Expected outcome: Interface response returns if an external accessory or connection was interfering. Reconnect accessories one at a time to identify the cause.

7. Perform a Normal Power Cycle

If no hazardous condition is present, shut the system down normally, allow shutdown to complete, and restart it using standard controls.

Do not repeatedly cycle a system that exhibits overheating, smoke, liquid intrusion, or electrical abnormalities.

Expected outcome: The interface initializes and responds consistently after restart. If the failure does not recur, continue with repeated functional verification.

8. Test All User-Accessible Controls

Away from patient use, check the user-accessible controls required for normal operation. Confirm each input produces the expected visible or functional response.

Expected outcome: Controls respond predictably and consistently. Any persistent dead, sticking, intermittent, or incorrect control requires escalation.

9. Perform Final Functional Verification

Configure the system with appropriate accessories or an approved test setup. Verify display information, controls, alarm presentation, and fluid-management operation.

Expected outcome: The interface operates normally throughout the functional test. If verification passes, the system may be returned to service according to local policy.

10. Escalate an Unresolved Interface Failure

If power, startup, physical condition, operating state, accessories, and normal restart have been ruled out, stop external troubleshooting.

Expected outcome: A system with unreliable controls is removed from service and routed for qualified repair.

If the Problem Persists

Common external causes have been ruled out. Remaining categories may include the display assembly, control interface, internal communication, software, protected configuration, or internal electronics.

The device should be:

The system should not return to clinical use until all required controls respond reliably and complete functional verification has passed. Knowing when to stop external troubleshooting is proper troubleshooting.

Clinical Use Tip

An intermittent control is still an unreliable control; do not return the CrossFlow to a procedure solely because the interface responds after one restart.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Staff reported that CrossFlow controls were not responding during room setup."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found dried cleaning residue around an external control surface that was interfering with normal operation."

Resolution

What action was taken.

Example:
"The control surface was cleaned using the approved method, normal response was restored, and complete functional operation was verified."

Helpful Details to Include (If Known)

Final Thought

Treat an unreliable interface as a patient-safety concern. Rule out power, external obstruction, operating state, and accessory effects first, then escalate persistent failures rather than assuming a specific internal component.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide