On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting missing PIC iX communication caused by network connections, assignments, settings, infrastructure, or monitor communication faults.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform extended communication troubleshooting while the IntelliVue MX monitor is the only device supporting an actively monitored patient.
If central surveillance is clinically required:
- Notify the clinical team that the patient is not visible at the PIC iX Central Station.
- Confirm the patient remains monitored locally at the bedside.
- Assign direct observation or transfer the patient to another verified monitoring location.
- Do not rely on central alarms until communication has been confirmed.
Expected outcome: Patient monitoring and alarm response continue without relying on the unavailable central-station connection.
Continue Clinical Engineering troubleshooting only when it is safe to do so.
2. Confirm the Exact Communication Failure
Determine whether:
- One monitor is missing from PIC iX.
- Multiple monitors in the same care area are missing.
- The bedside monitor displays a network or central-monitoring message.
- Waveforms and numerics are completely absent or only intermittently updating.
- The correct patient and bed are assigned at the central station.
- The problem began after moving, rebooting, replacing, or reconfiguring the monitor.
Check whether bedside monitoring remains functional.
Expected outcome: The failure is isolated to the bedside monitor, a network segment, a bed assignment, or the PIC iX system.
If several monitors are affected, involve the monitoring-system administrator or hospital IT before replacing bedside equipment.
3. Inspect the Bedside Network Connection
For a wired connection:
- Confirm the network cable is fully seated at the monitor and wall jack.
- Inspect the cable and connector clips for damage.
- Look for bent contacts, contamination, or a loose wall jack.
- Confirm any docking station, interface, or external network adapter is fully connected and powered.
Do not connect the monitor to an unapproved hospital network jack.
Expected outcome: The monitor has a secure physical connection to the approved patient-monitoring network.
If reseating the approved connection restores PIC iX communication, confirm stable data at the central station and stop.
4. Check Network Link Indicators
Observe available link or activity indicators at the monitor, docking station, network adapter, or approved wall connection.
- No link indication may suggest a cable, port, adapter, or switch-path problem.
- A link indication without PIC iX communication may suggest configuration, addressing, assignment, or system-level failure.
- Intermittent link activity may indicate a loose cable or unstable network port.
Expected outcome: A stable physical network link is present.
Record the indicator behavior in the work order.
5. Test With a Known-Good Approved Network Cable
Replace the existing cable with a known-good cable approved for the Philips monitoring network.
Do not use a cable of unknown condition or one taken from an unrelated network.
Expected outcome: Communication returns if the original cable was defective.
If the known-good cable restores communication, replace the damaged cable, verify central-station data and alarms, and stop.
6. Evaluate the Network Port
When permitted by facility policy, connect the affected monitor and known-good cable to another approved monitoring-network port assigned for that bed or care area.
Do not move the connection to a standard data-network port.
Alternatively, test the original approved port with a known-good compatible monitor if this can be done without disrupting patient care or creating duplicate network identities.
Expected outcome: Testing distinguishes a bedside-monitor problem from a wall-port or network-infrastructure problem.
If the monitor communicates on another approved port, escalate the original port to IT or the monitoring-network administrator.
If a known-good monitor also fails on the original port, suspect the network path rather than the bedside monitor.
7. Confirm the Monitor’s Network Status
Review the monitor’s accessible network or system-status information without changing protected configuration settings.
Look for:
- Network disconnected or unavailable status
- Missing or invalid network information
- Duplicate-address warnings
- Central monitoring unavailable
- Repeated connection attempts
- Incorrect network interface selection
- Wireless signal or association problems, when applicable
Photograph or record displayed messages according to facility policy.
Expected outcome: The monitor shows an active network connection without addressing or communication errors.
Do not enter service-level menus or alter IP settings unless authorized and supported by the facility’s Philips network documentation.
8. Verify the Bed and Equipment Assignment
At PIC iX, have authorized personnel confirm:
- The correct bed sector is selected.
- The bed is not assigned to another monitor.
- The monitor is associated with the correct unit and bed.
- The patient has been admitted or assigned correctly.
- The sector is not in standby, discharged, or otherwise unavailable.
- The monitor was not left associated with its previous location after transport.
Expected outcome: The physical monitor, network identity, bed sector, and patient assignment match.
If correcting the assignment restores communication, confirm waveforms, numerics, alarms, and patient identity before returning the system to clinical use.
9. Check for Duplicate or Incorrect Network Identity
Determine whether the problem began after:
- A monitor exchange
- Main-unit replacement
- Configuration cloning
- Software service
- Relocation between units
- Installation of another monitor
- A network-addressing change
A duplicate or incorrect network identity may prevent one or both devices from communicating reliably.
Do not independently assign addresses or equipment identifiers unless authorized.
Expected outcome: Each monitor has a unique, approved network identity associated with the correct clinical location.
Escalate suspected duplicate addressing to the Philips monitoring-system administrator or hospital IT.
10. Evaluate Wireless Connectivity, If Used
For wireless configurations:
- Confirm wireless communication is enabled for the intended configuration.
- Verify the monitor is within the approved coverage area.
- Check for weak, intermittent, or unavailable wireless status.
- Determine whether communication changes when the monitor is moved within the clinical area.
- Inspect any approved wireless adapter or antenna for external damage.
- Confirm other wireless monitors in the same area are communicating.
Expected outcome: The monitor maintains a stable connection to the approved monitoring network.
If several wireless devices fail in the same area, escalate as a coverage, access-point, or network-infrastructure issue.
11. Perform a Controlled Monitor Restart
After patient monitoring has been safely transferred:
- Disconnect the monitor from active patient use.
- Perform a normal shutdown using the approved control.
- Allow the shutdown to complete.
- Verify all external network and power connections.
- Restart the monitor.
- Observe network status and PIC iX communication during startup.
Do not repeatedly cycle power.
Expected outcome: The monitor completes startup and reconnects to the correct PIC iX sector.
If communication returns, verify stability before returning the monitor to service.
12. Verify Communication and Alarm Transfer
Do not consider the issue resolved merely because the monitor appears at PIC iX.
Confirm:
- The correct patient and bed are displayed.
- Waveforms update continuously.
- Numeric values match the bedside monitor.
- Technical and physiological alarms reach the correct central sector.
- Alarm messages clear appropriately.
- No communication-loss message remains.
- Communication remains stable for an appropriate observation period.
Use an approved simulator when clinical testing is necessary.
Expected outcome: Bedside data and alarm information are correctly and continuously displayed at PIC iX.
If verification is successful, return the monitor to service and document the result.
If the Problem Persists
If cables, approved ports, network link, monitor status, patient assignment, location assignment, and controlled restart have been checked, common external causes have been ruled out.
The problem may involve:
- The monitor’s network interface
- Docking or adapter hardware
- Corrupted or incorrect configuration
- Network-switch configuration
- Duplicate network identity
- PIC iX infrastructure
- Server or database services
- Wireless infrastructure
- A software or compatibility issue
The device should be:
- Removed from service when reliable central monitoring is required
- Labeled Out of Service
- Sent for bench evaluation or Philips-authorized repair
- Escalated to the Philips monitoring-system administrator and hospital IT when the failure appears infrastructure-related
Do not replace internal boards or alter protected network settings without authorized service information. Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot the IntelliVue MX monitor while it is supporting an active patient. Move the patient to a verified backup monitoring device or establish direct observation first so therapy and monitoring continuity are maintained.
A functioning bedside display does not confirm that the patient is visible or alarming at PIC iX. Verify central data and alarms before relying on remote surveillance.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the IntelliVue MX monitor was functioning at the bedside but was not displaying at the assigned PIC iX Central Station sector."
Cause
What was observed during troubleshooting.
Example:
"The bedside network cable had a damaged retaining clip, causing an intermittent network connection and repeated loss of central-station communication."
Resolution
What action was taken.
Example:
"Replaced the cable with an approved known-good cable and verified stable waveforms, numerics, patient identity, and alarm communication at PIC iX."
Helpful Details to Include (If Known)
- Patient safely transferred or alternate observation established
- Bedside monitoring remained functional
- Exact monitor and PIC iX messages recorded
- One monitor or multiple monitors affected
- Wired or wireless connection
- Network cable inspected
- Known-good cable tested
- Link and activity indicators observed
- Approved network port tested
- Bed and patient assignment verified
- Duplicate identity or address warning observed
- Monitor restart performed
- Waveforms and numerics verified at PIC iX
- Alarm communication verified
- IT or monitoring-system administrator notified
- Final device status documented
Final Thought
Central-station communication failures require attention to patient safety, physical connectivity, network scope, equipment identity, and bed assignment. Logical isolation prevents unnecessary monitor replacement and supports appropriate escalation. Complete CCR documentation preserves the findings for Clinical Engineering, IT, and Philips support.
That is successful troubleshooting.