Vip Mumbai Call Girls Andheri East Call On 9920725232 With Body to body massa...
Cobas u411
1. Roche Diagnostics AG
r
cobas u 411
Host Interface Manual
Version 2.1
cobas u 411 Host Interface Manual V 2.1 1 / 52
2. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 2 / 52
DISCLAIMER
ROCHE DIAGNOSTICS MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT
TO THE CONTENTS OF THIS DOCUMENT AND SPECIFICALLY DISCLAIMS ANY IMPLIED
WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. IN NO CASE SHALL ROCHE DIAGNOSTICS BE
LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES.
COPYRIGHT
COPYRIGHT 2011, BY ROCHE DIAGNOSTICS. ALL RIGHTS RESERVED. NO PART OF THIS
PUBLICATION MAY BE REPRODUCED WITHOUT THE EXPRESS WRITTEN PERMISSION OF
ROCHE DIAGNOSTICS.
VERSION HISTORY
Version Date Software version Modifications
1.0 Mar-2007 3.0 -First Release
1.1 Oct-2008 3.0.4.0801 -Implementation of US ranges
-Interface chapter 3 revised
-Further Help chapter 1.4 revised General bug fixing
2.0 Apr-2010 3.1.0.0901 -Implementation of Reference ranges
-Message Header Record chapter revised
-General wording corrections
2.1 May-2011 3.2.0.1001 -General wording corrections
-Chapter Introduction and Purpose rewritten
-Chapter Supported Host Protocols moved
-Chapter Size of Sample ID moved
-Chapter Flags created
-Chapter Transmitted Date moved and rewritten
-Chapter Host Interface Configuration rewritten
-Chapter Error Handling rewritten
-Chapter Sediment Result Record removed
-Result Record no. 9 modified
-All examples updated
-Reference ranges removed
3. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 3 / 52
1 Purpose.......................................................................................................................................4
1.1 Document structure ..............................................................................................................4
1.2 Audience...............................................................................................................................4
1.3 Related documents...............................................................................................................4
1.4 Used syntax and abbreviations.............................................................................................4
1.5 Support .................................................................................................................................5
2 Introduction ................................................................................................................................6
2.1 Overview cobas u 411 analyzer............................................................................................6
2.2 Supported host protocols......................................................................................................6
2.3 Sample ID length ..................................................................................................................6
2.4 Flags.....................................................................................................................................6
2.5 Upload (cobas u 411 to host system) ...................................................................................8
2.6 Arbitrary units........................................................................................................................9
2.7 Download data (host system to cobas u 411).....................................................................10
3 Host interface configuration ...................................................................................................10
3.1 Communication settings .....................................................................................................10
3.2 Host interface behaviour.....................................................................................................10
3.3 Serial cable.........................................................................................................................11
4 Error handling (behaviour of a failed transmission).............................................................11
5 Description of the supported protocols.................................................................................12
5.1 ASTM plus protocol ............................................................................................................12
5.1.1 General .......................................................................................................................12
5.1.2 Communication startup ...............................................................................................13
5.1.3 Record description ......................................................................................................14
5.1.4 ASTM plus trace file examples....................................................................................20
5.2 ASTM Urisys 2400 protocol................................................................................................35
5.2.1 General .......................................................................................................................35
5.2.2 Communication structure ............................................................................................37
5.2.3 Record descriptions ....................................................................................................38
5.2.4 ASTM Urisys 2400 trace file examples .......................................................................44
6 Appendices...............................................................................................................................49
6.1 Appendix 1: ASCII-table .....................................................................................................49
6.2 Appendix 2: Definition of test codes and test numbers (for ASTM plus protocol
only)..........................................................................................................................................50
6.3 Appendix 3: Printouts of control and sample results...........................................................51
4. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 4 / 52
1 Purpose
The purpose of this document is to describe the host interface specifications of the cobas u 411
analyzer. These specifications define the hardware and software settings and the data interchange
via null modem cable (RS-232) between the cobas u 411 and the host system.
1.1 Document structure
This document is structured in a general part for all supported host protocols (chapter 2 to 4) and a
protocol specific part (chapter 5).
The general part contains information about host interface configuration, cable wiring, brief
overview about the different supported host protocols, description of flags and error handling.
The protocol specific part contains a sub-chapter for each supported host protocol, in which the
communication structure and the records are described. There is a detailed example for a
better comprehension, at the end of each record description. The whole trace files of different
data interchanges are added at the end of the corresponding protocol description.
There are additional information in the chapter appendices, such as ASCII-Table, Definition of Test
Codes and Test Numbers for ASTM plus and the printouts of the different Control and Sample
Results used in the examples.
1.2 Audience
This document is written for engineers who must configure the cobas u 411 host interface in the
environment of a laboratory. Depending on the type of host system and on the work flow in the
laboratory the cobas u 411 host interface offers a set of configurable features.
1.3 Related documents
Related documents:
[1] Roche Diagnostics ASTM plus interface specification version 2.0
[2] E 1394-91 standard specification for transferring information between clinical
instruments and computer systems, American Society for Testing and Materials
(ASTM)
1.4 Used syntax and abbreviations
Used Syntax
<SpecimenID> Meaning any string (not containing delimiters), representing a
value of the ASTM field “SpecimenID”.
char Single character. Content specified by standard.
text String. Variable length.
pos_int Positive integer (0 to 65535)
d_t Date and time format as specified by ASTM
(YYYYMMDDHHMMSS)
date Date format as specified by ASTM (YYYYMMDD)
5. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 5 / 52
Terms
ASTM American Society for Testing and Materials
LIS Laboratory Information System (host system)
1.5 Support
In case of questions please contact your local Roche Diagnostics Service Department, or
alternatively the Global Customer Support:
E-Mail address: rotkreuz.gsscdiric@roche.com
Clarify queue: GSSCDIRIC
6. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 6 / 52
2 Introduction
The purpose of this document is to describe the host interface specifications of the cobas u 411
analyzer. These specifications define the hardware and software settings and the data interchange
via null modem cable (RS-232) between the cobas u 411 and the host system.
2.1 Overview cobas u 411 analyzer
The cobas u 411 analyzer is a semiautomatic urinalysis system intended for in vitro qualitative or
semi-quantitative determination of urine analytes, including specific gravity (SG), pH, leukocytes,
nitrite, protein, glucose, ketones, urobilinogen, bilirubin, erythrocytes and color.
2.2 Supported host protocols
The cobas u 411 analyzer supports the following host protocols:
• ASTM plus
• ASTM Urisys 2400
2.3 Sample ID length
The cobas u 411 analyzer supports a sample ID with a maximum length of 13 characters.
2.4 Flags
The result data which is transmitted to the host system (or printed) must be checked for flags.
There can be different flags, which are sent in a Comment Record additionally to the Result
Record or in the Result Record itself, using the ASTM plus or ASTM Urisys 2400 protocols. On the
printout, the flags are next to the data. The meaning of the flags is listed below.
Attention: Flags are in order to bring some of the values to attention of the operator. Therefore
it is important that these flags are displayed on the host system. If these flags are
not displayed, this could mislead the operator to wrong conclusions and medical
decisions!
Result flags
Flag Result flags Explanation
S Sieve Test parameter result corresponds to sieve criteria settings
* Abnormal For patient sample test parameter result corresponds to
abnormal criteria settings
# Changed reflectance
value
Initial range table is changed
! Edited result Data has been edited
7. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 7 / 52
Sample flags
Flag Sample flags Explanation
T Test strip Error during measurement of test strip or reference strip.
Possible reasons:
Strip upside down
Strip incompletely wet
Strip completely dry
Strip missing or wrong positioning
Calculation not possible
C Calibration exceeded Calibration interval of four weeks is exceeded
Control flags
Flag Control flags Explanation
S Sieve Test parameter result corresponds to sieve criteria settings
* Abnormal For control sample it means out of range
T Test strip Error during measurement of test strip or a reference strip.
Possible reasons:
Strip upside down
Strip incompletely wet
Strip completely dry
Strip missing or wrong positioning
Calculation not possible
C Calibration exceeded Calibration interval of four weeks is exceeded
Additional flags for ASTM Urisys 2400 protocol only
Flag Sample flags Explanation
R Test strip error Error during measurement of test strip or reference strip.
Possible reasons:
Strip upside down
Strip incompletely wet
Strip completely dry
Strip missing or wrong positioning
Calculation not possible
X Order cannot be done Usually in combination with the “R” flag
8. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 8 / 52
Transmitted Data
The cobas u 411 analyzer always initiates the communication to the host system. Hence, the
cobas u 411 analyzer is the master and the host system the slave.
2.5 Upload (cobas u 411 to host system)
Depending on the selected host protocol, different data is sent to the host system. The tables
below give an overview about the different protocols and their transmitted data.
Data
Protocol
ASTMplus
ASTMUrisys2400
Data
Protocol
ASTMplus
ASTMUrisys2400
Sample ID / Sequence number Name and lot ID
Date and time of calculation Control results for three levels
Strip results Date and time of calculation
Units Units
Flags Flags
Color and clarity of sample Color
Sediment results - compensated raw data (optional)
compensated raw data (optional) Instrument ID / serial no.
Instrument ID / serial no. User ID
User ID Software version
Software version Range table (boundary setting) -
Range table (boundary setting) - Test strip lot number -
Test strip lot number - Test strip expiry date -
Test strip expiry date - Calibration strip lot number -
Calibration strip lot number - Calibration strip expiry date -
StripResult
Calibration strip expiry date - Control lot number
Control name
ControlResult
Control expiry date -
Legend: Supported - not supported
Note: There are two different names for the same type of protocol, depending on which
analyzer is in use:
• Using the Urisys 1800 analyzer, the protocol is called "Urisys 2400"
• Using the cobas u 411 analyzer, the protocol is called "ASTM Urisys 2400".
Within this document the name ASTM Urisys 2400 for cobas u 411 is used.
9. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 9 / 52
ASTM plus protocol
Strip Results
• Sample ID / Sequence number
• Date and time of calculation
• Strip results
• Units
• Flags
• Color and clarity of sample
• Sediment results
• Compensated raw data (optional)
• Instrument ID
• User ID
• Software version
• Range tables (boundary setting)
• Test strip lot number
• Test strip expiry date
• Calibration strip lot number
• Calibration strip expiry date
Control Results
• Name and lot ID
• Control results for three levels
• Date and time of control calculation
• Units
• Flags
• Color
• Compensated raw data (optional)
• Instrument ID
• User ID
• Software version
• Range tables (boundary setting)
• Test strip lot number
• Test strip expiry date
• Calibration strip lot number
• Calibration strip expiry date
• Control lot number
• Control name
• Control expiry date
ASTM Urisys 2400
Strip Results
• Sample ID / Sequence number
• Date and time of calculation
• Strip results
• Units
• Flags
• Color and clarity of sample
• Compensated raw data (optional)
• Instrument ID
• User ID
• Software version
Control Results
• Name and lot ID
• Control results for three levels
• Date and time of control calculation
• Units
• Flags
• Color
• Compensated raw data (optional)
• Instrument ID
• User ID
• Software version
• Control lot number
• Control name
2.6 Arbitrary units
ASTM plus
Arbitrary units are sent to the host system in combination with other units (Conventional or SI).
With the control results, the preset arbitrary values (default) are transmitted.
ASTM Urisys 2400
Arbitrary units are sent to the host system only when they are selected separately and not in
combination with other units (Conventional or SI).
With the control results, the preset arbitrary values (default) are transmitted.
10. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 10 / 52
2.7 Download data (host system to cobas u 411)
The data download from the host system to the analyzer is performed on the cobas u 411 by
clicking the <Download> button. The following data can be transmitted from the host system to the
cobas u 411: Worklist (list of sample ID’s)
Note: The Urisys 2400 protocol does not support this mode.
3 Host interface configuration
The communication between the cobas u 411 analyzer and the host system is established using a
serial asynchronous interface cable. The communication settings must be equal on both sides
(cobas u 411 and host system), see chapter 3.1 below.
3.1 Communication settings
The host settings on the cobas u 411 analyzer are set to OFF by default. To establish the host
communication, the host settings must be set to ON. Changes in the cobas u 411 analyzer
communication parameters are only possible if the host settings are set to OFF. To configure the
host settings and to enable the host communication, go to the configuration menu: Utilities >
System Parameters > Host Comm.
The following host communication settings are configurable in the cobas u 411 analyzer user
interface.
Configuration Specification Default
Baud rate 1200, 2400, 4800, 9600, 19200, 38400, 57600 9600
Data bits 7, 8 8
Stop bits 1, 2 1
Flow control None, Xon-Xoff, RTS-CTS None
Parity None, odd, even None
3.2 Host interface behaviour
The host interface behaviour can be influenced by the following configuration setup (user
interface):
Item Specification Default
Host ON, OFF OFF
Protocol ASTM plus, ASTM Urisys 2400 ASTM plus
Raw data to host OFF, ON, upload only (setup in service) OFF
Checksum On, Off On
The automatic result transmission is active when the host support is switched to ON.
11. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 11 / 52
3.3 Serial cable
The cobas u 411 uses a serial asynchronous interface cable (RS 232) connected to the host
computer. The port COM 2 of the host system is usually allocated to this communication, but can
vary depending on the host system.
According to the serial asynchronous specification, the maximum cable length is 15 m. It is
recommended by Roche to use a 3 meter cable. All other cable length apart from the
recommended must be organized locally.
The following cable is assigned to use for connecting the cobas u 411 to the host system:
• Host Interface Cable RS 232, IBM PC Null modem D-Sub 9 pins, 3m
Please see table below for wiring details:
cobas u 411
Plug 9 pin female
Relevance
Host System
Plug 9 pin female
1 – - Legend:
2 RXD 3 RxD = Receiving data
3 TXD 2 TxD = Transmitting data
4 DTR 6 DTR = Data terminal ready
5 GND 5 GND =Ground
6 DSR 4 DSR = Data set ready
7 RTS 8 RTS = Request to send
8 CTS 7 CTS = Clear to send
9 – -
Note: If flow control is set to “None” or “Xon-Xoff” then the pin 4/6 and pin 7/8 (handshake
connections) are not required.
4 Error handling (behaviour of a failed transmission)
There are two different types of error handling:
• Host system does not acknowledge the transmission:
An alarm message (red alarm LED is activated) will occur if the transmission of data is not
confirmed by the host system. The failed transmission will not be repeated.
• Host receives wrong data:
In case the host system has received wrong data (e.g. wrong checksum), the incorrect
sequence will be repeated. After three failed attempts, the transmission will be aborted and
an alarm message will be displayed (red alarm LED is activated).
12. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 12 / 52
5 Description of the supported protocols
5.1 ASTM plus protocol
5.1.1 General
This chapter describes the ASTM plus protocol. The ASTM plus protocol consists of Records,
Frames and Messages.
• A record is the smallest logical group of information
• A frame is a defined data structure that contains a data block to be transmitted
• Messages are a collection of several records packed in frames into a logical unit
Note: The ASTM plus protocol is based on the ASTM protocol specification.
Records
A record is the smallest logical group of information. The ASTM plus protocol supports the
following records:
Identification Name Description
H Header record First record in every message, mandatory
P Patient information
record
This record is used to download patient demographics
from the host system to the analyzer. With the cobas u
411 no patient data can be handled. Therefore the
patient record is always empty.
O Order record This record defines the attributes of a particular order
R Result record Measurement data
C Comment record This record is used for the transmission of sample flags
and result flags.
M Manufacturer record This record is used for the transmission of raw data,
additional information for patient and control results
Q Request information
record (query)
Worklist request (query)
L Termination record Last record in every message, mandatory
Frames
A frame is a defined data structure that encapsulates a data block to be transmitted. According to
the ASTM plus protocol specification, a frame may contain one or more records. However, the
implementation in the cobas u 411 analyzer contains one record only. Each frame has the
following structure:
Description Start of
text
Frame
No.
End of
text
Check-
sum
Carriage
return
Line feed
ASCII
(hex)
STX
(0x02)
Protocol
specific
record
data
ETX
(0x03)
CR
(0x0D)
LF
(0x0A)
The frame no. always starts at 1 and will be incremented by one for each record. If the frame
reaches no. 7, the numbering starts at 0 (zero).
13. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 13 / 52
Messages
Messages are collections of several records packed in frames into a logical unit. A message starts
with the Header Record (H) and finishes with the Termination Record (L).
5.1.2 Communication startup
Only the cobas u 411 analyzer can start a communication. The cobas u 411 analyzer is always
the master, the host system the slave.
Exception: After the successful handling of the worklist request sequence, the master function
temporarily belongs to the host system for the duration of the worklist transmission.
A communication is initialized when the ASCII character ENQ
(Hex 05) is sent to the host system.
The host system (slave) acknowledges its readiness to
communicate by sending the ASCII character ACK (Hex 06) or
if it is not ready the ASCII character NAK (Hex 15).
If the host system has positively acknowledged its readiness to
communicate (ACK), the cobas u 411 analyzer transmits the
message frame by frame.
The host system confirms the frame reception with ACK.
The host system can trigger a resending of the last sent frame
with NAK.
The communication session is terminated with the ASCII
character EOT (Hex 04).
cobasu411
14. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 14 / 52
5.1.3 Record description
In this chapter, the meaning of the fields in individual records will be explained in the form of tables.
Fields which are not supported by the cobas u 411 analyzer are highlighted in grey. For a better
comprehension, there is a detailed example for each record description following the table.
Example trace files of different data interchanges are added at the end of this protocol description.
Message header record
Every message starts with a Message Header Record. This record is mandatory.
No. Field Content Comment
1 Record type ID H The character H identifies the record as a
message header record.
Field delimiter |
Repeat delimiter
Component delimiter ^
2
Escape delimiter &
Defines the delimiters to be used throughout
the subsequent records of the message.
3 Message control ID Not used in cobas u 411 analyzer
4 Access password Not used in cobas u 411 analyzer
5 Sender name or ID cobas u 411
^serial no.
^software version
^range boundary
setting
First sub field contains “cobas u 411”, second
sub field contains serial number (10 digits,
e.g. 0000000001), third sub field contains the
software version, and the fourth sub field
contains the range boundary setting
6 Sender street address
7 Reserved field
8 Sender telephone
number
9 Characteristics of
sender
10 Receiver ID
11 Comment of special
instructions
Not used in cobas u 411 analyzer
12 Processing ID P Always P (production)
13 Version no. Not used in cobas u 411 analyzer
14 Date and time of
message
Date and time (format YYYYMMDDhhmmss)
example 20110315101822)
Example:
No: Frame 1 2 3 4 5 6 7 8 9 10
Content: [STX] 1 H | ^& | | | cobas·u·411^8^3.2.0.1001^Int | | | | | |
No: 11 12 13 14 CR Frame
Content: | | P | | 20110315101822 [CR] [ETX]71[CR][LF]
15. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 15 / 52
Patient information record
Although the cobas u 411 analyzer does not save any patient data, the Patient Information
Record is mandatory by the ASTM plus standard. Therefore, the cobas u 411 analyzer simply
transmits an empty record.
No. Field Content Comment
1 Record type ID P The character P identifies the record as a
patient record.
2 Sequence no. 1 The cobas u 411 analyzer sends one order
per transmission only. Therefore this value is
always 1.
3 .. 35 All further fields are not supported and not transmitted
Example:
No: Frame 1 2 CR Frame
Content: [STX] 2 P | 1 [CR] [ETX]3F[CR][LF]
Order record
In the Order Record general sample information such as sample ID, sequence number, etc. will
be transmitted.
No. Field Content Comment
1 Record type ID O The character O identifies the record as an
order record.
2 Sequence no. 1 The cobas u 411 analyzer sends one order
per transmission only. Therefore this value is
always 1.
3 Specimen ID sample ID ID of the sample, numerical or
alphanumerical value (e.g. 001)
4 Instrument
specimen ID
sample no.
^rack ID
^position no.
^operator ID
^data carrier type
The cobas u 411 analyzer supports only
sample no. and data carrier type (“SAMPLE”
for patient samples, “CONTROL” for control
samples).For order download, the sample no.
is not needed and is ignored.
5 Universal test ID Not used in cobas u 411 analyzer
6 Priority R Always R (routine sample)
The cobas u 411 analyzer does not support
emergency samples
7 Request / ordered
date and time
8 Specimen
collection date and
time
9 Collection end time
10 Collection volume
11 Collector ID
Not used in cobas u 411 analyzer
12 Action code X or XQ Always X, in case of control samples XQ
13 Danger code
14 Relevant clinical
information
Not used in cobas u 411 analyzer
15 Date / time
specimen received
Date and time (format YYYYMMDDhhmmss)
example 20110315101822
16 .. 31 All further fields are not supported and not transmitted
16. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 16 / 52
Example patient sample:
No: Frame 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Content: [STX] 3 O | 1 | 001 | 1^^^^SAMPLE | | R | | | | | | X | | |
No: 15 CR Frame
Content: 20110315101754 [CR] [ETX]F0[CR][LF]
Example control sample:
No: Frame 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Content: [STX] 3 O | 1 | | 0^^^^CONTROL | | R | | | | | | XQ | | |
No: 15 CR Frame
Content: 20110315100924 [CR] [ETX]68[CR][LF]
Result record
The cobas u 411 analyzer uses the Result Record to transmit the measurement data. Each test
needs a separate Result Record. Flags are sent in the Comment Record and must be observed.
No. Field Content Comment
1 Record type ID R The character R identifies the record as a
result record.
2 Sequence no. 1 – 1000 The cobas u 411 stores up to 1000 results
(color, clarity and sediment parameters
included)
3 Universal test ID test no.
^test code
Test no. list (e.g. 1) see 6.2
Test code (e.g. “SG”) see 6.2
4 Data or
measurement value
result value
^arbitrary value
Result value: numerical value (e.g. 1.030) or
alphanumerical value (e.g. „neg.”)
Arbitrary value: additional, this subfield is
only used if arbitrary values are used in
combination with others (Conventional or SI);
arbitrary values for color and clarity don’t
exist
5 Unit unit Alphanumerical value (e.g. “mg/dl”), only if
result can be represented by several units
6 Reference ranges Not used in cobas u 411 analyzer, not
equivalent to range tables used in cobas u
411 analyzer
7 Result abnormal flag Not used in cobas u 411 analyzer,
abnormal flags are sent in the comment
record
8 Nature of
abnormality testing
9 Result status
10 Date of change in
instrument
normative values or
units
Not used in cobas u 411 analyzer
11 Operator ID user ID User ID of operator who performed the test
12 .. 14 All further fields are not supported and not transmitted
17. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 17 / 52
Example:
No: Frame 1 2 3 4 5 6 7 8 9 10 11 CR Frame
Content: [STX] 4 R | 1 | 1^SG | 1.005 | | | | | | | service [CR] [ETX]AD
No: Frame
Content: [CR][LF]
Comment record
The cobas u 411 analyzer uses the Comment Record to transmit the sample flags and result
flags. When at least one flag is present, this record will be attached to all corresponding Result
Records of the sample.
No. Field Content Comment
1 Record type ID C The character C identifies the record as a
comment record.
2 Sequence no. 1 – 1000 The cobas u 411 analyzer uses the same
sequence number as the prior result record.
3 Comment source I Always I (clinical instrument system)
4 Comment text Sample Flags /
Sample Result Flags
The cobas u 411 analyzer uses the
comment record only for transmitting flags,
each flag is separated with the ^ delimiter.
5 Comment type I Always I (instrument flag(s) comment)
Attention: Flags are in order to bring some of the values to attention of the operator. Therefore
it is important that these flags are displayed on the host system. If these flags are
not displayed, this could mislead the operator to wrong conclusions and medical
decisions!
Read the chapter “2.4 Flags” for detailed information!
Example (result record with additional comment record edited result: !-Flag):
Content: [STX]5R|2|2^pH|6|||||||service[CR][ETX]10[CR][LF] Result Record
No: Frame 1 2 3 4 5 CR Frame
Content: [STX] 6 C | 2 | I | ! | I [CR] [ETX]5E[CR][LF] Comment Record
Example (result record with additional comment record abnormal and sieve: *-Flag and S-Flag):
Content: [STX]5R|2|2^pH|8|||||||service[CR][ETX]12[CR][LF] Result Record
No: Frame 1 2 3 4 5 CR Frame
Content: [STX] 6 C | 2 | I | *^S | I [CR] [ETX]18[CR][LF] Comment Record
Example (result record with additional comment record test strip error: T-Flag):
Content: [STX]4R|1|1^SG||||||||service[CR][ETX]B9[CR][LF] Result Record
No: Frame 1 2 3 4 5 CR Frame
Content: [STX] 5 C | 1 | I | T | I [CR] [ETX]8F[CR][LF] Comment Record
18. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 18 / 52
Manufacturer record (raw result record - RR)
The cobas u 411 analyzer uses the Manufacturer Record RR to transmit raw data for special
application (e.g. evaluation / research). It is possible to activate this application via the user
interface (Utilities / Tools2 / Service “Raw Data to Host” ON)
No. Field Content Comment
1 Record type ID M The character M identifies the record as a
manufacturer record.
2 Sequence no. 1 – 1000 Running number
3 Record type sub-ID RR Always “RR” (raw result)
4 Universal test ID test no.^
test code
Test no. list (e.g. 1) see 6.2
Test code (e.g. “SG”) see 6.2
5 Test frequency frequency LED frequency (e.g. “green”)
blue (~470 nm)
green (~555 nm)
orange (~620 nm)
6 Raw result value reflectance Floating number in the format ##.## (e.g.
88.06)
Example:
No: Frame 1 2 3 4 5 6 CR Frame
Content: [STX] 0 M | 1 | RR | 11^COM | blue | 78.19 [CR] [ETX]1C[CR][LF]
Manufacturer record (result context record - RC)
The cobas u 411 analyzer uses the Result Context Record for the transmission of additional
information for patients or controls.
No. Field Content Comment
1 Record type ID M Needed by ASTM, always “M”
2 Sequence no. 1 Running number
3 Record type sub-ID RC Always RC (result context)
4 Calibration strip lot
number
e.g. 4567 Numerical or alphanumerical value
5 Calibration strip
expiration date
e.g. 20061231 Date and time format (YYYYMMDD)
6 Test strip lot number e.g. 1234 Numerical or alphanumerical value
7 Test strip expiration
date
e.g. 20061231 Date and time format (YYYYMMDD)
8 Control name e.g. ctrl Patient sample: always empty
Control sample: control name
9 Control lot number e.g. 7890 Patient sample: always empty
Control sample: control lot no
10 Control expiration date e.g. 20061231 Patient sample: always empty
Control sample: control expiration date
Date and time format (YYYYMMDD)
Example patient sample:
No: Frame 1 2 3 4 5 6 7 8 9 10 CR
Content: [STX] 0 M | 1 | RC | | | 2001601 | 20111001 | | | [CR]
No: Frame
Content: [ETX]8F[CR][LF]
19. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 19 / 52
Example control sample:
No: Frame 1 2 3 4 5 6 7 8 9
Content: [STX] 7 M | 1 | RC | | | 2001601 | 20111001 | ctrl | 123456 |
No: 10 CR Frame
Content: 20111001 [CR] [ETX]06[CR][LF]
Request information record (request for worklist download)
The cobas u 411 analyzer uses the Request Information Record to request the work list from the
host system. The host system must answer within 3 seconds.
No. Field Content Comment
1 Record type ID Q The character Q identifies the record as a
request information record.
2 Sequence no. 1 Always 1, using the cobas u 411 analyzer
3 Record type sub-ID ^ALL Request for all orders
4 .. 13 All further fields are not supported and not transmitted
Example:
No: Frame 1 2 3 CR Frame
Content: [STX] 2 Q | 1 | ^ALL [CR] [ETX]F3[CR][LF]
Termination record
Each message is closed with the Message Terminator Record. This record is mandatory.
No. Field Content Comment
1 Record type ID L Needed by ASTM, always “L”
2 Sequence no. 1 Always 1
3 Termination code N N for normal end of message
Example:
No: Frame 1 2 3 CR Frame
Content: [STX] 1 L | 1 | N [CR] [ETX]04[CR][LF]
Scientific record
This type of record is not used in cobas u 411 analyzer (the character S would identify the record
as a scientific record).
20. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 20 / 52
5.1.4 ASTM plus trace file examples
Example: Upload sample result without raw data
- Sample 1
- Sample 2 (with !-flag for pH)
- Sample 3 (with *- and S-Flag for pH and sediment data for ERY and LEU)
- Sample 4 (with T-flag)
Example: Upload sample result with raw data
- Sample 1
- Sample 2 (with !-flag for pH)
- Sample 3 (with *- and S-Flag for pH and sediment data for ERY and LEU)
- Sample 4 (with T-flag)
Example: Upload control result without raw data
Example: Upload control result with raw data
Example: Worklist download
Example: Upload sample result without raw data
Sample 1
u411 10:17:03,686 [ENQ]
Host 10:17:03,686 [ACK]
u411 10:17:03,795 [STX]1H|^&|||cobas·u·411^8^3.2.0.1001^Int|||||
||P||20110315101822[CR][ETX]71[CR][LF]
Host 10:17:03,811 [ACK]
u411 10:17:03,842 [STX]2P|1[CR][ETX]3F[CR][LF]
Host 10:17:03,858 [ACK]
u411 10:17:03,936 [STX]3O|1|001|1^^^^SAMPLE||R||||||X|||201103151
01754[CR][ETX]F0[CR][LF]
Host 10:17:03,951 [ACK]
u411 10:17:04,029 [STX]4R|1|1^SG|1.005|||||||service[CR][ETX]AD[C
R][LF]
Host 10:17:04,029 [ACK]
u411 10:17:04,108 [STX]5R|2|2^pH|7|||||||service[CR][ETX]11[CR][L
F]
Host 10:17:04,108 [ACK]
u411 10:17:04,186 [STX]6R|3|3^LEU|neg|||||||service[CR][ETX]45[CR
][LF]
Host 10:17:04,186 [ACK]
u411 10:17:04,264 [STX]7R|4|4^NIT|neg|||||||service[CR][ETX]4D[CR
][LF]
Host 10:17:04,264 [ACK]
u411 10:17:04,342 [STX]0R|5|5^PRO|neg|||||||service[CR][ETX]4E[CR
][LF]
Host 10:17:04,342 [ACK]
u411 10:17:04,420 [STX]1R|6|6^GLU|neg|||||||service[CR][ETX]48[CR
][LF]
Host 10:17:04,420 [ACK]
u411 10:17:04,498 [STX]2R|7|7^KET|neg|||||||service[CR][ETX]47[CR
][LF]
Host 10:17:04,498 [ACK]
u411 10:17:04,576 [STX]3R|8|8^UBG|neg|||||||service[CR][ETX]44[CR
][LF]
Host 10:17:04,592 [ACK]
u411 10:17:04,654 [STX]4R|9|9^BIL|neg|||||||service[CR][ETX]40[CR
][LF]
Host 10:17:04,670 [ACK]
u411 10:17:04,764 [STX]5R|10|10^ERY|neg|||||||service[CR][ETX]AA[
35. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 35 / 52
5.2 ASTM Urisys 2400 protocol
5.2.1 General
This chapter describes the ASTM URISYS 2400 protocol. This protocol consists of Records,
Frames and Messages.
• A Record is the smallest logical group of information
• A Frame is a defined data structure that contains a data block to be transmitted
• Messages are a collection of several records packed in frames into a logical unit
Note: The ASTM Urisys 2400 protocol is based on the ASTM protocol specification.
Records
A record is the smallest logical group of information. The ASTM Urisys 2400 protocol supports the
following records:
Identifier Name Description
H Header record First record in every message, mandatory
P Patient information
record
This record is used to download patient demographics
from the host system to the analyzer. With the cobas u
411 analyzer no patient data can be handled. Therefore
the patient record is always empty.
O Order record This record defines the attributes of a particular order.
R Result record Measurement data
C Comment record This record is used for the transmission of sample flags
and result flags.
M Manufacturer record This record is used for the transmission of raw data,
additional information for patient, control results.
Q Request information
record
Worklist request (query). Not supported.
Does not exist in ASTM URISYS 2400 protocol.
L Termination record Last record in every message, mandatory
Frames
A frame is a defined data structure that encapsulates a data block to be transmitted. According to
the ASTM Urisys 2400 protocol specification, a frame may contain one or more records. However,
the implementation in the cobas u 411 analyzer contains one record only. Each frame has the
following structure:
Description Start of
text
Frame
No.
End of
text
Check-
sum
Carriage
return
Line feed
ASCII
(hex)
STX
(0x02)
Protocol
specific
record
data
ETX
(0x03)
CR
(0x0D)
LF
(0x0A)
The frame no. always starts at 1 and will be incremented by one for each record. If the frame
reaches no. 7, the numbering starts at 0 (zero).
36. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 36 / 52
Usually, the ASTM protocol contains one record only per frame:
[STX] + Frame no. + Information (record) + [ETX] + Checksum + [CR] + [LF]
The ASTM Urisys 2400 protocol is a special implementation of ASTM. All records will be packed in
one frame. According to ASTM standard the total length of the data in one frame (message) is 247
bytes (including frame overhead). Messages longer than 240 bytes are divided into several frames,
called sub-frame. Such a sub-frame is terminated with an [ETB] character:
[STX] + Frame no. + Information 1 + [ETB] + Checksum + [CR] + [LF]
[STX] + Frame no. + Information 2 + [ETX] + Checksum + [CR] + [LF] (Msg-end, therefore [ETX])
Example:
u411 10:46:36,385 [ENQ]
Host 10:46:36,385 [ACK]
Information 1
u411 10:46:36,682 [STX]1H|^&|||8|||||||P|3.2.0.1001[CR]P|1[CR]O|
1|001|1^^^service^SAMPLE||R||||||X|||2011031510
1754[CR]R|1|^^^1|1.005|||||[CR]C|1|I||I[CR]R|2|
^^^2|7|||||[CR]C|2|I||I[CR]R|3|^^^3|NEG|||||[CR
]C|3|I||I[CR]R|4|^^^4|NEG|||||[CR]C|4|I||I[CR]R
|5|^^^5|NEG|||||[CR]C|5|I||I[CR]R|6|^^^6|NEG|||
||[CR][ETB]97[CR][LF] [ETB] Device control
Host 10:46:36,698 [ACK]
Information 2
u411 10:46:36,932 [STX]2C|6|I||I[CR]R|7|^^^7|NEG|||||[CR]C|7|I||I
[CR]R|8|^^^8|NEG|||||[CR]C|8|I||I[CR]R|9|^^^9|N
EG|||||[CR]C|9|I||I[CR]R|10|^^^10|NEG|||||[CR]C
|10|I||I[CR]R|11|^^^11|p.yel|||||[CR]C|11|I||I[
CR]R|12|^^^12||||||X[CR]C|12|I||I[CR]L|1|[CR][E
TX]D3[CR][LF] [ETX] End of text
Host 10:46:36,932 [ACK]
u411 10:46:36,979 [EOT]
Messages
Messages are collections of several records packed in frames into a logical unit. A message starts
with a Header Record (H) and ends with the Termination Record (L).
37. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 37 / 52
5.2.2 Communication structure
Only the cobas u 411 analyzer can start a communication. The cobas u 411 analyzer is always
the master, the host system the slave.
A communication is initialized when the ASCII character ENQ
(Hex 05) is sent to the host system.
The host system (slave) acknowledges its readiness to
communicate by sending the ASCII character ACK (Hex 06) or
if it is not ready the ASCII character NAK (Hex 15).
If the host system has positively acknowledged its readiness to
communicate (ACK), the cobas u 411 analyzer transmits the
message frame by frame.
The host system confirms the frame reception with ACK.
The host system can trigger a resending of the last sent frame
with NAK.
The communication session is terminated with the ASCII
character EOT (Hex 04).
cobasu411
38. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 38 / 52
5.2.3 Record descriptions
In this chapter, the meaning of the fields in individual records will be explained in the form of tables.
Fields which are not supported by the cobas u 411 analyzer are highlighted in grey.
For a better comprehension, there is a detailed example for each record description following the
table. Example trace files of different data interchanges are added at the end of this protocol
description.
Message header record
Each message starts with the Message Header Record. This record is mandatory.
No. Field Content Comment
1 Record type ID H The character H identifies the record as a
message header record.
Field Delimiter |
Repeat Delimiter
Component Delimiter ^
2
Escape Delimiter &
Defines the delimiters to be used
throughout the subsequent records of the
message.
3 Message control ID Not used in cobas u 411 analyzer
4 Access password Not used in cobas u 411 analyzer
5 Sender name or ID serial no. Serial number of the analyzer
6 Sender street address
7 Reserved field
8 Sender telephone
number
9 Characteristics of
sender
10 Receiver ID
11 Comment of special
instructinos
Not used in cobas u 411 analyzer
12 Processing ID P Always P (production)
13 Version number software version e.g. 3.2.0.1001
14 Date and time of
message
Not supported and not transmitted
Example:
No: 1 2 3 4 5 6 7 8 9 10 11 12 13 CR
Content: H | ^& | | | 8 | | | | | | | P | 3.2.0.1001 [CR]
Patient information record
Although the cobas u 411 analyzer does not record any patient data, the Patient Information
Record is mandatory by the ASTM standard. For this reason the cobas u 411 analyzer transmits
an empty record.
No. Field Content Comment
1 Record type ID P The character P identifies the record as a
patient record.
2 Sequence no. 1 The cobas u 411 analyzer sends one order
per transmission only. Therefore this value is
always 1.
3 .. 35 All further fields are not supported and not transmitted
39. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 39 / 52
Example:
No: 1 2 CR
Content: P | 1 [CR]
Order record
The cobas u 411 analyzer uses the Order Record to transmit general sample information such as
sample ID, sequence no. etc.
No. Field Content Comment
1 Record type ID O The character O identifies the record as an
order record.
2 Sequence no. 1 The cobas u 411 analyzer sends one order
per transmission only. Therefore this value is
always 1.
3 Specimen ID sample ID ID of the sample, numerical or
alphanumerical value (max. 13 digits)
4 Instrument
specimen ID
sample no
^rack ID
^position no.
^operator ID
^data carrier type
The cobas u 411 analyzer supports only
sample no, user ID and data carrier type
(“SAMPLE” for patient samples, “CONTROL”
for control samples. For order download the
sample no is not needed and is ignored.
5 Universal test ID Not used in cobas u 411 analyzer
6 Priority R Always R (routine sample), the cobas u 411
analyzer does not support emergency
samples
7 Request/ordered
date and time
8 Specimen collection
date and time
9 Collection end time
10 Collection volume
11 Collector ID
Not used in cobas u 411 analyzer
12 Action code X or XQ Always X, in case of control samples XQ
13 Danger code Not used in cobas u 411 analyzer
14 Relevant clinical
information
Not used in cobas u 411 analyzer
15 Date / time
specimen received
Date and time (format YYYYMMDDhhmmss)
example 20000202035009
16 .. 31 All further fields are not supported and not transmitted
Example patient sample:
No: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Content: O | 1 | 001 | 1^^^service^SAMPLE | | R | | | | | | X | | |
No: 15 CR
Content: 20110315101754 [CR]
Example control sample:
No: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Content: O | 1 | | 0^^^^CONTROL | | R | | | | | | XQ | | |
No: 15 CR
Content: 20110315100924 [CR]
40. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 40 / 52
Result record
The cobas u 411 analyzer uses the Result Record to transmit the measurement data. Each test
needs a separate Result Record. Flags related to test strip error, e.g. strip upside down, are sent
in this Result Record in no. 7 and no. 9. Flags related to results are sent in the Comment Record
and must be observed.
No. Field Content Comment
1 Record type ID R The character R identifies the record as a
result record.
2 Sequence no. 1 – 12 The cobas u 411 analyzer always saves 12
results (color and clarity included)
3 Universal test ID ^
^
^test no.
Test no list (fixation):
1: SG
2: pH
3: LEU
4: NIT
5: PRO
6: GLU
7: KET
8: UBG
9: BIL
10: ERY
11: COL
12: CLA
4 Data or
measurement value
result value Result value:
Numerical value (e.g. 1.030) or
alphanumerical value (e.g. „neg.”)
Important: To be compatible with the
original URISYS 2400 analyzer, the following
conversions are done in the driver:
pos POS
pos. POS
neg NEG
neg. NEG
norm NORM
norm. NORM
5 Unit unit Alphanumerical value (e.g. “mg/dL”), only if
result can be represented by several units
Important: All “l” letters, which stand for
“liter”, are converted to capital letters (e. g.
ml mL) and ’µ’ character is translated to a
‘u’ character.
6 Reference ranges Not used in cobas u 411 analyzer
7 Result abnorm. flag Flag “R”: Test Strip Error
8 Nature of
abnormality testing
Not used in cobas u 411 analyzer
9 Result status Flag “X”: Order cannot be done. Usually, in
combination with result abnormal flag (R)
10 .. 14 All further fields are not supported and not transmitted
Example:
No: 1 2 3 4 5 6 7 8 9 CR
Content: R | 1 | ^^^1 | 1.005 | | | | | [CR]
41. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 41 / 52
Example (test strip error: R/X-Flag):
No: 1 2 3 4 5 6 7 8 9 CR
Content: R | 2 | ^^^2 | | | | R | | X [CR]
Comment record
Every Result Record has a Comment Record attached. The cobas u 411 analyzer uses the
Comment Record to transmit the sample flags and result flags. In case of no flag, an empty
Comment Record is transmitted.
No. Field Content Comment
1 Record type ID C The character C identifies the record as a
comment record.
2 Sequence no. 1 The cobas u 411 analyzer uses the same
sequence number as the prior result record.
3 Comment source I Always I (clinical instrument system)
4 Comment text Sample result flags The cobas u 411 analyzer uses the
comment record only for transmitting flags,
each flag is separated with the ^ delimiter.
5 Comment type I Always I (instrument flag(s) comment)
Attention: Flags are in order to bring some of the values to attention of the operator. Therefore
it is important that these flags are displayed on the host system. If these flags are
not displayed, this could mislead the operator to wrong conclusions and medical
decisions!
Read the chapter “2.4 Flags” for detailed information!
Example (result record and comment record no flag):
Content: R|2|^^^2|7|||||[CR] Result record
No: 1 2 3 4 5 CR
Content: C | 2 | I | | I [CR] Comment record without flags
Example (result record and comment record edited result: !-flag:):
Content: R|2|^^^2|6|||||[CR] Result record
No: 1 2 3 4 5 CR
Content: C | 2 | I | ! | I [CR] Comment record with flags
Example (result record and comment record abnormal and sieve: *-flag and S-flag):
Content: R|2|^^^2|8|||||[CR] Result record
No: 1 2 3 4 5 CR
Content: C | 2 | I | *^S | I [CR] Comment record with flags
Example (result record and comment record test strip error: R/X-flag):
Content: R|2|^^^2||||R||X[CR] Result record with flags
No: 1 2 3 4 5 CR
Content: C | 2 | I | | I [CR] Comment Record without flags
42. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 42 / 52
Manufacturer record (raw result record - RR)
The cobas u 411 analyzer uses the Manufacturer Record RR to transmit raw data for special
application (e.g. evaluation / research). It is possible to activate this application via the user
interface (Utilities / Tools2 / Service “Raw Data to Host” ON)
No. Field Content Comment
1 Record type ID M The character M identifies the record as a
manufacturer record.
2 Sequence no. 1 – 16 The cobas u 411 analyzer determines
always 16 results, running number
3 Record type sub-ID RR Always RR (raw result)
4 Raw result value Reflectance floating number in the format ##.## (e.g.
88.06) fix order for raw result value:
1: COM blue
2: COM green
3: COM orange
4: ERY green
5: ERY orange
6: LEU green
7: NIT green
8: KET green
9: GLU green
10: PRO orange
11: UBG green
12: BIL green
13: pH green
14: pH orange
15: SG orange
16: not used, always 0
Example:
No: 1 2 3 4 CR
Content: M | 1 | RR | 78.19 | [CR]
Manufacturer record (result context record - RC)
The cobas u 411 analyzer uses the Manufacturer Record RC to transmit the control name as
well as the control lot number.
No. Field Content Comment
1 Record type ID M The character M identifies the record
as a manufacturer record.
2 Sequence no. 1 Running number
3 Record type sub-ID RC Always RC (result context)
4 Test strip cassette lot number Always empty
5 Date / time test strip cassette
set
Always empty
6 Control name e.g. Ctrl Control name
7 Control identifier e.g. 123456 Control lot no
Example:
No: 1 2 3 4 5 6 7 CR
Content: M | 1 | RC | | | ctrl | 123456 | [CR]
43. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 43 / 52
Termination record
Each message is closed with the Message Terminator Record. This record is mandatory.
No. Field Content Comment
1 Record type ID L The character L identifies the record
as a message terminator record.
2 Sequence no. 1 Per definition always 1
3 Termination code Empty if normal end of message
Example:
No: 1 2 3 CR
Content: L | 1 | [CR]
Scientific Record
This type of record is not used in cobas u 411 analyzer (the character S would identify the record
as a scientific record).
44. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 44 / 52
5.2.4 ASTM Urisys 2400 trace file examples
Example: Upload sample result without raw data
- Sample 1
- Sample 2 (with !-flag for pH)
- Sample 3 (with *- and S-flag for pH)
- Sample 4 (with T-flag)
Example: Upload sample result with raw data
- Sample 1
- Sample 2 (with !-flag for pH)
- Sample 3 (with *- and S-flag for pH)
- Sample 4 (with T-flag)
Example: Upload control result without raw data
Example: Upload control result with raw data
Example: Worklist download
Example: Upload sample result without raw data
Sample 1
u411 10:46:36,385 [ENQ]
Host 10:46:36,385 [ACK]
u411 10:46:36,682 [STX]1H|^&|||8|||||||P|3.2.0.1001[CR]P|1[CR]O|
1|001|1^^^service^SAMPLE||R||||||X|||2011031510
1754[CR]R|1|^^^1|1.005|||||[CR]C|1|I||I[CR]R|2|
^^^2|7|||||[CR]C|2|I||I[CR]R|3|^^^3|NEG|||||[CR
]C|3|I||I[CR]R|4|^^^4|NEG|||||[CR]C|4|I||I[CR]R
|5|^^^5|NEG|||||[CR]C|5|I||I[CR]R|6|^^^6|NEG|||
||[CR][ETB]97[CR][LF]
Host 10:46:36,698 [ACK]
u411 10:46:36,932 [STX]2C|6|I||I[CR]R|7|^^^7|NEG|||||[CR]C|7|I||I
[CR]R|8|^^^8|NEG|||||[CR]C|8|I||I[CR]R|9|^^^9|N
EG|||||[CR]C|9|I||I[CR]R|10|^^^10|NEG|||||[CR]C
|10|I||I[CR]R|11|^^^11|p.yel|||||[CR]C|11|I||I[
CR]R|12|^^^12||||||X[CR]C|12|I||I[CR]L|1|[CR][E
TX]D3[CR][LF]
Host 10:46:36,932 [ACK]
u411 10:46:36,979 [EOT]
Sample 2 (with !-flag for pH)
u411 11:02:07,436 [ENQ]
Host 11:02:07,436 [ACK]
u411 11:02:07,733 [STX]1H|^&|||8|||||||P|3.2.0.1001[CR]P|1[CR]O|
1|002|2^^^service^SAMPLE||R||||||X|||2011031510
2140[CR]R|1|^^^1|1.010|||||[CR]C|1|I||I[CR]R|2|
^^^2|6|||||[CR]C|2|I|!|I[CR]R|3|^^^3|NEG|||||[C
R]C|3|I||I[CR]R|4|^^^4|NEG|||||[CR]C|4|I||I[CR]
R|5|^^^5|NEG|||||[CR]C|5|I||I[CR]R|6|^^^6|NEG||
|||[ETB]9E[CR][LF]
Host 11:02:07,748 [ACK]
u411 11:02:07,983 [STX]2[CR]C|6|I||I[CR]R|7|^^^7|NEG|||||[CR]C|7|
I||I[CR]R|8|^^^8|NEG|||||[CR]C|8|I||I[CR]R|9|^^
^9|NEG|||||[CR]C|9|I||I[CR]R|10|^^^10|NEG|||||[
CR]C|10|I||I[CR]R|11|^^^11|p.yel|||||[CR]C|11|I
||I[CR]R|12|^^^12||||||X[CR]C|12|I||I[CR]L|1|[C
R][ETX]E0[CR][LF]
48. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 48 / 52
RC|||ctrl|123456|[CR]L|1|[CR][ETX]E3[CR][LF]
Host 10:45:59,208 [ACK]
u411 10:45:59,255 [EOT]
Example: Upload control result with raw data
u411 10:50:08,925 [ENQ]
Host 10:50:08,925 [ACK]
u411 10:50:09,222 [STX]1H|^&|||8|||||||P|3.2.0.1001[CR]P|1[CR]O|
1||0^^^service^CONTROL||R||||||XQ|||2011031510
0924[CR]R|1|^^^1|1.010|||||[CR]C|1|I||I[CR]R|2|
^^^2|8|||||[CR]C|2|I||I[CR]R|3|^^^3|NEG|||||[CR
]C|3|I||I[CR]R|4|^^^4|NEG|||||[CR]C|4|I||I[CR]R
|5|^^^5|NEG|||||[CR]C|5|I||I[CR]R|6|^^^6|NEG|||
||[CR][ETB]0C[CR][LF]
Host 10:50:09,222 [ACK]
u411 10:50:09,519 [STX]2C|6|I||I[CR]R|7|^^^7|NEG|||||[CR]C|7|I||I
[CR]R|8|^^^8|NEG|||||[CR]C|8|I||I[CR]R|9|^^^9|N
EG|||||[CR]C|9|I||I[CR]R|10|^^^10|NEG|||||[CR]C
|10|I||I[CR]R|11|^^^11|p.yel|||||[CR]C|11|I||I[
CR]M|1|RR|74.53|[CR]M|2|RR|73.39|[CR]M|3|RR|72.
37|[CR]M|4|RR|68.44|[CR]M|5|RR|73.07|[CR]M|6|RR
|76.90|[CR]M|7|[ETB]0B[CR][LF]
Host 10:50:09,534 [ACK]
u411 10:50:09,753 [STX]3RR|78.11|[CR]M|8|RR|62.41|[CR]M|9|RR|77.3
3|[CR]M|10|RR|70.10|[CR]M|11|RR|74.08|[CR]M|12|
RR|73.60|[CR]M|13|RR|32.52|[CR]M|14|RR|21.44|[C
R]M|15|RR|05.43|[CR]M|16|RR|0|[CR]M|17|RC|||ctr
l|123456|[CR]L|1|[CR][ETX]9F[CR][LF]
Host 10:50:09,753 [ACK]
u411 10:50:09,800 [EOT]
Example: Worklist download
ASTM Urisys 2400 protocol doesn’t support worklist download
49. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 49 / 52
6 Appendices
6.1 Appendix 1: ASCII-table
50. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 50 / 52
6.2 Appendix 2: Definition of test codes and test numbers
(for ASTM plus protocol only)
Parameter Test code Test number
Specific Gravity SG 1
pH-value pH 2
Leukocytes LEU 3
Nitrite NIT 4
Protein PRO 5
Glucose GLU 6
Ketones KET 7
Urobilinogen UBG 8
Bilirubin BIL 9
Erythrocytes ERY 10
Compensation pad COM 11
Color COL 12
Clarity CLA 13
… … …
Sediment Parameter 1 Name 1. Sediment Parameter 51
Sediment Parameter 2 Name 2. Sediment Parameter 52
Sediment Parameter 3 Name 3. Sediment Parameter 53
Sediment Parameter 4 Name 4. Sediment Parameter 54
Sediment Parameter 5 Name 5. Sediment Parameter 55
Sediment Parameter 6 Name 6. Sediment Parameter 56
Sediment Parameter 7 Name 7. Sediment Parameter 57
Sediment Parameter 8 Name 8. Sediment Parameter 58
Sediment Parameter 9 Name 9. Sediment Parameter 59
Sediment Parameter 10 Name 10. Sediment Parameter 60
Sediment Parameter 11 Name 11. Sediment Parameter 61
Sediment Parameter 12 Name 12. Sediment Parameter 62
Sediment Parameter 13 Name 13. Sediment Parameter 63
Sediment Parameter 14 Name 14. Sediment Parameter 64
Sediment Parameter 15 Name 15. Sediment Parameter 65
Sediment Parameter 16 Name 16. Sediment Parameter 66
Sediment Parameter 17 Name 17. Sediment Parameter 67
Sediment Parameter 18 Name 18. Sediment Parameter 68
Sediment Parameter 19 Name 19. Sediment Parameter 69
Sediment Parameter 20 Name 20. Sediment Parameter 70
Sediment Parameter 21 Name 21. Sediment Parameter 71
Sediment Parameter 22 Name 22. Sediment Parameter 72
Sediment Parameter 23 Name 23. Sediment Parameter 73
Sediment Parameter 24 Name 24. Sediment Parameter 74
Sediment Parameter 25 Name 25. Sediment Parameter 75
Sediment Parameter 26 Name 26. Sediment Parameter 76
Sediment Parameter 27 Name 27. Sediment Parameter 77
Sediment Parameter 28 Name 28. Sediment Parameter 78
Sediment Parameter 29 Name 29. Sediment Parameter 79
Sediment Parameter 30 Name 30. Sediment Parameter 80
51. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 51 / 52
6.3 Appendix 3: Printouts of control and sample results
Sample Result - Sample 1 Sample Result - Sample 2
with !-flag for pH
Sample Result - Sample 3
with *- and S-flag for pH
and sediment data for ERY and LEU
Sample Result - Sample 4
with T-flag
52. cobas u 411 Host
cobas u 411 Host Interface Manual V 2.1 52 / 52
Control Result
