Getinge Servo-i

Network, Serial, or Data Communication Failure

On this page

Asset Type

Ventilator

Manufacturer

Getinge

Model

Servo-i

What This Guide Helps With

Troubleshooting missing ventilator data, failed serial communication, interface dropouts, or unsuccessful connectivity to patient-monitoring and clinical information systems.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not interrupt ventilation or restart the Servo-i while it is actively supporting a patient solely to troubleshoot a data communication problem.

Confirm with the clinical team whether the failure affects only data transfer or also affects ventilator operation. Continue using the ventilator only when ventilation, monitoring, and local alarms remain fully functional.

Transfer the patient to another verified ventilator before performing any action that may interrupt therapy.

Expected outcome: The patient remains safely supported, and communication troubleshooting is performed without disrupting ventilation.

2. Confirm the Exact Communication Failure

Determine what information is missing and where it should appear:

Check whether the failure affects one Servo-i, multiple ventilators, or an entire clinical area.

Expected outcome: The affected communication path and scope of the failure are clearly identified.

3. Verify Normal Ventilator Operation

Confirm that the Servo-i:

A communication failure accompanied by startup faults, freezes, or technical errors may indicate a broader equipment problem.

Expected outcome: The problem is isolated to external communication rather than ventilation performance.

4. Inspect the Communication Cable and Connections

With the ventilator safely removed from patient use when required, inspect the applicable serial, adapter, or interface cable.

Check for:

Disconnect and securely reconnect accessible cables at both ends.

Expected outcome: Connections are secure and free of visible damage. If communication returns, document the loose connection and stop troubleshooting.

5. Confirm the Correct Cable and Interface Hardware

Verify that the installed cable, serial adapter, isolation device, or integration module is approved for the Servo-i and the receiving system.

Do not assume that visually similar serial cables have the same pin configuration. Getinge identifies the Servo Communication Interface as the protocol used for communication with external systems; connector wiring and integration details should be obtained through the manufacturer or approved integration documentation.

Expected outcome: The correct approved communication hardware is installed.

6. Test With a Known-Good Cable or Adapter

Replace the communication cable, serial converter, or external adapter with a known-good equivalent when available.

Change only one component at a time so the cause can be identified.

Expected outcome: Communication resumes if the original cable or adapter was defective. If resolved, remove the failed accessory from service and stop.

7. Check the External Integration Equipment

Inspect any equipment positioned between the Servo-i and the hospital network, including:

Confirm that the external device has power, normal indicator lights, and no obvious fault condition. Reboot external integration equipment only when authorized and when doing so will not interrupt other connected devices.

Expected outcome: The gateway or converter is powered, operational, and communicating normally.

8. Verify the Correct Bed, Port, or Device Assignment

Confirm that the ventilator is connected to the correct:

A physically functional connection may still fail when the Servo-i is assigned to the wrong bed, port, or device record.

Expected outcome: The physical connection and software assignment match the ventilator’s actual location and identity.

9. Compare With a Known-Good Connection

When safe and authorized, connect the Servo-i to a communication path known to work with another compatible ventilator.

Alternatively, connect a known-good compatible Servo-i to the suspected cable or integration port.

Interpret the result carefully:

Expected outcome: The failure is isolated to the ventilator or the external communication infrastructure.

10. Check for Recent Environmental or System Changes

Ask whether the failure began after:

Review available integration-system logs for connection failures, rejected messages, duplicate device assignments, or inactive ports.

Expected outcome: Any recent change associated with the failure is identified and corrected by the responsible support group.

11. Verify Communication Configuration

Compare accessible communication settings with those of a working Servo-i using the same integration system.

Check only settings available to authorized Clinical Engineering personnel, such as the selected interface, communication enablement, device identification, and approved serial communication parameters.

Do not change settings without documenting the original configuration. Do not access restricted service functions unless trained and authorized.

Expected outcome: The Servo-i configuration matches the approved integration standard.

12. Perform an Authorized Restart and Functional Test

After confirming that the ventilator is not supporting a patient, perform a normal shutdown and restart according to facility procedures.

Reconnect the approved test circuit, complete the required pre-use check, and verify:

Expected outcome: Communication is restored after restart, or the failure remains reproducible and requires escalation.

If the Problem Persists

If cables, adapters, external gateways, assignments, settings, and receiving systems have been checked, the common external causes have been ruled out.

The failure may involve the Servo-i communication interface, internal electronics, software configuration, or another condition requiring authorized service access.

The ventilator should be:

Do not open the ventilator or attempt board-level communication-port repair without the proper service documentation, training, and authorization. Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Loss of charting or central-system data does not necessarily mean ventilation has stopped. However, never assume remote data accurately represents the patient. Clinicians must rely on the ventilator’s local display, alarms, and direct patient assessment until communication is restored.

Do not restart, disconnect, or relocate a Servo-i supporting an active patient merely to restore data integration. Move the patient to another verified ventilator first when interruption is necessary.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory therapy reported that the Servo-i was ventilating normally but patient parameters were no longer appearing in the electronic charting system."

Cause

What was observed during troubleshooting.

Example:
"Testing found a failed serial-to-network adapter between the Servo-i communication cable and the bedside integration gateway."

Resolution

What action was taken.

Example:
"Replaced the adapter with a known-good approved unit, verified correct bed assignment, and confirmed stable transmission of ventilator parameters to the receiving system."

Helpful Details to Include (If Known)

Final Thought

Communication troubleshooting should begin by protecting the patient and confirming that ventilation remains normal. Follow the complete data path from the Servo-i through cables, adapters, gateways, assignments, and receiving systems before suspecting internal failure. Clear CCR documentation helps Clinical Engineering, IT, respiratory therapy, and integration teams resolve repeat failures efficiently.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide