On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed network communication, missing exported case data, or unavailable patient-monitor information caused by connections, configuration, network, or downstream system issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform extended communication troubleshooting while the Aisys CS2 is supporting an active patient.
If networked data, electronic charting, or patient-monitor communication fails during a procedure:
- Confirm that ventilation, gas delivery, alarms, and required measurements remain available locally.
- Notify the anesthesia provider of the communication failure.
- 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 continues safely without depending on the failed external interface.
Continue troubleshooting only when the system can be evaluated without disrupting patient care.
2. Confirm the Exact Failure
Determine which function is affected:
- The Aisys CS2 does not appear on the hospital network.
- Case data is not reaching the anesthesia information management system.
- Exported logs or files are unavailable.
- Patient-monitor values are missing from the Aisys CS2 display.
- A connected patient monitor is not receiving anesthesia data.
- Communication works intermittently.
- Communication fails only in one operating room.
Record any displayed communication message, network symbol, interface status, and the approximate time the failure occurred.
Expected outcome: The affected communication path is clearly identified before components are changed.
3. Verify Local Anesthesia Machine Operation
Confirm that the Aisys CS2:
- Starts normally.
- Completes its system checkout.
- Displays local ventilation and gas measurements.
- Responds normally to controls.
- Has no unrelated system, power, or display faults.
A communication problem should be separated from a broader anesthesia-system malfunction.
Expected outcome: Local anesthesia functions operate normally and the issue is isolated to connectivity or data exchange.
If local clinical functions are also unreliable, stop troubleshooting and remove the machine from service.
4. Inspect External Network and Communication Cables
Inspect all accessible Ethernet, serial, patient-monitor, USB, or approved interface cables associated with the failed function.
Check for:
- Loose connectors.
- Partially seated plugs.
- Broken locking tabs.
- Bent connector pins.
- Pinched or stretched cables.
- Damaged insulation.
- Improvised adapters or unapproved extension cables.
- Cables connected to the wrong port.
Disconnect and securely reconnect each accessible cable only after confirming that doing so will not disrupt active clinical systems.
Expected outcome: Each required cable is correctly routed, fully seated, and visibly undamaged.
If reseating a cable restores stable communication, verify operation and stop.
5. Check the Wall Network Connection
Confirm that the Ethernet cable is connected to the correct active wall jack assigned to the anesthesia machine or integration system.
When permitted by facility policy:
- Inspect the network-port link indicators.
- Test the wall jack with an approved network tester.
- Compare the connection with a functioning Aisys CS2 installation.
- Temporarily substitute a known-good network cable.
- Verify that the jack has not been reassigned during construction or network changes.
Expected outcome: The physical network connection and wall jack are functional.
If the wall jack fails testing, refer the infrastructure problem to the hospital network team and document the finding.
6. Inspect the Patient-Monitor Connection
If patient-monitor information is unavailable:
- Confirm that the monitor is powered and operating normally.
- Verify that the approved communication cable is connected at both devices.
- Confirm that the cable is connected to the correct ports.
- Check whether the monitor is displaying its own local patient data.
- Inspect any intermediate interface module, docking station, or adapter.
- Substitute a known-good approved cable when available.
- Determine whether the problem follows the monitor, cable, interface, or anesthesia machine.
Expected outcome: The external monitor and communication pathway are functional.
If communication returns with a replacement cable or monitor, remove the failed accessory from service and stop.
7. Compare With a Known-Good Operating Room
When possible, compare the affected system with another functioning Aisys CS2 installation.
Compare:
- Cable routing.
- Connected ports.
- Wall-jack identification.
- Network-status indications.
- Patient-monitor interface connections.
- Interface-module status lights.
- Data destination or room assignment.
Do not copy IP addresses or network settings between devices.
Expected outcome: An external setup difference or room-specific failure is identified.
If the machine works on a verified connection in another room, investigate the original room’s network jack, interface equipment, or configuration.
8. Review Accessible Communication Settings
Using authorized Clinical Engineering access, review the configured communication information without changing values unnecessarily.
Verify that:
- The expected interface is enabled.
- The correct data destination or server is selected.
- The device identity and room assignment are correct.
- Date and time are accurate.
- Network information matches the facility’s approved configuration.
- No duplicate network address or device identity is suspected.
- Configuration changes were not recently made.
The Aisys CS2 may use network or serial interfaces for communication with hospital systems and compatible monitoring equipment.
Expected outcome: The displayed configuration agrees with the hospital’s approved integration records.
Do not guess network values or assign temporary addresses without approval from the network or integration team.
9. Check for Recent Environmental or Infrastructure Changes
Ask whether the failure began after:
- Network maintenance.
- A switch replacement.
- A software or security update.
- An electronic medical record change.
- Movement of the anesthesia machine.
- Replacement of a patient monitor.
- Installation of a new interface device.
- A power interruption.
- Changes to the room or wall-jack assignment.
Expected outcome: The failure is correlated with a recent change that can be reversed or investigated.
10. Coordinate With the Network or Integration Team
Provide the responsible team with:
- Device model and serial number.
- Asset number.
- Room and wall-jack identification.
- Time the failure occurred.
- Network or communication status shown by the machine.
- Destination system that is not receiving data.
- Whether another device works on the same connection.
- Whether the Aisys CS2 communicates from another verified location.
Ask the team to verify:
- Switch-port status.
- Network-segment or VLAN assignment.
- Address conflicts.
- Device authorization.
- Server availability.
- Interface-engine status.
- Data routing and destination configuration.
Expected outcome: The hospital network and downstream information systems are confirmed operational or the external fault is identified.
11. Perform a Controlled Restart
After patient use has ended and facility procedures permit:
- Shut down the Aisys CS2 normally.
- Shut down or restart the associated external interface device when authorized.
- Verify all communication cables remain connected.
- Restore power.
- Allow the anesthesia machine, patient monitor, and interface systems to initialize fully.
- Recheck communication status.
Do not repeatedly power-cycle the system.
Expected outcome: Communication initializes normally following a controlled restart.
If the restart resolves the problem, complete a functional verification and monitor for recurrence.
12. Verify End-to-End Data Transfer
After communication appears restored:
- Confirm that the network connection remains stable.
- Verify that patient-monitor information appears at the correct destination.
- Generate approved test data when permitted.
- Confirm that the receiving system associates the data with the correct room and device.
- Verify date and time alignment.
- Confirm that no test information is entered into an active patient record.
- Allow sufficient time to identify intermittent disconnections.
Expected outcome: Data is transmitted accurately, continuously, and to the intended system.
If communication is intermittent, incorrect, delayed, or assigned to the wrong destination, do not return the device to service until the interface is corrected.
If the Problem Persists
If cables, accessories, wall connections, configuration, network availability, external monitors, and downstream systems have been verified, the failure may involve the Aisys CS2 communication hardware, internal interface, or software configuration.
The device should be:
- Removed from service.
- Labeled Out of Service.
- Sent for qualified repair or bench evaluation.
- Escalated to GE Healthcare or an authorized service provider when required.
Do not perform unauthorized internal disassembly or board-level repair. Knowing when external causes have been ruled out and escalation is required is proper troubleshooting.
Clinical Use Tip
A network or data-export failure may not stop ventilation, but it can remove electronic charting or integrated monitoring. Never assume data is being recorded elsewhere without direct confirmation. Use approved independent monitoring and downtime documentation until communication is verified.
Do not troubleshoot the Aisys CS2 while it is supporting an active patient. Move the patient to a verified backup device first and maintain therapy continuity throughout the equipment evaluation.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Aisys CS2 was operating locally, but anesthesia data and patient-monitor information were not reaching the electronic record."
Cause
What was observed during troubleshooting.
Example:
"Found the network cable partially seated at the wall jack, resulting in an unavailable network connection and failed data transfer."
Resolution
What action was taken.
Example:
"Reseated the cable, verified stable network communication and successful test-data transfer, completed system checkout, and returned the Aisys CS2 to service."
Helpful Details to Include (If Known)
- Exact communication symptom.
- Displayed message or network indication.
- Room and wall-jack identification.
- Network link lights observed.
- Cables inspected, reseated, or swapped.
- Patient monitor or interface tested.
- Whether another device worked on the same connection.
- Whether the machine worked in another room.
- Network or integration team findings.
- Time synchronization status.
- Test-data transfer result.
- Final device status.
Final Thought
Communication failures should be isolated methodically from the anesthesia machine to the cable, wall connection, network, interface, monitor, and receiving system. Protect patient care first, avoid unnecessary configuration changes, escalate internal faults appropriately, and document the complete communication path tested.
That is successful troubleshooting.