On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting missing network connectivity, failed data export, or unavailable central monitoring caused by cables, ports, configuration, network, or receiving-system problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform extended network troubleshooting while the WATO EX Series machine is supporting an active patient.
If communication fails during a procedure:
- Notify the anesthesia provider.
- Confirm that ventilation, gas delivery, alarms, and required measurements remain available locally.
- Use approved independent monitoring and downtime documentation procedures.
- Move the patient to another verified anesthesia machine if local therapy, alarms, or monitoring are also affected.
Expected outcome: Patient care remains supported by local equipment and does not depend on the failed network connection.
Continue troubleshooting only when the machine can be evaluated without disrupting patient care.
2. Identify the Exact Communication Failure
Determine which function is affected:
- No connection to the central monitoring system
- Missing patient or waveform information
- Data not reaching the anesthesia record
- Failed data export
- Intermittent connection
- Connection available but assigned to the wrong bed or patient
- Network status or communication error displayed
Record the complete message, affected destination, and time of failure.
Expected outcome: The failure is narrowed to the anesthesia machine, network pathway, or receiving system.
3. Confirm Local Machine Operation
Verify that the WATO EX Series machine:
- Starts normally
- Displays locally measured parameters
- Produces expected alarms
- Responds to controls
- Has no unrelated system fault
- Has the correct date and time
A network failure alone should not be treated as evidence that ventilation or gas delivery has failed.
Expected outcome: Local clinical functions operate normally, isolating the problem to communication or data transfer.
4. Inspect the Network Cable and Connection
Inspect the Ethernet cable from the anesthesia machine to the wall jack, network switch, interface device, or integration gateway.
Check for:
- Loose connectors
- Broken locking tabs
- Damaged insulation
- Bent connector contacts
- Excessive tension
- Improvised couplers or adapters
- Connection to an incorrect wall jack
Disconnect and firmly reseat both ends when safe.
Expected outcome: The cable is secure and physically undamaged. If communication returns, verify stable operation and stop.
5. Check Network Port Indicators
Observe the link and activity indicators at the anesthesia machine, wall interface, switch, or approved network adapter when visible.
- No link light may indicate a disconnected cable, failed cable, disabled port, or inactive network jack.
- A link light without activity may indicate a configuration, routing, or receiving-system problem.
- Intermittent indicators may suggest a loose connection or damaged cable.
Do not interpret indicator behavior as proof that clinical data is reaching its destination.
Expected outcome: Physical network-link status is documented.
6. Test With a Known-Good Approved Network Cable
Replace the existing Ethernet cable with a known-good cable of the correct type and rating.
Do not permanently exchange cables between active patient-care devices without maintaining proper identification and infection-control practices.
Expected outcome: If communication returns, replace the defective cable, confirm reliable data transfer, and stop.
7. Verify the Network Jack or Switch Port
When permitted by facility policy:
- Test the wall jack with an approved network tester.
- Confirm the jack is assigned to the correct medical-device network.
- Check whether the associated switch port is active.
- Compare the connection with a nearby functioning WATO EX Series machine using an equivalent network path.
Do not connect the anesthesia machine to an unapproved or general-purpose network.
Expected outcome: The physical network pathway is confirmed active and correctly assigned.
8. Verify Communication and Network Settings
Review accessible communication settings without changing values unless the correct configuration is documented.
Confirm, as applicable:
- Wired network is enabled.
- The correct interface or destination is selected.
- IP address information is present.
- Subnet mask and gateway match facility records.
- The device is not reporting a duplicate-address conflict.
- The correct central station, server, gateway, or data-export destination is configured.
- Bed, room, device, and department assignments are correct.
Settings and available interfaces can vary among WATO EX models, software revisions, and installed options.
Expected outcome: Configuration matches the hospital’s approved integration documentation.
9. Check for Duplicate or Incorrect Network Identity
Compare the machine’s approved network information with Clinical Engineering or Information Technology records.
Look for:
- Duplicate IP address
- Incorrect static IP address
- Incorrect hostname
- Wrong VLAN assignment
- Unrecognized device identity
- Recently replaced controller or network hardware
- Configuration copied from another anesthesia machine
Do not randomly assign a new address.
Expected outcome: The machine has a unique and approved network identity.
10. Confirm Patient, Bed, and Central-Station Assignment
Verify that:
- The correct patient is admitted or associated.
- The correct bed or room is selected.
- The central station is monitoring the intended location.
- The machine is not still associated with a previous room or patient.
- The destination system recognizes the anesthesia machine.
A working network connection can still appear unsuccessful when the device is assigned incorrectly.
Expected outcome: Device, patient, and location assignments agree across connected systems.
11. Check the Receiving System
Determine whether other networked devices are communicating with the same:
- Central monitoring station
- Anesthesia information management system
- Electronic medical record interface
- Integration server
- Data-export destination
- Network segment
If several devices are affected, the failure is more likely outside the WATO EX Series machine.
Expected outcome: The problem is isolated to one anesthesia machine or identified as a broader network or server issue.
12. Check Interface Equipment and Gateways
Inspect any approved interface device between the anesthesia machine and the destination system.
Verify:
- Power is present.
- Cables are secure.
- Status indicators are normal.
- The device has not been disconnected or relocated.
- No obvious fault or communication alarm is present.
Do not reset shared gateways or interface servers without coordinating with Information Technology and affected clinical departments.
Expected outcome: External interface equipment is operational or identified as the source of the failure.
13. Perform a Controlled Restart When Appropriate
After the machine is removed from patient use and clinical data has been preserved:
- Shut down the anesthesia machine using the normal procedure.
- Allow the shutdown to complete.
- Confirm network connections remain secure.
- Restart the machine.
- Allow sufficient time for network services and connected systems to reconnect.
Do not repeatedly power-cycle the machine.
Expected outcome: Communication initializes normally. If the connection returns, verify data at the receiving system and stop.
14. Verify Communication With a Controlled Test
Use a simulator or approved test setup to generate recognizable nonpatient data.
Confirm that:
- The machine displays the test values locally.
- The correct device appears at the central station.
- Values and waveforms reach the intended destination.
- Patient and bed assignments remain correct.
- Connection remains stable.
- Exported data has the correct date and time.
Mindray identifies the WATO EX-65 as compatible with its BeneVision central monitoring environment, but actual communication capabilities depend on installed options and facility integration.
Expected outcome: End-to-end communication is confirmed before the machine is returned to service.
If the Problem Persists
If the network cable, wall jack, port status, configuration, device identity, receiving system, and external interfaces have been checked, common external causes have been ruled out.
The problem may involve:
- Internal network-interface hardware
- Software or licensing configuration
- Corrupted communication settings
- An incompatible software revision
- A failed integration component
- An internal controller or communication-board fault
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Escalated to Mindray technical support, Information Technology, or the integration vendor as appropriate
Do not perform board-level repair or undocumented software changes. Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
A failed central-monitoring or data-export connection does not eliminate the need for continuous local monitoring. Never troubleshoot communication at the expense of ventilation, gas delivery, alarms, or patient observation. Do not troubleshoot on an active patient. Move the patient to a verified backup device first when therapy continuity or required monitoring could be affected.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Anesthesia staff reported that the WATO EX Series machine was not transmitting patient parameters to the central monitoring station."
Cause
What was observed during troubleshooting.
Example:
"Found a damaged Ethernet cable with no network link indication between the anesthesia machine and the assigned wall jack."
Resolution
What action was taken.
Example:
"Replaced the cable with an approved known-good cable, confirmed stable network link, and verified simulated parameters at the correct central station before returning the machine to service."
Helpful Details to Include (If Known)
- Exact communication error or reported symptom
- Local monitoring remained operational
- Date and time settings verified
- Ethernet cable inspected and reseated
- Known-good cable tested
- Network-link indicators observed
- Wall jack or switch port tested
- IP address and network identity verified
- Patient, bed, and room assignment checked
- Central station or destination system checked
- Other connected devices affected
- Interface or gateway status
- Controlled restart performed
- End-to-end test data received
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
Communication failures should be approached by protecting the patient, confirming local machine operation, and checking the physical connection before changing configuration. Clear documentation and proper coordination with Information Technology or the integration vendor prevent unnecessary parts replacement and repeated failures.
That is successful troubleshooting.