1.0 PURPOSE SCOPE REFERENCE DOCUMENTS ASCII MODE Respiration Commands ECG Commands

Transcription

1 PRO 1000 Host Communications Manual wieloszynski Mike

2 1.0 PURPOSE SCOPE REFERENCE DOCUMENTS ASCII MODE Respiration Commands ECG Commands NIBP Commands Pulse Oximetry Commands Printer Commands Heart/Pulse Rate Commands Temperature Commands Star (*) Commands NATIVE BINARY MODE Hz Binary Block OPS Data Particulars Invalid Parameter Values Operational Differences MPS Alarm FLAG ENCODING All Alarms ECG Alarm Mapping Respiration Alarm Mapping NIBP Alarm Mapping SPO2 Alarm Mapping Temperature Alarm Mapping HR/Pulse Alarm Mapping Recorder Alarm Mapping System Alarm Mapping Native Mode Alarm Handling Native Mode Alarm Mapping OPS Native Mode Structure LS Native Mode Structure

3 1.0 PURPOSE This document defines the Host Communications protocol for the DINAMAP PRO 1000 monitor and will define the full set of ASCII commands and responses that the PRO 1000 device will support; but will only document the new version of Native Binary Mode. Native HostComm Protocol Revision supported 1 Plus Emulation HostComm Protocol Revision supported 0 NOTE: The Plus Emulation Mode Revision Level did NOT have to be Rev advanced for this release of code, since the basic operation of the command/response & binary data have not been modified from the previous release. 2.0 SCOPE This document provides for downward compatibility with the Host Communications protocol implemented in the DINAMAP PLUS family of patient monitors. All ASCII commands and responses, in addition to the binary data stream (referred to as Plus Emulation Binary Mode) will appear the same as it does for the PLUS family of monitors. In addition, new commands and responses will be added for PRO 1000 devices support and the Native Binary Mode data stream will be revision advanced due to changes in the OPS & LS data structures. This, however, will not preclude interoperability with previous releases or Native Binary Mode. OPERATIONAL NOTES: 1. Host Communications are NOT operational during Configuration mode. 2. The unit only recognizes documented commands and only sends the documented responses; all other received data is ignored by the device. 3. Low level errors are not reported by the unit. Only invalid command and invalid parameter identifier and, when necessary, invalid syntax are detected by the unit (i.e. extra characters in string are usually not detected). 4. For Plus Emulation Binary Mode, the model number reported by Host Communications will be REFERENCE DOCUMENTS DINAMAP MPS Host Communications Reference Manual Rev. 3 DINAMAP Select / Portable Native HostComm Definition Document Rev. 2.1 DINAMAP PLUS HostComm Reference Manual March 1995 DINAMAP User Interface Functional Specification FS

4 4.0 ASCII MODE ASCII commands can be transmitted to the device and responses will be returned as long as it is operational and the port is enabled. Responses, however, will not be returned if the device is currently sending binary data via one of the Serial ports. ASCII commands must be sent from the Host to the device as a continuous character stram. The unit will not buffer received characters waiting for a <CR> character to terminate the string. Instead, the HostComm command parser will treat each incoming character (or group of characters) as a valid Hostcomm command and attempt to process it. Upon determining that it is not framed correctly and will quietly toss it and send no response. The PRO 1000 monitor supports the following commands: B ECG-Derived Respiration Rate E ECG (Single Lead Only) N Non-Invasive Blood Pressure O Pulse Oximeter P Printer (including Central Station Printing) R Heart or Pulse Rate T Temperature * PRO 1000 Non-Parameter Specific 4.1 Respiration Commands Respiration Status Command "uba" Read status of Respiration "ubaabbb" "a" "bbb" Resp Status "0"!Operate Mode "1" Operate Mode Breath Rate (breaths per minute) NOTE:: A Breath Rate of 999 indicates the value is undetermined. NOTE:: When in Operate Mode the parameter is deterministic & alarms are active. The parameter will continue to indicate Operate Mode when the unit is in Standby; it is up to the Host to check for the global Standby Alarm Respiration Alarm Limits Command "ubb" Read Respiration Alarm Limits "ubbaaabbb" "aaa" "bbb" Resp Rate Low Limit (breaths per minute) Resp Rate High Limit (breaths per minute) NOTE: Alarm Limits of 999 indicate the value is undetermined. 4.2 ECG Commands The PRO 1000 monitor supports a 3-wire ECG subsystem that can display any of three (3) standard leads. However, only one lead at a time can be displayed. The following commands are supported ECG 3-Wire Status Command "uea" Read ECG Status 2

5 "ueaabc" "a" "b" "c" ECG Status "0"!Operate "1" Operate "2" Lead Off Primary Lead Number "1" Lead I "2" Lead II "3" Lead III "9" MCL1 Adult/Neonate Flag "0" Not Neonate "1" Neonate NOTE: Common medical use of the term ECG "Lead" is ambiguous. "Lead" can refer to either a waveform (e.g. Lead II) or a wire (e.g. a 3-lead cable). Care has been taken to use the terms "waveform" and "electrode" in most instances to convey this difference and reduce ambiguity. Sometimes this substitution is awkward however; so, in some instances the term "lead" has been left. NOTE: "Primary Lead Number" indicates which lead is being sent. NOTE: For downward compatibility, if the MCL is the current Primary Lead a value of "9" (corresponding to Lead V1), will be returned Change ECG Primary Lead Command "uec" Change the Monitor primary lead identifier to the next higher number: i.e. Changes occur in a circular fashion, i.e.: lead 1 will be changed to lead 2, lead 2 to lead 3, and lead 3 to lead 1. "uec+ "Lead change request queued OK. "uec-" Lead change request not queued. The lead change request capability (remote mode operation) must be enabled via Configuration Mode. NOTE: The Change Lead command will be NAK'd if the command is received when the primary lead is MCL (Modified Chest Lead) PRO 1000 ECG Status Command "ued" Read PRO 1000 ECG Status "uedabbc" "a" "bb" "c" ECG Status "0"!Operate "1" Operate "2" Lead Off Primary Lead Number "0x01" Lead I "0x02" Lead II "0x03" Lead III "0x20" MCL1 (Modified Chest Lead 1) Adult/Neonate Flag "0" Adult "1" Neonate "2" Pediatric 3

6 4.3 NIBP Commands All PRO 1000 monitors have one channel of non-invasive blood pressure. The following commands are supported NIBP Status Command "una" Read Non-Invasive Blood Pressure Status "unaabcddddeeefffggg" "a" Determination Status "0" Busy "1" Done OK "2" Not Used "3" Determination Failed (N99) "4" Pumpup Timeout (N33) "5" Neonate Host (France Only) "6" Total Time Timeout (N44) "7" One-Pressure Timeout (N55) "8" OverPressure (N00) "9" Unknown NIBP Status "b" Adult/Neonate Status "0" Unknown "1" Adult "2" Neonate "c" Determination Type "0"!Stat Mode (Manual or Auto) "1" Stat Mode "dddd" Time since last determination "eee" Systolic Pressure "fff" Diastolic Pressure "ggg" Mean Arterial Pressure NOTE: "dddd" - When the timer exceeds 5400 (90 minutes) all values are invalid. NOTE: Although the Time Since Last Determination has been increased from 90 minutes to 120 minutes (refer to the NF command); the 'NA' Status command will continue to invalidate values exceeding 90 minutes. The new 'NF' Status command will go until 120 minutes before the values are invalid Cuff Pressure Command "unb" Read Cuff Pressure Channel "unbabbb" "a" "bbb" Determination in-progress indicator "0" Determination in-progress "1" Determination not in-progress Current pressure 4

7 4.3.3 Start NIBP Determination Command "unca" Start a Determination "a" Type of Determination "0"!Stat Mode (Manual) "1" Stat Mode "unc+" Determination started OK "unc-" Determination was NOT started. The remote mode operation must be enabled via Service Mode for this command to be performed Cancel NIBP Determination Command "und" Cancel a determination "und+" Determination canceled OK "und-" Determination was NOT canceled. The remote mode operation must be enabled via Configuration Mode for this command to be performed NIBP Alarm Limits Command "une" Read NIBP Alarm Limits "uneaaabbbcccdddeeefff" "aaa" Systolic Low Limit "bbb" Systolic High Limit "ccc" Diastolic Low Limit "ddd" Diastolic High Limit "eee" MAP Low Limit "fff" MAP High Limit 5

8 4.3.6 PRO 1000 NIBP Status Command "ung" Read PRO 1000 NIBP Status "ungabcddddeeefffggg" "a" Determination Status "0" Busy "1" Done OK "2" Not Used "3" Determination Failed (N99) "4" Pumpup Timeout (N33) "5" Neonate Host (France Only) "6" Total Time Timeout (N44) "7" One-Pressure Timeout (N55) "8" OverPressure (N00) "9" Unknown NIBP Status "b" Cuff Type "0" Unknown "1"!Neonate "2" Neonate "c" Determination Type "1" Manual Mode "2" Auto Mode "3" Stat Mode "dddd" Time since last determination "eee" Systolic Pressure "fff" Diastolic Pressure "ggg" Mean Arterial Pressure NOTE: "dddd" - When the timer exceeds 7200 (120 minutes) all values are invalid. 6

9 4.4 Pulse Oximetry Commands The PRO 1000 monitor has one channel of Pulse Oximetry. The following commands are supported Pulse Oximetry Status Command "uoa" Read SPO2 Status "uoaabbbcdd" "a" "bbb" "c" "dd" Always "00" Pulse Ox Status "0"!Operate "1" Operate Mode OK "2" Operate Mode OK "3" Lost Pulse "4" Not Used "5" Replace Sensor "6" Sensor Off Oxygen Saturation Signal Strength ('0' to '9') NOTE: When SPO2 is in Flash & Dash the O2 Saturation value will be invalidated. Pulse Search and Motion detection will still report the current 02 Saturation value. NOTE: For Pulse Ox Statuses of 3 through 6 the Nellcor alarms have been mapped to the corresponding existing ones for Critikon SPO2. NOTE: The Averaging Interval (dd) has no meaning for PRO 1000 SPO2 and the value will be invalidated (00) Pulse Oximetry Alarm Limits Command [HCS_OB] "uob" Read SPO2 Alarm Limits "uobaaabbb" "aaa" "bbb" SPO2 Low Limit SPO2 High Limit Pulse Oximetry Extended Alarm Limits Command [HCS_OD] "uod" Read SPO2 Extended Alarm Limits "uodaaabbbcccddd" "aaa" SPO2 Low Limit "bbb" SPO2 High Limit "ccc" Pulse Rate Low Limit "ddd" Pulse Rate High Limit 7

10 4.4.4 PRO 1000 Pulse Oximetry Status Command "uoe" Read PRO 1000 SPO2 Status "uoeabcdeeefggg" "a" Pulse Ox Status "0"!Operate "1" Operate Mode OK "2" Operate Mode OK "3" Lost Pulse "4" Not Used "5" Check Cable "6" SPO2 Disconnect "b" Flash & Dash Status "0" Off "1" Saturation "2" Rate "3" Saturation & Rate "c" Pulse Search Detected? "0" No "1" Yes "d" Motion Detected? "0" No "1" Yes "eee" Oxygen Saturation "f" Signal Strength ('0' to '9') "ggg" Pulse Rate NOTE: If the Flash & Dash Status indicates Saturation and/or Rate, then the corresponding values should be considered invalid. 8

11 4.5 Printer Commands The PRO 1000 monitor supports an optional strip printer. The following commands are supported: "ups" Print Snapshot to Monitor Printer "ups+" Snapshot Spooled to Printer "ups-" Snapshot NOT Spooled to Printer "upca" Central Station ACK to CS Print Note: Command has no effect in ASCII mode; however, in Binary Mode the Central Station sends this as a response when it accepts the Central Station printout request from the Monitor. "upcn" Central Station NACK to CS Print Note: Command has no effect in ASCII mode; however, in Binary Mode the Central Station sends this as a response when the printout requested by the Monitor cannot be printed at the Central Station. 9

12 4.6 Heart/Pulse Rate Commands The Heart/Pulse Rate values displayed on the PRO 1000 monitor can come from one of several sources. The following commands are supported Heart/Pulse Rate Status Command "ura" Read Heart/Pulse Rate Status "uraabbb" "a" "bbb" Heart/Pulse Rate Status "0" No Valid Rate Source "1" ECG "2" Pulse Oximeter "3" Non-Invasive Blood Pressure Heart/Pulse Rate NOTE: It is up to the programmer to assure that the Heart/Pulse Rate source indicates that the Heart/Pulse Rate values returned by this command are not invalidated by an associated alarm condition. NOTE: If SPO2 is the Source and is in Flash & Dash mode, then the Heart/Pulse Rate values will be invalidated Heart/Pulse Rate Alarm Limits Command "urb" Read Heart/Pulse Rate Alarm Limits "urbaaabbb" "aaa" "bbb" Heart/Pulse Rate Low Limit Heart/Pulse Rate High Limit 10

13 4.7 Temperature Commands The Temperature commands supported by the PRO 1000 monitor are as follows: Read Temperature Status Command "uta" Read Temperature Status (degrees C) "utaabbb" "a" "bbb" Temperature Display at Bedside "1" Centigrade "2" Fahrenheit Temperature (in tenths of degrees Centigrade) "000" Indicates unit is unplugged "999"/"-99" Invalid temperature value. NOTE: The Display Format value indicates the units used to display the temperature AT THE BEDSIDE ONLY. The value contained in the response to this command WILL ALWAYS respond with a value in tenths of degrees Centigrade Read degc Temperature Alarm Limits Command "utb" Read Temperature Alarm Limits "utbaaabbb" "aaa" "bbb" *Temperature Low Limit (degrees Centigrade) *Temperature High Limit (degrees Centigrade) * Note: Currently Temp alarm limits are not used. Response will be invalid values (-99 / 999). 11

14 4.7.3 Read PRO 1000 Temperature Status Command "ute" Read Temperature Status (degrees F) "uteabcddddeeeef" "a" Temperature Status "0" Idle "1" Probe 1 Busy "2" Probe 2 Busy "3" Probe 1 Done "4" Probe 2 Done "5" Monitor Value 1 Stable "6" Monitor Value 2 Stable "b" Temperature Mode "0" Monitor "1" Predictive "c" Monitor Display Format "0" Centigrade "1" Fahrenheit "dddd" Temperature (in tenths of degrees Fahrenheit) "eeee" Timer (in seconds) "f" Probe Type "0" Not Rectal (Blue) "1" Rectal (Red) NOTE: "eeee" - Predictive mode determinations give the t since the completion of the last temperature determination (0 to 7200 seconds minutes). Monitor mode determinations give the t since the temperature determination was started (0 to 60 minutes) NOTE: All values are invalidated from the moment a temperature determination begins. If the determination is canceled, the previous value is not redisplayed. NOTE: For both temperature modes, when the timer expires or is invalidated, the temperature value should no longer be considered valid. 12

15 4.8 Star (*) Commands "Star" (*) commands are used to change communications parameters or to read instrument status. These are the non-parameter specific commands Identity Command "u*?" "u*?aaabbc" "aaaa" Model number (1000) "bb" The Plus Emulation Binary Mode Revision Level (current rev level is "00"). "c" Instrument Mode Flag "0" Service Mode "1" Normal Operating Mode with Remote Control Enabled "2" Normal Operating Mode with Remote Control Disabled NOTE: Neither the syntax nor semantics of this command have changed. It has been added here to provide a further clarification that the Host Comm Revision Number that is returned is for the Plus Emulation binary protocol. The *?? command will have to be used to obtain the Native Mode binary Revision Number Extended Identity Command "u*??" "u*??aaabbccd" "aaaa" Model number (1000) "bb" The Plus Emulation Binary Mode Revision Level "cc" The Native Binary Mode Revision Number "d" Instrument Mode Flag "0" Service Mode "1" Normal Operating Mode with Remote Control Enabled "2" Normal Operating Mode with Remote Control Disabled Elapsed Time Command "u*a" "u*atttttttt" "tttttttt" Time since power-up (in seconds) 13

16 4.8.4 Change Bit Rate "u*bn" "n" bps 6 19,200 bps 7 28,800 bps 8 38,400 bps 9 57,600 bps A 115,200 bps "u*b+" Bit Rate Change Successful "u*b-" Bit Rate Change Not Performed NOTE: For a successful change in baud rate, the "*B+" response is sent at the OLD baud rate. NOTE: This command extends the "u*bn" command already defined in previous code versions. NOTE: The Baud Rate cannot be modified if either Binary Mode is currently active Read Counters "u*c" "u*cabcc" "a" The Good Command counter (modulo 64). "b" The Bad command counter (modulo 64). "cc" The Silence State counter (modulo 100). NOTE: The good command counter is incremented (modulo 64) every time a good command is received. The bad command counter is incremented (modulo 64) every time a bad command is received. These counters are each sent as a single printable ASCII character starting with space (0x1f) and ending with underscore (0x5f). After the underscore character, the sequence wraps around to space again. NOTE: The silence sequence number follow these rules: Every time the SILENCE key is pressed, the silence sequence number changes. A number won't repeat until after the SILENCE key has been pressed 100 times. If the silence sequence number is less than 50, the alarms at the Monitor aresilenced; otherwise alarms at the Monitor are enabled. Make no other assumptions. 14

17 4.8.6 Read All Counters This command includes the Central Station Snap Shot counter reported via an ASCII command. "u*d" "u*dabcdd" "a" The Good Command counter (modulo 64). "b" The Bad command counter (modulo 64). "c" The Central Station Snap Shot counter (modulo 64). "dd" The Silence State counter (modulo 100). NOTE: The value returned for the Good Command Counter DOES NOT include the command currently being processed (*C or *D), since the command is not considered to be "good" until the task that sends the message indicates that no errors occurred in transmission Get Patient Information "u*i" "u*iaaaaaaaaaaaaaaaaaaaa bbbbbb cccc d" "aaaaaaaaaaaaaaaaaaaa" The Patient Name (20 chars) " " Vertical Bar field delimiter "bbbbbb" The Patient Unit Number (6 chars) " " Vertical Bar field delimiter "cccc" The Patient Bed Number (4 chars) " " Vertical Bar field delimiter "d" The Patient Type 0 Adult 1 Neonate 2 Pediatric Set Patient Name "u*jaaaaaaaaaaaaaaaaaaaaa" "aaaaaaaaaaaaaaaaaaaa" The Patient Name (0 to 20 ASCII characters) "u*j+" Command performed NOTE: If the input string exceeds 20 characters the string will be truncated to 20 characters Set Patient Unit Number ] "u*jbbbbbbb" "bbbbbb" The Unit Number (0 to 6 ASCII characters) "u*j+" Command performed NOTE: If the input string exceeds 6 characters the string will be truncated to 6 characters. 15

18 Set Patient Bed Number ] "u*jccccc" "cccc" The Bed Number (0 to 4 ASCII characters) "u*j+" Command performed NOTE: If the input string exceeds 4 characters the string will be truncated to 4 characters Discharge Patient "u*jd" "u*j+" Command performed NOTE: If a discharge is received while in the discharged state, any non-admitted patient will be moved to the previous patient data Admit Patient "u*je" "u*j+" Command performed NOTE: If a patient is already admitted, the an automatic discharge followed by an admit will occur. NOTE: If trend data has already been collected in non-admitted mode, the patient will data will be kept Set User Configuration "u*kn" "n" 0 Default User Configuration 1 1 Default User Configuration 2 2 Default User Configuration 3 3 Default User Configuration 4 4 Default User Configuration 5 5 Default User Configuration 6 "u*k+" User Configuration Change Successful "u*k-" User Configuration Change Not Performed NOTE: This command cannot be performed unless Remote Access is enabled Read PLUS Alarm Flags Command "u*l" "u*laaaabbbbcccc" "aaaa" Alarm Group 2 (in hex) "bbbb" Alarm Group 1 (in hex) "cccc" Alarm Group 0 (in hex) NOTE: Alarm flags are sent as three hex groups of 4 digits (16 flags) each. Each group uses the usual encoding of 16 bits into 4 hex digits; i.e., 0x8000 is bit 15 and 0x0001 is bit 0. 16

19 Read Native Mode Alarm Flags Command "u*mnn" "nn" "u*maaaaaaaa "aaaaaaaa" "*M-" nn = '0' to '35'; indicating Alarm Byte A series of '0' and '1' characters indicating if alarm bit is ON (1) or OFF (0) Command NAK. Command could not be performed due to improper input parameter Read Native Mode Alarm Types "u*nnn" "nn" n = '1' to '35'; indicating Alarm Byte "u*naaaaaaaa" "aaaaaaaa" A series of characters ('0', '1', '2', or '3') indicating alarm priority for the alarms contained in the Alarm Byte. '0' Message Alarm '1' Procedural Alarm '2' Warning Alarm '3' Crisis Alarm "*N-" Command NAK. Command could not be performed due to improper input parameter. NOTE: The Alarm Byte values appear in the order as defined in the Alarm Mapping section of this document and are the same as they are reported in the OPS and LS structures. NOTE: Command *N0 is invalid because there are no Alarm Priorities that coincide with Alarm Byte 0 these are general alarms Get System Time Command "u*sa" "u*saaaaa-bb-cc dd:ee:ff" "aaaa" The Year (4 digits incl. century information) "bb" The Month (01 > Jan to 12 Dec) "cc" The Day (01 to 31) " " Space to delineate "dd" The Hour (military time) "ee" The Minutes (00 to 59) "ff" The Seconds (00 to 59) Set System Time Command "u*sb" "u*sbaaaa-bb-cc dd:ee:ff" "aaaa" The Year (4 digits incl. century information) "bb" The Month (01 > Jan to 12 Dec) "cc" The Day (01 to 31) " " Space to delineate "dd" The Hour (military time) "ee" The Minutes (00 to 59) "ff" The Seconds (00 to 59) 17

20 NOTE: Setting the system time will invalidate the patient trend information Get System IP Address "u*ua" "u*uaaaabbbcccddd" "aaa" First octet (0-255) "bbb" Second octet (0-255) "ccc" Third octet (0-255) "ddd" Fourth octet (0-255) Get Native Binary Mode Configuration "u*w" "u*waaaaaaaaaaa" "aaaaaaaaaaa" Configuration of up to 11 waveform channels "K" Pleth/ Resp "L" ECG Primary Lead "-" Not Used/Empty NOTE: While the response contains a data capable of reporting up to 11 waveforms, only 2 will ever be contained in the response. The trailing 9 values will always be 's Configure Native Binary Mode "u*xaaaaaaaaaaa" "aaaaaaaaaaa" "K" Pleth/ Resp "L" ECG Primary "-" No Waveform/Empty "u*x+" Configuration Successfully Changed "u*x-" Configuration Change Not Performed NOTE: The "aaaaaaaaaaa" field must be exactly 11 characters long. If less than 11 the field must be padded with "-" characters. A "-" character is not allowed to be imbedded within the waveform options. NOTE: Duplicate non-dash characters are NOT allowed. NOTE: The waveform characters must be in alphabetical order. NOTE: The default configuration is "KL ". NOTE: It is the responsibility of the Host to assure that the proper Bit Rate is set. NOTE: The type of the 50 Hz waveform block is selected by counting the number of dash characters (n) at the end of the "aaaaaaaaaaa" field. "BHC2_BINARY_BLOCKx" is sent if there are (x = 11-n) trailing dash characters. NOTE: The Native Binary Mode Configuration cannot be changed if Binary blocks are currently being sent. A *Y0 will have to be sent to stop Binary mode before the configuration change will be allowed Start Native Binary Mode 18 "u*ynnnn" "nnnn" The number of binary blocks to be sent. "0" Stops current Native Mode Binary stream

21 "9999" The unit is put into an "continuous binary mode" (approx. 2.5 years). <="9998" The new value is added to the existing Binary Count value. binarydata Native Mode binary blocks to follow NOTE: If the proper Bit Rate is not selected, the unit will not enter Native Binary mode. NOTE: ACK's / NAK's are not returned in response to the *Y command. Valid command results in receipt of Binary Data. An invalid command receives no response; a timeout should be implemented by the Host NOTE: The monitor returns to Command mode after the required number of binary blocks are sent. NOTE: To switch to Plus Emulation binary mode the current binary stream must first be terminated or the Binary Count must go to Start Plus Emulation Binary Mode "u*znnnn" "nnnn" The number of binary blocks to be sent. "0" Stops the current Native Mode Binary Stream. "9999" The unit is put into an "continuous binary mode" (approx. 2.5 years). <="9998" The new value is added to the existing Binary Count value. binarydata Plus Emulation Mode binary blocks to follow. NOTE: A minimum Bit Rate of 9600 bps is required for Plus Emulation binary mode. The operation of Plus Emulation binary mode is undefined for bit rates less than 9600 bits per second. NOTE: ACK's and NAK's are not returned in response to the *Z command (. A valid command will result in the receipt of Binary Data. An invalid command will receive no response; a timeout should be implemented by the Host. NOTE: The monitor returns to Command mode after the required number of binary blocks are sent. NOTE: To switch to Native binary mode the current binary stream must first be terminated or the Binary Count must go to 0; otherwise, the command will be ignored. 19

22 5.0 NATIVE BINARY MODE The *Z command causes Plus Emulation Binary Mode output. The *Y command causes Native Binary Mode output. These two binary output modes are mutually exclusive. Native Mode binary output is contained in a stream of bytes. A consecutive sequence of bytes forms a binary block. These are sent at an aggregate rate of 50 per second and are called the 50 Hz binary Block. The binary blocks are sent 4 at a time (a Quad Binary Block). Three (3) bytes are collected from each 50 Hz Binary Block for one continuous second. These bytes form a 150 byte structure that is called the once-per-second (OPS) structure. Sixteen bytes are collected from each OPS structure in one continuous 10 second period. These bytes form a 160 byte Low Speed (LS) structure that is updated once per 10 second period. The remainder of this section describes these structures Hz Binary Block typedef struct { char SeqNum; char WFStat; char WFData[N][5]; /* N = number of waveform channels */ char NonWFData[3]; char CSum[2]; char ocoseqnum; } BinBlkNType, *BinBlkNTypePTR; SeqNum WFStat This is the block sequence number, modulo 200. The byte counts up by 1 for each consecutive binary block. When the block sequence number reaches 199, it turns back to 0. Since binary blocks arrive at a rate of 50 times per second, the (SeqNum % 50) counts from 0 to 49 and forms a one second scan index. The first byte of a one second scan has (SeqNum % 50) == 0 and the last byte of the same one second scan occurs one second later and has (SeqNum % 50) == 49. The waveform status contains real-time waveform information. Bits <3:2> are incremented for every QRS event detected. Bits <1:0> are the waveform index (0, 1, 2 or 3), indicating which of the 4 binary blocks the event occurs in (this means that the QRS event occurred in 1 of the 4 samples contained in that binary block). Bits <5:4> are incremented for every breath detected. Bit <6> is set if any warning alarm bit is set. Bit <7> is set if any crisis alarm bit is set. NOTE: Both of the Alarm bits are latched for a minimum duration of 4 WF Stat samples. NOTE: The QRS Event Detection is only performed on the PRIMARY lead; therefore, if the Unit is not sending the primary lead, bits 0 through 3 in the WFStat should be ignored. NOTE: The Waveform Index field is only valid when a transition occurs in the QRS Event Detect field. NOTE: While the QRS & Breath Event fields (bits 0 through 5) are initialized to 0's when the unit is initially powered up this will not be the case if Native Binary Mode is stopped and restarted. The Host must check for transitions in these fields and not absolute values. 20

23 5.1.3 WFData For the purpose of host communications, waveform samples are packed into a 5 byte (40 bits) "packed waveform data array" (PWDA). A PWDA contains four 10 bit waveform samples which are packed, without gaps. The following C code fragment is an example of how to unpack the four waveform samples. char pwda[5]; /* packed waveform data array */ wfs[4]; /* waveform samples: bits 15 to 10 are zero. */ wfs[0] = ((pwda[0] << 2) (( pwda[1] >> 6) & 0x03)) & 0x03ff; wfs[1] = ((pwda[1] << 4) (( pwda[2] >> 4) & 0x0f)) & 0x03ff; wfs[2] = ((pwda[2] << 6) (( pwda[3] >> 2) & 0x3f)) & 0x03ff; wfs[3] = ((pwda[3] << 8) (( pwda[4] >> 0) & 0xff)) & 0x03ff; WFData[N][5] This is an array of PWDA arrays. The number of PWDA arrays can be 0, 1 or 2 waveform channels, and is configured by the "*X" command. There are 3 different 50 Hz binary block structures. The host must expect the appropriate structure for the configuration specified by the most recent "*X" command (defaults included). The waveform data is 4-way interleaved same as for Plus Emulation mode. It is the Host's responsibility to assure that the appropriate Bit Rate is configured. If the bit rate is not sufficient to support the number of waveforms selected, then binary mode will not be initiated bps will support all possible configurations of Native Mode binary waveform data NonWFData CSum Numeric (or non-waveform) parameter data and status are available once per second. NonWFData[3] is a 3 byte array that is used to assemble a 150 byte structure called the once-per-second (OPS) structure. The following C code fragment is an example of how to fill the OPS structure. It gets executed once for every new binary block (i.e. 50 times per second). BHC2_BINARY_BLOCK0 bblk; /* binary block (no waveforms) */ union { char bytes[150]; /* individual data bytes */ BHC2_OPS_DATA opsd; /* OPS data */ } uboth; char *ptr; /* data pointer */... ptr = uboth.bytes + (3 * (bblk.seqnum % 50)); *(ptr + 0) = bblk.nonwfdata[0]; *(ptr + 1) = bblk.nonwfdata[1]; *(ptr + 2) = bblk.nonwfdata[2]; The numeric data and status from an individual parameter cannot be used unless all bytes related to that parameter meet the following two criteria: All bytes must be from the same one second scan; and All bytes must be from good 50 Hz binary blocks. Note that data and status from a single parameter are not always grouped together. In particular, the error flags are not grouped with the other data and status. This must be considered when determining if the about two criteria are met. The OPS structure contains a member called "lsdata". This is used to build a 160 byte structure called the low speed (LS) structure by a method similar to building the OPS structure itself. The complete LS structure is available once per 10 second interval. Each binary block has two checksums. This checksum is calculated using the standard 8-bit CRC CCITT calculation which utilizes the generating polynomial x 8 + x 7 + x The first value, CSum[0], contains the checksum for the binary block. The second value, CSum[1], contains the one's compliment of the 21

24 checksum (CSum[0]). The checksum is calculated for the WFStats, WFData, and NonWFData. The SeqNum and ocoseqnum are not part of the checksum calculation ocoseqnum 5.2 OPS Data Particulars This member is the ones' compliment of SeqNum. ocoseqnum allows the host to find the start of a 50 Hz binary block as quickly as possible after loss of block synchronization. NOTE: If a transport method is used to send binary blocks that has it's own error checking and block framing mechanisms, then the CSum and ocoseqnum members need not be considered. These two members can be reconstructed at the receiver. NOTE: The data that makes up the OPS structure is captured, in its entirety, before the first byte of the next OPS structure is sent. The contents of the OPS structure should be viewed as a snapshot of the data values at the beginning of this one second interval. The LS structures are handled the same way. The selected LS structure should be viewed as a snapshot of the data values at the beginning of the 10 second interval. The following section gives further details to some of the OPS Data Structure Elements Waveform Config The waveform config field is a data type (16 bits) with each of the low order 11 bits corresponding to one of the 11 possible waveforms to be sent. If the prescribed bit field is SET (logical True) then that waveform is being sent; conversely, if the bit field is CLEAR (logical False) the corresponding waveform is not being sent. The bit field to waveform mapping is given below. X X X X L K X X X X X X X X X X Temperature Units In Plus Emulation mode the temperature value is given in tenths of degrees Centigrade; for Native Mode the temperature value is given in tenths of degrees Fahrenheit. The units that the temperature values are reported in DO NOT VARY; regardless of how the temperature is displayed at the bedside Binary Count Value The binary count value is provided as a means for the Host programmer to know when the binary data that a unit is sending is about to expire. In some instances this is the desired case; however, when the binary count is approaching a minimum value another *Yn command will have to be sent to keep Binary Mode active. To translate the value of 'n' to a time value you need to know that the count is decremented for each Quad Binary Block transmitted, which occurs at a 12.5 Hz rate so 12.5 counts equal 1 second. However, that much granularity is not needed. The value 9998 needs 14 bits to be stored it in its entirety. We will only be transmitting 8 bits. The lower 4 bits (bits 0 through 3) will not be transmitted, nor will the upper 2 bits (bits 12 & 13). This leaves bits 4 through 11 as shown below. X X X X By losing the lower 4 bits the granularity of the value is 1 count = 1.28 seconds (a change of 1 now corresponds to 16 counts > 16/12.5 = 1.28). By not including the upper two bits, this means that a value of 255 can be a value from 9998 (13.33 minutes) to 3855 (5.14 minutes) System Time - Year

25 The system time is returned in an array of 6 unsigned char's. To obtain the current year (with century information) use the following algorithm Patient Type If(systime.year > 89) yearwithcentury = systime.year ; else yearwithcentury = systime.year ; The following definitions apply to the patienttype field: 0 Adult patient 1 Neonate patient 2 Pediatric patient All other values are invalid Host Comm Revision There are two (2) Host Comm Revision Numbers: one for Plus Emulation mode and one for Native Mode. To obtain the current Host Comm Revision Number of either protocol the Host may check the appropriate field in the binary data or issue a *? Command (for Plus Emulation only) or *?? command (for both Plus Emulation & Native Mode) NIPB Pressure The NIBP Pressure returned for Plus Emulation is the Target Cuff Pressure. This has been changed in Native Mode to be the actual Cuff Pressure. This value will now match the values displayed by the Monitor. 23

26 5.3 Invalid Parameter Values Interpretation of non-waveform data (values contained in the OPS & LS structures), must be subject to the following conditions: If the status field for a particular parameter indicates that data is invalid then none of the values associated with that parameter should be considered valid. Invalid values for parameters can be interpreted as the positive and/or negative maximum for the data type. Examples: char (-128 or 127); unsigned char (255); ( or 32767); and unsigned (65535). A zero should be interpreted as a valid parameter value; except where noted otherwise. 5.4 Operational Differences 1. When the unit is in Configuration Mode, neither of the communications ports will be operational. This means that ASCII commands cannot be sent or received, nor will Binary Data (either Plus Emulation or Native modes), be sent. Host Comm will be restarted per the new configuration after Configuration Mode has been exited. 2. The first OPS structure received after HostComm has been started up will consist of all 0's and should be discarded. This is due to the fact that we are always sending the previous second's data and, as such, the first second after starting Binary Mode there is no valid data to send. The first LS structure received should contain correct information since it is gathered on the first second of the 10 seconds required to send it in its entirety. 24

27 6.0 MPS Alarm FLAG ENCODING Prior to the release of Day 3 software (SELECT/PORTABLE), alarm conditions were encodes as bits in three (3) 16-bit integers. This is the format that the current VitalNet Central Station uses to get alarm information and is fully supported by the PRO 1000 software via Plus Emulation Binary Mode or via the *L ASCII command. Each of the three (3) 16-bit integers is identified by a group number from 0 to 2. Of the 48 possible alarm flags, there are currently 36 alarm conditions defined in the Monitor. 6.1 All Alarms All but the and Bed Alarms are heritage PLUS alarms; & Bed Alarms were added for the MPS monitors. They will also be used to communicated the PRO 1000 alarms which do not map into the existing PLUS alarms. The following is a set of guidelines and conditions for all alarms. indicates procedural or technical alarms. Bed Alarm indicates a parameter limit condition has been violated. Unacknowledged crisis alarms set the Bed Alarm. When a parameter is turned off, the data is invalid. No alarm is generated. When a parameter Fatals (failed/error), the alarm bit is cleared with the user acknowledges it via the dialog box. When in Standby, the All Standby alarm bit is set. It is up to the Host to ignore subsequent alarms and data during this period. Group[0] Pulse Rate Low Pulse Rate High Pulse Ox Saturation Low Pulse Ox Sat. High NIBP Systolic Low NIBP Systolic High NIBP Diastolic Low NIBP Diastolic High NIBP MAP Low NIBP MAP High PR1 Systolic Low PR1 Systolic High PR1 Diastolic Low PR1 Diastolic High PR1 Mean Low PR1 Mean High 25

28 Group[1] PR2 Systolic Low PR2 Systolic High PR2 Diastolic Low PR2 Diastolic High PR2 Mean Low PR2 Mean High Temperature High Temperature Low ECG Lead Fail All Standby Alarm Very Low Battery NIBP Procedural Pulse Ox Procedural Printer Procedural Invasive Pressure Discon Temperature Disconnect Group[2] Internal RAM Battery Low RAM Lost on Power Down Bed Alarm RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED NOTE: The Bed Alarm and bits ARE NOT set by any other alarm that already has a bit assigned in this table. These two bits indicate that an alarm is pending that has not been otherwise indicated. 26

29 6.2 ECG Alarm Mapping The PRO 1000 ECG Parameter alarms are mapped as follows ALARM CONDITION ECG Asystole ECG Primary Lead Fault ECG Replace Electrodes ECG Artifact ECG Parameter Failed ECG Parameter Error ECG Vfib ECG Vtach CORRESPONDING ALARM Bed Alarm ECG Lead Fail Bed Alarm Bed Alarm 6.3 Respiration Alarm Mapping The PRO 1000 Respiration Parameter alarms are mapped as follows. ALARM CONDITION Resp High Resp Low Resp Artifact Resp Baseline Saturation Resp Lead Fail Resp Rate Approaching HR Resp Parameter Failed Resp Parameter Error CORRESPONDING ALARM Bed Alarm Bed Alarm 6.4 NIBP Alarm Mapping The PRO 1000 NIBP Parameter alarms are mapped as follows. ALARM CONDITION NIBP Systolic High NIBP Systolic Low NIBP Map High NIBP Map Low NIBP Diastolic High NIBP Diastolic Low NIBP No Determination NIBP Level Timeout NIBP Total Timeout NIBP Pump Timeout NIBP OverPressure NIBP Parameter Failed NIBP Parameter Error CORRESPONDING ALARM NIBP Systolic High NIBP Systolic Low NIBP Map High NIBP MAP Low NIBP Diastolic High NIBP Diastolic Low NIBP Procedural NIBP Procedural NIBP Procedural NIBP Procedural NIBP Procedural 27

30 6.5 SPO2 Alarm Mapping The PRO 1000 SPO2 Parameter alarms are mapped as follows. ALARM CONDITION SPO2 High SPO2 Low SPO2 PR High SPO2 PR Low SPO2 Lost Pulse SPO2 Sensor Disconnected SPO2 Check Cable SPO2 Parameter Failed SPO2 Parameter Error CORRESPONDING ALARM Pulse Ox Saturation High Pulse Ox Saturation Low Bed Alarm Bed Alarm Pulse Ox Procedural Pulse Ox Procedural 6.6 Temperature Alarm Mapping The PRO 1000 Temperature Parameter alarms are mapped as follows. ALARM CONDITION Temp Disconnected Temp Two Probes Out Temp Timed Out Temp Probes Same Type Temp Check Probe Temp Parameter Failed Temp Parameter Error CORRESPONDING ALARM Temp Disconnect 6.7 HR/Pulse Alarm Mapping The PRO 1000 HR/Pulse Parameter alarms are mapped as follows. ALARM CONDITION Heart Rate High Heart Rate Low CORRESPONDING ALARM Pulse Rate High Pulse Rate Low 6.8 Recorder Alarm Mapping The PRO 1000 HR/Pulse Parameter alarms are mapped as follows. ALARM CONDITION Recorder Door Open Recorder Out Of Paper Recorder Cannot Print Recorder Parameter Failed CORRESPONDING ALARM Printer Procedural Printer Procedural Printer Procedural 6.9 System Alarm Mapping The PRO 1000 System alarms are mapped as follows. ALARM CONDITION Memory Lost Battery Low CORRESPONDING ALARM RAM Lost When Powered Down Very Low Battery 28

31 7.0 Native Mode Alarm Handling There are over 200 different alarms in the SUNSCREEN monitor and several can be active at any particular time. Each possible alarm is identified by an integer value from 0 to 287. This is called the alarm number. Further, the operator can set most of these alarms to any of four severity levels. The following discussion requires the definition of a bit index. An array of n characters (char ch[n]) contains 8*n bits. Each bit can be addressed by a bit index ranging from 0 to 8*n-1 as follows. Array Element MSB LSB ch[0] bit index 0 bit index 7 ch[1] bit index 8 bit index ch[n-1] bit index 8*n-8 bit index 8*n-1 The ON/OFF status of each alarm is conveyed by a single bit in a 36 byte array named alarmflags in the OPS structure. Alarm number m is active if the bit indexed by bit index m is a 1; otherwise, alarm number m is inactive. Not all alarm flags are used. Refer to the following section for the meaning of each alarm bit. Each alarm can have one of 4 severity levels. The severity of each alarm is conveyed by two bit pairs in a 72 byte array named alarmtype in the LS structure that contains the alarm limits. The four severity levels (0 is low, 3 is high) and their severity codes are as follows Alarm Level Severity Code 0 Message 1 Procedural 2 Warning 3 Crisis The bit in the severity level for alarm number m that has a weight of 2 is specified by bit index 2*m in the alarmtype array. The bit in the severity level for alarm number m that has a weight of 1 is specified by bit index 2*m+1 in the alarmtype array. NOTE: The Alarm Levels contain default values unless the corresponding parameter is operational or the Alarm Level has been modified by the Host/User. NOTE: Alarms are reported by the system and should ALWAYS be considered valid, regardless of the parameter status. NOTE: The alarm priority of Off is not supported by Host Comm. It will always be reported as Message. 29

32 8.0 Native Mode Alarm Mapping For Native Mode all possible alarms will be sent, not just a group alarm. To this end, the alarms have been mapped into the bit fields of 30 Bytes as shown below. New additions will be appended to the end of the structure. To decode the Alarm Priority s for the associated alarm, simply treat the incoming data as unsigned s instead of bytes and allow 2 bits for each priority (values from 0 to 3). This way, the offsets remain the same. (e.g.: USHORT[5], bits 3*2 and (3*2) 1 yield the Priority associated with BYTE[5], bit 3). Byte[0] Standby Alarm Alarm In Progress UnACKed Alarms UNDEFINED UNDEFINED UNDEFINED UNDEFINED Byte[1] Alarm Fatal Alarm Removed Alarm Fail Alarm Error Alarm Too Many Alarm None ART Fatal ART Removed Byte[2] ART Fail ART Error ART Too Many PA Fatal PA Removed PA Fail PA Error PA Too Many Byte[3] CVP Fatal CVP Removed CVP Fail CVP Error CVP Too Many RA Fatal RA Removed RA Fail Byte[4] RA Error RA Too Many LA Fatal LA Removed LA Fail LA Error LA Too Many ICP Fatal Byte[5] ICP Removed ICP Fail ICP Error ICP Too Many UAC Fatal UAC Removed UAC Fail UAC Error 30

33 Byte[6] UAC Too Many UVC Fatal UVC Removed UVC Fail UVC Error UVC Too Many IP Fatal IP Removed Byte[7] IP Fail IP Error IP Too Many UNLABELED Fatal UNLABELED Removed UNLABELED Fail UNLABELED Error UNLABELED Too Many Byte[8] Pulse Fatal Pulse Removed Pulse Fail Pulse Error Pulse Too Many ECG Fatal ECG Removed ECG Fail Byte[9] ECG Error ECG Too Many Temp Fatal Temp Removed Temp Fail Temp Error Temp Too Many CO2 Fatal Byte[10] CO2 Removed CO2 Fail CO2 Error CO2 Too Many Resp Fatal Resp Removed Resp Fail Resp Error Byte[11] Resp Too Many SPO2 Fatal SPO2 Removed SPO2 Fail SPO2 Error SPO2 Too Many NIBP Fatal NIBP Removed Byte[12] NIBP Fail NIBP Error NIBP Too Many Recorder Fatal Recorder Removed Recorder Fail Recorder Error Recorder Too Many 31

34 Byte[13] ART Sys Hi PA Sys Hi CVP Sys Hi RA Sys Hi LA Sys Hi ICP Sys Hi UAC Sys Hi UVC Sys Hi Byte[14] IP Sys Hi ART Sys Lo PA Sys Lo CVP Sys Lo RA Sys Lo LA Sys Lo ICP Sys Lo UAC Sys Lo Byte[15] UVC Sys Lo IP Sys Lo ART Dias Hi PA Dias Hi CVP Dias Hi RA Dial Hi LA Dias Hi ICP Dias Hi Byte[16] UAC Dias Hi UVC Dias Hi IP Dias Hi ART Dias Lo PA Dias Lo CVP Dias Lo RA Dias Lo LA Dias Lo Byte[17] ICP Dias Lo UAC Dias Lo UVC Dias Lo IP Dias Lo ART Mean Hi PA Mean Hi CVP Mean Hi RA Mean Hi Byte[18] LA Mean Hi ICP Mean Hi UAC Mean Hi UVC Mean Hi IP Mean Hi ART Mean Lo PA Mean Lo CVP Mean Lo Byte[19] RA Mean Lo LA Mean Lo ICP Mean Lo UAC Mean Lo UVC Mean Lo IP Mean Lo ART No Signal PA No Signal 32

35 Byte[20] CVP No Signal RA No Signal LA No Signal ICP No Signal UAC No Signal UVC No Signal IP No Signal ART Not Zeroed Byte[21] PA Not Zeroed CVP Not Zeroed RA Not Zeroed LA Not Zeroed ICP Not Zeroed UAC Not Zeroed UVC Not Zeroed IP Not Zeroed Byte[22] ART Disconnect PA Disconnect CVP Disconnect RA Disconnect LA Disconnect ICP Disconnect UAC Disconnect UVC Disconnect Byte[23] IP Disconnect ECG Artifact ECG Replace Electrodes ECG Lead Fail Asystole Resp Hi Resp Lo Resp Artifact Byte[24] Resp Baseline Sat Resp Lead Fail Resp Rate App HR CO2 Resp Rate High CO2 Resp Rate Low CO2 High CO2 Low CO2 No Breath Byte[25] CO2 Sensor Unplugged CO2 Sensor Too Hot CO2 Sensor Faulty CO2 Sampling Line Broken CO2 Sampling Line Blocked CO2 Sensor Need Cal CO2 Zero Cal Error CO2 Check Adapter Byte[26] CO2 Cal Cannula (OBSOLETED) NIBP Sys High NIBP Sys Low NIBP Dias High NIBP Dias Low NIBP Map High NIBP Map Low NIBP No Det 33

36 Byte[27] NIBP Over Pressure NIBP Pump TO NIBP Total TO NIBP Level TO SPO2 Sat High SPO2 Sat Low SPO2 Sensor Off SPO2 Lost Pulse Byte[28] Pulse Rate High Pulse Rate Low Temp High Temp Low Temp Sensor Off Recorder No Paper Recorder Door Open Recorder Cannot Print 34