Roche Elysis Astm Guide PDF

2010 Host Interface Training Guide – Advanced Level
Introduction
Purpose of guide This guide is

• used in the advanced level training of the Roche Response Center on the
Elecsys 2010 disk and rack systems (2010), and
• intended to be used as a resource when troubleshooting the 2010 host
interface.
This guide incorporates all information from the 2010 Host Interface
Training Guide – Novice Level and is intended to serve as a replacement once
the advanced level training is completed.
Scope This guide is only applicable to the 2010 host interface, software version
03-12.
Caution! This guide serves as a supplement to the Roche Response Center host
interface training and is not for customer use. This document can be used in
conjunction with the Elecsys 2010 Advanced Level Host Interface CBT.
For further When in doubt of the information provided or if there is a need for further
information detail, refer to the 2010 host interface document, operator’s manual, or
Systems Support department.
Definitions In all examples and formats, a diamond (à) is used to represent a space.
Continued on next page
Published by: S. Pearson Approved by:

Date Printed: 11/21/00 C. Henderson
Black or Blank copy number indicates uncontrolled copy. Controlled Copy No.:
Roche Diagnostics confidential. Copy with care.
Revision: 1.0 Page 1 of 69

If using a hard copy, always check against electronic version prior to use.
2010 Host Interface Training Guide – Advanced Level,
Continued
Introduction, Continued
Guide contents This guide covers the following topics
Topic See Page

Parameters 3
ASTM 6
Message Header Record 12
Message Terminator Record 16
Patient Information Record 18
Test Order Record 23
Result Record 30
Comment Record 36
Request Information Record 38
Manufacturer Specific Records 47
Transmission Packets 48
Troubleshooting 63
Communication Examples 66
Workflow 60
Checksum 61
Host Port 62
Troubleshooting 63
Communication Examples 66

Continued
Parameters
Introduction There are several host parameters on the 2010 that impact the
communications between the host and analyzer. This section reviews these
parameters including how to set them.
Setting All host parameters on the 2010 are configured using the software.
parameters
Use the steps below to access host parameters.
Step Action
1 Touch the Util tab.
2 Touch the Interface Setup tab.
3 Press the appropriate button until desired setting is
displayed.
Note: To make changes to the parameter settings, communications must be

turned off and the analyzer must be in stand-by.
Screen The screen below shows the display when Interface Setup tab is pressed.

Continued
Parameters, Continued
Communi- When the communication button is pressed, a ‘Confirmation’ pop-up

cation window is displayed that lets you select your option.
The on setting activates the communication port while the off setting
deactivates the communication port.
Baud rate Baud rate can be set to 2400, 4800, 9600 or 19200.
Data bits Data bits can be set to 7 or 8.
Stop bits Stop bits can be configured at 1 or 2.
Parity Parity can be selected as none, odd or even.
Sync Synchronization can be set to on or off.
If synchronization is turned on, hardware handshaking (XON/XOFF) will be

activated. The Synchronization setting should be set to off.

Continued
Parameters, Continued
Upload options Results can be set to upload with or without a printout and automatically or
manually. To set the upload options, use the steps below.
Step Action
1 Press Util tab.
2 Press Documentation Setup tab.
3 Select Printout, Upload, or Print/Upload under Document
Options.
4 Select Automatic On or Automatic Off under Automatic Options.
Options for uploading are determined by the Document and Automatic

Options, as shown here.
Document Options Automatic Options Results

Automatic On Results are lost for transmission to
Printout host. Results automatically print.
Automatic Off Results are lost for transmission to
host. Results print when press Doc.
Automatic On Results will be uploaded to host
when completed. They can not be
printed.
Automatic Off Results will be uploaded to host
when triggered manually from
Upload Results folder. Results can not be
printed.
• Pressing DOC key will transmit
displayed sample.
• Pressing Print All button will
transmit all samples.
Automatic On Results will be uploaded to host
when printed. Results will be
Print/Upload printed when they are complete.
Automatic Off Results will be uploaded to host
when printed. Printing will occur
when requested by operator.
Note: If the 2010 is set to upload, results will not be deleted until they are
upload to the host.

Continued
ASTM
Introduction ASTM (American Society for Testing and Materials) is an organization of

users, manufacturers and vendors who develop standards for all different
products from highlighters to vacuum cleaners.
A group of LIS companies, lab equipment manufacturers and lab equipment

users got together and developed two standards for connecting laboratory
equipment (every type of laboratory equipment) to laboratory computers.
The idea behind the standard was that a customer could easily install a new
instrument without having to completely rewrite the interface.
ASTM standards The low-level protocol, E1381-91, describes how the data is transmitted
between the 2010 and host. This standard provides rules for how the two
systems talk to each other. Refer to the Protocol section for more details.
The high-level protocol, E1394-91, relates to the packet content and format of
the data that is transmitted. This standard provides rules for the sentence
structure. Refer to the Transmission Packets section for more information.
The 2010 implementation of these two standards and related terminology are
summarized in this document. Detailed specifications can be found in the
Elecsys 2010 Host Interface Manual.

Continued
ASTM, Continued
ASTM The following terms are used in the ASTM standard and 2010 specification.
terminology
Term Definition
Field One specific attribute of a record or patient.
Record A group of fields describing one aspect of a
message or patient.
Message A group of records describing a patient and
its related data.
Message This diagram shows the relationship between a message, record and field.
diagram
MESSAGE RECORD FIELD
Header Record Sequence
Number
Patient Record Patient ID
Order Record Patient Name Patient Name
Results Record Patient Sex
Terminator Patient Location
Record
describes patient and describes one aspect of one specific attribute of

related data a patient or message a patient or record
Message This example shows how fields, records and messages are related.
example
Field
1H|\^&| | | | | | | | | | P| | [CR] Record
2Q|1|^000083^135^0^1^^SAMPLE^NORMAL| |ALL| | | | | | | |O[CR]
3L|1[CR]
Message

Continued
ASTM, Continued
Messages Messages are a combination of records that are used to transmit data about a
patient. This table lists the different messages used in the ASTM standard.
Message Use
Test Selection Request 2010 asking for test selections
Test Selection Download Host sending test selections
Results Request Host asking for specific results
Measured Data 2010 sending results
Records Records describe one aspect of a message or patient. This table lists the
different records used.
Level ID Record Direction Contents

0 H Message Header 2010 ↔ Host Instrument identification and
delimiters
1 P Patient Information 2010 ↔ Host Information about a specific
patient
2 O Test Order 2010 ↔ Host Test selections for a specific
patient
3 R Result 2010 → Host One result for a specific patient
0 L Message Terminator 2010 ↔ Host End of message data
1 Q Request Information 2010 ↔ Host Request for specific
information
0..4 C Comment 2010 ↔ Host Free text about previous record
0..4 M Manufacturer 2010 → Host Manufacturer defined
Information
1 S Scientific Not used

Continued
ASTM, Continued
Messages and This table shows the combination of records used for each message.
records
Message Records Used

Test Selection Request Message Header Record
Request Information Record
Message Terminator Record
Test Selection Download Message Header Record
Patient Information Record
Order Record
Results Request Message Header Record
Measure Data Message Header Record
Order Record
Result Record

Continued
ASTM, Continued
Message rules The follow rules apply to the transmission of a message.

1. Messages start with a Message Header record and end with a Message
Terminator record.
2. An Order record must have a Patient record.
3. A Result record must have an Order record.
4. A Comment record may be inserted at any level other than after the
Message Terminator record.
Message order This example shows the various records that can be used to create a message
and how the hierarchy is used.
(Level 0) MESSAGE HEADER

(Level 1) | MANUFACTURER INFORMATION 1
(Level 1) | PATIENT 1 (general information about patient)
(Level 2) | | COMMENT 1 (relates to previous PATIENT 1)
(Level 2) | | ORDER 1 (information about first battery for patient 1)
(Level 3) | | | COMMENT 1 (relates to previous ORDER 1)
(Level 3) | | | RESULT 1 (information about first result of order 1)
(Level 3) | | | RESULT 2 (information about second result of order 1)
(Level 4) | | | | COMMENT 1 (relates to RESULT 2)
(Level 4) | | | | COMMENT 2 (relates to RESULT 2)
(Level 3) | | | RESULT n (information about last result in order 1)
(Level 2) | | ORDER 2 (information about battery 2)
(Level 2) | | ORDER n (information about last battery for first patient)
(Level 3) | | | RESULT 1 (information about first result of order n)
(Level 3) | | | RESULT n (information about last result in order n)
(Level 1) | PATIENT 2
(Level 2) | | ORDER 1 (information about first battery for patient 2)
(Level 3) | | | COMMENT 1 (relates to previous ORDER 1)
(Level 2) | | ORDER n (information about last battery for patient 2)
(Level 3) | | | RESULT 1 (information about first result of order n)
(Level 3) | | | RESULT n (information about last result in order n)
(Level 0) MESSAGE TERMINATOR

Continued
ASTM, Continued
Delimiters Delimiters are used to separate information. Delimiter characters are defined
by the host and transmitted in the Message Header record. The table below
lists the delimiters used in the ASTM standard but any character may serve as
a delimiter.
Delimiter Character Description Use

Record delimiter CR Carriage Used in a message to
Return separate records.
Field delimiter | Vertical Bar Used in a record to
separate fields.
Repeat delimiter \ Backslash Used in a field to separate
replicates such as test
codes.
Component ^ Caret Used in a field to separate
delimiter components such as an
address with street, city
and state.
Escape delimiter & Ampersand Used in a field to signify
special case operation such
as highlighted text.
Delimiter The message below provides an example of how delimiters are used.
example
1H|\^&| | | | | | | | | |P| |[CR] Component
Record delimiters
2P|1[CR] delimiters
3O|1|000004|40^0^4^^SAMPLE^REDUCED|^^^10^0\^^^50^0\^^^20^0
\^^^30^0|R|19970425085218| | | | |N| | | | | | | | | | | | | |Q[CR]
Repeat
4L|1|F[CR] Delimiter
Field
delimiters

Continued
Message Header Record
General notes The Message Header record is used by the host and 2010 at the beginning of
every message. This record identifies the sender and defines the delimiters
used in the message.
The Message Header record is always a level 0 record.
Because the field delimiters have not been defined, a field delimiter does not
separate the first and second fields of the Message Header record.
Message Header Below is the content of the Message Header record. Framing and delimiters
record content are not included in the table.
Field Content Comments

Record Type ID H
Delimiter Definition |\^& field, repeat, component
and escape delimiters
Message Control ID ignored
Access Password ignored
Sender Name or ID free text not used by 2010
Sender Street Address ignored
Reserved Field ignored
Sender Telephone Number ignored
Characteristics of Sender ignored
Receiver ID free text not used by 2010
Comment or Special ignored
Instruments
Processing ID P or D P: production
null = P D: debugging
see Processing IDs T: ignored
table Q: ignored
Version No. ignored not used by 2010
Date and Time of Message yyyymmddhhmmss not used by 2010

Continued
Message Header Record, Continued
Processing IDs This table lists the possible processing IDs and the definition of each. The
processing ID is used to indicate the purpose of the message. The host is not
required to send the Processing ID.
ID Name Use
P or null Production This is the normal processing ID and
message should be processed according to
protocol. The 2010 will send a P.
D Debugging Message is initiated for debugging
purposes.

Continued
Message Header Below is an example of a Message Header record sent by the 2010.
record example
1
Data Frame Record Delimiter Field Field Field
Start Number Type ID Definition Delimiter Delimiter Delimiter
STX 1 H |\^& | | |
… Field Field Field Field Field Field

Delimiter Delimiter Delimiter Delimiter Delimiter Delimiter
… | | | | | |
… Field Processing Field Field Record

Delimiter ID Delimiter Delimiter Delimiter
… | P | | CR
… Data End Checksum End Code

… ETX 05 CR LF
Example 1 The previous Message Header record example transmitted the following
details information.
Field Content Description

Frame Number 1 first record in message
Record Type ID H Header record
Delimiter Definition |\^& | - field delimiter
\ - repeat delimiter
^ - component delimiter
& - escape delimiter
Processing ID P production message
Checksum 05

Continued
Message Header Below is an example of a Message Header record sent by the host. In this
record example example, there is no data after the sender name so the remaining fields are not
2 sent.
Data Frame Record Delimiter Field Field

Start Number Type ID Definition Delimiter Delimiter
STX 1 H |\^& | |
… Field Sender Record Data End

Delimiter Name Delimiter End Checksum Code
… | ASTM-Host CR ETX 59 CR LF
Example 2 The previous Message Header record example transmitted the following

Frame Number 1 first record in message
Record Type ID H Header record
Delimiter Definition |\^& | - field delimiter
\ - repeat delimiter
^ - component delimiter
& - escape delimiter
Sender Name ASTM-Host identification of host - 2010
ignores this information
Checksum 59

Continued
Introduction The Message Terminator record is the last record in every message. It is used
by both the 2010 and host. The 201 will send errors concerning the protocol
in the Message Terminator Record.
The Message Terminator record is always a level 0 record.
Message Below is the content of the Message Terminator record. Framing and
Terminator delimiters are not included in the table.
record content

Record Type ID L
Sequence 1 indicates nth Terminator record
Number in message
Termination E, F, I, N, Q or E data content or format error
Code space F: all requested information
has been sent
see Termination I: no information available for
codes table query
N or null: normal termination
Q: response to invalid query
R: ignored
T: ignored
Termination The table below gives the various termination codes that are used in the
codes Message Terminator record. The Message Terminator record is used to give
additional information about the message transmission. These codes can be
used for troubleshooting protocol issues.
Code Definition
N or Null normal end
E unknown system or packet content error
F last request for information processed
I no information available for last query
Q error in last request for information

Continued
Message Terminator Record, Continued
Message Below is an example of a Message Terminator record sent by the 2010. In this
Terminator example, there is no Termination Code field because the message ended
record example normally.
Data Frame Record Field Sequence Record Data Checksum End

Start Number Type ID Delimiter Number Delimiter End Code
STX 3 L | 1 CR ETX 3C CR LF
Example details The previous Message Terminator record example transmitted the following
information.

Frame Number 3 third record in message
Record Type ID L Message Terminator record
Sequence Number 1 first Message Terminator
record in message
Checksum 3C

Continued
Introduction The Patient Information record is used by the host and 2010 to send
information about a specific patient.
The Patient Information record is always a level 1 record and will precede a
Test Order record if one is present.
Patient Below is the content of the Patient Information record. Framing and
Information delimiters are not included in the table.
record content
Note: The 2010 only recognizes the Laboratory Assigned Patient ID field. All
other fields are ignored.

Record Type ID P
Sequence Number numeric indicates nth Patient Information
record in message
Practice Assigned ignored
Patient ID
Laboratory Assigned text Not used as sample identification
Patient ID but when received with test order
will be sent back with results.
Patient ID No. 3 ignored
Patient Name ignored
Mothers Maiden ignored
Name
Date of Birth ignored
Patient Sex ignored
Patient Race ignored
Patient Address ignored
Patient Telephone ignored
Number

Continued
Patient Information Record, Continued
Patient Information record content (continued)

Attending Physician ignored
ID
Special Field 1 ignored
Special Field 2 ignored
Patient Height ignored
Patient Weight ignored
Patient Known or ignored
Suspected Diagnosis
Patient Active ignored
Medications
Patient’s Diet ignored
Practice Field 1 ignored
Practice Field 2 ignored
Admission and ignored
Discharge Dates
Admission Status ignored
Location ignored
Nature of ignored
Alternative
Diagnostic Code
Alternative ignored
Diagnostic Code
Patient Religion ignored
Marital Status ignored
Isolation Status ignored
Language ignored
Hospital Service ignored
Hospital Institution ignored
Dosage Category ignored

Continued
Patient Below is an example of a Patient Information record sent by the host. In this
Information example, there is no data after the Laboratory Assigned Patient ID field so the
record remaining fields are not sent.
example 1
Data Frame Record Field Sequence Field Field
Start Number Type ID Delimiter Number Delimiter Delimiter
STX 2 P | 1 | |
… Laboratory Assigned Record Data End Checksum End

Patient ID Delimiter Code
… 000004 CR ETX 5F CR LF
Example 1 The previous Patient Information record example transmitted the following

Frame Number 2 second record in message
Record Type ID P Patient Information record
Sequence Number 1 first Patient Information
record in message
Lab Assigned ID 000004 patient ID
Checksum 5F

Continued
Information example, there is no data after the Laboratory Assigned Patient ID field so the
record remaining fields are sent empty with only field delimiters.
example 2
Data Frame Record Field Sequence Field Field
Start Number Type ID Delimiter Number Delimiter Delimiter
STX 2 P | 1 | |
… Laboratory Assigned Field Field Field Field

Patient ID Delimiter Delimiter Delimiter Delimiter
… 000004 | | | |

… | | | | | |

… | | | | | |

… | | | | | |

… | | | | | |
… Field Field Field Record Data Checksum End

Delimiter Delimiter Delimiter Delimiter End Code
… | | | CR ETX 59 CR LF

Continued
Example 2 The previous example transmitted the following information.

details
record in message
Lab Assigned ID 000004 patient ID sent from host
Checksum 59
Information example, there is no Patient ID.
record
example 3
Data Frame Record Field Sequence
Start Number Type ID Delimiter Number
STX 2 P | 1
… Record Data End Checksum End

Delimiter Code
… CR ETX 3F CR LF
Example 3 The previous Patient Information record example transmitted the following

record in message
Checksum 5F

Continued
Test Order Record
Introduction The Test Order record is used by the 2010 and host to transmit the test
selections for a specific sample. This record can also be used by the host to
cancel test selections for a sample.
The Test Order record is always a level 2 record and follows the Patient
Information record. It will also precede a Result record if one is present.
Note: The host must echo the same patient information contained in the
Request Information record when responding to a query.
Test Order Below is the content of the Test Order record. Framing and delimiters are not
record content included in the table.

Record Type ID O
Sequence numeric indicates nth Test Order
Number record in message
Specimen ID barcode or sample ID 2010 sample ID
Instrument sequence number The 2010 will send the first
Specific ID ^carrier number three components as
^position in carrier applicable. If the host
^format downloads any remaining
^data carrier type components, the 2010 will
^container type return them with the results.
^container cap type
înitial volume in ml see Instrument specific ID
table

Continued
Test Order Record, Continued
Test Order record content (continued)

Universal Test ID universal test ID Only the fourth and
^test name remaining components are
^test ID type applicable to the 2010.
^2010 test number
âuto-dilution see Universal test ID table
factor
^pre-dilution factor
êndogenous
content of pre-
dilution
Priority R or S R: routine
S: STAT
Note: S=A and A: as soon as possible
R=C=P C: call back
P: preoperative
Requested/Order yyyymmddhhmmss If no data is sent from host,
Date and Time the 2010 will return this
field with the date and time
the patient information was
received.
Specimen Collection ignored
Date and Time
Collection End Time ignored
Collection Volume ignored
Collector ID ignored
Action Code A, C, N, P, Q, X or A: add to existing sample
space C: cancel tests listed
N: request for new sample
Note: The 2010 will P: pending sample
send a space for X: sample in process
normal samples and L: ignored
Q for controls. N\Q: new QC sample
A\Q: changing QC sample
The host must use a C\Q: canceling QC sample
combination of X\Q: control in process
codes for controls or
will treat as patient.

Continued
Test Order record content (continued)

Danger Code ignored
Relevant Clinical ignored
Information
Date/Time Specimen ignored
Received
Specimen Type & ignored
Source
Ordering Physician ignored
Physician’s Telephone ignored
Number
User Field No.1 ignored
User Field No. 2 ignored
Lab Field No. 1 ignored
Lab Field No. 2 ignored
Date/Time Results ignored
Reported/Modified
Instrument Charge to ignored
Computer System
Instrument Section ID ignored
Report Types F, O, I, Z or Q F: final results
O: order record
Note: If the host has I: pending in instrument
no test selections for Z: no record (in response
a query, it must to query for
respond using a Z. information)
Q: response to query
C, P, X, Y: ignored
Location of Specimen ignored
Collection
Nosocomial Infection ignored
Flag
Specimen Service ignored
Specimen Institution ignored

Continued
Instrument This table details the components of the Instrument Specific ID.
specific ID
Component Valid Entries
sequence number 2010 sequence number
carrier number Rack or sample disk number
rack system: 1-9999
disk system: 0-9
position in carrier Position in rack or sample disk
rack system: 1-5
disk system: 1-30
format not used by 2010
data carrier type Sample type: CONTROL or SAMPLE
container type Sample volume: NORMAL (75 or 100mm tube) or
REDUCED (all other tube sizes)
container cap type not used by 2010
initial volume in ml not used by 2010
Universal test This table details the components of the Universal Test ID.
ID
universal test ID not used by 2010
test name not used by 2010
test ID type not used by 2010
2010 test number Three digit Elecsys test code
* first two digits are test code defined in reagent
barcode and listed on test conditions screen (1-99)
* last digit represents generation (0-2)
See appendix A in Elecsys 2010 Host Manual
auto-dilution factor null or 0: sample not to be diluted
1, 2, 3, 5, 7, 9, 10: see Auto-dilution factor table
pre-dilution factor 0: sample not pre-diluted
1: sample pre-diluted
Note: Host cannot download this flag.

endogenous content not used by 2010
of pre-dilution

Continued
Auto-dilution See table below for auto-dilution factor usage.

factor
Field Ratio Pipetting

Content Used Volumes
1st dilution 2nd dilution
sample diluent sample diluent
volume volume volume volume
0 1:1 no sample dilution
1 2:1 50 ml 50 ml
2 5:1 40 ml 160 ml
3 10:1 20 ml 180 ml
5 20:1 20 ml 180 ml 100 ml 100 ml
7 50:1 20 ml 180 ml 40 ml 160 ml
9 100:1 20 ml 180 ml 20 ml 180 ml
10 100:1 10 ml 90 ml 20 ml 180 ml

Continued
Test Order Below is an example of a Test Order record from the host. In this example,
record there is no data after the Report Types field so remaining fields are not sent.
example
Data Frame Record Field Sequence Field Specimen
Start Number Type ID Delimiter Number Delimiter ID
STX 3 O | 1 | 000083
… Field Instrument Field Universal Repeat

Delimiter Specific ID Delimiter Test ID Delimiter
… | 135^0^1^^SAMP | ^^^10^0 \
LE^NORMAL
… Universal Field Priority Field Field Field

Test ID Delimiter Delimiter Delimiter Delimiter
… ^^^150^ | R | | |
0
… Field Field Field Action Field Field

Delimiter Delimiter Delimiter Code Delimiter Delimiter
… | | | N | |

… | | | | | |

… | | | | | |
… Report Record Data Checksum End

Types Delimiter End Code
… Q CR ETX F9 CR LF

Continued
Example details The previous example transmitted the following information.

Frame Number 3 third record in message
Record Type ID O Test Order record
Sequence Number 1 first Test Order record in
message
Specimen ID 000083 Sample ID
Instrument Specific 135^0^1^^SA sequence number – 135
ID MPLE^NORMA carrier number – 0
L position in carrier – 1
data carrier type – sample
container type - normal
Test ID 1 ^^^10^0 test code - 10 (TSH)
auto-dilution – no
Test ID 2 ^^^150^0 test code - 150 (FSH)
Priority R routine sample
Action Code N new patient request
Report Types Q in response to query
Checksum F9

Continued
Result Record
Introduction The Result record is used by the 2010 to transmit the results to the host.
The Result record is always a level 3 record and will always be preceded by a
Test Order record.
Result record Below is the content of the Result record. Framing and delimiters are not
content included in the table.

Record Type ID R
Sequence numeric nth Result record in message
Number
Universal Test ID universal test ID Only the fourth and
^test name remaining components are
^test ID type applicable to the 2010.
^2010 test number
âuto-dilution factor See Universal test ID table
^pre-dilution factor
êndogenous content
of pre-dilution
Data or alphanumeric Quantitative:
Measurement concentration
Value < concentration
> concentration
Qualitative:
1 = positive
0 = border line
-1 = negative
No Value: null
Units alphanumeric units as defined on 2010
Reference Ranges lower limit normal/panic ranges for test
ûpper limit target value/ranges for QC

Continued
Result Record, Continued
Result record content (continued)

Result Abnormal L, H, <,>, A, N, L: below low normal
Flag 2 digit data alarm H: above high normal
>: below absolute normal
Note: Instrument <: above absolute normal
warnings sent in A: abnormal
Comment record. N: normal
LL,HH,A,U,D,B,W: ignored
Nature of ignored
Abnormality
Testing
Result Status F, X, I, R, Q, V, Y, + F: final results
X: results cannot be done
I: results pending
R: results previously sent
Q: response to query
V: operator verified
Y: system blocked
+: user blocked
C, P, S, M, N: ignored
Date of Change in ignored
Instrument
Normative Values
Operator ID ignored
Date/Time Test yyyymmddhhmmss sampling time
Started
Date/Time Test yyyymmddhhmmss ready time
Completed
Instrument ID ignored

Continued
Universal test This table details the components of the Universal Test ID.
ID

of pre-dilution

Continued

factor

1 2:1 50 ml 50 ml
2 5:1 40 ml 160 ml
3 10:1 20 ml 180 ml
5 20:1 20 ml 180 ml 100 ml 100 ml
7 50:1 20 ml 180 ml 40 ml 160 ml
9 100:1 20 ml 180 ml 20 ml 180 ml
10 100:1 10 ml 90 ml 20 ml 180 ml

Continued
Result record Below is an example of a Result record from the 2010. In this example, there
example is no Instrument ID field so the last field is the field delimiter.
Data Frame Record Field Sequence Field Test ID

Start Number Type ID Delimiter Number Delimiter
STX 5 R | 2 | ^^^30^0
… Field Measurement Field Units Field

Delimiter Value Delimiter Delimiter
… | 16.29 | pmol/l |
… Reference Field Abnormal Field Field Result

Range Delimiter Flag Delimiter Delimiter Status
… 13.00^23.00 | N | | F
… Field Field Field Date/Time Test Field

Delimiter Delimiter Delimiter Started Delimiter
… | | | 19980403090847 |
… Date/Time Test Field Record Data Checksum End

Completed Delimiter Delimiter End Code
… 19980403092709 | CR ETX 63 CR LF

Continued
Example details The previous Result Record example transmitted the following information.

Frame Number 5 fifth record in message
Record Type ID R Result record
Sequence Number 2 second Result record in
message
Test ID ^^^30^0 test code - 30 (FT4)
Measurement Value 16.29 result
Units pmol/l units
Reference Range 13.00^23.00 13.00 – 23.00 (normal range)
Result Abnormal Flag N normal
Result Status F final results
Date/Time Test 19980403090847 sampling date – 4/3/98
Started sampling time – 09:08:47
Date/Time Test 19980403092709 ready date – 4/3/98
Completed ready time – 09:27:09
Checksum 63

Continued
Comment Record
Introduction The Comment record is used by the 2010 and host to transmit information
specific to the previous record.
The Comment record can be a level 0, 1, 2 or 3 record. The Comment record

always applies to the previous record. The Comment record cannot follow a
Message Terminator record.
Comment Below is the content of the Comment record. Framing and delimiters are not
record content included in the table.

Record Type ID C
Sequence Number numeric nth Comment record in
message
Comment Source I I: instrument
P, L: ignored
Comment Text free text or the 2010 will use the
alarm code^ Comment record to
alarm message transmit any data alarms
for previous Result
records using the alarm
codeâlarm message
format
Comment Type G, I G: generic free text
I: instrument flag
T, P, N: ignored

Continued
Comment Record, Continued
Comment Below is an example of a Comment record. This particular Comment record

record example would be an example of one that follows a Result record.
Data Frame Record Field Sequence Field

STX 6 C | 1 |
… Comment Field Field

Source Delimiter Comment Delimiter
… I | 52Êxpiredàreagentàpack |
… Comment Record Data End

Type Delimiter End Checksum Code
… I CR ETX 97 CR LF
Example details The previous Comment record example transmitted the following
information.

Frame Number 6 sixth record in message
Record Type ID C Comment record
Comment Source I instrument
Comment 52Êxpiredàrea alarm code – 52
gentàpack alarm message – Expired
reagent pack
Comment Type I instrument flag
Checksum 97

Continued
Introduction The Request Information record is used by the 2010 and host to request
demographics, test selections or test results for specific patients, specimens,
tests or dates.
The Request Information record is a level 1 record. The Request Information

record is sent with only a Message Header record and Message Terminator
record.
Request Below is the content of the Request Information record. Framing and
Information delimiters are not included in the table.
record content

Record Type ID Q
Sequence Number numeric indicates nth Request
Information record in
message
Starting Range ID Number patient ID Specimen ID is barcode
^specimen ID number of sample ID.
^sequence number
^carrier number See Range ID table
^position in carrier
^format
^data carrier type
^container type
^container cap type
înitial volume in
ml

Continued
Request Information Record, Continued
Request Information record content (continued)

Ending Range ID patient ID Specimen ID is barcode
^specimen ID number of sample ID
^sequence number
^carrier number This field is null when
^position in carrier only one sample’s
^format information is request
^data carrier type
^container type See Range ID table
^container cap type
înitial volume in
ml
Universal Test ID ALL or From host = ALL
universal test ID
^test name Only fourth and
^test ID type remaining components
^2010 test number are applicable to the
âuto-dilution 2010
factor
^pre-dilution factor See Universal test ID
êndogenous table
content of pre-
diluent
Nature of Request Time R or null R, null: result date
Limits S: ignored
Beginning Request Results ignored
Date and Time
Ending Request Results ignored
Date and Time
Requesting Physician Name ignored
Requesting Physician ignored
Telephone Number
User Field No. 1 N, Q N: normal sample
Q: control sample
Only used by host.

Continued
Request Information record content (continued)

User Field No. 2 ignored
Request Information Status O, F, X, I, R, A, N O: request test selections
Codes from host
The O status is used F: request final results
by the 2010 and the X: cancel specific request
remaining statuses I: request results pending
are used by host. R: request results sent before
A: cancel last request
N: request new or edited
result only
C, P, S, M, D: ignored

Continued
Range ID This table details the components of the Starting and Ending Range ID
Number.

patient ID
specimen ID barcode number or 2010 sample ID
sequence number 2010 sequence number
carrier number Rack or sample disk number
rack system: 1-9999
disk system: 0-9
Note: A default Rack ID of @ symbol plus a one or two

digit number is sent when the rack barcode has not
been read prior to the Request Information record
being sent. The host must echo this exact carrier
number. The results will be returned with the
appropriate rack ID number.
position in carrier Position in rack or sample disk
rack system: 1-5
disk system: 1-30
format not used by 2010
data carrier type Sample type: CONTROL or SAMPLE
container type Sample volume: NORMAL or REDUCED
container cap type not used by 2010
initial volume in ml not used by 2010

Continued
Query data The following table shows what data is sent by the 2010 when querying
ID Seq. # Car. # Pos. #

Query (disk)
Bar-coded sample √ √ √ √
No BC, but SID assigned √ √ √ √
No BC, no SID assigned √ √ √
empty position √ √ √
Query (rack)
Bar-coded sample √ √ default rack ID √
No BC, but SID assigned √ √ √ √
empty position NO QUERY
No BC, rack ID not read √ default rack ID √
No BC, SID assigned, rack √ default rack ID √
ID not readable

Continued
Universal test This table details the components of the Universal Test ID. When sent by the
ID host as a query for a sample’s results, ALL is used.

of pre-dilution

Continued

factor

1 2:1 50 ml 50 ml
2 5:1 40 ml 160 ml
3 10:1 20 ml 180 ml
5 20:1 20 ml 180 ml 100 ml 100 ml
7 50:1 20 ml 180 ml 40 ml 160 ml
9 100:1 20 ml 180 ml 20 ml 180 ml
10 100:1 10 ml 90 ml 20 ml 180 ml

Continued
Request Below is an example of a Request Information record. This particular

Information Request Information record is an example of what the 2010 would send to the
record example host to request test selections for a specific sample.
Data Frame Record Field Sequence Field

STX 2 Q | 1 |
… Starting Range ID Field Field Universal Field

Delimiter Delimiter Test ID Delimiter
… ^000083^135^0^1^^ | | ALL |
SAMPLE^NORMAL

… | | | | | |
… Field Request Record Data Checksum End

Delimiter Information Delimiter End Code
Status Code
… | O CR ETX FE CR LF

Continued
Example details The previous Request Information record example transmitted the following
information.

Record Type ID Q Query record
Sequence Number 1 first Request Information
Record in message
Starting Range ID ^0000135^135^0^ specimen ID – 000083
Number 1^^SAMPLE^NOR sequence number – 135
MAL
carrier number – 0
position in carrier – 1
data carrier type – sample
container type - normal
Universal Test ID ALL request for all tests the host
has available
Request Information O requesting test selections
Status Code
Checksum FE

Continued
Manufacturer Specific Records
Introduction ASTM allows for records that can be defined by the manufacturer to transmit
data not found in other records. These are the Manufacturer Specific records.
The main use of these records is the LSM. Refer to host manual for details.
Disabling These records are disabled by default starting with version 03-08, data disk 14.
records It is recommended that the host keep them disabled.
The following messages can be used to enable or disable the transmission of

the records. The 2010 must be in standby.
Disable Transmission Enable Transmission

H|\^& H|\^&
M|1|IC^BMÊ1^1| | | | | |No M|1|ICQ^BMÊ1^1
L|1 L|1
Record types The table below lists the Manufacturer Specific records used by the 2010.
Record Description
Action Confirmation Confirmation of processing actions
Action Request Request for instrument action
Calibrator Parameters Calibrator parameter definition
Calibration Request Request for calibration
Diluent Parameters Diluent parameter definition
Instrument Configuration Instrument specific configuration
Instrument Status General status information
Log File Transfer of message information
Processing Message Fast warnings and system events
Control Parameters Control parameter definition
Result Context Data on reagent lot used for
measurement
Raw Result Transfer of raw results
Service Data Instrument specific service data
Sample Status Sample specific status
Test Application Roche accessible part of application
Test Conditions User accessible part of application
Substance Data General substance information

Continued
Transmission Packets
Introduction The 2010 and host use packets to communicate. This section provides details
on the structure and use of these packets.
General notes • Messages are transmitted in one or more packets dependent on size.
• Most host vendors transmit one record per packet.
• Each packet has the same general format.
• Packet length is a maximum of 247 bytes.
• There are 7 bytes of delimiters, checksum and identifiers.
• There is a maximum of 240 data byes.
Packet format The format below is a general format for all frames.
Data Frame Data Data End Checksum End

Start Number Code
STX 0-7 …. ETX or ETB CSH CSL CR LF
1 1 240 max. 1 2 2 = 247 max.
Data Start Each packet begins with an STX (ASCII 02).
Frame Number Each packet has a frame number from zero to seven for error recovery.
Packets within one complete message are numbered starting with 1 and going
to 7 then continuing with 0, 1 etc.
Data This portion of the packet is dependent on the record type. See specific
format sections for details.
Data End Each packet ends with an ETX (ASCII 03) or ETB (ASCII 23). The end packet
will always have a data end of ETX and the remaining packets will have a data
end of ETB.

Continued
Transmission Packets, Continued
Checksum Each packet has a checksum specific for the data in that packet. See the
Checksum section for calculation.
End Code All packets terminate with CR (carriage return) and LF (line feed).
Packet example The example below shows the breakdown of a packet.
Start of End of
Text Data Text End Code
[STX]1H|\^&| | |ASTM-Host[CR][ETX]59[CR][LF]
Frame Number Checksum
Packet rules The following general rules apply to all packets.

1. Field size is variable.
2. Delimiters for empty fields should be included to ensure proper counting
of fields.
3. Delimiters do not need to be included for trailing null fields.
4. Null values do not overwrite existing data.
5. A pair of double quotes (“ “) with delete a field’s contents.
6. Valid characters include ASCII characters 32-126 excluding those used as
delimiter characters, ASCII 7, 9, 11, 12, and 128-254.

Continued
Protocol
Introduction This section reviews the protocol used by the 2010 to transmit messages. It
summarizes how the 2010 implements the ASTM low level protocol.
Protocol rules The following are general rules of the 2010 protocol.
1. Information flows in one direction at a time.
2. Either the host or 2010 may initiate communications.
3. Only one device at a time can be a receiver.
4. Only one device at a time can be a sender.
5. When data is not being transferred, both devices are considered to be idle.
6. When idle, all but an ENQ is ignored.
Control packets Control packets consist of control characters used to control the flow of
information between the 2010 and host. The table below details the packets.
Control Packet Definition Description

ACK Acknowledgement Used to positively acknowledge
receipt of information
EOT End of Used to relinquish transmission line
Transmission
NAK Not Acknowledged Used to negatively acknowledge
receipt of information
ENQ Inquiry Used to bid for transmission line.

Continued
Protocol, Continued
Phases To ensure proper coordination of message transmission, four distinct phases

are recognized in the 2010 protocol. The drawing below shows how these
phases are used.
Establishment Phase Idle Phase

• Control of the line is • Neither side is talking
established by side wanting to
• Phones are hung up
be sender
• Pickup phone and call
someone
Termination Phase
• Control of the line is
relinquished by sender
Transfer Phase
• Data is transferred by sender • Say good-bye and hang up the
to receiver phone
• Talk with person you called

Continued
Protocol, Continued
Establishment In the Establishment phase the device wishing to be sender will send an ENQ
phase letting the other device know it wants control of the communication line.
Receiver responds with ACK (hello)

• Establishment phase is complete and Transfer phase is entered.
Receiver responds with NAK (answering machine)

• Receiving side answers but can not talk
• The 2010 waits 10 seconds and resends the ENQ.
Receiver does not respond (ringing)

• Sender should wait 15 seconds and send an EOT to enter the Termination
phase.
Receiver responds with ENQ (busy signal)

• If there is contention for the line the 2010 has priority.
• The 2010 will wait for 1 second after contention and send the ENQ again.
The host must respond with an ACK or NAK.
• The host must wait no shorter than 20 seconds after a contention before
sending their ENQ again.
Receiver sends other than ACK, NAK or ENQ (wrong number)

• The 2010 waits 10 seconds and resends the ENQ.

Continued
Protocol, Continued
Transfer phase Records are transmitted by the sender in the Transfer phase.
Receiver responds with ACK (yes)

• Frame is considered accepted.
• Next frame is sent.
Receiver responds with EOT (goodbye)

• Frame is considered accepted.
• Receiver is requesting control of the line with the EOT so the sender
should give up control of the line as soon as possible by sending an EOT
and entering the Termination phase.
Receiver responds with NAK (no)

• Frame is considered not accepted.
• Sender should send the frame again.
Receiver does not respond (on hold)

• Sender waits 15 seconds then enters Termination phase by sending EOT.
Receiver sends other than NAK, EOT or ACK (static)

• Frame is considered not accepted.
• Sender should send the frame again until the retry limit of six is reached.
• Once retry limit is reached, sender should enter Termination phase by
sending an EOT.
Host does not complete sending of a frame (disconnected)

• If reception of a frame or an EOT is not received within 30 seconds after
the previous frame is acknowledged (with ACK or NAK), the 2010 will
timeout and change to the idle state.
Termination Control of the line is relinquished by the sender in the Termination phase and
phase both devices return to the idle state.
To enter the Termination phase, the sender sends an EOT. There is no

response from the receiver.

Continued
Protocol, Continued
Idle phase In the Idle phase, nobody is communicating.
Phase diagram The diagram below further defines the four phases.
Idle Establishment Transfer Phase Termination Idle

Phase Phase Phase Phase
Sender ENQ Data 1 Data n EOT
Receiver ACK ACK ACK
Timing This table provides the times that are used by the sender and receiver and any
actions that may occur in response to a time out.
Phase Who Timer Starts Timer Stops Time Out Reaction

Establishment Sender Transmission of ENQ Reply of ACK, NAK, 15 s Sender enters
ENQ Termination phase
Contention ENQ from analyzer 20 s Host enters Idle
(Host Timer) phase and
transmits ENQ
Contention After time out 1s Analyzer
(Analyzer Timer) retransmits ENQ
Transfer Receiver After sending of last Complete reception of 30 s Receiver enters
ACK valid frame or EOT Idle phase
Sender After transmission of Any reply of receiver 15 s Sender enters
last character of frame Termination phase
Triggering The following events trigger host interface activity.

events
Activity Event
Test Order Message • Sample scanning after start is pressed
Results Message • Automatic output of results is generated
• DOC key on Results screen is pressed
• 2010 power switched on

Continued
Test Selecting
Introduction The 2010 can receive test selections from the host in response to a query or
prior to a sample being identified by the 2010. This section describes both
methods.
Query mode In the query mode, test selections are sent in response to a query from the
2010. The 2010 will send a query for the sample after the sample is identified.
This requires START to be pressed. Sample scan will not initiate
communications with the host. Requests are only sent for samples without
test selections assigned at the 2010.
Initiating test Use the following steps to initiate a test selection query from the 2010.
selection query
Step Action
1 Load samples on the sample disk or in sample racks.
2 Press START.

Continued
Test Selecting, Continued
Query example The following data shows how the host and 2010 interact in query mode. The
first box shows the query from the 2010 for test selections and the second box
shows the download of test selections from the host in response to the query.
Message
E2010[ENQ] Establishment Phase
Header HOST[ACK]
Record E2010[STX]1H|\^&| | | | | | | | | |P| |[CR][ETX]05[CR][LF]
HOST[ACK]
Transfer Phase
Request E2010[STX]2Q|1|^000083^135^0^1^^SAMPLE^NOR
Information MAL| |ALL| | | | | | | |O[CR][ETX]FE[CR][LF]
Record HOST[ACK]
Message E2010[STX]3L|1[CR][ETX]3C[CR][LF]
Terminator HOST[ACK]
Record E2010[EOT] Termination Phase
Message
HOST[ENQ]
E2010[ACK] Establishment Phase
Header
Record HOST[STX]1H|\^&| | |ASTM-Host[CR][ETX]59[CR][LF]
E2010[ACK]
HOST[STX]2P|1[CR][ETX]3F[CR][LF]
Transfer Phase
Patient E2010[ACK]
Record HOST[STX]3O|1|000083|135^0^1^^SAMPLE^NORMAL
\^^^10^0\^^^150^0|R| | | | | |N| | | | | | | | | | | | | |Q[CR]
[ETX]F9[CR][LF]
Message HOST[STX]4L|1[CR][ETX]3D[CR][LF]
Terminator E2010[ACK]
Record HOST[EOT] Termination Phase

Continued
Test Selecting, Continued
Unrequested In the unrequested mode, test selections are sent when the host is ready to
send them. Test selections are sent before a sample is identified. When the
2010 identifies the sample, it will run what is assigned at the instrument
instead of sending a query.
Unrequested The following data shows how the host and 2010 interact in unrequested
example mode. The box shows the test selection download from the host. Remember
that there is no query from the 2010.
Message
HOST[ENQ]
E2010[ACK] Establishment Phase
Header
Record HOST[STX]1H|\^&| | |ASTM-Host[CR][ETX]59[CR][LF]
E2010[ACK]
HOST[STX]2P|1[CR][ETX]3F[CR][LF]
Transfer Phase
Patient E2010[ACK]
Record HOST[STX]3O|1|000083|135^0^1^^SAMPLE^NORMAL
\^^^10^0\^^^150^0|R| | | | | |N| | | | | | | | | | | | | |Q[CR]
[ETX]F9[CR][LF]
Message HOST[STX]4L|1[CR][ETX]3D[CR][LF]
Terminator E2010[ACK]
Record HOST[EOT] Termination Phase

Continued
Result Transmission
Introduction Result transmission can be accomplished automatically, on initiation by the

operator or in response to a query from the host. This section describes all
three methods.
Automatic In automatic mode, results for a sample are sent as soon as all results for the
sample are completed.
Document Options must be set to Print/Upload or Upload. Automatic

Options must be set to Automatic On. See Upload options section.
Manual The operator can initiate transmission of results from the 2010. All results
can be sent or just one sample’s.
Document Options must be set to Print/Upload or Upload. Automatic

Options can be set to Automatic On or Automatic Off. If set to Automatic
On then the results are being sent for a second time. If set to Automatic Off
then results are being sent for first time. See Upload options section.
Use the following steps to initiate manual transmission of results.
Upload All Results Upload One Sample’s Results

Step Action Step Action
1 Press Results tab. 1 Press Results tab.
2 Press DOC button. 2 Enter sample’s ID.
3 Select appropriate options 3 Press DOC button.

Continued
Result Transmission, Continued
Query The host can request results for a specific sample from the 2010 by sending a
Request Information record. The 2010 will send the results at the next
available time.
Result example No matter which method is used, automatic, manual or query, the
transmission of the result looks the same.
The following data shows how the host and 2010 interact when results are
being sent to the host from the 2010.
E2010[ENQ]
Message HOST[ACK] Establishment Phase
Header
E2010[STX]1H|\^&| | | | | | | | | |P| |[CR][ETX]05[CR][LF]
Record
HOST[ACK]
E2010[STX]2P|1| | | | | | | | | | | | | | | | | | | | | | | | | |
Transfer Phase
Patient
Record | | | |[CR][ETX]3B[CR][LF]
HOST[ACK]
E2010[STX]3O|1|000083|135^0^1^^SAMPLE^NOR
Order MAL|ALL|R|19980403090614| | | | |X| | | | | | | | |
Record
| | | | |O| | | | |CR][ETX]79[CR][LF]
HOST[ACK]
E2010[STX]4R|1|^^^10^0|2.73|ulU/ml|0.270^4.20|N| |F| |
|19980403090641|19980403092503|
Result [CR][ETX]B7[CR][LF]
Records HOST[ACK]
Transfer Phase
E2010[STX]5R|2|^^^150^0|7.43|ulU/ml|0.110^198.0|N| |
F| | |19980403090723|19980403092545|
[CR][ETX]24[CR][LF]
HOST[ACK]
Message E2010[STX]6L|1[CR][ETX]3F[CR][LF]
Terminator HOST[ACK]
Record E2010[EOT] Termination Phase

Continued
Workflow
Introduction The 2010 works with a combination of query and unrequested test selecting.
Implementation is not based upon switch settings. This section describes the
workflow of the 2010 analyzer in regard to the host interface.
Diagram This diagram gives a simple picture of the 2010 workflow.
STEP 2
If test selections are available at
the 2010, these are run. Step 3
If no test selections are
STEP 1 found, a query is sent to the
Sample is placed on analyzer host, else go to Step 5.
and barcode is read.
Step 5
Sample is processed.
Step 4
The host responds with
Step 6 appropriate test selections.
Results are
transmitted to host.
Details This table gives more details on the 2010 workflow.
Step Action
1 The sample is placed on the analyzer and the barcode is read.
2 If test selections are available for this sample, they are used.
3 If test selections are not available, a query is sent to the host.
Note: If no response or test selections are received from the host,

the 2010 will send a second query for the sample. If the host sends
the test selections in response to the second query, the sample will
be run. If no response is received, the sample is skipped. Because
of the additional cycle time the second query requires, a rack
system will skip remaining samples in the rack and start the query
process again at the next rack. On a disk system, the second query
forces the 2010 to skip one or two samples before sending the next
query.
4 The host responds with the test selections for the sample.
5 The sample is processed.
6 The results are transmitted to the host, dependent upon the
Document Options and Automatic Options selected.
Sample scan Be aware that pressing sample scan does not initiate communications with the
host. This is only done after start is pressed.

Continued
Checksum
Introduction The 2010 uses a standard checksum calculation. This section provides an
example and the general rules about the 2010 checksum calculation.
Calculation The table below shows the standard checksum calculation steps.
Step Action
1 Add decimal values of data from frame number to ETX.
2 Take sum from Step 1 modulo 256.
3 Convert value from Step 2 to hexadecimal.
Note: The checksum is used on messages only. Control packets do not use a
checksum.
Example STX 1 H | \ ^ & CR ETX CSH CSL CR LF
Step Action Example

1 Add decimal 49 + 72 + 124 + 92 + 94 + 38 + 13 + 03 = 485
values of data.
2 Take sum from 1
Step 1 modulo 256 485
256. -256
229
3 Convert value 14
from Step 2 to 16 229
hexadecimal. -224
5
Checksum 1416 516 = E 5
Note: Valid values are 0-9 = 0-9 and A-F = 10-15.

Continued
Host Port
Introduction This section provides details on the 2010 host port.
Location The 2010 has a standard 9 pin male connector on the left-hand side of the
analyzer as shown in the picture below. Older 2010’s may have female
connectors.
Caution! Turn off the 2010 at the circuit breaker prior to connecting or disconnecting
the host cable. If not, damage can occur to the 2010.
Pin Only the following pins should be connected.

configuration
2010 End of Cable Host End of Cable

2 Transmit
3 Receive
5 Ground
7-8 Jumpered
The Elecsys 2010 Host Interface Manual states that the 2010 does not have to
be jumpered. We have found that things work better if the 2010 end of the
cable is indeed jumpered as shown above.

Continued
Troubleshooting
Introduction This section describes what troubleshooting tools are available on the 2010
and provides troubleshooting tips including details on interface alarms.
Loop back test There is not a loop back test on the 2010.
Communication There is not a communication log on the 2010.

log
Flowchart This flowchart shows a basic troubleshooting process for the 2010 interface.
Receive call that host
is not working
Has it Test
No Yes Results Yes No
worked selections Error
getting to getting to
before? messages?
2010? host?
Yes No No Yes
Focus on Yes Has Results Yes See

anything Sync = No
area getting to alarm
changed? OFF?
changed host? details
No No
Yes
No Are the Enter Turn

Enter Are the
correct parameters correct parameters Sync
settings right? settings right? OFF
No
Yes Yes
Reconnect No Is cable Fix Are

cable Get trace and forward
cable connected pin-outs
pin-outs to Interface Champion
properly right? Yes No correct? Yes or Systems Support

Continued
Troubleshooting, Continued
Alarm codes There are twelve different host interface alarms on the 2010. The table below
further defines the codes and provides possible solutions.
Alarm # Definition Interpretation Possible Causes

44-01-01 Interface 2010 resent a message • Host cable not
retransmission because previous connected
occurred transmission was not • Incorrect parameters.
successful
• Host cable not pinned
correctly
• Host not following
protocol
44-01-02 Interface 2010 was sending a • Host cable
communication message and disconnected
aborted (sending) communications • 2010 had other
stopped priority
• contention for line
44-01-03 Interface 2010 was receiving a • Host cable
communication message and disconnected
aborted (receiving) communications • Host stopped
stopped transmitting
44-01-04 Interface 2010 has tried • Host cable not
retransmission failed unsuccessfully to send a connected
previous message • Incorrect parameters
correctly
protocol
44-01-05 Interface timeout 2010 has tried • Host cable not
(sending) unsuccessfully to send connected
same message a • Incorrect parameters
maximum number of
times • Host cable not pinned
correctly
protocol
44-01-06 Interface timeout 2010 did not receive a • Pins 7 and 8 are not
(sending) response from the host jumpered on the 2010
after sending a message side of the cable
• Host did not send
acknowledgement

Continued
Troubleshooting, Continued
Alarm codes (continued)
Alarm # Definition Interpretation Possible Causes

44-01-07 Interface timeout 2010 did not received • Pins 7 and 8 are not
(receiving) full message from host jumpered on the 2010
in required time side of the cable
• Host did not send
acknowledgement
44-01-08 Interface format error 2010 received a • No Terminator record
message that was • Header record is not
incorrectly formatted first
• Invalid or undefined
record
• Record content
incorrect
• Message structure
incorrect
44-01-09 Interface acceptance 2010 was unable to • Host cable not
error enter information connected
received from host into
• Incorrect parameters
instrument database
• Database full
44-01-10 Interface device error 2010 hardware problem • Host cable not
connected
correctly
protocol
• 2010 hardware
problem
44-01-11 Interface application 2010 software problem • Host cable not
error connected
correctly
protocol
• Reboot 2010
44-01-12 Interface off-line 2010 does not detect a • Upload or
host connection Print/Upload setting is
on and
Communications setting
is off

Continued
Communication Examples
Introduction This section shows examples of following communications.

• Test selection request from 2010.
• Test selection download from host.
• Result upload from 2010.
Refer to 2010 Host Interface document for more examples.
Test selection This is an example of a message transmission in which the 2010 has read a
request example sample’s barcode and sent a request for test selections to the host.
Message E2010 [ENQ]

Header HOST [ACK]
Record
E2010 [STX]1H|\^&| | | | | | | | | |P| |[CR][ETX]05[CR][LF]
HOST [ACK]
Request E2010 [STX]2Q|1|^000083^135^0^1^^SAMPLE^
Information NORMAL| |ALL| | | | | | | |O[CR][ETX]FE[CR][LF]
Record HOST [ACK]
Message E2010 [STX]3L|1[CR][ETX]3C[CR][LF]
Terminator HOST [ACK]
Record
E2010 [EOT]

Continued
Communication Examples, Continued
Test selection This is an example of a message transmission in which the host is sending test
download selections to the 2010 for a specific sample.
example
Message HOST [ENQ]

Header E2010 [ACK]
Record
HOST [STX]1H|\^&| | |ASTM-Host[CR][ETX]59[CR][LF]
E2010 [ACK]
Patient HOST [STX]2P|1[CR][ETX]3F[CR][LF]
Record E2010 [ACK]
Order HOST [STX]3O|1|000083|
Record 135^0^1^^SAMPLE^NORMAL|^^^10^0\^^^150
^0|R| | | | | |N| | | | | | | | | | | | |
|Q[CR][ETX]F9[CR][LF]
E2010 [ACK]
Message HOST [STX]4L|1[CR][ETX]3D[CR][LF]
Terminator E2010 [ACK]
Record
HOST [EOT]

Continued
Sample result This is an example of a message transmission in which the 2010 is sending
upload example results to the host for a specific sample.
Message E2010 [ENQ]

Header HOST [ACK]
Record
HOST [ACK]
Patient E2010 [STX]2P|1| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Record |[CR][ETX]3B[CR][LF]
HOST [ACK]
Order E2010 [STX]3O|1|000083|135^0^1^^SAMPLE^
Record NORMAL|ALL|R |19980403090614| | | | |X| | | | | | | | |
| | | | |O| | | | |[CR][ETX]79[CR][LF]
HOST [ACK]
Result E2010 [STX]4R|1|^^^10^0| 2.73|ulU/ml|0.270^4.20|N| |F|
Records | |19980403090641|19980403092503|[CR][ETX]
B7[CR][LF]
HOST [ACK]
E2010 [STX]5R|2|^^^150^0|7.43|uIU/ml|0.110^198.0|
N| |F| | |19980403090723|19980403092545|
[CR][ETX]24[CR][LF]
HOST [ACK]
Message E2010 [STX]6L|1[CR][ETX]3F[CR][LF]
Record
E2010 [EOT]

Continued
Control result This is an example of a message transmission in which the 2010 is sending
upload example control results to the host.
Message E2010 [ENQ]

Header HOST [ACK]
Record
HOST [ACK]
Patient E2010 [STX]2P|1| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Record |[CR][ETX]3B[CR][LF]
HOST [ACK]
Order E2010 [STX]3O|1|PCàTSH|138^0^4^^CONTROL^
Record NORMAL|ALL|R|19980403091021| | | | |X\Q| | | | | | |
| | | | | | |O| | | | |[CR][ETX]FB[CR][LF]
HOST [ACK]
Result E2010 [STX]4R|1|^^^10^^0|0.265|uIU/ml|0.168^
Records 0.312|N||F| | |19980403091053|19980403092915|
[CR][ETX]23[CR][LF]
HOST [ACK]
Message E2010 [STX]5L|1[CR][ETX]3E[CR][LF]
Record
E2010 [EOT]

Elecsys 2010 Host Interface Review – Advanced
Purpose This document is to be used as a review of the Elecsys 2010 host interface,
advanced level training. Answers can be found in the next section. Send
completed test records, including completed Training Acknowledgement
form, to the TSS Trainer.
Questions Circle best answer.
1. A Comment record can follow which record?

a) Result Record
b) Message Terminator Record
c) Any record
2. The host must echo what information from the Request Information
record when sending test selections in response to a query?
a) Patient information
b) Sample information
c) Test information
3. What are the four phases used in the ASTM protocol?

a) Idle/Query/Transfer/Terminate
b) Idle/Query/Send/Termination
c) Idle/Establishment/Transfer/Termination
4. What record is used to transmit data alarms and messages?

a) Order record
b) Comment record
c) Results record
5. What is the only field recognized in the Patient Information record?

a) Patient ID
b) Sample ID
c) Patient Name
6. Which control packet is used to bid for the transmission line?

a) ACK
b) EOT
c) ENQ
Revision: 1.0 Page: 1 of 5

Elecsys 2010 Host Interface Review – Advanced, Continued
Questions (continued)
7. What is a group of records?
a) Packet
b) Message
c) Frame
8. What two items make up the test number field?

a) test number and test name
b) test number and generation
c) test name and generation
9. Which record defines the delimiters?

a) Message Header record
b) Message Terminator record
c) Information record
10. A Test Selection Download message contains which records?

a) Message Header Record/Order Record/Message Terminator Record
b) Message Header Record/Patient Information Record/
Order Record/Message Terminator Record
c) Message Header Record/Request Information Record/Patient
Information Record/Order Record/Message Terminator Record
11. Which is not one of the rules regarding packets?

a) Field size is variable
b) Null values do not overwrite existing data
c) Delimiters need to be included for trailing null fields
12. The Establishment phase is similar to what?

a) Talking with someone on the phone
b) Calling someone on the phone
c) Saying good-bye to someone and hanging up the phone
13. The 2010 acquires test selections in what order?

a) identifies sample, looks internally, queries host
b) identifies sample, queries host, look internally
c) identifies sample, queries host, skips sample

(continued)
14. What three methods can be used to get results from the 2010 to the host?
a) Automatic, Manual, Unrequested
b) Automatic, Manual, Query
c) Automatic, Print/Upload, Query
15. In Automatic results transmissions, results for a sample are sent when all
of the results are available for that sample. What settings are required?
a) Automatic ON and Print/Upload or Upload
b) Automatic OFF and Print/Upload or Upload
c) Automatic ON and Print/Upload or Upload or Printout
16. In manual results transmission, results for a sample are sent when
requested by the operator. What settings are required?
a) Automatic ON and Print/Upload or Upload
b) Automatic OFF and Print/Upload or Upload
c) Automatic ON and Print/Upload or Upload or Printout
17. When the 2010 sends an ENQ and the host responds with an ACK, what
is happening?
a) The 2010 has successfully relinquished control of the transmission
line and the idle phase has been entered
b) The 2010 has successfully transmitted a data packet
c) The 2010 has successfully bid for control of the transmission line and
the transfer phase has been entered
18. What pins are jumpered on a 2010 host cable?

a) 7 and 8
b) 2 and 3
c) No pins are jumpered
19. Who can initiate communications?

a) 2010 only
b) Host only
c) 2010 or Host
20. Which is used as a default field delimiter?

a) ^
b) |
c) \

Answers 1. A
2. B
3. C
4. B
5. A
6. C
7. B
8. B
9. A
10. B
11. C
12. B
13. A
14. B
15. A
16. B
17. C
18. A
19. C
20. B
Published by: S. Pearson Approved by:

Date Printed: 11/06/00 C. Henderson
Black or Blank copy number indicates uncontrolled copy. Controlled Copy No.:
Roche Diagnostics confidential. Copy with care.

Training Acknowledgement
I acknowledge that I have received, read, completed and understood the Advanced Level training
materials for the Elecsys 2010.
I understand that the execution and return of this acknowledgement is an official record that I
have successfully completed this training and that this record will become a permanent part of
my training record.
Name (please print): _______________________________________________
Your Signature: ___________________________________________________
Employee Number: ________________________________________________
Date: ___________________________________________________________


Roche Elysis Astm Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Roche Elysis Astm Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

2010 Host Interface Training Guide – Advanced Level

Purpose of guide This guide is

Continued on next page

Published by: S. Pearson Approved by:

Revision: 1.0 Page 1 of 69

Guide contents This guide covers the following topics

Topic See Page

Revision: 1.0 Page 2 of 69

Note: To make changes to the parameter settings, communications must be

Continued on next page

Revision: 1.0 Page 3 of 69

Communi- When the communication button is pressed, a ‘Confirmation’ pop-up

Data bits Data bits can be set to 7 or 8.

Stop bits Stop bits can be configured at 1 or 2.

Parity Parity can be selected as none, odd or even.

Sync Synchronization can be set to on or off.

If synchronization is turned on, hardware handshaking (XON/XOFF) will be

Continued on next page

Revision: 1.0 Page 4 of 69

Options for uploading are determined by the Document and Automatic

Document Options Automatic Options Results

Revision: 1.0 Page 5 of 69

Introduction ASTM (American Society for Testing and Materials) is an organization of

A group of LIS companies, lab equipment manufacturers and lab equipment

Continued on next page

Revision: 1.0 Page 6 of 69

describes patient and describes one aspect of one specific attribute of

1H|\^&| | | | | | | | | | P| | [CR] Record

2Q|1|^000083^135^0^1^^SAMPLE^NORMAL| |ALL| | | | | | | |O[CR]

Continued on next page

Revision: 1.0 Page 7 of 69

Level ID Record Direction Contents

Continued on next page

Revision: 1.0 Page 8 of 69

Message Records Used

Continued on next page

Revision: 1.0 Page 9 of 69

Message rules The follow rules apply to the transmission of a message.

(Level 0) MESSAGE HEADER

Continued on next page

Revision: 1.0 Page 10 of 69

Delimiter Character Description Use

Revision: 1.0 Page 11 of 69

The Message Header record is always a level 0 record.

Field Content Comments

Continued on next page

Revision: 1.0 Page 12 of 69

Continued on next page

Revision: 1.0 Page 13 of 69

… Field Field Field Field Field Field

… Field Processing Field Field Record

… Data End Checksum End Code

Field Content Description

Continued on next page

Revision: 1.0 Page 14 of 69

Data Frame Record Delimiter Field Field

… Field Sender Record Data End

Field Content Description

Revision: 1.0 Page 15 of 69

The Message Terminator record is always a level 0 record.

Field Content Comments

Continued on next page

Revision: 1.0 Page 16 of 69