On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide helps troubleshoot NO CENTRAL MONITORING on a Philips IntelliVue MP Series patient monitor when bedside monitoring is active but central station surveillance or Information Center connection is unavailable.
This condition can affect patient visibility at the central station even when local parameters continue to display at the bedside.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the patient is not relying only on central station visibility for active monitoring.
- If the monitor is not visible at central or central surveillance is lost, notify clinical staff immediately.
- Ensure the patient is being observed locally at the bedside while the central monitoring issue is investigated.
- Expected outcome: Patient monitoring continues safely while the central monitoring issue is investigated.
Verify the Reported Alarm and Behavior
- Confirm the exact message displayed is NO CENTRAL MONITORING.
- Observe whether the message appears at startup, after moving the monitor, after assigning the patient to a sector, intermittently, only on wireless, or after a network or Information Center issue.
- Check whether bedside parameters still display normally.
- Expected outcome: The monitor functions locally but is not being monitored at central, or connection to the Information Center has been lost.
Confirm Local Bedside Monitoring Works
- Verify ECG, SpO2, NIBP, and other active parameters are displaying correctly at the bedside.
- Confirm audible local alarms are functioning.
- Expected outcome: The monitor continues to provide bedside monitoring even though central monitoring is unavailable.
Check Sector Assignment
- Verify the monitor is assigned to the correct sector, bed, unit, or Information Center location.
- Confirm the equipment label and bed label match the expected central station assignment.
- Expected outcome: The monitor is assigned to the correct central monitoring sector.
Confirm the Information Center Is Operational
- Check whether the Information Center or central station is functioning normally.
- Ask staff whether other monitors in the same unit are visible at central.
- Expected outcome: Other bedside monitors are visible and monitored normally.
Check Wired Network Connection
- If the monitor is using LAN, inspect the network cable at the monitor and wall jack.
- Confirm the cable is fully seated.
- Confirm the cable is not damaged.
- Confirm the wall jack is the correct clinical network jack.
- Check for link or activity indicators if visible.
- Confirm the cable has not been swapped into a non-clinical network port.
- Expected outcome: The monitor has a stable wired network connection.
Try a Known-Good Network Cable
- Replace the LAN cable with a known-good approved cable.
- Recheck whether the NO CENTRAL MONITORING message clears.
- Verify whether central can see the monitor.
- Expected outcome: The monitor reconnects to central monitoring if the original cable was faulty.
- Stop if resolved: Document the failed cable, replace it, verify central visibility, and return the monitor to service.
Check the Network Wall Port or Docking Location
- If possible, connect the monitor to a known-good network port used by another working monitor.
- Avoid disrupting patient care.
- Perform this only when clinically safe or during bench testing.
- Expected outcome: The monitor connects successfully from a known-good network port.
Check Wireless Range if Applicable
- If the monitor is operating wirelessly, confirm it is within approved wireless coverage.
- Move the monitor back near the expected coverage area or access point zone.
- Check whether the message clears after the monitor re-establishes wireless communication.
- Expected outcome: Wireless monitors reconnect when returned to proper coverage.
Check for Recent Movement or Bed Transfer
- Determine whether the monitor was recently moved between rooms, units, beds, or network areas.
- Verify that the bed label, sector assignment, and location configuration were updated after the move.
- Expected outcome: The monitor’s network identity and central assignment match its current clinical location.
Power Cycle Only When Safe
- If the patient is transferred to another monitor or the device is not in active use, restart the monitor.
- After restart, verify the alarm clears.
- Verify the monitor reconnects to the Information Center.
- Verify central station confirms visibility.
- Verify local monitoring functions remain normal.
- Expected outcome: Temporary communication faults clear after restart.
Compare With Another Monitor
- If available, connect another compatible IntelliVue monitor to the same network location.
- Then connect the suspect monitor to a known-good location.
- Expected outcome: The issue follows either the monitor or the network location.
Escalate Network or Information Center Findings
- If multiple monitors are affected, escalate to the appropriate network, clinical informatics, or Philips support pathway.
- If the issue follows a specific room, jack, switch, access point, or central station, escalate the infrastructure finding.
- Expected outcome: Infrastructure and Information Center issues are addressed through the correct support team.
If the Problem Persists
If sector assignment, bedside function, LAN cable, network port, wireless range, and Information Center status have been checked and NO CENTRAL MONITORING remains active, external causes have been ruled out.
Remove the monitor from service if central surveillance is required for that care area.
Label the device Out of Service.
Send the monitor for repair or bench evaluation.
Persistent NO CENTRAL MONITORING after external causes are ruled out may indicate a configuration issue, internal communication fault, network interface problem, or Information Center connectivity problem requiring higher-level support.
Clinical Use Tip
Never troubleshoot central monitoring communication on an active patient without clinical coverage.
Move the patient to a backup device first if central surveillance is required and the current monitor is not visible at the central station.
Maintain therapy continuity and make sure clinical staff understand the patient may not be visible at central while NO CENTRAL MONITORING is unresolved.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Philips IntelliVue MP Series patient monitor displayed NO CENTRAL MONITORING. Bedside parameters were active, but central station reported the monitor was not being monitored or Information Center connection was lost."
Cause
What was observed during troubleshooting.
Example:
"Checked monitor sector assignment, bedside monitoring function, LAN connection, network cable, wall port, and Information Center visibility. Issue appeared related to central monitoring connection/configuration rather than patient parameter failure."
Resolution
What action was taken.
Example:
"Corrected sector assignment and verified monitor was visible at central. Confirmed local alarms and parameter display were functioning. Returned monitor to service."
Helpful Details to Include (If Known)
- Alarm behavior, including when NO CENTRAL MONITORING appeared and whether it was constant or intermittent.
- Accessories swapped, including LAN cable, docking connection, or approved network cable.
- Power behavior, including whether the issue appeared after startup, movement, or a safe restart.
- Environmental factors, including wireless range, room location, access point coverage, wall jack, or switch port.
- Indicator lights, including visible link or activity indicators at the network connection if available.
- Final device status, including whether the monitor was visible at central, returned to service, removed from service, or sent for bench evaluation.
Final Thought
Central monitoring alarms must be treated as patient safety issues, even when the bedside monitor appears to work. Start with assignment, cabling, wireless range, and Information Center status before assuming device failure. Clear documentation helps separate monitor problems from network or central station issues.
That is successful troubleshooting.