On this page
Asset Type
Electrocardiograph (EKG) Machine
Manufacturer
Model
What This Guide Helps With
Identifies external causes of network or EMR connectivity failure, including cables, switches, network settings, EMR interface configuration, and software updates.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm no patient is actively undergoing an EKG procedure.
- Expected outcome: Safe environment to troubleshoot without affecting patient care.
Verify Power and Device Status
- Ensure the EKG machine is powered on, battery is charged (if applicable), and no warning lights indicate system errors.
- Expected outcome: Device is operational and ready to connect.
Check Physical Network Connections
- Inspect the Ethernet cable or Wi-Fi connection. Swap cables or test with a known-good port if needed.
- Expected outcome: Solid physical connection; link lights on Ethernet port should be active.
Confirm Network Access
- Ping the device from the hospital network or attempt to access the EMR server from another workstation.
- Expected outcome: Network is reachable; if not, escalate to IT/network support.
Verify EMR Configuration
- Check the device’s network settings, EMR interface settings, and IP addresses. Confirm they match hospital network requirements.
- Expected outcome: Correct configuration; misconfigurations may prevent data transfer.
Restart EKG and Network Equipment
- Power-cycle the EKG machine, connected switches, or routers. Temporary software or network glitches often resolve with a restart.
- Expected outcome: Connectivity restored without further intervention.
Test with EMR/Network Export
- Perform a test EKG export to EMR or network location. Confirm successful data transfer.
- Expected outcome: Data is sent and received correctly.
If the Problem Persists
External causes have been ruled out. Likely internal network interface or software failure.
- Remove the device from service.
- Label Out of Service.
- Send for bench evaluation or manufacturer service.
Knowing when to stop prevents unnecessary risk and preserves patient safety.
Clinical Use Tip
Do not attempt network troubleshooting on a patient-attached device. Move the patient to another functioning EKG before testing connectivity.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"EKG machine will not send data to EMR."
Cause
What was observed during troubleshooting.
Example:
"Ethernet cable was loose; IP configuration mismatch on device."
Resolution
What action was taken.
Example:
"Secured cable and updated device network settings; verified successful EMR data transfer."
Helpful Details to Include (If Known)
- Ethernet/Wi-Fi tested
- Switch/port checked
- IP address configuration verified
- EMR interface settings confirmed
- Test export successful
- Device operational status confirmed
Final Thought
Patient safety is the priority. Start with external checks, use logical troubleshooting, escalate appropriately, and document every action. Proper steps reduce downtime and prevent patient care disruption.
That is successful troubleshooting.