On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting central monitoring disconnects, network communication loss, and duplicate IP conflicts caused by cabling, wall ports, configuration, or network infrastructure.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform extended network troubleshooting while the IntelliVue monitor is the only device supporting an actively monitored patient.
If central monitoring is required:
- Notify the clinical team that central monitoring or remote alarm notification may be unavailable.
- Confirm that alarms remain active and audible at the bedside.
- Maintain direct observation or transfer the patient to another verified monitoring device.
- Do not assume the central station is receiving alarms or patient data during a network failure.
Expected outcome: Patient monitoring continues safely without relying on an unavailable network connection.
Continue Clinical Engineering troubleshooting only after appropriate alternate monitoring has been established.
2. Confirm the Exact Failure
Determine whether the issue involves:
- A network-disconnected or central-monitoring message
- Loss of the patient sector at the Philips Information Center
- Intermittent connection and reconnection
- A duplicate IP address warning
- Data available locally but missing at the central station
- One affected monitor or multiple monitors in the same area
- Wired Ethernet, wireless connectivity, or both
Record the exact message, affected bed, room, monitor serial number, and time of occurrence.
Expected outcome: The failure is clearly identified as an isolated monitor issue, room-port issue, configuration conflict, or broader network event.
3. Verify Bedside Monitoring Operation
Confirm that the monitor:
- Powers on normally
- Displays local waveforms and numeric values
- Produces bedside alarms
- Responds normally to touchscreen or control inputs
- Has not restarted, frozen, or entered a service condition
A network failure should not automatically be treated as a complete monitor failure.
Expected outcome: Local patient monitoring functions remain operational.
If local monitoring is also unreliable, remove the monitor from service and perform a separate functional evaluation.
4. Inspect the Network Cable
For a wired connection:
- Confirm the Ethernet cable is connected securely at the monitor and wall jack.
- Inspect both connector latches for damage.
- Check the cable for cuts, crushed sections, sharp bends, contamination, or stretched conductors.
- Disconnect and reconnect both ends until they lock securely.
- Confirm that the cable is connected to the approved clinical monitoring network port.
Expected outcome: The network cable is intact and securely connected.
If reconnecting the cable restores communication, verify central monitoring and stop troubleshooting.
5. Check Network Link Indicators
Observe the network port indicators, when visible.
- No link light may indicate a disconnected cable, defective cable, inactive wall port, or monitor network-interface problem.
- A link light without communication may indicate configuration, addressing, switch, VLAN, or central-system issues.
- Compare the indicator behavior with a functioning monitor in the same area.
Expected outcome: A stable physical network link is present.
Document whether the link indicator is off, steady, or flashing.
6. Test With a Known-Good Network Cable
Replace the existing cable with an approved, known-good Ethernet cable.
Do not use an unverified cable taken from another malfunctioning device.
Expected outcome: The monitor reconnects using the known-good cable.
If communication returns, replace the defective cable, verify operation, and stop troubleshooting.
7. Test the Wall Network Port
Connect the monitor to a known-good clinical monitoring network port, following hospital network and infection-control procedures.
Alternatively, test the original wall port using an approved network-testing method or another properly configured monitor.
Do not connect the monitor to a general-purpose, guest, office, or unknown network jack.
Expected outcome: The monitor communicates through the known-good port.
If the monitor works on another port, leave the original port out of use and escalate the wall-port or switch-port issue to the appropriate network team.
8. Check for a Room-Specific or Area-Wide Outage
Determine whether other IntelliVue monitors connected to the same:
- Room
- Network switch
- Nursing unit
- Central station
- Wireless coverage area
are experiencing the same problem.
Expected outcome: The scope of the failure is established.
If several monitors are affected, stop repeatedly restarting individual monitors. Escalate the probable network, switch, central-system, or infrastructure outage.
9. Confirm the Assigned Bed and Network Identity
Verify that the monitor is assigned to the correct:
- Bed
- Room
- Unit
- Central station
- Monitoring domain or clinical network
Check for recent monitor swaps, room moves, loaner installations, software servicing, or configuration replacement.
Do not alter protected network settings without authorization and the approved Philips or hospital configuration process.
Expected outcome: The monitor identity matches its physical location and intended central-station assignment.
10. Investigate a Duplicate IP Address Warning
When a duplicate IP warning is displayed:
- Record the complete message and the monitor’s displayed network information.
- Determine whether another monitor was recently installed, moved, restored from backup, or returned from repair.
- Check whether two monitors may have received the same static configuration.
- Compare the affected monitor’s address with the hospital’s approved network inventory.
- Ask the network team to identify the other device using the address.
Do not randomly assign a new IP address. Unauthorized changes may create additional conflicts or prevent communication with the monitoring system.
Expected outcome: The conflicting device or incorrect network assignment is identified.
Once the approved address is corrected by authorized personnel, restart or reconnect the monitor only as required by local procedure, then verify central communication.
11. Evaluate Wireless Connectivity, If Equipped
For monitors using approved wireless connectivity:
- Confirm that wireless operation is enabled in the authorized configuration.
- Check whether the monitor connects normally in another known-good coverage area.
- Determine whether the failure occurs only in one room, hallway, elevator, or transport route.
- Inspect external wireless components or antennas for visible damage, when accessible.
- Check whether other wireless monitors are affected.
Do not open the monitor or alter wireless security settings during floor-level troubleshooting.
Expected outcome: The issue is identified as monitor-specific or coverage/infrastructure-related.
12. Perform a Controlled Restart
After patient safety has been addressed and cable, port, and configuration checks are complete:
- Disconnect the monitor from active patient use.
- Shut it down using the normal procedure.
- Wait for shutdown to complete.
- Restart the monitor.
- Observe network and central-station registration.
Do not repeatedly power-cycle a monitor that continues to lose communication.
Expected outcome: The monitor reconnects and remains visible at the central station.
If restarting resolves the issue, continue observing long enough to confirm that the connection remains stable.
13. Verify Central-Station Communication
Confirm with the clinical team or central-monitoring staff that:
- The correct patient appears in the correct sector.
- Waveforms and numeric values update normally.
- Bedside alarms are received centrally.
- Demographic and bed information are correct.
- No duplicate patient or duplicate bed assignment remains.
- Communication remains stable during an observation period.
Expected outcome: Bidirectional monitoring workflow and alarm communication are restored.
If successful, return the monitor to service and document the final configuration and test results.
If the Problem Persists
If known-good cables and ports have been tested, the bed assignment is correct, duplicate addressing has been investigated, and the monitor still cannot maintain communication, common external causes have been ruled out.
The problem may involve the monitor’s network interface, stored configuration, wireless hardware, software, central monitoring system, switch configuration, or hospital network infrastructure.
The device should be:
- Removed from service when reliable network or central monitoring is required
- Labeled Out of Service
- Sent for bench evaluation or authorized Philips service
- Escalated to the hospital network or monitoring-system team when infrastructure involvement is suspected
Do not perform unauthorized IP changes, software reloads, internal disassembly, or network-interface replacement at the bedside.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
A bedside monitor may continue displaying patient data even when it is disconnected from the central station. Never assume central staff can see the patient or receive alarms until communication has been directly verified.
Do not troubleshoot on an active patient. Move the patient to a verified backup monitoring device first and maintain therapy and monitoring continuity throughout the process.
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 repeatedly disconnected from the central station and displayed a duplicate IP address warning."
Cause
What was observed during troubleshooting.
Example:
"Inspection found that the monitor had the same static network address as a recently installed replacement monitor."
Resolution
What action was taken.
Example:
"Removed the affected monitor from clinical use, coordinated correction of the approved network configuration, and verified stable waveforms, numerics, and alarm communication at the central station."
Helpful Details to Include (If Known)
- Exact network or duplicate IP message
- Date and time of failure
- Monitor serial number and equipment ID
- Room, bed, unit, and central-station assignment
- Wired or wireless connection
- Network cable inspected
- Known-good cable tested
- Wall port tested
- Network link indicator behavior
- Other monitors affected
- Recent monitor replacement or relocation
- Displayed IP address or network identity
- Network or central-monitoring team contacted
- Bedside alarms tested
- Central alarm reception verified
- Environmental factors
- Indicator lights
- Accessories swapped
- Power behavior
- Final device status
Final Thought
Network troubleshooting should begin with patient safety, physical connections, cable and port testing, and the scope of the outage. Configuration changes should be controlled and coordinated. Clear documentation helps Clinical Engineering and network teams identify recurring conflicts while preventing unsafe assumptions about central alarm availability.
That is successful troubleshooting.