Man0614-905894C CNS6201 PS

PROTOCOL SPECIFICATIONS
Central Monitor
CNS-6201
Bedside Monitor
BSM-3000 series
BSM-6000 series
PVM-2701/PVM-2703
First Edition: 12 Mar 2012

Fourth Edition: 15 Mar 2016
0614-905894C
Printed: 2020/08/06
Protocol Specifications
Central Monitor
CNS-6201
Bedside Monitor
BSM-3000 series
BSM-6000 series
PVM-2701/PVM-2703
If you have any comments or suggestions

on this manual, please contact us at:
www.nihonkohden.com 0614-905894C
The contents of this manual are subject to change without notice.
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.
DANGER A danger alerts the user to a hazardous situation
which causes death or serious injury.
WARNING A warning alerts the user to the possible injury or

death associated with the use or misuse of the
instrument.
CAUTION A caution alerts the user to possible injury or

problems with the instrument associated with its
use or misuse such as instrument malfunction,
instrument failure, damage to the instrument, or
damage to other property.
WARNING WARNING
When several medical instruments are used When using the HL7 output data in a central
together, ground all instruments to the same monitor or bedside monitor, connect only the
one-point ground. Any potential difference between specified instrument to the central monitor or
instruments may cause electrical shock to the bedside monitor and follow the specified procedure.
patient and operator. Otherwise, the patient or operator may receive
electrical shock.
WARNING
Do not use the HL7 output data as monitoring data
for diagnosis. For monitoring a patient, use
monitoring equipment such as a bedside monitor.
Nihon Kohden is not responsible for use and
application of output data.
CAUTION CAUTION
Before connecting or disconnecting instruments, Do not pull the cables with too much force and
make sure that each instrument is turned off and keep the cables out of the way. Otherwise, people
the power cord is disconnected from the AC socket. may trip over them, the personal computer, central
Otherwise, it may cause electrical shock to the monitor or bedside monitor may fall and injure the
patient or operator, or it may cause data loss, patient or operator, and monitoring may be affected.
malfunction or instrument failure.
CAUTION CAUTION
There are two or more network ports on the central Be careful to avoid computer viruses when
monitor. Connect the instrument to the port connecting instruments to the HL7 output port on
specified for HL7 output. Also, do not connect any the central monitor or bedside monitor.
unspecified instrument to other ports. Nihon
Kohden is not responsible for any damage on the
central monitor which is caused by incorrect
connection.
CAUTION CAUTION
Using the same IP address on multiple instruments Nihon Kohden is not responsible for the following:
or making a loop connection on the network hub • Installation and management problems of an
may cause serious damage to the connected instrument or connector connected to the HL7
instruments. Network management must only be output port on the central monitor or bedside
done by qualified service personnel or a person monitor
with technical knowledge.
• Problems on the central monitor or bedside
monitor caused by the connected instruments or
connector
CAUTION CAUTION
The central monitor and bedside monitor are For customer convenience, Nihon Kohden provides
medical instruments and strict standards are information for outputting HL7 data as needed.
applied.
However, Nihon Kohden is not responsible for any
However, there is a possibility that connecting the use of output HL7 data directly involved with the
central monitor or bedside monitor to a personal patient life such as alarms or feedback system.
computer causes leakage current to flow to the
Also, be careful about effect from ECG artifact or
patient or operator and leads to a dangerous
data loss caused by noise from data transfer.
situation. It could be a legal matter if the HIS
supplier does not provide sufficient information or
training to the customer in regard to the above
issues.
Take necessary measures such as isolation by a

light isolator or isolation transformer, and provide
sufficient training to the customer or medical staff.
CAUTION CAUTION
The specifications in this Protocol Specification are This document contains confidential technical
correct as of March 2016. If the central monitor or information which is intended only for use of
bedside monitor software is updated, the authorized customers, and may not be shared with
specifications, especially messages, may change. any other third party. If you need to share this
information with a third party, contact Nihon
Kohden.
Contents
1. Overview
1.1. Behavior
1.2. Interfaces
2. Communication Protocol
2.1. Communication Acceptance
3. Data Structure
4. Data Items
5. Description of Abbreviations
6. Message Delimiters
7. HL7 Messages and Segments
7.1. Message List
7.2. Patient Information Query (Event A19)
7.2.1. Query of Patient Information: QRYÂ19
7.2.2. Patient Basic Information Response Message: ADT Response (ADRÂ19)
7.3. Unsolicited Transmission of Vital Data (Event R01)
7.3.1. Unsolicited Transmission of an Observation Message: ORU^R01
7.3.2. Observation Unsolicited Transmission Response Message: ACK^R01
7.4. Query for Results of Observation (Events R02, R04)
7.4.1. Vital Information Query Message: QRY^R02
7.4.2. Observation Result Query - Response Message: ORF^R04
8. Error Condition Table
8.1. HL7Table0357 – Message Error Condition Codes
Protocol Specification HL7 Gateway Server 1

1. Overview
This document describes the HL7 version 2.4-based interface specifications for the HL7 gateway
server protocol.
Responsibility
Nihon Kohden Corporation is not responsible for any damage or harm caused by use of this product.
Nihon Kohden Corporation is not responsible for any damage or harm caused by use of data from
the HL7GW and the bedside monitor.
The user is responsible for any use of data from the HL7GW and the bedside monitor.
1.1. Behavior
The HL7 Gateway Server Program
The data output from HL7GW to an external system can not be used for the diagnosis.
The HL7 gateway server assumes cooperation with an external system (such as HIS) and
handles monitor information for the monitors that have been preconfigured to be connected.
Based on a patient ID entered from a monitor, the external system is queried about patient
information through the HL7 protocol and the information is returned to that monitor.1
The information retrieved from the monitors is sent to the external system actively on a regular
basis or as required by the system.
The information to send is the information retrieved from the monitors, including observation
information, and patient attribute information (retrieved from the external system).2
When Patient ID overlaps on the monitor system side, the output data from HL7 gateway
becomes irregular.
Continuous data output might fail because of a high load or temporary error in the network or
HL7 gateway server.
The bedside monitor

The data output from the bedside monitor to an external system can not be used for the
diagnosis.
The bedside monitor assumes cooperation with an external system (such as HIS) and handles
1
Be sure to confirm that there is nothing wrong with the patient information displayed on the monitor when a
patient ID is entered.
2
Information is not output in real time.
* The interface might be influenced by factors on the external system (such as HIS) side, including the setting
change, environmental change, and specification change.
* Any error occurring in the linkage including the network between the monitor and the HL7 gateway must be
recognizable by the external system as well.
*Supported parameters are different by the product. Please check the Appendix A for more information.
2 Protocol Specification HL7 Gateway Server

information that is monitored by the bedside monitor.
Based on a patient ID entered from the bedside monitor, the external system is queried about
patient information through the HL7 protocol and the information is returned to the bedside
monitor.1
The information retrieved from the bedside monitor is sent to the external system actively on a
regular basis or as required by the system.
The information to send is the information retrieved from the bedside monitor, including
observation information, and patient attribute information (retrieved from the external
system).2
When Patient ID overlaps on the monitor system side, the output data from HL7 gateway
becomes irregular.
Continuous data output might fail because of a high load or temporary error in the network or
the bedside monitor.

1.2. Interfaces
The HL7 gateway server program provides the following information exchanges by the single-
session.
1) Query and response of patient information

When a patient ID is entered by the bedside monitor, the HL7 gateway requests the patient attribute
information from the external system, and registers the patient attribute information received from
the external system in that monitor.
This function uses QRY/ADR of HL7 (Event A19).
External system < [ QRYÂ19 ] < HL7 GW (Central Monitor) < Bedside
monitor
External system > [ ADRÂ19 ] > HL7 GW (Central Monitor) > Bedside
monitor
(1)
Input a Patient-ID
(3)
(2)
Query Send a Patient-ID
other system HL7GW
Patient Information
(HIS etc.)
(Central BED SIDE
Monitoer
Monitor)
(4) (5)
Answer Send
Patient Information Patient Information
(Name Birthday Sex
Height Weight Blood-Type)
Any query is limited to a query and response for only one patient at a time.

2) Unsolicited transmission of observation values
By using the Session Open from the external system as a trigger, the HL7 gateway automatically
sends the recent observation information received from the bedside monitor to the external system
at the preset interval.
This function uses ORU/ACK of HL7 (Event R01).
External system < [ ORU^R01 ] < HL7 GW (Central Monitor) < Monitor
External system > [ ACK^R01 ] > HL7 GW (Central Monitor)
(2)
Send
numerical data
at a constant frequency (1)
Send
HL7GW numerical data
other system
other system HL7GW
(Central Monitor)
ＨＩＳetc.).）
（(HIS Cyclic Monitor
Monitor
Monitor
Monitor
BED SIDE
(3) BED SIDE
Monitor
Monitor
ACK
This function returns the recent value received by the HL7 gateway from the monitor, but the value is not
real-time information.

3) Query and response of observation values
When the external system makes a query, with a patient ID and period specified, to find previous
observation information, the HL7 gateway ( the central monitor ) sends the observation value to the
external system at the preset sampling.
The function uses QRY/ORF of HL7 (Events R02 and R04).
External system > [ QRY^R02 ] > HL7 GW (Central Monitor)

External system < [ ORF^R04 ] < HL7 GW (Central Monitor)
(1) Query a patient

numerical data
of the past
other system
other system HL7GW
HL7GW
.）
(HIS etc.)
（ＨＩＳ (Central Monitor)
(2) Answer a patient

numerical data
The width of a single request with the period specified is 10 samplings or less. A one-minute interval
provides 10 minutes or less.
This function returns the numerical observation data corresponding to a specified patient ID and it is
stored by the central monitor. The data storage period depends on the central monitor.
An excessive request will cause an overload in the central monitor, network, or HL7 gateway, probably
leading to a problem such as an instable monitoring system or data output discontinuation. The problem
must be solved by the client (external system) side.

The bedside monitor provides the following information exchanges by the single-session.
1) Query and response of patient information

When a patient ID is entered by the bedside monitor, it requests the patient attribute information
from the external system, and registers the patient attribute information received from the external
system into itself.
This function uses QRY/ADR of HL7 (Event A19).
External system < [ QRYÂ19 ] < Bedside monitor

External system > [ ADRÂ19 ] > Bedside monitor
(1)
Input a Patient-ID
(2)
Query
other system Bedside Monitor
Patient Information
(HIS etc.)
(3)
Answer
Patient Information
(Name Birthday Sex
Height Weight Blood-Type)
Any query is limited to a query and response for only one patient at a time.

2) Unsolicited transmission of observation values
By using the Session Open from the external system as a trigger, the bedside monitor automatically
sends the recent observation information to the external system at the preset interval.
This function uses ORU/ACK of HL7 (Event R01).
External system < [ ORU^R01 ] < Bedside monitor

External system > [ ACK^R01 ] > Bedside monitor
(1)
Send
numerical data
at a constant frequency
Bedside Monitor
other system
other system HL7GW
ＨＩＳetc.).）
（(HIS Cyclic
(2)
ACK
This function returns the recent value monitored by the bedside monitor, but the value is not real-time
information.

3) Query and response of observation values
When the external system makes a query, with a patient ID and period specified, to find previous
observation information, the bedside monitor sends the observation value to the external system at
the preset sampling.
The function uses QRY/ORF of HL7 (Events R02 and R04).
External system > [ QRY^R02 ] > Bedside monitor

External system < [ ORF^R04 ] < Bedside Monitor
(1) Query a patient

numerical data
of the past
other system
other system Bedside
HL7GWMonitor
.）
(HIS etc.)
（ＨＩＳ
(2) Answer a patient

numerical data
The width of a single request with the period specified is 10 samplings or less. A one-minute interval
provides 10 minutes or less.
This function returns the numerical observation data corresponding to a specified patient ID and it is
stored by the bedside monitor. The data storage period depends on the bedside monitor.
An excessive request will cause an overload in the bedside monitor or network, probably leading to a
problem such as an instable monitoring system or data output discontinuation. The problem must be
solved by the client (external system) side.

2. Communication Protocol
2.1. Communication Acceptance
TCP/IP socket connections
Query and response of patient information The HL7 gateway and the
bedside monitor acts as a
client.
Unsolicited transmission of observation values The HL7 gateway and the
server.
Query and response of observation values The HL7 gateway and the
server.
Port numbers are required individually for the above table.

A client establishes a communication (socket open).
It is assumed that any open socket will be closed the moment when a single request has
been completed, unless an event such as a failure or restart occurs. If a connection is
refused, the client application must make connection attempts until the connection is
accepted.
Any failure between the monitor system and the HL7 gateway must be displayed as an
alert on the HIS side.
Any failure of the bedside monitor must be displayed on the HIS side as an alert.
Once communication is established between the two systems, message exchanges start. The
sending system initiates message transmission. After transmitting a message, the sending
application must wait for an HL7 message-type response before transmitting the next message.
If the sending application does not receive an HL7 message-type response within a specified time,
it retransmits the message.
In-hospital network HL7 gateway (Central Monitor) LS-Net
External system HL7 Gateway (Central Monitor)

Query and response of patient information
Unsolicited transmission of observation values Bedside

monitor
Query and response of observation values

In-hospital network Bedside Monitor
External system Bedside Monitor

Query and response of patient information
Unsolicited transmission of observation values
Query and response of observation values

3. Data Structure
Every HL7 message ends with <EOM> (End of message).
4. Data Items
Patient information (information sent to a monitor)
Patient name: PID-5

Patient ID (internal ID): PID-3
Birth date: PID-7
Sex: PID-8
Diagnosis: DG1-4 *1)
Height: OBX-2,3,5,6
Weight: OBX-2,3,5,6
Blood type: OBX-2,3,5,6
The following two items are automatically generated from the above information.
Age: Calculated from the birth date.
Body surface area (BSA): Calculated from the height and weight.
*1) It is unsuitable to use DG1-4 information as a doctor name.
Vital sign data (information sent to the other system)
HR, Resp, Temp, BP (SYS, DIAS, MEAN), SpO2, NIBP (SYS, DIAS, MEAN), etc.
The data indicates instantaneous values.

The transmission interval is a time interval set in the HL7 gateway or the bedside monitor.
Up to 255 items of vital sign data are sent from a single bedside monitor.
For irregular data such as NIBP, the value measured within the transmission interval is sent.
An excessive request will cause an overload in the central monitor, the bedside monitor,
network, or HL7 gateway, probably leading to a problem such as an instable monitoring
system or data output discontinuation. The problem must be solved by the client (external
system) side.

5. Description of Abbreviations
Abbreviations used in each message or segment table are described below. (common to
all tables)
SEQ: Ordinal position of the data field within the segment. This number is used to refer to the data
field in the text comments that follow the segment definition table.
LEN: Maximum number of characters that one occurrence of the data field may occupy.
DT: Restrictions on the contents of the data field.
OPT: Whether the field is required, optional, or conditional in a segment.
R - required
O - optional
C - conditional on the trigger event or on some other field(s). The field
definitions following the segment attribute table should specify the algorithm
that defines the conditionality for this field.
X - not used with this trigger event
B - left in for backward compatibility with previous versions of HL7. The field
definitions following the segment attribute table should denote the optionality
of the field for prior versions.
HL7 G/W: A setup by this specification (this item defines the existence of segments in this system,
or element setup)
R - required
O - optional
N - Usually not used (it is used only in Institution).
PVM: A setup by this specification (this item defines the existence of segments in this system, or
element setup) Bedside monitor
PVM-2700 Series.
R - required
O - optional
N - Usually not used (it is used only in Institution).

BSM: A setup by this specification (this item defines the existence of segment in this system, or an
element setup) Bedside monitor
BSM-6000 Series. / BSM-3000 Series.
R - required
O - optional
N - Usually, it is not used (it is used only in institution).
RP/#: Whether the field may repeat.

N or blank - no repetition
Y - the field may repeat an indefinite or site-determined number of
times
(integer) - the field may repeat up to the number of times specified by the
integer
Remarks: Fixed value is described in this column.

6. Message Delimiters
In constructing a message, certain special characters are used. They are the segment terminator, the
field separator, the component separator, subcomponent separator, repetition separator, and escape
character. The segment terminator is always a carriage return (in ASCII, a hex 0D). The other
delimiters are defined in the MSH segment, with the field delimiter in the 4th character position,
and the other delimiters occurring as in the field called Encoding Characters, which is the first field
after the segment ID. The delimiter values used in the MSH segment are the delimiter values used
throughout the entire message. In the absence of other considerations, HL7 recommends the
suggested values found in Figure 2-1. Delimiter values.
At any given site, the subset of the possible delimiters may be limited by negotiations between
applications. This implies that the receiving applications will use the agreed upon delimiters, as
they appear in the Message Header segment (MSH), to parse the message.
Encoding Character
Delimiter Suggested Value Usage
Position
Terminates a segment record. This value cannot
Segment Terminator <cr> (hex 0D) - be changed by implementers.
Separates two adjacent data fields within a
Field Separator | - segment. It also separates the segment ID from
the first data field in each segment.
Separates adjacent components of data fields
Component Separator ^ 1 where allowed.
Separates adjacent subcomponents of data fields
Subcomponent Separator & 4 where allowed. If there are no subcomponents,
this character may be omitted.
Separates multiple occurrences of a field where
Repetition Separator ~ 2 allowed.
Escape character for use with any field
represented by an ST, TX or FT data type, or
for use with the data (fourth) component of the
Escape Character \ 3 ED data type. If no escape characters are used
in a message, this character may be omitted.
However, it must be present if subcomponents
are used in the message.
Delimiter values
In the standard HL7 message protocol, these are no definition about the message start code. In this
system, we define the message start code as hex 0x0b in ASCII.
In the standard HL7 message protocol, these are no definition about the message terminator. In this
system, we define the message terminator as hex 0x1c 0x0d in ASCII.

7. HL7 Messages and Segments
7.1. Message List
HL7 Section
No. Function Message
MSG EVT Sending Receiving
Query and
HL7 Gateway
response of patient
Information Query, original mode QRY / Bedside Other system
monitor
1 A19 HL7
Gateway /
ADT response ADR Other system
Bedside
monitor
Unsolicited HL7 Gateway
transmission of Unsolicited transmission of
observation values ORU / Bedside Other system
an observation message
monitor
2 R01 HL7
General acknowledgement Gateway /

ACK Other system
message Bedside
monitor
Query and HL7
response of
observation values Gateway /
Query, original mode QRY R02 Other system
Bedside
3 monitor
HL7 Gateway
Vital numerical value
information response ORF R04 / Bedside Other system
message
monitor
Table 1. Message list

7.2. Patient Information Query (Event A19)
7.2.1. Query of Patient Information: QRYÂ19
A patient basic information query message consists of the following segments.
HL7 G/W / PVM

No. Segment Segment Remarks
/ BSM
1 MSH Message Header R
2 QRD Query Definition R
3 (QRF) Query Filter N
Table 2. Query, original mode message (QRYÂ19)
Braces {...} indicate one or more repetitions of the enclosed group of segments.
Brackets [...] indicate that the enclosed group of segments is optional.
If a group of segments is optional and may repeat it should be enclosed in brackets and braces
{[...]}.

7.2.1.1. Patient Basic Information Query Message: MSH Segment
The MSH segment in a patient basic information query message consists of the following
elements.
HL7
G/W /
OP
SEQ LEN DT RP/# Element Remarks
T PVM /
BSM
1 1 ST R R - Field Separator ｜
2 4 ST R R - Encoding Characters ^~\&
3 180 HD O O - Sending Application
4 180 HD O O - Sending Facility
5 180 HD O O - Receiving Application
6 180 HD O O - Receiving Facility
7 26 TS O O - Date/Time of Message
8 40 ST O N - Security
Message Type QRYÂ19^QRY
9 13 CM R R -
_A19
10 20 ST R R - Message Control ID
11 3 PT R R - Processing ID P
12 60 VID R R - Version ID 2.4
13 15 NM O N - Sequence Number
14 180 ST O N - Continuation Pointer
N Accept Acknowledgement Type
15 2 ID O -
R
16 2 ID O R - Application Acknowledgement Type
17 3 ID O O - Country Code
18 16 ID O O Y Character Set
19 250 CE O N - Principal Language of Message
Alternate Character Set Handling
20 20 ID O O -
Scheme
21 10 ID O N Y Conformance Statement ID
Table 3. Patient basic information query message: MSH Segment
The field definition of an indispensable setup in MSH segment and an arbitrary setup is shown
below.
MSH-1. Field Separator

Value Description
| (fixed) Separator between the fields

MSH-2. Encoding Characters
Value Description
^~\& (fixed) Component separator, repetitive separator, an escape
character, subcomponent separator
MSH-3. Sending Application

Value Description
<Sending Application> (example) HL7 Gateway
*In the case of the CNS, set in the System Setup
screen. In the case of the PVM / BSM, set in the
SYSTEM CONFIGURATION screen.
MSH-4. Sending Facility

Value Description
<Institution>^<Section> (example) Nihon Kohden
MSH-5. Receiving Application

Value Description
<Receiving Application> (example) HL7 Client
MSH-6. Receiving Facility

Value Description
<Institution>^<Section> (example) Receiving Facility
MSH-7. Date/Time of Message

Value Description
YYYYMMDDHHMMSS Year/month/day/hour/minute/second
(example) 20070401171823
(Usually this field is not used)

MSH-9. Message Type
Value Description
QRYÂ19^QRY_A19 (fixed) <Message Type>^<Event Type>
Message Type: Reference of HL7Table0076
Event Type: Reference of HL7Table0003
MSH-10. Message Control ID

Value Description
YYYYMMDDNNNNNN Year/Month/Day/Sequence Number
(example) 20070401123456
MSH-11. Processing ID
Value Description
P (fixed) Production: Reference of HL7Table0103
MSH-12. Version ID
Value Description
2.4 (fixed) HL7 protocol version 2.4
MSH-15. Accept Acknowledgment

Value Description
NE (fixed) “necessary”
The PCD TF requires that this field be valued as NE.
MSH-16. Application Acknowledgment

Value Description
AL (fixed) “always”
The PCD TF requires that this field be valued as AL.
MSH-18. Character Set

Value Description
ASCII
MSH-20. Alternate Character Set Handling Scheme

Value Description
ASCII

7.2.1.2. Patient Basic Information Query Message: QRD Segment
The QRD segment in a patient basic information query message consists of the following
elements.
HL7
G/W /
SEQ LEN DT OPT RP/# Element Remarks
PVM /
BSM
1 26 TS R R - Query Date / Time
2 1 ID R R - Query Format Code R
3 1 ID R R - Query Priority I
4 10 ST R R - Query ID
5 1 ID O N - Deferred Response Type
6 26 TS O N - Deferred Response Date/Time
7 10 CQ R R - Quantity Limited Request RD^1
8 250 XCN R R Y Who Subject Filter
9 250 CE R R Y What Subject Filter
10 250 CE R R Y What Department Data Code
11 20 ST O N Y What Data Code Value Qual
12 1 ID O N - Query Results Level
Table 4. Patient basic information query message: QRD Segment
The field definition of an indispensable setup in QRD segment and an arbitrary setup is shown
below.
QRD-1. Query Date/Time

Value Description
(example) 20010131171823
QRD-2. Query Format Code

Value Description
R (fixed) Response is in record-oriented format:
Reference of HL7Table0106
QRD-3. Query Priority

Value Description
I (fixed) Immediate: Reference of HL7Table0091

QRD-4. Query ID
Value Description
MMDDNNNNNN month/day/Sequence Number
(example) 0131123456
QRD-7. Quantity Limited Request

Value Description
RD^1 (fixed) Records: Reference of HL7Table0126
QRD-8. Who Subject Filter

Value Description
<Patient ID number (ST)>^<family name
A candidate patient is set up.
(ST)>^<given name (ST)>
^<middle initial or name (ST)>
Only <Patient ID Number> is used.
^<suffix (e.g., JR or III) (ST)>
^<prefix (e.g., DR) (ST)>
^<degree (e.g., MD) (IS)>
^<source table (IS)>
^<assigning authority (HD)>
^<name type code (ID)>
^<code identifying the check digit scheme
employed (ID)>
^<identifier type code (IS)>
^<assigning facility (HD)>
QRD-9. What Subject Filter

Value Description
Patient name lookup
APN (fixed)
QRD-10. What Department Data Code

Value Description
<identifier (ID)>^<text (ST)> (Usually this field is not used)
^<name of coding system (ST)>
^<alternate identifier (ID)>
^<alternate text (ST)>
^<name of alternate coding system (ST)>

7.2.2. Patient Basic Information Response Message: ADT Response (ADRÂ19)
A patient basic information response message consists of the following segments.
NO. Segment Segment Name HL7 G/W / PVM / Remarks

BSM
1 MSH Message header R
2 MSA Message Acknowledgment R
3 [ERR] Error N
4 [QAK] Query Acknowledgment N
6 [QRF] Query Filter N
{
7 [EVN] Event Type N
8 PID Patient Identification R
9 [PD1] Additional Demographics N
10 [{ROL}] Role N
11 [{NK1}] Next of Kin/Associated Parties N
－
12 PV1 Patient Visit R
13 [PV2] Patient Visit Additional Info N
14 [{ROL}] Disability Information N
15 [{DB1}] Observation/Result N
16 [{OBX}] Allergy Information O
17 [{AL1}] Diagnosis Information N
18 [{DG1}] Diagnosis Related Group O
19 [DRG] Next of Kin/Associated Parties N
[{
20 PR1 Procedures N
21 [{ROL}] Role N
}]
22 [{GT1}] Guarantor N
[{
23 IN1 Insurance N
24 [IN2] －
Insurance Additional Info N
25 [{IN3}] Insurance Additional Info – Cert N
26 [{ROL}] Role N
}]
27 [ACC] Accident Information N
28 [UB1] Universal Bill Information N
29 [UB2] Universal Bill 2 Information N
}
30 [DSC] Continuation Pointer N
Table 5. Patient basic information response message (ADR)

If a group of segments is optional and may repeat it should be enclosed in brackets and
braces {[...]}.

7.2.2.1. Patient Basic Information Response Message: MSH Segment
The MSH segment in a patient basic information response message consists of the following
elements.
SEQ LEN DT OPT HL7 RP/#

G/W /
Element Remarks
PVM /
BSM
1 1 ST R R - Field Separator |
R R - Message Type ADRÂ19ÂDR_
9 13 CM
A19
15 2 ID O N - Accept Acknowledgement Type
16 2 ID O N - Application Acknowledgement Type
17 3 ID O N - Country Code
18 16 ID O O Y Character Set
O O - Alternate Character Set Handling
20 20 ID
Scheme
Table 6. Patient basic information response message: MSH Segment
below.

Value Description

Value Description

Value Description
<Sending Application> (example) HL7 Client

Value Description

Value Description
<Receiving Application> (example) HL7 Gateway

Value Description

Value Description
(example) 20010131171823
MSH-9. Message Type

Value Description
ADRÂ19ÂDR_A19 (fixed) <Message Type>^<Event Type>
Message Type: Reference of HL7Table0076

Value Description
<Message Control ID> ID of a partner system rule
Set QRYÂ19 MSH-10 Message Control ID.
Value Description
MSH-12. Version ID
Value Description

Value Description

Value Description

Value Description
ASCII

Value Description
ASCII

7.2.2.2. Patient Basic Information Response Message: MSA Segment
The MSA segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 2 ID R R - Acknowledgment Code
3 80 ST O N - Text Message
4 15 NM O N - Expected Sequence Number
5 1 ID B N - Delayed Acknowledgment Type
6 250 CE O O - Error Condition
Table 7. Patient basic information response message: MSA Segment
The field definition of an indispensable setup in MSA segment and an arbitrary setup is shown
below.
MSA-1. Acknowledgment Code

Value Description
<Acknowledgment Code> Reference of HL7Table0008
MSA-2. Message Control ID

Value Description
<Message Control ID> Set QRYÂ19 MSH-10 Message Control ID.
MSA-6. Error Condition

Value Description
<identifier (ST)>^<text (ST)> This field allows the acknowledging system to
^<name of coding system (IS)> use a user-defined error code to further specify
^<alternate identifier (ST)> AR or AE type acknowledgments.
^<alternate text (ST)> (Usually this field is not used)
^<name of alternate coding system (IS)>

7.2.2.3. Patient Basic Information Response Message: QRD Segment
The QRD segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 26 TS R R - Query Date/Time
Table 8. Patient basic information response message: QRD Segment
below.

Value Description
(example) 20010131171823

Value Description
R (fixed)
Response is in record-oriented format

Value Description

QRD-4. Query ID
Value Description

Value Description

Value Description
<Patient ID number (ST)>^<family name A candidate patient is set up.
(ST)>^<given name (ST)>
Only <Patient ID number> is used.
^<name type code(ID)>
employed (ID)>

Value Description
Patient name lookup: Reference of
APN (fixed) HL7Table0048

Value Description
<identifier (ID)>^<text (ST)> (Usually this field is not used)
^<name of coding system (ST)>
^<alternate identifier (ID)>
^<alternate text (ST)>
^<name of alternate coding system (ST)>

7.2.2.4. Patient Basic Information Response Message: PID Segment
The PID segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI O N - Set ID - PID
2 20 CX B N - Patient ID
2 250 CX R R Y Patient Identifier List
4 20 ST O N Y Alternate Patient ID - PID
5 250 XPN R R Y Patient Name
6 250 XPN O N - Mother’s Maiden Name
7 26 TS O R - Date/Time of Birth
8 1 IS O R - Administrative Sex
9 250 XPN B N Y Patient Alias
10 250 CE O N - Race
11 250 XAD O N Y Patient Address
12 4 IS O N - County Code
13 250 XTN O N Y Phone Number - Home
14 250 XTN O N Y Phone Number - Business
15 250 CE O N - Primary Language
16 250 CE O N - Marital Status
17 250 CE O N - Religion
18 250 CX O N - Patient Account Number
19 16 ST B N - SSN Number - Patient
20 25 DLN O N - Driver's License Number - Patient
21 250 CX O N - Mother's Identifier
22 250 CE O N - Ethnic Group
23 250 ST O N - Birth Place
24 1 ID O N - Multiple Birth Indicator
25 2 NM O N - Birth Order
26 250 CE O N - Citizenship
27 250 CE O N - Veterans Military Status
28 250 CE O N - Nationality
29 26 TS O N - Patient Death Date and Time
30 1 ID O N - Patient Death Indicator
31 1 ID O N - Identity Unknown Indicator
32 20 IS O N Y Identity Reliability Code
33 26 TS O N - Last Update Date/Time
34 40 HD O N - Last Update Facility
35 250 CE C N - Species Code
36 250 CE C N - Breed Code
37 80 ST O N - Strain
38 250 CE O N - Production Class Code
Table 9. Patient basic information response message: PID Segment

The field definition of an indispensable setup in PID segment and an arbitrary setup is shown below.
PID-3. Patient ID (Internal ID)

Value Description
<Patient ID>
PID-5. Patient Name

Value Description
<family name (ST)> Name type code: Reference of HL7Table0200
^<given name (ST)> Name representation code: Reference of HL7Table0465
(example)
Kohden^Tarou^^^^^LÂ
^<name representation code (ID)>
PID-7. Date/Time of Birth

Value Description
Year/month/day/hour/minute/second
YYYYMMDD(HHMM(SS))
(example) 20010131171823
PID-8. Sex
Value Description
<Sex> Reference of HL7Table0001
F Female
M Male
O Other
U Unknown

7.2.2.5. Patient Basic Information Response Message: PV1 Segment
The PV1 segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI O N - Set ID - PV1
2 1 IS R R - Patient Class
3 80 PL O N - Assigned Patient Location
4 2 IS O N - Admission Type
5 250 CX O N - Preadmit Number
6 80 PL O N - Prior Patient Location
7 250 XCN O N Y Attending Doctor
8 250 XCN O N Y Referring Doctor
9 250 XCN B N Y Consulting Doctor
10 3 IS O N - Hospital Service
11 80 PL O N - Temporary Location
12 2 IS O N - Preadmit Test Indicator
13 2 IS O N - Re-admission Indicator
14 6 IS O N - Admit Source
15 2 IS O N Y Ambulatory Status
16 2 IS O N - VIP Indicator
17 250 XCN O N Y Admitting Doctor
18 2 IS O N - Patient Type
19 250 CN O N - Visit Number
20 50 FC O N Y Financial Class
21 2 IS O N - Charge Price Indicator
22 2 IS O N - Courtesy Code
23 2 IS O N - Credit Rating
24 2 IS O N Y Contract Code
25 8 DT O N Y Contract Effective Date
26 12 NM O N Y Contract Amount
27 3 NM O N Y Contract Period
28 2 IS O N - Interest Code
29 1 IS O N - Transfer to Bad Debt Code
30 8 DT O N - Transfer to Bad Debt Date
31 10 IS O N - Bad Debt Agency Code
32 12 NM O N - Bad Debt Transfer Amount
33 12 NM O N - Bad Debt Recovery Amount
34 1 IS O N - Delete Account Indicator
35 8 DT O N - Delete Account Date
36 3 IS O N - Discharge Disposition
37 25 CM O N - Discharged to Location
38 250 CE O N - Diet Type

39 2 IS O N - Servicing Facility
40 1 ID B N - Bed Status
41 2 IS O N - Account Status
42 80 PL O N - Pending Location
43 80 PL O N - Prior Temporary Location
44 26 TS O N - Admit Date/Time
45 26 TS O N Y Discharge Date/Time
46 12 NM O N - Current Patient Balance
47 12 NM O N - Total Charges
48 12 NM O N - Total Adjustments
49 12 NM O N - Total Payments
50 250 CX O N - Alternate Visit ID
51 1 IS O N - Visit Indicator
52 250 XCN B N Y Other Healthcare Provider
Table 10. Patient basic information response message: PV1 segment
The field definition of an indispensable setup in PV1 segment and an arbitrary setup is shown
below.
PV1-2. Patient Class

Value Description
<Patient class> Records: Reference of HL7Table0126

7.2.2.6. Patient Basic Information Response Message: OBX Segment
Here, the receipt of height, weight, and a blood type is assumed.

The OBX segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI O O - Set ID - OBX
2 2 ID C R - Value Type
3 250 CE R R - Observation Identifier
4 20 ST C N - Observation Sub-ID
5 65536 * C R Y Observation Value
6 250 CE O O - Units
7 60 ST O N - References Range
8 5 IS O N Y/5 Abnormal Flags
9 5 NM O N - Probability
10 2 ID O N Y Nature of Abnormal Test
11 1 ID R R - Observation Result Status
12 26 TS O N - Date Last Observation Normal Value
13 20 ST O N - User Defined Access Checks
14 26 TS O N - Date/Time of the Observation
15 250 CE O N - Producer's ID
16 250 XCN O N - Responsible Observer
17 250 CE O N - Observation Method
18 22 EI O N Y Equipment Instance Identifier
19 26 TS O N - Date/Time of the Analysis
Table 11. Patient basic information response message: OBX segment
The field definition of an indispensable setup in OBX segment and an arbitrary setup is shown
below.
OBX-1. Set ID
Value Description
This field contains the sequence number.

OBX-2. Value Type
Value Description
Value type: Reference of HL7Table0125
NM Numeric
ST String Data
The rest is omitted.
OBX-3. Observation Identifier

Value Description
<identifier (ST)>^<text (ST)>^<name of coding Height, weight, blood type
system (IS)>^<alternate identifier The name should be given according to the NK
(ST)>^<alternate text (ST)>^<name of alternate
coding system (IS)> definition.
Height: 2522^Height
Weight: 2523^Weight
Blood type: 520^Blood
OBX-5. Observation Value

Value Description
The model specified by OBX-2 is followed.
The height and weight are expressed by numeric
values.
The blood type is indicated by the following: A+,
A-, B+, B-, O+, O-, AB+, and AB-.
OBX-6. Units
Value Description
The model specified by OBX-2 or OBX-5 is
followed.
Height and weight are in cm and kg.
OBX-11. Observation Result Status

Value Description
F Order detail description only (no result)

7.2.2.7. Patient Basic Information Response Message: DG1 Segment
The DG1 segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI R R - Set ID - DG1
2 2 ID (B)R N - Diagnosis Coding Method
3 250 CE O O - Diagnosis Code - DG1
4 40 ST B O - Diagnosis Description
5 26 TS O N - Diagnosis Date/Time
6 2 IS R N - Diagnosis Type
7 250 CE B N - Major Diagnostic Category
8 250 CE B N - Diagnostic Related Group
9 1 ID B N - DRG Approval Indicator
10 2 IS B N - DRG Grouper Review Code
11 250 CE B N - Outlier Type
12 3 NM B N - Outlier Days
13 12 CP B N - Outlier Cost
14 4 ST B N - Grouper Version And Type
15 2 ID O N Diagnosis Priority
16 250 XCN O O Y Diagnosing Clinician
17 3 IS O N - Diagnosis Classification
18 1 ID O N - Confidential Indicator
19 26 TS O N - Attestation Date/Time
Table 12. Patient basic information response message: DG1 segment
The field definition of an indispensable setup in DG1 segment and an arbitrary setup is shown
below.
DG1-1. Set ID
Value Description
It does not have any special purpose.

DG1-3. Diagnosis Code
Value Description
<identifier (ST)>^<text (ST)> DG1-3-diagnosis code contains the diagnosis code
^<name of coding system (IS)> assigned to this diagnosis. Refer to user-defined
^<alternate identifier (ST)> HL7Table0051 – Diagnosis code for suggested
^<alternate text (ST)> values.
^<name of alternate coding system (IS)> (Usually this field is not used)
DG1-4. Diagnosis Description

Value Description
Diagnosis description
(Usually, this field is not used)
This field has been retained for backward
compatibility only. Use the components of DG1-3 -
diagnosis code-DG1 field instead of this field.
DG1-16. Diagnosing Clinician

Value Description
<ID number (ST)>^<family name (Usually this field is not used)
(ST)>^<given name (ST)>^<middle initial or
name (ST)>^<suffix (e.g., JR or III)
(ST)>^<prefix (e. g., DR) (ST)>^<degree (e. g., It may be unsuitable although this field is used
MD) (IS)>^<source table (IS)>^<assigning when a doctor name is displayed by the monitor
authority (HD)>^<name type code(ID)>
^<identifier check digit (ST)>^<code side.
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)>

7.3. Unsolicited Transmission of Vital Data (Event R01)
7.3.1. Unsolicited Transmission of an Observation Message: ORU^R01
A vital numerical information distribution message consists of the following segments.
No. Segment Segment Name HL7 G/W / PVM / Remarks

BSM
1 MSH Message Header Segment R
{
[
2 PID Patient Identification Segment R
3 [PD1] Additional Demographics N
4 [{NK1}] Next of Kin/Associated Parties N
5 [{NTE}] Notes and Comments N
6 [PV1 Patient Visit R
7 [PV2] ] Patient Visit - Additional Info N
]
{
8 [ORC] Order common R
9 OBR Observations Report ID R
10 [{NTE}] Notes and comments N
11 [CTD] Contact Data N
{
12 [OBX] Observation/Result R
13 {[NTE]} Notes and comments N
}
14 {[FTI]} Financial Transaction N
15 {[CTI]} Clinical Trial Identification N
}
}
Table 13. Vital numerical information distribution message: ORU^R01
Braces {…} indicate one or more repetitions of the enclosed group of segments.
braces {[...]}.

7.3.1.1. Unsolicited Transmission of an Observation Message: MSH Segment
The MSH segment in an unsolicited transmission of an observation message consists of the

following elements.

G/W /
Element Remarks
PVM /
BSM
9 13 CM R R - Message Type ORU^R01ÔR
U_R01
12 60 VID R R - Version ID 2. 4
15 2 ID O R - Accept Acknowledgement Type
18 16 ID O O Y Character Set ASCII
20 20 ID O O - Alternate Character Set Handling Scheme ASCII
Table 14. Unsolicited transmission of an observation message: MSH segment
below.

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description
(example) 20070401171823
MSH-9. Message Type

Value Description
ORU^R01ÔRU_R01 (fixed) Message Type: Reference of HL7Table0076

Value Description
(example) 20070401123456
Value Description
MSH-12. Version ID
Value Description

Value Description

Value Description

Value Description
ASCII

Value Description
ASCII

7.3.1.2. Unsolicited Transmission of an Observation Message: PID Segment
The PID segment in an unsolicited transmission of an observation message consists of the

following elements.

G/W /
Element Remarks
PVM /
BSM
Table 15. Unsolicited Transmission of an Observation Message: PID segment


Value Description
<Patient ID>
PID-5. Patient Name

Value Description
^<given name (ST)> Name representation code: Reference of HL7Table0465
(example)

Value Description
YYYYMMDD(HHMM(SS))
(example) 20010131171823
PID-8. Sex
Value Description
F Female
M Male
O Other
U Unknown

7.3.1.3. Unsolicited Transmission of an Observation Message: PV1 segment
The PV1 segment in a patient basic information response message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI O N - Set ID - PV1
2 1 IS R R - Patient Class
3 80 PL O R - Assigned Patient Location
4 2 IS O N - Admission Type
5 250 CX O N - Preadmit Number
6 80 PL O N - Prior Patient Location
7 250 XCN O N Y Attending Doctor
8 250 XCN O N Y Referring Doctor
9 250 XCN B N Y Consulting Doctor
10 3 IS O N - Hospital Service
11 80 PL O N - Temporary Location
12 2 IS O N - Preadmit Test Indicator
13 2 IS O N - Re-admission Indicator
14 6 IS O N - Admit Source
15 2 IS O N Y Ambulatory Status
16 2 IS O N - VIP Indicator
17 250 XCN O N Y Admitting Doctor
18 2 IS O N - Patient Type
19 250 CN O N - Visit Number
20 50 FC O N Y Financial Class
21 2 IS O N - Charge Price Indicator
22 2 IS O N - Courtesy Code
23 2 IS O N - Credit Rating
24 2 IS O N Y Contract Code
25 8 DT O N Y Contract Effective Date
26 12 NM O N Y Contract Amount
27 3 NM O N Y Contract Period
28 2 IS O N - Interest Code
29 1 IS O N - Transfer to Bad Debt Code
30 8 DT O N - Transfer to Bad Debt Date
31 10 IS O N - Bad Debt Agency Code
32 12 NM O N - Bad Debt Transfer Amount
33 12 NM O N - Bad Debt Recovery Amount
34 1 IS O N - Delete Account Indicator
35 8 DT O N - Delete Account Date
36 3 IS O N - Discharge Disposition

37 25 CM O N - Discharged to Location
38 250 CE O N - Diet Type
39 2 IS O N - Servicing Facility
40 1 ID B N - Bed Status
41 2 IS O N - Account Status
42 80 PL O N - Pending Location
43 80 PL O N - Prior Temporary Location
44 26 TS O N - Admit Date/Time
45 26 TS O N Y Discharge Date/Time
46 12 NM O N - Current Patient Balance
47 12 NM O N - Total Charges
48 12 NM O N - Total Adjustments
49 12 NM O N - Total Payments
50 250 CX O N - Alternate Visit ID
51 1 IS O N - Visit Indicator
52 250 XCN B N Y Other Healthcare Provider
Table 16. Unsolicited Transmission of an Observation Message: PV1 segment
The field definition of an indispensable setup in PV1 segment and an arbitrary setup is shown
below.
PV1-2. Patient Class

Value Description
<Patient class> Refer to HL7Table0004
PV1-3. Assigned Patient Location

Value Description
<point of care (IS)>^<room (IS)>^<bed <bed> ： monitor name
(IS)>^<facility (HD)>^<location status
(IS)>^<person location type (IS)>^<building <facility> ： IP address + Bed Index No.1
(IS)>^<floor (IS)>^<location description (ST) ex) ^^BSM001^192.10.1.1:1
In the case of the bedside monitor, only a bed name
is set to <bed>.
ex) ^^BED-001^
1
HL7GW uses Internet Protocol address to specify a pertinent monitor. HL7GW doesn't see the first Internet
Protocol address because the first Internet Protocol address on the monitor system side is the same of it. The one
that a wireless cordless handset such as ORG adheres is identified with Bed Index Number 1･･･8 of the
cordless handset.

7.3.1.4. Unsolicited Transmission of an Observation Message: ORC Segment
The ORC segment in an unsolicited transmission of an observation message consists of the

following elements.

G/W /
Element Remarks
PVM /
BSM
1 2 ID R R N Order Control RE
－
2 22 EI C N - Placer Order Number
3 22 EI C N Filler Order Number
4 22 EI O N － Placer Group Number
5 2 ID O N N Order Status
6 1 ID O N - Response Flag
7 200 TQ O N Y Quantity/Timing
8 200 CM O N - Parent
9 26 TS O N Date/Time of Transaction
10 250 XCN O N Y Entered By
11 250 XCN O N Y Verified By
12 250 XCN O N Y Ordering Provider
13 80 PL O N - Enterer’s Location
14 250 XTM O N Y/2 Call Back Phone Number
15 26 TS O N - Order Effective Date/Time
16 250 CE O N - Order Control Code Reason
17 250 CE O N - Entering Organization
18 250 CE O N - Entering Device
19 250 XCN O N Y Action By
20 250 CE O N - Advanced Beneficiary Notice Code
21 250 XON O N Y Ordering Facility Name
22 250 XAD O N Y Ordering Facility Address
23 250 XTN O N Y Ordering Facility Phone Number
24 250 XAD O N Y Ordering Provider Address
25 250 CWE O N N Order Status Modifier
Table 17. Unsolicited transmission of an observation message: ORC segment
The field definition of an indispensable setup in ORC segment and an arbitrary setup is shown
below.
ORC-1. Order Control

Value Description
RE Determines the function of the order segment.
Refer to HL7Table0119

7.3.1.5. Unsolicited Transmission of an Observation Message: OBR Segment
The OBR segment in an unsolicited transmission of an observation message consists of the
following elements.
G/W /
Element Remarks
PVM /
BSM
1 4 SI O R - Set ID - OBR
2 22 EI C N -
－
Placer Order Number
3 22 EI C N
－
Filler Order Number
4 250 CE R R
－
Universal Service Identifier
5 2 ID B N Priority - OBR
6 26 TS B N - Requested Date/Time
7 26 TS C C - Observation Date/Time #
8 26 TS O N - Observation End Date/Time #
9 20 CQ O N - Collection Volume *
10 250 XCN O N Y Collector Identifier *
11 1 ID O N - Specimen Action Code *
12 250 CE O N -
－
Danger Code
13 300 ST O N Relevant Clinical Info.
14 26 TS C N - Specimen Received Date/Time *
15 300 CM O N - Specimen Source *
17 250 XTN O N Y/2 Order Callback Phone Number
18 60 ST O N - Placer Field 1
20 60 ST O N - Filler Field 1 +
22 26 TS C N - Results Rpt/Status Chng - Date/Time +
23 40 CM O N - Charge to Practice +
24 10 ID O N Diagnostic Serv Sect ID
25 1 ID C C - Result Status +
26 400 CM O N - Parent Result +
28 250 XCN O N Y/5 Result Copies To
29 200 CM O N Parent
30 20 ID O N - Transportation Mode
31 250 CE O N Y Reason for Study
32 200 CM O N - Principal Result Interpreter +
33 200 CM O N Y Assistant Result Interpreter +
34 200 CM O N Y Technician +
35 200 CM O N Y Transcriptionist +
36 26 TS O N - Scheduled Date/Time +
37 4 NM O N - Number of Sample Containers *
38 250 CE O N Y Transport Logistics of Collected Sample *
39 250 CE O N Y Collector's Comment *
40 250 CE O N - Transport Arrangement Responsibility
41 30 ID O N - Transport Arranged
42 1 ID O N - Escort Required

43 250 CE O N Y Planned Patient Transport Comment
44 250 CE O N Procedure Code
45 250 CE O N Y Procedure Code Modifier
46 250 CE O N Y Placer Supplemental Service Information
47 250 CE O N Y Filler Supplemental Service Information
Table 18. Unsolicited transmission of an observation message: OBR segment
The field definition of an indispensable setup in OBR segment and an arbitrary setup is shown
below.
OBR-1. Set ID
Value Description
sequence number
OBR-4. Universal Service identifier

Value Description
The code and name about the general term “vital
sign” of output information enter.
A default is the name and code which are received
from HL7 Gateway.
Other than observation value NIBP: VITAL
Observation value NIBP: NIBP
OBR-7. Observation Date/Time

Value Description
YYYYMMDDHHMMSS Year/Month/Day/Hour/minute/second
(example) 20070401171823
CNS: Current Time
PVM / BSM: Measurement Time
OBR-25. Result Status

Value Description
A (fixed) This field is the status of results for this order.

7.3.1.6. Unsolicited Transmission of an Observation Message: OBX Segment
The OBX segment in an unsolicited transmission of an observation message consists of the

following elements.

G/W /
Element Remarks
PVM /
BSM
14 26 TS O R - Date/Time of the Observation
15 250 CE O N - Producer’s ID
Table 19. Unsolicited transmission of an observation message: OBX segment
The field definition of an indispensable setups in OBX segment and an arbitrary setup is shown
below.
OBX-1. Set ID
Value Description
OBX-2. Value Type

Value Description
NM Numeric
ST String Data

Value Description
<identifier (ST)>^<text (ST)> The parameter code is set in <identifier>
and the universal ID plus the parameter
name are set in <text>.
Example: 001000^VITAL HR
Use the parameter code and the parameter
name received from the monitor network or
acquired from the bedside monitor.

Value Description
This field contains the value observed by the
Bedside Monitor. OBX-2-value type contains the
data type for this field according to which
observation value is formatted.
OBX-6. Units
Value Description
The unit defined with the monitor system is set.

Value Description
F Final results. Can only be changed with a corrected
result.
OBX-14. Date/Time of Observations

Value Description
YYYYMMDDHHMMSS Observation date/time
Year/Month/Day/hour/minute/second
(example) 20070401171823

7.3.2. Observation Unsolicited Transmission Response Message: ACK^R01
A vital numerical information distribution message consists of the following segments.
No. Segment Segment name HL7 G/W / PVM Remarks

/ BSM
Table 20. Observation unsolicited transmission response message: ACK^R01
The HL7 Gateway closes the socket under the following conditions.
1. MSA-1 Acknowledgment Code is AE.

2. ACK^R01 MSA-2 MsgCtrlID is not the same as ORU^R01 MSH-10 MsgCtrlID.
3. ACK^R01 cannot be received within five seconds after ORU^R01 is transmitted.

7.3.2.1. Vital Numerical Information Distribution Message: MSH Segment
The MSH segment in a vital numerical information distribution message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
9 13 CM R R - Message Type ACK^R01^
ACK
Table 21. Vital numerical information distribution message: MSH segment
below.

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description
(example) 20070401171823
MSH-9. Message Type

Value Description
ACK^R01ÂCK (fixed) Message Type: Reference of HL7Table0076

Value Description
YYYYMMDDNNNNNN ID of a partner system rule.
Set ORU^R01 MSH-10 Message Control ID.
Value Description
MSH-12. Version ID
Value Description

Value Description

Value Description

Value Description
ASCII

Value Description
ASCII

7.3.2.2. Observation Unsolicited Transmission Response Message: MSA segment
The MSA segment in a vital numerical information distribution message consists of the following
elements.

G/W /
Element Remarks
PVM /
BSM
6 250 CE O O - Error Condition
Table 22. Observation unsolicited transmission response message: MSA segment
below.

Value Description
<Acknowledgment code> Refer to HL7Table0008
MSA-2. Message Control ID

Value Description
YYYYMMDDNNNNNN This field contains the message control ID (MSH-
10) of the message sent by the sending system.
MSA-6. Error Condition

Value Description
<identifier (ST)>^<text (ST)>^<name of coding The Message Error Condition codes are defined by
system (IS)>^<alternate identifier HL7Table0357.
(ST)>^<alternate text (ST)>^<name of alternate (Usually this field is not used)
coding system (IS)>

7.4. Query for Results of Observation (Events R02, R04)
7.4.1. Vital Information Query Message: QRY^R02
A Vital Information Query Message consists of the following segments.
No. Segment Segment name HL7 G/W / PVM / Remarks

BSM
3 QRF Query Filter O
Table 23. Query, original mode message (QRY^R02)
braces {[...]}.

7.4.1.1. Observation Result Query - Query Message: MSH segment
The MSH segment in a Vital Information Query Message consists of the following elements.

G/W /
Element Remarks
PVM/
BSM
9 13 CM R R - Message Type QRY^R02^QRY_
R02
20 20 ID O O - Alternate Character Set Handling ASCII
Scheme
Table 24. Observation result query - query message: MSH segment
below.

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description
(example) 20010131171823
MSH-9. Message Type

Value Description
QRY^R02^QRY_R02 (fixed) Message Type: Reference of HL7Table0076

Value Description
<Message Control ID> ID of a partner system rule.
Value Description
MSH-12. Version ID
Value Description
2.4 (fixed) HL7 v2.4

Value Description

Value Description

Value Description
ASCII

Value Description
ASCII

7.4.1.2. Observation Result Query - Query Message: QRD segment
The QRD segment in a Vital Information Query Message consists of the following elements.
HL7
G/W /
PVM /
BSM
Table 25. Observation Result Query - Query Message: QRD segment
below.

Value Description
(example) 20010131171823

Value Description

Value Description

QRD-4. Query ID
Value Description
ID of the rule defined by the HL7 gateway or the
bedside monitor

Value Description

Value Description
<ID number (ST)>^<family name (ST)>^<given
A candidate patient is set up.
name (ST)>
Only <Patient ID Number> is used.
^<suffix (e. g., JR or III) (ST)>
^<prefix (e. g., DR) (ST)>
^<degree (e. g., MD) (IS)>
employed (ID)>

Value Description
Result
RES (fixed)

Value Description
<identifier (ID)>^<text (ST)>^<name of coding (Usually this field is not used)
system (ST)>^<alternate identifier
(ID)>^<alternate text (ST)>^<name of alternate
coding system (ST)>

7.4.1.3. Observation Result Query - Query Message: QRF segment
HL7
G/W /
PVM /
BSM
1 20 ST R R Y Where Subject Filter
2 26 TS B N - When Data Start Date/Time
3 26 TS B N - When Data End Date/Time
4 60 ST O N Y What User Qualifier
5 60 ST O N Y Other QRY Subject Filter
6 12 ID O N Y Which Date/Time Qualifier
7 12 ID O N Y Which Date/Time Status Qualifier
8 12 ID O N Y Date/Time Selection Qualifier
9 60 TQ O O - When Quantity/Timing Qualifier
10 10 NM O N - Search Confidence Threshold
Table 26. Observation Result Query - Query Message: QRF segment
The field definition of an indispensable setup in QRF segment and an arbitrary setup is shown
below.
QRF-1. Where Subject Filter

Value Description
This field identifies the department, system, or
subsystem to which the query pertains.
(example) HL7 Gateway
QRF-9. When Quantity/Timing Qualifier

Value Description
^^^YYYYMMDDhhmmss (start date/time)^
YYYYMMDDhhmmss (end date/time)

7.4.2. Observation Result Query - Response Message: ORF^R04
No. Segment Segment name HL7 G/W / PVM / Remarks

BSM
4 (QRF) Query Filter N
{
[
5 PID Patient ID R
6 [{NTE}] Notes and Comments N
]
{
7 [ORC] Order common R
8 OBR Observation request R
10 [CTD] Contact Data N
{
11 [OBX] Observation/Result R
}
13 {[CTI]} Clinical Trial Identification N
}}
14 [ERR] Error N
15 [QAK] Query Acknowledgement N
Table 27. Vital Information Response Message: ORF
braces {[...]}.

7.4.2.1. Observation Result Query - Response Message: MSH segment

G/W /
Element Remarks
PVM/
BSM
9 13 CM R R - Message Type ORF^R04ÔRF_R04
Table 28. Observation Result Query - Response Message: MSH segment
below.

Value Description
MSH-2. Encoding characters

Value Description

Value Description

Value Description

Value Description

Value Description

Value Description
(example) 20070401171823

MSH-9. Message Type
Value Description
ORF^R04ÔRF_R04 (fixed) Message Type: Reference of HL7Table0076

Value Description
(example) 20070401123456
ID of the partner system rule
The message control ID of MSH-10 in QRY^R02 is
returned.
Value Description
MSH-12. Version ID
Value Description

Value Description

Value Description

Value Description
ASCII

Value Description
ASCII

7.4.2.2. Observation Result Query - Response Message: MSA segment

G/W /
Element Remarks
PVM /
BSM
6 250 CE O N - Error Condition
Table 29. Observation Result Query - Response Message: MSA segment
below.

Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment:
Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment:
Error
MSA-2. Message Control

Value Description
Set QRYÂ19 MSH-10 Message Control ID.
This field contains the message control ID of the
message sent by the sending system.

7.4.2.3. Observation Result Query - Response Message: QRD segment
The QRD segment in a Vital Information Query Message consists of the following elements.
Each value is the same as the QRD segment of the QRY message.
HL7
G/W /
PVM /
BSM
Table 30. Observation Result Query - Response Message: QRD segment
below.

Value Description
(example) 20010131171823

Value Description

Value Description

QRD-4. Query ID
Value Description
Same as QRD-4 of QRY

Value Description

Value Description
<ID number (ST)>^<family name (ST)>^<given
A candidate patient setup.
name (ST)>
Only <Patient ID Number > is used.
^<degree (e. g., MD) (IS)>
employed (ID)>

Value Description
Result
RES (fixed)

Value Description
<identifier (ID)>^<text (ST)>^<name of coding (Usually this field is not used)
system (ST)>^<alternate identifier
(ID)>^<alternate text (ST)>^<name of alternate
coding system (ST)>

7.4.2.4. Observation Result Query - Response Message: PID segment
The PID segment in a Vital Information Response Message consists of the following elements.

G/W /
Element Remarks
PVM /
BSM
Table 31. Observation Result Query - Response Message: PID Segment


Value Description
<Patient ID>
PID-5. Patient Name

Value Description
^<given name (ST)> Name representation type: Reference of HL7Table0465
(example)

Value Description
YYYYMMDD(HHMM(SS))
(example) 20010131171823
PID-8. Sex
Value Description
F Female
M Male
O Other
U Unknown

7.4.2.5. Observation Result Query - Response Message: ORC segment
The ORC segment in a Vital Information Response Message consists of the following elements.

G/W /
Element Remarks
PVM /
BSM
1 2 ID R R N Order Control RE
2 22 EI C N -
－
Placer Order Number
3 22 EI C N Filler Order Number
4 22 EI O N － Placer Group Number
5 2 ID O N N Order Status
6 1 ID O N - Response Flag
8 200 CM O N - Parent
9 26 TS O N Date/Time of Transaction
10 250 XCN O N Y Entered By
11 250 XCN O N Y Verified By
13 80 PL O N - Enterer’s Location
14 250 XTM O N Y/2 Call Back Phone Number
15 26 TS O N - Order Effective Date/Time
16 250 CE O N - Order Control Code Reason
17 250 CE O N - Entering Organization
18 250 CE O N - Entering Device
19 250 XCN O N Y Action By
20 250 CE O N - Advanced Beneficiary Notice Code
21 250 XON O N Y Ordering Facility Name
22 250 XAD O N Y Ordering Facility Address
23 250 XTN O N Y Ordering Facility Phone Number
24 250 XAD O N Y Ordering Provider Address
25 250 CWE O N N Order Status Modifier
Table 32. Observation Result Query - Response Message: ORC segment
The field definition of an indispensable setup in ORC segment and an arbitrary setup is shown
below.
ORC-1. Order control

Value Description
RE Determines the function of the order segment.

7.4.2.6. Observation Result Query - Response Message: OBR segment
The OBR segment in a Vital Information Response Message consists of the following elements.

G/W /
Element Remarks
PVM /
BSM
1 4 SI O R - Set ID - OBR
2 22 EI C N -
－
Placer Order Number
3 22 EI C N
－
Filler Order Number
4 250 CE R R
－
Universal Service Identifier
5 2 ID B N Priority - OBR
6 26 TS B N - Requested Date/Time
7 26 TS C C - Observation Date/Time #
8 26 TS O N - Observation End Date/Time #
9 20 CQ O N - Collection Volume *
10 250 XCN O N Y Collector Identifier *
11 1 ID O N - Specimen Action Code *
－
12 250 CE O N - Danger Code
13 300 ST O N Relevant Clinical Info.
14 26 TS C N - Specimen Received Date/Time *
15 300 CM O O - Specimen Source *
17 250 XTN O N Y/2 Order Callback Phone Number
22 26 TS C N - Results Rpt/Status Chng - Date/Time +
23 40 CM O N - Charge to Practice +
24 10 ID O N Diagnostic Serv Sect ID
25 1 ID C C - Result Status +
26 400 CM O N - Parent Result +
28 250 XCN O N Y/5 Result Copies To
29 200 CM O N Parent
30 20 ID O N - Transportation Mode
31 250 CE O N Y Reason for Study
32 200 CM O N - Principal Result Interpreter +
33 200 CM O N Y Assistant Result Interpreter +
34 200 CM O N Y Technician +
35 200 CM O N Y Transcriptionist +
36 26 TS O N - Scheduled Date/Time +
37 4 NM O N - Number of Sample Containers *
38 250 CE O N Y Transport Logistics of Collected Sample *
39 250 CE O N Y Collector's Comment *
40 250 CE O N - Transport Arrangement Responsibility

41 30 ID O N - Transport Arranged
42 1 ID O N - Escort Required
43 250 CE O N Y Planned Patient Transport Comment
44 250 CE O N Procedure Code
45 250 CE O N Y Procedure Code Modifier
46 250 CE O N Y Placer Supplemental Service Information
47 250 CE O N Y Filler Supplemental Service Information
Table 33. Observation Result Query - Response Message: OBR segment
The field definition of an indispensable setup in OBR segment and an arbitrary setup is shown
below.
OBR-1. Set ID
Value Description
sequence number
OBR-4. Universal Service Identifier

Value Description
The code and name about the general term “vital
sign” of output information enter.
A default is the name and code which are received
from HL7 Gateway.
Other than observation value NIBP: VITAL
Observation value NIBP: NIBP
OBR-7. Observation Date/Time

Value Description
YYYYMMDDHHMMSS Year/Month/Day/Hour/minute/second
(example) 20070401171823
OBR-15. Specimen Source

Value Description
Specimen Source (fixed)
OBR-25. Result Status

Value Description
A (fixed) This field is the status of results for this order.

7.4.2.7. Vital Information Response Message: OBX segment
The OBX segment in a Vital Information Response Message consists of the following elements.

G/W /
Element Remarks
PVM /
BSM
14 26 TS O O - Date/Time of the Observation
15 250 CE O N - Producer's ID
Table 34. Vital Information Response Message: OBX segment
The field definition of an indispensable setup in OBX segment and an arbitrary setup is shown
below.
OBX-1. Set ID
Value Description
OBX-2. Value Type

Value Description
NM Numeric
ST String Data

Value Description
<identifier (ST)>^<text (ST)> The parameter code is set in <identifier>
and the universal ID plus the parameter
name are set in <text>.
Example: 001000^VITAL HR
Use the parameter code and the parameter
name received from the monitor network or
acquired from the bedside monitor.

Value Description
This field contains the value observed by the
Bedside Monitor. OBX-2-value type contains the
data type for this field according to which
observation value is formatted.
OBX-6. Units
Value Description
The unit defined with the monitor system is set.

Value Description
F Final results. Can only be changed with a corrected
result.
OBX-14. Date/Time of Observation

Value Description
YYYYMMDDHHMMSS Observation date/time.
Year/Month/Day/hour/minute/second
(example) 20070401171823

8. Error Condition Table
8.1. HL7Table0357 – Message Error Condition Codes
Error Error Condition Text Description/Comment

Condition
Code
0 Message accepted Success. Optional, as the AA conveys success. Used for systems
that must always return a status code.
100 Segment sequence error Errors. The message segments were not in the proper order, or
required segments are missing.
101 Required field missing Errors. A required field is missing from a segment.
102 Data type error Errors. The field contained data of the wrong data type, e.g. an
NM field contained “FOO.”
103 Table value not found Errors. A field of data type ID or IS was compared against the
corresponding table, and no match was found.
200 Unsupported message type Rejection. The Message Type is not supported.
201 Unsupported event code Rejection. The Event Code is not supported.
202 Unsupported processing ID Rejection. The Processing ID is not supported.
203 Unsupported version id Rejection. The Version ID is not supported.
204 Unknown key identifier Rejection. The ID of the patient, order, etc., was not found. Used
for transactions other than additions, e. g. transfer of a non-
existent patient.
205 Duplicate key identifier Rejection. The ID of the patient, order, etc., already exists. Used in
response to addition transactions (Admit, New Order, etc. ).
206 Application record locked Rejection. The transaction could not be performed at the
application storage level, e. g. database locked.
207 Application internal error Rejection. A catchall for internal errors not explicitly covered by
other codes.
Table 35. Message error condition codes

Appendix
Appendix-1
Contents
Appendix A ParameterList ............................................................................................ 3
Appendix B samples ..................................................................................................... 9
【】
1. Patient information query QRYÂ19 ADRÂ19 .......................................................... 9
【
2. Unsolicited observation - measurement value ORU^R01 ACK^R01 ....................... 10 】
【】
3. Query for measurement value QRY^R02 ORF^R04 .................................................. 11
Appendix-2
Appendix A ParameterList
Parameter Parameter Subcode String String Remarks

Code
1 ECG 0 Average HR 001000 HR||80|bpm
(beats/min)
2 VPC 0 VPC / minute 002000 VPC||5|/min
3 ST 0 I (mV) 003000 ST1||-0.07|mV
1 II (mV) 003001 ST2||-0.06|mV
2 III (mV) 003002 ST3||-0.05|mV
3 AVR (mV) 003003 STVR||-0.04|mV
4 AVL (mV) 003004 STVL||-0.03|mV
5 AVF (mV) 003005 STVF||-0.02|mV
6 V1 (mV) 003006 STV1||-0.01|mV
7 V2 (mV) 003007 STV2||0.00|mV
8 V3 (mV) 003008 STV3||0.01|mV
9 V4 (mV) 003009 STV4||0.02|mV
10 V5 (mV) 003010 STV5||0.03|mV
11 V6 (mV) 003011 STV6||0.04|mV
12 V (mV) 003012 STV||0.05|mV
13 MCL (mV) 003013 STMCL||0.06|mV
14 ECG1 (mV) 003014 STecg1||0.07|mV
15 ECG2 (mV) 003015 STecg2||0.08|mV
4 Respiration 0 Average Resp Rate 004000
RESP||12|/min
(/min)
1 Apnea (sec) 004001 APSEC(RESP)||5|sec
5 Impedance Resp Rate 004005
rRESP(imp)||15|/min
(/min)
6 Thermistor Resp Rate 004006 *1
rRESP(the)||15|/min
(/min)
73 CO2 Resp Rate (/min) 004073 rRESP(co2)||15|/min
85 Flow Resp Rate (/min) 004085 rRESP(flow)||15|/min *1
91 Anesthesia Resp Rate 004091 *1
rRESP(anes)||15|/min
(/min)
5 Impedance 0 Impedance Resp Rate 005000 RESP||14|/min
Respiration (/min)
1 Apnea (sec) 005001 APSEC(RESP)||0|sec
6 Thermistor 0 Thermistor 006000 *1 *5
RESP_T||14|/min
Respiration Respiration (/min)
1 Apnea (sec) 006001 APSEC(RESP_T)||5|sec *1 *5
7 SpO2 0 SpO2 (%) 007000 SpO2||98|%
1 Average PR (/min) 007001 PR(spo2)||82|/min
8 SpO2-2 0 SpO2 (%) 008000 SpO2_2||90|% *1 *5
1 Average PR (/min) 008001 PR(spo2_2)||80|/min *1 *5
9 NiBP 0 Systolic (mmHg) 009000 SYS||127|mmHg *2
1 Diastolic (mmHg) 009001 DIAS||77|mmHg *2
2 Mean (mmHg) 009002 MEAN||90|mmHg *2
11 Tskin 0 Temperature (C) 011000 TSKIN||36.9|C *1
12 Tskin-2 0 Temperature (C) 012000 TSKIN_2||36.9|C *1
13 Tskin-3 0 Temperature (C) 013000 TSKIN_3||36.9|C *1 *5
14 Trect 0 Temperature (C) 014000 TRECT||37.1|C *1
Appendix-3
15 Tcore 0 Temperature (C) 015000 TCORE||37.1|C *1
16 Tnaso 0 Temperature (C) 016000 TNASO||37.1|C *1
17 Teso 0 Temperature (C) 017000 TESO||36.8|C *1
18 Ttymp 0 Temperature (C) 018000 TTYMP||37.0|C *1
21 Tblad 0 Temperature (C) 021000 TBLAD||37.1|C *1
22 Taxil 0 Temperature (C) 022000 TAXIL||37.1|C *1
27 Temp 0 Temperature (C) 027000 TEMP||37.1|C
28 Temp-2 0 Temperature (C) 028000 TEMP2||36.9|C *1
29 Temp-3 0 Temperature (C) 029000 TEMP3||36.8|C *1 *5
30 Temp-4 0 Temperature (C) 030000 TEMP4||37.0|C *1 *5
31 Temp-5 0 Temperature (C) 031000 TEMP5||37.1|C *1 *4 *5
37 Delta-T 0 Delta-T (C) 037000 dT1||2.1|C *1
38 Delta-T2 0 Delta-T (C) 038000 dT2||2.2|C *1 *5
39 Delta-T3 0 Delta-T (C) 039000 dT3||2.3|C *1 *4 *5
40 Delta-T4 0 Delta-T (C) 040000 dT4||2.4|C *1 *4 *5
41 Tb (Cath) 0 Temperature (C) 041000 TB||37.1|C *1 *4 *5
43 Tb (CCO) 0 Temperature (C) 043000 TB_CCO||37.1|C *1 *4 *5
44 ART 0 Systolic (mmHg) 044000 ART(S)||120|mmHg
1 Diastolic (mmHg) 044001 ART(D)||60|mmHg
2 Mean (mmHg) 044002 ART(M)||85|mmHg
6 Average PR (/min) 044006 PR(art)||80|/min
45 ART-2 0 Systolic (mmHg) 045000 ART_2(S)||120|mmHg *1
1 Diastolic (mmHg) 045001 ART_2(D)||60|mmHg *1
2 Mean (mmHg) 045002 ART_2(M)||85|mmHg *1
6 Average PR (/min) 045006 PR(art_2)||79|/min *1
46 RAD 0 Systolic (mmHg) 046000 RAD(S)||120|mmHg
1 Diastolic (mmHg) 046001 RAD(D)||60|mmHg
2 Mean (mmHg) 046002 RAD(M)||85|mmHg
6 Average PR (/min) 046006 PR(rad)||79|/min
47 DORS 0 Systolic (mmHg) 047000 DORS(S)||120|mmHg
1 Diastolic (mmHg) 047001 DORS(D)||60|mmHg
2 Mean (mmHg) 047002 DORS(M)||85|mmHg
6 Average PR (/min) 047006 PR(dors)||79|/min
48 AO 0 Systolic (mmHg) 048000 AO(S)||120|mmHg
1 Diastolic (mmHg) 048001 AO(D)||60|mmHg
2 Mean (mmHg) 048002 AO(M)||85|mmHg
6 Average PR (/min) 048006 PR(ao)||79|/min
49 FEM 0 Systolic (mmHg) 049000 FEM(S)||120|mmHg
1 Diastolic (mmHg) 049001 FEM(D)||60|mmHg
2 Mean (mmHg) 049002 FEM(M)||85|mmHg
6 Average PR (/min) 049006 PR(fem)||79|/min
50 UA 0 Systolic (mmHg) 050000 UA(S)||120|mmHg
1 Diastolic (mmHg) 050001 UA(D)||60|mmHg
Appendix-4
2 Mean (mmHg) 050002 UA(M)||85|mmHg
3 Average PR (/min) 050003 PR(ua)||79|/min
51 UV 0 Systolic (mmHg) 051000 UV(S)||12|mmHg
1 Diastolic (mmHg) 051001 UV(D)||6|mmHg
2 Mean (mmHg) 051002 UV(M)||8|mmHg
3 Average PR (/min) 051003 PR(uv)||79|/min
52 PAP 0 Systolic (mmHg) 052000 PAP(S)||21|mmHg
1 Diastolic (mmHg) 052001 PAP(D)||7|mmHg
2 Mean (mmHg) 052002 PAP(M)||14|mmHg
53 CVP 0 Systolic (mmHg) 053000 CVP(S)||8|mmHg
1 Diastolic (mmHg) 053001 CVP(D)||3|mmHg
2 Mean (mmHg) 053002 CVP(M)||5|mmHg
3 Average PR (/min) 053003 PR(cvp)||6|/min
54 RAP 0 Systolic (mmHg) 054000 RAP(S)||135|mmHg
1 Diastolic (mmHg) 054001 RAP(D)||80|mmHg
2 Mean (mmHg) 054002 RAP(M)||102|mmHg
3 Average PR (/min) 054003 PR(rap)||79|/min
55 RVP 0 Systolic (mmHg) 055000 RVP(S)||9|mmHg
1 Diastolic (mmHg) 055001 RVP(D)||4|mmHg
2 Mean (mmHg) 055002 RVP(M)||6|mmHg
3 Average PR (/min) 055003 PR(rvp)||79|/min
56 LAP 0 Systolic (mmHg) 056000 LAP(S)||9|mmHg
1 Diastolic (mmHg) 056001 LAP(D)||4|mmHg
2 Mean (mmHg) 056002 LAP(M)||6|mmHg
3 Average PR (/min) 056003 PR(lap)||79|/min
57 LVP 0 Systolic (mmHg) 057000 LVP(S)||120|mmHg
1 Diastolic (mmHg) 057001 LVP(D)||60|mmHg
2 Mean (mmHg) 057002 LVP(M)||85|mmHg
3 Average PR (/min) 057003 PR(lvp)||79|/min
58 ICP 0 Maximum (mmHg) 058000 ICP(S)||8|mmHg
1 Minimum (mmHg) 058001 ICP(D)||3|mmHg
2 Mean (mmHg) 058002 ICP(M)||5|mmHg
59 ICP-2 0 Maximum (mmHg) 059000 ICP_2(S)||8|mmHg *1
1 Minimum (mmHg) 059001 ICP_2(D)||3|mmHg *1
2 Mean (mmHg) 059002 ICP_2(M)||5|mmHg *1
62 Press 0 Systolic (mmHg) 062000 PRESS(S)||135|mmHg
1 Diastolic (mmHg) 062001 PRESS(D)||80|mmHg
2 Mean (mmHg) 062002 PRESS(M)||102|mmHg
3 Average PR (/min) 062003 PR(p1)||79|/min
63 Press-2 0 Systolic (mmHg) 063000 PRESS_2(S)||12|mmHg *1
Appendix-5
1 Diastolic (mmHg) 063001 PRESS_2(D)||6|mmHg *1
2 Mean (mmHg) 063002 PRESS_2(M)||8|mmHg *1
3 Average PR (/min) 063003 PR(p2)||79|/min *1
69 Press-8 0 Systolic (mmHg) 069000 PRESS_8(S)||12|mmHg *1 *4 *5
1 Diastolic (mmHg) 069001 PRESS_8(D)||6|mmHg *1 *4 *5
2 Mean (mmHg) 069002 PRESS_8(M)||8|mmHg *1 *4 *5
3 Average PR (/min) 069003 PR(p8)||79|/min *1 *4 *5
72 PR 0 Average PR (/min) 072000 PR||79|/min
7 SpO2 Avg PR (/min) 072007 rPR(spo2)||80|/min
8 SpO2_2 Avg PR (/min) 072008 rPR(spo2_2)||80|/min *1
44 ART Avg PR (/min) 072044 rPR(art)||80|/min
45 ART-2 Avg PR (/min) 072045 rPR(art_2)||80|/min *1
46 RAD Avg PR (/min) 072046 rPR(rad)||80|/min
47 DORS Avg PR (/min) 072047 rPR(dors)||80|/min
48 AO Avg PR (/min) 072048 rPR(ao)||80|/min
49 FEM Avg PR (/min) 072049 rPR(fem)||80|/min
50 UA Avg PR (/min) 072050 rPR(ua)||80|/min
51 UV Avg PR (/min) 072051 rPR(uv)||80|/min
52 PAP Avg PR (/min) 072052 rRP(pap)||80|/min
53 CVP Avg PR (/min) 072053 rPR(cvp)||80|/min
54 RAP Avg PR (/min) 072054 rPR(rap)||80|/min
55 RVP Avg PR (/min) 072055 rPR(rvp)||80|/min
56 LAP Avg PR (/min) 072056 rPR(lap)||80|/min
57 LVP Avg PR (/min) 072057 rPR(lvp)||80|/min
62 Press Avg PR (/min) 072062 rPR(press)||80|/min
63 Press-2 Avg PR (/min) 072063 rPR(press2)||80|/min *1
Appendix-6
69 Press-8 Avg PR (/min) 072069 rPR(press8)||80|/min *1 *4 *5
73 CO2 0 Average Resp Rate 073000
RESP(co2)||12|/min
(/min)
1 Exp CO2 (EtCO2) 073001
EtCO2||4.0|mmHg
(mmHg)
2 Insp CO2 (FiCO2) 073002
FiCO2||1.0|mmHg
(mmHg)
3 Apnea (sec) 073003 APSEC（CO2）||0|sec
75 FiO2 0 Inspired O2 (FiO2) (%) 075000 FiO2||23.00|% *1 *5
1 Expired O2 (EtO2) (%) 075001 EtO2||50.00|% *1 *4 *5
76 CCO 0 CCO (L/min) 076000 CCO||5.12|L/min *1
1 Tb (C) 076001 CCOTb||37.2|C *1
2 CI (L/min/m2) 076002 CCI||2.93|L/(min*sq,m,) *1
83 SvO2 0 SvO2 (CCO) (%) 083000 *1
SvO2_CCO||69|%
(CCO)
84 tcP (tcPO2 0 TcPO2 (mmHg) 084000 tcPO2||40|mmHg *1
+ tcPCO2) 1 TcPCO2 (mmHg) 084001 *1
tcPCO2||50|mmHg
85 Flow 0 Average Resp Rate 085000 *1
RESP(Flow)||14|/min
(/min)
1 MV (L/min) 085001 MV(Flow)||5.3|L/min *1
2 Expired TV (mL) 085002 TV(Flow)||500|mL *1
12 Apnea Time (sec) 085012 APSEC(Flow)||6|sec *1
86 PAW 0 Maximum (Ppeak) 086000 *1
Ppeak||16.00|cmH2O
(cmH2O)
3 PEEP (cmH2O) 086003 PEEP||3.00|cmH2O *1
88 Ventilator 0 Compliance 088000 *1
EVITAC||0.1|mL/cmH2O
(mL/cmH2O)
1 Resistance 088001 *1
EVITAR||2|cmH2O/L/sec
(cmH2O/L/sec)
2 PAW Minimum 088002 *1
EVITAPmin||1.00|cmH2O
(cmH2O)
3 PAW Mean (cmH2O) 088003 EVITAPmean||1.00|cmH2O *1
5 PEEP (cmH2O) 088005 EVITAPEEP||1.00|cmH2O *1
6 PAW Peak (cmH2O) 088006 EVITAPpeak||1.00|cmH2O *1
7 TV (L) 088007 EVITATV||0.08|L *1
8 Spont Resp Rate 088008 *1
EVITARRspo||9|/min
(/min)
9 Spont MV (L/min) 088009 EVITAMVspo||1.0|L/min *1
10 MV (L/min) 088010 EVITAMV||1.1|L/min *1
11 Airway Temperature 088011 *1
EVITATemp||1.2|C
(C)
12 Resp Rate (/min) 088012 EVITARR||13|/min *1
13 ExpCO2 (EtCO2) 088013 *1
EVITAEtCO2||10.0|mmHg
(mmHg)
14 InspO2 (FiO2) (%) 088014 EVITAFiO2||1.00|% *1
91 Anesthesia 0 ExpAgent CO2 091000 *1
ANESEtCO2||40.0|mmHg
(EtCO2) (mmHg)
1 InspAgent CO2 091001 *1
ANESFiCO2||0.0|mmHg
(FiCO2) (mmHg)
Appendix-7
2 ExpAgent N2O 091002 *1
ANESEtN2O||58.00|%
(EtN2O) (%)
3 InspAgent N2O 091003 *1
ANESFiN2O||64.00|%
(FiN2O) (%)
4 ExpAgent O2 (EtO2) 091004 *1
ANESEtO2||28.00|%
(%)
5 InspAgent O2 (FiO2) 091005 *1
ANESFiO2||34.00|%
(%)
6 ExpHal (EtHAL) (%) 091006 ANESEtHal||1.00|% *1
7 InspHal (FiHAL) (%) 091007 ANESFiHal||1.00|% *1
8 ExpIso (EtISO) (%) 091008 ANESEtISO||2.50|% *1
9 InspIso (FiISO) (%) 091009 ANESFiISO||3.50|% *1
10 ExpEnf (EtENF) (%) 091010 ANESEtENF||3.50|% *1
11 InspEnf (FiENF) (%) 091011 ANESFiENF||4.00|% *1
12 ExpDes (EtDES) (%) 091012 ANESEtDES||10.00|% *1
13 InspDes (FiDES) (%) 091013 ANESFiDES||10.00|% *1
14 ExpSev (EtSEV) (%) 091014 ANESEtSEV||1.00|% *1
15 InspSev (FiSEV) (%) 091015 ANESFiSEV||1.00|% *1
18 Agent Resp Rate 091018 *1
ANESRESP||14|/min
(/min)
19 Agent Apnea (sec) 091019 APSEC(ANES)||5|sec *1
103 BIS 0 BIS 103000 BIS||68.0| *1
108 Delta-SpO2 0 Delta-SpO2 (%) 108000 dSpO2||8|% *1 *5
111 EEG1 0 SEF (Spectral Edge 111000 *1 *4 *5
SEF1||5.9|Hz
Frequency) (Hz)
3 TP (Total Power) (nW) 111003 TP1||9.99|nW *1 *4 *5
112 EEG2 0 SEF (Spectral Edge *1 *4 *5
112000 SEF2||5.9|Hz
Frequency) (Hz)
3 TP (Total Power) (nW) 112003 TP2||9.99|nW *1 *4 *5
113 CNIBP 0 Systolic (mmHg) 113000 SYS(cnibp)||200|mmHg *1 *3 *4 *5
1 Diastolic (mmHg) 113001 DIAS(cnibp)||100|mmHg *1 *3 *4 *5
2 Mean (mmHg) 113002 MEAN(cnibp)||155|mmHg *1 *3 *4 *5
119 PiCCO 0 PCCO (L/min) 119000 PCCO(EXT)||5.12|L/min *1
1 PCCI (L/min/m2) 119001 PCCI(EXT)||2.93|L/(min*sq,m,) *1
9 Tb(EXT) (C) 119009 Tb(EXT)||37.2|C *1
17 ScvO2 (%) 119017 ScvO2(EXT)||69|% *1
*1 PVM-2700 series does not support.

*2 OBR2 (non-reguler data)
*3 OBR1 (reguler data)
*4 BSM-6000 series does not support.
*5 BSM-3000 series does not support.
Appendix-8
Appendix B samples
1. Patient information query 【QRYÂ19 ADRÂ19 】

【 QRY A19 】HL7GW / Bedside monitor → Other system
MSH|^~\&|NIHON KOHDEN|NIHON KOHDEN|CLIENT APP|CLIENT

FACILITY|20080123110707||
QRYÂ19^QRY_A19|20080123000000|P|2.4|||NE|AL|Japan|ASCII||ASCII
QRD|20080123110707|R|I|0123000000^|||RD^1|id-sbr1203|APN|||
【 ADR A21 】Other system → HL7GW / Bedside monitor
MSH|^~\&|HIS||GCP97||||ADRÂ19ÂDR_A19|19971104015820|P|2.4||||||ASCII||
MSA|AA|20080123000000
QRD|19971104015820|R|I|QPID015820|||RD^1|id-sbr1203
PID|||id-sbr1203||Kohden^Taro^^^^^LÂ|KOHDEN|19600101|M||AAA|
OBX|1|NM|12345^Height||170|cm|||||F||||||
OBX|2|NM|12345^Weight||65|kg|||||F||||||
OBX|3|NM|12345^Blood||A+||||||F||||||
DG1|1|||Server overweight||||||||||||WhiteID-9800|||
Appendix-9
2. Unsolicited observation - measurement value 【ORU^R01 ACK^R01 】
【 ORU R01 】HL7GW / Bedside monitor → Other system

FACILITY|20080123143207||ORU^R01ÔRU_R01|20080123000205|P|2.4|||NE|AL|Japa
n|ASCII||ASCII
PID|||id-sbr1203||Kohden^Taro^^^^^LÂ||19600101|M
PV1||I|^^sbr003^10.2.2.12:3
ORC|RE
OBR|1|||VITAL|||20080123143206||||||||||||||||||A
OBX|1|NM|001000^VITAL HR|1|80|bpm|||||F|||20080123143206|||
OBX|2|NM|002000^VITAL VPC|1|5|/min|||||F|||20080123143206|||
OBX|3|NM|003001^VITAL ST2|1|-0.06|mV|||||F|||20080123143206|||
OBX|4|NM|004001^VITAL APSEC(RESP)|1|5|sec|||||F|||20080123143206|||
OBX|5|NM|004005^VITAL rRESP(imp)|1|15|/min|||||F|||20080123143206|||
OBX|6|NM|005000^VITAL RESP|1|14|/min|||||F|||20080123143206|||
OBX|7|NM|007000^VITAL SpO2|1|98|%|||||F|||20080123143206|||
OBX|8|NM|007001^VITAL PR(spo2)|1|82|/min|||||F|||20080123143206|||
OBX|9|NM|062000^VITAL PRESS(S)|1|135|mmHg|||||F|||20080123143206|||
OBX|10|NM|062001^VITAL PRESS(D)|1|80|mmHg|||||F|||20080123143206|||
OBX|11|NM|062002^VITAL PRESS(M)|1|102|mmHg|||||F|||20080123143206|||
OBX|12|NM|062003^VITAL PR(p1)|1|79|/min|||||F|||20080123143206|||
OBR|2|||NIBP|||20071030103052||||||||||||||||||A
OBX|1|NM|009000^NIBP SYS|1|127|mmHg|||||F|||20071030103052|||
OBX|2|NM|009001^NIBP DIAS|1|77|mmHg|||||F|||20071030103052|||
OBX|3|NM|009002^NIBP MEAN|1|90|mmHg|||||F|||20071030103052|||
【 ACK＾R01 】Other system → HL7GW / Bedside monitor
MSH|^~\&|||||||ACK^R01ÂCK|20080123000205|P|||||||ASCII||ASCII
MSA|AA|20080123000205
Appendix-10
3. Query for measurement value 【QRY^R02 ORF^R04 】
transmission interval : 5 minutes
【 QRY^R02 】Other system → HL7GW / Bedside monitor
MSH|^~\&|Trend Data Test Client|HIS Send TEST|Trend Data Server|RCV TEST|

20080118115103||QRY^R02^QRY_R02|20080118115103|P|2.4|||NE|AL||ASCII||
QRD|20080118115103|R|I|Trend|||RD^1|id-sbr097|RES|||
QRF|||||||||^^^20080118095017^20080118105017
【 ORF R04 】HL7GW / Bedside monitor → Other system

FACILITY|20080118114856||ORF^R04ÔRF_R04|20080118115103|P|2.4|||NE|AL|Japan
|ASCII||
MSA|AA|20080118115103
QRD|20080118115103|R|I|Trend|||RD^1|id-sbr097|RES|||
PID|||id-sbr097||Kohden_097^Subaru^^^^^LÂ||19670119|M
ORC|RE
OBR|1|||VITAL|||20080118095000||||||||SpecimenSource||||||||||A
OBX|3|NM|003000^VITAL ST1|1|-7|mV|||||F|||20080118095000|||
OBX|4|NM|004001^VITAL APSEC(RESP)|1|5|sec|||||F|||20080118095000|||
OBX|6|NM|007000^VITAL SpO2|1|98|%|||||F|||20080118095000|||
OBX|11|NM|027000^VITAL TEMP|1|371|C|||||F|||20080118095000|||
OBX|12|NM|044000^VITAL ART(S)|1|120|mmHg|||||F|||20080118095000|||
OBX|13|NM|044001^VITAL ART(D)|1|60|mmHg|||||F|||20080118095000|||
OBX|14|NM|044002^VITAL ART(M)|1|85|mmHg|||||F|||20080118095000|||
OBR|2|||VITAL|||20080118095500||||||||SpecimenSource||||||||||A
OBX|3|NM|003000^VITAL ST1|1|-7|mV|||||F|||20080118095500|||
OBX|5|NM|007000^VITAL SpO2|1|98|%|||||F|||20080118095500|||
：
OBX|11|NM|027000^VITAL TEMP|1|371|C|||||F|||20080118104500|||
OBX|12|NM|044000^VITAL ART(S)|1|120|mmHg|||||F|||20080118104500|||
OBX|13|NM|044001^VITAL ART(D)|1|60|mmHg|||||F|||20080118104500|||
OBX|14|NM|044002^VITAL ART(M)|1|85|mmHg|||||F|||20080118104500|||
Appendix-11
Manufacturer
NIHON KOHDEN CORPORATION NIHON KOHDEN ITALIA S.r.l.
1-31-4 Nishiochiai, Shinjuku-ku Tokyo 161-8560, Japan Via Fratelli Bronzetti 28, 24124 Bergamo, Italy
Phone + 81 3- 5996 -8036 Phone + 39 035-219543
Fax + 81 3- 5996-8100 Fax + 39 035-232546
NIHON KOHDEN UK LTD

North and South America Trident Court 118, 1 Oakcroft Road
Chessington, Surrey KT9 1BD, UK
Phone + 44 20-8391-6800
NIHON KOHDEN AMERICA, INC. Fax + 44 20-8391-6809
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
Asia
NIHON KOHDEN LATIN AMERICA S.A.S SHANGHAI KOHDEN
Carrera 16 No.93A-36 Of. 802. Bogota D.C., Colombia MEDICAL ELECTRONIC INSTRUMENT CORP.
Phone + 57 1-300-1742 567 Huancheng Bei Road
Fax + 57 1- 300 -1825 Shanghai Comprehensive Industrial Development Zone
Shanghai 201401, China
NIHON KOHDEN DO BRASIL LTDA. Phone + 86 21-5743-6998
Rua Diadema, 89, 1º andar, conjuntos 11 a 17, bairro Mauá Fax + 86 21-5743- 6939
no Município de São Caetano do Sul, Estado de São Paulo
CEP 09580-670, Brasil NIHON KOHDEN SINGAPORE PTE LTD
Phone + 55 11-3044-1700 1 Maritime Square, #10-34 HarbourFront Centre
Fax + 55 11-3044-0463 Singapore 099253
Phone + 65 6376-2210
Fax +65 6376-2264
Europe
NIHON KOHDEN INDIA PVT. LTD.
European Representative 308, Tower A, Spazedge, Sector 47, Sohna Road
Gurgaon-122 002 Haryana, India
NIHON KOHDEN EUROPE GmbH Toll-free +91 1800-103-8182
Raiffeisenstrasse 10, D-61191 Rosbach, Germany
Phone + 91 124-493 -1000
Phone + 49 6003-827- 0
Fax + 91 124-493 -1029
Fax + 49 6003- 827- 599
NIHON KOHDEN MIDDLE EAST FZE

NIHON KOHDEN DEUTSCHLAND GmbH JAFZA One Tower A, 19th floor, Office No. 1912
Raiffeisenstrasse 10, D-61191 Rosbach, Germany
P.O. Box 261516, Jebel Ali Free Zone, Dubai, U.A.E
Phone + 49 6003-827- 0
Phone + 971 4- 884-0080
Fax + 49 6003- 827- 599
Fax + 971 4- 880-0122
NIHON KOHDEN FRANCE SARL NIHON KOHDEN KOREA, INC.

8, rue Francois Delage, 94 230 Cachan, France
5F Miso Bldg.
Phone + 33 1-49-08 -05 -50
890-47 Daechi-dong, Gangnam-gu, Seoul, 135-280 Korea
Fax + 33 1- 49- 08-93 -32
Phone + 82 2-3273-2310
Fax + 82 2-3273 -2352
NIHON KOHDEN IBERICA S.L.
C/Ulises 75A, E-28043 Madrid, Spain
Phone + 34 91-7-161080
Fax + 34 91- 3- 004676
Contact information is accurate as of January 2016. 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.
Model Serial Number
Your Representative

Man0614-905894C CNS6201 PS

Uploaded by

Copyright:

Available Formats

Man0614-905894C CNS6201 PS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Man0614-905894C CNS6201 PS

Uploaded by

Copyright:

Available Formats

PROTOCOL SPECIFICATIONS

First Edition: 12 Mar 2012

If you have any comments or suggestions

WARNING A warning alerts the user to the possible injury or

CAUTION A caution alerts the user to possible injury or

Take necessary measures such as isolation by a

Protocol Specification HL7 Gateway Server 1

The bedside monitor

2 Protocol Specification HL7 Gateway Server

Protocol Specification HL7 Gateway Server 3

1) Query and response of patient information

4 Protocol Specification HL7 Gateway Server

Protocol Specification HL7 Gateway Server 5

External system > [ QRY^R02 ] > HL7 GW (Central Monitor)

(1) Query a patient

(2) Answer a patient

6 Protocol Specification HL7 Gateway Server

1) Query and response of patient information

External system < [ QRY^A19 ] < Bedside monitor

Protocol Specification HL7 Gateway Server 7

External system < [ ORU^R01 ] < Bedside monitor

8 Protocol Specification HL7 Gateway Server

External system > [ QRY^R02 ] > Bedside monitor

(1) Query a patient

(2) Answer a patient

Protocol Specification HL7 Gateway Server 9

TCP/IP socket connections

Port numbers are required individually for the above table.

In-hospital network HL7 gateway (Central Monitor) LS-Net

External system HL7 Gateway (Central Monitor)

Unsolicited transmission of observation values Bedside

Query and response of observation values

10 Protocol Specification HL7 Gateway Server

External system Bedside Monitor

Unsolicited transmission of observation values

Query and response of observation values

Protocol Specification HL7 Gateway Server 11

Every HL7 message ends with <EOM> (End of message).

Patient information (information sent to a monitor)

Patient name: PID-5

*1) It is unsuitable to use DG1-4 information as a doctor name.

Vital sign data (information sent to the other system)

The data indicates instantaneous values.

12 Protocol Specification HL7 Gateway Server

Protocol Specification HL7 Gateway Server 13

RP/#: Whether the field may repeat.

Remarks: Fixed value is described in this column.

14 Protocol Specification HL7 Gateway Server

Protocol Specification HL7 Gateway Server 15

7.1. Message List

General acknowledgement Gateway /

16 Protocol Specification HL7 Gateway Server

A patient basic information query message consists of the following segments.

HL7 G/W / PVM

2 QRD Query Definition R

3 (QRF) Query Filter N

Table 2. Query, original mode message (QRY^A19)

Protocol Specification HL7 Gateway Server 17

MSH-1. Field Separator