Schiller CARDIOVIT AT Series

Asset Type

Electrocardiograph (EKG) Machine

Manufacturer

Schiller

Model

CARDIOVIT AT Series

What This Guide Helps With

Failure to transmit ECGs to EMR, network disconnects, or missing studies due to cable, Wi-Fi, or configuration issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Do not delay ECG acquisition due to connectivity issues
• If needed, print or store the ECG locally

Expected: Patient diagnostics continue without interruption.

Why it matters: Network issues should not delay clinical decision-making.

Verify the Reported Issue

• Confirm ECG saves locally but does not export
• Check for error messages on screen
• Determine if failure is intermittent or complete

Expected: Clear understanding of the failure type.

Why it matters: Helps determine if issue is network, configuration, or workflow-related.

Check Physical Network Connection (Wired Systems)

• Ensure cable is fully seated in device and wall port
• Check for link/activity lights on port
• Swap with a known good Ethernet cable
• Try a different wall port

Expected: Link lights active and stable connection.

Why it matters: Loose or failed cables are a common cause.

Verify Wi-Fi Connection (If Applicable)

• Confirm Wi-Fi is enabled on the device
• Check signal strength
• Reconnect to the correct network
• Ensure correct SSID is selected

Expected: Device shows connected status with adequate signal.

Why it matters: Weak or dropped Wi-Fi prevents data transmission.

Confirm Network Configuration Settings

• Verify IP address is assigned (not 0.0.0.0)
• Check subnet and gateway settings
• Confirm DHCP vs static IP configuration
• Compare with known working unit if available

Expected: Valid network configuration present.

Why it matters: Incorrect settings prevent communication on the network.

Check EMR / Server Configuration Settings

• Verify correct server IP or hostname
• Confirm correct port and protocol (HL7, DICOM, etc.)
• Ensure device is assigned to the correct department/location
• Check device ID or AE title if applicable

Expected: Settings match hospital configuration.

Why it matters: Misconfiguration prevents successful export even with network connection.

Attempt Test Transmission

• Send a test ECG or stored record
• Observe for error messages
• Check for transmission success or failure
• Note any time delays or retries

Expected: Successful transmission without errors.

Why it matters: Confirms whether issue is resolved or persistent.

Check for Network-Wide Issues

• Ask staff if similar issues are occurring
• Check nearby devices on same network
• Contact IT if multiple devices are impacted

Expected: Identify if issue is isolated or system-wide.

Why it matters: Helps differentiate device issue from infrastructure problem.

Power Cycle the Device

• Power off completely
• Wait 10–15 seconds
• Power back on and reconnect

Expected: Network reconnects and export resumes.

Why it matters: Clears temporary communication or software faults.

If the Problem Persists

All common external and configuration-related causes have been ruled out. The issue is likely internal (network interface, mainboard, or software fault).

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

Always complete ECG acquisition first. If the network is down, print or manually upload results to avoid delays in patient care.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"EKG not transmitting studies to EMR; staff reports export failures."

Cause

What was observed during troubleshooting.

Example:
"Misconfigured network settings with incorrect gateway address."

Resolution

What action was taken.

Example:
"Corrected network configuration and verified successful test transmission."

Helpful Details to Include (If Known)

• Ethernet cable tested or swapped
• Wi-Fi signal strength verified
• IP address confirmed
• Error messages observed
• Other devices affected or not
• Test transmission results
• Final device status (working or removed from service)

Final Thought

Effective troubleshooting starts with simple external checks like cables and network status before assuming device failure. Patient care must always come first, and proper escalation ensures safety and efficiency. Clear documentation supports continuity and future troubleshooting.

That is successful troubleshooting.