On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses failures in event data storage, memory errors, or inability to export/download event logs to external software.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the AED is not in active clinical use. Move the patient to another device if necessary before troubleshooting.
Check Device Power
- Verify the battery is fully charged and seated correctly. Low power can cause memory write errors. Expected outcome: device powers on and self-tests without battery warnings.
Inspect Memory/SD Card Access (if applicable)
- Check that any removable memory card or USB/data interface is properly seated, undamaged, and free of debris. Outcome: card recognized by device or software.
Attempt Data Download via Manufacturer Software
- Connect the device to a known working computer using the recommended Cardiac Science software and cables. Outcome: event logs appear in the software.
Verify Software/Driver Updates
- Confirm that the AED software and computer drivers are up to date. Outdated software can prevent proper communication. Expected outcome: device recognized, download initiated successfully.
Test with Alternate Computer or Port
- Use a different USB port or computer to rule out local PC issues. Outcome: successful recognition and download of event data.
Check for Device Error Messages or Logs
- Review AED screen for any error codes related to memory, storage, or communication. Outcome: note codes for documentation or escalation.
If the Problem Persists
If all external checks are complete and errors remain:
- Remove the device from service.
- Label “Out of Service.”
- Send to manufacturer service or qualified repair bench for internal evaluation.
Knowing when to stop prevents potential data loss or device damage.
Clinical Use Tip
Do not attempt troubleshooting during patient use. Ensure event data is backed up before attempting any memory operations.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"AED failed to download event logs; memory errors displayed."
Cause
What was observed during troubleshooting.
Example:
"Memory access or data communication error identified during troubleshooting."
Resolution
What action was taken.
Example:
"Device removed from service and sent for bench evaluation; software attempted on alternate PC without success."
Helpful Details to Include (If Known)
- Device battery status
- Software version and connection method
- Any displayed error codes
- Attempts on multiple computers or ports
- Final device status (OOS)
Final Thought
Logical troubleshooting ensures patient safety and protects critical event data. Follow manufacturer guidance and escalate when memory errors persist, documenting all actions thoroughly.
That is successful troubleshooting.