Security Classification: Secret Z-110-002557-002-2.

3107 HL7 Communication Protocol

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 1 of 27
 Security Classification: Secret Z-110-002557-002-2.0

Table of Contents
Table of Contents...............................................................................................................................................3
1 Low-Level Protocol............................................................................................................................4
2 HL7 Message Constructing Principles.........................................................................................5
3 Principles of Escape Character Conversion..............................................................................6
4 Communication...................................................................................................................................7
4.1 Process of communication..........................................................................................................7
4.2 Message Information...................................................................................................................7
4.3 Message Description...................................................................................................................9
5 Example..............................................................................................................................................18
5.1 Sample Message........................................................................................................................18
5.2 Sample Response Message....................................................................................................19
5.3 QC Message...............................................................................................................................19
5.4 QC Response Message............................................................................................................19
5.5 Bidirectional LIS inquiry response message.........................................................................20
5.6 HL7 Coding and Constant Definition......................................................................................20
5.7 OBR-4 Message Type Coding.................................................................................................20
5.8 OBX-3 parameter type code.....................................................................................................20
5.9 Analysis Parameter....................................................................................................................24
6 Enumeration Value of the Other HL7 Field...............................................................................26
6.1 HL7 Data Type Definition..........................................................................................................26
6.2 Binary Data Communication.....................................................................................................28
6.3 Base64 Coding...........................................................................................................................28

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 2 of 27
 Security Classification: Secret Z-110-002557-002-2.0

1 Low-Level Protocol
TCP interface communication/port communication is based on byte stream, there is no message
boundary. HL7 of high-level protocol is based on messages. The function of terminating the
message is not provided. In order to determine the message boundary, the MLLP low-level protocol
is used (see HL7 Interface Standards Version 2.3 .1). Messages are transmitted in the following
format:
<SB> ddddd <EB><CR>
among which:

<SB> = Start Block character (1 byte)

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

ddddd = Data (variable number of bytes)

ddddd is valid data of the HL7 information, and is displayed as UTF-8 code string.

<EB> = End Block character (1 byte)

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

<CR> = Carriage Return (1 byte)

ASCII carriage return character, i.e.<0x0D>.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 3 of 27
 Security Classification: Secret Z-110-002557-002-2.0

2 HL7 Message Constructing Principles

Every HL7 message consists of several segments and ends up with the <CR>.
Each segment consists of the segment name of three characters and a number of fields, and each
field consists of some components and subcomponents. The first segment of each segment is MSH
segment, which includes the field, unit and unit of delimiter.
MSH|^~\&| | |||1231235941||ORU^R01|2|P|2.3.1||||||UNICODE
Example D-1 MSH segments
The five characters following MSH segment define the delimiters used between fields, components
and subcomponents. Although they can be any non-text characters, HL7 standard recommends you
use the characters in the table below:
Character It means...
| Field delimiter
^ Component delimiter
& Subcomponent
delimiter
~ Repetition delimiter
\ ESC
The first field of MSH contains all the delimiters. Some fields behind are null because they are
optional and not used by Mindray HL7 interface. Details about field definition and selection will be
stated below.
For message of any type, the segments behind MSH appear in a fixed order. The order will be
described in the following sections and the following grammar is used to organize the segments in
proper order.
[] encloses optional segments.
{ } encloses segments which can repeat once or more.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 4 of 27
 Security Classification: Secret Z-110-002557-002-2.0

3 Principles of Escape Character Conversion

For the field data of ST, TX, FT, and CF, etc. delimiters may be used in strings like remarks, clinical
diagnosis and customized gender etc. When coding, the delimiters in the original strings shall be
converted to escape sequence; which is restored in decoding. The principles for escape character
conversion for HL7 interface are as follows:
ESC Original Character
Sequence
\F\ Field delimiter
\S\ Component delimiter
\T\ Subcomponent delimiter
\R\ Repetition delimiter
\E\ Escape delimiter
\.br\ <CR>, segment end character.
Note: the "\" in the escape sequence represents the ESC delimiter, whose value is defined in the
MSH segment.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 5 of 27
 Security Classification: Secret Z-110-002557-002-2.0

4 Communication
4.1 Process of communication
4.1.1 The main unit directly sends the test results
The PC connecting the analyzer actively sends the test results to the LIS. Test results and QC data
are all send this way. The communication process is shown in Figure 1.

Figure 1 Test results communication process

4.1.2 Query worklist information

Worklist belongs to the Order message. Thus, the corresponding HL7 messages: ORM(General
Order Message) and ORR(General Order Response Message) can be used. The communication
process is shown in Figure 2.

Figure 2 Worklist searching communication process

4.2 Message Information

During the communication process, the message construction involves ORU^R01 message and
ACK^R01 message. ORU^R01 message and ACK^R01 message appeared twinning, and is used
for the communication of the analysis result and QC data.

4.2.1 ORU^R01 message

ORU^R01 message: is mainly used for the transmission of the analysis results and QC data.
ORU Observational Results (Unsolicited) Description

MSH Message Header, mandatory, including the communication information like

message No., sending time, message delimiter and coding method, etc.
{
PID Patient demographic information, including patient name, gender, patient ID, date of
birth, etc.
[PV1] Patient visit information, including patient type, department, bed No. and payer*,
etc.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 6 of 27
 Security Classification: Secret Z-110-002557-002-2.0
{
OBR sample information, including sample No., operator and time of analysis,
etc.
{[OBX]} analysis data, including analysis results and mode of analysis, etc.
}
}

4.2.2 ACK^R01 message

ACK^R01 message: it confirms the receival of ORU^R01 message
ACK Acknowledgment Description

MSH Message head

MSA message acknowledgment, describing whether it has received the transmitted
message

4.2.3 ORM^O01 message

ORM^O01 message: Common order message, all the actions related to order basically uses the
message of this type. For example, create a new order or cancel an order. Here, the main unit
requests LIS to re-fill the order message.
ORM General Order Message Description

MSH Message header

{ORC} Common message of Order, including the No. information of the sample
searched

4.2.4 ORM^O02 message

ORR^O02 message: affirming of the ORM^O01 message. Here, returning the completed
information of order (i.e. worklist).
ORR^O02 General Order Response Message Description

MSH Message header

MSA Message affirm
[
PID Patient basic information
[PV1] Patient visit information
]
{
ORC Common message of Order, including the sample No.
[
OBR sample information
{
[OBX] Data of other sample information, including work mode, etc.
}

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 7 of 27
 Security Classification: Secret Z-110-002557-002-2.0
]
}

4.3 Message Description

The tables in this section provide detailed definitions of the fields in all the message segments. Each
row provides the information of one field, and the content of each column is described as follows:

1. No.: the HL7 message begins with the segment name of 3 characters followed by the fields
which are separated by delimiters. "No." refers to the order of the field in the HL7 message
segment.
E.g.
PID |1 | |7393670^^^^MR||^Liu Jia ||19950804000000|Female
↑ ↑ ↑
Segment name Field 1 Field 3
Note: for MSH segment, the field delimiter following the segment name is considered to be the first
field, used to define the field delimiter values of the whole message.

2. Field name: the logic sense of the field.

3. Data type ： the data type based on HL7 standards, See 6.1 HL7 Data Type Definition for
details;
4. Recommended max length: the recommended max length based on HL7 standards. But
during the communication process, the data length may be longer than recommended, in
which case the fields shall be identified by delimiters mark while analyzing the message
segment.
5. Description: description to the value of the field.
6. Example: example of the fields.

4.3.1 MSH
MSH (Message Header) segment contains basic information of HL7 messages, including delimiter
value, message type and coding method etc. It is the first field of every HL7 message.
Message example:
MSH|^~\&| | |||20361231235941||ORU^R01|2|P|2.3.1||||||UNICODE

For the value of each filed of the MSH message, see Table 4 -1.
Table 4-1 Meaning table of the MSH message
No. Field/delimit Data Recomm Description Example
er Name Type ended
Max
Length
1 Field ST 1 Includes the delimiter of the first |
Separator field after the segment name; used
to determine the delimiter values of

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 8 of 27
 Security Classification: Secret Z-110-002557-002-2.0
the rest part of the message.
2 Encoding ST 4 Includes component delimiters, ^~\&
Characters repetition delimiters, escape
delimiters and subcomponent
delimiters.
3 Sending EI 180 Application of sending terminal.
application
4 Sending EI 180 Device of sending terminal.
Facility
7 Date/Time TS 26 Time of creating the message (in 203612312
Of Message the format of 35925
YYYY[MM[DD[HH[MM[SS]]]]]),
using the system time
9 Message CM 7 Message type, in the format of ORU^R01
Type "message type^event type".
10 Message ST 20 Message control ID, used as the 2
Control ID unique identifier of a message.
11 Processing PT 3 Message processing ID. Value: P
ID "P": sample and worklist searching
message;
"Q": QC analysis result message;
In Ack messages, it is consistent
with the previously received
message.
12 Version ID VID 60 HL7 version number. Value: "2.3.1". 2.3.1
18 Character ID 10 Character set. UNICODE
Set Value: "UNICODE", which means
the message is expressed in UTF-8
strings.

4.3.2 MSA
MSA（Message Acknowledgment）message includes the confirmation information, which appears
in the Bi-Directional Response Message.
Message example:
MSA|AA|1
See Table 4 -2 for field definitions in use.
Table 4-2 MSA Field Definitions
No. Field/delimi Data Recom Description Example
ter Name Type mended
Max
Length
1 Acknowledg ID 2 Acknowledgment code:”AA”- AA
ment Code received; “AE” – error; “AR”-

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 9 of 27
 Security Classification: Secret Z-110-002557-002-2.0
rejected.
2 Message ST 20 Message control ID, consistent with 1
Control ID the MSH-10 of the received
message
6 Error CE 100 Error condition (status code); it also
Condition contains error condition
specification information; see Table
4 -3 for the value.

Table 4-3 Error code of MSA-6 field

Status code Status text (MSA- Description/Remark
(MSA-6) 3)
Successful: AA
0 Message accepted Successful
Error status AE
code:
100 Segment sequence Segment order in the message is
error wrong, or necessary segment lost
101 Required field Necessary field lost in a segment
missing
102 Data type error Segment data type error, e.g. numbers
are replaced by characters
103 Table value not Table value is not found; not used
found temporarily
Rejection status AR
code:
200 Unsupported Message type is not supported
message type
201 Unsupported event Event code is not supported
code
202 Unsupported Processing ID is not supported
processing id
203 Unsupported version Version ID is not supported
id
204 Unknown key Unknown key identifier, e.g.
identifier transmitting the patient information
that is not exited
205 Duplicate key Repeated key words existed
identifier
206 Application record Issues can not be executed at
locked application program saving level, e.g.
database is locked
207 Application internal Other interior errors of application
error program

4.3.3 PID

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 10 of 27
 Security Classification: Secret Z-110-002557-002-2.0
The PID (Patient Identification) segment contains the patient demographic information.
Message example :
PID|1||7393670^^^^MR||Jerry^Tom||19900804000000|Male

Example D-2 PID message example

See Table 4 -4 for field definitions in use.
Table 4-4 Definition table of the PID field
No. Field/delimi Data Recomme Description Example
ter Name Type nded Max
Length
1 Set ID - PID SI 4 Serial No., used to identify 1
different PID segments in a
message
3 Patient CX 20 Used as patient ID in the 7393670^^^^
Identifier List sample analysis result MR
messages, in the form of
"patient ID^^^^MR".
Used as batch No. of control in
QC messages.
5 Patient XPN 48 Patient name (consists of Jerry^Tom
Name Animal Name and Owner
Name), in the form of
"AnimalName^OwnerName"
7 Date/Time of TS 26 Used as time of birth in sample 1990080400
Birth information messages. 0000
In the form of
YYY[MM[DD[HH[MM[SS]]]]].
Used as expiration date of the
control in QC messages.
8 Sex IS 1 Gender, string. Male

4.3.4 PV1
The PV1 (Patient Visit) segment contains the patient visit information.
Message example:
PV1|1||ICU^^BedNO1
See Table 4 -5 for field definitions in use.
Table 4-5 PV1 Field Definitions
No. Field/delimi Data Recomme Description Example
ter Name Type nded Max
Length
1 Set ID - PV1 SI 4 Serial No., used to identify 1
different PV1 segments in a

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 11 of 27
 Security Classification: Secret Z-110-002557-002-2.0
message.

4.3.5 OBR
The OBR (Observation Request) segment contains the test report information.
Message example:
OBR|1||ABCDEF-0YT-4|00001^Automated Count^99MRC||20000706050000|20090626103851|||
DELIVERY||||20000706070000||||||||||HM||||||||Li
See Table 4 -6 for field definitions in use.
Table 4-6 OBR Field Definitions
No. Field/delimi Data Recomme Description Example
ter Name Type nded Max
Length
1 Set ID - SI 10 Serial No., used to identify 1
OBR different OBR segments in a
message
3 Filler Order EI 22 Used as sample ID in sample ABCDEF-
Number + analysis result messages. 0YT-4
Used as QC file No. in QC
messages.
4 Universal CE 200 Universal service ID, used to 00001^Auto
Service ID identify different types of mated
analysis results. See the Count^99MR
enumeration constant sampling C
section for details.
6 Requested TS 26 Draw time. 2000070605
Date/time Used as the time when the 0000
blood sample is drawn.
7 Observation TS 26 Time of analysis. 2009062610
Date/Time # 3851
10 Veterinarian XCN 60 Veterinarian DELIVERY
13 Relevant ST 300 Relevant clinical information.
Clinical Info. Can be used as the clinical
diagnostic information of patient
information.
14 Specimen TS 26 Time when the sample is 2000070607
Received received. 0000
Date/Time * Used as the time when the
analysis is ordered.
24 Diagnostic ID 10 Diagnosis maker ID; value: HM
Serv Sect ID "HM" (means Hematology)
32 Principal CM 200 Principal result interpreter. Li
Result Used as the operator of the
Interpreter + sample analysis in sample

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 12 of 27
 Security Classification: Secret Z-110-002557-002-2.0
messages.
Used as the operator of the QC
count in QC messages.

4.3.6 OBX
The OBX (Observation/Result) segment contains the parameter information of each test result.
Message example:
OBX|7|NM|6690-2^WBC^LN||9.55|10*9/L|4.00-10.00||||F
See Table 4 -7 for field definitions in use.
Table 4-7 OBX Field Definitions
No. Field/delimi Data Recomme Description Example
ter Name Type nded Max
Length
1 Set ID - OBX SI 10 Serial No., used to identify 7
different OBX segments in a
message.
2 Value Type ID 3 Data type of the analysis result. NM
Value: "ST", "NM", "ED", "IS",
etc.
3 Observation CE 590 Analysis item identifier. 6690-
Identifier In the form of 2^WBC^LN
"ID^Name^EncodeSys", where
ID is the identifier of the
analysis item; Name is the
description of the item;
EncodeSys is the coding
system of the item.
See the enumeration constant
sampling section for details.
Note: ID and EncodeSys are
used to identify different
analysis parameters, while
Name is for description
purpose rather than
identification.
5 Observation * 65535 Analysis result data, which can 9.55
Value be numeric, string,
enumeration value, binary
data, etc. (Binary data like
histogram or scattergram are
converted to codes using the

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 13 of 27
 Security Classification: Secret Z-110-002557-002-2.0
Base64 coding method. See
the following sections for the
coding method).
6 Units CE 90 Unit of analysis items. It adopts 10*9/L
the ISO standard unit. See the
enumeration constant sampling
section for details.
7 References ST 90 Reference range of analysis 4.00-10.00
Range results, in the form of "lower
limit-higher limit", "<upper limit"
or ">lower limit".
8 Abnormal ID 5 Analysis result flags. Value
Flags definitions:
“N”- normal
“A”- abnormal
"H": higher than upper limit
“L” – lower than lower limit
Note: The flag for normal or
abnormal and that for high or
low result may appear in this
field at the same time. In this
case, the two types of flags are
connected by a “~”, e.g. “H~A”
11 Observ ID 1 Status of the analysis result. F
Result "F" - （ Final Result ） , which
Status refers to Final Result.
13 User ST 20 User-defined. For flags of
Defined reagent expiration or
Access modification, etc. In the form
Checks of”Flag1~Flag2”.

There are 3 types of flags in all:

O – reagent expiration

E – result edited flag

e – result changed due to the

manual editing of another
parameter result based on
which it is calculated

4.3.7 ORC
The ORC(Common Order) segment contains the common information of order.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 14 of 27
 Security Classification: Secret Z-110-002557-002-2.0
Message example:
ORC|RF||SampleID||IP
See Table 4 -8 for definition of the fields used.
Table 4-8 ORC Field Definitions
No. Field/delimi Data Recomme Description Example
ter Name Type nded Max
Length
1 Order ID 2 Order control word In the ORM RF
Control message the value is “RF”
which means “re-fill the order
request”. In the ORR message
the value is “AF” which means
“affirm the re-filled order”.
2 Placer Order EI 22 Placer order number In the
Number ORM message the value is
empty; in the ORR message
the value is the sample ID.
3 Filler Order EI 22 Filler Order Number In the SampleID
Num ORM message the value is the
sample ID; in the ORR
message the value is empty.
5 Order Status ID 2 Order status In the ORM IP
message the value is “IP”
which means “order is being
processed, but results are not
obtained”; in the ORR
message the value is empty.

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 15 of 27
 Security Classification: Secret Z-110-002557-002-2.0

5 Example
5.1 Sample Message
MSH|^~\&|||||20101206164344||ORU^R01|1|P|2.3.1||||||UNICODE
PID|1||ChartNo^^^^MR||LastName^FirstName||20040506070809|Male
PV1|1|Neike|Hema^^BN1|||||||||||||||||ChargeType
OBR|1||TestSampleID1|00001^Automated Count^99MRC||20000102030405|20010203040506|||
Sender|||Cold|20020304050607||||||||20030405060708||HM||||Auditer||||Tester
OBX|1|IS|08001^Take Mode^99MRC||O||||||F
OBX|2|IS|08002^Blood Mode^99MRC||W||||||F
OBX|3|IS|08003^Test Mode^99MRC||CBC||||||F
OBX|4|IS|01002^Ref Group^99MRC||Common||||||F
OBX|5|NM|30525-0^Age^LN||Age|yr|||||F
OBX|6|ST|01001^Remark^99MRC||Remark||||||F
OBX|7|NM|6690-2^WBC^LN||***.**|10*9/L|***.**-***.**|N|||F
OBX|8|NM|731-0^LYM#^LN||***.**|10*9/L|***.**-***.**|N|||F
OBX|9|NM|736-9^LYM%^LN||***.*|%|***.*-***.*|N|||F
OBX|10|NM|789-8^RBC^LN||**.**|10*12/L|**.**-**.**|N|||F
OBX|11|NM|718-7^HGB^LN||***.*|g/L|***.*-***.*|N|||F
OBX|12|NM|787-2^MCV^LN||***.*|%|***.*-***.*|N|||F
OBX|13|NM|785-6^MCH^LN||***.*|pg|***.*-***.*|N|||F
OBX|14|NM|786-4^MCHC^LN||****|g/L|****-****|N|||F
OBX|15|NM|788-0^RDW-CV^LN||***.*|%|***.*-***.*|N|||F
OBX|16|NM|21000-5^RDW-SD^LN||***.*|fL|***.*-***.*|N|||F
OBX|17|NM|4544-3^HCT^LN||***.*|%|***.*-***.*|N|||F
OBX|18|NM|777-3^PLT^LN||****|10*9/L|****-****|N|||F
OBX|19|NM|32623-1^MPV^LN||**.*|fL|**.*-**.*|N|||F
OBX|20|NM|32207-3^PDW^LN||**.*||**.*-**.*|N|||F
OBX|21|NM|10002^PCT^99MRC||*.***|%|*.***-*.***|N|||F
OBX|22|NM|10027^MID#^99MRC||***.**|10*9/L|***.**-***.**|N|||F
OBX|23|NM|10029^MID%^99MRC||***.*|%|***.*-***.*|N|||F
OBX|24|NM|10028^GRAN#^99MRC||***.**|10*9/L|***.**-***.**|N|||F
OBX|25|NM|10030^GRAN%^99MRC||***.*|%|***.*-***.*|N|||F
OBX|26|NM|10014^PLCR^99MRC||***.*|%|***.*-***.*|N|||F
OBX|27|IS|12045^Multiple alerts^99MRC||T||||||F
OBX|28|IS|12046^Lym left region alert^99MRC||T||||||F

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 16 of 27
 Security Classification: Secret Z-110-002557-002-2.0
OBX|29|IS|||T||||||F
OBX|30|IS|12048^Mid gran region alert^99MRC||T||||||F
OBX|31|IS|12049^Gran right region alert^99MRC||T||||||F
OBX|32|IS|12050^Plt rbc boundary blur^99MRC||T||||||F
OBX|33|IS|12051^Micro plt over aboundce^99MRC||T||||||F
OBX|34|IS|12052^Macro plt over aboundce^99MRC||T||||||F
OBX|35|NM|15004^WBC Histogram. Meta Length^99MRC||1||||||F
OBX|36|NM|15010^WBC Lym left line.^99MRC||1||||||F
OBX|37|NM|15011^WBC Lym Mid line.^99MRC||2||||||F
OBX|38|NM|15012^WBC Mid Gran line.^99MRC||3||||||F
OBX|39|NM|15013^WBC Gran right line^99MRC||4||||||F
OBX|40|ED|15000^WBC Histogram. Binary^99MRC||^Application^Octer-
stream^Base64^AAAAAAAAAAAAAAAAAAAAAA==||||||F
OBX|41|NM|15051^RBC Histogram. Left Line^99MRC||5||||||F
OBX|42|NM|15052^RBC Histogram. Right Line^99MRC||6||||||F
OBX|43|NM|15053^RBC Histogram. Binary Meta Length^99MRC||2||||||F
OBX|44|ED|15050^RBC Histogram. Binary^99MRC||^Application^Octer-
stream^Base64^AAAAAAAAAAAAAAAAAAAAAA==||||||F
OBX|45|NM|15111^PLT Histogram. Left Line^99MRC||7||||||F
OBX|46|NM|15112^PLT Histogram. Right Line^99MRC||8||||||F
OBX|47|NM|15113^PLT Histogram. Binary Meta Length^99MRC||4||||||F
OBX|48|ED|15100^PLT Histogram. Binary^99MRC||^Application^Octer-
stream^Base64^AAAAAAAAAAAAAAAAAAAAAA==||||||F

5.2 Sample Response Message

A sample response message needs to be responded after receiving a sample result each time.
which contains two segments: MSH and MSA. To send a correct response message, take into
consideration that: the MSH-9 field should be ACK^R01 which indicates that it is a sample response
message; If the value in the MSA-2 field is the same with the MSH-10 value of the received analysis
result, it indicates that this response message is corresponding to the sent analysis result. The MSA-
2 value in the following example is 2.
MSH|^~\&|LIS||||20361231235956||ACK^R01|1|P|2.3.1||||||UNICODE MSA|AA|2

5.3 QC Message
The content form of QC Message is different from that of the sample count result message, the
MSH-11 of the QC message is valued as Q, the represented message type is QC data.

5.4 QC Response Message

The only difference between the QC response message and the sample analysis result response

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 17 of 27
 Security Classification: Secret Z-110-002557-002-2.0
message is that the MSH-11 value of the QC response message is Q.

5.5 Bidirectional LIS inquiry response message

When the LIS received an inquiry message, it needs to send back an inquiry response message.
The first two message segments of the inquiry response message are MSH and MSA. The MSH-9
field (indicating the type of the segment) is filled with ORR^O02, while the MSA segment should be
filled up as shown in the following example of the inquiry response message. If the LIS gets
searching results for the inquiry, there will be PID, PV1, ORC, OBR and OBX message segments
after the two heading segments to provide the patient and sample information, in the same way as
the sample data message does. The ORC segment is indispensable for an inquiry response
message with searching results, in which the ORC-1 value is AF, and ORC-2 is the filter (the sample
ID). Note that the OBR-2 field indicates the sample ID, which should be the same value as in the
ORC-2 field; Otherwise, the message will be regarded as incorrect.
An example of the inquiry response message with searching results is shown as follows:
MSH|^~\&||Mindray|||20141105151358||
ORR^O02||P|2.3.1||||||UNICODE
MSA|AA|60PID|1||test1^^^^MR||^Tom||20080525000000|
PV1|1||ICU^^BedNO1
ORC|AF|257
OBR|1|257||00001^Automated Count^99MRC||20090205100000||||S1||||20090203101020||||||||||
HM||||||||A5
OBX|1|IS|08002^Blood Mode^99MRC||W||||||F
OBX|2|IS|08003^Test Mode^99MRC||CBC||||||F
OBX|3|NM|30525-0^Age^LN||14|yr|||||F
OBX|4|ST|01001^Remark^99MRC||R5||||||F

5.6 HL7 Coding and Constant Definition

5.7 OBR-4 Message Type Coding
OBR-4 field is used to mark the analysis type, see Table 4-9.
Table 4-10 OBR-4 message type value table
Code
Data Name EncodeSys
（ID）
Sample Analysis
00001 Automated Count 99MRC
Result
LJ C count result 00003 LJ QCR 99MRC

5.8 OBX-3 parameter type code

Each OBX message field contains an analysis item or information of other data. OBX-2 defines the
HL7 data type of the carried data ; OBX-3 （Observation Identifier ） is the mark of the data item,

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 18 of 27
 Security Classification: Secret Z-110-002557-002-2.0

which displays as “ID^Name^EncodeSys”；OBX-5 contains the value of the data item; OBX-6 contains
the parameter unit, which is displayed as the ISO standard unit.
HL7 Example of OBX-3 field
Type
Data Code(ID) Name EncodeSys
(OBX-
2)
Non-parameter Data Items
Presentation 08001^Take
IS 08001 Take Mode 99MRC
mode Mode^99MRC
08002^Blood
Blood Mode IS 08002 Blood Mode 99MRC
Mode^99MRC
Measuremen 08003^Test
IS 08003 Test Mode 99MRC
t Mode Mode^99MRC
Age NM 30525-0 Age LN 30525-0^Age^LN
Remarks ST 01001 Remark 99MRC 01001^Remark^99MRC
Reference 01002^Ref
IS 01002 Ref Group 99MRC
group Group^99MRC
Level of 05001^Qc
IS 05001 Qc Level 99MRC
control Level^99MRC
Recheck 01006^ Recheck
Reexam flag IS 01006 99MRC
flag flag^99MRC
Parameter Result Items
WBC NM 6690-2 WBC LN 6690-2^WBC^LN
BAS NM 704-7 BAS# LN 704-7^BAS#^LN
BAS_PER NM 706-2 BAS% LN 706-2^BAS%^LN
NEU NM 751-8 NEU# LN 751-8^NEU#^LN
NEU_PER NM 770-8 NEU% LN 770-8^NEU%^LN
EOS NM 711-2 EOS# LN 711-2^EOS#^LN
EOS_PER NM 713-8 EOS% LN 713-8^EOS%^LN
LYM NM 731-0 LYM# LN 731-0^LYM#^LN
LYM_PER NM 736-9 LYM% LN 736-9^LYM%^LN
MON NM 742-7 MON# LN 742-7^MON#^LN
MON_PER NM 5905-5 MON% LN 5905-5^MON%^LN
RUO parameter
ALY NM 26477-0 *ALY# LN 26477-0^*ALY#^LN
ALY_PER NM 13046-8 *ALY% LN 13046-8^*ALY%^LN
LIC (Large 10000^*LIC#^99MRC
Immature NM 10000 *LIC# 99MRC
Cell)
LIC_PER（L 10001^*LIC%^99MRC
arge
Immature
NM 10001 *LIC% 99MRC
Cell
Percentage
）
RBC NM 789-8 RBC LN 789-8^RBC^LN
HGB NM 718-7 HGB LN 718-7^HGB^LN
MCV NM 787-2 MCV LN 787-2^MCV^LN
MCH NM 785-6 MCH LN 785-6^MCH^LN
MCHC NM 786-4 MCHC LN 786-4^MCHC^LN
RDW_CV NM 788-0 RDW-CV LN 788-0^RDW-CV^LN
RDW_SD NM 21000-5 RDW-SD LN 21000-5^RDW-SD^LN

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 19 of 27
 Security Classification: Secret Z-110-002557-002-2.0

HCT NM 4544-3 HCT LN 4544-3^HCT^LN

PLT NM 777-3 PLT LN 777-3^PLT^LN
MPV NM 32623-1 MPV LN 32623-1^MPV^LN
PDW NM 32207-3 PDW LN 32207-3^PDW^LN
PCT（Platel 10002^PCT^99MRC
NM 10002 PCT 99MRC
etcrit）
PLCC NM 10013 PLCC 99MRC 10013^ PLCC^99MRC
PLCR NM 10014 PLCR 99MRC 10014^ PLCR^99MRC
QC specific parameter
GRAN-X NM 10003 GRAN-X 99MRC 10003^GRAN-X^99MRC
GRAN-Y NM 10004 GRAN-Y 99MRC 10004^GRAN-Y^99MRC
10005^GRAN-
GRAN-Y(W) NM 10005 GRAN-Y(W) 99MRC
Y(W)^99MRC
10006^WBC-
WBCMCV NM 10006 WBC-MCV 99MRC
MCV^99MRC
Intermediate Data of Analysis Results histogram and scattergram data of WBC, RBC, and
PLT, etc.)
WBChistogra WBC 15000^WBC Histogram.
m binary ED 15000 Histogram. 99MRC Binary^99MRC
data Binary
Left 15001^WBC Histogram.
WBC
discriminator Left Line^99MRC
NM 15001 Histogram. 99MRC
of the WBC
Left Line
histogram
Right 15002^WBC Histogram.
WBC
discriminator Right Line^99MRC
NM 15002 Histogram. 99MRC
of the WBC
Right Line
histogram
Middle 15003^WBC Histogram.
WBC
discriminator Middle Line^99MRC
NM 15003 Histogram. 99MRC
of the WBC
Middle Line
histogram
WBC 15004^WBC Histogram.
WBC
histogram Meta Length^99MRC
NM 15004 Histogram. 99MRC
metadata
Meta Length
length
WBC WBC 15005^WBC Histogram.
histogram left Histogram. Left Line
NM 15005 99MRC
discriminator Left Line Adjusted^99MRC
adjusted flag Adjusted
WBC 15006^WBC Histogram.
WBC
histogram Right Line
Histogram.
right NM 15006 99MRC Adjusted^99MRC
Right Line
discriminator
Adjusted
adjusted flag
WBC 15007^WBC Histogram.
WBC
histogram Middle Line
Histogram.
middle NM 15007 99MRC Adjusted^99MRC
Middle Line
discriminator
Adjusted
adjusted flag
WBC WBC 15008^WBC Histogram.
histogram ED 15008 Histogram. 99MRC BMP^99MRC
bitmap data BMP
Total number WBC 15009^WBC Histogram.
of WBC NM 15009 Histogram. 99MRC Total^99MRC
Histogram Total

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 20 of 27
 Security Classification: Secret Z-110-002557-002-2.0
RBC RBC 15050^RBC Histogram.
histogram ED 15050 Histogram. 99MRC Binary^99MRC
binary data Binary
Left 15051^RBC Histogram.
RBC
discriminator
NM 15051 Histogram. 99MRC Left Line^99MRC
of the RBC
Left Line
histogram
Right 15052^RBC Histogram.
RBC
discriminator
NM 15052 Histogram. 99MRC Right Line^99MRC
of the RBC
Right Line
histogram
RBC RBC 15053^RBC Histogram.
historgram Histogram. Binary Meta
NM 15053 99MRC
metadata Binary Meta Length^99MRC
length Length
RBC RBC 15054^RBC Histogram.
histogram left Histogram. Left Line
IS 15054 99MRC
discriminator Left Line Adjusted^99MRC
adjusted flag Adjusted
RBC IS 15055 99MRC 15055^RBC Histogram.
RBC
histogram Right Line
Histogram.
right Adjusted^99MRC
Right Line
discriminator
Adjusted
adjusted flag
PLT PLT 15100^PLT Histogram.
histogram ED 15100 Histogram. 99MRC Binary^99MRC
binary data Binary
Left 15111^PLT Histogram.
PLT
discriminator
NM 15111 Histogram. 99MRC Left Line^99MRC
of the PLT
Left Line
histogram
Right 15112^PLT Histogram.
PLT
discriminator
NM 15112 Histogram. 99MRC Right Line^99MRC
of the PLT
Right Line
histogram
PLT PLT 15113^PLT Histogram.
historgram Histogram. Binary Meta
NM 15113 99MRC
metadata Binary Meta Length^99MRC
length Length
PLT PLT 15114^PLT Histogram.
histogram left Histogram. Left Line
IS 15114 99MRC
discriminator Left Line Adjusted^99MRC
adjusted flag Adjusted
PLT IS 15115 99MRC 15115^PLT Histogram.
PLT
histogram Right Line
Histogram.
right Adjusted^99MRC
Right Line
discriminator
Adjusted
adjusted flag
15200^WBC DIFF
DIFF WBC DIFF
scattergram ED 15200 Scattergram 99MRC Scattergram.
bitmap data . BMP
BMP^99MRC
DIFF WBC DIFF 15201^WBC DIFF
scattergram ED 15201 Scattergram 99MRC Scattergram.
binary data . BIN BIN^99MRC
DIFF WBC DIFF 15202^ WBC DIFF
Scattergram ED 15202 Scattergram 99MRC Scattergram. BIN type
Type data . BIN data^99MRC
DIFFscatterg NM 15203 WBC DIFF 99MRC 15203^ WBC DIFF

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 21 of 27
 Security Classification: Secret Z-110-002557-002-2.0
ram Scattergram. Meta
Scattergram
metadata len^99MRC
. Meta len
length
DIFF 15204^ WBC DIFF
WBC DIFF
scattergram Scattergram. Meta
NM 15204 Scattergram 99MRC
metadata count^99MRC
. Meta count
length
Flags of Abnormal Blood Cell Differential or Morphology
WBC 12011^WBC
WBC Abn. IS 12011 99MRC
Abnormal Abnormal^99MRC
Imm 34165-1^Imm
Immature
IS 34165-1 Granulocyte LN Granulocytes?^LN
Granulocyte?
s?
Abn./Atypical Atypical 15192-8^Atypical
IS 15192-8 LN
Lymph? Lymphs? Lymphs?^LN
RBC RBC 12013^RBC Abnormal
Distribution IS 12013 Abnormal 99MRC distribution^99MRC
Abn. distribution
Anemia IS 12014 Anemia 99MRC 12014^Anemia^99MRC
HGB 12015^HGB
HGB
Abn./Interfer IS 12015 99MRC Interfere^99MRC
Interfere
e?
Platelet PLT 12016^PLT Abnormal
Distribution IS 12016 Abnormal 99MRC Distribution^99MRC
Abn. Distribution

5.9 Analysis Parameter

The analysis parameter unit is displayed as standard unit.
Table 4-11 Parameter Units in Analysis
Parameter Units in
Units in Software Communication
(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 (age unit) yr

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 22 of 27
 Security Classification: Secret Z-110-002557-002-2.0

month (age unit) mo

day (age unit) d
hour (age unit) hr
week (age unit) wk

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 23 of 27
 Security Classification: Secret Z-110-002557-002-2.0

6 Enumeration Value of the Other HL7 Field

Data Value Enumeration

Take Mode Value enumeration:
“O” - open-vial
“A” - autoloading
Blood Mode Value enumeration:
“W”- whole blood
“P” - predilute
“W_WBCHGB” － WBC/HGB whole blood
“P_WBCHGB” －WBC/HGB predilute. specific
3-diff blood mode
“W_RBCPLT” － RBC/PLT whole blood,
specific 3-diff blood mode
“P_RBCPLT"”－ RBC/PLT predilute, specific
3-diff blood mode
Test Mode Value enumeration:
"CBC"
“CBC+5DIFF”
Qc Level Value enumeration:
“L”- low
“M”- normal
“H”- high
Histogram discriminator adjusted mark and The data type of OBX-2 is "IS". Value
reexam flag and other flags enumeration:
“T”- true
“F”- false

6.1 HL7 Data Type Definition

 CE - Code Element
<identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^
<alternate text (ST)> ^ <name of alternate coding system (ST)>

 CM - Composite
Format defined by the field.

 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 (IS)> ^ < assigning facility (HD)>

 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)>

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 24 of 27
 Security Classification: Secret Z-110-002557-002-2.0
 FC – Financial Class
<financial class (IS)> ^ <effective date (TS)>

 HD - Hierarchic designator
<namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>

Used only as part of EI and other data types.

 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.

 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>

 XCN - Extended composite ID number and name

In Version 2.3, use instead of the CN data type. <ID number (ST)> ^ <family name (ST)> &

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 25 of 27
 Security Classification: Secret Z-110-002557-002-2.0
<last_name_prefix (ST) ^ <given name (ST)> ^ <middle initial or name (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)>

 XPN - Extended person name

In Version 2.3, replaces the PN data type. <family name (ST)> ^ <given name (ST)> &
<last_name_prefix (ST)> ^ <middle initial or name (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)>

 VID - Version identifier

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

6.2 Binary Data Communication

Histogram data is transmitted the binary. :The data type field of OBX segment is "ED", and the data
field is in the form of ^Application^Octer-stream^Base64^……histogram data……”, meanwhile the
“Application” indicates that application program data is transmitted, “Octer-stream” indicates the data
is of byte stream type, “Base64” indicates the coding mode of the bitmap data.
The scattergram binary data transmission is the similar as the histogram data.
Scattergram, bitmap data communication: The data type field of OBX segment is "ED", and the data
field is in the form of “^Image^BMP^Base64^……scattergram bitmap data……”,
“Image^BMP^Base64” indicates that the data in transmission is BMP data coded by Base 64.

6.3 Base64 Coding

1. Select the 3 adjacent bytes (i.e. 24 bit) from the data stream to be encoded; from left to right,
divide them into 4 6-bit groups; and then, the ASCII string is obtained by mapping based on Table 14
below.

Raw data:: 15H A3H 4BH

Binary data 00010101 10100011 01001011
6-bit groups obtained after dividing 000101 011010 001101 001011
Corresponding codes 5H 1AH 0DH 0BH
Corresponding characters F a N L
Table 11-12 Base64 Mapping

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 26 of 27
 Security Classification: Secret Z-110-002557-002-2.0

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

0A 17 R 34 I 51 z
1B 18 S 35 j 52 0
2C 19 T 36 k 53 1
3D 20 U 37 l 54 2
4E 21 V 38 m 55 3
5F 22 W 39 n 56 4
6G 23 X 40 o 57 5
7H 24 Y 41 p 58 6
8I 25 Z 42 q 59 7
9J 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
14 O 31 f 48 w (pad) =
15 P 32 g 49 x
16 Q 33 h 50 y
2. Repeat step 1 continuously till the whole data stream is encoded.
When the data left is less than 3 bytes, 0 is added to the right to complement. If the 6-bit groups
obtained is composed of the complement bit (0) only, then it is mapped to the “=” character. When
there is the last one byte left, there will be two “=” characters in the obtained coding string; when two
bytes are left, then the obtained coding string consists of one “=” character. See the two examples
below:

① Raw data 0AH

00001010
Data obtained after 00001010 00000000 00000000
6-bit groups obtained after dividing 000010 100000 000000 000000
Corresponding codes 02H 20H 00H 00H
Corresponding characters C g = =

② Raw data 0AH 0BH

00001010 00001011
Data obtained after 00001010 00001011 00000000
6-bit groups obtained after 000010 100000 101100 000000
Corresponding codes 02H 20H 2CH 00H
Corresponding characters C g s =

Classified documents, its Intellectual Property belongs to Mindray Co. Ltd Page 27 of 27