On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots compatible tubing, accessories, connected components, or modules that the CrossFlow does not detect or accept correctly.
Step-by-Step Troubleshooting
1. Protect the Patient Before Changing Components
Do not disconnect or substitute fluid-management components while they are actively supporting patient care unless the clinical team has transitioned to an approved alternate setup.
Expected outcome: Accessory troubleshooting occurs away from active patient dependence. If continuity cannot be maintained, stop troubleshooting.
2. Identify the Exact Unrecognized Component
Record the exact accessory, module, tubing component, or connected device reported as unrecognized. Determine whether:
- It has never worked with this console
- It previously worked
- The problem started after replacement
- Multiple examples of the same accessory fail
- Only one particular component fails
- A message appears on the display
Expected outcome: The failure is narrowed to a specific component or connection path.
3. Confirm Compatibility
Verify the accessory is intended for the CrossFlow configuration using approved manufacturer documentation. Check labeling and relevant identifiers without assuming visually similar components are interchangeable.
Expected outcome: The accessory is confirmed compatible. An incompatible component should be replaced with the correct approved component rather than further troubleshooting the console.
4. Inspect the Accessory
Examine the accessory for:
- Physical damage
- Contamination
- Improper assembly
- Bent or damaged connector features
- Missing components
- Packaging or protective material not removed
- Signs of prior use when applicable
- Incorrect orientation
Expected outcome: The accessory is intact and properly prepared. If correcting installation resolves recognition, troubleshooting can stop after functional verification.
5. Inspect the Console Connection Point
With the system in a safe state, inspect the accessible mating area for fluid, debris, damage, bent contacts, or mechanical obstruction.
Do not insert tools into connectors or attempt internal connector repair.
Expected outcome: The connection point is clean, dry, intact, and unobstructed. Damage requires removal from service or service evaluation as appropriate.
6. Reseat the Component
Disconnect and reinstall the component using the normal approved connection method. Confirm complete mechanical engagement.
Expected outcome: The system recognizes the accessory after proper seating. If recognition remains stable through functional testing, the issue is resolved.
7. Test a Known-Good Compatible Accessory
When available, substitute a known-good approved component of the same applicable type.
This is useful for separating a defective accessory from a console-side recognition problem.
Expected outcome: If the known-good component is recognized, the original accessory is suspect. If multiple verified compatible accessories fail, investigate the console connection or service-level causes.
8. Test the Suspect Accessory on Another Appropriate System if Allowed
If local procedure and manufacturer compatibility permit, test the suspect accessory with another verified CrossFlow system or compare behavior using an equivalent known-good setup.
Expected outcome: The comparison identifies whether the fault follows the accessory or remains with the console.
9. Perform Functional Verification
Once recognition is restored, verify the component remains detected and the associated fluid-management function operates normally using an approved nonpatient test setup.
Expected outcome: Recognition remains stable and the associated function operates correctly. Troubleshooting can stop.
10. Escalate Persistent Recognition Failure
If compatibility, installation, condition, connection quality, and known-good substitutions have been verified but the accessory remains unrecognized, stop external troubleshooting.
Expected outcome: The affected system is removed from clinical use if the missing accessory function is required and is routed for qualified service.
If the Problem Persists
External compatibility, installation, accessory condition, and connection issues have been ruled out. Remaining possibilities may involve the recognition interface, internal communication, protected configuration, software, or other service-level electronics.
The device should be:
- Removed from service when the required accessory function is unavailable
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate Stryker documentation and approved test equipment
- Repaired or configured only by qualified personnel
Return to service only after the affected accessory is consistently recognized and its complete function has been verified. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Confirm the entire fluid path and accessory setup after any component substitution before the system is made available for a procedure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported the CrossFlow would not recognize the installed fluid-management accessory during room setup."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the accessory was not fully seated in its connection point."
Resolution
What action was taken.
Example:
"The accessory was reinstalled correctly, recognition remained stable, and the associated system function was verified with a nonpatient setup."
Helpful Details to Include (If Known)
- Exact accessory or component
- Displayed message
- Accessory labeling or identifier
- Physical condition
- Installation orientation
- Connection-point condition
- Reseating result
- Known-good substitution result
- Whether the problem followed the accessory
- Final functional test result
Final Thought
Accessory recognition faults are often best isolated by verifying compatibility, physical installation, connections, and known-good substitutions before suspecting the console. Escalate once those external causes are eliminated.
That is successful troubleshooting.