On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies causes of freezing, unresponsive software, or failed data synchronization due to connectivity, software state, storage, or external communication issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the device is not actively being used on a patient.
- Ensure all completed tests are saved locally before proceeding.
Verify the Reported Behavior
- Determine if the issue is:
- Complete device freeze
- Slow or intermittent response
- Sync failure with EMR or PC
- Attempt to reproduce the issue.
Perform a Controlled Restart
- Turn off the device.
- Wait 10–15 seconds.
- Restart the device.
- If connected to a PC or tablet, restart that system as well.
Check Device Storage Capacity
- Review available storage on the device.
- Delete old or transferred test data if storage is near capacity.
Verify Connectivity (USB / Bluetooth / Wireless)
- Check USB cable is fully seated and undamaged.
- Confirm Bluetooth or wireless connection is active.
- Ensure correct device is paired or selected.
- Reconnect or re-pair if needed.
Confirm Receiving System Status (PC / EMR / App)
- Ensure software/application is open and responsive.
- Verify correct patient/session is selected.
- Check for system freeze or crash on receiving side.
- Restart application if needed.
Check Software Version and Updates
- Verify device and associated software are up to date per facility standards.
Inspect for Environmental or Usage Factors
- Check for excessive device heat.
- Identify long continuous use without restart.
- Look for wireless interference if applicable.
- Allow device to cool or relocate if needed.
If the Problem Persists
If freezing or sync errors continue after completing these steps, external causes have been ruled out. The issue is likely internal (software corruption, memory fault, or communication hardware failure).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Do not troubleshoot software or sync issues during an active patient test. Move the patient to a functioning device first to maintain testing continuity and prevent data loss.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Device freezing during testing and unable to sync results to EMR."
Cause
What was observed during troubleshooting.
Example:
"Device storage near capacity and intermittent Bluetooth connection."
Resolution
What action was taken.
Example:
"Cleared stored data, re-paired device, and restored normal operation."
Helpful Details to Include (If Known)
- Storage capacity checked and cleared
- Restart performed (device and PC)
- Connection type verified (USB/Bluetooth)
- Software/application status confirmed
- Sync behavior observed (fail vs intermittent)
- Any error messages displayed
- Final device status (returned to service or removed)
Final Thought
Software and communication issues are often caused by simple external factors like storage, connections, or system state. A structured approach prevents unnecessary escalation while protecting patient data and workflow.
That is successful troubleshooting.