No.: R.

RD-0110-01

LIS Communication Protocol

(F 8 Series Automatic Hematology Analyzer)

1/ 55
 Table of Contents
Chapter 1 Upgrade Record .................................................................................................. 4
1.1 Document Upgrade Record .............................................................................. 4
Chapter 2 Descriptions of LIS Communication Protocol................................................. 5
2.1 HL7 Interface Overview .................................................................................... 5
2.1.1 Connection ........................................................................................................ 5
2.1.2 Data sending..................................................................................................... 5
2.1.3 Disconnection ................................................................................................... 6
2.2 HL7 Message Layer Protocol ........................................................................... 6
2.2.1 HL7 upper layer message protocol .................................................................. 6
2.2.2 HL7 lower layer message protocol ................................................................... 6
Chapter 3 Introductions of HL7........................................................................................... 8
3.1 Basic Syntax of HL7 ......................................................................................... 8
3.1.1 Message structure rules ................................................................................... 8
3.1.2 String escape rules ........................................................................................... 8
3.2 HL7 Data Types ................................................................................................ 9
3.3 Message Types................................................................................................. 9
3.3.1 Reporting of observational results .................................................................... 9
3.3.2 Request information query ............................................................................. 10
3.4 Segment Descriptions ..................................................................................... 11
3.4.1 MSH ................................................................................................................ 12
3.4.2 MSA ................................................................................................................ 14
3.4.3 PID .................................................................................................................. 16
3.4.4 OBR ................................................................................................................ 17
3.4.5 OBX ................................................................................................................ 21
3.4.6 QRD ................................................................................................................ 24
3.4.7 QRF ................................................................................................................ 25
3.4.8 ERR ................................................................................................................ 27
3.4.9 QAK ................................................................................................................ 27
3.4.10 DSP................................................................................................................. 28
3.4.11 DSC ................................................................................................................ 32
Chapter 4 Example of complete message ....................................................................... 34
4.1 Reporting of sample observational results ..................................................... 34
4.2 Reporting of QC Results................................................................................. 34

2/ 55
4.3 Query the Request Information of the Sample with Specified Barcode......... 35
4.4 Query the Request Information of the Sample in Specified Period ............... 36
Appendix A: Definition of HL7 Data Types ....................................................................... 40
Appendix B: OBX-3 Parameter Type Codes .................................................................... 43
Appendix C: Unit of Observation Items ............................................................................ 52
Appendix D: OBX-5 Observation Result Data .................................................................. 53
Appendix E: Base64 Encoding Flows............................................................................... 54

3/ 55
 Chapter 1 Upgrade Record

1.1 Document Upgrade Record

Version No. 01 Date of creation March 30, 2020

Version No. Date of creation

Reason

Contents

Version No. Date of creation

Reason

Contents

4/ 55
 Chapter 2 Descriptions of LIS Communication
Protocol

2.1 HL7 Interface Overview

maccura now has different types of medical devices, such as F 800, G 01, U 2000 and P100.
These devices communicate with LIS (Laboratory Information System) via Ethernet/serial
interface to send observational results on observation instruments to LIS or receive sample
request information from LIS.

The definition of this communication protocol is based on the HL7 standard (an electronic
data exchange standard in the medical field). The standard was originally defined by the
US-based Health Level Seven Committee and has been widely adopted by many countries.
The definition of this protocol is based on HL7 v2.4. Please refer to HL7 Interface Standards
Version 2.4 for the details about HL7.

Communication process

Instrument software sends messages via network interface/serial interface. The

communication process can be divided into three phases as follows.

2.1.1 Connection
After startup, the instrument software will automatically connect to LIS server. Upon
successful connection, the software will maintain the link to ensure data can be sent at any
time. In case of disconnection when the software is still running, the software will try to
reconnect to the server.

2.1.2 Data sending

For instrument software, message sending is synchronous with message receiving. In detail,
while sending a message, the software will always wait for an acknowledgment message. If
an acknowledgment message is received within 10s, the process of message sending is
completed and then the software will start sending the next message. If no acknowledgment
message is received after 10s, the software deems a failure to send the message. Then it
will skip this message and directly send the next message.

While intending to query the sample request information, the instrument will send a query
message, which contains such information as sample number and period of time. LIS will
query the sample information according to sample number, period of time and other related
information and make a response using HL7 messages. Then the instrument software
performs subsequent operations according to the received message. If no response
message is received 10s after the query message is sent, a query failure has occurred.

5/ 55
2.1.3 Disconnection
When the instrument software quits operation, it will automatically close the communication
link. While changing any communication setting, the software will also close the current link
and connect to LIS according to the latest settings.

2.2 HL7 Message Layer Protocol

2.2.1 HL7 upper layer message protocol
The communication of sample results and other related data information complies with
UTF-8 coded character strings.

Message strings are organized according to the HL7 standard. In detail, a message consists
of multiple segments, each message is divided into multiple fields, each field is divided into
multiple components and each component is divided into multiple sub components.
Segment, field, component and sub component are spaced by separators.

Some HL7 message samples are presented as follows:

MSH|^~\&|F 800|1268-1478a123|PC-1 LIS|PC-1|20180123075742||ORU^R01|1|P|2.4||||||UTF-8

PID|1||987654321||Mark||19810506000000|M

OBR|1|123456789||maccura|Y||||0

OBX|0|NM|00008^XR QCR Mean^99MRC|FT4|3.1400000000000001||||||F

OBX|1|ST|704-7^BAS#^LN|TSH|+||||||F

OBX|2|ED|706-2^BAS%^LN|AFP|^Application^Octer-stream^Base64^AQIDBAUGBxE6S1xtfo+g/v8=||||||F

2.2.2 HL7 lower layer message protocol

Known as a byte stream protocol, TCP/IP does not provide any message boundary. While
serving as an upper layer protocol, HL7 is based on messages. It does not provide a
message termination mechanism. In order to determine message boundaries, we have
applied MLLP (Minimal Lower Layer Protocol) (you can find the corresponding description in
HL7 Interface Standards Version 2.4).

Messages are sent in the format below:

<SB> ddddd <EB><CR>

Where,

<SB> = Start Block character (1 byte)

ASCII <VT>, also <0x0B>. Do not confuse with SOH or STX in ASCII.

ddddd = Data (variable number of bytes)

dddd is defined as the valid data of HL7 message and expressed through UTF-8 coded
character string.

6/ 55
<EB> = End Block character (1 byte)

ASCII <FS>, also <0x1C>. Do not confuse with ASCII character ETX or EOT.

<CR> = Carriage Return (1 byte)

ASCII carriage return, also <0x0D>.

7/ 55
 Chapter 3 Introductions of HL7
3.1 Basic Syntax of HL7
3.1.1 Message structure rules
A HL7 message consists of some segments. Each segment ends with character <CR>.

Each segment consists of a three-character segment name and a variable number of fields.
Each field comprises components and sub components. Separators are defined in the MSH
segment of each message for field, component and sub-component.

For example,

MSH|^~\&|F 800|1268-1478a123|PC-1 LIS|PC-1|20180123075742||ORU^R01|1|P|2.4||||||UTF-8

Where,

The five characters following MSH define the separators that differentiate fields,
components and sub components. These characters can be any non-text characters.
However, the HL7 standard recommends the characters in the following table:

Character Meaning

| Field separator

^ Component separator

& Sub component separator

~ Repetition separator

\ Escape character

The first field of MSH contains all the separators. Some of the following fields are empty
because they are optional and not used by the HL7 interface of instrument software.
Detailed field definitions and selections are given in other chapters.

For any type of message, the segments following MSH have constant sequences, which will
be detailed in the following sections.

3.1.2 String escape rules

Escape separators may appear in ST, TX, FT, CT and other types of field data, such as
remarks, diagnosis information, user-defined gender and other string data. Convert the
separators in the original string into escape character sequences while encoding and
restore them while decoding. The escape rules used by the HL7 interface are described as
follows:

8/ 55
 Escape character Original characters
sequence

\F\ Field separator

\S\ Component separator

\T\ Sub component separator

\R\ Repetition separator

\E\ Escape character

\X000d\ <CR>, also the terminator

of a segment

Note: ‘\’ in the escape string sequence represents an escape separator with its value defined
in the MSH segment.

3.2 HL7 Data Types

All data information in a message is represented by different HL7 type fields. At present,
only some of communication protocols provided by the HL7 standard have been used. For
details, please refer to Subsection 0.

3.3 Message Types

In the process of communication, four message structures, including ORU^R01, ACK^R01,
QRY^Q01 and DSR^Q01, are involved in the HL7 communication protocol.

3.3.1 Reporting of observational results

ORU^R01 and ACK^R01 appear in pair to send sample observational results (or quality
control data) to LIS. See the schematic diagram below:

Instrument

9/ 55
Message ORU^R01: Mainly used for the transmission of observational results and quality
control (QC) data.

ORU Observational Results (Unsolicited) Descriptions

MSH Message Header

PID Patient Information

OBR Sample Information

{[OBX]} Test Data

Message ACK^R01: Acknowledge any received message ORU^R01.

ACK Acknowledgment Descriptions

MSH Message Header

MSA Message Acknowledgment

Note: The segment in [ ] is optional and the segment in {} can be repeated once or several times.

3.3.2 Request information query

QRY^Q01 and DSR^Q01 appear in pair to acquire sample request information from LIS.
See the schematic diagram below:

Instrument

Message QRY^Q01: Used to query the necessary sample request information in LIS.

10/ 55
QRY Query Message Descriptions

MSH Message Header

QRD Query Definition

[QRF] Query Filter

Message DSR^Q01: Mainly used to send and display query results. In detail, LIS is enabled
to send the necessary sample request information to instruments.

DSR Display Response Message

Descriptions

MSH Message Header

MSA Message Acknowledgment

[ERR] Error

[QAK] Query Acknowledgment

[QRD] Query Definition

[QRF] Query Filter

{DSP} Display Data Segment

[DSC] Continuation Pointer

Note: The segment in [ ] is optional and the segment in {} can be repeated once or several times.

3.4 Segment Descriptions

The definition of fields contained in each segment will be detailed in the following list. A row
in the table corresponds to a field in the segment. The meaning of each row in the table is
given as follows:

1. No.: A HL7 segment starts with a three-character segment name. Each field separator
is followed by the contents of one field and the number indicates the sequence of a field in
the HL7 segment.

Example:

PID | 1 | |987654321||Mark||19810506000000|M

↑ ↑ ↑

Segment name Field 1 Field 3

Note: MSH segments differ slightly. The field separator closely following the segment name is regarded as
the first field to describe the value of the field separator used for the entire message.

11/ 55
2. Field name: Logical meaning of a field.

3. Data type: These fields are of HL7 standard types and their structures are described in
Subsection 0.

4. Recommended maximum length: It is also the length recommended by the HL7

standard. However, the actual transmission length exceeds this value during actual
message transmissions. Therefore, use separators as identifiers to read message fields
while parsing a message.

5. Descriptions: Descriptions about actual values of each field.

6. Example: Example of actual values of each field.

3.4.1 MSH
The segment MSH (Message Header) contains the basic information of HL7 message, such
as message separator value, message type and message encoding mode. It is also the first
segment of each HL7 message.

Example message:

MSH|^~\&|F 800|1268-1478a123|PC-1 LIS|PC-1|20180123075742||ORU^R01|1|P|2.4||||||UTF-8

See the table below for the definition of each field in a MSH segment:

Table 1 Definitions of MSH Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Field ST 1 It contains the first field |

Seperator separator following
segment name to
determine the value of
other field separators in a
message.

2 Encoding ST 4 It contains component ^~\&

Characters separator, repetition
separator, escape
separator and sub
component separator.

3 Sending HD 180 Model of sending facility,

application select one of the following F 800
values:

12/ 55
 F 800: Hematology analyzer

G 01: Glycosylated
hemoglobin analyzer

U 2000: Urine analyzer

P 100: C-reactive protein

analyzer

P300: Urine biochemical

analyzer

i 1000: Immunoassay
equipment

i 3000: Immunoassay
equipment

RIS: Intermediate

4 Sending HD 180 Serial number of sending xxxx-xxxxxx

Facility facility

7 Date/Time TS 26 Message creation date 20180123075742

Of and time
Message (YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

9 Message CM 7 Message type, for ORU^R01

Type example “Message
Type^Event Type”.

10 Message ST 20 Message control ID, used 1

Control ID to uniquely identify a
message.

11 Processing PT 3 Message processing ID, P

ID values:

“P”: Sample test result and

sample request
information query;

“Q”: QC test result;

In ACK message, it is
consistent with the

13/ 55
 previously received
message.

12 Version ID VID 60 HL7 version number, also 2.4

“2.4”

18 Character ID 10 Character set, value UTF-8

Set “UTF-8”; communication
messages are
represented by UTF-8
encoded strings.

3.4.2 MSA
MSA (Message Acknowledgment) segment contains message acknowledgment
information.

Example message:

MSA|AA|1

See the table below for the definition of each field in a MSA segment:

Table 2 Definitions of MSA Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Acknowledgement ID 2 Acknowledgment code. AA

Code
“AA”: Accepted;

“AE”: Error;

"AR”: Rejected;

2 Message Control ST 20 Message control ID, the 1

ID same as MSH-10 in the
corresponding received
message.

6 Error Condition CE 100 Error condition (status 0

code). Refer to Table 3
for the value.

14/ 55
 Table 3 List of Error Codes

Status codes (MSA-6) Status texts (MSA-3) Descriptions/Remarks

Succeeded: AA

0 Message accepted Succeeded

Error status codes: AE

8 Query Result Empty The query result is empty

and no valid is record is
found

100 Segment sequence error The sequence of segments

in a message is not correct
or any required segment is
missing

101 Required field missing Any required field in a

segment is missing

102 Data type error The data type of field is

incorrect, for example, the
number becomes a
character

103 Table value not found Table value is not found

and will not be used
temporarily

Rejection status codes: AR

200 Unsupported message type The message type is not

supported

201 Unsupported event code The event code is not

supported

15/ 55
202 Unsupported processing id The processing ID is not
supported

203 Unsupported version id The version ID is not

supported

204 Unknown key identifier Unknown keyword

identifier, for example
transmission of patient
information that does not
exist

205 Duplicate key identifier Repeated keywords exist

206 Application record locked Service cannot be executed

at application storage level,
for example database is
locked

207 Application internal error Other unknown errors in an

application

3.4.3 PID
PID (Patient Identification) segment contains the basic information of a patient.

Example message:

PID|1||987654321||Mark|37&Y|19810506000000|M

See the table below for the definition of each field in a PID segment:

Table 4 Definition of PID Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Set ID – SI 4 Serial number, used to 1

PID identify different PID
segments in a message

3 Patient CX 20 Medical record No. 987654321

Identifier
List

16/ 55
4 Alternate CX 20 Bed No. 2
Patient ID
– PID

5 Patient XPN 48 Patient name Mark

Name

6 Mother’s XPN 10 Patient age and age unit 37&Y

Maiden
Y: Year
Name
M: Month

D: Day

H: Hour

7 Date/Time TS 26 Patient’s date of birth, for 19810506000000

of Birth example
YYYYMMDDHHmmSS.

8 Sex IS 1 Genders. M

“M”: Male

“F”: Female

“U”: Unknown

11 Patient XAD 106 Patient address No.1, Xiyuan

Avenue,
Chengdu

13 Phone XTN 40 Phone number 13666666666

Number –
Home

22 Ethnic CE 80 Ethnicity Han

Group

23 Birth Place ST 60 Place of birth (native place) Chengdu,

Sichuan

3.4.4 OBR
OBR (Observation Request) segment mainly contains observation report information.

Example message:

17/ 55
OBR|1|123456789||maccura|Y||||0

See the table below for the definition of each field in OBR during the transmission of
patient’s sample observation results (when MSH-11 is P):

Table 5 Definition of OBR Fields (Sample Observation Results)

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Set ID – SI 10 Serial number, used to 1

OBR determine different OBR
segments in a message

2 Placer EI 22 Sample barcode 123456789

Order
Number

3 Filler Order EI 22 Sample No. 2

Number

4 Universal CE 200 Universal service maccura

Service ID identifier, use
manufacturer
name^model

5 Priority ID 2 Emergency or not, Y (Yes) Y

or N (No)

6 Requested TS 26 Sample collection time 20180124080000

Date/time (form:
YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

7 Observation TS 26 Sample observation time 20180124100000

Date/Time (form:
YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

8 Observation TS 26 End time of sample 20180124100500

End observation (form:
Date/Time YYYYMMDDHHmmSS),

18/ 55
 subject to the time of
UTC+0.

9 Collection CQ 20 Manual dilution factor of 2

Volume sample

10 Collector XCN 60 Sample bit, consist of 1^3

Identifier sample rack
number^sample position

The test mode is the

combination of different
equipment test modes. All
modes are connected
through “+”. The test
modes of F 800 include:

CBC

DIFF

RET

AWS
Relevant
PCF
13 clinical ST 60 CBC+A1C+CRP
information Test modes of G 01
equipment:

A1C

Test mode of U 2000

equipment:

CHEM

SED

Test modes of P 100

equipment:

CRP

Time of sending sample

Specimen for observation (form:
14 Received TS 26 YYYYMMDDHHmmSS), 20180124090000
Date/Time subject to the time of
UTC+0.

19/ 55
15 Specimen SPS 300 Sample type, the default serum
Source values are as follows:

Serum

Plasma

Whole blood

Urine

CSF

Other

16 Ordering XCN 120 Referring physician Li Si

Provider

17 Order XCN 40 Referring department Internal medicine

Callback
Phone
Number

See the table below for the definition of each field in OBR during the transmission of item
QC test results (when MSH-11 is Q):

Table 6 Definition of OBR Fields (QC Test Results)

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Set ID – SI 10 Serial number, used to 1

OBR determine different OBR
segments in a message

2 Placer EI 22 Control solution number 123456789

Order
Number

4 Universal CE 200 Universal service maccura

Service ID identifier, use
manufacturer
name^model

20/ 55
7 Observation TS 26 Time of starting QC test 20180124100000
Date/Time (form:
YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

11 Specimen ID 50 Control solution type

Action Code

12 Danger CE 60 QC method
Code

13 Relevant ST 300 Control solution name

Clinical Info

14 Specimen TS 26 Shelf life of control 20180124080000

Received solution (form:
Date/Time YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

15 Specimen SPS 300 Control solution batch 1000

Source number

17 Order XCN 40 Control solution H: High;

Callback concentration level
M: Medium;
Phone
Number L: Low;

3.4.5 OBX
OBX (Observation Result) segment mainly contains the parameter information of
observation results.

Example message:

OBX|1|NM|6690-2^WBC^LN |WBC|5.32|10*9/L|10.00-11.00|L|||F

See the table below for the definition of each field in an OBX segment:

Table 7 Definition of OBX Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

21/ 55
1 Set ID - SI 10 Serial number, used to 1
OBX identify different OBX
segments in a message.

2 Value Type ID 3 Data types of observation NM

result. Select one of the
following values:

ST: String;

NM: Number;

ED: Compressed data, for

example image and byte
array;

WR: IP alarm information

(string actually);

3 Observation CE 590 Observation item 6690-2^WBC^LN

Identifier identification.

Its form is
“ID^Name^EncodeSys”.
ID is the observation item
identification, Name is the
description of observation
items and EncodeSys is
the encoding system of
observation items. Refer
to Subsection 0for the
encoding values of each
observation item.

Note: ID and EncodeSys

are used to determine a
unique observation
parameter. However,
Name only serves as
description and cannot be
used as an identification.

4 Observation ST 20 Item name WBC

Sub-ID

5 Observation * 65535 The data of observation 5.32

22/ 55
 Value results can be number,
string, byte array, image
data, etc. See Subsection
0for the specific value of
each field. Byte array and
image data are converted
by Base64 encoding
method. See Subsection
0 for the encoding method

6 Units CE 90 Unit of observation items. 10*9/L

All observation items are
expressed with ISO
standard units. See
Subsection 0for the units
used in communications.

7 References ST 90 Range of observation 10.00-11.00

Range results, form: “Lower limit
of reference range -
Upper limit of reference
range”, or “<Upper limit of
reference range”,
or >Lower limit of
reference range”.

8 Abnormal IS 5 Sign of observation L

Flags results with the following
values:

“N”: Normal

“H”: The result is higher

than the upper limit of
reference range

“L”: The result is lower

than the lower limit of
reference range

9 Probability ST 5 Qualitative observation +

result values (negative (-),
positive (+), weak positive
(+-), etc.)

23/ 55
10 Nature of ID 20 Qualitative reference 5
Abnormal values
Test

11 Observe ID 1 Status of observation F

Result results. Value “F” - (Final
Status Result) indicates the final
result.

14 Date/Time TS 26 Observation time (form: 20180124080000

of the YYYYMMDDHHmmSS),
Observation subject to the time of
UTC+0.

15 Producer's CE 60 Examining department Internal medicine

ID

16 Responsible XCN 80 Examining physician Wang Wu

Observer

17 Observation QC target value 3.0

CE 60
Method

18 Equipment QC standard deviation 1.0

Instance EI 60
Identifier

3.4.6 QRD
QRD (Query Definition) segment mainly contains query parameter information.

Example message:

QRD|20180124022123|R|I|1|||9999^RD|123456789|OTH|||T

See the table below for the definition of each field in a QRD segment:

Table 8 Definition of QRD Fields

No. Field Data Recommended Descriptions Example

name type maximum
length

1 Query TS 26 Current query generation 20180124022123

Date/Time time (form:
YYYYMMDDHHmmSS),

24/ 55
 subject to the time of
UTC+0.

2 Query ID 1 Query format code, R R

Format (record-oriented format)
Code

3 Query ID 1 Query priority, select I I

Priority (Immediate)

4 Query ID ST 10 Query ID, indicate different 1

queries

7 Quantity CQ 10 Quantity limit requirement, RD

Limited select RD (Records)
Request

8 Who XCN 60 Sample barcode/number 123456789

Subject
Filter

9 What CE 60 Requirements of query OTH

Subject result with the following
Filter values:

ASSAY_RESULT: Acquire
the latest result of the
observation item;

OTH: No special
requirements for query
results;

12 Query ID 1 Level of query results, T

Results select T (Full result)
Level

3.4.7 QRF
QRF (Query Filter) segment is used together with QRD to further refine the original query
contents.

Example message:

QRF|F 800|20180124022123|20180124032123|||RCT|COR|ALL

See the table below for the definition of each field in a QRF segment:

25/ 55
 Table 9 Definition of QRF Fields

No. Field Data Recommended Descriptions Example

name type maximum
length

1 Where ST 20 Requester location filter,

Subject also equipment model,
Filter select one of the following
values:

F 800: Hematology analyzer

G 01: Glycosylated hemoglobin

analyzer

U 2000: Urine analyzer

P 100: C-reactive protein

analyzer
F 800
P 300: Urine biochemical
analyzer

i 1000: Immunoassay
equipment

i 3000: Immunoassay
equipment

RIS: Intermediate

LMS: Line Management

System

2 When TS 26 Start of sample receiving 20180124022123

Data Start time (form:
Date/Time YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

3 When TS 26 End of sample receiving 20180124032123

Data End time (form:
Date/Time YYYYMMDDHHmmSS),
subject to the time of
UTC+0.

4 What User ST 60 Sample rack number Rack001

26/ 55
 Qualifier

5 Other QRY ST 60 Slot position number, also 1

Subject the location of sample tube
Filter on sample rack.

6 Which ID 12 Target type, select RCT RCT

Date/Time (Specimen receipt
Qualifier date/time, receipt of
specimen in filling
ancillary(Lab))

7 Which ID 12 Target status, select COR COR

Date/Time (Corrected only (no final
Status with corrections))
Qualifier

8 Date/Time ID 12 Date/Time selection ALL

Selection qualifier, select ALL (All
Qualifier values within the range)

3.4.8 ERR
ERR (Error) segment is used to add error descriptions to acknowledge messages.

Example message:

ERR|203

See the table below for the definition of each field in an ERR segment:

Table 10 Definition of ERR Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Error Code ELD 80 Error codes and locations 203

and
Location

3.4.9 QAK
QAK (Query Acknowledgment) segment contains some information that follows query
response.

Example message:

27/ 55
QAK|SR|OK

See the table below for the definition of each field in a QAK segment:

Table 11 Definition of QAK Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Query Tag ST 32 Query tag, select SR SR

(indicating the sample
request information)

2 Query ID 2 Query response status. OK

Response
OK: Data is found and no
Status
error has occurred

NF: Data is not found and no

error has occurred

AE: Application error

AR: Application rejection

3.4.10 DSP
DSP (Display Data) segment is used to display the sample request information and patient
information obtained through queries. It can be repeated.

Example message:

DSP|1||BingLiHao1

See the table below for the definition of each field in a DSP segment:

Table 12 Definition of DSP Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

1 Set ID – SI 4 Type code, used to 1

DSP determine the type of sample
properties.

2 Display SI 4 Level of display

Level

28/ 55
3 Data Line * 300 Data line, contents obtained BingLiHao1
through queries

4 Logical ST 2 Logical break point

Break Point

5 Result ID TX 20 Result ID

Field DSP-1 has designated the type of sample property and field DSP-3 indicates the value
of sample property.

See the table below for the type code and value of each property for the sample request
information. Where, sample barcode (type code: 21) and sample number (type code: 22)
are required properties.

As for those devices using modes to differentiate sample measurement tasks, such as F
800, G01, U 2000 and P 100, test mode (type code: 29) will be a required property.

With regard to the devices using items to be tested to differentiate sample measurement
tasks, such as i 1000, i 3000 and P 300, item information (type code: 1000) will be a
required property. When the sample contains more than one item to be tested, the
number will steadily increase from 1000 with the maximum increment of 100.

For RIS (intermediate) and LMS (Line Management System), both test mode (type code: 29)
and item information (type code: 1000) are required properties.

Type Items Values

code

1 Medical record No. string

2 Bed No. string

3 Patient name string

4 Date of birth string, form: YYYYMMDDHHmmSS (year, month, day, hour,

minute, second), for example 20171222093625

5 Gender char, M: Male; F: Female; U: Unknown

6 Blood type
string，O、A、B、AB

7 Ethnicity string

29/ 55
8 Patient address string

9 Postcode string

10 Phone number string

11 Sample position string, consist of sample rack number~sample position

12 Sample collection string, UTC+0, form: YYYYMMDDHHmmSS (year, month,

time day, hour, minute, second), for example 20171222093625

13 Marital status string

14 Religious belief string

15 Patient type string, outpatient; inpatient; other

16 Medical insurance string

account number

17 Charge type string, own; insurance

18 Ethnicity string

19 Native place (place string

of birth)

20 Country string

21 Sample barcode string

22 Sample No. string, also sample number or LIS short number.

23 Sample submission string, UTC+0, form: YYYYMMDDHHmmSS (year, month,

time day, hour, minute, second), for example 20171222093625

24 Emergency? char, Y: Yes, N: No

25 Manual dilution float

factor

26 Sample type string, select one of the following values:

30/ 55
 Serum

Plasma

Whole blood

Urine

CSF

Other

27 Referring physician string

28 Referring string
department

string, the test mode during initial sample observation, also

the combination of different equipment test modes, all modes
are spaced with “+”. F 800 has the following test modes:

CBC

DIFF

RET

AWS

PCF

Test modes of G 01 equipment:

A1C
29 Test modes
Test mode of U 2000 equipment:

CHEM

SED

Test modes of P 100 equipment:

CRP

Example value of the field is given as follows:

CRP+CBC+DIFF+A1C

Note: For F 800, G 01, U 2000, P 100, RIS and LMS, this field is
required.

31/ 55
30 Re-examination? char, Y: Yes, N: No

It has the same value with the field “measurement mode”

Re-examination
31 (type code: 29), indicating the measurement mode during
mode
sample re-examination.

32 Patient age Int

Char, select the following values:

Y: Year

33 Unit of patient age M: Month

D: Day

H: Hour

1000 Item information string, describe the information of items to be tested for the
sample, format:

Item number~Item name~Dilution factor~Normal range of observation

result values~Unit of observation result
values~Re-examination?~Latest observation results of item

See Subsection 0for the value of item number. Item number

is a required field but other fields are optional and the
continuous “~” at the end of the value can be omitted.

Note 1: For i 1000, i 3000, P 300, RIS and LMS, this field is required.

Note 2: If the value of QRD-9 is ASSAY_RESULT, this field is required

and the latest test results of the item should be provided.

… Item information string, describe the information of items to be tested for the
sample, have the same format as above.

3.4.11 DSC
DSC (Continuation Pointer Segment) is used to indicate whether it is the latest data
message in the response message.

Table 13 Definition of DSC Fields

No. Field name Data Recommended Descriptions Example

type maximum
length

32/ 55
1 Continuation ST 180 Continuation pointer. If this field is N
pointer empty, it indicates that the current
data is the last piece of data.
Otherwise, there is subsequent
data information.

While querying sample request information, one DSR information can only respond to one
piece of sample information. When multiple pieces of sample information exist, DSC
segment can be added after the DSR message to indicate the existence of subsequent
sample information.

33/ 55
 Chapter 4 Example of complete message

4.1 Reporting of sample observational results

Taking the sample as a unit, the instrument software sends sample observation results to
LIS server. In other words, a sample and the observation results contained herein are sent
as a message. After judging the message, LIS server makes a corresponding response.

(1) Example of sample message

<SB>MSH|^~\&|F 800|1268-1478a123|||20180123075742||ORU^R01|1|P|2.4||||||UTF-8<CR>
PID|1||987654321||Mark||19810506000000|M<CR>
OBR|1|123456789||maccura|Y||||0<CR>
OBX|0|NM|6690-2^WBC^LN|WBC|3.14|10*3/uL|||||F<CR>
OBX|1|ST|704-7^BAS#^LN|TSH|+||||||F<CR>
OBX|2|ED|F800-IMG1^DIFF image^99MRC||^Image^BMP^Base64^.…DIFF histogram data… ||||||F<CR>
OBX|3|ED|F800-IMG2^WPC image^99MRC||^Image^BMP^Base64^...WPC histogram data…||||||F<CR>
OBX|4|ED|F800-WARN2^NEUTROPENIA^99MRC||Neutropenia||||||F<CR>
<EB><CR>

(2) Example of sample response message

After receiving the message, LIS server firstly judges the conformity and type of this
message and then make corresponding response. The response under normal conditions is
shown as follows:

<SB>MSH|^~\&|||F 800|1268-1478a123|20180123075743||ACK^R01|1|P|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
<EB><CR>

If LIS server detects an error in the received ORU message, the corresponding error code
can be set in the MSA segment and then returned. If the rejection error (error code 206)
occurs to LIS server, the ACK message in response is

<SB>MSH|^~\&|||F 800|1268-1478a123|20180123075743||ACK^R01|1|P|2.4||||||UTF-8<CR>
MSA|AR|1|Application record locked|||206<CR>
<EB><CR>

Note: The ID (MSH-10) of the response message must be the same as that of the sample message;

4.2 Reporting of QC Results

(1) Example of QC message

<SB>MSH|^~\&|F 800|1268-1478a123|||20180123075742||ORU^R01|1|Q|2.4||||||UTF-8<CR>
OBR|1|123456789||maccura|||20180124100000||||||level1|20200124080000|1000|L<CR>
OBX|0|NM|6690-2^WBC^LN|WBC|3.14|10*3/uL|||||F||||3.0|1.0<CR>

34/ 55
 <EB><CR>

(2) Example of QC response message

The only difference between QC response message and sample response message lies in
that the value of field MSH-11 is Q.

The following is an X-R QC message ACK.

<SB>MSH|^~\&|||F 800|1268-1478a123|20180123075743||ACK^R01|1|Q|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
<EB><CR>

Note: The ID (MSH-10) of the response message must be the same as that of the QC message;

4.3 Query the Request Information of the Sample with Specified

Barcode

(1) Example of query request message

The value of MSH-9 message type field is QRY^Q01. Fill QRD-8 with sample number. In this
example, fill the field with SampleID1.

<SB>MSH|^~\&|F 800|1268-1478a123| | |20180125062608||QRY^Q01|1|P|2.4||||||UTF-8<CR>

QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD|SampleID1|OTH|||T<CR>
QRF| F 800|||||RCT|COR|ALL<CR>
<EB><CR>

(2) Example of query request response message

LIS query request message contains sample number. After receiving the message, LIS
queries the patient and sample information response corresponding to the sample.

<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|1|P|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD|SampleID1|OTH|||T<CR>
QRF| F 800|||||RCT|COR|ALL<CR>
DSP|1||BingLiHao1<CR>
DSP|2||ChuangHao1<CR>
DSP|3||Name1<CR>
DSP|4||19870609102137<CR>
DSP|5||M<CR>
DSP|6||A<CR>
DSP|7||ZhongZu1<CR>
DSP|8||DiZhi1<CR>
DSP|9||CountryCode1<CR>
DSP|10||HomePhoneNumber1<CR>
DSP|11||SamplePosition1<CR>

35/ 55
 DSP|12||20171221080102<CR>
DSP|13||HunYin1<CR>
DSP|14||ZongJiao1<CR>
DSP|15||InPatient<CR>
DSP|16||SheBaoZhangHao1<CR>
DSP|17||own<CR>
DSP|18||MinZu1<CR>
DSP|19||JiGuan1<CR>
DSP|20||GuoJia1<CR>
DSP|21||TiaoMa1<CR>
DSP|22||YangBenHao1<CR>
DSP|23||20171221080102<CR>
DSP|24||Y<CR>
DSP|25||1.1<CR>
DSP|26||serum<CR>
DSP|27||Doctor1<CR>
DSP|28||Department1<CR>
DSP|29||CBC<CR>
DSP|30||31<CR>
DSP|31||Y<CR>
<EB><CR>

Note: The ID (MSH-10) of the response message must be the same as that of the query request
message;

If no valid record is found, the response message is as follows:

<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|1|P|2.4||||||UTF-8<CR>
MSA|AE|8<CR>
<EB><CR>

4.4 Query the Request Information of the Sample in Specified

Period

(1) Example of query request message

The value of MSH-9 message type field is QRY^Q01. Fill QRF-2 with the start time of

receiving sample and QRF-3 with the end time of receiving sample.

<SB>MSH|^~\&|F 800|1268-1478a123| | |20180125062608||QRY^Q01|1|P|2.4||||||UTF-8<CR>

QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD| |OTH|||T<CR>
QRF| F 800|20180125000000|20180125235959|||RCT|COR|ALL<CR>
<EB><CR>

(2) Example of query request response message

36/ 55
The LIS query request message contains the sample receiving period. After receiving the
request, LIS queries the patient corresponding to the sample and responds to the sample
information. Each response message contains the complete information of one sample. If
multiple pieces of sample information exist, use DSC section to indicate whether there is
any subsequent sample information.

If there are three samples that have met criteria in the specified period, three messages will
be continuously given as response. The first response message is as follows:

<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|1|P|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD| |OTH|||T<CR>
QRF| F 800|20180125000000|20180125235959|||RCT|COR|ALL<CR>
DSP|1||BingLiHao1<CR>
DSP|2||ChuangHao1<CR>
DSP|3||Name1<CR>
DSP|4||19870609102137<CR>
DSP|5||M<CR>
DSP|6||A<CR>
DSP|7||ZhongZu1<CR>
DSP|8||DiZhi1<CR>
DSP|9||CountryCode1<CR>
DSP|10||HomePhoneNumber1<CR>
DSP|11||SamplePosition1<CR>
DSP|12||20171221080102<CR>
DSP|13||HunYin1<CR>
DSP|14||ZongJiao1<CR>
DSP|15||InPatient<CR>
DSP|16||SheBaoZhangHao1<CR>
DSP|17||own<CR>
DSP|18||MinZu1<CR>
DSP|19||JiGuan1<CR>
DSP|20||GuoJia1<CR>
DSP|21||TiaoMa1<CR>
DSP|22||YangBenHao1<CR>
DSP|23||20171221080102<CR>
DSP|24||Y<CR>
DSP|25||1.1<CR>
DSP|26||serum<CR>
DSP|27||Doctor1<CR>
DSP|28||Department1<CR>
DSP|29||CBC<CR>
DSP|30||31<CR>
DSP|31||Y<CR>
DSC|1<CR>

37/ 55
<EB><CR>

Note: The ID (MSH-10) of the first response message must be the same as that of the query request
message;

The second response message is shown as follows:

<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|2|P|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD| |OTH|||T<CR>
QRF| F 800|20180125000000|20180125235959|||RCT|COR|ALL<CR>
DSP|1||BingLiHao2<CR>
DSP|2||ChuangHao2<CR>
DSP|3||Name2<CR>
DSP|4||19970609112137<CR>
DSP|5||F<CR>
DSP|6||B<CR>
DSP|7||ZhongZu2<CR>
DSP|8||DiZhi2<CR>
DSP|9||CountryCode2<CR>
DSP|10||HomePhoneNumber2<CR>
DSP|11||SamplePosition2<CR>
DSP|12||20171221080102<CR>
DSP|13||HunYin2<CR>
DSP|14||ZongJiao2<CR>
DSP|15||InPatient<CR>
DSP|16||SheBaoZhangHao2<CR>
DSP|17||own<CR>
DSP|18||MinZu2<CR>
DSP|19||JiGuan2<CR>
DSP|20||GuoJia2<CR>
DSP|21||TiaoMa2<CR>
DSP|22||YangBenHao2<CR>
DSP|23||20171221080102<CR>
DSP|24||N<CR>
DSP|25||2.2<CR>
DSP|26||urine<CR>
DSP|27||Doctor2<CR>
DSP|28||Department2<CR>
DSP|29||CBC+DIFF+CRP<CR>
DSP|30||21<CR>
DSP|31||Y<CR>
DSC|1<CR>
<EB><CR>

The last response message is as follows. Note that it has no DSC segment.

38/ 55
<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|3|P|2.4||||||UTF-8<CR>
MSA|AA|1<CR>
QRD|20180125062608|R|I|a47d7494-0b97-46bc-a0fe-aa491a844c2f|||^RD| |OTH|||T<CR>
QRF| F 800|20180125000000|20180125235959|||RCT|COR|ALL<CR>
DSP|1||BingLiHao3<CR>
DSP|2||ChuangHao3<CR>
DSP|3||Name3<CR>
DSP|4||20170609112137<CR>
DSP|5||F<CR>
DSP|6||B<CR>
DSP|7||ZhongZu3<CR>
DSP|8||DiZhi3<CR>
DSP|9||CountryCode3<CR>
DSP|10||HomePhoneNumber3<CR>
DSP|11||SamplePosition3<CR>
DSP|12||20171221080102<CR>
DSP|13||HunYin3<CR>
DSP|14||ZongJiao3<CR>
DSP|15||InPatient<CR>
DSP|16||SheBaoZhangHao3<CR>
DSP|17||own<CR>
DSP|18||MinZu3<CR>
DSP|19||JiGuan3<CR>
DSP|20||GuoJia3<CR>
DSP|21||TiaoMa3<CR>
DSP|22||YangBenHao3<CR>
DSP|23||20171221080102<CR>
DSP|24||Y<CR>
DSP|25||3.3<CR>
DSP|26||plasma<CR>
DSP|27||Doctor3<CR>
DSP|28||Department3<CR>
DSP|29||A1C+CBC+DIFF+AWS+CRP<CR>
DSP|30||11<CR>
DSP|31||Y<CR>
<EB><CR>

If no valid record is found, the response message is as follows:

<SB>MSH|^~\&|||F 800|1268-1478a123|20180125062610||DSR^Q01|1|P|2.4||||||UTF-8<CR>
MSA|AE|8<CR>
<EB><CR>

39/ 55
Appendix A: Definition of HL7 Data Types

CE - Code Element

<identifier (ST)> ^ <text (ST)> ^ <name of coding system (IS)> ^ <alternate identifier(ST)> ^
<alternate text (ST)> ^ <name of alternate coding system (IS)>

⚫ CM – Composite

The format of the union consisting of other data fields that have respective meanings is
defined by specific fields.

⚫ CX - Extended composite ID with check digit

<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed(ID)> ^
< assigning authority (HD)> ^ <identifier type code (ID)> ^ < assigning facility (HD)> ^
<effective date (DT)> ^ <expiration date (DT)>

⚫ ED – Encapsulate Data

<source application (HD)> ^ <type of data (ID)> ^ <data sub type (ID)> ^ <encoding (ID)> ^
<data (ST)>

⚫ EI - Entity Identifier

<entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type

(ID)>

⚫ FC – Financial Class

<financial class (IS)> ^ <effective date (TS)>

⚫ FT - Formatted text

This data type is derived from the string data type by allowing the addition of embedded
formatting instructions. These instructions are limited to those that are intrinsic and
independent of the circumstances under which the field is being used.

⚫ HD - Hierarchic designator

40/ 55
<namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>

⚫ IS - Coded value for user-defined tables

The value of such a field follows the formatting rules for an ST field except that it is drawn
from a site-defined (or user-defined) table of legal values. There shall be an HL7 table
number associated with IS data types.

⚫ ID - Coded values for HL7 tables

The value of such a field follows the formatting rules for an ST field except that it is drawn
from a table of legal values. There shall be an HL7 table number associated with ID data
types.

⚫ NM – Numeric

A number represented as a series of ASCII numeric characters consisting of an optional

leading sign (+ or -), the digits and an optional decimal point.

⚫ PL - Person location

<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ < location status (IS)> ^
<person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>

⚫ PT - Processing type

<processing ID (ID)> ^ <processing mode (ID)>

⚫ SI - Sequence ID

A non-negative integer in the form of an NM field. The uses of this data type are defined
in the chapters defining the segments and messages in which it appears.

⚫ ST – String

⚫ TS - Time stamp

YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ] ^ <degree of precision>

41/ 55
⚫ VID - Version identifier

<version ID (ID)> ^ <internationalization code (CE)> ^ <international version ID (CE)>

⚫ XCN - Extended composite ID number and name

<ID number (ST)> ^ <family name (FN)> ^ <given name (ST)> ^ <second and further given
names or initials thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^
<degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type
code (ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme
employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name
representation code (ID)> ^ <name context (CE)> ^ <name validity range (DR)> ^ <name
assembly order (ID)>

⚫ XPN - Extended person name

<family name (FN)> ^ <given name (ST)> & <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD)
(IS)> ^ <name type code (ID) > ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>

42/ 55
 Appendix B: OBX-3 Parameter Type Codes
Each OBX segment contains one check parameter or other data item information. OBX-2
indicates the HL7 data type of carried data items. OBX-3 (Observation Identifier) is the
identifier of data item with the expression of “ID^Name^EncodeSys”. OBX-5 contains the
value of data item and OBX-6 contains ISO standard units for parameter items.

The value range of OBX segment for F 800, G 01, U 2000 and P 100 is respectively
described in the following subsections.

B.1. OBX segment of F 800 equipment

Data item Type Unit Code (ID) Name Example of OBX-3 Corre
descriptions (OBX-2 (OBX-6) fields spond
) ing
test
mode
Data items of observation results
Number of white NM 10*9/L 6690-2 WBC 6690-2^WBC^LN CBC
blood cells
Number of red NM 10*12/L 789-8 RBC 789-8^RBC^LN CBC
blood cells
Hemoglobin NM g/L 718-7 HGB 718-7^HGB^LN CBC
concentration
Hematocrit NM % 4544-3 HCT 4544-3^HCT^LN CBC
Mean corpuscular NM fL 62242-3 MCV 62242-3^MCV^LN CBC
volume
Mean corpuscular NM pg 62243-1 MCH 62243-1^MCH^LN CBC
hemoglobin
content
Mean corpuscular NM g/L 62246-4 MCHC 62246-4^MCHC^L CBC
hemoglobin N
concentration
Platelets NM 10*9/L 777-3 PLT 777-3^PLT^LN CBC
Standard NM fL 21000-5 RDW-SD 21000-5^RDW-SD CBC
deviation of red ^LN
cell distribution
width
Variation NM % 62247-2 RDW-CV 62247-2^RDW-CV CBC
coefficient of red ^LN
blood cell
distribution width
Platelet NM fL 32207-3 PDW 32207-3^PDW^LN CBC
distribution width
Average platelet NM fL 32623-1 MPV 32623-1^MPV^LN CBC
volume

43/ 55
 Number of large NM 10*9/L 34167-7 P-LCC 34167-7^P-LCC^L CBC
platelets N
Platelet-large cell NM % 48386-7 P-LCR 48386-7^P-LCR^L CBC
ratio N
Thrombocytocrit NM % 51637-7 PCT 51637-7^PCT^LN CBC
Number of NM 10*9/L 30392-5 NRBC# 30392-5^NRBC#^ CBC
nucleated red LN
blood cells
Percentage of NM % 19048-8 NRBC% 19048-8^NRBC% CBC
nucleated red ^LN
blood cells
Neutrophil number NM 10*9/L 751-8 NEUT# 751-8^NEUT#^LN DIFF
Number of NM 10*9/L 731-0 LYMPH# 731-0^LYMPH#^L DIFF
lymphocytes N
Number of NM 10*9/L 742-7 MONO# 742-7^MONO#^L DIFF
monocytes N
Eosinophil number NM 10*9/L 711-2 EO# 711-2^EO#^LN DIFF
Basophil number NM 10*9/L 704-7 BAS# 704-7^BAS#^LN DIFF
Percentage of NM % 71676-1 NEUT% 71676-1^NEUT%^ DIFF
neutrophils LN
Percentage of NM % 71678-7 LYMPH% 71678-7^LYMPH DIFF
lymphocytes %^LN
Percentage of NM % 71677-9 MONO% 71677-9^MONO% DIFF
monocytes ^LN
Eosinophil NM % 71679-5 EO% 71679-5^EO%^LN DIFF
percentage
Basophil NM % 706-2 BAS% 706-2^BAS%^LN DIFF
percentage
Number of NM 10*9/L 53115-2 IG# 53115-2^IG#^LN DIFF
immature
granulocytes
Percentage of NM % 71695-1 IG% 71695-1^IG%^LN DIFF
immature
granulocytes
Reticulocyte NM % 17849-1 RET% 17849-1^RET%^L RET
percentage N
Reticulocyte NM 10*9/L 60474-4 RET# 60474-4^RET#^L RET
number N
Immature NM % 33516-6 IRF 33516-6^IRF^LN RET
reticulocyte ratio
Ratio of NM % 82591-9 LFR 82591-9^LFR^LN RET
reticulocytes with
low fluorescence

44/ 55
 intensity
Ratio of NM % 82592-7 MFR 82592-7^MFR^LN RET
reticulocytes with
medium
fluorescence
intensity
Ratio of NM % 51642-7 HFR 51642-7^HFR^LN RET
reticulocytes with
high fluorescence
intensity
Hemoglobin NM % 71694-4 RET-He 71694-4^RET-He^ RET
content of LN
reticulocytes
Immature platelet NM % 71693-6 IPF 71693-6^IPF^LN PCF
ratio (index)
White blood cell NM 10*9/L F800-ST1 WBC-A F800-ST1^WBC-A AWS
count calculated ^99MRC
from FCA channel
Total number of NM 10*9/L F800-ST2 TNC-A F800-ST2^TNC-A AWS
nucleated cells ^99MRC
calculated from
FCA channel
Intermediate data of observation results (WBC, RBC, PLT histogram and scattergram data)
WDF histogram ED F800-IMG1 WDF F800-IMG1^WDF
N/A N/A
bitmap data image image^99MRC
WNR histogram ED F800-IMG2 WNR F800-IMG2^WNR
N/A N/A
bitmap data image image^99MRC
RBC histogram ED F800-IMG3 RBC image F800-IMG3^RBC
N/A N/A
bitmap data image^99MRC
PLT histogram ED F800-IMG4 PLT image F800-IMG4^PLT
N/A N/A
bitmap data image^99MRC
WPC histogram ED F800-IMG5 WPC F800-IMG5^WPC
N/A N/A
bitmap data image image^99MRC
RET histogram ED F800-IMG6 RET image F800-IMG6^RET
N/A N/A
bitmap data image^99MRC
PLTF histogram ED F800-IMG7 PLTF F800-IMG7^PLTF
N/A N/A
bitmap data image image^99MRC
IP alarm information
F800-WARN1^W
Leukocyte WBC ABN
BC ABN
scattergram WR N/A F800-WARN1 SCATTER N/A
SCATTERGRAM^
abnormal GRAM
99MRC
Neutrophil NEUTROP F800-WARN2^NE
WR N/A F800-WARN2 N/A
decreased ENIA UTROPENIA^99M

45/ 55
 RC
F800-WARN3^NE
Neutrophil NEUTROP
WR N/A F800-WARN3 UTROPHILIA^99 N/A
increased HILIA
MRC
F800-WARN4^LY
Lymphopenia LYMPHOP
WR N/A F800-WARN4 MPHOPENIA^99 N/A
decreased ENIA
MRC
F800-WARN5^LY
Lymphocyte LYMPHOC
WR N/A F800-WARN5 MPHOCYTOSIS^ N/A
increased YTOSIS
99MRC
F800-WARN6^M
Monocyte MONOCYT
WR N/A F800-WARN6 ONOCYTOSIS^99 N/A
increased OSIS
MRC
F800-WARN7^EO
Eosinophil EOSINOP
WR N/A F800-WARN7 SINOPHILIA^99M N/A
increased HILIA
RC
F800-WARN8^BA
Basophils BASOPHIL
WR N/A F800-WARN8 SOPHILIA^99MR N/A
increased IA
C
F800-WARN9^LE
Leukocyte count LEUKOCY
WR N/A F800-WARN9 UKOCYTOPENIA N/A
decreased TOPENIA
^99MRC
F800-WARN10^L
White blood cell LEUKOCY
WR N/A F800-WARN10 EUKOCYTOSIS^9 N/A
count increased TOSIS
9MRC
F800-WARN11^N
Nucleated red
NRBC RBC
blood cell WR N/A F800-WARN11 N/A
PRESENT PRESENT^99MR
increased
C
F800-WARN12^I
Immature
IG G
granulocyte WR N/A F800-WARN12 N/A
PRESENT PRESENT^99MR
increased
C
BLASTSO F800-WARN13^B
Primitive
R LASTSOR
cells/abnormal WR N/A F800-WARN13 N/A
ABNLYMP ABNLYMPHO
lymphocytes?
HO S S^99MRC
F800-WARN14^A
Atypical ATYPICAL
WR N/A F800-WARN14 TYPICALLYMPH N/A
lymphocyte LYMPHO S
O S^99MRC
F800-WARN15^L
Left shift LEFT
WR N/A F800-WARN15 EFT SHIFT N/A
abnormal? SHIFT S
S^99MRC
Red blood cell WR N/A F800-WARN16 RBC ABN F800-WARN16^R N/A

46/ 55
 histogram DISTRIBU BC ABN
abnormal TION DISTRIBUTION^9
9MRC
DIMORPHI F800-WARN17^DI
Bimodal C MORPHIC
WR N/A F800-WARN17 N/A
erythrocyte POPULATI POPULATION^99
ON MRC
F800-WARN18^R
Reticulocyte RETICULO
WR N/A F800-WARN18 ETICULOCYTOSI N/A
increased CYTOSIS
S^99MRC
F800-WARN19^A
Red blood cell ANISOCYT
WR N/A F800-WARN19 NISOCYTOSIS^9 N/A
size uneven OSIS
9MRC
F800-WARN20^M
MICROCY
Microcytosis WR N/A F800-WARN20 ICROCYTOSIS^9 N/A
TOSIS
9MRC
F800-WARN21^M
MACROC
Macrocytosis WR N/A F800-WARN21 ACROCYTOSIS^ N/A
YTOSIS
99MRC
F800-WARN22^H
HYPOCHR
Hypopigmentation WR N/A F800-WARN22 YPOCHROMIA^9 N/A
OMIA
9MRC
F800-WARN23^A
Anaemia WR N/A F800-WARN23 ANEMIA N/A
NEMIA^99MRC
F800-WARN24^E
Erythrocyte ERYTHRO
WR N/A F800-WARN24 RYTHROCYTOSI N/A
increased CYTOSIS
S^99MRC
F800-WARN25^R
RBC
Erythrocyte BC
WR N/A F800-WARN25 AGGLUTI N/A
agglutination? AGGLUTINATION
NATION S
S^99MRC
F800-WARN26^T
TURBIDIT
URBIDITY OR
Chyle? WR N/A F800-WARN26 Y OR HGB N/A
HGB INTERF
INTERF S
S^99MRC
IRON F800-WARN27^IR
Iron deficiency? WR N/A F800-WARN27 DEFICIEN ON DEFICIENCY N/A
CY S S^99MRC
F800-WARN28^H
Hemoglobin HGB
WR N/A F800-WARN28 GB DEFECT N/A
abnormal? DEFECT S
S^99MRC
F800-WARN29^F
Red blood cell FRAGMEN
WR N/A F800-WARN29 RAGMENT N/A
fragment? TS
S^99MRC

47/ 55
 F800-WARN30^P
PLT ABN
Platelet histogram LT ABN
WR N/A F800-WARN30 DISTRIBU N/A
abnormal DISTRIBUTION^9
TION
9MRC
THROMB F800-WARN31^T
Platelet decreased WR N/A F800-WARN31 OCYTOPE HROMBOCYTOP N/A
NIA ENIA^99MRC
THROMB F800-WARN32^T
Platelet increased WR N/A F800-WARN32 OCYTOSI HROMBOCYTOSI N/A
S S^99MRC
F800-WARN33^P
Platelet PLT
WR N/A F800-WARN33 LT N/A
agglutination? CLUMPS
CLUMPS^99MRC
F800-WARN34^R
Reticulocyte RET ABN
ET ABN
scattergram WR N/A F800-WARN34 SCATTER N/A
SCATTERGRAM^
abnormal GRAM
99MRC
F800-WARN35^P
Platelet PLT ABN
LT ABN
scattergram WR N/A F800-WARN35 SCATTER N/A
SCATTERGRAM^
abnormal GRAM
99MRC
F800-WARN36^B
Primitive cell? WR N/A F800-WARN36 BLASTS S N/A
LASTS S^99MRC
F800-WARN37^A
Abnormal ABN
WR N/A F800-WARN37 BN LYMPHO N/A
lymphocytes? LYMPHO S
S^99MRC

B.2. OBX segment of G 01 equipment

Data item Typ Unit Code Name Example of OBX-3 fields Correspon
descriptions e (OBX-6) (ID) ding test
(OB mode
X-2)
Data items of observation results
A1c NM % G01-1 A1c NGSP G01-1^A1c A1C
concentration NGSP^99MRC
value under
NGSP standard
A1c NM mmol/mo G01-2 A1c IFCC G01-2^A1c A1C
concentration l IFCC^99MRC
value under
IFCC standard
Average blood NM mmol/L G01-3 A1c eAG G01-3^A1c eAG^99MRC A1C
glucose
concentration

48/ 55
 A1a area ratio NM % G01-4 A1a NGSP G01-4^A1a A1C
NGSP^99MRC
A1b area ratio NM % G01-5 A1b NGSP G01-5^A1b A1C
NGSP^99MRC
F area ratio NM % G01-6 F NGSP G01-6^F NGSP^99MRC A1C
LA1c area ratio NM % G01-7 LA1c G01-7^LA1c A1C
NGSP NGSP^99MRC
P3 area ratio NM % G01-8 P3 NGSP G01-8^P3 A1C
NGSP^99MRC
P4 area ratio NM % G01-9 P4 NGSP G01-9^P4 A1C
NGSP^99MRC
A0 area ratio NM % G01-10 A0 NGSP G01-10^A0 A1C
NGSP^99MRC
V area ratio NM % G01-11 V NGSP G01-11^V NGSP^99MRC A1C
S area ratio NM % G01-12 S NGSP G01-12^S A1C
NGSP^99MRC
C area ratio NM % G01-13 C NGSP G01-13^C A1C
NGSP^99MRC
UK area ratio NM % G01-14 UK NGSP G01-14^UK A1C
NGSP^99MRC
Intermediate data of observation results (histogram and scattergram data).
Total area NM N/A G01-10 Total Area G01-1000^Total A1C
00 Area^99MRC
Alarm code WR N/A G01-10 Alarm G01-1001^Alarm A1C
01 Code Code^99MRC
Raw data ED N/A G01-10 Raw Data G01-1002^Raw A1C
02 Data^99MRC
Result data ED N/A G01-10 Result G01-1003^Result A1C
03 Data Data^99MRC
Hemoglobin ED N/A G01-10 Hb Image G01-1004^Hb A1C
image 04 Image^99MRC

B.3. OBX segment of U 2000 equipment

Data item Type Unit Code Name Example of OBX-3 fields Correspondi
descriptions (OBX- (OBX- (ID) ng test mode
2) 6)
Data items of observation results
pH ST U2000-1 pH U2000-1^PH^99MRC CHEM
Specific ST U2000-2 SG U2000-2^SG^99MRC CHEM
density
Urobilinogen ST U2000-3 URO U2000-3^URO^99MRC CHEM
Vitamin C ST U2000-4 VC U2000-4^VC^99MRC CHEM
A/C ratio ST U2000-5 ACR U2000-5^AC^99MRC CHEM
Bilirubin ST U2000-6 BIL U2000-6^BIL^99MRC CHEM

49/ 55
Occult blood ST U2000-7 BLD U2000-7^BLD^99MRC CHEM
Protein ST U2000-8 PRO U2000-8^PRO^99MRC CHEM
Urine calcium ST U2000-9 Ca U2000-9^CA^99MRC CHEM
Creatinine ST U2000-1 Cr U2000-10^CR^99MRC CHEM
0
Glucose ST U2000-1 GLU U2000-11^GLU^99MRC CHEM
1
Micro-albumi ST U2000-1 MA U2000-12^MA^99MRC CHEM
n 2
Acetone ST U2000-1 KET U2000-13^KET^99MRC CHEM
3
White blood ST U2000-1 LEU U2000-14^LEU^99MRC CHEM
cell 4
Nitrite ST U2000-1 NIT U2000-15^NIT^99MRC CHEM
5
Chrominance ST U2000-1 COLOR U2000-16^COLOR^99MRC CHEM
6
Turbidity ST U2000-1 TURB U2000-17^TURB^99MRC CHEM
7
Crystal ST U2000-1 CRYS U2000-18^CRYS^99MRC SED
8
Transparent ST U2000-1 HYA U2000-19^HYA^99MRC SED
tube type 9
Bacteria ST U2000-2 BACT U2000-20^BACT^99MRC SED
0
Microzyme ST U2000-2 BYST U2000-21^BYST^99MRC SED
1
Viscose silk ST U2000-2 MUCS U2000-22^MUCS^99MRC SED
2
Non-squamo ST U2000-2 NEC U2000-23^NEC^99MRC SED
us epithelial 3
cells
Pathological ST U2000-2 PAT U2000-24^PAT^99MRC SED
tube type 4
Red blood ST U2000-2 RBC U2000-25^RBC^99MRC SED
cell 5
Squamous ST U2000-2 SEC U2000-26^SEC^99MRC SED
epithelial cell 6
Sperm ST U2000-2 SPRM U2000-27^SPRM^99MRC SED
7
Unknown ST U2000-2 UNKNOW U2000-28^UNKNOWN^99M SED
8 N RC
White blood ST U2000-2 WBC U2000-29^WBC^99MRC SED

50/ 55
 cell 9
Leukocyte ST U2000-3 WBCC U2000-30^WBCC^99MRC SED
mass 0
Urinary tract ST U2000-3 UTI U2000-31^UTI^99MRC SED
infection 1

B.4. OBX segment of P 100 equipment

Data item Type Unit Code (ID) Name Example of OBX-3 Corresponding
descriptions (OBX-2) (OBX-6) fields test mode
Data items of observation results
C-reactive NM mg/L 71426-1 CRP 71426-1^CRP^LN CRP
protein

51/ 55
Appendix C: Unit of Observation Items

All observation items are expressed in ISO standard units.

Table 14 Unit of Observation Items

Unit of parameters displayed on software interface Unit of observation items (OBX-6)

10^12/L 10*12/L
10^9/L 10*9/L
10^6/uL 10*6/uL
10^4/uL 10*4/uL
10^3/uL 10*3/uL
10^2/uL 10*2/uL
mL/L mL/L
/nL /nL
/pL /pL
g/L g/L
g/dL g/dL
L/L L/L
mmol/L mmol/L
% %
fL fL
um^3 um3
pg pg
fmol fmol
amol amol
Year (unit of age) yr
Month (unit of age) Mo
Day (unit of age) d
Hour (unit of age) hr

52/ 55
Appendix D: OBX-5 Observation Result Data

Observation results can be data types such as numbers, strings, byte arrays and images.
The following subsections describe their formats respectively.

D.1 Byte array

The value of data type field in OBX-2 field is “ED” and the value of OBX-5 data field shows
the form of “^Application^Octer-stream^Base64^……Byte Array Data……”. Where,
“^Application^Octer-stream^Base64” indicates the transmission of byte array data that first
goes through gzip compression and then Base64 transcoding.

bmp image

The value of OBX-2 data type field is “ED” and the value of OBX-5 data field shows the form
of “^Image^BMP^Base64^……bmp image data……”. Where “^Image^BMP^Base64”
indicates the transmission of bmp image data that first goes through gzip compression and
then Base64 transcoding.

D.2 jpg image

The value of OBX-2 data type field is “ED” and the value of OBX-5 data field shows the form
of “^Image^JPG^Base64^……jpg image data……”. Where “^Image^JPG^Base64” indicates
the transmission of jpg image data that first goes through gzip compression and then
Base64 transcoding.

D.3 png image

The value of OBX-2 data type field is “ED” and the value of OBX-5 data field shows the form
of “^Image^PNG^Base64^……png image data……”. Where “^Image^PNG^Base64”
indicates the transmission of png image data that first goes through gzip compression and
then Base64 transcoding.

53/ 55
Appendix E: Base64 Encoding Flows
(1) Take three adjacent bytes (also 24bit) to be encoded from the data stream, divide them
into four 6-bit groups from left to right and then obtain corresponding ASCII strings after
mapping according to Table 15. See the following contents:

Raw data: 0x15 0xA3 0x4B

Binary data: 00010101 10100011 01001011

The 6-bit group obtained after division: 000101 011010 001101 001011

Corresponding coded values: 0x05 0x1A 0x0D 0x0B

Corresponding characters: F a N L

Table 15 Base64 Mapping

Value/Code Value/Code Value/Code Value/Code

0 A 17 R 34 i 51 z

1 B 18 S 35 j 52 0

2 C 19 T 36 k 53 1

3 D 20 U 37 l 54 2

4 E 21 V 38 m 55 3

5 F 22 W 39 n 56 4

6 G 23 X 40 o 57 5

7 H 24 Y 41 p 58 6

8 I 25 Z 42 q 59 7

9 J 26 a 43 r 60 8

10 K 27 b 44 s 61 9

11 L 28 c 45 t 62 +

12 M 29 d 46 u 63 /

13 N 30 e 47 v

54/ 55
 14 O 31 f 48 w (pad) =

15 P 32 g 49 x

16 Q 33 h 50 y

(2) Repeat the encoding in Step (1) till the data stream encoding is completed.

When the remaining data is less than 3 bytes, fill 0 on the right side to make it up. If all the
6-bit groups obtained by encoding are composed of padding bits, they will be mapped to ‘=’
character. It can be known that there are two ‘=’ characters in the obtained coded string
when the remaining data has only one byte, and there is one ‘=’ character in the obtained
coded string when the remaining data has two bytes. The example of these two cases is
shown as follows:

① Raw data: 0x0A

Binary data: 00001010

Data obtained by filling: 00001010 00000000 00000000

The 6-bit group obtained after division: 000010 100000 000000 000000

Corresponding coded values: 0x02 0x20 0x00 0x00

Corresponding characters: C g = =

② Raw data: 0x0A 0x0B

Binary data: 00001010 00001011

Data obtained by filling: 00001010 00001011 00000000

The 6-bit group obtained after division: 000010 100000 101100 000000

Corresponding coded values: 0x02 0x20 0x2C 0x00

Corresponding characters: C g s =

55/ 55