On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting MX100 patient assignment, central station visibility, network connection, sector assignment, and communication issues before repair escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the Philips IntelliVue MX100 is not the only active source of patient surveillance before troubleshooting communication or assignment issues.
If continuous monitoring is required, have clinical staff verify local bedside monitoring, central station visibility, or move the patient to another working monitor first.
Expected outcome: Patient monitoring remains active and safe while the communication issue is evaluated.
Confirm the Exact Complaint
Ask clinical staff what they are seeing. Determine whether the issue is:
- Patient not visible at the central station
- Patient assigned to the wrong bed, room, or sector
- Monitor visible but no waveforms or numerics are transmitting
- Central station shows communication loss, offline, or no monitor
- Admission, discharge, or transfer information is incorrect
- Issue occurs after transport, docking, undocking, or room transfer
- One MX100 is affected or multiple monitors are affected
Expected outcome: The issue is narrowed to patient assignment, monitor setup, network connection, central station configuration, or possible device communication failure.
Verify Local Monitoring First
Check whether the MX100 itself is displaying patient parameters correctly at the bedside. Confirm ECG, SpO2, NIBP, or other connected parameters are present locally.
Expected outcome: If local monitoring is working but central station communication is not, the issue is more likely assignment, network, or central station related.
Confirm Correct Patient Assignment on the MX100
Review the patient name, MRN, bed label, room number, or assigned monitoring location on the MX100, depending on site configuration.
Correct any obvious assignment mismatch only if permitted by facility workflow.
Expected outcome: The monitor is assigned to the correct patient and location before deeper troubleshooting.
Check for Recent Patient Movement or Transfer
Ask whether the patient was recently admitted, discharged, transferred, moved rooms, transported, or reconnected to monitoring.
Patient assignment problems often occur when the monitor still reflects the previous location or has not been reassigned properly.
Expected outcome: Recent workflow changes are identified as a possible cause.
Verify the Central Station Bed or Sector Assignment
At the central station, confirm the correct bed, sector, or care area is selected for the MX100.
Look for duplicate beds, unassigned beds, inactive tiles, or a patient assigned to the wrong room.
Expected outcome: The central station is looking for the correct device and patient location.
Check Wireless or Network Connection Status
Review the MX100 communication or network status indicators. Look for signs of weak wireless signal, no network connection, LAN disconnect, or communication loss.
Expected outcome: The monitor shows an active network connection. If not, continue checking external network causes.
Move the Monitor Within the Care Area if Wireless Is Suspected
If the MX100 communicates wirelessly and the issue appears location-related, move the monitor closer to a known good coverage area if clinically safe and approved.
Expected outcome: If communication restores, document a possible wireless coverage or access point issue rather than a monitor failure.
Check Physical Docking or Network Accessories
If the MX100 is connected through a dock, mount, network adapter, or wired network point, confirm it is fully seated and all external cables are secure.
Inspect for bent pins, loose connectors, damaged network cables, or unstable docking.
Expected outcome: External communication paths are secure and visibly undamaged.
Compare Against a Known Working Monitor or Bedside Location
If available, compare the affected MX100 with another known working MX100 in the same area.
Determine whether the issue follows the monitor, the room, the dock, the network jack, or the central station assignment.
Expected outcome: The fault is isolated to the device, location, network path, or assignment workflow.
Check for Duplicate or Conflicting Patient Assignments
Look for another monitor or central station tile already assigned to the same patient, bed, or room.
Duplicate assignments can prevent proper display or cause staff to see the patient in the wrong location.
Expected outcome: Only one correct active assignment exists for the patient and bed.
Review Alarm and Message Behavior
Check both the MX100 and central station for communication-related messages, offline indicators, missing waveform tiles, or assignment prompts.
Expected outcome: The displayed messages help separate a patient assignment issue from a network communication issue.
Power Cycle Only When Safe and Appropriate
If the patient is not actively dependent on the monitor, restart the MX100 according to normal facility practice.
Do not power cycle the device during active monitoring unless staff have moved the patient to another verified monitoring method.
Expected outcome: Temporary software or communication lockups may clear. If the issue resolves, verify central station visibility before returning to service.
Verify Communication After Correction
Confirm the central station displays the correct patient, room, bed, waveforms, numerics, and alarm status.
Ask clinical staff to confirm the patient appears in the expected monitoring sector.
Expected outcome: The MX100 is communicating properly and the patient assignment is accurate.
Stop if the Issue Is Resolved
If correcting assignment, reseating the monitor, restoring network connection, or correcting the central station bed location resolves the issue, stop troubleshooting and document the final working condition.
Expected outcome: The device remains in service only after communication and patient assignment are verified.
If the Problem Persists
If common external causes have been ruled out, the issue may involve internal communication hardware, software configuration, network infrastructure, central station configuration, or system integration.
The device should be:
- Removed from service if patient monitoring reliability is uncertain
- Labeled Out of Service
- Sent for repair, bench evaluation, or escalation to the appropriate Philips/network support path
Knowing when to stop is proper troubleshooting. Do not continue repeated resets or assignment changes on a device that cannot reliably communicate with the central station.
Clinical Use Tip
Do not troubleshoot patient assignment or central station communication while assuming the patient is safely monitored. Always verify that bedside monitoring, central station visibility, and alarm routing are correct before leaving the device in clinical use.
Do not troubleshoot on an active patient when communication reliability is uncertain. Move the patient to a backup device first when needed so therapy and monitoring continuity are maintained.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Philips IntelliVue MX100 was monitoring locally but the patient was not appearing correctly at the central station."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the MX100 assigned to the wrong bed location after a patient room transfer."
Resolution
What action was taken.
Example:
"Corrected the patient/bed assignment, verified live waveforms and numerics at the central station, and returned the MX100 to service."
Helpful Details to Include (If Known)
- Alarm behavior or communication loss messages
- Accessories, docks, cables, network adapters, or bedside locations swapped
- Power behavior, restart behavior, or whether a power cycle was performed
- Environmental factors such as wireless coverage area, room transfer, docking, undocking, or transport history
- Indicator lights, wireless indicators, LAN status, offline messages, missing waveform tiles, or assignment prompts
- Patient visible locally on MX100
- Central station bed or sector checked
- Patient name, room, or bed assignment verified
- Network or wireless indicator status
- Docking or network cable condition
- Whether the issue followed the monitor or stayed with the room
- Final central station visibility confirmed
- Final device status
Final Thought
Patient assignment and central station communication issues should be handled carefully because a monitor can appear functional locally while still failing to provide proper remote surveillance. Start with patient safety, verify assignment and network basics, compare against known working locations, and escalate when communication cannot be trusted. Clear CCR documentation protects both the patient and the Clinical Engineering record.
That is successful troubleshooting.