Siemens Rapidlab 348EX Host Interface

RAPIDLab 348EX
S ys te m
Interface Specifications Manual
10698303 Rev. A, 2012-03

© 2012 Siemens Healthcare Diagnostics. All rights reserved.
No part of this manual or the products it describes may be reproduced by any means or in any
form without prior consent in writing from Siemens Healthcare Diagnostics.
RAPIDLab, RAPIDComm, and RAPIDLink are trademarks of Siemens Healthcare Diagnostics.
www.siemens.com/diagnostics
The information in this guide was correct at the time of printing. However, Siemens continues to
improve products and reserves the right to change specifications, equipment, and maintenance
procedures at any time without notice.
Implementing an LIS software interface to a RAPIDLab 348EX system is solely the responsibility of
the customer. Siemens recommends that a professional software programmer develop and
implement the LIS software interface. Siemens is not responsible for any communications
problems or for any damage to a RAPIDLab 348EX system or an LIS that might result from
implementing an LIS communication protocol.
Contents
Contents
1 Introduction
Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
About the Communication Protocols . . . . . . . . . . . . . . . . . . .7
2 Setting up the Hardware Connection

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Connecting the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Protocol Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Protocol Support for RS232 Ports. . . . . . . . . . . . . . . . . . . . . .10
3 Interfacing to a Data Management System

Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Configuring Data Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
LIS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Interfacing with an External Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
LIS 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Messages Supported by LIS 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
LIS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Patient, QC, and Calibration Transactions

Patient Sample Transactions . . . . . . . . . . . . . . . . . . . . . . . . .17
Measurement Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Data Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Request Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Sample Assay Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
QC Assay Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Measurement Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Data Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Request QC Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
QC Assay Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
RAPIDLab 348EX Interface Specification Guide page 3

Delete QC Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Calibration Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Calibration Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Data Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Request Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Calibration Pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Device Identity Transactions . . . . . . . . . . . . . . . . . . . . . . . . . 22
Sample Assay Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Remote Control Transactions . . . . . . . . . . . . . . . . . . . . . . . . 23
1-Point or 2-Point Calibration Request . . . . . . . . . . . . . . . . . . . . . 23
Wash Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Sample Analysis Lock-Out Request . . . . . . . . . . . . . . . . . . . . . . . . 23
LIS 3 Communication Protocol Formats . . . . . . . . . . . . . . . . 24
Frame Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Acknowledgement Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Message Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Flow Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Checksum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ID Data Message Checksum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Maximum Transmission Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Example Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Transaction Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
5 Message Formats
Identifier Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sample Assay Data Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Exceptions for Gases and Electrolytes . . . . . . . . . . . . . . . . . . . . . . . . . .36
Exceptions for Hematocrit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Sample Assay Data Record (Dialysis Fluid) . . . . . . . . . . . . . . . . . . 36
Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
QC Assay Data Record – LIS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
page 4 RAPIDLab 348EX Interface Specification Guide

QC File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Calibration Data Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1-Point Total (Calibration Only) – LIS 3 . . . . . . . . . . . . . . . . . . . . . . . . 40
2-Point Total (Calibration and Slope) – LIS 3 . . . . . . . . . . . . . . . . . . . . 41
Hematocrit Slope – LIS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Gas and pH/Electrolyte Calibrations . . . . . . . . . . . . . . . . . . . . . . . 43
Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Sample Assay Order Data Record . . . . . . . . . . . . . . . . . . . . . . . . . 44
Examples of Data Records . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Sample Data Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Example of an Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
QC Data Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Calibration Data Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Device Identity Data Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Index

1 Introduction
The RAPIDLab® 348EX system transmits patient sample data, quality

control (QC) sample data, and system calibration data to a laboratory
information system (LIS) or to a hospital information system (HIS), either
directly or through a data manager. Transmission of patient sample, QC
sample, and calibration data can be automatic or only upon request of the
LIS or the operator. The system also communicates with an external printer
if one is configured.
For a complete description of the system, its intended use, and how to
operate it, see the RAPIDLab 348EX Operator’s Guide.
Communication Options
The system can communicate with a variety of systems through the RS232
ports at the rear of the instrument. Specific systems with which the system
can communicate are:
• External printers
• RAPIDLink® Data Management System
• RAPIDComm® Data Management System
• LIS/HIS systems
This guide provides information that helps you connect the
RAPIDLab 348EX system with any of these systems. For configuration
information, see the RAPIDLab 348EX Operator’s Guide.
About the Communication Protocols

The system uses the different protocols for different kinds of data
transmissions:
• LIS 1 protocol communicates with external printers
• LIS 2 protocol sends data messages in one direction following the
completion of patient sample, quality control or calibration
measurements

Introduction
• LIS 3 protocol transmits patient, QC, and calibration data from the
system to the LIS or HIS upon the request of the LIS.
Messages sent using the LIS 3 protocol are enclosed within control
characters so that the LIS can detect the start and end of transmissions.
Each message also includes a checksum to enable the detection of bad
transmissions. Messages are automatically retransmitted once if the LIS
does not acknowledge a transmission.

2 Setting up the Hardware Connection
Hardware Requirements
The system has two data ports. (See Figure 1.)
• Port 1 supports 3 data communication protocols.
• Port 2 supports only the LIS 1 protocol. Use port 2 when connecting an
external printer.
For information about configuring the data ports, see the RAPIDLab 348EX
Operator’s Guide.
The interconnection cable required depends on the PC used as the platform
for the data management system. The output pin configuration of both
RS232 ports is as follows:
Figure 1: Left: Port 1 (Female), Right: Port 2 (Male)
Data Port 1 (Female) Data Port 2 (Male)

Pin 1 Not used Pin 1 Not used
Pin 2 Tx data (transmitted) Pin 2 Tx data (transmitted)
Pin 3 Rx data (received) Pin 3 Rx data (received)
Pin 4 DTR (data terminal ready) Pin 4 DTR (data terminal ready)
Pin 5 0V digital Pin 5 0V digital
Pin 8 CTS (clear to send) Pin 8 CTS (clear to send)
Pin 9 Not used Pin 9 +5V digital
Connecting the Hardware

1. Ensure that power is disconnected from both the PC or printer and the
RAPIDLab 348EX system.
2. Connect the two systems using the appropriate cable.

Setting up the Hardware Connection
3. Reconnect the power and turn on both systems and the printer.
The systems are now connected.
4. Configure the protocol to use for each port.
For detailed configuration information, see the RAPIDLab 348EX
Operator’s Guide.
Protocol Specifications
Protocol Supports
LIS 1 Communication to an external printer or to a data
collection system that can accept an asynchronous,
unidirectional data transmission.
LIS 2 Unidirectional communications with an external LIS
system.
LIS 3 Bi-directional communications with an external data
management system such as a RAPIDLink, RAPIDComm,
HIS, or LIS system.
Protocol Support for RS232 Ports

Port Protocol Support
1 LIS 1
LIS 2
LIS 3
2 LIS 1

3 Interfacing to a Data Management System
The system communicates with a RAPIDLink Data Management System, a

RAPIDComm Data Management System, and with laboratory and hospital
information systems (LIS/HIS).
The system transmits data without any handshaking protocol, and
transmission begins as soon as the data is ready in the system (for
example, measurement complete, calibration complete, and so on).
Data Format
The transmitted data reflects the internal printer format. The system does
not transmit any control codes. The blocks of data that are transmitted are
as follows:
• Sample data
• QC sample data
• Calibration data
• Set-up data
• Calibration history file
• QC analysis file
• Test sample data
Conventions
This guide uses the following conventions to represent string delimiters:
Symbol Description
< > (angle brackets) Delimit a control code
{ } (braces) Delimit data strings
Note These characters are not transmitted as part of any message.
Configuring Data Ports

You can configure both RS232 data ports to your requirements. See the
RAPIDLab 348EX Operator’s Guide for detailed configuration information.
1. Select Ready > Settings > System Setup > Communications.

Interfacing to a Data Management System
2. To set the protocol to use for Port 1, select Port 1 Protocol, then select
the appropriate option:
• LIS 1 (default)
• LIS 2
• LIS 3
Note Selecting a different protocol for a port overwrites previous
selections.
3. To set the communication options for Port 1, select Port 1 Options,
then select the appropriate parameters:
Parameter Possible Values Default Value

Baud rate 300 9600
2400
4800
9600
Stop bit 1 or 2 1
Parity Even Off
Odd
Off
These same options apply to all 3 protocols.

Note The protocol for Port 2 is preset to LIS 1, the only acceptable protocol
for Port 2.
4. To set the baud rate, stop bit, and parity for Port 2, select Port 2
Options.
These parameters are the same as for Port 1.
Note The system uses the default options whenever you select any
protocol, unless you specify otherwise.

5. Select the protocol for the designated output port as follows:
For Communication With Port Protocol

External printer or a data collection 2 LIS 1
system that can accept an
asynchronous, unidirectional data
transmission.
A data management system, such as a 1 LIS 3

RAPIDComm system or a RAPIDLink
system, requiring bidirectional data
flow
A data management system requiring 1 LIS 2

unidirectional data flow
LIS 1
Interfacing with an External Printer
Use the LIS 1 protocol when interfacing with an external printer or with
any device using a printer-compatible communications format.
LIS 2
• The LIS 2 protocol transmits data messages following the completion

of patient sample, quality control or calibration measurements.
• The LIS 2 protocol does not support sample assay order, QC assay order
or remote control transactions.
• The data flow is uni-directional using XON/XOFF flow control to
prevent buffer overrun.
For details about flow control, see Flow Control, page 4-25.
• LIS 2 uses limited error detection by sending a modulo-25610
checksum with every message.
The checksum consists of 2 ASCII characters that represent a
2-character hexadecimal number in the range 00–FF, expressed as an
8-bit unsigned hexadecimal integer.
• The protocol options are the same as for LIS 1.

Data Messages Supported by LIS 2
Sample Data {SMP_NEW_DATA}{Sample assay data}

Edited Sample Data {SMP_EDIT_DATA}{Sample assay data}
QC Data {QC_NEW_DATA}{QC assay data}
QC Delete Data {QC_DEL}{aMOD, iIID, iQFILE, rSEQ, rDATE, rTIME}
Calibration Data {CAL_NEW_DATA}{Calibration data}
For details about data records, see LIS 3 Communication Protocol Formats
on page 24
LIS 3
Using the LIS 3 protocol, the system transmits a data-available message
following the completion of a patient sample, quality control, or calibration
measurement. It is then up to the LIS to request that data. The system also
sends a data-available message if the operator initiates a print function for
the respective data.
In addition to patient and operator identification, the protocol also
supports instrument identification, sample assay order and some remote
control transactions.
LIS 3 also includes a mechanism for requesting a retransmission of data
upon detection of a transmission error. This mechanism uses a relatively
simple message acknowledgement protocol that allows one retry.
When using the LIS 3 protocol, the receiving system must respond to all
messages with the acknowledge message.
The protocol does not detect when the same, error-free message is
transmitted twice. This situation can occur when the receiving device
acknowledges an error-free message, but the acknowledgement is
corrupted, causing the transmitting device to resend the message.
• If the LIS application has a problem with receiving duplicated data,
then the receiver can check each data message to ensure it is not a
duplicate of the preceding message.
• If the environment in which the interface is used has a low risk of
message corruption, then the application can choose to ignore the
possibility of a duplicate message.
• If the environment is noisy, it may be useful, to use hardware, (for
example, short haul modems), to improve the environment and still
ignore the possibility of a duplicated message.

Note Transmission of duplicate data messages can also occur in an error

free environment with multiple operator selections of the print option,
with a recall data function.
The messages are enclosed within control characters to allow the detection
of start and end transmissions. The messages also include a checksum to
enable the detection of bad transmissions.
To aid in parsing messages, delimiters are used to identify variable
boundaries. See the description of the data messages in Section 5,
Message Formats for descriptions of the control characters and delimiters
in the messages.


4 Patient, QC, and Calibration Transactions
Patient and QC measurements have separate sequence numbers. The

patient and QC sequence numbers run from 1 to 99999 and then revert
back to 1.
Calibrations are assigned a sequence number starting at 1 and
incrementing to 99999 and then reverting to 1.
When new patient, QC, or calibration data is generated, the system informs
the LIS of its availability and also indicates the appropriate sequence
number allocated to the data.
To obtain patient, QC, or calibration data, the LIS must include the required
sequence number in the data request message.
The system stores the last 250 patient results, and the last 90 QC results for
each level, and a 24-hour calibration history file. Because of the format of
the calibration history file, only the last calibration data is available in LIS 3
format.
Patient Sample Transactions

Measurement Status
System Action Function Message Content
Informs the LIS Sample LIS 3 {SMP_START}{aMOD,iIID}
when a patient measurement
sample initiated (sample
measurement is start).
initiated (sample
detected).
Detects a bubble Sample LIS 3 {SMP_ABORT}{aMOD,iIID}
in the sample, and measurement
the user selects canceled.
the Flush option.
Note The system should send the sample canceled message only after it
has sent the sample start message.

Patient, QC, and Calibration Transactions
Data Available
The following messages indicate to the LIS when patient sample data is
available:
Sample assay: LIS 3 {SMP_NEW_AV}{aMOD,iIID,rSEQ}
This message is initiated by the system when results are available following
a patient sample measurement process. It signals completion of the assay
for sample sequence # rSEQ.
The same message is initiated for updated data when the operator selects
Print Data in Data Recall.
Request Sample Data

Following the notification of data availability, the external device may
request the data, by sending the following message, which identifies the
sequence number of the required sample data:
Request sample data: LIS 3 {SMP_REQ}{aMOD,iIID,rSEQ}
Sample Assay Data

If the requested data is no longer available, the system sends the following
message:
Sample data not available: LIS 3 {SMP_NOT_AV}{aMOD,iIID,rSEQ}
If the requested data is available, the system sends one of the following
messages:
• Sample data original: {SMP_NEW_DATA}{sample assay data}
• Edited sample data: If the operator recalls and edits patient sample
data and then selects Print Data, the system sends the following
message:
LIS 3 {SMP_NEW_AV}{aMOD,iIID,rSEQ}
If the LIS responds with the SMP_REQ message, the system sends the
following message:
{SMP_EDIT_DATA}{Sample assay data)
Refer to Sample Assay Data Record, page 33 and Sample Assay Data
Record (Dialysis Fluid), page 36 for descriptions of sample assay data
records.

QC Assay Transactions
The system does not support QC assay order and QC Set-up File
transactions.
Measurement Status
The system informs the LIS when it initiates a QC sample measurement
(sample detected) and when, if applicable, the operator cancels the
measurement sequence. The system sends the following message:
QC sample measurement initiated: LIS 3 {QC_START}{aMOD,iIID}
Data Available
The following message indicates to the LIS that QC data is available.
QC assay: LIS 3 {QC_NEW_AV}{aMOD,iIID,rSEQ}
The system initiates this message when results are available following a QC
measurement process. It signals completion of the assay for QC sequence
# rSEQ.
The system transmits the same message in Data Recall when the Print QC
Data option is selected.
Request QC Data
After being notified that data is available, the LIS may request the data by
sending the following message, which identifies the sequence number of
the required QC data:
Request QC data: LIS 3 {QC_REQ}{aMOD,illD,rSEQ}
QC Assay Data
message:
QC data not available: LIS 3 {QC_NOT_AV}{aMOD,iIID,rSEQ}
If the requested data is available, the system sends the following message:
QC data original: {QC_NEW_DATA}{QC assay data}
See QC Assay Data Record – LIS 3, page 37 for a description of QC assay
data records.

Delete QC Data
To allow the LIS to track QC sample file operations performed on the
system, the following delete message is made available.
QC delete data:
LIS 3 {QC_DEL}{aMOD,iIID,iQFILE,rSEQ,rDATE,rTIME}
The system transmits this delete message as a result of the following data
operation:
The user recalls a QC sample and moves it to another QC file at the system.
In this case, the system sends the delete message, followed by a
QC_NEW_AV message for the new file entry.
If user moves a QC sample to a full file, and the QC sample is older than any
other samples in the file, then it will be discarded.
Calibration Transactions
Calibration Initiated
The system sends the following messages to the LIS when a calibration
sequence is initiated and when the operator cancels the sequence:
Calibration initiated: LIS 3 {CAL_START}{aMOD,iIID}
Calibration canceled: LIS 3 {CAL ABORT}{aMOD,iIID}
Data Available
The following messages indicate to the external device when calibration
data is available:
Calibration: LIS 3 {CAL_NEW_AV}{aMOD,iIID,rSEQ}
The system initiates this message when results are available following the
measurement of a calibrant. It signals completion of the measurement for
calibration sequence # rSEQ.
Request Calibration Data

Following the notification of data availability, the external device may
request the data by sending the following message, which identifies the
sequence number of the requested calibration data:
Request calibration data: LIS 3 {CAL_REQ}{aMOD,iIID,rSEQ}

Calibration Data
message:
Calibration data not available: LIS 3 {CAL_NOT_AV}{aMOD,iIID,rSEQ}
If the requested data is available, the system sends the following message:
Calibration data original: {CAL_NEW_DATA}{calibration data}
Note Only the last calibration is available. Previous calibrations are stored
in the history file in a different format.
Calibration Pending
The system sends the following message when the countdown to the next
calibration reaches the last 5 minutes:
{SYS_CAL_PEND}{aMOD,iIID}
The calibration data records sent by the system depend upon the particular
type of calibration performed. Each type of calibration sequence contains
either a cal data set, a slope data set, or both:
• Hematocrit (slope only)
• 1-point Total (cal only)
• 2-point Total (cal followed by slope)
• 1-point Gas (cal only)
• 2-point Gas (cal followed by slope)
• 1-point pH/electrolytes + Hct (cal only)
• 2-point pH/electrolytes (cal followed by slope)
Within each calibration and slope data set, each analyte, except measured
barometric pressure, is represented by 3 entries, as shown in the following
table:
Calibration (Cal) Slope

Format Function Format Function
aCmname MEASURED aSmname MEASURED
aCaname ADJUSTED aSaname ADJUSTED
aCdname DRIFT aSdname DRIFT
In this table, the terms in the Function columns have the following
meanings:
• MEASURED is the measured calibrant value.
• ADJUSTED is the system's target calibrant value.

• DRIFT is the drift in cal or slope for that analyte, calculated by the
system as: DRIFT = MEASURED – ADJUSTED.
If applicable, one entry at the end of each data set corresponds to the
measured barometric (mBP), if applicable.
Refer to Calibration Data Record, page 40 for a description of calibration
data records.
Note If more than one attempt is made during a calibration, the measured
data sent is the data from the first attempt.
Device Identity Transactions

The LIS device can request the identity of the RAPIDLab 348EX system at
any time by sending the following request identifier message:
Request device identity: {ID_REQ}
The receiving device responds by sending a data record containing the
name and value of the variable aMOD, its model number, and value of the
variable iIID, the serial number. The message format is as follows:
Device identifier: {ID_DATA}{aMOD,iIID}
The variables aMOD and iIID are as defined in the data records for the
system.
Sample Assay Order

The LIS can download to the RAPIDLab 348EX system a patient sample
assay order that provides the patient ID of a sample to be run, and the LIS
can define entered parameters for that sample.
Only one patient assay order should be pending in the system at one time.
If the system is at the Ready screen when it receives a patient assay order,
it prompts the operator to begin sample analysis.
The format of the assay order message is as follows:
{SMP_ORD}{Sample assay order data)
For a description of the sample assay order data record, refer to Sample
Assay Order Data Record, page 44
To cancel the sample assay order, you can perform one of the following
actions:
• Select Cancel from the sample assay order screen.
• Open the probe, select Cancel, then close the probe.

If you perform one of these actions, the system sends the following
message:
LIS 3 {SMP_ORD_ABORT}{aMOD,iIID,iPID}
where iPID is the patient ID sent with the order.

If the system detects a bubble in the sample and the user selects Flush,
then the system sends the following message:
LIS 3 {SMP_ABORT}{aMOD,iIID}
If the system receives a patient sample assay order during the cal-pending
period, the cal pending 5-minute countdown restarts. After 5 minutes, if
the sample has not been measured, the system transmits the calibration-
initiated message, waits for acknowledgement, then transmits the sample
order canceled message.
The system ignores any fields sent that are not defined in the Calibration
Data Record, page 40. The patient ID field must always contain a valid
patient ID. All data sent with the sample assay order can be edited on the
system.
Remote Control Transactions

Note Remote control requests are be acted upon only when the system is
on the "Ready" or ''Not Ready" screen.
1-Point or 2-Point Calibration Request

Note You can request only full 1-point and 2-point calibrations.
• Initiate a 1-point calibration: LIS 3 {CTL_lPT}{aMOD,iIID}
• Initiate a 2-point calibration: LIS 3 {CTL_2PT}{aMOD,iIID}
Wash Request
Initiate wash: LIS 3 {CTL_WASH}{aMOD,iIID}
Sample Analysis Lock-Out Request

Lock sample mode out: LIS 3 {CTL_LOCK}{aMOD,iIID}
Restore sample mode: LIS 3 {CTL_FREE}{aMOD,iIID}

LIS 3 Communication Protocol Formats

The LIS 3 protocol uses message acknowledgements and message retry on
no acknowledgement, plus an XON/XOFF to prevent buffer overrun in the
external (receiving) device.
The system's communication protocol also builds the message to be
transmitted into a frame which includes a checksum for error detection.
Frame Format
The format of the frame is as follows:
<STX>{identifier}<RS>{data}<RS> <ETX>checksum<EOT> Message
where:
• <STX> is the ASCII control character Start of Text (02 decimal).
• <ETX> is the ASCII control character End of Text (03 decimal).
• checksum is the variable 2-digit hexadecimal number included to
support error checking by the receiver.
• <EOT> is the ASCII control character End of Transmission (04 decimal).
Acknowledgement Format
The format of an acknowledgement is as follows:
<STX><ACK><ETX>checksum<EOT>
where:
<ACK> is the ASCII control character Acknowledgement (06 decimal)
This provides a transmission format identical to that used for message

transmission and therefore allows the interrupt mechanism to easily detect
start and end of transmissions.
The checksum for this fixed content acknowledgement is 0B, making the
acknowledgement message:
<STX><ACK><ETX>0B<EOT>
Message Acknowledgement
The LIS software performs the following functions to implement the
acknowledgement protocol:
• When the sender has a message to send, it transmits the message and
starts a timer. It then waits for the receipt of an acknowledgement
from the receiver and also sets a variable, RETRY = FALSE (Transaction
Started).

• When a good message (no parity/framing errors or checksum error) is

received by the receiver, it transmits an acknowledgement to the
sender, and passes the message on to higher levels of the application
code.
• If the sender's timer expires and RETRY = FALSE, the sender retransmits
the message and restarts the timer. It also sets the variable RETRY =
TRUE.
• If the sender's timer expires and RETRY = TRUE, the sender logs an error
(Transaction Complete).
• When a bad message is received, the receiver ignores it.
• When the sender receives an acknowledgement, the sender stops the
timer (Transaction Complete).
The system (or LIS) does not start retry timer until the last character in the
message has been transmitted. (This allows the XON/XOFF to function as
described in the following section.) The timer duration depends on the
baud rate, as follows:
Baud Rate Timer (seconds)

9600 6
4800 8
2400 11
300 15
All messages are acknowledged, provided the aMOD and iIID fields match.
After a message is sent, no further messages are sent until either an
acknowledgement is received or the transaction is complete and an error
logged.
Flow Control
During data transfers, the LIS may monitor its input buffers to ensure that
sufficient space remains to allow it time to react to the receipt of additional
data. When insufficient sufficient space remains, the LIS may send an
<XOFF> to the system, which suspends the transmission until the LIS sends
an <XON>, to indicate that transmission may resume.
Control Character Description

<XON> The ASCII control character Device Control 1
(decimal 17)
<XOFF> The ASCII control character Device Control 3
(decimal 19)

Note If the LIS continuously halts the transmission as soon as it is

resumed, and if additional messages become available for transmission, it
is possible for the LIS to lose messages, as the system's message buffer fills
and overwrites data.
After receiving an XOFF command, the system waits 10 seconds,
irrespective of baud rate, and if it does not receive an XON command
during this time the system resumes transmission. The system ignores
further XOFF commands until after it receives an XON command.
Checksum
The checksum consists of 2 ASCII characters that represent a 2-character
hexadecimal number in the range 00 through FF.
The hexadecimal number is generated by performing a modulo-25610
summation of all the previous characters in the frame (that is, over the
range <STX>..<ETX>, inclusive) and then expressing the resulting 8-bit
unsigned integer in hexadecimal format.
For example, consider the {ID_DATA} message:
<STX>ID_DATA<FS><RS>aMOD<GS>348<GS><GS><GS><FS>iIID
<GS>1234<GS><GS><GS><FS><RS><ETX>
The summation of the value of each character in the string and the
resulting hexadecimal numbers is as follows:
ID Data Message Checksum
Decimal Hexadecimal
Summation 1899 76B
Modulo 25610 107 6B
2-Character Hexadecimal NA 6B
Number
The checksum is transmitted as the two ASCII characters 6 and B.
Maximum Transmission Size

The longest data message that the system transmits is 1500 characters,
including all control characters and the checksum.

Example Transaction
The example describes the messages transmitted during a typical patient
sample analysis. The content of the messages is explained in the message
key following the transaction table.
Transaction Table
RAPIDLab 348EX System LIS

Message #1 (Sample initiated) ---->
<--- Message #2 (Acknowledge)
Message #3 (Assay complete) ---->
<--- Message #4 (Request sample data)
Message #2 (Acknowledge) ---->
Message #5 (sample data) ---->
Message key
Message #1:
<STX>SMP_START<FS><RS>aMOD<GS>348<GS><GS><GS>
<FS>iIID<GS>1234<GS><GS><GS><FS><RS><ETX>43<EOT>
Message #2:
<STX><ACK><ETX>0B<EOT>
Message #3:
<STX>SMP_NEW_AV<FS><RS>aMOD<GS>348<GS><GS><GS>
<FS>iIID<GS>1234<GS><GS><GS><FS>rSEQ<GS>6<GS><GS>
<GS><FS><RS><ETX>B6<EOT>
Message #4:
<STX>SMP_REQ<FS><RS>aMOD<GS>348<GS><GS><GS>
<FS>iIID<GS>1234<GS><GS><GS><FS>rSEQ<GS>6<GS><GS>
<GS><FS><RS><ETX>BE<EOT>
Message #5:
<STX> SMP_NEW_DATA<FS><RS>
aMOD <GS>
348 <GS>

<GS>
<GS><FS>
iIID <GS>
1234 <GS>
<GS>
<GS><FS>
rTYPE <GS>
SAMPLE <GS>
<GS>
<GS><FS>
rSEQ <GS>
6 <GS>
<GS>
<GS><FS>
rDATE 27Nov11
<GS>
<GS><FS>
rTIME <GS>
11:06 <GS>
<GS>
<GS><FS>
iPID <GS>
123-456-789 <GS>
<GS>
<GS><FS>
iOID <GS>
987-654-321 <GS>
<GS>
<GS><FS>
rDEVICE <GS>
SYRINGE <GS>
<GS>
<GS><FS>
mpH <GS>
7.329 <GS>
<GS>
<GS><FS>
mPC02 <GS>

13.5 <GS>
mmHg <GS>
<GS><FS>
mPO2 <GS>
107.2 <GS>
mmHg <GS>
<GS><FS>
mBP <GS>
761 <GS>
mmHg <GS>
<GS><FS>
cHC03std <GS>
27.9 <GS>
mmol/L <GS>
<GS><FS>
cBE(vt) <GS>
3.9 <GS>
mmol/L <GS>
<GS><FS>
ctC02 <GS>
30.1 <GS>
mmol/L <GS>
<GS><FS>
c02SAT <GS>
7.3 <GS>
% <GS>
<GS><FS>
mNa+ <GS>
135 <GS>
mmol/L <GS>
<GS><FS>
mCa++ <GS>
1.17 <GS>
mmol/L <GS>
<GS><FS>
cCa++ <GS>
1.19 <GS>
mmol/L <GS>

<GS><FS>
mK+ <GS>
4.15 <GS>
mmol/L <GS>
<GS><FS>
mHct <GS>
43.5 <GS>
% <GS>
<GS><FS>
ctHb <GS>
14.8 <GS>
g/dL <GS>
<GS><FS><RS>
<ETX>6D<EOT>

5 Message Formats
This section describes the rules for building messages (message structure)
and the rules for decoding the received messages.
Each message consists of at most 2 records:
• The first record identifies the message type (identifier record).
• The second record (if present) contains further information or data
(data record).
The {identifier} record and the {data} record are each terminated by the
ACSII control character Record Separator (decimal 30), <RS>. That is, the
message has the format:
{identifier}<RS>{data}<RS>
Identifier Record Format

The format of the {identifier} record is simply the ASCII characters that
make up the identification, terminated by the ASCII control character Field
Separator (decimal28) <FS>.
The format of the {data} record is a variable number of fields separated by
Field Separators <FS> as follows:
{name}<GS>{value}<GS>{units}<GS>{exception(s)}<ETB>
<GS><FS>
where each field contains 4 groups separated by the ASCII control

character Group Separator (decimal29)<GS>. The groups are as follows:
{name} The parameter for which data is being transmitted.
{value} The actual value of the parameter.

Message Formats
{units} The units applicable to the value of the parameter.

(This field can be empty.)
{exceptions} Error codes appropriate to the parameter being

measured. If no error codes are present, the field is
empty. If 1 or more error codes exist, they are
separated by the ASCII control character End
Transmission Block (decimal 23)<ETB>. For
example:
<GS> no errors reported
{exception}<ETB><GS> one error reported
{exception}<ETB>{exception}<ETB><GS>
two errors reported
Note No group can have more than 2 exceptions.
Date/Time
Day, year, hours, and minutes are sent with leading zeroes; for example, 2
minutes past 8 o'clock on 1 January 2012 is sent as
01Jan1208:02
Invalid dates/times are sent as ddMmmyy and HH:MM.
Sequence Numbers
Sequence numbers appear without leading zeroes in reports. They are
reset only by a restart, which sets the first sequence number to 1.
Canceled samples, calibrations and QC samples do not increment the
associated sequence number.
Data Record Formats

When present, the data record always follows the identifier record. The
data record can be any of several formats:
• Sample Assay Data Record, page 5-33
• Sample Assay Data Record (Dialysis Fluid), page 5-36
• QC Assay Data Record – LIS 3, page 5-37
• Calibration Data Record, page 5-40
• 2-Point Total (Calibration and Slope) – LIS 3, page 5-41
• Hematocrit Slope – LIS 3, page 5-43

Message Formats
• Gas and pH/Electrolyte Calibrations, page 5-43

• Sample Assay Order Data Record, page 5-44
Sample Assay Data Record

Parameter Name Value Units Note
Model aMOD 348
number
Model iIID xnnn 1
identification
Sample type rTYPE SAMPLE
Sequence rSEQ nnnnn
number
Date rDATE ddMmmyy
Time rTIME hh:mm
Patient ID iPID nnnnnnnnnnnnn
nnn
Operator ID iOID nnnnnnnnnnnnn
nnn
Sample rDEVICE CAPILLARY,
device SYRINGE, or
AMPULE
pH mpH n.nnn
(measured) mH+ nnn.n nmol/L
pO2 mPO2 nnn.n mmHg
(measured) nn.nn kPa
pCO2 mPCO2 nnn.n mmHg
(measured) nn.nn kPa
Na+ mNa+ nnn mmol/L
(measured)
K+ mK+ nn.nn mmol/L
(measured)
Ca++ mCa++ n.nn mmol/L 2
Cl– mCl– nnn mmol/L 2
(measured)
Hematocrit mHct nn %
(measured)

Message Formats

Barometric mBP nnn mmHg
Pressure nnn.n kPa
pH cpH n.nnn
(corrected) cH+ nnn.n nmol/L
pCO2 cPCO2 nnn.n mmHg
(corrected) nn.nn kPa
pO2 cPO2 nnn.n mmHg
(corrected) nn.nn kPa
Ca++ cCa++ n.nn mmol/L 3
(corrected)
Actual cHCO3act nn.n mmol/L
Bicarbonate
Standard cHCO3std nn.n cHCO3std
Bicarbonate
Oxygen cO2(CT) nn.n mL/dL 4
Content
Total Carbon ctCO2 nn.n mmol/L
dioxide
Oxygen cO2SAT nnn.n %
Saturation
Alveolar/ cA–aDO2 nnn.n mmHg 5
Arterial nn.n kPa
difference
Arterial/ ca/A nn.n 5
Alveolar Ratio
Base Excess cBE(vt) ±nn.n mmol/L 6
(Blood)
Base Excess cBE(vv) ±nn.n mmol/L 6
(ecf)
Hemoglobin ctHb(est) nn.n g/dL 7
(calculated) nnn g/L
nn.n mmol/L
Anion gap cAnGap ±nn.n mmol/L
Oxygenation cPO2/FIO2 n.nn
ratio
Patient iTEMP nn.n C
temperature

Message Formats

Patient itHb nn.n g/dL 7
Hemoglobin nnn g/L
nn.n mmol/L
Patient FIO2 iFIO2 nnn.n %
Notes
1. The model identification is normally the serial number.
2. Either Ca++ or Cl– is present, but not both.
3. cCa++ is reported only if pH is between 7.20 and 7.60.
4. Oxygen content is reported only if calculated tHb is selected, or an
actual tHb is input.
5. The gas indices are reported only if FIO2 is input.
6. Both Base Excesses can be negative as well as positive.
7. Calculated Hemoglobin is derived from Hematocrit and is overridden by
input Hemoglobin.
If any parameter is not selected, then its associated field is not transmitted.
Exceptions
The following tables show the exceptions to this list in priority order,
highest first, for gases and electrolytes and for Hematocrit.

Message Formats
Exceptions for Gases and Electrolytes
Exception Mnemonic
No end point (unstable) NEP
Bubble in Sample BUB
Split sample SPLIT
Temperature Warning TEMP
Above reporting range >
Below reporting range <
Above reference range H
Below reference range L
Exceptions for Hematocrit
Exception Mnemonic
Split sample SPLIT
Uncorrected UNCORR
Sample Assay Data Record (Dialysis Fluid)

Parameter Name Value
Model number aMOD 348
Model identification iIID xnnn
Sample type rTYPE SAMPLE
Sequence number rSEQ nnnnn
Date rDATE ddMmmyy
Time rTIME hh:mm
Patient ID iPID nnnnnnnnnnnnnnnn
Operator ID iOID nnnnnnnnnnnnnnnn
Sample source iSOURCE DIALYSIS-FLUID
Sample device cDEVICE SYRINGE

Message Formats
Exceptions
Exception Mnemonic
QC Assay Data Record – LIS 3

Note The system reports either Ca++or Cl–, but not both.
Parameter Name Value Units

Model number aMOD 348
Model identifier iIID xnnn
Sample Type rTYPE QC
Date rDATE ddMmmyy
Time rTIME hh:mm
QC file no. iQFILE n
QC level iQLEV n
Lot no. iQLOT aaaaaa
pH (measured) mpH n.nnn
mH+ nnn.n nmol/L
Low QC limit ( pH) sLQmpH n.nnn
sLQmH+ nnn.n nmol/L
High QC limit (pH) sHQmpH n.nnn
sHQmH+ nnn.n nmol/L
pO2 (measured) mPO2 nnn.n mmHg
nn.nn kPa
Low QC limit (pO2) sLQmPO2 nnn.n mmHg
nn.nn kPa
High QC limit (pO2) sHQmPO2 nnn.n mmHg
nn.nn kPa

Message Formats

pCO2 (measured) mPCO2 nnn.n mmHg
nn.nn kPa
Low QC limit sLQmPCO2 nnn.n mmHg
(pCO2) nn.nn kPa
High QC limit sHQmPCO2 nnn.n mmHg
( pCO2) nn.nn kPa
Na+(measured) mNa+ nnn mmol/L
Low QC limit (Na+) sLQmNa+ nnn mmol/L
+)
High QC limit (Na sHQmNa+ nnn mmol/L
+ K+ mmol/L
K (measured) nn.n
Low QC limit (K+) sLQmK+ nn.n mmol/L
High QC limit (K+) sHQmK+ nn.n mmol/L
–
Cl (measured) mCl– nnn mmol/L
–
Low QC limit (Cl ) sLQmCl– nnn mmol/L
High QC limit (Cl –) sHQmCl– nnn mmol/L
Ca++ (measured) mCa++ n.nn mmol/L
Low QC limit sLQmCa++ n.nn mmol/L
(Ca++)
High QC limit sHQmCa++ n.nn mmol/L
(Ca++)
Hematocrit mHct nn.n %
(measured)
Low QC limit (Hct) sLQmHct nn.n %
High QC limit sHQmHct nn.n %
(Hct)
Barometric Pressure mBP nnn mmHg
nnn.n kPa

Message Formats
Exceptions
The following table shows the exceptions for the QC Data Assay
Record in priority order, highest first:
Exception Mnemonic
QC File Structure
The system has a fixed QC file structure, defined as follows:
File number (iQFILE) Level

1 Level I (BG/Electrolytes)
2 Level II (BG/Electrolytes)
3 Level III (BG/Electrolytes)
A Level A (Hct)
B Level B (Hct)
X Level X (Undefined QC)
Lot number (iQLOT) is as entered on the system. Expiration date is a null

field. All other fields associated with the QC file are null fields.

Message Formats
Calibration Data Record

1-Point Total (Calibration Only) – LIS 3

Model Number aMOD 348
Model Identifier iIID xnnn
Calibration type rTYPE 1-POINT
Date rDATE ddMmmyy
Time rTIME hh:mm
Cal pH aCmpH n.nnn
(MEASURED) aCmH+ nnn.n nmol/L
Cal pH aCapH n.nnn
(ADJUSTED) aCaH+ nnn.n nmol/L
Cal pH (DRIFT) aCdpH n.nnn
aCdH+ nnn.n nmol/L
Cal pO2 aCmPO2 nnn.n mmHg
(MEASURED) nn.nn kPa
Cal pO2 aCaPO2 nnn.n mmHg
(ADJUSTED) nn.nn kPa
Cal pO2 (DRIFT) aCdPO2 nnn.n mmHg
nnn.n kPa
Cal pCO2 aCmPCO2 nnn.n mmHg
Cal pCO2 aCaPCO2 nnn.n mmHg
Cal pCO2 (DRIFT) aCdPCO2 nnn.n mmHg
nn.nn kPa
+
Cal Na aCmNa+ nnn mmol/L
(MEASURED)
Cal Na+ aCaNa+ nnn mmol/L
(ADJUSTED)
Cal Na+ (DRIFT) aCdNa+ nnn mmol/L
+
Cal K aCmK+ n.nn mmol/L
(MEASURED)
Cal K+ (ADJUSTED) aCaK+ n.nn mmol/L

Message Formats

Cal K+ (DRIFT) aCdK+ n.nn mmol/L
Cal Ca++ aCmCa++ n.nn mmol/L
(MEASURED)
Cal Ca++ aCaCa++ n.nn mmol/L
(ADJUSTED)
Cal Ca++ (DRIFT) aCdCa++ n.nn mmol/L
Cal Cl– aCmCl– nnn mmol/L
(MEASURED)
Cal Cl– aCaCl– nnn mmol/L
(ADJUSTED)
Cal Cl– (DRIFT) aCdCl– nnn mmol/L
Cal Hct aCmHct nn.n %
(MEASURED)
Cal Hct aCaHct nn.n %
(ADJUSTED)
Cal Hct (DRIFT) aCdHct nn.n %
Barometric mBP nnn mmHg
Pressure
nnn.n kPa
Note The DRIFT value can be either positive or negative. The system
reports either Ca++ or Cl–, but not both.
2-Point Total (Calibration and Slope) – LIS 3
Except for the Calibration Type parameter, all of the parameters in the
following table appear between the end of the calibration data and the
barometric pressure.
These records are identical to the 1-Point record, with the following
exceptions and additions:

Calibration type rTYPE 2-POINT
Slope pH (MEASURED) aSmpH n.nnn
aSmH+ nnn.n nmol/L
Slope pH (ADJUSTED) aSapH n.nnn
aSaH+ nnn.n nmol/L

Message Formats

Slope pH (DRIFT) aSdpH n.nnn
aSdH+ nnn.n nmol/L
Slope pO2 aSmPO2 nnn.n mmHg
Slope pO2 aSaPO2 nnn.n mmHg
Slope pO2 (DRIFT) aSdPO2 nnn.n mmHg
nn.nn kPa
Slope pCO2 aSmPCO2 nnn.n mmHg
Slope pCO2 aSaPCO2 nnn.n mmHg
Slope pCO2 (DRIFT) aSdPCO2 nnn.n mmHg
nn.nn kPa
+ mmol/L
Slope Na aSmNa+ nnn
(MEASURED)
Slope Na+ (ADJUSTED) aSaNa+ nnn mmol/L
+
Slope Na (DRIFT) aSdNa+ nnn mmol/L
Slope K+ (MEASURED) aSmK+ n.nn mmol/L
+
Slope K (ADJUSTED) aSaK+ n.nn mmol/L
+
Slope K (DRIFT) aSdK+ n.nn mmol/L
Slope Ca++ aSmCa++ n.nn mmol/L
(MEASURED)
Slope Ca++ aSaCa++ n.nn mmol/L
(ADJUSTED)
Slope Ca++ (DRIFT) aSdCa++ n.nn mmol/L
Slope Cl– (MEASURED) aSmCl– nnn mmol/L
–
Slope Cl (ADJUSTED) aSaCl– nnn mmol/L
Slope Cl– (DRIFT) aSdCl– nnn mmol/L
Note The DRIFT value can be either positive or negative. The system
reports either Ca++ or Cl–, but not both.

Message Formats
Hematocrit Slope – LIS 3

Sample type rTYPE HCT
Date rDATE ddMmmyy
Time rTIME hh:mm
Hematocrit (MEASURED) aSmHct nn.n %
Hematocrit (ADJUSTED) aSaHct nn.n %
Hematocrit (DRIFT) aSdHct nn.n %
Gas and pH/Electrolyte Calibrations

Gas and pH/electrolyte calibrations are the same as their respective total
calibrations except as shown in the following table.
Calibration Type Same as Total Exception

Calibration Type (Does not include)
1-Point Gas 1-Point pH/electrolyte results
2-Point Gas 2-Point pH/electrolytes results
1-Point pH/electrolyte 1-Point gas results
2-Point pH/electrolytes 2-Point gas results
Exceptions
The following table shows the exceptions for the QC Data Assay Record in
priority order, highest first:
Exception Mnemonic
Slope out of range SLPO
Offset out of range OFFO
Excessive drift DRIFT
Note If the result for a channel is overrange (slope or offset) or no

endpoint, the result has null value.

Message Formats
Sample Assay Order Data Record

Patient ID iPID nnnnnnnnnnnnnnnn
Patient iTEMP nn.n C
Temperature
Patient itHb nn.n g/dL (see Note)
Hemoglobin nnn g/L (see Note)
nn.n mmol/L
(see Note)
Patient FIO2 iFIO2 nnn.n %
Note If the units for tHb that are sent with the assay order do not match
the RAPIDLab 348EX system selection, the system converts them to the
selected units.
Examples of Data Records

The following example records reflect the LIS 3 mode:
• Sample Data Record, page 5-45
• Example of an Error, page 5-46
• QC Data Record, page 5-47
• Calibration Data Record, page 5-49

Message Formats
Sample Data Record

Record Comment/Field Description
<STX> Start of record
SMP_NEW_DAT<FS><RS> New sample data record
aMOD<GS>348<GS><GS><GS><FS> Model number (348)
iIID<GS>A123<GS><GS><GS><FS> Serial number
rTYPE<GS>SAMPLE<GS><GS><GS><FS> Measurement Type
(SAMPLE)
rSEQ <GS>00006<GS><GS><GS><FS> Sample number (00006)
rDATE<GS>30Nov11<GS><GS><GS><FS> Date (30 November 2011)
rTIME<GS>11:06<GS><GS><GS><FS> Time 11:06
(A.M., 24-hour clock)
rDEVICE<GS>SYRINGE<GS><GS><GS><FS> Sample device
iPID<GS>01-23-456-7-8900<GS><GS> Patient ID (up to 16 digits)
<GS><FS>
iOID<GS>987-65-4-3210987<GS><GS> Operator ID (up to 16 digits)
<GS><FS>
mpH<GS>7.329<GS><GS><GS><FS> pH (measured)
mPO2<GS>107.2<GS>mmHg<GS><GS> pO2 (measured)
<FS>
mPCO2<GS>25.3<GS>mmHg<GS><GS> pCO2 (measured)
<FS>
mNa+<GS>141<GS>mmol/L<GS><GS> Na+ (measured)
<FS>
mKa+<GS>4.05<GS>mmol/L<GS><GS> K+ (measured)
<FS>
mCa++<GS>1.25<GS>mmol/L<GS><GS> Ca++ (measured)
<FS> (Could be Cl– instead)
mHct<GS>43.5<GS>%<GS><GS><FS> Hematocrit (measured)
cHCO3act<GS>7.1<GS>mmol/L<GS><GS> Actual bicarbonate
<FS> (calculated)
ctCO2<GS>7.5<GS>mmol/L<GS><GS> Total Carbon Dioxide
<FS> (calculated)
cBE(vt)<GS>15.3<GS>mmol/L<GS><GS> Base excess (in vitro)
<FS> (calculated)
cO2SAT<GS>98.7<GS>%<GS><GS><FS> Oxygen saturation
(calculated)

Message Formats

cCa++<GS>1.28<GS>mmol/l<GS><GS> Ca++ (corrected for pH 7.4)
<FS>
mBP<GS>766<GS>mmHG<GS><GS><FS> Barometric Pressure
(measured)
<RS> End of Data Record
<ETX> End of Text
(Checksum) Checksum
<EOT> End of Transmission
Example of an Error
If the oxygen channel, for example, had no endpoint, the measured
oxygen field would be as follows:
mPO2<GS>107.2<GS>mmHg<GS>NEP<ETB<GS><FS>

Message Formats
QC Data Record
QC_NEW_DATA<FS><RS> QC data record
rTYPE<GS>QC<GS><GS><GS><FS> Record Type (QC)
rDATE<GS>30Nov11<GS><GS><GS><FS> Date (30 November 2011)
iQFILE<GS>1<GS><GS><GS><FS> File number
iQLEV<GS>1<GS><GS><GS><FS> QC Level (Level 1)
iQLOT<GS>331408<GS><GS><GS><FS> Lot number (331408)
mpH<GS>7.150<GS><GS><GS><FS> pH
sLQmpH<GS>7.126<GS><GS><GS><FS> Lower limit for Level 1 QC
(pH)
sHQmpH<GS>7.166<GS><GS><GS><FS> Upper limit for Level 1 QC
(pH)
mPO2<GS>65.0<GS>mmHg<GS><GS> pO2 (measured)
<FS>
sLQmPO2<GS>64.2<GS>mmHg<GS><GS> Lower limit for Level 1 QC
<FS> (pO2)
sHQmPO2<GS>74.2<GS>mmHg<GS><GS> Upper limit for Level 1 QC
<FS> (pO2)
mPCO2<GS>71.0<GS>mmHg<GS><GS> pCO2 (measured)
<FS>
sLQmPCO2<GS>65.2<GS>mmHg<GS> Lower limit for Level 1 QC
<GS><FS> (pCO2)
sHQmPCO2<GS>75.2<GS>mmHg<GS> Upper limit for Level 1 QC
<GS><FS> (pCO2)
mNa+<GS>117<GS>mmol/L<GS><GS> Na+ (measured)
<FS>
sLQmNa+<GS>112<GS>mmol/L<GS> Lower limit for Level 1 QC
<GS><FS> (Na+)
sHQmNa+<GS>122<GS>mmol/L<GS> Upper limit for Level 1 QC
<GS><FS> (Na+)

Message Formats

mK+<GS>2.89<GS>mmol/L<GS><GS> K+ (measured)
<FS>
sLQmK+<GS>2.39<GS>mmol/L<GS> Lower limit for Level 1 QC
<GS><FS> (K+)
sHQmK+<GS>3.39<GS>mmol/L<GS> Upper limit for Level 1 QC
<GS><FS> (K+)
mCa++<GS>1.64<GS>mmol/L<GS><GS> Ca++ (measured)
<FS>
sLQmCa++<GS>1.54<GS>mmol/L<GS> Lower limit for Level 1 QC
<GS><FS> (Ca++)
sHQmCa++<GS>1.74<GS>mmol/L<GS> Upper limit for Level 1 QC
<GS><FS> (Ca++)
(measured)
<ETX> End of Text
(Checksum) Checksum
Note The QC data record for Hct would be a separate record.

Message Formats
Calibration Data Record

CAL_NEW_DATA<FS><RS> Calibration data record
rTYPE<GS>2-POINT<GS><GS><GS><FS> Record Type (2-Point
calibration)
rDATE<GS>01Dec11<GS><GS><GS><FS> Date (01 December 2011)
aCmpH<GS>7.380<GS><GS><GS><FS> pH calibration value
(MEASURED)
aCapH<GS>7.382<GS><GS><GS><FS> Target pH calibration value
(ADJUSTED)
aCdpH<GS>–0.002<GS><GS><GS><FS> pH calibration drift
(MEASURED–ADJUSTED)
aCmPO2<GS>85.0<GS>mmHg<GS><GS> pO2 calibration value
<FS> (MEASURED)
aCaPO2<GS>86.0<GS>mmHg<GS><GS> Target pO2 calibration value
<FS> (ADJUSTED)
aCdPO2<GS>–1.00<GS>mmHg<GS><GS> pO2 calibration drift
<FS> (MEASURED–ADJUSTED)
aCmPCO2<GS>36.5<GS>mmHg<GS><GS> pCO2 calibration value
<FS> (MEASURED)
aCaPCO2<GS>36.0<GS>mmHg<GS> Target pCO2 calibration value
<GS><FS> (ADJUSTED)
aCdPCO2<GS>0.5<GS>mmHg<GS> pCO2 calibration drift
<GS><FS> (MEASURED–ADJUSTED)
aCmNa+<GS>141<GS>mmol/L<GS><GS> Na+ calibration value
<FS> (MEASURED)
aCaNa+<GS>140<GS>mmol/L<GS><GS> Target Na+ calibration value
<FS> (ADJUSTED)
aCdNa+<GS>1<GS>mmol/L<GS> Na+ calibration drift
aCmK+<GS>4.02<GS>mmol/L<GS><GS> K+ calibration value
<FS> (MEASURED)

Message Formats

aCaK+<GS>4.00<GS>mmol/L<GS> Target K+ calibration value
<GS><FS> (ADJUSTED)
aCdK+<GS>0.02<GS>mmol/L<GS> K+ calibration drift
aCmCa++<GS>1.23<GS>mmol/L<GS><GS> Ca++ calibration value
<FS> (MEASURED)
aCaCa++<GS>1.25<GS>mmol/L<GS> Target Ca++ calibration value
<GS><FS> (ADJUSTED)
aCdCa++<GS>–0.02<GS>mmol/L<GS> Ca++ calibration drift
aSmpH<GS>6.844<GS><GS><GS><FS> pH slope value (MEASURED)
aSapH<GS>6.838<GS><GS><GS><FS> Target pH slope value
(ADJUSTED)
aSdpH<GS>0.006<GS><GS><GS><FS> pH slope drift
(MEASURED–ADJUSTED)
aSmPO2<GS>0.1<GS>mmHg<GS><GS> pO2 slope value (MEASURED)
<FS>
aSaPO2<GS>0.0<GS>mmHg<GS><GS> Target pO2 slope value
<FS> (ADJUSTED)
aSdPO2<GS>-0.1<GS>mmHg<GS><GS> pO2 slope drift
<FS> (MEASURED–ADJUSTED)
aSmPCO2<GS>72.5<GS>mmHg<GS><GS> pCO2 slope value
<FS> (MEASURED)
aSaPCO2<GS>71.8<GS>mmHg<GS> Target pCO2 slope value
<GS><FS> (ADJUSTED)
aSdPCO2<GS>0.7<GS>mmHg<GS> pCO2 slope drift
aSmNa+<GS>109<GS>mmol/L<GS><GS> Na+ slope value (MEASURED)
<FS>
aSaNa+<GS>110<GS>mmol/L<GS><GS> Target Na+ slope value
<FS> (ADJUSTED)
aSdNa+<GS>–1<GS>mmol/L<GS> Na+ slope drift (MEASURED–
<GS><FS> ADJUSTED)
aSmK+<GS>8.02<GS>mmol/L<GS><GS> K+ slope value (MEASURED)
<FS>
aSaK+<GS>8.00<GS>mmol/L<GS> Target K+ slope value
<GS><FS> (ADJUSTED)

Message Formats

aSdK+<GS>0.02<GS>mmol/L<GS> K+ calibration drift
asmCa++<GS>2.47<GS>mmol/L<GS><GS> Ca++ slope value
<FS> (MEASURED)
aSaCa++<GS>2.50<GS>mmol/L<GS> Target Ca++ slope value
<GS><FS> (ADJUSTED)
aSdCa++<GS>–0.03<GS>mmol/L<GS> Ca++ slope drift (MEASURED–
<GS><FS> ADJUSTED)
(measured)
<ETX> End of Text
(Checksum) Checksum
Device Identity Data Record

ID_DATA<FS><RS> ID data record
<ETX> End of Text
(Checksum) Checksum

Message Formats

Index
Symbols data retransmission, requesting (LIS 3) 14
data-available message 14
LIS 3 protocol 14
delete QC data 20
A device identifier message 22
acknowledge message, LIS 3 14 device identity transactions 22
C drift, calculation 22
duplicate messages 14
calibration
remote request 23 E
transactions 20 edited sample data message 18
calibration canceled message 20 external printer
calibration data available message 20 interface 13
calibration data not available message 21 external printers 7
calibration data original message 21
F
calibration data, request 20
calibration initiated message 20 Flow Control 25
calibration pending message 21 flow control 13
checksum 13 format
communication data 11
protocols 9, 10 H
communication options 7
HIS 11
communication protocol 7
HIS (hospital information system) 7
conventions 11
hospital information system (HIS) 7
D L
data available message 18
laboratory information system (LIS) 7
data communication
LIS 11
protocol 9, 10
LIS (laboratory information system) 7
data format 11
LIS 1
data management system
description 9, 10
interface with a RAPIDLab 348EX system 11
LIS 1 protocol 13
data manager 7
overview 7
data messages
LIS 2 protocol 13
LIS 2 14
overview 7
data ports
LIS 3 protocol
configuring 11
calibration and slope data 21
RAPIDLab 348EX Interface Specification Guide page Index-1

overview 8 request sample data message 18
LIS2 protocol retransmission of data, requesting (LIS 3) 14
data messages 14 RS232 ports 7
M S
measurement status 17 sample analysis lock-out remote request 23
message sample assay data message 18
parsing 15 sample assay message 18
P sample assay order, canceling 22
sample assay order, patient 22
parsing messages 15
sample data not available message 18
patient sample assay order 22
sample data original message 18
patient sample assay order, canceling 22
sequence numbers 17
patient sample transactions 17
patient, QC and calibration transactions 17 T
printer, extermal 7 transactions
protocol device identity 22
communication 7 patient, QC and calibration 17
data communication 9, 10 QC sample assay 19
remote control requests 23
Q
W
QC assay 19
QC assay data message 19 wash request, remote 23
QC assay transactions 19 X
QC data available message 19 XON/XOFF flow control 13
QC data not available message 19
QC data original message 19
QC data, request 19
QC delete data message 20
QC sample measurement status 19
R
RAPIDComm Data Management System 7,
11
RAPIDLink Data Management System 7, 11
remote control requests 23
request calibration data message 20
request device identity message 22
request QC data 19
page Index-2 RAPIDLab 348EX Interface Specification Guide

Siemens Rapidlab 348EX Host Interface

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Siemens Rapidlab 348EX Host Interface

Uploaded by

Copyright:

Available Formats

RAPIDLab 348EX

Interface Specifications Manual

10698303 Rev. A, 2012-03

2 Setting up the Hardware Connection

3 Interfacing to a Data Management System

4 Patient, QC, and Calibration Transactions

RAPIDLab 348EX Interface Specification Guide page 3

page 4 RAPIDLab 348EX Interface Specification Guide

RAPIDLab 348EX Interface Specification Guide page 5

The RAPIDLab® 348EX system transmits patient sample data, quality

About the Communication Protocols

RAPIDLab 348EX Interface Specification Guide page 7

page 8 RAPIDLab 348EX Interface Specification Guide

Figure 1: Left: Port 1 (Female), Right: Port 2 (Male)

Data Port 1 (Female) Data Port 2 (Male)

Connecting the Hardware

RAPIDLab 348EX Interface Specification Guide page 9

Protocol Support for RS232 Ports

page 10 RAPIDLab 348EX Interface Specification Guide

The system communicates with a RAPIDLink Data Management System, a

Note These characters are not transmitted as part of any message.

Configuring Data Ports

RAPIDLab 348EX Interface Specification Guide page 11

Parameter Possible Values Default Value

These same options apply to all 3 protocols.

page 12 RAPIDLab 348EX Interface Specification Guide

5. Select the protocol for the designated output port as follows:

For Communication With Port Protocol

A data management system, such as a 1 LIS 3

A data management system requiring 1 LIS 2

• The LIS 2 protocol transmits data messages following the completion

RAPIDLab 348EX Interface Specification Guide page 13

Data Messages Supported by LIS 2

Sample Data {SMP_NEW_DATA}{Sample assay data}

page 14 RAPIDLab 348EX Interface Specification Guide

Note Transmission of duplicate data messages can also occur in an error­

RAPIDLab 348EX Interface Specification Guide page 15

page 16 RAPIDLab 348EX Interface Specification Guide

Patient and QC measurements have separate sequence numbers. The

Patient Sample Transactions

RAPIDLab 348EX Interface Specification Guide page 17

Request Sample Data

Sample Assay Data

{SMP_EDIT_DATA}{Sample assay data)

page 18 RAPIDLab 348EX Interface Specification Guide

RAPIDLab 348EX Interface Specification Guide page 19

Request Calibration Data

page 20 RAPIDLab 348EX Interface Specification Guide

Calibration (Cal) Slope

RAPIDLab 348EX Interface Specification Guide page 21

Device Identity Transactions

Sample Assay Order

page 22 RAPIDLab 348EX Interface Specification Guide

where iPID is the patient ID sent with the order.

Remote Control Transactions

1-Point or 2-Point Calibration Request

Sample Analysis Lock-Out Request

RAPIDLab 348EX Interface Specification Guide page 23

LIS 3 Communication Protocol Formats

This provides a transmission format identical to that used for message

page 24 RAPIDLab 348EX Interface Specification Guide

• When a good message (no parity/framing errors or checksum error) is

Baud Rate Timer (seconds)

Control Character Description

Note Transmission of duplicate data messages can also occur in an error