Mindray BeneVision N Series

Asset Type

Patient Monitor

Manufacturer

Mindray

Model

BeneVision N Series

What This Guide Helps With

This guide helps troubleshoot the CMS/eGW Disconnected alarm on the Mindray BeneVision N Series patient monitor. This alarm means the bedside monitor has lost communication with the central monitoring system or eGateway. The monitor may still function locally at the bedside, but patient data may not be visible at the central station.

This can affect central monitoring visibility, alarm awareness, patient tracking, and clinical workflow. The goal is to confirm patient safety first, then check the most common external causes such as network cable connection, wall jack, monitor assignment, and central station communication.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Confirm the patient is being monitored safely at the bedside.
• Verify that waveforms, numerics, and local alarms are still active on the BeneVision monitor.
• Notify clinical staff that central monitoring may not be receiving live data from this monitor.
• If the patient requires continuous central monitoring and communication cannot be restored quickly, move the patient to another verified monitored bed or use another known-good monitor.
• Do not assume the central station is receiving patient data until live communication is confirmed.

Verify the Reported Alarm and Behavior

• Confirm the exact alarm displayed is CMS/eGW Disconnected.
• Check whether the alarm appears at startup, after moving the monitor, after docking, after network cable removal, or intermittently.
• Ask staff whether the patient is missing from the central station, showing stale data, or showing as disconnected.
• Confirm whether the issue affects one monitor, one room, or multiple beds on the unit.

Confirm the Bedside Monitor Is Working Locally

• Verify active parameters such as ECG, SpO2, NIBP, invasive pressure, temperature, EtCO2, or other monitored values.
• Confirm local audible and visual alarms work at the bedside.
• Check that the monitor responds normally to touch, buttons, menus, and alarm controls.
• If the monitor is frozen, rebooting, or not displaying parameters, treat that as a monitor function issue instead of only a CMS/eGW communication issue.

Check the Network Cable Connection

• Inspect the Ethernet/network cable connected to the monitor, docking station, wall jack, or network adapter.
• Make sure the cable is fully seated on both ends.
• Look for a loose connector, broken locking tab, stretched cable, damaged jacket, bent connector, or cable strain.
• If the monitor is docked, confirm the monitor is seated correctly in the dock.
• Reseat the cable and allow time for the monitor to re-establish communication.

Check the Network Wall Jack or Port

• Confirm the network cable is connected to the correct wall jack.
• Check whether the jack is labeled for patient monitoring or medical device network use.
• Avoid using unknown or general-purpose network jacks unless approved by the facility configuration.
• If available, test the monitor on another known-good patient monitoring network jack.
• If the issue stays with the room, suspect the wall jack, network switch port, VLAN assignment, or network path.

Replace the Network Cable With a Known-Good Cable

• Swap the current Ethernet cable with a known-good cable approved for clinical use.
• Reconnect the monitor and allow time for network communication to recover.
• Check whether the CMS/eGW Disconnected alarm clears.
• If the alarm clears after replacing the cable, remove the bad cable from service.

Confirm Central Station Visibility

• Check the central monitoring station after the bedside alarm clears.
• Confirm the correct bed, patient, waveforms, numerics, and alarms are visible.
• Verify that the data is live and updating, not frozen or stale.
• Ask clinical staff to confirm the patient is visible in the expected location.
• Do not return the monitor to normal use until central station communication is confirmed.

Check for Recent Monitor Movement or Bed Assignment Changes

• Ask whether the monitor was recently moved from another room, dock, or network location.
• Confirm the monitor is assigned to the correct bed, room, care area, and patient.
• Check whether the patient was recently admitted, discharged, transferred, or reassigned.
• Correct any assignment mismatch according to facility workflow.

Restart the Monitor Only If Clinically Safe

• Confirm with clinical staff that restarting the monitor is safe.
• Move the patient to alternate monitoring first if needed.
• Restart or power cycle the monitor according to facility workflow.
• After restart, verify bedside monitoring first, then confirm central station communication.
• If the alarm returns after restart, continue isolation steps instead of repeatedly rebooting the device.

Isolate Monitor, Dock, Room, or Network Cause

• Connect the monitor to a known-good patient monitoring network location if available.
• Check whether the CMS/eGW Disconnected alarm follows the monitor.
• If available, connect another known-good monitor to the same wall jack and cable path.
• If the issue follows the monitor, suspect monitor configuration, dock communication, network interface, or internal communication fault.
• If the issue stays with the room, suspect wall jack, switch port, VLAN/configuration, or network infrastructure.

Check for a Broader CMS/eGW or Network Issue

• Ask clinical staff whether other beds are also disconnected.
• Check nearby monitors on the same unit.
• Contact Clinical Engineering, IT, central monitoring support, or the vendor if multiple devices are affected.
• Verify whether CMS, eGateway, network switch, server, or planned maintenance activity is involved.

If the Problem Persists

If the CMS/eGW Disconnected alarm remains after checking the network cable, known-good cable, wall jack, monitor assignment, central station visibility, restart, and alternate network location, external and common causes have been ruled out.

Persistent disconnection may indicate a faulty network path, bad wall jack, incorrect network configuration, docking station communication issue, monitor network interface issue, or CMS/eGateway communication problem.

Remove the monitor from central-monitoring-dependent use if reliable CMS/eGW communication cannot be restored. Label the device Out of Service if the issue appears monitor-related. Escalate to Clinical Engineering, IT/network support, central monitoring support, or the vendor as appropriate. Send the monitor or dock for repair or bench evaluation if the problem follows the device.

Clinical Use Tip

Never troubleshoot this alarm while assuming the central station is still seeing the patient. Verify local bedside monitoring first. If central monitoring is required and the connection cannot be restored quickly, move the patient to a backup monitor or verified monitored bed before continuing troubleshooting.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Mindray BeneVision N Series patient monitor displayed CMS/eGW Disconnected alarm. Staff reported the patient was not visible at the central station."

Cause

What was observed during troubleshooting.

Example:
"Monitor continued local bedside monitoring, but CMS/eGW communication was lost. Network cable, wall jack, monitor assignment, and central station visibility were checked."

Resolution

What action was taken.

Example:
"Verified patient remained monitored locally. Reseated network cable, replaced Ethernet cable with known-good cable, and confirmed live waveforms and numerics were restored at the central station. Monitor returned to service."

Helpful Details to Include (If Known)

• Alarm behavior
• Accessories swapped
• Power behavior
• Environmental factors
• Indicator lights
• Final device status

Final Thought

A CMS/eGW Disconnected alarm should be handled as a patient visibility and communication issue first. Protect the patient, verify bedside monitoring, check simple network causes, confirm live central station data, and escalate when the issue points beyond the bedside setup. Clear documentation helps separate cable, room network, configuration, dock, monitor, and CMS/eGateway failures.

That is successful troubleshooting.