On this page
Asset Type
Electrocardiograph (EKG) Machine
Manufacturer
Model
What This Guide Helps With
Failure to transmit ECG data to EMR, network disconnection, or communication errors caused by cables, settings, or configuration issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not delay patient care due to connectivity issues. Complete ECG acquisition and print or store locally if needed.
Expected: Patient diagnostics continue without interruption.
Why it matters: Network issues should not impact immediate clinical decisions.
Verify the Reported Issue
- Confirm what is failing.
- Check if the ECG is saving locally but not transmitting.
- Check for error messages.
- Determine if the issue is intermittent or constant.
Expected: Clear understanding of failure type.
Why it matters: Determines whether issue is network, configuration, or workflow related.
Check Physical Network Connection
- Ensure cable is fully seated in the ECG and wall port.
- Check for link/activity lights at the port.
- Swap with a known good Ethernet cable.
Expected: Link lights active and stable connection.
Why it matters: Loose or faulty cables are a common cause of connectivity failure.
Verify Network Port and Wall Jack
- Test the wall port with another network device (laptop or known working device).
- Try a different known working network jack.
Expected: Verified active network port.
Why it matters: Dead or misconfigured ports will prevent communication regardless of device condition.
Check Device Network Settings
- Confirm IP address is assigned (not blank or incorrect range).
- Verify DHCP vs static configuration matches facility setup.
- Confirm gateway and subnet settings.
Expected: Valid network configuration.
Why it matters: Incorrect settings prevent the device from reaching the EMR network.
Confirm EMR/Server Configuration
- Check server/IP address or hostname entered in the ECG.
- Confirm correct port and communication protocol.
- Ensure device is properly registered in the system.
Expected: Correct EMR/server configuration.
Why it matters: Even with network connectivity, incorrect destination settings will block transmission.
Restart the Device
- Power off the ECG.
- Wait 10–15 seconds.
- Power back on and allow full startup.
Expected: Network reconnects after reboot.
Why it matters: Clears temporary communication or software faults.
Check for Network-Wide Issues
- Ask staff if other ECGs or devices are failing to connect.
- Check central system or IT alerts.
Expected: Identification of isolated vs widespread issue.
Why it matters: Helps determine if escalation should go to IT/network instead of device repair.
Test Data Transmission
- Attempt to send a test ECG.
- Observe for successful transmission, errors, or delays.
Expected: Successful export to EMR.
Why it matters: Confirms resolution or persistent failure.
If the Problem Persists
If all external connections, settings, and network conditions have been verified, the issue is likely internal (network interface or communication hardware/software).
Remove the device from service, label it Out of Service, and send for repair or further bench evaluation.
Knowing when to stop prevents unnecessary risk and wasted troubleshooting time.
Clinical Use Tip
Never delay patient diagnosis due to connectivity issues. Always print or locally store ECGs and ensure results are available to clinicians.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"ECG not transmitting results to EMR."
Cause
What was observed during troubleshooting.
Example:
"Loose Ethernet cable at device port causing intermittent network connection."
Resolution
What action was taken.
Example:
"Reseated and secured network cable; verified successful ECG transmission."
Helpful Details to Include (If Known)
- Ethernet cable condition and swap performed
- Network port tested and verified active
- IP address and configuration verified
- Error messages displayed
- Other devices affected or not
- Successful/failed test transmission
- Final device status
Final Thought
Network troubleshooting should always start with simple, external checks before assuming device failure. Maintaining patient care, verifying connectivity step-by-step, and escalating appropriately ensures safe and efficient resolution.
That is successful troubleshooting.