Spacelabs Healthcare Xprezzon

Network / central station communication failure

On this page

Asset Type

Patient Monitor

Manufacturer

Spacelabs Healthcare

Model

Xprezzon

What This Guide Helps With

Troubleshooting Xprezzon monitors not communicating with the central station, network, remote viewing, or alarm display systems.

Step-by-Step Troubleshooting

Ensure Patient Safety First

If the Xprezzon is actively monitoring a patient and communication to the central station is lost, notify clinical staff immediately.

Do not assume central station alarm visibility is active until confirmed.

Move the patient to another monitored bed, use a known-good monitor, or provide direct bedside observation according to clinical policy.

Expected outcome: Patient monitoring and alarm awareness are maintained without relying on failed network communication.

Why it matters: Loss of network connectivity may prevent alarms and patient data from appearing at central stations or other networked displays. Spacelabs documentation identifies Xprezzon as a network-capable bedside monitor, and FDA recall documentation has described loss of network connectivity as affecting central station alarm and data display.

Confirm the Reported Communication Failure

Check whether the issue is:

Confirm whether bedside monitoring functions still display correctly on the Xprezzon.

Expected outcome: The problem is identified as a network or central station communication issue, not a general monitor failure.

Check Whether the Issue Is Isolated or Widespread

Ask staff whether other Spacelabs monitors on the same unit are communicating normally.

Check nearby monitors connected to the same network area or central station.

Expected outcome: One failed monitor suggests a local cable, port, configuration, or monitor issue. Multiple failed monitors suggest a network switch, central station, server, or IT infrastructure issue.

If multiple monitors are affected, escalate to Clinical Engineering leadership and IT/network support before replacing parts.

Verify Bedside Monitor Power and Normal Operation

Confirm the Xprezzon is powered on, fully booted, and not frozen.

Check for normal waveform and numeric display at the bedside.

Confirm there are no obvious system errors, lockups, repeated restarts, or abnormal boot behavior.

Expected outcome: The monitor is operating locally before network communication is investigated.

If the monitor is frozen or repeatedly rebooting, remove it from service and send for bench evaluation.

Check Network Cable Connection

Inspect the network cable at the monitor and wall jack.

Confirm the cable is fully seated and not loose, bent, crushed, pulled tight, or routed where bed movement may strain it.

Reseat both ends of the cable if accessible and safe.

Expected outcome: A loose or partially disconnected network cable is corrected.

If communication restores, verify central station visibility and stop.

Inspect Network Link Indicators

Check the network port on the monitor, dock, wall jack, or associated network adapter if visible.

Look for link/activity lights.

Expected outcome: Link lights should indicate an active physical network connection.

If no link light is present, continue checking the cable, wall port, and network pathway.

Swap with a Known-Good Network Cable

Replace the current network cable with a known-good hospital-approved cable.

Avoid using damaged, unlabeled, excessively long, or non-approved cables.

Expected outcome: Communication returns if the original cable was defective.

If communication restores, document the failed cable and remove it from use. Stop.

Test the Wall Network Jack

Move the monitor to a known-good network jack assigned for patient monitoring, or connect a known-good monitor to the suspect jack if appropriate.

Do not connect to random wall ports unless the network assignment is verified.

Expected outcome: The issue follows either the wall jack/network drop or the monitor.

If the suspect jack fails with multiple monitors, escalate to IT/network support.

If the Xprezzon fails on a known-good jack, continue troubleshooting the monitor-side issue.

Confirm Correct Network Location and Bed Assignment

Verify the monitor is being used in the correct room, bed, care area, or network zone.

Confirm the central station is looking for the correct bed label or monitor assignment.

Check whether the monitor was recently moved, swapped, replaced, or returned from repair.

Expected outcome: The monitor appears under the correct bed or central station location.

Why it matters: A monitor may be working normally but assigned to a different bed, sector, or central station view.

Check Patient Admit / Discharge / Monitor Association

Confirm whether the patient has been admitted, discharged, transferred, or reassigned at the monitor or central station.

Ask clinical staff whether the issue began after a bed move, patient transfer, or monitor swap.

Expected outcome: Patient and bed association is corrected if the monitor was not properly assigned.

If communication restores after correct assignment, verify waveform and alarm visibility at the central station and stop.

Review Central Station Display and Alarm Behavior

At the central station, confirm whether the monitor is:

Expected outcome: The central station side of the failure is confirmed.

If the issue is only at one central station display, troubleshoot that workstation or escalate appropriately.

Restart Only When Clinically Safe

If the patient is not dependent on the affected monitor, or monitoring has been safely transferred, restart the bedside monitor according to facility procedure.

Do not reboot a monitor that is actively needed for continuous patient monitoring without clinical approval.

Expected outcome: Temporary communication faults may clear after a controlled restart.

If communication restores, confirm stable central station display and alarm visibility before returning to use.

Check for Recent Configuration or Network Changes

Ask whether any of the following occurred recently:

Expected outcome: Recent changes help identify whether the failure is device-specific or infrastructure-related.

Escalate for Network or System-Level Review

If the cable, wall jack, bed assignment, and local monitor operation appear normal, escalate to the appropriate support group.

This may include Clinical Engineering, IT/networking, Spacelabs system administration, or vendor support depending on site structure.

Provide the affected room, bed, monitor serial number, network port, central station name, time of failure, and whether other beds are affected.

Expected outcome: Network configuration, central station routing, switch port status, or system communication issues are reviewed by the proper support team.

Remove from Service if the Monitor Itself Remains Suspect

If the Xprezzon does not communicate on a known-good cable, known-good network jack, and known-good central station assignment, remove it from clinical use.

Label it Out of Service and send it for bench evaluation.

Expected outcome: A potentially faulty monitor network interface or internal communication problem is removed from patient care.

If the Problem Persists

If the Xprezzon still does not communicate after checking patient safety, network cable, wall jack, link status, room assignment, central station view, and known-good network connections, common external causes have been ruled out.

The device should be:

Knowing when to stop is proper troubleshooting. A monitor that cannot reliably communicate with the central station should not be returned to patient care until communication and alarm visibility are verified.

Clinical Use Tip

Do not troubleshoot central station communication on an active patient unless clinical staff have confirmed safe alternate monitoring or direct observation. A bedside monitor may still show vitals locally while alarms are not visible at the central station.

Move the patient to a backup device or provide direct bedside observation before continuing any troubleshooting that could affect therapy continuity or alarm visibility.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Nursing reported that the Spacelabs Xprezzon in ICU Bed 12 was displaying patient vitals locally but was not appearing at the central station."

Cause

What was observed during troubleshooting.

Example:
"Found network cable loose at the wall jack with no active link light present."

Resolution

What action was taken.

Example:
"Reseated the network cable, verified link activity, confirmed waveform and alarm visibility at the central station, and returned the monitor to service."

Helpful Details to Include (If Known)

Final Thought

Network communication failures should be handled carefully because bedside monitoring and central station visibility are not the same thing. Start with patient safety, then verify the physical network path, monitor assignment, central station behavior, and whether the issue is isolated or widespread. Clear documentation helps separate device failure from network or configuration problems.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide