PreVV Communication Protocol Tables
PreVV Communication Protocol Tables
Base Parameters:
SpO2........................................... ✘
Pulse Rate................................... ✘
Perfusion Index........................... ✘
PVI (optional).............................☐
Base Settings:
Averaging Modes
2-4 seconds.................................
4-6 seconds.................................
8 seconds.................................... ✘
10 seconds..................................
12 seconds..................................
14 seconds..................................
16 seconds..................................
Sensitivity Modes
Normal........................................ ✘
APOD......................................... ✘
Maximum................................... ✘
FastSat Mode
On............................................... ✘
Off.............................................. ✘
SmartTone Mode
On............................................... ✘
Off.............................................. ✘
Waveforms:
Pleth............................................ ✘
Signal IQ....................................
Resp. filter..................................
MS/MSX/uSpO2 PreV&V Protocol Checklist/Data Tables
For all section topics below, please indicate with an “OK”, or “Verified” when returning the document to
Masimo. Use Masimo simulator MSCPT.exe to confirm the applicable details of the protocol integration
tables in this document, See R-CSD1133 for simulator interface details and instructions details.
1.2 Activate Host Configurable Features command
1.2.1 Ensure the Activate Host Features Command Sent (this is a Masimo requirement for new integrations)
(Expiration Message Support)?
Yes
Note: This feature is only available on DSP versions V5.1.0.3 and later of MS-2003/2011/2013 boards and DSP versions
V2.1.0.0 and later of MS-2040, MSX-2040, boards and uSpO2 cables. It is required for all new integrations.
1.2.1.1 Is the AHCF (activate host configurable features) command resent whenever a board reset occurs (ref CSD-1186)?
Yes
1.3 Displayed Settings vs. MX Board Settings, state match
1.3.1 Ensure all user interface settings match the actual board state during run-time and power cycles/board resets.
1.3.2 Ensure the host software reads the board settings state to confirm the user interface setting matches.
1.8 Pulse-Ox System Exceptions (all exceptions must be handled by the host and displayed to the end-user).
1.8.1 Ensure all display messages are in accordance with Masimo guidance document R-CSD1257.
1.8.2 Ensure the host does not remove parameter values from the screen during any exception event.
1.8.3 Ensure the host does not implement additional logic using Masimo exception events .
1.8.3.1 The only time a parameter value should be removed or dashed from the user interface is when the associated
parameter invalid exception is active (i.e. numeric “0”), or whenever a board/diagnostic failure is active.
1.11 FastSat
Default Value on Power Up: Verified
✘ On
✘ Off
Selectable through User Interface: Verified
Correctly configured: Verified
Returns to Default State on Power
Up: -
1.12 SmartTone Must be independent of averaging
time: Verified
Default Value on Power Up: Verified
✘ On Selectable through User Interface: Verified
✘ Off Correctly configured: Verified
Returns to Default State on Power
Up: -
MS/MSX/uSpO2 PreV&V Protocol Checklist/Data Tables
Which Masimo protocol feature is used to generate pulse beeps, Signal IQ or Pulse Beep? - Pulse Beep
1.20 Exceptions
Ensure exceptions never force a parameter numeric to dash or be removed from the screen. The only
time a numeric should be dashed is when the parameter value received from the MS board protocol module is
“0”. “0” is the indicator for an invalid numeric reading and must be the only indicator used by a host to
remove or dash values from the screen.
Reference R- CSD-1132 for Masimo guidance on device display exception/message mapping.
Exceptions 3 messages must be implemented in all new integrations. The Exceptions 2 message “Low
Signal IQ” must be handled as well.
Exceptions 1 and 2 messages are only shown below for legacy integrations.
Exception handling can be tested using Masimo protocol simulator tool MSCPT.exe provided in the
development kit documentation and tools zip file.
Ensure the device dashes values and removes waveforms from the screen. An error message should also be displayed
on screen indicating an issue to the end-user. - Verified