Access 2
Access 2
Access 2
P/N 387264H
4/10
Printed in U.S.A.
© 2010 Beckman Coulter, Inc.
BECKMAN COULTER, INC. • BREA, CA 92821
Publication Each page of this UniCel DxI and Access 2 LIS Vendor Information
Notes document is identified with its revision and release date. For pages other
than the title page, revision information is located at the bottom of the page.
All pages in this manual are issued as revision P/N 387264H, release date
4/10.
From time to time, the documentation for the UniCel DxI Access
Immunoassay System and Access 2 Immunoassay System will need
to be updated. Beckman Coulter, Inc. will make every attempt to
distribute these updates to you in electronic format; however, that is
not always feasible. At times, you may receive these updates in paper
format, which must be used in conjunction with the electronic
documentation. For example, you may receive a paper copy of a
revised LIS Vendor Information page. This change will not be
available immediately in the LIS Vendor Information that is
available on CD.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2 Low Level Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
4 Sample Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
A ASCII Character Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
B Test Codes Used by the Instrument . . . . . . . . . . . . . . . . . . . . .51
C Using Japanese and Simplified Chinese Characters . . . . . .55
D EIA-232 Cables, Connectors, and Adapters . . . . . . . . . . . . .56
Preface
This document is intended as a guide to laboratory information system (LIS) vendors
developing interfaces that communicate with the UniCel DxI Access Immunoassay
System or the Access 2 Immunoassay System. In this document, the term, instrument,
refers to either of these systems, except where noted. Provide this document to your
LIS vendor prior to interfacing the instrument and the laboratory computer.
NOTES
• This document is not applicable to Access 2 Immunoassay Systems that are
parts of SYNCHRON LXi 725 or UniCel DxC 600i Synchron Access Clinical
Systems.
• This document is not applicable to UniCel DxI Access Immunoassay Systems
that are parts of UniCel DxC Synchron Access Clinical System Integrated
Workstations.
Overview
The LIS feature of the instrument software allows a laboratory computer to
communicate with the instrument through a standard serial connection. The LIS
interface specification consists of two major functional groups:
• Low level transfer protocol
• Message format definitions
The low level transfer protocol specified by ASTM E1381 includes the methods of
physical interconnection of devices, characteristics and format of data, and methods
of opening and closing communications sessions.
The message format definitions specified by ASTM E1394 define the format of the
data records to be passed between the instrument and the laboratory computer.
Message data is sent in delimited records, of which there are seven types. For
information on the record types and their contents, see the Record Field Descriptions
topic in Section 3: Message Format.
Definitions of The following table lists terms and definitions as they are used in this document.
Terms
Term Definition
<ETX> end of text (ASCII Decimal 3). Required at the end of each
record.
<LF> line feed (ASCII Decimal 10).
<NAK> negative acknowledge (ASCII Decimal 21).
<STX> start of text (ASCII Decimal 2).
[C1] The most significant hexadecimal digit of the checksum,
expressed as an ASCII character.
[C2] The least significant hexadecimal digit of the checksum,
expressed as an ASCII character.
[DATA] The data contents of the record.
[frame#] An ASCII numeric character ranging from 0 to 7. Frame
numbers begin at 1, and are incremented using modulo 8
arithmetic. When the frame number reaches 7, the
numbering starts over at 0.
Communications All framing required for transmission of data. This framing
Packet includes: <STX> [frame#] [DATA] [<ETB> or <ETX>]
[C1] [C2] <CR> <LF>.
Component Field A single data element or data elements which express a finer
aggregate or extension of data elements which precede it.
For example, a field called Name may have component
fields called Last, First, and Middle Initial. A component
field may not include Repeat delimiters.
Download The transmission of data from the laboratory computer to the
instrument.
Field A specific location within a record for a piece of
information, indicated by a field delimiter and position.
Frame A subdivision of a message, used to allow periodic
communication housekeeping such as error checks and
acknowledgement.
Instrument The UniCel DxI Access Immunoassay System or the
Access 2 Immunoassay System. Except as noted, both
systems behave identically with respect to the LIS interface.
Laboratory A computer that has been set up to communicate with one or
Computer more laboratory instruments, using the ASTM E1394 and
ASTM E1381 specifications.
Sender The system that has a message to send and initiates the
transmission process between two devices. The sender in
this document is either the instrument or the laboratory
computer.
Session A complete unit of communication activity consisting of the
establishment phase, the transfer phase, and the termination
phase. For more information, see the Data Link Layer topic
in Section 2: Low Level Transfer Protocol.
Test A determination of a single analyte or a combination of
values from other determinations or observations from
which a variable or gradable result is derived.
Test Order, or The sample and test information downloaded from the LIS,
Test Request or manually entered by an operator on the Test Request
screen.
Upload The transmission of data from the instrument to the
laboratory computer.
The data link layer is responsible for establishing a connection between the sender
and receiver, initiating the transfer of data frames, and termination of the connection.
In the LIS interface specification, the data link layer also handles error checking
through the use of checksum characters.
Physical Layer All communications are expected to use the EIA-232 asynchronous serial
communication protocol, based on the Electronics Industries Association (EIA)
standard EIA-232-D. The instrument is configured as Data Terminal Equipment
(DTE).
The instrument is connected to the laboratory computer using a DB-9 male connector
on the back of the instrument external PC. Because most computer ports are
configured for DTE operation, a null modem cable is typically required for
connecting the laboratory computer to the instrument. For details about the pin
assignments for the instrument LIS port, and the signals that must be provided on the
corresponding pins of the laboratory computer cable, see Appendix D: EIA-232
Cables, Connectors, and Adapters.
The instrument serial interface is configured for 1 start bit, 8 data bits, no parity bit,
and 1 stop bit. This configuration is fixed in accordance with ASTM standard E1381,
and cannot be changed. The baud rate is set by default to 9600, but the interface can
be configured for 1200, 2400, 4800, 9600, 14400, or 19200 baud operation.
Data Link The data link layer includes procedures for link connection and release, delimiting
Layer and synchronism, sequential control, error detection, and error recovery as specified
in ASTM E1381 (Section 6, Data Link Layer). There are three distinct phases in
transferring information between the instrument and the laboratory computer. These
phases assure that the actions of the sender and receiver are coordinated. The three
phases are establishment, transfer, and termination. Together, these three phases
constitute a session.
The data link layer uses a character-based protocol to send messages between directly
connected systems. The data link mode of operation is one-way transfer of
information with alternate supervision. Information flows in one direction at a time.
Replies occur after information is sent, never at the same time. It is a simplex
stop-and-wait protocol. At times the two systems are actively operating to transfer
information. The remainder of the time the data link is in a neutral state.
Establishment Phase
The establishment phase determines the direction of information flow and prepares
the receiver to accept information. A system which does not have information to send
normally monitors the data link to detect the establishment phase. It acts as a receiver,
waiting for the other system to initiate a message exchange.
The system with information to send initiates the establishment phase. After the
sender determines that the data link is in a neutral state, it transmits the <ENQ>
transmission control character. The receiver ignores any character other than <ENQ>
while in the neutral state. The sender ignores any response to <ENQ> other than
<ACK>, <NAK>, or <ENQ>.
Transfer Phase
During the transfer phase, the sender transmits records to the receiver. The transfer
phase continues until all records are sent. Records are sent in frames. Each frame
contains a maximum of 247 characters, including seven characters of frame overhead.
Records with content of more than 240 characters are divided between two or more
frames. Multiple records cannot be combined in a single frame. Every record must
begin in a new frame.
There are two types of frames: intermediate and end. Intermediate frames terminate
with the characters <ETB> [C1] [C2] <CR> <LF>. End frames terminate with the
characters <ETX> [C1] [C2] <CR> <LF>. A record containing 240 characters or less
is sent in a single end frame. Longer records are sent in intermediate frames with the
last part of the record sent in the end frame. A complete record frame has the
following format:
(The example shows a single, or end frame. An intermediate frame has <ETB> after
the [DATA], instead of <ETX>.)
Frame Number
The frame number permits the receiver to distinguish between new and retransmitted
frames. It is sent immediately after the <STX> character.
The frame number is an ASCII numeric character ranging from 0 to 7. Frame numbers
begin at 1 with the first frame of the transfer phase, and are incremented, using
modulo 8 arithmetic, for each new frame transmitted. When the frame number
reaches 7, the numbering starts over at 0.
The system expects the frame number to fit one of the following conditions:
If the frame number does not fit one of these conditions, the frame is considered
defective.
Checksum
The checksum permits the receiver to detect a frame that is defective due to a
transmission error. It is encoded as two characters, which are sent after the <ETB> or
<ETX> character. The checksum is computed by adding the binary values of
[frame#], the [DATA] characters, and the <ETB> or <ETX> character, keeping only
the least significant eight bits (modulo 256 arithmetic).
The 8-bit checksum is expressed in hexadecimal by two ASCII characters, [C1] and
[C2], of the range [0-9, A-F]. [C1] represents the most significant four bits of the
checksum, and [C2] represents the least significant four bits.
Acknowledgement
The receiver must acknowledge the receipt of each frame before the sender can
transmit the next frame. The receiver acknowledges a frame by sending one of three
characters:
• <ACK> signifies that the frame was received successfully and that the
receiver is ready to receive another frame.
• <NAK> signifies that the frame was not received successfully, and that the
receiver is ready to receive that frame again
• <EOT> signifies that the frame was received successfully and that the
receiver is ready to receive another frame. It is also a request for the sender to
stop transmitting.
The acknowledgement must be transmitted within the time-out period. (For more
information, see the Time-outs topic in this section).
Receiver Interrupts
The receiver interrupt is an <EOT> acknowledgement that requests that the sender
stop transmitting messages as soon as possible. If the sender ignores the <EOT> and
continues transmitting, the receiver must request the interrupt again after receiving the
next frame.
When the sender honors the interrupt request, it must enter the termination phase.
This gives the receiver an opportunity to enter the establishment phase and become
the sender. The original sender must not enter the establishment phase for at least 15
seconds or until the receiver has sent a message and returned the data link to the
neutral state.
Defective Frames
The receiver checks each frame for validity. A reply of <NAK> is transmitted for
invalid frames. The receiver ignores any characters occurring before the <STX> or
<EOT>, or after the end of block character <ETB> or <ETX> when checking the
frame. A frame is rejected when:
• Any character framing errors are detected
• The frame checksum does not match the checksum computed on the received
frame
• The frame number is not the same as the last accepted frame (or one number
higher, modulo 8)
Upon receiving a <NAK> or any character other than <ACK> or <EOT>, the sender
increments a retransmit counter and retransmits the frame with the same frame
number. If a single frame is sent six times without being accepted, the sender must
stop transmitting this message and enter the termination phase. This should be
extremely rare, but it provides a mechanism to escape from a condition where the
transfer phase cannot continue.
Termination Phase
The termination phase returns the data link to the neutral state. The sender transmits
the <EOT> transmission control character to notify the receiver that no more records
will be sent and that the data link has been returned to the neutral state. Upon
receiving <EOT> the receiver also regards the data link to be in a neutral state.
Time-outs
The sender and receiver both use timers to detect loss of coordination between them.
The following conditions are resolved by time-outs:
NOTE
Receivers that cannot process messages fast enough to keep up with a sender may
cause message buffer overflows in the sender. A sender can normally store at
least one complete message. Storage space for more than one outgoing message is
desirable but optional.
Restricted Characters
The low-level transfer protocol is designed for sending character based message text.
Restrictions are placed on which characters can be used in the message text. The
restrictions make it simpler for senders and receivers to recognize replies and frame
delimiters. Additional characters are restricted to avoid interfering with software
controls for devices such as multiplexers.
The <LF> character is not permitted in the [DATA] portion of the message text, and
must only be used as the last character of a frame. The following characters are
restricted, and must not appear in the [DATA] portion of the message frame: <SOH>,
<STX>, <ETX>, <EOT>, <ENQ>, <ACK>, <DLE>, <NAK>, <SYN>, <ETB>,
<LF>, <DC1>, <DC2>, <DC3>, and <DC4>.
Message Format
The message format used by the LIS interface conforms to the ASTM standard
E1394.
This section describes the record types, and the fields and delimiters that make up a
record (shown as [DATA] in the low-level transfer protocol).
Record The following topics identify the limitations and general considerations regarding
Content record content. For the acceptable values for each field, see the Record Field
Descriptions topic.
NOTE
When instruments are configured for the Japanese or Chinese languages,
additional considerations for record content apply. For information about using
Japanese or Chinese language characters, see Appendix C.
Allowed Characters
The message data sent to the instrument must be restricted to ASCII characters
32-126 (the standard printable keyboard characters) for proper operation of the
instrument software. Specific fields may further restrict allowed characters. Also see
Appendix A: ASCII Character Codes.
Language
All transmissions to and from the instrument must be in English, even if the user
interface is set to a language other than English.
Record Codes
The following codes are required for conformance to the ASTM standard:
Delimiters
The Message Header record defines the unique field, repeat, component, and escape
delimiters that are used in the message.
Care should be taken when assigning delimiters. Avoid using any character that is
likely to be contained in the record text. The recommended delimiters are shown in
Table 3-1. These delimiters are used in the examples throughout this document.
Field | 124
Repeat \ 92
Component ^ 94
Escape & 38
When a record field contains a character that is also defined as a delimiter, the
character must be preceded and followed by the Escape delimiter to prevent the parser
from interpreting the character as a delimiter.
Null Fields
Fields are identified by counting field delimiters from the beginning of the record. If
no data is provided for a field (a null field), the field delimiter must be included to
enable the parser to correctly identify subsequent fields. However, delimiters are not
required for contiguous null fields at the end of a record. When the parser encounters
the End of Record delimiter, any remaining fields are considered null. In this
document, null refers to an empty field, and not to the ASCII character <NUL>.
The laboratory computer can be programmed to send a null field for 1) an unknown
value, 2) a value that is ignored by the instrument, or 3) a value that matches the
instrument default value.
Record Field The ASTM E1394 specification defines nine record types, of which seven are used by
Descriptions the instrument:
• Message Header record
• Patient Information record
• Test Order record
• Result record
• Comment record
• Manufacturer Information record (not used by the instrument)
• Scientific record (not used by the instrument)
• Request Information record
• Message Terminator record
The following topics describe the fields in each record type and give examples of
complete messages of that type. For each record, a table shows the record identifier,
the delimiters for each field or component, an example, and the maximum length of
the field. The table also shows how the instrument supports that field when receiving
and sending messages:
• Required - Mandatory field which must not be null. The instrument must
include it when uploading messages, and will reject downloaded messages in
which it is null.
• Yes - Supported, but optional. The instrument will store the data received in
downloaded messages, and, if the data is available, will include it in uploaded
messages.
• Ignored - Not supported in downloaded messages. The field will be accepted
by the instrument, but not stored.
• No - Not supported for uploaded messages (not sent by the instrument).
Message The Message Header record is the first record of every message. It contains overhead
Header information such as sender and receiver IDs, and the date and time of the message,
Record and defines the delimiters to be used for all records in the message.
Examples
NOTE
Do not use the /, -, or * characters as delimiters. If they
are defined as delimiters, the system cannot recognize
test codes that contain these characters.
Field - Marks the beginning of a field. The vertical bar (|)
character is the recommended field delimiter.
Repeat - Used to indicate that the previous field is to be
repeated. Only certain fields, such as the Universal Test ID
in the Test Order record, allow repeat delimiters. The
number of repeat delimiters is restricted only by the 1024
character record size limit. The backslash (\) character is
the recommended repeat delimiter.
Component - Used to delimit components of a multi-part
field, such as Sender Name, which has a System ID
component. The circumflex (^) character is the
recommended component delimiter.
Patient The Patient Information record contains patient identification information and
Information demographic information, which is used by the instrument in range determination
Record calculations.
All Test Order records that follow are associated with this patient until a subsequent
patient record is encountered.
Examples
Typical Upload:
<STX>2P|1|098765678<CR><ETX>A3<CR><LF>
Typical Download:
<STX>2P|1|0987656789|||Smith^Tom^A^Jr.^Mr.||19631124|M|||||Jones
<CR><ETX>6E<CR><LF>
Minimal Download:
<STX>2P|1|<CR><ETX>BB<CR><LF>
Test Order The Test Order record contains information that uniquely identifies a sample, the list
Record of tests to be completed, the priority, and the type of action requested.
All Test Order records are associated with the preceding Patient Information record.
Result records that follow are associated with this Test Order record until a
subsequent Test Order record is encountered.
Examples
Typical Download:
<STX>3O|1|SPEC1234||^^^Ferritin|R||||||A||||Serum<CR><ETX>F8
<CR><LF>
Minimal Download:
<STX>3O|1|SPEC1234||^^^Ferritin<CR><ETX>0E<CR><LF>
Typical Upload:
<STX>3O|1|SPEC1234|^1^4|^^^Ferritin^2|||||||||||Serum||||||||||F
<CR><ETX>34<CR><LF>
Record Identifier The Test Order record is identified by the letter O in the
Record Identifier field. Case sensitive.
Sequence Number Begins with 1 and is incremented within the message for
each subsequent Test Order record. A new Patient
Information record resets the sequence number to 1.
Specimen ID Equivalent to the Sample ID on the instrument software.
Identifies the specimen independently of the instrument
rack ID and position. The maximum field length is 15
characters. The contents are case sensitive. Allowed
characters are 0-9, A-Z, a-z, +, /, -, *. Spaces and
punctuation are not allowed.
NOTE
A Specimen ID that matches a calibrator name (such
as AFPCal) will be rejected.
Instrument Only the second and third components of this field are
Specimen ID supported. The first component is ignored by the
instrument, and should be left blank by the laboratory
computer.
Rack Number and Sample Position are uploaded to the
laboratory computer but are ignored on downloads.
Rack Number - Numeric field containing the sample rack
number read by the internal bar code reader in the
instrument. Supported values are 1-9999.
Sample Position - Numeric field containing the position
of the sample in the rack. Supported values are:
• 1-4 for the UniCel DxI instrument
• 1-10 for the Access 2 instrument
Universal Test ID Only the fourth and fifth components of this field are used.
The first three components are ignored by the instrument,
and should be left blank by the laboratory computer.
The instrument supports repeat delimiters in this field. The
instrument may produce repeat delimiters in this field
when uploading Test Order records, to list each test code
for each Result record to follow for a specific sample
position.
Local Code: Test - Alphanumeric field containing the
test code for the instrument. The maximum field length is 8
characters. Test codes are not case sensitive. The hyphen
character (-) may be used. For a list of available test codes,
see Appendix B: Test Codes Used by the Instrument.
Local Code: Replicate - On uploads, the instrument
includes this component to indicate the test replicate
number. Replicate numbers are ignored on downloads. The
range of acceptable values is 1-99.
Priority The following test priority codes are accepted:
S STAT
R Routine
Although the instrument accepts up to nine characters, the
priority code is the first character in the field.
Code S gives a test order STAT priority.
Code R or a null field gives the order routine priority.
If any other code is used, the test order is rejected and an
error message is returned to the LIS.
Action Code The action to take for the test codes named in this record,
indicated by one of the following codes:
C Cancel the tests for the indicated sample. The
instrument removes the tests from the LIS workpool.
A Add the test to the indicated sample. If the sample
location is unknown on the instrument, add the sample
with the indicated test requests to the LIS workpool.
N New tests for the indicated sample. If tests are already
associated with the sample, the new tests are rejected.
If this field is null, it is received as an Add request.
Result Record The Result record contains information regarding a particular test that identifies the
result value and units, the demographic range information, the condition of the result
(normal or abnormal), and the date and time of the test.
All Result records are associated with the preceding Test Order record.
If a test result includes one or more flags, the flags are uploaded separately in a
Comment record immediately following the Result record containing the flagged
results.
The instrument can be configured to send results to the laboratory computer either
when each test is finished (LIS Send Mode is By Test), or when all of the tests on a
sample container are finished (LIS Send Mode is By Sample Container).
Examples
Typical Upload:
<STX>4R|1|^^^Ferritin^1|105.6|ng/ml||N||F||||20021231235959<CR>
<ETX>54<CR><LF>
Possible Upload:
<STX>3R|1|^^^TU^1|Cancelled|%Uptake||N||X||||20021231235959<CR>
<ETX>67<CR><LF>
Record Identifier The Result record is identified by the letter R in the Record
Identifier field. Case sensitive.
Sequence Number Begins with 1 and is incremented within the message for
each subsequent Result record. A new Test Order record
will reset the Result record Sequence Number to 1.
Universal Test ID Only the fourth and fifth components of this field are used.
Repeat delimiters are not used for this field in the Result
record.
Local Code: Test - Alphanumeric field containing the
test code for the instrument. The maximum field length is 8
characters. Not case sensitive. The hyphen character (-)
may be used. For a list of available test codes, see
Appendix B: Test Codes Used by the Instrument.
Local Code: Replicate - Numeric value that specifies the
replicate number for a particular assay. Supported values
of 1-99.
Data Measure- The test result is reported in the two components of this
ment and Value field.
Value - Alphanumeric test result. Other possible values are
Cancelled, N/A, and No Value. This field is empty if result
is fatally flagged.
Interpretation - This field indicates the interpretation of
the result value. The following codes are used: Reactive,
Non-React., Confirmed, Not Conf., Negative, Positive,
Equivocal.
Result Abnormal This field indicates the status of the result. The following
Flags codes are used:
L Below normal reference low limit. Indicates an
instrument ORL flag.
H Above normal reference high limit. Indicates an
instrument ORH flag.
LL Below panic low. Indicates an instrument CRL flag.
Comment The Comment record is uploaded immediately following a Result record for a result
Record that contains one or more flags.
When the instrument finds an error in a patient or test order record which will prevent
tests from being ordered, it uploads a Patient Information record, Test Order record
and Comment record containing an error message in an informational comment to the
laboratory computer.
If multiple Result records are uploaded in a message, the Comment record applies to
the Test Result record immediately preceding the Comment record.
Examples:
Typical Uploads:
<STX>4C|1|I|CEX;PEX|I<CR><ETX>42<CR><LF>
<STX>4C|1|I|Assay Not Enabled|G<CR><ETX>55<CR><LF>
NOTE
Multiple flags are delimited with semicolons.
LRH The result is above the upper limit of the LIS range.
LRL The result is below the lower limit of the LIS range.
ORH Result higher than normal reference range.
Comment Type Used to indicate type of comment. The following codes are
used:
G Generic/Free Text Comment (for error messages)
I Instrument Flag Comment (for test result flags)
End of Record Always the <CR> character.
Request The Request Information record is used to query the laboratory computer for test
Information order information for a specific specimen ID.
Record
Example
Message The Message Terminator record signals the end of the message.
Terminator
Example:
Record
Typical upload or download:
<STX>4L|1|F<CR><ETX>FF<CR><LF>
Manufacturer The Manufacturer Information record is ignored when received by the instrument, and
Information is not created or sent by the instrument.
Record
Scientific The Scientific record is ignored when received by the instrument, and is not created or
Record sent by the instrument.
Sample Messages
The following examples show messages transmitted between the instrument and the
laboratory computer.
H|\^&|||Host LIS|||||||P|1|20001010080000<CR>
P|1|AbelCindy<CR>
O|1|123456||^^^TSH|R||||||A||||Serum<CR>
P|2|32445|||Baker^Tom^M^S^Mr||19530101|M<CR>
O|1|123458||^^^TSH|R||||||A||||Serum<CR>
O|2|123458||^^^TSH|R||||||A||||Serum<CR>
L|1|F<CR>
In this example, the laboratory computer orders tests for two different patients.
The first patient is identified by the Patient ID of AbleCindy. One TSH test is ordered
on Sample ID 123456.
The second patient’s Patient ID is 32445, and his name, birth date, and sex are
included. Two TSH tests are ordered on Sample ID 123458. The tests are ordered in
separate records.
H|\^&|||Host LIS|||||||P|1|20001010080000<CR>
P|1|CasperJane|||Johnson^Joan||19580101|F<CR>
O|1|AABB1234||^^Ferritin\^^^Ferritin\^^^Theo|R||||||A||||Serum<CR>
O|2|AABB1235||^^^TSH|R||||||A||||Serum<CR>
L|1|F<CR>
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010131522<CR>
P|1|AbelCindy<CR>
O|1|123456|^9^1|^^^TSH^1|||||||||||Serum||||||||||F<CR>
R|1|^^^TSH^1|0.18|uIU/mL||N||F||||20001010113536<CR>
L|1|F<CR>
In this example, the instrument reports the results of the downloaded test order for
Patient ID AbleCindy. Sample ID 123456 was found in position 1 of sample rack 9.
The test result is 0.18 μIU/mL of TSH.
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010131522<CR>
P|1|23445<CR>
O|1|123458|^9^2|^^^TSH^1|||||||||||Serum||||||||||F<CR>
R|1|^^^TSH^1|0.03|uIU/mL||N||F||||20020131113612<CR>
O|2|123458|^9^2|^^^TSH^1|||||||||||Serum||||||||||F<CR>
R|2|^^^TSH^2|0.01|uIU/mL||N||F||||20020131113648<CR>
L|1|F<CR>
In this example, the instrument reports the results of the downloaded test order for
Patient ID 23445. Sample ID 123458 was found in position 2 of rack 9. There are two
results. In the first test, 0.03 μIU/mL of TSH was found. In the second test, 0.01
μIU/mL of TSH was found.
NOTE
The instrument in this example has the LIS Send Mode set to By Sample
Container. If the LIS Send Mode was set to By Result, each result would be
reported in a separate message.
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010131522<CR>
P|1|CasperJane<CR>
O|1|AABB1234|^9^3|^^^Theo^1\^^^Ferritin^1\^^^Ferritin^2|||||||||||Serum||||||||||F<CR>
R|1|^^^Theo^1|0.13|ug/mL||N|F||||20020131111100<CR>
C|1|I|PEX|I<CR>
R|2|^^^Ferritin^1|0.0|ng/mL||N||F||||20020131112300<CR>
R|3|^^^Ferritin^2|0.0|ng/mL||N||F||||20020131112336<CR>
L|1|F<CR>
In this example, the instrument reports the results of the downloaded test order for
Sample ID AABB1234, from Patient ID CasperJane. The Comment record included
after Result record number 1 indicates that the Theo reagent pack has expired (PEX
flag).
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010131522<CR>
P|1|CasperJane<CR>
O|1|AABB1235|^9^4|^^^TSH^1|||||||||||Serum||||||||||F<CR>
R|1|^^^TSH^1|0.02|uIU/mL||N||F||||20020131113636<CR>
L|1|F<CR>
In this example, the instrument reports the results of the downloaded test order for
Sample ID AABB1235, from Patient ID CasperJane.
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010115158<CR>
P|1|<CR>
O|1|47G|^1^3|^^^Folate^1\^^^Ferritin^1\^^^VitB12^1\^^^Rub-IgG^1|||||||||||Serum||||||||||F<CR>
R|1|^^^Folate^1|0.09|ng/mL||N||F||||20001010115045<CR>
R|2|^^^Ferritin^1|0.0|ng/mL||N||F||||20001010114745<CR>
R|3|^^^VitB12^1|00|pg/mL||N||F||||20001010115121<CR>
L|1|F<CR>
The instrument reports results for Sample ID 47G. In this example, the LIS Send
Mode on the instrument is set to By Sample Container, so all results for the sample
are sent in one message. One replicate each of Folate, Ferritin, VitB12, and Rub-IgG
was requested. The test was ordered at the instrument console, without a Patient ID.
Because of a fatal flag, no result was calculated for the Rub-IgG test, so no result is
sent to the laboratory computer. Only non-fatally flagged results are transmitted to the
laboratory computer.
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010085833<CR>
P|1|675DRC4<CR>
O|1|W3|^|^^^Theo|||||||||||Serum||||||||||X<CR>
C|1|I|Sample already exists|G<CR>
L|1|F<CR>
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010085834<CR>
P|1|675DRC4<CR>
O|1|W3|^|^^^Ferritin|||||||||||Serum||||||||||X<CR>
C|1|I|Sample already exists|G<CR>
L|1|F<CR>
In this example, the instrument sends rejection notification messages for Sample ID
W3. This Sample ID already exists on the instrument and therefore cannot be
accepted as a new test order (assuming that the action code in the downloaded Test
Order record was N). The rejections are sent in separate messages because the
instrument LIS Send Mode is set to By Test.
H|\^&|||ACCESS^500001|||||LIS||P|1|20021010114936<CR>
P|1|DOEjane<CR>
O|1|661|^1^1|^^^TotT4^1\^^^TotT4^2\^^^TU^1\^^^TU^2|^^^FTIndex^1|||||||||||Serum||||||||||F<CR>
R|1|^^^TotT4^1|3.33|ug/dL||N||F||||20021010114333<CR>
R|2|^^^TotT4^2|3.33|ug/dL||N||F||||20021010114333<CR>
R|3|^^^TU^1|15.33|%Uptake||N||F||||20021010114221<CR>
R|4|^^^TU^2|15.33|%Uptake||N||F||||20021010114857<CR>
R|5|^^^FTIndex^1|1.28|ug/dL||N||F||||20021010114931<CR>
L|1|F<CR>
In this example, the instrument reports results for Sample ID 661. Two replicates of
TotT4 and two replicates of TU were ordered. The FTIndex was not ordered (it cannot
be ordered using the LIS interface), but it was generated automatically when valid
TotT4 and TU results were obtained. The instrument LIS Send Mode is set to By
Sample Container, so all results for the sample are sent in one message.
LIS setup. The instrument interprets the next message it receives during this time-out
period as the response to its query.
H|\^&|||ACCESS^500001|||||LIS||P|1|20001010085833<CR>
Q|1|^Samp45||ALL||||||||O<CR>
L|1|F<CR>
In this example, the instrument sends a query to the laboratory computer for test
information for sample ID Samp45, after the rack containing this sample is loaded
onto the instrument.
H|\^&|||LIS|||||||P|1|20001010080000<CR>
P|1|435600<CR>
O|1|Samp45||^^^TSH|R||||||A||||Serum<CR>
L|1|F<CR>
In this example, the laboratory computer responds to a query for sample Samp45 with
a test order for TSH.
H|\^&|||LIS|||||||P|1|20001010080000<CR>
L|1|F<CR>
In this example, the laboratory computer responds to a query for sample Samp45 with
a message indicating that no tests are available for the sample.
^@ 0 00 <NUL> null
^a 1 01 <SOH> start of heading
^b 2 02 <STX> start of text
^c 3 03 <ETX> end of text
^d 4 04 <EOT> end of transmission
^e 5 05 <ENQ> enquiry
^f 6 06 <ACK> acknowledge
^g 7 07 <BEL> bell
^h 8 08 <BS> backspace
^i 9 09 <TAB> horizontal tab
^j 10 0A <LF> line feed
^k 11 0B <VT> vertical tab
^l 12 0C <FF> form feed
^m 13 0D <CR> carriage return
^n 14 0E <SO> shift out
^o 15 0F <SI> shift in
^p 16 10 <DLE> data link escape
^q 17 11 <DC1> device control 1 (XON)
^r 18 12 <DC2> device control 2
/ 47 2F / forward slash
0 48 30 0 digit 0
1 49 31 1 digit 1
2 50 32 2 digit 2
3 51 33 3 digit 3
4 52 34 4 digit 4
5 53 35 5 digit 5
6 54 36 6 digit 6
7 55 37 7 digit 7
8 56 38 8 digit 8
9 57 39 9 digit 9
: 58 3A : colon
; 59 3B ; semicolon
< 60 3C < less than
= 61 3D = equal sign
> 62 3E > greater than
? 63 3F ? question mark
@ 64 40 @ at sign
A 65 41 A capital A
B 66 42 B capital B
C 67 43 C capital C
D 68 44 D capital D
69 69 45 E capital E
F 70 46 F capital F
G 71 47 G capital G
H 72 48 H capital H
I 73 49 I capital I
J 74 4A J capital J
K 75 4B K capital K
L 76 4C L capital L
M 77 4D M capital M
N 78 4E N capital N
O 79 4F O capital O
P 80 50 P capital P
Q 81 51 Q capital Q
R 82 52 R capital R
S 83 53 S capital S
T 84 54 T capital T
U 85 55 U capital U
V 86 56 V capital V
W 87 57 W capital W
X 88 58 X capital X
Y 89 59 Z capital Y
Z 90 5A Z capital Z
[ 91 5B [ left bracket
\ 92 5C \ backslash
] 93 5D ] right bracket
^ 94 5E ^ circumflex
_ 95 5F _ underscore
‘ 96 60 ‘ grave accent
a 97 61 a small a
b 98 62 b small b
c 99 63 c small c
d 100 64 d small d
e 101 65 e small e
f 102 66 f small f
g 103 67 g small g
h 104 68 h small h
i 105 69 i small i
j 106 6A j small j
k 107 6B k small k
l 108 6C l small l
m 109 6D m small m
n 110 6E n small n
o 111 6F o small o
p 112 70 p small p
q 113 71 q small q
r 114 72 r small r
s 115 73 s small s
t 116 74 t small t
u 117 75 u small u
v 118 76 v small v
w 119 77 w small w
x 120 78 x small x
y 121 79 y small y
z 122 7A z small z
{ 123 7B { left brace
| 124 7C | vertical bar
} 125 7D } right brace
~ 126 7E ~ tilde
^? 127 7F <DEL> delete
This Access Test Codes list is subject to change without notification. Tests listed may
or may not be available for use with commercial systems. The availability of any
assay in your country depends on the status of submissions to local regulatory
agencies. Contact your Beckman Coulter representative for more information on
test availability.
NOTE
The instrument Tests screen displays the test codes available on the instrument.
Access DL2000
Code Code Assay Name
Access DL2000
Code Code Assay Name
Access DL2000
Code Code Assay Name
Access DL2000
Code Code Assay Name
Access DL2000
Code Code Assay Name
Access DL2000
Code Code Assay Name
The following record fields support extended ASCII Katakana and Simplified
Chinese characters.
Comment Record
• Comment Text, when the Comment Type is G. (Flags, in which the Comment
Type is F, are always sent in English.)
NOTES
• Simplified Chinese characters each require two bytes. Therefore, if a field has
a limitation of 40 characters, up to 20 Simplified Chinese characters may be
entered in that field. Likewise, if a field has a limitation of 15 characters, up to
7 Simplified Chinese characters may be entered.
• It is permissible to combine Simplified Chinese and U.S. ASCII characters in
a field, provided that the total number of bytes does not exceed the limitation
specified for that field.
• Simplified Chinese currently is available only on Access 2 systems with
software versions 2.3 or higher.
Instrument The instrument LIS port is the COM2 DB-9 male connector located on the back of the
LIS Port external PC. See the External Computer Ports topic in the system Help or in the
Reference Manual for the location of the port.
The DB-9 male connector provides Receive Data (RD) on pin 2, Transmit Data (TD)
on pin 3, and signal ground (GND) on pin 5. No other signals are required or
supported.
NOTE
Beckman Coulter recommends that only the three supported signal lines be
connected to the instrument LIS port. Connecting other signals may cause
communication failure.
5 9 1 6
6 9
1 5
2308A.eps 2307A.eps
RD 2 2 TD
TD 3 3 RD
GND 5 5 GND
Wiring RJ-45 In installations where long cable runs are required, it is a common practice to run
Adapters for category 5 network cable terminated with RJ-45 modular connectors. When RJ-45
Use with terminated cables are used, adapters are required at each end of the cable to connect to
Category 5 the DB-9 male connector on the instrument external computer, and to a DB-9 or
Cable Runs DB-25 connector on the laboratory computer. Figure D-2 shows a typical category 5
cable run, in which the laboratory computer EIA-232 port is a DB-25 connector.
Other configurations are possible.
Figure D-2 Typical Category 5 Cable Run with RJ-45 Adapters
NOTE
When wiring RJ-45 adapters, it is advisable to obtain an inexpensive pin extractor
tool. Once pins are inserted in the DB connector, they cannot be removed without
this tool. Pin extractors can be purchased at most electronics stores.
RJ-45 RJ-45
Signal Pin Pin Signal
TD 6 6 TD
RD 5 5 RD
Ground 4 4 Ground
2309A.eps