On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide helps troubleshoot the MsmtSrv not Supp INOP alarm on a Philips IntelliVue MP Series patient monitor when the monitor does not support the connected measurement server configuration. This may prevent the connected measurement server from being recognized and may make required parameters unavailable.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the Philips IntelliVue MP Series monitor is not the only active source of patient monitoring before disconnecting measurement servers, removing modules, or power cycling the device.
- If the monitor is in use on a patient, have clinical staff transfer monitoring to another working monitor first.
- Do not continue troubleshooting on an active patient if ECG, SpO2, NIBP, pressure, temperature, CO2, or other required parameters are unavailable.
- Expected outcome: Patient monitoring continues safely during troubleshooting.
Verify the Reported Alarm and Behavior
- Confirm the exact INOP message displayed is MsmtSrv not Supp.
- Observe whether the alarm appears immediately at startup, after connecting a Multi-Measurement Server, after adding additional measurement servers, intermittently when a module or server is moved, or after software service, equipment swap, or configuration change.
- Check whether the measurement server is not recognized, parameters are unavailable, the connected MMS is not usable, the INOP remains active, or the monitor otherwise powers on normally.
- Expected outcome: The INOP is clearly observed and linked to the connected measurement server setup.
Check the Measurement Server Connection
- Inspect the connection between the monitor and the measurement server.
- Confirm the MMS or measurement server is fully seated and connected correctly.
- Check for bent pins, damaged connectors, loose fit, contamination, or obvious physical damage.
- Disconnect and reconnect the measurement server, then observe whether the INOP clears.
- Expected outcome: A properly connected compatible measurement server should be recognized without the MsmtSrv not Supp INOP.
Power Cycle the Monitor With the Measurement Server Connected
- Turn the monitor off using normal shutdown procedures.
- Wait briefly, then power the monitor back on with the measurement server connected.
- Observe whether the INOP returns during startup.
- Expected outcome: If the issue was a temporary communication or recognition problem, the monitor should restart and recognize the measurement server normally.
Test With a Known-Compatible Measurement Server
- Disconnect the suspect measurement server.
- Connect a known-compatible, known-working measurement server used successfully on the same IntelliVue MP Series platform.
- Restart the monitor or allow the monitor to recognize the connected server.
- Expected outcome: If the known-compatible server works, the issue is likely with the original measurement server type, software revision, or compatibility.
Check for Too Many Connected Measurement Servers
- Review the connected measurement server configuration.
- Disconnect any extra, duplicate, or unnecessary measurement servers.
- Test with only the required supported measurement server connected.
- Expected outcome: The INOP clears if the monitor was rejecting the configuration because too many measurement servers were attached.
Verify the Measurement Server Type Is Supported
- Confirm the connected measurement server type is intended for use with the Philips IntelliVue MP Series monitor and the facility’s configuration.
- Look for a measurement server from another platform, unsupported MMS type, wrong model family, measurement server added from another department without compatibility confirmation, or recently swapped or borrowed measurement server.
- Expected outcome: Only compatible measurement server types should be connected to the monitor.
Check Software Revision Compatibility
- Verify the software revision of the monitor and the connected measurement server, if available through service/configuration screens or asset records.
- Compare the software revisions against facility standards, service documentation, or known compatible configurations.
- Expected outcome: The monitor and measurement server software revisions should be compatible with each other.
Compare Against a Known-Good Monitor
- Connect the suspect measurement server to another compatible IntelliVue MP monitor, if available and appropriate.
- Connect a known-good measurement server to the original monitor.
- If the INOP follows the measurement server, suspect unsupported server type or server software mismatch.
- If the INOP stays with the monitor, suspect monitor configuration or monitor software compatibility.
- If both work in proper matched configurations, suspect an unsupported combination rather than hardware failure.
Correct the Configuration if the Cause Is Identified
- If the issue is caused by an unsupported or extra measurement server, remove it and return the monitor to a supported configuration.
- If the issue is caused by software mismatch, escalate for approved software alignment or upgrade of the monitor and/or measurement server.
- Confirm required parameters display correctly and no related INOP messages remain.
- Return the monitor to service only after normal operation is confirmed.
If the Problem Persists
If the MsmtSrv not Supp INOP remains after checking connections, reducing connected measurement servers, testing known-compatible servers, and verifying software compatibility, external and common configuration causes have been ruled out.
A persistent alarm may indicate an incompatible monitor software revision, incompatible measurement server software revision, unsupported measurement server type, incorrect system configuration, or a monitor or measurement server communication fault requiring service evaluation.
Remove the monitor from service, label it Out of Service, and send it for bench evaluation or Philips/service-level repair support.
Clinical Use Tip
Never troubleshoot measurement server compatibility on an active patient if required parameters are missing. Move the patient to a backup device first, then evaluate the monitor and measurement server combination safely while maintaining therapy and monitoring continuity.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Philips IntelliVue MP Series monitor displays MsmtSrv not Supp INOP when measurement server is connected. Required parameters may not be available."
Cause
What was observed during troubleshooting.
Example:
"Connected measurement server configuration was not supported. Possible wrong software revision, unsupported measurement server type, or too many measurement servers connected."
Resolution
What action was taken.
Example:
"Verified INOP, removed monitor from patient use, inspected and reseated measurement server connection, power cycled monitor, tested with known-compatible measurement server, and checked for unsupported or extra measurement servers. Device returned to service after compatible configuration was confirmed, or removed from service for software compatibility review/bench evaluation if INOP persisted."
Helpful Details to Include (If Known)
- Alarm behavior, including when the MsmtSrv not Supp INOP appears
- Accessories swapped, including measurement server model/type and any known-compatible MMS tested
- Power behavior during startup, shutdown, and restart with the measurement server connected
- Environmental factors, including recent movement, department swap, service activity, or configuration change
- Indicator lights, communication status, unavailable parameters, and whether the INOP followed the measurement server or stayed with the monitor
- Final device status, including returned to service, removed from service, sent for bench evaluation, or escalated for software compatibility review
Final Thought
The MsmtSrv not Supp INOP should be approached as a compatibility and configuration problem first, not an automatic hardware failure. Clinical Engineering should verify the alarm, protect patient monitoring, check the connected measurement server setup, confirm supported combinations, and escalate when software or system compatibility cannot be corrected at the user-accessible level.
That is successful troubleshooting.