On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a Mindray TE Series ultrasound system becomes slow, freezes, or stops responding during use.
Common symptoms include:
- Long delays when navigating menus
- System freezing during imaging
- Touch inputs taking several seconds to respond
- System requiring frequent reboots
- Lag when saving images or studies
The guide focuses on basic external checks and system conditions before assuming internal hardware or software failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Verify the system is not actively in use on a patient.
- If the unit froze during a procedure, confirm the patient has been moved to another ultrasound system before proceeding.
- Only begin troubleshooting once patient care is no longer dependent on the affected device.
Perform a Controlled System Reboot
- Many performance issues are temporary software or memory-related.
- Exit any active studies if possible.
- Shut down the system through the software interface.
- Wait about 30 seconds after power down.
- Restart the system.
- Observe whether performance improves after the reboot.
Check for Peripheral Devices Causing Delays
- External accessories can sometimes cause slow performance.
- Inspect connected USB drives.
- Inspect external printers.
- Inspect network cables.
- Inspect ECG modules or other accessories.
- Temporarily disconnect non-essential devices and check if the system response improves.
Verify Available Storage Space
- Ultrasound systems can slow significantly if internal storage becomes full.
- Check local study storage.
- Check image archive space.
- If storage is near capacity, delete unnecessary local studies if policy allows.
- Confirm images are successfully transferring to PACS.
Check Network Connectivity
- Poor or unstable network connections may cause delays when saving studies or communicating with PACS.
- Verify the network cable is securely connected.
- Confirm the system successfully connects to PACS or network services.
- Check for visible network error messages.
- If needed, temporarily disconnect the network cable to determine if the slowdown is network-related.
Observe System Indicators and Behavior
- While operating the system, note any unusual conditions.
- Check for error messages on the screen.
- Listen for excessive fan noise.
- Check for signs of system overheating.
- Note any unexpected application crashes.
- These observations help determine whether the issue is software-related or hardware-related.
Check Probe Connections
- Faulty or intermittently connected probes can cause system instability.
- Disconnect the probe.
- Inspect the probe connector and port for debris or damage.
- Reconnect firmly.
- Test with another probe if available.
Test Basic System Functions
- Verify system responsiveness by performing simple tasks.
- Navigate menus.
- Select probes.
- Freeze and unfreeze imaging.
- Save a test image.
- Determine whether freezing occurs during specific actions or randomly.
Check for Repeated System Freezing
- If the system freezes multiple times during testing, document key details.
- Note what function was being used.
- Note whether a probe was connected.
- Note whether imaging was active.
- Reproducible behavior is useful for vendor support.
If the Problem Persists
If the system continues freezing or performing slowly after these checks, common external causes have likely been ruled out.
The issue may be related to:
- Internal storage failure
- Software corruption
- System memory issues
- Internal hardware faults
At this point the device should be:
- Removed from service
- Labeled Out of Service
- Scheduled for vendor service or bench evaluation
Recognizing when to escalate prevents extended downtime and protects clinical workflow.
Clinical Use Tip
Do not attempt troubleshooting while the ultrasound system is being used on a patient.
If the system freezes during an exam, the patient should be moved to another ultrasound unit first. Troubleshooting should only begin once patient care is no longer dependent on the affected device.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“User reported the ultrasound system was freezing during exams and taking a long time to respond to touch input.”
Cause
What was observed during troubleshooting.
Example:
“System storage found nearly full with large number of locally stored studies, contributing to slow system performance.”
Resolution
What action was taken.
Example:
“Unnecessary local studies were cleared per department policy, system rebooted, and normal performance restored.”
Helpful Details to Include (If Known)
- Outlet tested
- Power cable secure
- USB devices removed or tested
- Network cable checked
- Storage space verified
- Error messages observed
- Probe connections inspected
- System reboot performed
- System response after reboot
- Final device status (returned to service or sent for repair)
Final Thought
Effective troubleshooting begins with simple, logical checks before assuming internal failure. Verifying power, storage capacity, network connectivity, and connected accessories can resolve many system performance issues quickly. When the problem persists after these checks, removing the device from service and escalating for repair ensures both patient safety and reliable equipment availability.
That is successful troubleshooting.