On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed rescue-event exports caused by USB media, file compatibility, device access, software, computer security, or connection problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform data-export troubleshooting while the ZOLL AED 3 is assigned as the only available AED for an active patient-care area.
Before beginning:
- Confirm another verified AED is immediately available.
- Ensure the AED 3 remains operational and displays its normal ready status.
- Do not remove the battery, pads, or essential accessories solely to retrieve event data.
- Follow facility procedures for preserving post-rescue clinical information.
Expected outcome: Emergency-response coverage remains available while the device is being evaluated.
Continue only after the AED can be safely removed from active readiness.
2. Confirm the Exact Failure
Determine which part of the process is unsuccessful:
- The USB drive is not recognized.
- The export option is unavailable.
- No rescue event appears for selection.
- The export begins but does not complete.
- A file is created but cannot be opened.
- RescueNet EventSummary does not detect or import the exported information.
- The computer blocks access to the USB drive.
Record any displayed message and whether the problem occurs with every event or only one rescue record.
Expected outcome: The failure is isolated to the AED, USB media, exported file, computer, or review software.
3. Verify the AED Is in the Correct Non-Rescue Mode
Confirm the AED is not in active rescue operation and that Clinical Engineering has entered the appropriate maintenance or data-access function using authorized facility procedures.
Do not attempt to export information while:
- The pads are connected to a patient.
- A rescue sequence is active.
- The AED is performing a self-test.
- The device is displaying another unresolved fault.
Expected outcome: The appropriate data-management options become available.
If the export option remains unavailable, stop and verify authorized access requirements before proceeding.
4. Inspect the USB Port and Drive
Remove the USB drive and inspect:
- The USB connector for bending, contamination, or physical damage.
- The AED USB port for debris, looseness, or damaged contacts.
- The drive housing for cracks or signs of liquid exposure.
- Whether the drive seats fully without excessive force.
Do not insert tools into the AED USB port or attempt to straighten internal contacts.
Reconnect the drive firmly and retry the export.
Expected outcome: The AED recognizes the USB device and permits the export.
If successful, verify the exported file before returning the AED to service and stop troubleshooting.
5. Test With an Approved Compatible USB Drive
Use a known-good, facility-approved USB flash drive that:
- Has adequate free storage space.
- Is not write-protected.
- Is free of unrelated sensitive information.
- Uses a file-system format supported by the facility’s ZOLL data-export process.
- Has been approved under hospital cybersecurity and removable-media policies.
Avoid USB hubs, card readers, encrypted drives, adapters, and drives containing bundled security software unless specifically approved.
Retry the export using the known-good drive.
Expected outcome: The event exports successfully, identifying the original USB drive as incompatible, full, corrupted, or defective.
If successful, remove the failed media from use and stop troubleshooting.
6. Confirm That a Rescue Event Is Stored
Review the AED’s available event information using the authorized data-access process.
Consider whether:
- The reported activation actually progressed far enough to create a rescue record.
- A newer event may have affected storage availability.
- The incorrect date or event was selected.
- Event information was previously exported or managed under local procedures.
- The AED’s date and time could make the event appear under an unexpected timestamp.
Do not erase, reset, or overwrite event information while investigating a download complaint.
Expected outcome: The required rescue event is located and selected for export.
If no event is available, document that finding and escalate before performing any action that could alter stored data.
7. Verify the Exported Files on a Computer
After the AED reports a completed export:
- Use the operating system’s safe-removal process before disconnecting the USB drive.
- Connect the drive to an approved hospital computer.
- Confirm that files or folders were created.
- Compare the file date and time with the rescue event.
- Copy the files to the approved secure location before analysis.
- Do not rename, modify, or open the source files with unrelated applications.
The ZOLL AED 3 supports rescue-data review through ZOLL RescueNet EventSummary, and ZOLL identifies USB as a supported method for exporting detailed rescue information.
Expected outcome: The exported files are present, readable, and associated with the correct rescue event.
If the USB drive is empty despite a completed-export indication, repeat the export once using a different approved drive.
8. Check RescueNet EventSummary and Computer Compatibility
Confirm that the receiving computer:
- Has an approved version of RescueNet EventSummary installed.
- Recognizes the USB drive normally.
- Allows access to removable media.
- Has sufficient local storage.
- Is not blocking the file through endpoint-security software.
- Is being used under an account with the required permissions.
Attempt to import the same file on another approved computer with known-good RescueNet EventSummary software.
ZOLL’s current RescueNet EventSummary download page lists support for the ZOLL AED 3 product family.
Expected outcome: The event opens on the alternate workstation, identifying the original computer, application installation, permissions, or security controls as the cause.
If the file cannot be opened on more than one approved workstation, preserve the original exported files and continue to escalation.
9. Restart and Recheck the AED
After confirming that no patient is connected and no export is in progress:
- Exit the data-access function normally.
- Turn the AED off.
- Remove the USB drive.
- Wait briefly.
- Restart the AED according to normal operating procedures.
- Confirm the normal ready indication.
- Reenter the authorized data-access function and retry with a known-good USB drive.
Do not remove the battery as a reset method unless directed by approved service documentation or ZOLL technical support.
Expected outcome: A temporary software or USB-enumeration condition clears and the export completes.
If the AED displays a readiness failure, startup error, or abnormal indicator after restarting, remove it from service.
If the Problem Persists
If the AED cannot recognize multiple approved USB drives, cannot locate a known rescue event, repeatedly produces unreadable files, or fails export on multiple approved computers, common external causes have been ruled out.
The problem may involve the AED’s USB interface, stored-event database, software, or internal data-management circuitry.
The device should be:
- Removed from service.
- Labeled Out of Service.
- Replaced with another verified AED.
- Sent for authorized repair or bench evaluation.
- Referred to ZOLL technical support when rescue-data recovery is required.
Preserve all original USB files and document every attempted export. Do not initialize, erase, reformat, update, or reset the AED when doing so could affect rescue-event evidence.
Knowing when to stop protects both emergency readiness and the integrity of the clinical record.
Clinical Use Tip
Do not delay patient care, post-event replacement coverage, or required clinical reporting while troubleshooting a data export. Move the AED to a controlled area only after another verified AED is available.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical Engineering was notified that the ZOLL AED 3 would not export the most recent rescue event to a USB flash drive."
Cause
What was observed during troubleshooting.
Example:
"The original USB drive was not recognized by the AED, while a facility-approved known-good drive was detected and completed the export normally."
Resolution
What action was taken.
Example:
"Exported and verified the rescue-event files using an approved USB drive, confirmed the AED’s ready status, and removed the defective drive from service."
Helpful Details to Include (If Known)
- AED ready-indicator status
- Exact export message
- Rescue-event date and time
- Whether the event appeared in the AED
- USB drive manufacturer and capacity
- Available USB storage space
- Whether another USB drive was tested
- Whether files appeared on the drive
- RescueNet EventSummary version
- Computer or workstation tested
- Endpoint-security or permission messages
- Whether another computer opened the file
- Final device status
- Location of securely preserved event files
Final Thought
Patient readiness and rescue-data integrity are equally important. Check authorized access, USB media, stored events, computer compatibility, and review software logically before suspecting an internal failure. Escalate without altering the original data when recovery remains unsuccessful, and document the complete process.
That is successful troubleshooting.