On this page
Asset Type
Electrocardiograph (EKG) Machine
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed ECG transmission caused by network connection, Wi-Fi coverage, Ethernet cabling, destination availability, device configuration, or infrastructure problems.
Step-by-Step Troubleshooting
1. Protect Patient Care and Preserve the ECG
Do not repeatedly transmit or delete an ECG unless its storage and patient association are understood.
If immediate clinical review is required, use an approved alternate method to deliver the ECG while troubleshooting the network path.
Expected outcome: The diagnostic ECG remains available and patient care is not delayed by the transmission problem.
2. Confirm the Scope of the Failure
Determine whether transmission fails over Wi-Fi, wired LAN, or both. Confirm whether the problem affects one MAC 7, one room, one network segment, or multiple devices.
Note whether ECG acquisition and local storage remain normal.
Expected outcome: The transmission problem is narrowed to the device, connection method, destination, or broader infrastructure.
3. Verify Basic Network Status
Check user-accessible network indicators on the MAC 7.
For Wi-Fi, confirm that the unit is in an area where the approved clinical wireless network is expected to be available. For LAN, confirm that the Ethernet cable is fully seated.
Expected outcome: The intended network connection is present. If connectivity returns after reseating or relocating, retest transmission.
4. Inspect the Ethernet Path When Using LAN
Inspect the network cable for damaged connectors, crushed sections, broken latches, or loose seating.
Substitute a known-good approved cable and, when practical, test from a known-good network port.
Expected outcome: The MAC 7 establishes normal wired connectivity. A failed cable or wall-port issue is isolated without altering device configuration.
5. Check Wi-Fi Conditions When Using Wireless
Determine whether the failure occurs only in one physical area or throughout the facility.
Compare with another known-working MAC 7 or approved wireless device on the same clinical network when available.
Expected outcome: Normal connectivity in another location suggests a coverage or infrastructure problem rather than a device-wide failure.
6. Verify Accessible Network Selection
Confirm that the device is attempting to use the expected authorized network connection.
Do not change IP settings, security parameters, certificates, wireless profiles, or enterprise network configuration without appropriate authorization.
Expected outcome: The MAC 7 is using its intended configured network path.
7. Verify MUSE or Destination Availability
Determine whether other ECG devices can transmit successfully to the same MUSE environment or intended destination.
If several devices are affected simultaneously, involve the appropriate clinical systems, network, or MUSE support team.
Expected outcome: A destination or enterprise outage is distinguished from a failure isolated to one MAC 7.
8. Perform a Controlled Restart When Appropriate
If the network infrastructure is known to be available and the device has lost connectivity, perform a normal restart when the ECG is safely stored and the device is not supporting active patient care.
Expected outcome: Network connection re-establishes and the device can communicate normally.
9. Test End-to-End ECG Transmission
Using approved test data and workflow, acquire or select a non-patient test ECG and transmit it through the intended path.
Verify that transmission completes and, when possible, confirm receipt at the intended system rather than relying solely on a send command.
Expected outcome: The ECG is transmitted and received successfully. Troubleshooting can stop after consistent end-to-end verification.
10. Escalate Persistent Transmission Failure
If the MAC 7 cannot communicate through a known-good network connection while peer devices function normally, stop external troubleshooting.
Expected outcome: The device or its configuration is escalated to qualified Clinical Engineering, IT, MUSE, or manufacturer support as appropriate.
If the Problem Persists
External cabling, network availability, Wi-Fi location, destination status, and basic accessible settings have been addressed. Remaining possibilities include device network hardware, authorized network configuration, certificates or security credentials, MUSE interface configuration, server-side conditions, or other service-level problems.
The device should be:
- Removed from normal network-dependent workflow if reliable transmission cannot be assured.
- Labeled Out of Service if the intended clinical use requires transmission.
- Sent for repair or bench evaluation when a device fault is suspected.
- Evaluated using appropriate manufacturer documentation and approved test equipment.
- Configured only by qualified and authorized personnel.
Coordinate with network or MUSE support when the failure extends beyond the device. Before return to service, verify the complete acquisition-to-destination communication path. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A successful local ECG acquisition does not prove successful archival; verify receipt in the intended MUSE or clinical system whenever resolving a transmission complaint.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the MAC 7 acquired ECGs normally but could not transmit them to MUSE over the wired network."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the Ethernet cable had a damaged connector and the MAC 7 communicated normally when connected with a known-good cable."
Resolution
What action was taken.
Example:
"Replaced the damaged network cable and verified successful end-to-end transmission and receipt of a test ECG in the intended system."
Helpful Details to Include (If Known)
- Wi-Fi, LAN, or both affected.
- Network indicators.
- Location of failure.
- Ethernet cable condition.
- Network port tested.
- Known-good cable or location used.
- Whether other MAC 7 units were affected.
- Whether MUSE was available.
- Transmission result.
- Destination receipt confirmed.
- Final device status.
Final Thought
Treat ECG transmission as an end-to-end workflow. Rule out cables, Wi-Fi conditions, network availability, and destination outages before assuming a MAC 7 hardware failure, and always verify actual receipt before closing the work order.
That is successful troubleshooting.