On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots failed USB export or external storage caused by media compatibility, connection, file workflow, device condition, storage capacity, or port problems.
Step-by-Step Troubleshooting
1. Protect Patient Data
Do not delete locally stored patient images simply because export has failed.
Follow facility privacy, cybersecurity, and approved removable-media policies when using external storage.
Expected outcome: Patient data remains preserved and only approved storage media is used.
2. Confirm the Exact Export Complaint
Determine whether:
- USB device is not recognized
- Export begins but fails
- Export completes but files are absent
- Only certain studies fail
- One USB device fails while another works
- All external storage devices fail
- The USB port is physically loose or damaged
Expected outcome: The problem is clearly defined as media recognition, export workflow, file creation, or physical connection failure.
3. Inspect the USB Port and External Media
Inspect externally without inserting tools.
Look for:
- Bent or damaged port structure
- Debris
- Liquid contamination
- Loose connector fit
- Cracked USB device
- Damaged connector
Expected outcome: The port and media are visibly intact and safe to use. Physical damage requires removal from service or escalation as appropriate.
4. Verify the Media Is Approved for Use
Confirm the USB device meets facility cybersecurity and device-use requirements.
Avoid unknown, personal, or unapproved removable media.
Expected outcome: An approved external storage device is used for testing.
5. Reconnect the USB Device
Remove and reconnect the media using the normal USB interface.
Allow the system time to detect the device before attempting export.
Expected outcome: The storage device is recognized. If recognition returns and export works, continue to final verification.
6. Check External Storage Capacity
If user-accessible information is available, determine whether the external storage device has sufficient available capacity.
Do not delete existing data unless authorized.
Expected outcome: Adequate storage exists for the intended export.
7. Test With a Known-Good Approved USB Device
Use a known-good approved device with available capacity.
Expected outcome: If the known-good media works, the original USB device is the likely cause. If neither works, continue evaluating the PX port and workflow.
8. Verify Local Image Storage First
Confirm the intended images or study exist locally on the PX before troubleshooting export.
Expected outcome: The source data is present and available for export. Missing local images indicate a capture/storage issue rather than USB export failure.
9. Verify the Correct Export Workflow
Confirm the intended study or images are selected and the normal export destination is chosen.
Do not change protected data-management configuration.
Expected outcome: The system initiates the export to the selected external storage device.
10. Test Another Accessible USB Port if Applicable
If the PX configuration provides another approved accessible USB interface intended for storage, compare behavior.
Expected outcome: The failure is isolated to one external connection or shown to affect USB storage generally.
11. Perform a Controlled Restart
If media and workflow are correct but recognition remains abnormal, safely remove the USB device and restart the system.
Reconnect approved media after normal startup.
Expected outcome: The device is recognized and export succeeds.
12. Verify the Exported Data
After a successful export:
- Confirm export completes without error
- Safely remove the storage device according to the normal workflow
- Verify the expected files are present using an approved facility computer or workflow when permitted
- Protect patient information throughout verification
Expected outcome: The expected data is successfully exported and retrievable. Troubleshooting can stop once reliable export is confirmed.
If the Problem Persists
If approved media, available capacity, local image availability, USB connection, alternate media, workflow, and restart have been ruled out, the remaining cause may involve the USB interface, internal storage, software, system configuration, or another service-level fault.
The system should be:
- Removed from service if USB export is required for the clinical workflow and no approved alternative exists
- Labeled Out of Service when appropriate
- Sent for repair or bench evaluation
- Evaluated using appropriate Fujifilm SonoSite documentation and approved test equipment
- Repaired or configured only by qualified personnel
Do not open the system or attempt internal USB-port or board repair without authorized procedures.
After repair, verify local storage, USB recognition, export, and file retrieval before return to service.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
Treat removable media as part of the patient-data chain; use only approved devices and verify the export before removing or deleting source images.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the SonoSite PX would not recognize the USB drive used for approved image export."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the original USB device was not recognized, while a known-good approved USB device was detected and exported normally."
Resolution
What action was taken.
Example:
"Replaced the failed external storage media, verified export and retrieval of a test study, and returned the system to service."
Helpful Details to Include (If Known)
- USB device type
- Facility approval status
- Port used
- Port condition
- Media capacity
- Whether local images were present
- Known-good media result
- Alternate port result
- Export message or behavior
- Restart result
- Exported files verified
- Final device status
Final Thought
USB export problems should be separated into local storage, media, port, and workflow causes before internal failure is assumed. Preserve patient data and verify the completed export before closing the work order.
That is successful troubleshooting.