On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting Corometrics fetal monitors that experience software communication issues or fail to connect properly with central monitoring systems. These problems can prevent real-time monitoring and data transmission. Most often, the causes are external, network-related, or configuration errors rather than internal hardware faults.
Step-by-Step Troubleshooting
Verify Power and Device Status
- Ensure the fetal monitor is powered on and has completed its boot sequence.
- Check for any warning or error lights on the device.
- Why: A device not fully booted cannot communicate with central monitoring.
Check Network Connections
- Confirm the Ethernet cable or Wi-Fi module is securely connected.
- Swap cables or test a known working port if possible.
- Why: Loose or faulty connections are a common cause of central monitoring failures.
Confirm IP and Network Settings
- Ensure the monitor has a valid IP address, subnet, and gateway.
- Verify that the IP is compatible with the hospital network.
- Why: Misconfigured network settings prevent data from reaching the central server.
Ping the Central Monitoring Server
- From the device or a nearby workstation, ping the central monitoring server to check connectivity.
- Why: Confirms if the network path is functional.
Review Software Version and Compatibility
- Check the monitor’s software version against the central monitoring system requirements.
- Update the monitor or server software if a version mismatch exists.
- Why: Incompatibility can prevent successful data transmission.
Check for Active Alarms or Software Errors
- Review the device logs for error codes related to network, server, or software modules.
- Why: Specific codes can guide further troubleshooting or escalation.
Restart Device and/or Central Monitoring Client
- Power cycle the fetal monitor and, if allowed, the central monitoring server software.
- Why: Temporary software glitches often resolve after a controlled restart.
If the Problem Persists
External checks have been completed.
Likely causes: internal software corruption, server-side configuration issues, or hardware network interface failure.
Action:
- Remove the monitor from patient care temporarily.
- Label it Out of Service.
- Escalate to GE Healthcare Service or central IT/network support for in-depth evaluation.
Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never troubleshoot connectivity on a device currently monitoring an active patient.
Move the patient to another verified monitor before performing network or software troubleshooting.
Ensure alarms are always active on the backup device during the swap.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
Central monitoring connection fails; software errors observed; alarms not transmitting.
Cause
What was observed during troubleshooting.
Example:
Network cable found loose; device had incorrect IP configuration; software version incompatible with central server.
Resolution
What action was taken.
Example:
Reconnected network cable, updated IP settings, and verified software version compatibility; monitor successfully communicated with central system.
Helpful Details to Include
- Outlet tested and verified.
- Cables swapped and ports tested.
- Indicator lights and error codes recorded.
- Software versions documented.
- Network ping and connectivity tests results.
Final Thought
Maintaining connectivity between fetal monitors and central monitoring systems is crucial for patient safety. Troubleshooting should follow a logical, external-first approach, ensuring patient care is not interrupted. Proper documentation ensures accountability and aids future troubleshooting efforts. Escalation to specialized service or IT is appropriate when basic checks do not resolve the issue.
That is successful troubleshooting.