Manual HL-7-Data-Commnication-Protocol.pdf

Printed:
1st Edition: 16 Oct 2015
HL7 Data Communication Protocol
Automated
Hematology Analyzer
MEK-9100
0614-907509
2016/05/23

About This Manual
In order to use this product safely and fully understand all its functions, read this manual before using the
product.
Keep this manual near the instrument or in the reach of the operator and refer to it whenever the operation is
unclear.
Trademark
The company name and model name are trademarks and registered trademarks of each company.
Copyright Notice
The entire contents of this manual are copyrighted by Nihon Kohden. All rights are reserved. No part of this
document may be reproduced, stored, or transmitted in any form or by any means (electronic, mechanical,
photocopied, recorded, or otherwise) without the prior written permission of Nihon Kohden.
This product stores personal patient information. Manage the information appropriately.
The contents of this manual are subject to change without notice.
If you have any comments or suggestions on this manual, please contact us at: www.nihonkohden.com

Introduction............................................................ 2
Applicable Standards......................................................... 2
TCP/IP Communication Method............................ 3
Session Layer Specifications................................ 4
Application Layer Specifications............................ 5
Reference Terms................................................................ 5
IHE Domain and Unified Profile.......................................... 5
Message, Segment and Field Specifications..................... 5
Messages....................................................................... 5
Segments....................................................................... 6
LAB-27 Transaction Specifications..................................... 7
QBP (Query By Parameter) Messages.......................... 7
RSP (Segment Pattern Response) Messages..............10
LAB-28 Transaction Specifications................................... 13
OML (Laboratory Order Message) Messages..............13
ORL (Laboratory Order Acknowledgment)
Messages......................................................................18
LAB-29 Transaction Specifications................................... 21
OUL (Unsolicited Laboratory Observation)
Messages......................................................................21
ACK (General Acknowledgement) Messages.............. 29
Code System Specifications................................ 31
Measurement Items Code System................................... 31
Code System Specifications............................................. 34
Abnormal Flag Code System........................................... 35
Error Code System........................................................... 35
Character Set Code System............................................. 35
Data Communication Examples.......................... 36
MEK-9100 Communication Examples.............................. 36
Order Communication using Sample Tube Barcode
ID.................................................................................. 36
Order Communication with Sampling Tube Position
in the Rack................................................................... 39
When Sending QC Data................................................41
Contents

2 MEK-9100 HL7 Data Communication Protocol
Introduction
This document describes the HL7 based communication protocol of the
following product.
• MEK-9100 automated hematology analyzer: V01-01 or later
Applicable Standards
The communication specifications of the analyzer are based on the applicable
standards of each layer in the network layer framework “OSI (Open Systems
Interconnection)” which is defined in ISO 7498. The following table shows the
applicable standards.
Applicable Standards of the Communication Specifications of the Analyzer
OSI Reference Model
Applicable Standard
Layer Layer Name
7 Application layer HL7
5 Session layer MLLP
4 Transport layer TCP
3 Network layer IP
2 Data link layer Ethernet (IEEE 802.3)
1 Physical layer Ethernet (IEEE 802.3)

MEK-9100 HL7 Data Communication Protocol3
TCP/IP Communication Method
Communication uses TCP/IP sockets.
For the communication ports, each transaction defined in the application layer
is alloted to one port. For example, in the LAW profile, LAB 27, 28 and 29
transactions are assigned one port each (total 3 ports).
The send port of the analyzer (LAB 27 or LAB 29 in case of the
LAW profile) can be set to the same port.
LAW Profile Example
Analyzer
Port 50002
Analyzer Manager
Port 50001
Port 50003
LAB-27 transaction
LAB-28 transaction
LAB-29 transaction
Create a socket on the server and wait for a connection from the client. At the
transaction start, a socket is established at the client side, and connection is made
to the server.
If connection is established, the client sends a message to the server then it is
necessary to wait for a response message from the server. When a response
message is received, the socket is closed.
Socket Communication Example
Socket (Create socket)
Connect (Connect to socket)
Send (Send data)
Recv (Receive data)
Close (Close socket)
Client
Listen (Prepare socket)
Socket (Create socket)
Accept (Standby for socket
connection)
Bind (Bind socket)
Recv (Receive data)
Send (Send data)
Close (Close socket)
Server

Session Layer Specifications
In the session layer, in accordance with the HL7 MLLP (Minimal Lower
Layer Protocol), the HL7 message which is defined in the application layer
in the following format is enclosed by a start block (SB) and an end block
(EBCR).
The start block (SB) can be appended or not appended to the HL7 message by
a setting on the System window.
Format: SBdataEBCR
Symbol
Hexadecimal
Code
Description
SB 0x0B
Start bit (1 byte)
Note that this is not an ASCII STX (0x02) or SOH
(0x01).
data ―
Variable length data.
This data is shown in the HL7 message data in the
application layer.
EB 0x1C
Stop bit (1 byte)
Note that this is not an ASCII ETX (0x03) or EOT
(0x04).
CR 0x0D Carriage return (1 byte)

Application Layer Specifications
This section explains the HL7 messages and segment specifications which are
based on the IHE technical framework.
Reference Terms
These application layer specifications are stipulated based on the following
terms.
(A) HL7 MESSAGING STANDARD VERSION 2.5.1
(B) IHE Laboratory Technical Framework Supplement
Laboratory Analytical Workflow (LAW)
Trial Implementation Rev. 1.4
For the protocol, refer to the IHE website.
IHE Domain and Unified Profile
These specifications conform to the IHE domain and unified profile in the chart
below.
IHE Domain and Unified Profile
IHE Domain Unified Profile Transaction Refer to
Laboratory LAW
LAB-27 p. 7
LAB-28 p. 13
LAB-29 p. 21
Message, Segment and Field Specifications
This section explains the HL7 message, segment and field specifications.
Messages
Details of each message item are shown below.
Message Description
MESSAGE Shows the names of messages which are determined in MSH-9.
Message Semantics
Shows the segments that can be used in a message. Segments that are enclosed with brackets have
the following conditions.
[ ]: Square brackets show parts that may be abbreviated.
{ }: Curly brackets show parts that may repeat.

Segments
Following table shows details of items which are used in the tables.
Segment Description
SEGMENT Shows the segment name.
SEQ
Shows the position of data in the segment. This is expressed in 3 layers. The first layer is the
field position, the second layer is the component position and the third layer is the subcomponent
position.
LEN Shows the maximum number of uppercase characters in the field.
DT Shows the data type of the field. For details about data type, refer to HL7 v2.5.1 Chapter 2.A.
OPT
Shows the handling method for field data.
The following conditions are observed.
M: It is necessary to set the data (including NULL data) at the sending side.
For NULL data, |””| double quotes can be used. (|| is not acceptable.) It is not always
necessary for the receiving side to use the data. But when the data does not exist (in the
case of ||), set the MSA-1 field of the response message to AE and it becomes possible to
notify errors on the sending side.
R: It is necessary to set the data (not including NULL data) at the sending side.
But to show NULL data, |””| double quotes cannot be used.
It is not always necessary for the receiving side to use the data. But when the data does
not exist (|| or |””|), set the MSA-1 field of the response message to AE and it becomes
possible to notify errors on the sending side.
RE: It is necessary to set this if the data may be used at the sending side. If it will not be used, it
is not necessary to set this.
It is not always necessary for the receiving side to use the data. But even when the data
does not exist, it is necessary to allow it.
O: Common use of data with the receiving side is optional.
X: Common use of data with the receiving side is not possible.
C (a/b): Follows the handling method of (a) if positive or (b) if negative. The conditions are
included in the protocol specifications. (a) or (b) will be M/R/RE/X.
Element name Shows the field name.
Protocol Specifications Field details are included in the protocol specifications.

LAB-27 Transaction Specifications
LAB-27 transaction is a communication transaction to query the orders.
A specific query about the conditions of the QBP message is sent from the analyzer
to the Analyzer Manager (sample system). (The Analyzer Manager is hereafter
referred to as “AM”.)
After querying, it is necessary for the AM to return a response as to whether the
query to the analyzer in regard to the RSP message was accepted.
AM Analyzer
QBP^Q11^QBP_Q11
(Query for AWOS)
Specimen
recognized
RSP^K11^RSP_K11
(Acknowledgement of Query)
QBP (Query By Parameter) Messages
These messages are for the analyzer querying the AM for orders. Set the query
conditions in the QPD segment.
• MESSAGE: QBP^Q11^QBP_Q11
• Message Semantics
Segment Remarks
MSH Message header
QPD Query Parameter Definition
RCP Response Control Parameter
Segment: MSH
SEQ LEN DT OPT Element Name Protocol Specifications
1 1 ST M Field Separator | (fixed)
2 4 ST M Encoding Characters ^~¥ (fixed)
3 227 HD M Sending Application
1 20 IS R namespace ID Application name of the analyzer set on the System window
Example: MEK-9100
4 227 HD M Sending Facility
1 20 IS R namespace ID Facility name of the analyzer set on the System window
Example: Laboratory
5 227 HD M Receiving Application
1 20 IS R namespace ID AM application name
MSH-3 content in the message received from the AM is set.
If a message is not received from the AM, ”” (double quotes)
are set.
(Continued on next page)

Segment: MSH
6 227 HD M Receiving Facility
1 20 IS R namespace ID AM facility name
are set.
7 26 TS M Date/Time of Message
1 19 DTM R Time Time message sent
Format: YYYYMMDDhhmmss
9 15 MSG M Message Type
1 3 ID R Message Code QBP (fixed)
2 3 ID R Trigger Event Q11 (fixed)
3 7 ID R Message Structure QBP_Q11 (fixed)
10 50 ST M Message Control ID Identifier specifying if the message is unique
Format: YYYYMMDDhhmmssXXXX
XXXX is a 4-digit number from 0000 to 9999. Starting from
0000, it increments by 1 whenever a message is sent. It returns
to 0000 after 9999.
11 3 PT M Processing ID
1 1 ID R Processing ID P (fixed)
12 60 VID M Version ID
1 5 ID R Version ID 2.5 (fixed)
15 2 ID M Accept
Acknowledgement Type
NE (fixed)
16 2 ID M Application
AL (fixed)
18 16 ID M Character Set Character set of the analyzer
If a message is not received from the AM, the character set
which is set on the System window is set.
21 427 EI M Message Profile Identifier
1 50 ST R Entity Identifier LAB-27 (fixed)
2 3 IS R Namespace ID IHE (fixed)

Segment: QPD
1 60 CE M Message Query Name
1 7 ST R Identifier WOS: When there is a query depending on the
sampling tube barcode
WOS_BY_RACK: When there is a query depending on the
rack position
2 19 ST R Text Work Order Step: When there is a query depending on
the sampling tube bar code
Work Order Step by Rack: When there is a query depending on
the rack position
single-byte space (0x20)
3 6 ID R Name of Coding System IHELAW (fixed)
2 32 ST M Query Tag Identifier specifying if the QPD segment is unique
The same content as MSH-10 is set.
3 80 EI C (M/X) SAC-3: Container Identifier
1 50 ST R Entity Identifier Barcode ID (sample ID) of sampling tube used in query to AM
When this field is used, QPD-4 and QPD-5 are not set.
When QPD-1-1 is “WOS”, this is not set.
4 80 EI C (M/X) SAC-10: Carrier Identifier
1 50 ST R Entity Identifier Barcode ID in the rack which is used for request
When this field is used, QPD-3 is not set.
5 80 NA C (M/X) SAC-11: Position in Carrier
1 16 NM R Value1 Location in the rack which is used for request
Valid range: 1-10
When this field is used, QPD-3 is not set.
Segment: RCP
1 1 ID M Query Priority I (fixed)
3 60 CE M Response Modality
1 1 ST R Identifier R (fixed)
2 9 ST O Text Real Time (fixed)
Single-byte space (0x20)
3 7 ID R Name of Coding System HL70394 (fixed)

RSP (Segment Pattern Response) Messages
These messages are for the AM sends response to analyzer after receiving query
from the analyzer. Set the response contents in the QAK segment.
• MESSAGE: RSP^K11^RSP_K11
Segment Remarks
MSH Message header
MSA Message Acknowledgement
[ERR] Error
QAK Query Acknowledgement
QPD Query Parameter Definition
Segment: MSH
1 20 IS R namespace ID Analyzer application name
Matches the MSH-3 of the message that was just sent by the
analyzer.
1 20 IS R namespace ID Analyzer facility name
Matches the MSH-4 of the message that was just sent by the
analyzer.
1 3 ID R Message Code RSP (fixed)
2 3 ID R Trigger Event K11 (fixed)
3 7 ID R Message Structure RSP_K11 (fixed)
10 20 ST M Message Control ID Matches the MSH-10 of the message that was just sent by the
analyzer.
15 2 ID M Accept
NE (fixed)
AL (fixed)

Segment: MSH
18 16 ID M Character Set Character set used for AM
For the character sets that can be used, refer to “Character Set
Code System” (p. 35).
Segment: MSA
1 2 ID M Acknowledgment Code Response codes
One of the following responses is sent.
AA: When message is accepted
AE: When message has an error
AR: When MSH segment has an error
2 50 ST M Message Control ID MSH-10 content is set.
Segment: ERR
2 18 ERL RE Error Location
1 3 ST R Segment ID Segments
2 2 NM R Segment Sequence Segments
3 2 NM RE Field Position Position of field that has error
4 2 NM RE Field Repetition Position of repeated field that has error
5 2 NM RE Component Number Position of component that has error
6 2 NM RE Sub-Comonen Number Position of subcomponent that has error
3 705 CWE M HL7 Error Code
1 20 ST R Identifier Error code when MSA-1 is AE or AR
For details, refer to “Error Code System” (p. 35).
2 199 ST RE Text Explanation for error codes
4 2 ID M Severity E (fixed)

Segment: QAK
1 32 ST M Query Tag Matches the MSH-10 of the message that was just sent by the
analyzer.
2 2 ID M Quantity Response Status Query response codes
Set one of the following codes.
OK: When query is accepted
AE: When query has an error
AR: When query is rejected
3 60 CE M Message Query Name
1 7 ST R Identifier Matches the QPD-1-1 content of the message that was just sent
by the analyzer.
2 19 ST R Text Matches the QPD-1-2 content of the message that was just sent
by the analyzer.
3 6 ID R Name of Coding System IHELAW (fixed)

LAB-28 transaction is a communication transaction in which the order sent
by the Analyzer Manager (sample system) is received by the analyzer. (The
Analyzer Manager is hereafter referred to as “AM”.)
The AM sends an OML message to the analyzer and the order is sent.
The analyzer sends an ORL message to the AM and an acceptance response is
sent.
AM Analyzer
ORLÔ34
Order Accepted (ORC-1: OK)
Unable to Accept (ORC-1: UA)
OMLÔ33
New Order (ORC-1: NW)
ORLÔ34
Order Canceled (ORC-1: CR)
Unable to Cancel (ORC-1: UC)
OMLÔ33
Order Cancel (ORC-1: CA)
OML (Laboratory Order Message) Messages
These messages are for the AM sending the orders to the analyzer.
• MESSAGE: OMLÔ33ÔML_O33
Segment Remarks
MSH Message header
[ --- PATIENT begin
PID Patient Identification
[PV1] Patient Visit
] --- PATIENT end
{ --- SPECIMEN begin
SPM Specimen
[{ --- SPECIMEN_CONTAINER begin
SAC Specimen Container
}] --- SPECIMEN_CONTAINER end
{ --- ORDER begin
ORC Common Order (for one battery)
[ --- OBSERVATION REQUEST begin
OBR Observation Request
[{ --- OBSERVATION begin
OBX Observation/Result
}] --- OBSERVATION end
] --- OBSERVATION REQUEST end
} --- ORDER end
] --- SPECIMEN end

Segment: MSH
1 3 IS R Message Code OML (fixed)
2 3 IS R Trigger Event O33 (fixed)
3 7 IS R Message Structure OML_O33 (fixed)
10 20 ST M Message Control ID Identifier specifying if the message is unique
11 3 PT M Processing Id
1 1 ID R processing ID P (fixed)
15 2 ID M Accept
NE (fixed)
AL (fixed)
18 16 ID M Character Set Character set by AM

For the character sets that can be used, refer to“Character Set

Segment: PID
3 250 CX R Patient Identifier List
1 50 ST R ID Patient ID
5 250 XPN R Patient Name
1 50 ST RE family name Family name of the patient
2 30 ST RE given name Given name of the patient
3 30 ST RE second and further given
names
Other given names of the patient
7 1 ID R name type code “L” (fixed)
7 26 DTM RE Date/Time of Message Date of birth of the patient
Format: YYYYMMDD
8 1 IS RE Administrative Sex Patient gender
F: Female
M: Male
U: Unspecified
If other than the above:
The order is treated as invalid and discarded.
Segment: PV1
3 80 PL RE Assigned Patient Location
1 20 IS R Room Patient location
Segment: SPM
SEQ LEN DT OPT Element name Protocol Specifications
11 250 CWE M Specimen Role
1 20 ST R Identifier Sample type
P: Patient blood
Q: Control blood

Segment: SAC
3 80 EI C (M/X) Container Identifier
1 20 ST R Entity Identifier Barcode ID of sample tube

When System Setting Work Orders Order key is set to
“Aspiration tube” and this field is set, this order is treated as
invalid and discarded.
10 80 EI C (M/X) Carrier Identifier
1 20 ST R Entity Identifier Barcode ID of rack
When the barcode ID is from a rack tray that is not Nihon
Kohden, the order is treated as invalid and discarded.

“Sample ID” and this field is set, this order is treated as invalid
and discarded.
11 80 NA C (M/X) Position in Carrier
1 16 NM M Value1 Aspiration tube rack position
Valid range: 1-10

When out of range, the order is treated as invalid and discarded.

“Sample ID” and this field is set, this order is treated as invalid
and discarded.
Segment: ORC
1 2 ID M Order Control Order control code
NW: Set when AM adds an order to the analyzer. When there
are unmeasured orders which match the SAC segment
information at the analyzer side, the analyzer overwrites
it. When that order is being processed (measured), the
analyzer refuses it.
CA: Set when AM cancels an order to the analyzer. When
there are unmeasured orders which match the SAC
segment information, the analyzer cancels it. When that
order is being processed (measured) or processing is
complete (measurement complete, report complete), the
analyzer refuses it.

Segment: OBR
2 50 EI M Placer Order Number (AWOS ID)
1 50 ST R Entity Identifier Unique identifier ID for the order for the AM
4 250 CE M Universal Service Identifier
1 20 ST R Identifier Identifier of the measurement item in the order
For measurement item identifiers, refer to “Measurement Items
2 199 ST R Text Name of the measurement item in the order
3 20 ID R Name of Coding System Name of the system of the measurement item order code
For code system names, refer to “Measurement Items Code
System” (p. 31).
16 250 XCN RE Ordering Provider
2 50 FN O Family Name Family name of the physician
3 30 ST O Given Name Given name of the physician
4 30 ST O Second Name Other given names of the physician
Segment: OBX
1 4 SI M Set ID-OBX Segment identifier number starts from 1
3 250 CE M Observation Identifier
Use of this field for measurement items in a work order is not
recommended. Use the QBR-4-1.
3 20 ID R Name of Coding System Name of the system of the measurement item order code
System” (p. 31).
Use of this field for measurement items in a work order is not
recommended. Use the QBR-4-3.

ORL (Laboratory Order Acknowledgment) Messages
These are messages for the analyzer sending a response for the order to the AM.
Set the response contents in the ORC segment.
• MESSAGE: ORL^O34^ORL_O34
Segment Remarks
MSH Message header
[{ERR}] Error
[ --- RESPONSE begin
[ --- PATIENT begin
PID Patient Identification
] --- PATIENT end
SPM Specimen
[{SAC}] Specimen Container
[{ --- ORDER begin
ORC Common Order
}] --- ORDER end
} --- SPECIMEN end
] --- RESPONSE end

Segment: MSH
SEQ LEN DT OPT Element name Protocol Specifications
Example: MEK-9100
Example: Laboratory
1 3 ID R Message Code ORL (fixed)
2 3 ID R Trigger Event O34 (fixed)
3 7 ID R Message Structure ORL_O34 (fixed)
10 20 ST M Message Control ID MSH-10 content in the message received from the AM is set.
15 2 ID M Accept
Acknowledgement
Type
NE (fixed)
Acknowledgement
Type
AL (fixed)

Segment: MSA
AA: When message was accepted
2 50 ST M Message Control ID MSH-10 content is set.
Segment: ERR
2 18 ERL R Error Location
1 3 ST R Segment ID Segment that has an error
2 2 NM R Segment Sequence Position of segment that has error
6 2 NM RE Sub-Comonen Number Position of subcomponent that has error
Segment: ORC
1 2 ID M Order Control Order control code
OK: When order is accepted
UA: When order has an error and cannot be accepted
CR: When order is successfully canceled
UC: When order was not able to be canceled1
1
Use when order is being processed (measured) or handling is
finished (measurement, report).

A LAB-29 transaction is a communications transaction where the analyzer sends
measurement results to the Analysis Manager (sample system). (The Analyzer
Manager is hereafter referred to as “AM”.)
Sends measurement results by OUL message from the analyzer to the AM.
For the AM, it is necessary to send a response to the analyzer by an ACK
message as to whether or not the measurement results were accepted.
If measurement results are based on a LAB-28 received order, the content of
each segment in the OUL message is nearly the same as the segments in the
LAB-28 OUL message except for some parts.
For fields that have discrepancies, refer to the protocol specifications for each
field.
AM Analyzer
ACK^R22 (Result Accepted)
OUL^R22 (Test Result)
OUL (Unsolicited Laboratory Observation) Messages
These messages are for the analyzer sending the measurement results to the AM.
Set the measurement results contents in the OBX segment.
• MESSAGE: OUL^R22^OUL_R22
Segment Remarks
MSH Message header
[ --- PATIENT begin
[PID] Patient Identification
Same as the OML message PID segment. When
the analyzer creates a work order, generated
content for each field is set.
] --- PATIENT end
[ --- PATIENT begin
[PV1] Patient Visit
When the analyzer creates a work order,
generated content for each field is set.
] -- VISIT end
SPM Specimen information
[{ --- CONTAINER begin
SAC Container information
Same as the OML message SPM segment. When
the analyzer creates a work order, generated
content for each field is set.

Segment Remarks
}] --- CONTAINER end
{ --- ORDER begin
OBR Observation Order
Same as the OML message OBR segment.
[{NTE}] Notes and comments (for Order)
Set the comment for the work order.
[ORC] Common Order
Same as the OML message ORC segment.
[{ TIMING_QTY begin
TQ1 Timing Quantity
Same as the OML message TQ1 segment. When
the analyzer creates an order, this is not set.
}] TIMING_QTY end
[{ --- RESULT begin
OBX Observation Result
}] --- RESULT end
} --- ORDER end
} --- SPECIMEN end

Segment: MSH
Example: MEK-9100
Example: Laboratory
1 20 IS R namespace ID MSH-3 content in the message received from the AM is set.
are set.
1 20 IS R namespace ID MSH-4 content in the message received from the AM is set.
are set.
1 3 ID R Message Code OUL (fixed)
2 3 ID R Trigger Event R22 (fixed)
3 7 ID R Message Structure OUL_R22 (fixed)
10 20 ST M Message Control ID Identifier to uniquely specify a message
Format: YYYYMMDDhhmmssXXXX
XXXX is a 4-digit number from 0000 to 9999. Starting from
0000, it increments by 1 whenever a message is sent. It returns
to 0000 after 9999.
15 2 ID M Accept
NE (fixed)
AL (fixed)
18 16 ID M Character Set MSH-18 content in the message received from the AM is set.

Segment: PID
3 250 CX RE1
Patient Identifier List
1 50 ST R ID Patient ID
When create a work order on the analyzer and the patient ID is
not entered, it is empty data.
5 250 XPN RE1
Patient Name
1 50 ST RE family name Family name of the patient
When create a work order on the analyzer and the patient name
is not entered, it is empty data.
2 30 ST RE given name Given name of the patient
3 30 ST RE second and further given
names
Other given names of the patient
7 1 ID R name type code L (fixed)
7 24 DTM O Date/Time of Message Date of birth of the patient
Format: YYYYMMDD
8 1 IS O Administrative Sex Patient gender
F: Female
M: Male
U: Unspecified
1
R in the LAW profile, but RE in the MEK-9100.
Segment: PV1
3 80 PL RE Assigned Patient Location
1 20 IS R Room Patient location

Segment: SPM
1 4 SI M Set ID-SPM Segment identifier number starts from 1
2 80 EIP RE Specimen ID
2 80 EI R Filler Assigned Identifier
1 50 ST R Entity Identifier Sample ID of measurement results
3 199 ST O Universal ID Set the same content as SPM-2-2-1.
11 250 CWE M Specimen Role
1 20 ST R Identifier Sample type
P: Patient sample
Q: Control
2 199 ST R Text Explanation of sample types
Patient specimen: Identifier is P
Control specimen: Identifier is Q
3 7 ID R Name of Coding System Set HL70369 (fixed) when order is created on analyzer.
Segment: SAC
3 80 EI C (M/X) Container Identifier

When System Setting Work Orders Order key is “Aspiration
tube”, this field is not set.
10 80 EI C (M/X) Carrier Identifier

When System Setting Work Orders Order key is “Sample
ID”, this field is not set.
11 80 NA C (M/X) Position in Carrier
1 16 NM M Value1 Aspiration tube rack position
Valid range: 1-10

When System Setting Work Orders Order key is “Sample
ID”, this field is not set.

Segment: OBR
1 4 SI M Set ID-OBR Segment identifier number starts from 1
3 50 EI O Filler Order Number
1 50 ST R Entity Identifier Indentifier for orders managed by the analyzer
4 250 CE M Universal Service Identifier
For measurement item identifiers, refer to “Measurement
Items Code System” (p. 31).
For measurement item identifiers, refer to “Measurement
Items Code System” (p. 31).
3 20 ID O Name of Coding System Name of the system of the measurement item order code
System” (p. 31).
Segment: ORC
1 2 ID M Order Control SC (fixed)
5 2 ID M Order Status CM (fixed)

Segment: OBX
1 4 SI M Set ID-OBX Segment identifier number starts from 1
2 2 ID M Value Type Set one of the followings.
NM: Measurement value information
ED: Histogram or scattergram images
3 250 CE M Observation Identifier
1 20 ST R Identifier Measurement parameter code
Refer to “Measurement Items Code System” (p. 31).
2 199 ST R Text Measurement parameter name
3 12 ID R Name of Coding System Code name of the measurement parameter
5 99999 Var C (M/X)1
Observation Value
1 20 Var M Value/Source application When OBX-2 is NM: Measurement value
When there is no value, ”” (double
quotes) are set.
When OBX-2 is ED: Analyzer name in system settings
2 20 ID O Type of Data When OBX-2 is NM: Not set
When OBX-2 is ED: IM (fixed)
3 20 ID O Subtype When OBX-2 is NM: Not set
When OBX-2 is ED: PNG (fixed)
4 20 ID O Encoding When OBX-2 is NM: Not set
When OBX-2 is ED: Base64 (fixed)
5 99999 TX O Data When OBX-2 is NM: Not set
When OBX-2 is ED: base64 image data
6 250 CE C (M/X) Units
1 20 ST R Identifier When OBX-2 is NM: Unit code
When OBX-2 is ED: Not set
Refer to “Code System Specifications” (p. 34).
2 199 ST R Text When OBX-2 is NM: Unit name
3 12 ID R Name of Coding System When OBX-2 is NM: Name of unit code system
7 70 ST C (M/X) Reference Range When OBX-2 is NM: Standard range of analyzer
Set the upper and lower limit values joined by a hyphen.
Example: 3.5-4.5

Segment: OBX
8 250 CWE C (M/X)1
Interpretation Codes
1 20 ST R Identifier When OBX-2 is NM: Abnormal flag code
Refer to “Abnormal Flag Code System” (p. 35).
When there no abnormal flag, set ”” (double quotes).
2 199 ST RE Text When OBX-2 is NM: Explanation for abnormal flags
3 12 ID R Name of Coding System When OBX-2 is NM: Name of the abnormal flag code system
11 1 ID M Observation Result
Status
F (Fixed)
18 427 EI M Equipment Instance Identifier
1 50 ST R Model
Serial number
Vendor/site defined
Model and serial number are delimited by a repeat delimiter (˜).
Example: MEK-9100˜0000001
29 4 ID M Observation Type RSLT (fixed)
1
M is in the LAW profile, but C (M/X) is in the MEK-9100.

ACK (General Acknowledgement) Messages
These are messages for the AM sending response for measurement results to the
analyzer. Set the response contents in the MSA segment.
• MESSAGE: ACK^R22^ACK_R22
Segment Remarks
MSH Message header
[{NTE}] Error
Segment: MSH
1 20 IS R namespace ID Analyzer application name
Matches the MSH-3 content of the message that was just sent
by the analyzer.
1 20 IS R namespace ID Analyzer facility name
Matches the MSH-4 content of the message that was just sent
by the analyzer.
1 3 ID R Message Code ACK (fixed)
2 3 ID R Trigger Event R22 (fixed)
3 7 ID R Message Structure ACK_R22 (fixed)
10 20 ST M Message Control ID Matches the MSH-10 content of the message that was just sent
by the analyzer.
15 2 ID M Accept
NE (fixed)
AL (fixed)

Segment: MSA
AA: When message was accepted
2 50 ST M Message Control ID Set the MSH-10 content.
Segment: ERR
2 18 ERL RE Error Location
1 3 ST R Segment ID Segment that has an error
2 2 NM R Segment Sequence Segments
6 2 NM RE Sub-Component Number Position of subcomponent that has error

Code System Specifications
This section describes the code system that is used in the content of the message.
Measurement Items Code System
In the measurement item code system, order codes set by the AM in the OBR-4
fields (or OBX-3 fields) in the OML message in the LAB-28 transaction, and
result codes set by the analyzer in the OBX-3 field in the OUL message in the
LAB-29 transaction are separated.
The relation between the order code and the result code is shown below.
Name of Coding System: 99UNK
Request Codes Result Codes
Identifier Text (optional) Identifier Text
CBC CBC order WBC White Blood Cell Count
RBC Red Blood Cell Count
HGB Hemoglobin
HCT Hematocrit
MCV Mean Corpuscular Volume
MCH Mean Corpuscular Hemoglobin
MCHC Mean Corpuscular Hemoglobin
Concentration
PLT Platelet Count
RDW-CV Red Blood Cell Distribution Width in
CV
RDW-SD Red Blood Cell Distribution Width in
SD
PCT Plateletcrit
MPV Mean Platelet Volume
PDW Platelet Distribution Width
P-LCR Platelet Large Cell Ratio
DIFF WBC Differential order NE Neutrophil Count
LY Lymphocyte Count
MO Monocyte Count
EO Eosinophil Count
BA Basophil Count
NE% Neutrophil Percent
LY% Lymphocyte Percent
MO% Monocyte Percent
EO% Eosinophil Percent
BA% Basophil Percent
WBC White Blood Cell Count WBC White Blood Cell Count
RBC Red Blood Cell Count RBC Red Blood Cell Count
HGB Hemoglobin HGB Hemoglobin

Name of Coding System: 99UNK
HCT Hematocrit HCT Hematocrit
MCV Mean Corpuscular Volume MCV Mean Corpuscular Volume
MCH Mean Corpuscular Hemoglobin MCH Mean Corpuscular Hemoglobin
Concentration
Concentration
PLT Platelet Count PLT Platelet Count
NE Neutrophil Count NE Neutrophil Count
LY Lymphocyte Count LY Lymphocyte Count
MO Monocyte Count MO Monocyte Count
EO Eosinophil Count EO Eosinophil Count
BA Basophil Count BA Basophil Count
NE% Neutrophil Percent NE% Neutrophil Percent
LY% Lymphocyte Percent LY% Lymphocyte Percent
MO% Monocyte Percent MO% Monocyte Percent
EO% Eosinophil Percent EO% Eosinophil Percent
BA% Basophil Percent BA% Basophil Percent
CV
CV
SD
SD
PCT Plateletcrit PCT Plateletcrit
MPV Mean Platelet Volume MPV Mean Platelet Volume
PDW Platelet Distribution Width PDW Platelet Distribution Width
P-LCR Platelet Large Cell Ratio P-LCR Platelet Large Cell Ratio
@P-LCC1
Platelet Large Cell Count (Only research
use)
@P-LCC1
Platelet Large Cell Count (Only research
use)
@MentzerIndex1
MentzerIndex (Only research use) @MentzerIndex1
MentzerIndex (Only research use)
@RDWI1
Red blood cell Distribution Width Index
(Only research use)
@RDWI1
Red blood cell Distribution Width Index
(Only research use)
@IG1
Immature Granulocyte Count (Only
research use)
@IG1
Immature Granulocyte Count (Only
research use)
@IG%1
Immature Granulocyte Percent (Only
research use)
@IG%1
Immature Granulocyte Percent (Only
research use)
@Band1
Band cell Count (Only research use) @Band1
Band cell Count (Only research use)
@Band%1
Band cell Percent (Only research use) @Band%1
Band cell Percent (Only research use)
@Seg1
Segmented neutrophils Count (Only
research use)
@Seg1
Segmented neutrophils Count (Only
research use)
@Seg%1
Segmented neutrophils Percent (Only
research use)
@Seg%1
Segmented neutrophils Percent (Only
research use)
1

Items in which @ is attached are research parameters.

Name of Coding System: JC10
2A9900000019920: Peripheral blood normal sample
(whole blood)
2A990000001992051 RBC count (whole blood)
2A990000001992052 WBC count (whole blood)
2A990000001992053 Hemoglobin (whole blood)
2A990000001992054 Hematocrit (whole blood)
2A990000001992055 Platelet count (whole blood)
2A990000001992056 MCV (whole blood)
2A990000001992057 MCH (whole blood)
2A990000001992058 MCHC (whole blood)
2A1600000019301: Blood Profile (whole blood) 2A160000001930151 Neutrophils (whole blood)
2A160000001930154 Eosinophils (whole blood)
2A160000001930155 Basophils (whole blood)
2A160000001930156 Monocytes (whole blood)
2A160000001930157 Lymphocytes (whole blood)
Name of Coding System: LN
58410-2 Complete blood count (hemogram) panel 6690-2 WBC
789-8 RBC
718-7 HGB
4544-3 HCT
787-2 MCV
785-6 MCH
786-4 MCHC
777-3 PLT
788-0 RDW-CV
21000-5 RDW-SD
32623-1 MPV
57023-4 Auto Differential panel 751-8 NE
731-0 LY
742-7 MO
711-2 EO
704-7 BA
770-8 NE%
736-9 LY%
5905-5 MO%
713-8 EO%
706-2 BA%

Name of Coding System: LN
57021-8 CBC W Auto Differential panel 6690-2 WBC
789-8 RBC
718-7 HGB
4544-3 HCT
787-2 MCV
785-6 MCH
786-4 MCHC
777-3 PLT
788-0 RDW-CV
21000-5 RDW-SD
32623-1 MPV
751-8 NE
731-0 LY
742-7 MO
711-2 EO
704-7 BA
770-8 NE%
736-9 LY%
5905-5 MO%
713-8 EO%
706-2 BA%
Code System Specifications
Name of Coding System: UCUM
Identifier Text
10*2/uL hundred per microliter
10*3/uL thousand per microliter
10*4/uL ten thousand microliter
10*6/uL million per microliter
10*9/L billion per liter
10*12/L trillion per liter
/uL per micro liter
pg picogram
% percent
fL femtoliter
g/dL gram per deciliter
g/L gram per liter
fmol femtomole
mmol/L millimole per liter

Abnormal Flag Code System
Name of Coding System: HL70078
Identifier Text
L Low
H High
Name of Coding System: 99FNK
Identifier Text
* Possibility of abnormal cells
? Low data reliability with a measurement alarm
! Possibility of poor hemolyzation
C Possibility of PLT clumps
Error Code System
Name of Coding System: HL70357
Identifier Text
100 Segment sequence error
101 Required field missing
102 Data type error
103 Table value not found
200 Unsupported message type
201 Unsupported event code
202 Unsupported processing id
203 Unsupported version id
207 Application internal error
Character Set Code System
HL7 Table 0211
Value Description Note
UNICODE UTF-8 UTF-8 encoding method
is defined in Unicode
UTF-8 is recommended in the LAW profile.

Data Communication Examples
MEK-9100 Communication Examples
The followings show the communication example between the MEK-9100 and
AM.
For examples of AM sent messages, which the MEK-9100 requires for minimum
limit are shown in bold.
If there are no fields with bold items, it becomes a communication error and the
message received by the MEK-9100 is discarded.
Message examples with MLLP have SB or EBCR abbreviated.
Order Communication using Sample Tube Barcode ID
Example of Order Query from LAB-27
The following example shows an order query message to the AM with the
sampling tube barcode ID (SAMPLEID0001) from the MEK-9100.
MEK-9100 outputs a sampling tube barcode ID to QPD-3.
Example of MEK-9100 Sent Message
MSH|^~¥|MEK-9100|Laboratory|LIS|Laboratory|20150903131244||QBP^Q11^QBP_
Q11|ID201509031312440002|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-27ÎHECR
QPD|WOS^Work Order StepÎHELAW|ID201509031312440003|SAMPLEID0001CR
RCP|I||R^Real Time^HL70394CR
The following example shows a message where the AM accepted the query.
Example of AM Sent Message
MSH|^~¥|LIS|Laboratory|MEK-9100|Laboratory|20150903131245||RSP^K11^RSP_
K11|LAWAM00000001|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-27ÎHECR
MSA|AA|ID201509031312440003CR
QAK|ID201509031312440003|OK|WOS^Work Order StepÎHELAW|1CR
QPD|WOS^Work Order StepÎHELAW|ID201509031312440003|SAMPLEID0001CR

Example of Order Received from LAB-28
The following example shows a message when the AM sends order information
to the MEK-9100, in regard to the necessity of an MEK-9100 query in the
“Example of Order Query from LAB-27” (p. 36).
The AM outputs a sample order item to OBR segment.
When Ordering by Sample Name
MSH|^~¥|LIS|Laboratory|MEK-9100|Laboratory|20150903131247||OMLÔ33ÔML_
O33|LAWAM00000001|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-28ÎHECR
PID|||1234567890||Smith^John^^^^^L||19800502|MCR
PV1|||Room0001CR
SPM|||||||||||P^Patientspecimen^HL70369CR
SAC|||SAMPLEID0001CR
ORC|NWCR
OBR|1|20150903101333||CBC^CBC order^99UNK||||||||||||12345^Roe^RichardCR
ORC|NW|20150903101333CR
OBR|1|20150903101333||DIFF^WBC Differential order^99UNK||||||||||||12345^Roe^RichardCR
When Ordering by Specified Measurement Parameter
PV1|||Room0001CR
ORC|NWCR
OBR|1|20150903101333||WBC^White Blood Cell Count^99UNK||||||||||||12345^Roe^RichardCR
ORC|NWCR
OBR|1|20150903101333||RBC^Red Blood Cell Count^99UNK||||||||||||12345^Roe^RichardCR
ORC|NWCR
OBR|1|20150903101333||PLT^Platelet Count^99UNK||||||||||||12345^Roe^RichardCR

Example of Measurement Result Sent from LAB-29
The following example shows a message when the AM receives measurement
results from the MEK-9100, in regard to AM order information in the “Example
of Order Received from LAB-28” (p. 37).
MSH|^~¥|MEK-9100|Laboratory|LIS|Laboratory|20150903155410||OUL^R22ÔUL_
R22|ID201509031554100000|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-29ÎHECR
PV1|||Room0001CR
SPM|1|^SAMPLEID0001SAMPLEID0001|||||||||P^Patientspecimen^HL70369CR
OBR|1|20150903101333||CBC^CBC order^99UNK||||||||||||12345^Roe^Richard|||||||||FCR
NTE||Z|comment...CR
ORC|SC||||CMCR
OBX|1|NM|WBC^White Blood Cell Count^99UNK||41.1|10*2/uL^hundred per microliterÛCUM|40.0 - 90.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|2|NM|RBC^Red Blood Cell Count^99UNK||496|10*4/uL^ten thousand microliterÛCUM|376 - 570||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|3|NM|HGB^Hemoglobin^99UNK||14.06|g/dL^gram per deciliterÛCUM|12.00 - 17.99||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|4|NM|HCT^Hematocrit^99UNK||36.9|%^percentÛCUM|33.5 - 52.0||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|5|NM|MCV^Mean Corpuscular Volume^99UNK||74.4|fL^femtoliterÛCUM|80.0 - 100.0|L^Low^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|6|NM|MCH^Mean Corpuscular Hemoglobin^99UNK||28.3|pg^picogramÛCUM|28.0 - 32.1||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|7|NM|MCHC^Mean Corpuscular Hemoglobin Concentration^99UNK||38.1|g/dL^gram per deciliterÛCUM|30.9 -
35.0|!^^99FNK|||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|8|NM|RDW-CV^Red Blood Cell Distribution Width in CV^99UNK||14.3|%^percentÛCUM|11.6 -
14.0|H^High^HL70078|||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|9|NM|RDW-SD^Red Blood Cell Distribution Width in SD^99UNK||76.9|fL^femtoliterÛCUM|39.0 -
OBX|10|NM|PLT^Platelet Count^99UNK||16.03|10*4/uL^ten thousand microliterÛCUM|15.00 - 35.00||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|11|NM|PCT^Plateletcrit^99UNK||0.12|%^percentÛCUM|0.16 - 0.33|L^Low^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|12|NM|MPV^Mean Platelet Volume^99UNK||7.7|fL^femtoliterÛCUM|7.0 - 11.0||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|13|NM|PDW^Platelet Distribution Width^99UNK||17.8|%^percentÛCUM|15.0 - 17.0|H^High^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|14|NM|P-LCR^Platelet Large Cell Ratio^99UNK||48.8|%^percentÛCUM|20.0 - 58.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBR|2|20150903101333||DIFF^WBC Differential order^99UNK||||||||||||12345^Roe^Richard|||||||||FCR
ORC|SC||||CMCR
OBX|1|NM|NE%^Neutrophil Percent^99UNK||46.89|%^percentÛCUM|28.00 - 78.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|2|NM|LY%^Lymphocyte Percent^99UNK||36.11|%^percentÛCUM|17.00 - 57.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|3|NM|MO%^Monocyte Percent^99UNK||14.55|%^percentÛCUM|0.00 - 10.00|H^High^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|4|NM|EO%Êosinophil Percent^99UNK||2.15|%^percentÛCUM|0.00 - 10.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|5|NM|BA%^Basophil Percent^99UNK||0.30|%^percentÛCUM|0.00 - 2.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|6|NM|NE^Neutrophil Count^99UNK||19.3|10*2/uL^hundred per microliterÛCUM|11.0 - 70.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|7|NM|LY^Lymphocyte Count^99UNK||14.8|10*2/uL^hundred per microliterÛCUM|7.0 - 51.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|8|NM|MO^Monocyte Count^99UNK||6.0|10*2/uL^hundred per microliterÛCUM|0.0 - 9.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|9|NM|EOÊosinophil Count^99UNK||0.9|10*2/uL^hundred per microliterÛCUM|0.0 - 9.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|10|NM|BA^Basophil Count^99UNK||0.1|10*2/uL^hundred per microliterÛCUM|0.0 - 2.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR

Order Communication with Sampling Tube Position in the Rack
Example of Order Query from LAB-27
Sampling tube position in the rack can be queried to the AM.
The rack tray ID (barcode ID attached in the rack tray) is queried as an order to
the Analyzer Manager as sampling tube position “0210” on the rack (8th from
the left).
MSH|^~¥|MEK-9100|Laboratory|LIS|Laboratory|20150903143044||QBP^Q11^QBP_
Q11|ID201509031430440003|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-27ÎHECR
QPD|WOS_BY_RACK^Work Order Step by RackÎHELAW|ID201509031430440004||0210|8CR
RCP|I||R^Real Time^HL70394CR
When the AM accepts the query, a message such as below is sent.
Example of Message Received from AM
MSH|^~¥|LIS|Laboratory|MEK-9100|Laboratory|20150903143045||RSP^K11^RSP_
K11|LAWAM00000003|P|2.5|||NE|AL||UNICODE UTF-8|||LAB-27ÎHECR
MSA|AA|ID201509031430440004CR
QAK|ID201509031430440004|OK|WOS_BY_RACK^Work Order Step by RackÎHELAW|1CR
QPD|WOS_BY_RACK^Work Order Step by RackÎHELAW|ID201509031430440004||0210|8CR
The following example shows a message when the AM sends order information
to the MEK-9100, in regard to the necessity of an MEK-9100 query in the
“Example of Order Query from LAB-27” (p. 39).
The AM outputs a sample order item to OBR segment.
PV1|||Room0001CR
SAC||||||||||0210|8CR
ORC|NWCR
OBR|1|20150903101333||CBC^CBC order^99UNK||||||||||||12345^Roe^RichardCR
ORC|NWCR
OBR|1|20150903101333||DIFF^WBC Differential order^99UNK||||||||||||12345^Roe^RichardCR

The following example shows a message when the AM receives measurement
results from the MEK-9100, in regard to AM order information in the “Example
of Order Received from LAB-28” (p. 39).
PV1|||Room0001CR
SPM|1||||||||||P^Patientspecimen^HL70369CR
SAC||||||||||0210|8CR
OBR|1|20150903101333||CBC^CBC order^99UNK||||||||||||12345^Roe^Richard|||||||||FCR
NTE||Z|comment...CR
ORC|SC||||CMCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
OBX|3|NM|HGB^Hemoglobin^99UNK||14.06|g/dL^gram per deciliterÛCUM|12.00 - 17.99||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|5|NM|MCV^Mean Corpuscular Volume^99UNK||74.4|fL^femtoliterÛCUM|80.0 - 100.0|L^Low^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
35.0|!^^99FNK|||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|8|NM|RDW-CV^Red Blood Cell Distribution Width in CV^99UNK||14.3|%^percentÛCUM|11.6 -
OBX|9|NM|RDW-SD^Red Blood Cell Distribution Width in SD^99UNK||76.9|fL^femtoliterÛCUM|39.0 -
9100~00001|||||||||||RSLTCR
OBX|11|NM|PCT^Plateletcrit^99UNK||0.12|%^percentÛCUM|0.16 - 0.33|L^Low^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|13|NM|PDW^Platelet Distribution Width^99UNK||17.8|%^percentÛCUM|15.0 - 17.0|H^High^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|14|NM|P-LCR^Platelet Large Cell Ratio^99UNK||48.8|%^percentÛCUM|20.0 - 58.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBR|2|20150903101333||DIFF^WBC Differential order^99UNK||||||||||||12345^Roe^Richard|||||||||FCR
ORC|SC||||CMCR
OBX|3|NM|MO%^Monocyte Percent^99UNK||14.55|%^percentÛCUM|0.00 - 10.00|H^High^HL70078|||F|||||||MEK-
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR

When Sending QC Data
The example shows when QC data is sent from the MEK-9100. QC data does not
support queries from LAB-27 or receiving orders from LAB-28.
Example of Quality Control Date Sent from LAB-29
The following example shows a message when QC data is sent from the
MEK-9100 to the AM.
PID||||||||UCR
SPM|1|^MEK5D505LMEK5D505L|||||||||Q^Control specimen^HL70369CR
SAC|||MEK5D505LCR
OBR|1|||QC|||||||||||||||||||||FCR
ORC|SC||||CMCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
OBX|3|NM|HGB^Hemoglobin^99UNK||6.24|g/dL^gram per deciliterÛCUM|0.00 - 0.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|5|NM|MCV^Mean Corpuscular Volume^99UNK||87.7|fL^femtoliterÛCUM|0.0 - 0.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
0.0||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|8|NM|RDW-CV^Red Blood Cell Distribution Width in CV^99UNK||17.4|%^percentÛCUM|0.0 - 0.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
OBX|9|NM|RDW-SD^Red Blood Cell Distribution Width in SD^99UNK||79.4|fL^femtoliterÛCUM|0.0 - 0.0||||F|||||||MEK-
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
OBX|11|NM|PCT^Plateletcrit^99UNK||0.03|%^percentÛCUM|0.00 - 0.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|13|NM|PDW^Platelet Distribution Width^99UNK||17.3|%^percentÛCUM|0.0 - 0.0||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|14|NM|P-LCR^Platelet Large Cell Ratio^99UNK||29.4|%^percentÛCUM|0.0 - 0.0||||F|||||||MEK-9100~00001|||||||||||RSLTCR
OBX|17|NM|MO%^Monocyte Percent^99UNK||14.59|%^percentÛCUM|0.00 - 0.00||||F|||||||MEK-9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR
9100~00001|||||||||||RSLTCR

Serial Number
Model
Your Representative
Contact information is accurate as of Jan 2015. Visit www.nihonkohden.com for the latest information.
The model and serial number of your instrument are identified on the rear or bottom of the unit.
Write the model and serial number in the spaces provided below. Whenever you call your representative concerning
this instrument, mention these two pieces of information for quick and accurate service.
Manufacturer
NIHON KOHDEN CORPORATION
1-31-4 Nishiochiai, Shinjuku-ku Tokyo 161-8560, Japan
Phone +81 3-5996-8036
Fax +81 3-5996-8100
North and South America
NIHON KOHDEN AMERICA, INC.
15353 Barranca Parkway, Irvine, CA 92618, U.S.A.
Toll-free +1-800-325-0283
Phone +1 949-580-1555
Fax +1 949-580-1550
NIHON KOHDEN LATIN AMERICA S.A.S
Carrera 16 No.93A-36 Of. 802. Bogota D.C., Colombia
Phone +57 1-300-1742
Fax +57 1-300-1825
NIHON KOHDEN DO BRASIL LTDA.
Rua Gomes de Carvalho
1507-Bloco A 9 andar-cjto 91A Vila Olimpia
CEP 04547-005 Sao Paulo-SP. Brasil
Phone +55 11-3841-9943
Fax +55 11-3044-0463
Europe
European Representative
NIHON KOHDEN EUROPE GmbH
Raiffeisenstrasse 10, D-61191 Rosbach, Germany
Phone +49 6003-827-0
Fax +49 6003-827-599
NIHON KOHDEN FRANCE SARL
8, rue Francois Delage, 94 230 Cachan, France
Phone +33 1-49-08-05-50
Fax +33 1-49-08-93-32
NIHON KOHDEN IBERICA S.L.
C/Ulises 75A, E-28043 Madrid, Spain
Phone +34 91-7-161080
Fax +34 91-3-004676
NIHON KOHDEN ITALIA S.r.l.
Via Fratelli Bronzetti 28, 24124 Bergamo, Italy
Phone +39 035-219543
Fax +39 035-232546
NIHON KOHDEN UK LTD
Trident Court 118, 1 Oakcroft Road
Chessington, Surrey KT9 1BD, UK
Phone +44 20-8391-6800
Fax +44 20-8391-6809
Asia
SHANGHAI KOHDEN
MEDICAL ELECTRONIC INSTRUMENT CORP.
567 Huancheng Bei Road
Shanghai Comprehensive Industrial Development Zone
Shanghai 201401, China
Phone +86 21-5743-6998
Fax +86 21-5743-6939
NIHON KOHDEN SINGAPORE PTE LTD
1 Maritime Square, #10-34 HarbourFront Centre
Singapore 099253
Phone +65 6376-2210
Fax +65 6376-2264
NIHON KOHDEN INDIA PVT. LTD.
308, Tower A, Spazedge, Sector 47, Sohna Road
Gurgaon-122 002 Haryana, India
Toll-free +91 1800-103-8182
Phone +91 124-493-1000
Fax +91 124-493-1029
NIHON KOHDEN MIDDLE EAST FZE
P.O.Box 261516, JAFZA View 19
Room 308 Jebel Ali Free Zone, Dubai, U.A.E
Phone +971 4-884-0080
Fax +971 4-880-0122
NIHON KOHDEN KOREA, INC.
5F Miso Bldg.
890-47 Daechi-dong, Gangnam-gu, Seoul, 135-280 Korea
Phone +82 2-3273-2310
Fax +82 2-3273-2352
MEK-9100_0614-907509

Manual HL-7-Data-Commnication-Protocol.pdf

More Related Content

Similar to Manual HL-7-Data-Commnication-Protocol.pdf (20)

Recently uploaded (20)

Manual HL-7-Data-Commnication-Protocol.pdf