On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses barcode and data-transfer failures caused by accessories, cables, media, network availability, configuration, signal conditions, or infrastructure problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Preserve Clinical Workflow
Confirm that the data-transfer problem does not interfere with active blood processing or patient identification. If electronic transfer is unavailable, use the facility-approved alternate documentation workflow.
Do not interrupt active therapy solely to troubleshoot nonessential connectivity.
Expected outcome: Patient care and required documentation can continue safely while connectivity is evaluated.
2. Define Which Interface Has Failed
Determine whether the complaint involves barcode scanning, USB export, wired Ethernet, Wi-Fi, or more than one interface.
Ask whether the problem affects every patient or only a particular device, accessory, network location, or destination.
Expected outcome: The failure is narrowed to a specific communication method.
3. Verify Basic System Operation
Confirm the Cell Saver Elite+ starts normally and is not experiencing a broader touchscreen, startup, or shutdown problem.
Expected outcome: The device operates normally aside from the reported communication function.
4. Inspect the Barcode Scanner or External Accessory
If barcode scanning is affected, inspect the scanner, cable, connector, and reading surface for damage or contamination. Verify the barcode itself is legible and compatible with the clinical workflow.
Use a known-good barcode if available.
Expected outcome: The accessory is physically intact and can read a known-good barcode. If replacing or reconnecting the accessory restores scanning, troubleshooting can stop.
5. Inspect USB Media and Connections
For USB transfer problems, verify the media and external connector are undamaged and fully inserted. If policy permits, test with known-good approved media.
Do not connect unapproved or unknown USB devices to clinical equipment.
Expected outcome: Approved known-good media is recognized and data transfer functions normally.
6. Inspect Ethernet Cabling and Link Conditions
For wired connectivity, verify the Ethernet cable is fully seated at both ends and free of visible damage. Test with a known-good approved network cable and known-good network port when available.
Expected outcome: The physical network connection is intact. If a cable or port substitution restores connectivity, the issue is resolved.
7. Check Wi-Fi Environment
For wireless problems, confirm Wi-Fi is expected to be available in the current location and that the issue is not due to unusual distance, shielding, relocation, or a known wireless outage.
Do not alter security settings or credentials without authorization.
Expected outcome: The device is within the intended wireless environment and no obvious infrastructure limitation is present.
8. Verify Approved Communication Configuration
Review accessible network or data-transfer settings against approved site documentation. Look for obvious discrepancies without changing addresses, security parameters, destinations, or credentials unless authorized.
Expected outcome: Device configuration matches the approved site configuration or a documented discrepancy is identified for correction by authorized personnel.
9. Compare With Other Devices or Network Services
Determine whether another known-good device can use the same cable, port, Wi-Fi environment, barcode workflow, or destination.
This helps separate a Cell Saver Elite+ problem from a facility infrastructure problem.
Expected outcome: The failure is isolated to either the equipment, accessory, or external network environment.
10. Verify Data Transfer After Correction
Perform an approved nonpatient transfer, scan, or connectivity test and confirm the expected destination receives the information correctly.
Expected outcome: The complete communication path works as intended. Troubleshooting can stop when repeat testing succeeds.
11. Escalate Persistent Connectivity Problems
If hardware connections, known-good accessories, approved configuration, and infrastructure checks do not resolve the problem, remove the affected communication function from use and escalate appropriately.
If the communication problem compromises required clinical identification, documentation, or device operation, remove the entire system from service.
Expected outcome: Unreliable communication is not used clinically until repaired or formally restored.
If the Problem Persists
External cables, accessories, approved media, network access, physical ports, and obvious configuration conditions have been ruled out. The remaining cause may involve internal communication hardware, software, approved configuration, interface services, or hospital IT infrastructure.
When the fault compromises required device function, the system should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate manufacturer documentation and approved test equipment
- Repaired or configured only by qualified personnel
Coordinate with hospital IT or interface-support teams when infrastructure or network services are involved. Verify the complete communication path before return to service. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A successful network connection is not enough by itself; verify that the intended patient or procedure data reaches the correct destination.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"OR staff reported that the Cell Saver Elite+ would not transfer case data through the wired network connection."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the Ethernet cable damaged near the equipment connector while the network port tested normally."
Resolution
What action was taken.
Example:
"The cable was replaced with a known-good approved cable, and a test data transfer completed successfully to the expected destination."
Helpful Details to Include (If Known)
- Interface affected
- Barcode scanner condition
- USB media tested
- Ethernet cable and port tested
- Wi-Fi availability
- Device location
- Approved configuration observed
- Known-good substitution
- Destination or interface tested
- Transfer result before and after correction
- Final device status
- Interface affected
- Barcode scanner condition
- USB media tested
- Ethernet cable and port tested
- Wi-Fi availability
- Device location
- Approved configuration observed
- Known-good substitution
- Destination or interface tested
- Transfer result before and after correction
- Final device status
Final Thought
Connectivity problems should be isolated systematically from accessory to cable, port, configuration, and infrastructure before the device itself is blamed. Verify the complete data path and document both the cause and final result.
That is successful troubleshooting.