On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots applicable CrossFlow external communication, data-transfer, or interface problems without disturbing the system's primary fluid-management function.
Step-by-Step Troubleshooting
1. Protect the Patient and Separate Communication From Therapy
If the CrossFlow remains clinically functional but an optional communication or data function is unavailable, do not disrupt active fluid management merely to troubleshoot connectivity.
If the communication failure affects a required clinical workflow, provide an approved alternate method.
Expected outcome: Patient care remains uninterrupted while the communication issue is evaluated separately.
2. Confirm Which Communication Function Is Actually Used
Verify the installed CrossFlow configuration supports the reported network, data-export, or interface function. Determine whether the problem involves:
- External interface communication
- Data export
- Connected peripheral
- Network connection
- Another integrated system
Do not assume every CrossFlow installation includes every possible interface feature.
Expected outcome: The applicable interface and expected data path are clearly identified.
3. Define the Failure Point
Determine whether the CrossFlow:
- Does not recognize the external connection
- Appears connected but does not transfer data
- Transfers intermittently
- Communicates locally but not with the destination
- Fails only at a specific port, cable, or receiving system
Expected outcome: Troubleshooting is focused on the part of the communication path actually failing.
4. Inspect External Cables and Connections
Inspect accessible communication cables, adapters, connectors, and strain reliefs. Confirm connectors are fully seated and connected to the intended ports.
Look for bent contacts, broken latches, contamination, or cable damage.
Expected outcome: The physical connection path is intact. If reseating a loose cable restores communication, verify repeated successful operation.
5. Check Available Connection Indicators
Observe applicable link, connection, or interface indicators if provided. Compare the affected setup with a known working installation when available.
Expected outcome: Available indicators show normal physical connectivity. An absent link may point to cabling, port, or infrastructure rather than the CrossFlow application itself.
6. Substitute a Known-Good External Cable or Port
When permitted, test with a known-good compatible cable and known working infrastructure connection.
Do not alter network infrastructure or security configuration without authorization.
Expected outcome: If communication returns, the failed external cable or connection is identified.
7. Verify User-Accessible Configuration
Compare user-accessible interface or export settings with the site's documented working configuration. Check for obvious changes made during equipment relocation, replacement, or software servicing.
Do not modify protected network, security, or service parameters without authorization.
Expected outcome: Applicable configuration matches the intended workflow.
8. Check the Receiving System
Confirm the destination system, peripheral, or integration point is available. Determine whether other devices using the same destination are functioning.
Coordinate with IT or the integration team when the failure extends beyond the CrossFlow.
Expected outcome: The fault is isolated to the console, external connection, or infrastructure rather than assumed to be a CrossFlow hardware failure.
9. Verify End-to-End Communication
After correcting the cause, perform an approved test of the complete path from the CrossFlow through the external interface to the intended destination.
Expected outcome: Communication or transfer completes consistently and the expected information reaches the intended destination. Troubleshooting can stop.
10. Escalate the Appropriate Layer
If cables, ports, external devices, configuration, and infrastructure checks do not identify the cause, escalate to qualified Stryker service, IT, or the integration team according to the isolated failure point.
Expected outcome: The unresolved fault is routed to the correct technical owner without unnecessary changes to the fluid-management system.
If the Problem Persists
Common physical connection and accessible configuration causes have been ruled out. Remaining categories may include internal interface hardware, software, protected configuration, network infrastructure, destination-system configuration, or integration-level faults.
If the communication function is required for safe or approved clinical operation, the device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation as appropriate
- Evaluated using appropriate manufacturer documentation and approved test equipment
- Repaired or configured only by qualified personnel
Coordinate infrastructure issues with the responsible IT or integration team. Verify the complete communication path before return to service. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Verify the destination received the expected information; a connected cable or active link indicator alone does not prove successful end-to-end communication.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported the CrossFlow external interface was no longer communicating with the connected system."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the external communication cable was loose at the interface connection."
Resolution
What action was taken.
Example:
"The cable was reseated, communication was restored, and successful end-to-end transfer was verified with the connected system."
Helpful Details to Include (If Known)
- Interface function affected
- Destination system
- Cable and connector condition
- Connection indicators
- Port tested
- Known-good cable substitution
- Relevant accessible settings
- Whether other connected systems were affected
- End-to-end test result
- Final device status
Final Thought
Communication failures should be isolated across the complete path rather than automatically assigned to the console. Verify cabling, connection, configuration, infrastructure, and destination behavior before escalating the appropriate layer.
That is successful troubleshooting.