Host Transmission Manual

CellMek SPS Sample Preparation System

Host Transmission

C48508AA
November 2021

Beckman Coulter, Inc.

250 S. Kraemer Blvd.
Brea, CA 92821 U.S.A.
CellMek SPS Host Transmission
PN C48508AA, November 2021

© 2021 Beckman Coulter, Inc.

All Rights Reserved

Beckman Coulter, the stylized logo, and the Beckman

Coulter product and service marks mentioned herein are
trademarks or registered trademarks of Beckman Coulter,
Inc. in the United States and other countries.

Windows 10 is a registered trademark of Microsoft

Corporation in the United States and/or other countries.

All other trademarks are the property of their respective

owners.

Contact Us
If you have any questions, contact our Customer Support
Center.

• Worldwide, find us via our website at

www.beckman.com/support/technical.
• In the USA and Canada, call us at 1-800-369-0333.
• Outside of the USA and Canada, contact your local
Beckman Coulter Representative.

Beckman Coulter Eurocenter S.A.

22, rue Juste-Olivier
Case Postale 1044
CH - 1260 Nyon 1, Switzerland
Tel: +41 (0) 22 365 36 11

Glossary of Symbols is available at

beckman.com/techdocs (PN C24689).

May be covered by one or more pat. - see

www.beckman.com/patents

Original Instructions
 Revision History
Initial Release, November 2021
Software Version 1.0

This document applies to the latest software listed and higher versions. When a subsequent software version affects the
information in this document, a new issue will be released to the Beckman Coulter website. For labeling updates, go to
www.beckman.com/techdocs and download the latest version of the manual or system help for your instrument.

C48508AA iii
 Revision History

iv C48508AA
 Safety Notice
Read all product manuals and consult with Beckman Coulter-trained personnel before attempting
to operate instrument. Do not attempt to perform any procedure before carefully reading all
instructions. Always follow product labeling and manufacturer’s recommendations. If in doubt as
to how to proceed in any situation, contact us.

Beckman Coulter, Inc. urges its customers to comply with all national health and safety standards
such as the use of barrier protection. This may include, but is not limited to, protective eyewear,
gloves, and suitable laboratory attire when operating or maintaining this or any other automated
laboratory analyzer.

Alerts for Warning and Caution

WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, could
result in death or serious injury. May be used to indicate the possibility of
erroneous data that could result in an incorrect diagnosis (does not apply to all
products).

CAUTION
CAUTION indicates a potentially hazardous situation, which, if not avoided, may
result in minor or moderate injury. It may also be used to alert against unsafe
practices. May be used to indicate the possibility of erroneous data that could
result in an incorrect diagnosis (does not apply to all products).

C48508AA v
 Safety Notice
Alerts for Warning and Caution

WARNING
Risk of operator injury if:
• All doors, covers and panels are not closed and secured in place prior to and
during instrument operation.
• The integrity of safety interlocks and sensors is compromised.
• Instrument alarms and error messages are not acknowledged and acted upon.
• You contact moving parts.
• You mishandle broken parts.
• Doors, covers and panels are not opened, closed, removed and/or replaced
with care.
• Improper tools are used for troubleshooting.

To avoid injury:
• Keep doors, covers and panels closed and secured in place while the
instrument is in use.
• Take full advantage of the safety features of the instrument.
• Acknowledge and act upon instrument alarms and error messages.
• Keep away from moving parts.
• Report any broken parts to your Beckman Coulter Representative.
• Open/remove and close/replace doors, covers and panels with care.
• Use the proper tools when troubleshooting.

CAUTION
System integrity could be compromised and operational failures could occur if:
• This equipment is used in a manner other than specified. Operate the
instrument as instructed in the product manuals.
• You introduce software that is not authorized by Beckman Coulter into your
computer. Only operate your system’s software with software authorized by
Beckman Coulter.
• You install software that is not an original copyrighted version. Only use
software that is an original copyrighted version to prevent virus
contamination.

CAUTION
If you purchased this product from anyone other than Beckman Coulter or an
authorized Beckman Coulter distributor, and, it is not presently under a Beckman
Coulter service maintenance agreement, Beckman Coulter cannot guarantee that
the product is fitted with the most current mandatory engineering revisions or
that you will receive the most current information bulletins concerning the
product. If you purchased this product from a third party and would like further
information concerning this topic, contact your Beckman Coulter Representative.

vi C48508AA
 Contents

Revision History, iii

Safety Notice, v
Introduction, ix
CHAPTER 1: Communication Transport, 1-1
Supported Transport Methods, 1-1
TCP/IP Configuration Options, 1-1
Multiple Lines of Transport , 1-1
ASTM Protocol, 1-1
ASTM Data Record Format, 1-2
ASTM Message General Format, 1-2
ASTM Message Record Codes, 1-3
Unicode support, 1-3
LIS Message Formats, 1-4
Max Len Column, 1-4
Format Column, 1-4
Floating Point Format, 1-4
Receive Column, 1-5
Send Column, 1-6
Unicode Column, 1-6
Header Record – “H”, 1-6
Patient Information Record – “P”, 1-7
Test Order Record – “O”, 1-9
Comment Record – “C”, 1-11
Host Query (Request Information Record), 1-12
Message Terminator Record – “L”, 1-13
Manufacturer Record – “M|106” (Test Communication), 1-14
Rules, 1-14

APPENDIX A: Messages, A-1

Messages, A-1

APPENDIX B: Messages from ASTM Engine, B-1

General ASTM Protocol Errors, B-1
Errors With Individual Fields, B-3
Port-Specific Errors, B-4

vii
 Contents

Glossary
Beckman Coulter, Inc.
End-User License Agreements
Related Documents

viii
 Introduction

Purpose

This document establishes the basis for the design and implementation of an LIS interface by both
LIS Vendors and the CellMek SPS (Sample Prep System). This document is also intended to be used
by service and support personnel as a guide to diagnosing and troubleshooting LIS communication
problems.

Overview

The primary purpose of the LIS interface is to allow the CellMek SPS to receive sample
programming from an LIS.

Conventions

This document uses the following conventions:

• Bold face font indicates buttons or selections that appear on the Workstation screen.
• The term select is used to indicate either one or both of the following actions:
— To tap or touch with your finger.
— To click with a mouse.

NOTE The verb “press” is reserved for mechanical buttons, such as keys on the keyboard.

• The software path to a specific function or screen appears with the greater than (>) symbol
between screen options.
• Links to information in another part of the document for additional information are in blue and
are underlined. To access the linked information, select the blue, underlined text.

IMPORTANT IMPORTANT is used for comments that add value to the step or procedure being performed.
Following the advice in the IMPORTANT adds benefit to the performance of a piece of equipment or to a
process.

NOTE NOTE is used to call attention to notable information that should be followed during use or
maintenance of this equipment.

C48508AA ix
 Introduction
Conventions

x C48508AA
 CHAPTER 1
Communication Transport

Supported Transport Methods

The following transports are supported for CLSI (NCCLS) LIS1-A:

• TCP/IP – As client.

TCP/IP Configuration Options

CellMek SPS will allow the following configuration option for TCP/IP data transport:

• Server port number

• Server IP Address

Multiple Lines of Transport

CellMek SPS will support only single line communications to the LIS.

ASTM Protocol

The low-level protocol is specified by the “Standard for Low-Level Protocol to Transfer Messages
Between Clinical Laboratory Instruments and Computer Systems”, LIS1-A (formerly ASTM E1381-
02).

The format of the records used is based on “Specification for Transferring Information Between
Clinical and Laboratory Instruments and Information Systems; Approved Standard-Second
Edition”, LIS2-A2 (formerly ASTM 1394).

The data transmission rate for an LIS using TCP/IP will conform to IEEE 802.3 and operate at least
10 MB/second. (LIS01-A2–7.2.3.1).

CellMek SPS supports a frame size of 64,000 characters (including overhead) for TCP
communication. However, in order to improve LIS compatibility. CellMek SPS will not send frames
larger than 8192 bytes (including overhead).

When there is line contention (both systems are bidding at the same time), CellMek SPS will behave
as an Instrument (LIS01-A2, 6.2.7.1). When line contention occurs, the CellMek shall retry 10 times
before raising a loss of communication alert. CellMek SPS will wait a random amount of time
between 1 and 3 seconds after line bid contention to send another ENQ.

C48508AA 1-1
 Communication Transport
ASTM Protocol

ASTM Data Record Format

The data record format for all transmissions to and from CellMek SPS is:

<STX> FN <FRAME> <CR> <<ETB> or <ETX>> <<CS> or <CRC>> <CR><LF>

where:

<STX> the start of message character (Hexadecimal ASCII CODE: 0x02)

FN Frame number (Integer Value: 0 to 7)
<FRAME> data - the message
<CR> data always terminated by a carriage return (Hexadecimal ASCII
CODE: 0x0D)

NOTE <CR> is only present when ETX is present at the end of a

record.
<ETB> end of frame – required when record is too big for a frame
(Hexadecimal ASCII CODE: 0x17)
<ETX> end of frame (Hexadecimal ASCII CODE: 0x03)
<CS> checksum - follows exactly LIS1-A 6.3.3. in the case of CS.
<CR> Carriage Return ASCII character (Hexadecimal ASCII CODE: 0x0D)
<LF> Line Feed ASCII character (Hexadecimal ASCII CODE:0x0A)

ASTM Message General Format

Sending Sample Program
H – Header record
P – Patient Information (demographics)
C – Patient comment if any
O – Order (sample information)
C – Sample Comment if any

L – terminator record

All messages will start with a Header record and finish with a terminator record.

1-2 C48508AA
 Communication Transport
ASTM Protocol 1

ASTM Message Record Codes

Record Type Sent By Record Explanation

H - Header Record
P - Patient Information Record
O - Test Order Record
C - Comment Record
Q - Request Information Record
L - Message Terminator Record
M - Manufacturer Record
R - Result Record
LIS and Record contains information about the LIS
CellMek SPS and CellMek SPS. It also defines the field, repeat,
and component delimiters.
LIS Record contains information about an
individual patient.
Sent to CellMek SPS immediately preceding an
Order Record. CellMek SPS only uses this record to
respond to a failed Test Order request from the LIS,
but no Patient Information is added.
LIS and When sent by the LIS, this record represents a test
CellMek SPS order (i.e., tests to run) for a sample.
CellMek SPS only sends this record to respond to a
failed Test Order request from the LIS.
LIS Record contains sample comments.
CellMek SPS only processes WBC values from
comment records.
CellMek SPS Request Information Record (Host Query)
LIS and Terminator Record
CellMek SPS
CellMek SPS Communications Status Check message
LIS Result messages sent by the LIS will not be
processed. CellMek SPS does not sent result
messages.

Unicode support
CellMek SPS uses characters in the Unicode character set with a UTF-8 encoding as characters in
some of the data fields of messages transmitted and received.

By default, CellMek SPS will use the delimiters below. CellMek SPS can support any set of delimiters
that are defined as per LIS2-A2 delimiter requirements. CellMek SPS also supports LIS2-A2 standard
escape delimiter processing for embedding delimiters within fields.

Delimiter Type Delimiter Description

Field | Vertical bar (|) Latin-1 (124)
Repeat \ Backslash (\) Latin-1 (96)
Component ^ Caret (^) Latin-1 (94)
Escape & Ampersand (&) Latin-1 (38)

C48508AA 1-3
 Communication Transport
LIS Message Formats

LIS Message Formats

The following paragraphs define the column specification for the LIS message formats.

Max Len Column

The maximum length specified for this field. If this field is blank, then the CellMek SPS will not
validate the length of this field. The CellMek SPS accepts messages received with alternate
delimiters, but it still sends any response to that message with the CellMek SPS default delimiters.

Format Column
The Format column will be specified as follows:

Format Column Description

N Numeric – '0', '1', '2', '3', '4', '5', '6', '7', '8' and '9' only
F Floating Point – see Floating Point Format
FS Floating Point including symbols - A floating point number which may be preceded by
a single ‘<’ and ‘>’ to indicate a range of numbers.
C Characters – Supports either standard ASCII or Unicode UTF-8 encoded characters
depending on the field or component. See Unicode Column below.

NOTE Leading and trailing whitespace will be removed.

C-X Characters-Exact – Same as C, however, it must match the given choices provided
in the specification for the particular field or component. If an exact match is not
made, the message will be rejected.
D Date – YYYYMMDD
DT Date and Time – YYYYMMDDHHMMSS
T Time – HHMMSS
ID ID format – Same as C.

Alphabet Supports either standard ASCII or Unicode UTF-8 encoded alphabet characters. See
Unicode Column below.
characters

Floating Point Format

The receiver should be able to handle as many significant figures as are possible given a field’s
length. If a field has a length of 15, the receiver should have some method of storing 15 digits of
precision. Floating point formatted fields must contain at least one digit (ASCII 0x30-0x39), an
optional single decimal point (ASCII 0x2E) in any position, and an optional leading hyphen (ASCII
0x2D) to indicate a negative number. If a required field that has this format does not have valid
syntax the message will be rejected.

1-4 C48508AA
 Communication Transport
LIS Message Formats 1

Grammar
This is an Extended Backus-Naur Form grammar describing the floating point format.

• Digit ::= '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' ;
• Number ::= Digit+ ;
• Float ::= Number | Number '.' | '.' Number | Number '.' Number ;
• SignedFloat ::= Float | '-' Float ;

Examples
Valid:

• -0.0023
• 1.
• 9248
• 0.00005
• -.5

Invalid:

• .
• -.

Receive Column
The Receive column will be specified as follows:

Receive Column Description

Req • This field must be sent by the sender.
• CellMek SPS will validate the length and format of this field. This field must be
well-formed or the message will be rejected. See APPENDIX B, Messages from ASTM
Engine for rejection messages.
Yes • Sending this field is optional.
• If the field is sent, the CellMek SPS will validate the length and format of this field.
This field must be well-formed or the message will be rejected. See APPENDIX B,
Messages from ASTM Engine for rejection messages.
No • This field is ignored by the CellMek SPS.
• CellMek SPS will not validate the length and format of this field.

C48508AA 1-5
 Communication Transport
LIS Message Formats

Send Column
The Send column will be specified as follows:

Send Column Description

Req • CellMek SPS will always send this field.
• CellMek SPS guarantees that this field will satisfy the message length and
format specified.
Yes • Sending this field is optional. If data is available, the CellMek SPS will send this
field.
• CellMek SPS guarantees that this field will satisfy the message length and
format specified.
No • CellMek SPS will not send this field.

Unicode Column
The Unicode column will be specified as follows:

Unicode Column Description

Yes • CellMek SPS supports the Unicode (UTF-8) characters for this field.
• Unicode characters must be specified by Unicode escape characters.
No • CellMek SPS will not accept Unicode characters for this field. If a Unicode escape
character is found in this field, the message will be rejected. See APPENDIX B,
Messages from ASTM Engine for rejection messages.

Header Record – “H”

The Header Record will be the first record of each message sent.

Any set of messages always starts with message header record ‘H’. The second field in this record
contains the delimiters that are going to be used for the set of records.

The Header record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record Identifier 1 C Req Req No H
2 Delimiters: | 1 C Req Req No vertical bar (|) Latin-1(124)
Field
Repeat delimiter \ 1 C Req Req No backslash (\) Latin-1(96)
Component delimiter ^ 1 C Req Req No caret (^) Latin-1(94)
Escape delimiter & 1 C Req Req No ampersand (&) Latin-1(38)
3-4 Ignored

1-6 C48508AA
 Communication Transport
LIS Message Formats 1

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
5 Sender Name or ID | 128 C Yes Yes No CellMek SPS
Device ID ^ 128 N Yes Yes No This is the ID from the LIS
setup screen. This number
should be unique per
workstation or computer
connected to the LIS. The
maximum length is 128 for
receive and 10 for send.
6-12 Ignored
13 Version Number | 128 C Yes Yes No LIS2-A2
This is the ASTM version
14 Date and Time of | 14 DT Yes Yes No 20020417120501 (format
Message YYYYMMDDHHMMSS)
End of Record <CR> 1 Req Req No

Example:
Sending Header and Terminator (Minimum Header)

H | \ ^ & <CR>
L | 1 | N <CR>

Sending Header and Terminator (Long Header)

H | \ ^ & | | | CellMekSPS^100 | | | | | | | | LIS2-A2 | 20121004190802 <CR>

L | 1 | N <CR>

Patient Information Record – “P”

The patient record is used as defined by the LIS2-A2 protocol and will be sent before test order
information, even if there is no patient information.

Data listed as discarded below will not be retained in the CellMek SPS software except in the LIS
communication logs. LIS logs will automatically purge after 60 days.

The Patient Information Record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record Identifier 1 C No Req No P
2 Sequence Number | 5 N No Req No
3 Ignored
4 Laboratory-Assigned | 128 ID No Yes Yes Will be discarded by
Patient ID CellMek SPS.

C48508AA 1-7
 Communication Transport
LIS Message Formats

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
5 Government ID | 128 C No Yes Yes Will be discarded by
(Social Security CellMek SPS.
Number)
6 Patient Name | 128 C No Yes Yes Will be discarded by
Last Name CellMek SPS.
First Name ^ 128 C No Yes Yes Will be discarded by
CellMek SPS.
Middle Name ^ 1 C No Yes Yes Will be discarded by
CellMek SPS.
7 Ignored
8 Birth date | 8 D No Yes No 19501120, YYYYMMDD
Will be discarded by
CellMek SPS.
9 Sex | 1 C No Yes No M = Male
F = Female
U = Unknown or Undefined
(If blank or non-listed value, will
assume ‘U’)
Will be discarded by
CellMek SPS.
10-13 Ignored
14 Attending Physician | 128 C No Yes Yes Will be discarded by
ID (Doctor) CellMek SPS.
Last Name ^ 128 C No Yes Yes Will be discarded by
CellMek SPS.
First Name ^ 128 C No Yes Yes Will be discarded by
CellMek SPS.
Middle Name ^ 128 C No Yes Yes Will be discarded by
CellMek SPS.
15-24 Ignored
25 Admission Status | 128 C No Yes Yes Will be discarded by
CellMek SPS.
26 Patient Location | 128 C No No Yes Will be discarded by
CellMek SPS.
End of Record <CR> 1 No Req No <CR>

Example:
Sending Patient Information Record

H|\^&<CR>
P|1||PID||Smith^John^S||19501120|M|||||Dr. Mark Jones^^||||||||||||Room 421<CR>

1-8 C48508AA
 Communication Transport
LIS Message Formats 1

Sending Patient Information Record with minimum required information:

H|\^&<CR>
P|1<CR>

Test Order Record – “O”

The Test Order Record contains information about the specimen, including test requests.

Data listed as discarded below will not be retained in the CellMek SPS software except in the LIS
communication logs. LIS logs will automatically purge after 60 days.

Host query responses and LIS broadcasts containing multiple tests for the same specimen ID must
use the repeat delimiter and not use separate order records. Only orders contained in the most
recent LIS broadcast message will be used. Previous orders for the same specimen ID will be over-
written.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record Identifier 1 C Req Req No O
2 Sequence Number | 5 N Req Req No
3 Specimen ID/Control | 24 ID Req Req Yes SAMPLE001
ID Minimum Length: 5
No leading or trailing spaces
Invalid characters: *<>\/?|:’,[] ‘’
“”
4 Ignored
5 Universal Test ID: | No No No Up to 3 Test IDs are allowed in an
Identifier order, any more and the
message is rejected (via
message response with
comment indicating reason)
Identifier portion of this
composite field will be discarded
by CellMek SPS
Name ^ No No No Discarded by CellMek SPS.
Type ^ No No No Discarded by CellMek SPS.
Test ID1 ^ 50 C Req Req Yes Must match a Panel Test ID in the
CellMek SPS software to be
accepted.
No leading or trailing spaces.
Must be all capital alphabet.
Accepts only alphabet and
numbers.
6 Priority | 1 C-X Yes Yes No Will be discarded by
CellMek SPS.
7 Ignored

C48508AA 1-9
 Communication Transport
LIS Message Formats

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
8 Specimen Collection | 14 DT Yes Yes No Will be discarded by
Date and Time CellMek SPS.
9-11 Ignored
12 Action Code | 1 C-X Yes Yes No C = Cancel tests. All LIS test
requests for the specimen will be
cancelled regardless of the test
codes supplied in the message.
A = Add - creates a new sample
order if none exists, if it exists
the order is replaced.
(If blank or non-listed value, will
generate an error and reject the
order request.)
13-15 Ignored
16 Specimen Type | 128 C-X Yes Yes No NOTE The values above may
be mapped to other codes in
the software.
(May be blank if Report Type
= “Y” or “X”)
Discarded by CellMek SPS.
17 Ordering Physician | 128 C Yes No Yes Will be discarded by
ID CellMek SPS.
Last Name ^ 128 C Yes Yes Yes Will be discarded by
CellMek SPS.
First Name ^ 128 C Yes Yes Yes Will be discarded by
CellMek SPS.
Middle Name ^ 128 C Yes Yes Yes Will be discarded by
CellMek SPS.
18-25 Ignored
26 Report Type | 1 C Yes Yes No Y, Z = No Information in
response to a Host Query
O = LIS provided order
(If blank or non-listed value
(other than 'X'), will assume ‘O’)
For Send:
X = When Order or Sample is
rejected by CellMek SPS.
O = otherwise
End of Record <CR> 1 Req Req No <CR>

1 It is recommended for LIS to use repeat delimiter and not use separate order records for each test
to download the sample programs.

1-10 C48508AA
 Communication Transport
LIS Message Formats 1

Example:
Sending Test Order Record (Normal Order)

H|\^&<CR>
P|1||PID||Smith^John^S||19501120|M|||||Dr. Mark Jones||||||||||||Room 421<CR>
O|1|SAMPLE001||^^^01A\^^^02A|S||20091005120000||||A||||Serum|Dr. John Jones Jr.|||||||||O<CR>
L|1|N <CR>

Sending Test Order Record (No Test Order, in response to Host Query)

H|\^&<CR>
P|1||||||||||||||||||||||||<CR>
O|1|SAMPLE001||||||||||||||||||||||Y<CR>
L|1|N <CR>
Sending Test Order Record (Cancel all tests on a sample)

H|\^&<CR>
P|1||PID<CR>
O|1|SAMPLE001||^^^01A\^^^02A||||||C<CR>
L|1|N <CR>

CellMek SPS Software Rejecting Test Order Record

H|\^&<CR>
P|1||||||||||||||||||||||||<CR>
O|1|SAMPLE001|||||||||||||||||||||||X<CR>
C|1|I|Reason for rejection.|G<CR>
L|1|N <CR>

Comment Record – “C”

Comment records sent by the LIS will be received by CellMek SPS will be parsed for WBC
information. All other comment records will be discarded.

Data listed as discarded below will not be retained in the CellMek SPS software except in the LIS
communication logs. LIS logs will automatically purge after 60 days.

The Comment Record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record Identifier 1 C Req Req No C
2 Sequence Number | 5 N Req Req No
3 Comment Source | 1 A No Yes No Discarded by CellMek SPS.

C48508AA 1-11
 Communication Transport
LIS Message Formats

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
4 Comment | 256 C Yes Yes Yes Only WBC values will be
(Applies only to Order processed from comment
records) records. The format for these
comments is:

“WBC:[value]”

Example:
“WBC:234”
5 Comment Type | 1 C Yes Yes Yes G = Generic Comment
(If blank or non-listed value,
will assume ‘G’).
End of Record <CR> 1 Req Req No <CR>

Example:
Sending Sample Comment Record
H|\^&<CR>
P|1||PID||Smith^John^S||19501120|M|W||||Dr. Mark Jones||||||||||||Hospital^Room 421<CR>
O|1|SAMPLE001||^^^01A\^^^02A|S||20090109120000||||A||||Serum|Dr. John Jones Jr.|||||||||O <CR>
C|1|L|WBC:234|G<CR>
L|1|N<CR>

Host Query (Request Information Record)

The CellMek SPS will operate in exclusively broadcast download or host query mode. The CellMek
SPS will provide the option to select the mode of operation.

Upon receipt of a host query request, if the LIS has corresponding sample information, the LIS must
reply with a sample order. If no sample information is available, the LIS must reply to the host query
request with a sample order where the Report Type is set to “Y”. A Report Type of “Y” indicates that
no sample programming is available for the sample.

The Host Query Record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record Identifier 1 C No Req No Q
2 Sequence Number | 5 N Req Req No

1-12 C48508AA
 Communication Transport
LIS Message Formats 1

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
3 Starting Range ID | No No No
Number Patient ID
Specimen ID ^ 24 ID No Req Yes Minimum Length: 5
Maximum Length: 24
No leading or trailing spaces
No *<>\/?|:',[] `' “ ”
characters
4-12 Ignore
13 Request Information | 1 C-X No Req No O = Request Sample
Status Codes Programming information
End of Record <CR> 1 Req Req No <CR>

Sending Host Query

H|\^&|||CellMekSPS^100||||||||1.0|20121004190802<CR>
Q|1|^1000||||||||||O<CR>
L|1|N<CR>

Message Terminator Record – “L”

This record is sent by CellMek SPS and the LIS. The record signifies the last record in a message.
There must be one terminator record for every header record sent by either system.

The Terminator Record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record 1 C Req Req No L
Identifier
2 Sequence | 5 N Req Req No
Number
3 Terminator | 1 C-X Yes Yes No N=Normal termination
End of <CR> 1 Req Req No <CR>
Record

Example:
Sending Header and Terminator

H|\^&<CR>
L|1|N<CR>

C48508AA 1-13
 Communication Transport
Rules

Manufacturer Record – “M|106” (Test Communication)

The M|106 Record is record is sent by CellMek SPS as a test message to test communications between
the LIS and CellMek SPS. No response to this message is required.

The M|106 Record will be formatted as specified in the table below.

Field Description Delimiter Max Format Receive Send Unicode Example/Comments

No. Len
1 Record 1 C Req Req No M
Identifier
2 Sequence | 5 N Req Req No
Number
3 Record | 3 N Req Req No 106
Identifier
4 Date and | 14 DT No Yes No 20020215121532
Time (Format:
YYYYMMDDHHMMSS)
5 CellMek SPS | 128 C No Yes No LIS2-A2
Driver
Version
Number
End of <CR> 1 Req Req No <CR>
Record

Example:
CellMek SPS Sending M|106 Test Communication Record

H|\^&<CR>
M|1|106|20080523162244|1.00.00.00<CR>
L|1|N<CR>

Rules

When CellMek SPS rejects a sample program (request), it will send a Test Order Record with the
relevant Specimen ID and a Report Type of "X". A comment record of type G after the Order record
will provide a textual explanation for the rejection. See APPENDIX A, Messages.

CellMek SPS will reject the order and send the appropriate message if one of the following
conditions are met:
• Specimen ID is blank or invalid
• No Test IDs are provided
• More than 3 Test IDs are provided
• If any Test ID provided is not found in the list of Test IDs in CellMek SPS software (case-sensitive
comparison).

1-14 C48508AA

Messages
Message
Invalid action code [Action Code] for
specimen ID 1000001, rejecting
message.
The request could not be added for
specimen ID 1000001 because Report
Type = 'X'.
Field [field name] is required but was
not supplied, rejecting message.
Invalid test code [Test Code] for
specimen ID 1000001, rejecting
message.
Field [PatientLocation] exceed 50
characters and was truncated, rejecting defined length. Rejected message is sent back to LIS. The
message.
The request could not be added
because the Sample ID is invalid. [xxx]
is invalid.
Error formatting data for analyzer for
Specimen ID: Specimen ID,
Exception.Message
An error occurred processing ASTM
messages: Exception.Message
Error formatting result value for test
code for specimen ID: Specimen ID,
Exception.Message
C48508AA
APPENDIX A
Messages
Comments Err Msg to
LIS
Logged when an invalid action code is transmitted by the Y Y
LIS. The following message is also sent as a comment
back to the LIS when a rejected message is sent:
Invalid action code [Action Code] for specimen ID
1000001, rejecting message.
Logged when an order record sent by the LIS has the Y Y
Report Type field = 'X'. Report Type = 'X' only when
CellMek SPS is rejecting a message.
A request was received with a blank required field. The Y Y
request is rejected.
Logged when an invalid test code is transmitted by the Y Y
LIS. The following message is also sent as a comment
back to the LIS when a rejected message is sent:
Invalid test code [Test Code] for specimen ID 1000001,
rejecting message.
Exception is thrown when an incoming field exceeds the Y Y
following message is also sent as a comment back to the
LIS when a rejected message is sent:
Field [PatientLocation] exceed 50 characters and was
truncated, rejecting message.
Sample ID sent from LIS is invalid. Rejected message is Y Y
sent back to LIS. The following message is also sent as a
comment back to the LIS when a rejected message is
sent:
The request could not be added because the Sample ID is
invalid. [xxx] is invalid.
Unknown type of exception is thrown when unable to Y N
create dataset when parsing ASTM message from LIS.
Unknown type of exception thrown when an error occurs Y N
parsing LIS transaction to send to LIS
Unknown type of exception when populating BCI. Results Y N
object for sending results to LIS.
A-1
 Messages
Messages

Message Comments Err Msg to

LIS
No ACK received sending message to BCI.LISDeviceClient.SendResults() returns this error when Y, from N
LIS. sending results to LIS. Engine
Parsing failure sending message to LIS. BCI.LISDeviceClient.SendResults() returns this error when Y, from N
sending results to LIS. Engine
Success sending message to LIS. BCI.LISDeviceClient.SendResults() returns this result N, from N
when sending results to LIS to signal success. Engine
Error formatting result message for LIS Unknown type of exception when populating Y N
for specimen ID Specimen ID, BCI.ResultMessage object for sending results to LIS.
Exception.Message
No ACK received sending rejected order BCI.LISDeviceClient.SendRejectedOrders() returns this Y, from N
message to LIS. error when sending rejected order message to LIS. Engine
Parsing failure sending rejected order BCI.LISDeviceClient.SendRejectedOrders() returns this Y, from N
message to LIS. error when sending rejected order message to LIS. Engine
Success sending rejected order BCI.LISDeviceClient.SendRejectedOrders() returns this N, from N
message to LIS. result when sending rejected order message to LIS to Engine
signal success.
Error formatting rejected order Unknown type of exception occurs when creating Y N
message for LIS for specimen ID BCI.DriverLib.RejectedOrder object and/or calling
Specimen ID, Exception.Message BCI.LISDeviceClient.SendRejectedOrders().
No specimen ID supplied for host query. Logged when no specimen ID is sent by analyzer when Y N
requesting a host query.
No ACK received sending host query. BCI.LISDeviceClient. SendHostQuery () returns this error Y, from N
when sending host query to LIS Engine
Parsing failure while sending host BCI.LISDeviceClient. SendHostQuery () returns this error Y, from N
query. when sending host query to LIS Engine
Success sending host query. BCI.LISDeviceClient.SendHostQuery() returns this result N, from N
when sending host query to LIS to signal success. Engine
Error formatting host query message Unhandled exception while executing Y N
for LIS for specimen ID Specimen ID, BCI.LISDeviceClient.SendHostQuery()
Exception.Message
Disconnected or Connected Informational message when the connection state with N, from N
the LIS toggles. Engine
Order was received. Informational message when an order was received from N N
LIS.
Order cancellation was received. Informational message when an order cancellation N N
message was received from LIS.
SEND or RECV Data sent or received Informational message that logs all incoming or outgoing N N
from LIS data included in the ASTM message. Example:
SEND
1H|\^&|||CellMekSPS^100||||||||1.0|20120912072526
Or
RECV 1H|\^&|||||||||||1.0|20120912072526

A-2 C48508AA
 Messages
Messages A

Message Comments Err Msg to

LIS
==== An unhandled exception This message is logged when BCI.LISDeviceClient raises Y, from N
occurred. Driver restarted. ==== an unhandled exception. Engine
ASTM processing is initialized. Informational message when BCI.LISDeviceClient is N N
initialized for processing message.
ASTM processing is stopped. Informational message when BCI.LISDeviceClient N N
processing has been terminated
Too many Test IDs for Specimen ID Indicates that a transmission contained more than the Y Y
1000001, rejecting order permitted number of test orders (3) for specimen ID
1000001.

C48508AA A-3
 Messages
Messages

A-4 C48508AA

General ASTM Protocol Errors
These errors are should be somewhat rare outside of debugging and indicate some of the more rare
(and possibly severe) connection problems or protocol violations.
Message
The byte cache has been reset. It is
possible that a malformed packet was
received or the connection was reset
incorrectly.
Received more than the maximum
number of allowed bytes ({0}) in an
incoming frame. Message cannot be
received.
Received a byte which failed the parity
check in an incoming frame. Message
cannot be received.
Could not send frame. Did not contain
correct framing bytes (STX, ETX, or
ETB). {0}
Could not send frame. Contained one or Indicates that a packet could not be created due to the record containing invalid
more invalid bytes. See LIS1-A 6.6.2 for bytes.
further details. {0}
Bad packet received. Sent NAK.
Received unexpected bytes: {0}
Timed out while waiting to receive the
next packet.
Timed out while waiting for a response
to a transmitted line bid.
Timed out while waiting for a response
to a transmitted message.
Too many consecutive errors while
trying to send.
C48508AA
APPENDIX B
Messages from ASTM Engine
Comments
Indicates that bytes making up a partial message have been thrown away in an
attempt to be able to properly parse future messages. This is due to the device
violating the protocol or a lossy connection.
{0}: The buffer at the time of the overflow.
TokenizerCacheReset
Indicates that the tokenizer received more than the specified number of allowed
bytes in a data packet.
{0}: The maximum number of allowed bytes.
{1}: The buffer at the time of the overflow.
TokenizerBufferOverflow
Indicates that the tokenizer received a byte which failed the parity check.
FailedParityBit
Indicates that a packet could not be created due to missing frame bytes.
{0}: The failed bytes.
ASTMPacketFactoryFailedToPacketize
{0}: The failed bytes.
ASTMPacketFactoryContainedInvalidBytes
Indicates that a bad packet was received, causing a NAK to be sent.
FlowControlBadPacketReceived
Indicates that a bad byte or set of bytes was received in the given state.
{0}: The byte or bytes.
FlowControlReceivedUnexpectedBytesInState
Indicates that we timed out while waiting for a response to a line bid.
TimedOutWaitingForPacket
Indicates that we timed out while waiting for a response to a line bid.
TimedOutWaitingForLBACK
Indicates that we timed out while waiting for a response to a transmitted
message.
TimedOutWaitingForACK
Indicates that there were too many consecutive errors while attempting to send
data.
FlowControlSendingErrors
B-1
 Messages from ASTM Engine
General ASTM Protocol Errors

Message Comments
Packet failed frame number test. {0} Indicates that the given packet failed the frame number test.
{0}: The human readable string representing the packet.
FlowControlFailedFrameNumberTest
Packet failed checksum test. {0} Indicates that the given packet failed the check sum test.
{0}: The human readable string representing the packet.
FlowControlFailedChecksumTest
Attempted to send a record longer than Indicates that the flow controller could not send a given record because it was
the maximum allowable record length. longer than the allowed maximum record length.
FlowControlRecordLength
Received a record of type {0} from the Indicates that the Record Collator received a record of a type it was not
device. This record is not valid as the expecting, given the records already received.
next record in the sequence: \r\n{1} {0}: The type of the unexpected record
{1}: A newline separated list of the records already received. No more than 5
lines.
UnexpectedRecord
No Pending ASTM Records. (This is Used to indicate that there were no records when an unexpected record type
usually due to a previous error). was received. Should be passed in as the {1} argument to UnexpectedRecord.
NoRecords
Received an unknown record type: {0}. Indicates that the Record Collator received a record of a type it doesn't know
how to handle.
{0}: The type of the unexpected record
UnknownRecord
Received an unknown manufacturer's Indicates that the Flater received a manufacturer's record of a type it doesn't
record id: {0}. know how to handle.
UnknownManufacturersRecord
The device sent an incomplete The analyzer sent a chain of bytes which did not contain enough information to
transmission and it could not be parsed. identify the record type.
UnableToIdentifyRecord

B-2 C48508AA
 Messages from ASTM Engine
Errors With Individual Fields B

Errors With Individual Fields

These errors will be reported by individual fields.

Message Comments
DeflationError The driver cannot send the message due to an error at field '{0}':
InflationError The driver cannot parse the message due to an error at field '{0}':
StringTooBig The value '{0}' is too long.
BlankAttemptFailed The driver attempted to blank the string and failed.
ArraySizeInvalid The array size '{0}' is invalid
AnyNotDefined The value '{0}' is not defined.
NumericOutOfRange The value '{0}' is out of range for this field.
StringCoderFallback Exception thrown by the string encoder/decoder
The string cannot be processed due to the following: \r\n{0}
StringInvalidUnicodePoints The string cannot be processed as it contains invalid characters:\r\n{0}
RecordTooShort The record is '{0}' bytes long. More bytes were expected.
TruncatedFieldMessage The human-readable string which will be displayed on the Communication Log page when
a field is truncated.
{0}: The name of the field. Should be localized.
{1}: The original, non-truncated text from the field.
{2}: The truncated version of the original text.
Modified {0} from '{1}' to '{2}'.
FieldParseFailed Indicates that a field could not be successfully parsed.
{0}: The human readable name of the field.
{1}: The string representation of the unparsable bytes
The device sent invalid characters in the {0} field.\r\nThe device sent: \”{1}\”
MaxParseLengthExceeded Indicates that a field could not be sent because it exceeded the maximum width
{0}: The human readable name of the field
{1}: The expected maximum width
{2}: The string representation of the unparsable bytes.
The device sent too many characters in the {0} field, exceeding the maximum allowed
width of {1} characters for this type of device.\r\nThe device sent: \”{2}\”
RequiredParseDataMissing Indicates that a transmission was received with required data missing.
{0}: The human readable name of the field or component.
The device sent a record which is missing required data. The missing required data is in
the {0} field.
RequiredPrintDataMissing Indicates that a transmission was received with required data missing.
{0}: The human readable name of the field or component.
The driver cannot send a record which is missing required data. The missing required data
is in the {0} field.

C48508AA B-3
 Messages from ASTM Engine
Port-Specific Errors
Port-Specific Errors
Usually reported in the ‘description’ string of the DeviceClient’s ‘ConnectionStatus’ event. If the
connection is up (if the event reports ‘isError’ is false) the ‘description’ string will be blank.
Message
TCPClientConnecting
TCPClientError
TCPServerNoClientError
TCPServerAddressAlreadyInUse
NamedPipeConnectionError
B-4
Comments
This text directly follows the human-readable text for when a device using TCP
Client is attempting to connect to a server.
Client is trying to establish connection to server.
This text directly follows the human-readable text for when a device using TCP
Client is disconnected.
Client was closed.
This text directly follows the human-readable text for when a device using TCP
Server is listening but does not have a client yet.
TCP Server for driver is listening, but still does not have a connected client.
Displayed when the TCP server has not yet started because another program is
running a server on the same port.
Cannot start the TCP server because the configured port is already in use.
This text explains that a named socket connection was terminated by the other
end of the connection.
Named socket server connection was terminated abnormally.
C48508AA
 Glossary

This glossary is a collection of specialized terms and their meanings that are either used in this
manual or related to the information in it. If a term has more than one meaning, all meanings
relevant to this manual are included.

LIS — Laboratory Information System

CellMek SPS — Sample Preparation instrument and the software that controls it.

ASTM — American Society for Testing and Material (communication protocol)

NCCLS — An International, interdisciplinary, nonprofit, standard-developing, and educational

organization that promotes the development and use of voluntary consensus standards and guidelines
within healthcare community. (NCCLS (Now known as CLSI) inherited the ASTM protocol and currently
supports it.)

CLSI — Clinical and Laboratory Standards Institute. Formerly named NCCLS. Currently CLSI
inherits and updates NCCLS or ASTM documents.

Message — A collection of information passed from one software component or device to another.

Record — Part of a message. A message is composed of several records.

Frame — Part of a record. If record size is large, it will be divided into multiple frames.

Accept (Sample Program) — Update the CellMek SPS database with the sample information. No need to
send a message for acceptance per ASTM protocol.

Reject (Sample Program) — Send a rejection message (order message with report type “X”) to the LIS.
CellMek SPS Database is not updated with the sample information.

C48508AA Glossary-1
 Glossary

Glossary-2 C48508AA
 Index

A Multiple Lines of Transport, 1-1

ASTM Message General Format TCP/IP Configuration Options, 1-1
Sending Sample Program, 1-2
Unicode support, 1-3
ASTM Protocol, 1-1
ASTM data record format, 1-2
ASTM Message General Format, 1-2
ASTM Message Record Codes, 1-3
Unicode support, 1-3

L
LIS Message Formats, 1-4
Comment Record – “C”, 1-11
Format Column, 1-4
Floating Point Format, 1-4
Grammar, 1-5
Host Query (Request Information
Record), 1-12
Manufacturer Record – “M|106” (Test
Communication), 1-14
Max Len Column, 1-4
Message Terminator Record – “L”, 1-13
Receive Column, 1-5
Send Column, 1-6
Test Order Record – “O”, 1-9
Unicode Column, 1-6

M
Messages, A-1
Messages from ASTM Engine
Errors With Individual Fields, B-3
General ASTM Protocol Errors, B-1
Port-Specific Errors, B-4

R
Rules, 1-14

S
Supported Transport Methods, 1-1

Index-1
 Index

Index-2
 Beckman Coulter, Inc.
End-User License Agreements

CellMek Panel Designer Software

IMPORTANT Read this End-User License Agreement

THIS END-USER LICENSE AGREEMENT ("Agreement") GOVERNS THE USE OF CERTAIN COMPUTER
PROGRAMS ASSOCIATED WITH "CellMek PANEL DESIGNER" ("Product") PROVIDED BY BECKMAN COULTER,
INC. ("BCI"). YOUR USE OF SUCH PROGRAMS, YOUR PURCHASE OF THE PRODUCT, AND/OR YOUR USE OF THE
PRODUCT CONSTITUTES ASSENT AND ACCEPTANCE OF THIS AGREEMENT BY YOU (collectively "You" or
"Your") AND SIGNIFIES YOUR AGREEMENT TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS
AGREEMENT. IF YOU DO NOT AGREE WITH ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT, YOU
DO NOT HAVE THE RIGHT TO AND MAY NOT USE THE COMPUTER PROGRAMS PROVIDED.

1. GRANT OF LICENSE. Subject to all of the terms and conditions of this Agreement, BCI grants to You a non-
exclusive, non-sub licensable license to use the computer programs provided by BCI ("Programs") in
connection with and/or installed on the Product, and the associated user documentation
("Documentation") (together with the Programs referred to herein, collectively, as the ("Software")),
only in accordance with the Documentation ("License"). You have no right to receive, use or examine any
source code or design documentation relating to the Programs. The Software is licensed and not sold. As
between the parties, BCI and its licensors retains all right, title and interest in and to the Software and
any and all derivative works, except as expressly and unambiguously licensed herein, and BCI reserves
all rights in the Software not granted to You. Except as otherwise expressly provided under the
Agreement, You shall only use the Software as part of the CellMek SPS system.
2. USE RESTRICTIONS. You shall not (and shall not allow others to), directly or indirectly: (a) use (including
make any copies of) the Programs beyond the scope of the license granted under Section 1; (b) modify,
translate, adapt, or otherwise create derivative works or improvements, whether or not patentable, of
the Programs or any part thereof; (c) combine the Programs or any part thereof with, or incorporate the
Programs or any part thereof in, any other programs; (d) reverse engineer, disassemble, decompile,
decode, or otherwise attempt to derive or gain access to the source code of the Programs or any part
thereof; (e) reverse engineer, disassemble, decompile, decode, or otherwise attempt to derive or gain
access to the object code of the Programs or any part thereof; (f) remove, delete, alter, or obscure any
trademarks or any copyright, trademark, patent, or other intellectual property or proprietary rights
notices provided on or with the Software, including any copy thereof; (g) rent, lease, lend, sell,
sublicense, assign, distribute, publish, transfer, or otherwise make available the Programs, or any
features or functionality of the Programs, to any third party for any reason, whether or not over a
network or on a hosted basis, including in connection with the internet or any web hosting, wide area
network (WAN), virtual private network (VPN), virtualization, time-sharing, service bureau, software as
a service, cloud, or other technology or service; (h) use the Software in, or in association with, the design,
construction, maintenance, or operation of any hazardous environments or systems; (i) use the Software
in violation of any law, regulation, or rule; or (j) use the Software for purposes of competitive analysis of
the Programs, the development of a competing software product or service, or any other purpose that is
to BCI's commercial disadvantage.
3. TERMINATION. The License is effective until terminated. You may terminate the Agreement and the
License at any time by destroying all copies of the Program. The License will terminate automatically
without notice if You fail to comply with any provision of this Agreement. Within fourteen (14) days
following termination, You shall cease all use of, and, destroy all copies of the Software in Your
possession or control and so certify to BCI in writing. Except for the License, the terms of this Agreement

C48508AA Warranty-1
 Beckman Coulter, Inc. End-User License Agreements
CellMek Panel Designer Software

shall survive termination. Termination is not an exclusive remedy and all other remedies will be
available to BCI whether or not the License is terminated.
4. SOFTWARE SUPPORT. Please refer to the BCI support number provided in the Documentation for the
Product for information regarding support of the Product.
5. DISCLAIMER OF WARRANTY. THE SOFTWARE IS PROVIDED TO YOU "AS IS" AND WITH ALL FAULTS AND
DEFECTS WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED UNDER
APPLICABLE LAW, BCI, ON ITS OWN BEHALF AND ON BEHALF OF ITS AFFILIATES AND ITS AND THEIR
RESPECTIVE LICENSORS AND SERVICE PROVIDERS, EXPRESSLY DISCLAIMS ALL WARRANTIES,
WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, WITH RESPECT TO THE SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
TITLE, AND NON-INFRINGEMENT, AND WARRANTIES THAT MAY ARISE OUT OF COURSE OF DEALING,
COURSE OF PERFORMANCE, USAGE, OR TRADE PRACTICE. WITHOUT LIMITATION TO THE FOREGOING,
BCI PROVIDES NO WARRANTY OR UNDERTAKING, AND MAKES NO REPRESENTATION OF ANY KIND
THAT THE LICENSED SOFTWARE WILL MEET YOUR REQUIREMENTS, ACHIEVE ANY INTENDED RESULTS,
BE COMPATIBLE, OR WORK WITH ANY OTHER SOFTWARE, APPLICATIONS, SYSTEMS, OR SERVICES,
OPERATE WITHOUT INTERRUPTION, MEET ANY PERFORMANCE OR RELIABILITY STANDARDS OR BE
ERROR FREE, OR THAT ANY ERRORS OR DEFECTS CAN OR WILL BE CORRECTED.
6. LIMITATION OF LIABILITY. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW:
a. IN NO EVENT WILL BCI OR ITS AFFILIATES, OR ANY OF ITS OR THEIR RESPECTIVE LICENSORS OR
SERVICE PROVIDERS, BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY USE, INTERRUPTION,
DELAY, OR INABILITY TO USE THE SOFTWARE; LOST REVENUES OR PROFITS; DELAYS,
INTERRUPTION, OR LOSS OF SERVICES, BUSINESS, OR GOODWILL; LOSS OR CORRUPTION OF DATA;
LOSS RESULTING FROM SYSTEM OR SYSTEM SERVICE FAILURE, MALFUNCTION, OR SHUTDOWN;
FAILURE TO ACCURATELY TRANSFER, READ, OR TRANSMIT INFORMATION; FAILURE TO UPDATE OR
PROVIDE CORRECT INFORMATION; SYSTEM INCOMPATIBILITY OR PROVISION OF INCORRECT
COMPATIBILITY INFORMATION; OR BREACHES IN SYSTEM SECURITY; OR FOR ANY
CONSEQUENTIAL, INCIDENTAL, INDIRECT, EXEMPLARY, SPECIAL, OR PUNITIVE DAMAGES,
WHETHER ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, BREACH OF CONTRACT,
TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, REGARDLESS OF WHETHER SUCH DAMAGES
WERE FORESEEABLE AND WHETHER OR YOU WERE ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES;
b. IN NO EVENT WILL BCI'S AND ITS AFFILIATES', INCLUDING ANY OF ITS OR THEIR RESPECTIVE
LICENSORS' AND SERVICE PROVIDERS', COLLECTIVE AGGREGATE LIABILITY UNDER OR IN
CONNECTION WITH THIS AGREEMENT OR ITS SUBJECT MATTER, UNDER ANY LEGAL OR EQUITABLE
THEORY, INCLUDING BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY,
AND OTHERWISE, EXCEED TWO HUNDRED AND FIFTH DOLLARS (US$250); AND
c. THE LIMITATIONS SET FORTH IN THIS SECTION 6 SHALL APPLY EVEN IF YOUR REMEDIES UNDER
THIS AGREEMENT FAIL OF THEIR ESSENTIAL PURPOSE.

7. U.S. GOVERNMENT RIGHTS. The Software is commercial computer software, as such term is defined in
48 C.F.R. §2.101. Accordingly, if You are the US Government or any contractor therefor, You shall receive
only those rights with respect to the Software as are granted to all other end users under license, in
accordance with (a) 48 C.F.R. §227.7201 through 48 C.F.R. §227.7204, with respect to the Department of
Defense and their contractors, or (b) 48 C.F.R. §12.212, with respect to all other US Government licensees
and their contractors.
8. EXPORT REGULATION. The Software may be subject to US export control laws, including the US Export
Administration Act and its associated regulations. You shall not, directly or indirectly, export, re-export,
or release the Software to, or make the Software accessible from, any jurisdiction or country to which
export, re-export, or release is prohibited by law, rule, or regulation. You shall comply with all applicable
federal laws, regulations, and rules, and complete all required undertakings (including obtaining any
necessary export license or other governmental approval), prior to exporting, re-exporting, releasing, or
otherwise making the Software available outside the US.

Warranty-2 C48508AA
 Beckman Coulter, Inc. End-User License Agreements
CellMek Panel Designer Software

9. INTELLECTUAL PROPERTY RIGHTS. You acknowledge and agree that the Software is provided under
license, and not sold, to You. You do not acquire any ownership interest in the Software under this
Agreement, or any other rights thereto, other than to use the same in accordance with the license
granted and subject to all terms, conditions, and restrictions under this Agreement. BCI shall retain its
entire right, title, and interest in and to the Software and all intellectual property rights arising out of or
relating to the Software, except as expressly granted to You in this Agreement. You shall use
commercially reasonable efforts to safeguard all Software (including all copies thereof) from
infringement, misappropriation, theft, misuse, or unauthorized access.
10. THIRD PARTY COMPONENTS; ADDITIONAL TERMS. The Software may contain or be delivered with one
or more components, which may include third-party components, identified by BCI in the
Documentation, readme.txt file, third-party click-accept or elsewhere (e.g., on www.beckman.com or
attached to this Agreement as an appendix) (the "Identified Component(s)") as being subject to different
license agreement terms, disclaimers of warranties, limited warranties or other terms and conditions
(collectively, "Additional Terms") than those set forth herein. You agree to the applicable Additional
Terms for any such Identified Component(s).
11. MISCELLANEOUS. You may not assign this Agreement or any of Your rights hereunder without BCI's
prior written consent and any attempt to do so without such consent shall cause this Agreement and any
of Your associated rights hereunder to be null and void. No failure to exercise any right hereunder will
operate as a waiver thereof. If any provision of this Agreement shall be adjudged by any court of
competent jurisdiction to be unenforceable or invalid, that provision shall be limited or eliminated to the
minimum extent necessary so that this Agreement shall otherwise remain in full force and effect and
enforceable. This Agreement shall be construed in accordance with the laws of the State of California and
the United States without regard to conflicts of laws, provisions thereof and without regard to the United
Nations Convention on Contracts for the International Sale of Goods. The sole and exclusive jurisdiction
and venue for any actions related to the subject matter hereof shall be the state and U.S. federal courts
located in the County of Orange, California. You irrevocably submit to the jurisdiction of such courts and
consent to venue in such forum with respect to any action or proceeding that relates to this Agreement.
The prevailing party in any action to enforce this Agreement shall be entitled to recover its reasonable
costs and expenses including reasonable attorneys' fees. No amendment to or modification of this
Agreement will be binding unless in writing and signed by a duly authorized officer of BCI. This
Agreement is in the English language only, which language shall be controlling and any revision of this
Agreement in any other language shall not be binding. Both parties agree that this Agreement is the
complete and exclusive statement of the mutual understanding of the parties relating to the subject
matter of this Agreement.

C48508AA Warranty-3
 Beckman Coulter, Inc. End-User License Agreements
CellMek Panel Designer Software

Warranty-4 C48508AA
 Related Documents
CellMek SPS Host Transmission
PN C48508

CellMek SPS Instructions for Use

PN C48507

www.beckman.com

© 2021 Beckman Coulter, Inc.

All Rights Reserved