IntelliVue Information Center System Release N

HL7 Programmer’s Reference Guide

Part Number 4535 642 64661

Printed in the U.S.A. October 2011
Edition 1

i
 Notice

Proprietary Information
This document contains proprietary information, which is protected by copyright.

Copyright
Copyright © 2011 Koninklijke Philips Electronics N.V.

All Rights Reserved

Manufacturer
Philips Medical Systems
3000 Minuteman Road
Andover, MA 01810
(978) 687-1501
Document Number
4535 642 64661

Warranty Disclaimer
The information contained in this document is subject to change without notice. Philips Medical Systems makes no
warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability
and fitness for a particular purpose. Philips Medical Systems shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing, performance, or use of this material.

ii
Printing History
New editions of this document incorporate all material updated since the previous edition. Update packages may be
issued between editions and contain replacement and additional pages to be merged by a revision date at the bottom of
the page. Pages that are rearranged due to changes on a previous page are not considered revised.

The documentation printing date and part number indicate its current edition. The printing date changes when a new
edition is printed. (Minor corrections and updates that are incorporated at reprint do not cause the date to change.) The
document part number changes when extensive technical changes are incorporated.

First Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . October 2011

Conventions
The manual uses the following conventions for Notes, Cautions, and Warnings.

Note — A Note calls attention to an important point in the text.

Caution A Caution calls attention to a condition or possible situation that could damage or destroy the product or the
user’s work.

Warning A Warning calls attention to a condition or possible situation that could cause injury to the user and/or patient.

iii
iv
 Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Scope and Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Terms and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

HL7 Interface Connection Management and Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Connection Management Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Communication Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
TCP/IP Socket Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
HL7 Low-Level Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
HL7 Message Processing: Socket and Application Layer Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Troubleshooting HL7 Parameter Data Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Configuration and HL7 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Purchased Options and Support Information Screen: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Local General Configuration Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Network Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Configuring the List of Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

System Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Integration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Table of Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Actor Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Actor / Transaction Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
ADT: Communicating Patient Demographics (CPD-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Communicating Patient Demographics (CPD-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Communicating Vital Signs (CVS-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Communicating Vital Signs (CVS-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Communicating Network Time (CNT-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Implementation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Interaction Sequence Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Communicate Patient Demographics (CPD-1) Interaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Contents-1
 Communicate Patient Demographics (CPD-2) Interaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Communicate Vital Signs (CVS-1) Interaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Communicate Vital Signs (CVS-2) Interaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Communicate Network Time (CNT-1) Interaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

HL7 Message Profile Definitions (Categorized by Integration Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
Patient Administration (ADT) Integration Profile (PHC PAM-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
Mapping PHC CPD-1 Transactions to HL7 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
HL7 Message Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Patient Register and Update - HL7 ADT A01, A03, A08 and A47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
HL7 Segment Level Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
MSH Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
EVN Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
PID Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
PV1 Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
MRG Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Sample Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Sample ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions) . . . . . . . . . . . . . . . . . . . . .4-7
Compatibility with Patient Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
IntelliVue Clinical Network Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
MRx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
CareNet/SDN Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
HL7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Mapping Communicate Vital Signs (CVS-1) Transaction to HL7 Messages (Unsolicited Observation Reporting) . . . . . . . 4-9
Overview History of PDI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Unsolicited Messages Interface (CVS-1 Transactions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Auto-Unsolicited On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Aperiodic Parameters, Settings, and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
HL7 Message Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Observation Reporting - HL7 ORU^R0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
HL7 Segment Level Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
MSH Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
PID Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
PV1 Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

2
 OBR Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
OBX Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Acknowledgements and Business Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Acknowledgements Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Sample Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Mapping Communicate Vital Signs (CVS-2) Transaction to HL7 Messages - Query Mode . . . . . . . . . . . . . . . . . . . . . . . 4-14
Overview History of Polling Interface (CVS-2 Transactions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
HL7 Message Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Observation Reporting - HL7 ORU^R04 and QRD / QRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
HL7 Segment Level Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
MSH Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
QRD Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
QRF Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
MSA Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
PID Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
PV1 Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
OBR Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
OBX Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Acknowledgements and Business Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Error Handling (ACK message processing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Sample Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
QRY Message (using above segment definitions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
ORF Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
MDIL Coding Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
SDN Coding Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Sample ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Time Sync Reporting (CNT-1 - Communicate Network Time Transaction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Mapping Communication Network Time Transaction (CNT-1) Transactions to HL7 Messages . . . . . . . . . . . . . . . . . . . . 4-30
HL7 Message Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Communicate Network Time HL7 NMD message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
HL7 Segment Level Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
MSH Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
NCK Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
NMD Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

3
 Shared Segment Profile Definitions (Across Integration Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31
Common MSH Segment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Supporting Details for CVS-1 Transactions (Unsolicited Reporting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Supporting Details for CVS-2 Transactions (Query Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Common PID Segment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Supporting Details for CVS-1 Transactions (Unsolicited Reporting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Supporting Details for CVS-2 Transactions (Query Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Common PV1 Segment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Supporting Details for CVS-1 Transactions (Unsolicited Reporting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Supporting Details for CVS-2 Transactions (Query Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Common OBR Segment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Common OBX Segment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Overview History of OBX Segment Operation (CVS-1 and CVS-2 Transactions) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Observation Field Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Observation Sub-ID (Device Identifier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Parameter Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
OBX Field Message Type Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Parameter Identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Coding Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Parameter Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Parameter List for Possible Coded Values for OBX.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
MRx Device Parameter List for Possible Coded Values for OBX.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
Physiological Calculation Parameter Identifiers for Possible Coded Values for OBX.5 . . . . . . . . . . . . . . . . 4-119
Unit Code Identifiers for Possible Coded Values for OBX.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
OBX Segment Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-130
Supported Data Types (All Integration Profiles) - Non-Atomic Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-132
CE Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
CE Coded Element Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
CX Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
CX Extended Composite ID with Check Digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
EI Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
EI Entity Identifier Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
HD Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135
HD Hierarchic Designator Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135

4
 PL Data Type ................................................................................................................................................................... 4-135
PL Person Location Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135
TS Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
TS Time Stamp Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
XPN Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
XPN Extended Person Name Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
XCN Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-138
XCN Extended Composite ID Number and Name for Persons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-138
MSG Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
MSG Message Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
PT Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
PT Processing Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
VID Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
VID Version Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
Deviations in Messages from HL7 Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-141
International Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-141

Standard HL7 Message Profile Definition Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Standard HL7 Message Profile Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Message Profile Definition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Table definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Message Profile Definition Notation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Cardinality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Relationship Between HL7 Optionality and Conformance Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Relationship Between Usage and Cardinality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Condition Predicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Message Profile Definition - Message Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Segment Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Segment Profile Cardinality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Field Cardinality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Field Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Table Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

5
 Database / XML Table Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Notes Reference Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Field Profile Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
User-Defined and Suggested Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Components and SubComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Parameter Data Interface vs. Clinical Data Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Parameter Label Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
HL7 Data Output Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

6
 Document Overview

1
Introduction

Document Overview
This document covers the Philips IntelliVue Information Center Release (PIIC) N HL7 interface documentation.

Intended Audience
Intended audience is, but are not limited to, individuals being involved in planning, designing and implementing an IntelliVue Information
Center interface integration amongst other Philips products integration profiles.

Scope and Exclusions

This document defines the HL7 Interface of the PIIC Release N product, including the PIIC relevant part of the CareVue Integration Engine
(CIE) Release A.0.

Related Documents
For additional information on how the PIIC processes ADT messages, refer to the CareVue Integration Engine (CIE) Release A.0 guide (part
number 4535 640 30181).

Introduction
1-1
Terms and Acronyms

Terms and Acronyms

Term Meaning

Integration Profile An integration Profile is a method of categorization and a representation of a real-world integration capabilities
that is supported by a set of actors that interact through transactions. See IHE for more details.

Actor Actors are functional integration components of information systems that produce, manage, or act on exchange
of information with other systems. See IHE for more details.

Transaction Transactions are interactions between Actors that exchange the required information through one or
more HL7 messages.

CIE The Clinical Integration Engine aka CareVue Integration Engine (CIE) is a clinical messaging and
interfacing integration engine that features Symphonia 3 from Orion Ltd., a highly flexible and
configurable 3rd party message mapping engine. It supports healthcare and IT interfacing and
messaging standards such as HL7, ASTM, LIS2, TCP/IP sockets, RS-232, and file sharing. CIE also
integrates Philips clinical information system products such as the Philips IntelliVue Information
Center (PIIC) system and the OB TraceVue system into an existing hospital IT infrastructure.

Introduction
1-2
 Overview

26
HL7 Interface Connection Management and Processing

Overview
This chapter describes the connection management installation procedures and details.

Connection Management Details

The following diagram is a high-level architectural drawing of how the PIIC handles both Vital Signs and ADT HL7 messaging.

• Handling of Vital Signs HL7 Patient Data Interface (PDI) unsolicited messages
– Support of RY, ORF, and ACK messages within the PDI messages.
• Handling of Admission/Discharge/Transfer (ADT) messages.
– Support of Admit, Discharge, Transfer, Update, and Patient ID (MRN) Change messages

Communication Layers

The following diagram shows the communication layers involved in the communication between the HL7 Parameter Data Interface and a client
computer.

HL7 Interface Connection Management and Processing

2-1
Connection Management Details

Parameter Data Interface Client Computer

HL7 Message HL7 Message

HL7 low-level protocol HL7 low-level protocol

(message delimiters) (message delimiters)

TCP/IP TCP/IP
Socket Connection Socket Connection

Network Interface Network Interface

(Ethernet) (Ethernet)

IP Network

TCP/IP Socket Connection

Each client uses a TCP/IP socket connection for PDI communication. PDI allows multiple connections, but only one connection at one time to
one particular client machine as identified by IP Address.

If a client machine not configured for any bed in the Config Wizard attempts to connect to an Unsolicited port, the connection will be shut
down immediately by the Parameter Data Interface. A client that is configured for a particular set of beds will receive data for those beds and
no others.

The hostname or IP address of the client systems are set in the Config Wizard (as described in the Information Center System Installation and
Service Guide).

The port number for the unsolicited messages interface as well as the polling interface is specified by a parameter set with the Information
Center configuration utility (Config Wizard). The default PDI port number for the unsolicited messages interface (UMI) is 8000. The default
port number for the polling interface is 9010. The port numbers can be modified in the IIC Config Wizard.

HL7 Interface Connection Management and Processing

2-2
 Connection Management Details

HL7 Low-Level Protocol

TCP/IP is a byte-stream protocol and does not provide messaging boundaries. HL7, which is the standard for the upper-level protocol, is based
on messages but does not provide a mechanism to detect message termination. To mark message boundaries, the Minimal Lower Layer
Protocol is used (as described in HL7 Interface Standards Version 2.x).

Messages are transmitted as follows:

<VT>ddddd<FS><CR>

where:

<VT> is a vertical tab.

ddddd is the HL7 message. Includes only ISO 8859-1 characters (hexadecimal values between 20 and FF, inclusive) and <CR>. Must not
contain other control/non-printable characters. It is the responsibility of the external system not to send any forbidden control characters. There
is no special treatment for forbidden control characters in PDI.

Unwanted symbols must be filtered out at the receiving system.

<FS> is a field separator.

<CR> is a carriage return.

HL7 Interface Connection Management and Processing

2-3
Connection Management Details

HL7 Message Processing: Socket and Application Layer Description

Description of HL7 message processing at the IIC is in the following table. DbServ is the process on the database server or standalone IIC that
sends data to the HL7 clients.

Sending Option Description Process/Steps Behavior

Unsolicited Once connection is established Client connectivity is required before The behavior described in this table assumes that
by client, all HL7 from the set data is sent by source. TCP connection is established and operating
of beds configured for each • DbServ listens on socket. properly.
individual client is sent to A description of the Unsolicited sending option
• Client tries to connect at
configured client hosts by behavior is Open Port and Send.
application level.
DbServ.
• DbServ responds to connection (if
configured).
• DbServ sends data to configured
clients on configured interval.

Startup Behavior:
DbServ starts and waits for connection for each
configured client. ExportLog.txt contains the
following message when client connects.
SDHL7SessMgr::processSocketEvent Connection
request from client 10.40.41.31 accepted

Shutdown Behavior:
HL7 output is discontinued and socket is closed.

HL7 Interface Connection Management and Processing

2-4
 Connection Management Details

Sending Option Description Process/Steps Behavior

Disconnect/Reconnect:
If connection is lost or broken on either the source
or client side, the source will time-out and close
socket; data feed stops.
If a connection is lost the client implements a keep-
alive function at the application level; the client
will try to reconnect if connection is lost. If there is
no keep-alive function implemented, the user must
manually restart the client connection.
When client disconnects the following message
appears in ExportLog.txt.
SDHL7ClientSess::processSocketEvent Socket
connection to client closed with error code 0
(remote host:'10.40.41.31')

Auto Unsolicited Client only has to open socket DbServ automatically sends HL7 data to The behavior described in this table assumes that
that is configured in CGS HL7 configured clients once client opens TCP connection is established and operating
to receive data. socket. properly.
Client only has to listen on socket for A description of the Auto Unsolicited sending
data/activity option behavior is Send.
• Client listens on socket.
• DbServ sends data to all
configured clients.

HL7 Interface Connection Management and Processing

2-5
Connection Management Details

Sending Option Description Process/Steps Behavior

Startup Behavior:
DbServ initiates the connect message with the
client and confirms the client (target port) is open.
When the confirmation that the client port is open,
the DBServ begins to send the HL7 data.
The following message appears in ExportLog.txt
when DbServ starts.
SDHL7SessMgr::execute Socket connection to
10.40.41.31 created, Client thread started
When the client has not opened its socket
ExportLog.txt contains the message,
SDHL7ClientSess::processThreadEvent(1fca3a8)
Cannot connect to HL7 Client 10.40.41.31.
When the client opens its socket ExportLog.txt
contains the message,
SDHL7ClientSess::processThreadEvent(1fca3a8)
HL7 Client 10.40.41.31 connected.

Shutdown Behavior:
DbServ closes the connection. The client socket
should remain open.

Disconnect / Reconnect Behavior:

If client closes the socket DbServ will re-initiate
connection to the client. When the connection to
the client is lost Exportlog.txt contains the
message, SDHL7ClientSess::processSocketEvent
Socket connection to client closed with error code 0
(remote host:'10.40.41.31').

HL7 Interface Connection Management and Processing

2-6
 Connection Management Details

Sending Option Description Process/Steps Behavior

When the client reopens the socket the connect
message appears.
• In Release L and earlier, systems the
reconnect attempts quit in approximately 2
minutes. An error message in Exportlog.txt
reports "30 retries - closing socket".
• In Release M and later, DbServ will
continuously auto attempt to resend to a
configured client/port at each HL7 configured
interval.
Solicited Query Polling (solicited) message Client connectivity required before "The behavior described in this table assumes that
interface data sent by source. TCP connection is established and operating
properly.
Data is transmitted by source • DbServ listens on socket. A description of the Solicited (Query) sending
only on request with every option behavior is Open Port, Listen, and Respond.
• Client tries to connect at
query message generating
application level.
exactly one response message.
• DbServ responds to connection.
• DbServ waits for query request.
• Client requests data.
• DbServ sends requested data.
Startup Behavior:
DbServ starts and waits for connection for each
configured client. Once TCP connect and
application requests connection, and source waits
for HL7 Query requests.

Shutdown Behavior:
HL7 output is discontinued and socket is closed.

Disconnect/Reconnect:
If connection is lost or broken on either the source
or client side the source will time-out and close
socket; data feed stops.

HL7 Interface Connection Management and Processing

2-7
Connection Management Details

Sending Option Description Process/Steps Behavior

If client implements a keep-alive function at the
application level, the client will try to reconnect if
connection is lost.

Troubleshooting HL7 Parameter Data Interface

If problems are encountered HL7 Parameter Data Interface (PDI) on the Information Center system, there are tools and a log file that can be
used to identify the source of the problem. In addition, if the Information Center detects a failure in communication with one or more HL7
clients, a System Message is displayed on the Information Center main screen that states: HL7 Client Disconnected.

Refer to the troubleshooting chapter in the IntelliVue Information Center System Installation and Service Manual, located on the Information
Center documentation CDROM, for details on these tools.

Configuration and HL7 Setup

Config Wizard is a series of screens that permit an IIC support user to configure the IIC System and associated devices. HL7 configuration and
message behavior is determined by various configuration settings that you make during system setup. A description of the required IIC HL7
configuration settings and subsequent processing behavior are included in this appendix.

Purchased Options and Support Information Screen:

The IIC Config Wizard Purchased Options and Support Information screen shows information identifying hardware, software, and purchased

HL7 Interface Connection Management and Processing

2-8
 Connection Management Details

options. In order to support HL7 information exchange you must have the HL7 Purchased Option.

Purchased Options
Changes in Purchased Options can only be made by an authorized Philips Representative

HL7 Export Configuration Enables/disables HL7 export capability

The default is Disable.
• Networked Information Center: Enable or Disable
• Database Server: not applicable
• Local Database Information Center: Enable or Disable
• Information Center Client: not applicable
• Patient Link: Enable or Disable
If you disable the HL7 Export option you must also remove the HL7
Export Interface from the List of Network Devices on the Network
Configuration page.

Local General Configuration Settings Screen

HL7 Interface Connection Management and Processing

2-9
Connection Management Details

The Local General Configuration Settings Config Wizard screen permits HL7 Export Configuration settings that are applicable to
Information Centers.

HL7 Export Configuration Permits selection of HL7 output type

Selection is active if HL7 Export option is enabled on Purchased Options
and Support Information. When selected, the HL7 Configuration dialog
opens with the settings:
• LAN Based Monitors Only: Data originating from LAN monitors
(IntelliVue Patient Monitors) is HL7 output.
• Send Alert Messages: Alert, INOP, and parameter data is HL7
output.
• Send Aperiodic Data: Aperiodic measurements (e.g. noninvasive
blood pressure) is included in HL7 output.
• Send Patient Name: Patient Name is included in the HL7 output. Be
sure that hospital policy permits this feature.
• Target: Database Server host name

HL7 Interface Connection Management and Processing

2-10
 Connection Management Details

Network Configuration Screen

The Network Configuration screen helps the Server identify devices on the LAN. You can add, edit, and remove HL7devices in the List of
Network Devices section of this screen.

HL7 Interface Connection Management and Processing

2-11
Connection Management Details

Configuring the List of Network Devices

The List of network devices section of the Network Configuration screen permits configuration of the network devices connected to the
system.

Button/Selection Description Action/Steps

New 1. Click New to open the Network Devices screen.

2. Select HL7 Export Interface from the list.
3. HL7 client Device Name and IP Address/Host Name are required.
4. Enter (15 character limit) or select a device name in the Device
Name text box.
Adds a new network device to the list
by means of the Network Devices 5. Enter the IP Address of the device being added in the IP Address/
screen. Host Name text box.
6. Click OK in the Network Devices screen to store/save changes.
Up to six HL7 Interface target client devices can be configured. (See the
Equipment Setup Screen.)
If you disable the HL7 Export purchased option, you must also remove the
HL7 Export Interface from the List of Network Devices.

Edit 1. Select the device name you want to change in the List of Network
Changes the information for a device in Devices.
the List of network devices section of
the Network Configuration screen 2. Click Edit to open the device type Network Devices screen.
3. Edit/change the required information, then click OK.

Remove Removes a device from the List of 1. Click the device name you want to remove.
network devices section of the 2. Click Remove.
Network Configuration screen 3. Click OK

The Config Wizard Equipment Setup permits configuration of the HL7 messages.

HL7 Interface Connection Management and Processing

2-12
 Connection Management Details

HL7 Interface Connection Management and Processing

2-13
Connection Management Details

Click the HL7 Configuration button to open the configuration dialog.

Button/Selection Action/Steps
HL7 Target Client Permits selection of the target client from a drop-down list

Sending Options

Periodic Parameter Type • Current - sends the last actual parameter value received from the monitor.
• Averaged - sends the average of measurement since the last data time values were sent.

HL7 Interface Connection Management and Processing

2-14
 Connection Management Details

Button/Selection Action/Steps
Message Type Depending on the option, a numeric code is shown for parameter identification. Not all IntelliVue Clinical
Network numerics are supported with EMFC encoding.
• EMFC Coding (Default) - Extended Medical Function Codes
• MDIL Coding - Medical Device Interface Language
• PDS Compatible - Permits selection of Patient Data Server compatible output
Click the check box to select the option.

• VistA Compatible - Permits selection of Vista-compatible output

Click the check box to select the option.
When you select VistA Compatible, Middle Name and MDIL Coding are automatically selected.

Enhanced Fields Processing ID

• Production
• Debugging
• Test

Middle Name - Permits including patient middle name in message

Encounter Number - Permits including encounter number in message
Alternative ID - Permits selecting alternative patient identification

Send Time Messages Specifies whether a Network Management (NMD) message with the current date/time should be sent periodically
every 60 seconds
When the connection is established, the message is sent to the client.
Click the check box to select the option.

Send Facility ID Specifies whether the Facility ID should be sent with the data
Click the check box to select the option

Post HL7 Disconnect Message Determines if the HL7 Disconnect message appears on the Resting Display
Click the check box to suppress the HL7 Disconnect message on the Resting Display; clear the check box to
show the message when this client disconnects.

Unsolicited

HL7 Interface Connection Management and Processing

2-15
Connection Management Details

Button/Selection Action/Steps
Auto Unsolicited Opens an HL7 Auto Unsolicited Setting dialog which permits automatic sending of HL7 unsolicited data
without a request from the client
By default this check box is clear (Off)
You must notify appropriate Hospital IT staff before you select the Set Auto Unsolicited On check box.

Sending Interval Permits selection of the interval that triggers the HL7 unsolicited data export for periodic parameter
Click the drop down arrow to show the available settings and click the desired selection.
5, 10, 30 (Default), 60

IP Port for Unsolicited Specifies the socket port number through which clients connect to the HL7 unsolicited message interface
This is the port the client connects to that determines whether it will be treated as an unsolicited or a query client.
• 1 to 65536
• 8000 (Default)
Solicited

IP Port for Query Specifies the socket port number through which clients connect to the HL7 polling message interface
• 1 to 65536
• 9010 (Default)

Bed Assignment

Determines the Available Bed - Target Client host name association

Only clients whose host names are found in the list are allowed to connect to the HL7 export interface.
Up to 6 clients of either unsolicited or query types can be associated with a bed label. If a bed is associated with more than one client, the same bed
information will be sent to each client.

HL7 Interface Connection Management and Processing

2-16
 Connection Management Details

Button/Selection Action/Steps
Target Client Lists possible host names
If the Target Client is a CareVue server in duplex mode configuration, use the secondary server name as the
target client.
Click a bed in the Target Client(s) list to select it.

Available Beds Lists available beds

Click a bed label in the Available Beds list to select it.

Assign • Select the host name from the Target Client(s) list.
• Select the beds from the Available Beds list.
Unassign
• Click Assign (or Unassign) button to associate (or disassociate) the client to the bed label.

Edit IDs

Opens an Edit IDs dialog box that permits configuring the SDN ID and the LBN ID.

If exporting HL7 output to CareVue, you must configure Network ID (Id/SDN) and Bed ID (Lbn) settings so
that they are an exact match to those of the CareVue system.
For existing CareVue systems with CMS beds upgrading to IntelliVue Monitors, document the existing CareVue
Unit SDN Bed Map page. Enter the documented settings for each bed label.
For new CareVue systems with IntelliVue Patient Monitors, continue to assign SDN settings for IPMs (id/SDN &
Lbn) in the Unit SDN Bed map page.
• Enter Network ID (Id/SDN) and Bed ID (Lbn) in adjacent text box.
• Click OK to save changes or Cancel.

Bed Label Displays read-only bed label

HL7 Interface Connection Management and Processing

2-17
Connection Management Details

Button/Selection Action/Steps
Network ID (id/SDN) Permits entering the target client bed Network ID value (either 1 or 2) or the target client bed ID from 0- 24. The
default for each is 0.
Bed ID (Lbn)
• Enter Network ID (Id/SDN) in adjacent text box.
• Enter Bed ID (Lbn) in adjacent text box.
• Click OK in the Edit IDs screen to save changes or Cancel.
• Click Apply in the HL7 Configuration screen to save changes without exiting the screen.
• Click OK in the HL7 Configuration screen to save changes and open the next screen, or Cancel.

HL7 Interface Connection Management and Processing

2-18
 Overview

3
System Integration Overview

Overview
This section focuses on the highest level functional view of integration capabilities. It is a description of each Integration Profile and its
associated transactions. In addition, it includes both the structural and dynamic aspects of the system-level integration. The structural
description is most typically represented as a system-level graphical block diagram showing each Philips and non-Philips systems within the
defined scope. The dynamic description is represented using a series of system interaction diagrams showing the HL7 messages being passed
to/from each system within the defined scope

Each Philips Integration Profile is defined by:

• The Integration actors involved

• The specific set of message transactions exchanged by each actor
These requirements are presented in the form of a table of transactions required for each integration actor supporting the Integration Profile.
Integration actors supporting multiple Integration Profiles are required to support all the required transactions of each Integration Profile
supported.

The HL7 Interface of the PIIC allows PIIC to act as a sender and a receiver of HL7 messages (queries and unsolicited updates).

ADT communication is exclusively routed through the CareVue Integration Engine (CIE). The CIE is a separate product, which connects PIIC
to other external hospital information systems.

System Integration Overview

3-1
Overview

Integration Profiles

Each integration profile of this specification is a representation of a real-world capability that is supported by a set of actors that interact
through transactions. Actors are functional components of information systems that produce, manage, or act on categories of information
required for integration in the enterprise. Transactions are interactions between actors that transfer the required information through HL7
messages.

Table of Profiles

Profile Name Description

ADT

Admit Discharge Transfer This integration profile describes the mechanisms that enable this product to report ADT patient
identification data and/or demographics to the Hospital Patient Registration system or other
interested data consumer.

VSR

Vital Signs Reporting This integration profile describes mechanisms that enable this product to communicate
vital signs data to enterprise information systems and interested clients. The typical
data includes periodic physiological data (heart rate, invasive blood pressure,
respiration rate, etc.) for specified monitored patient.

TSR

Time Sync Reporting This integration profile describes mechanisms that enable this product to communicate
network time to enterprise information system and interested clients. The typical data is
a time message (NMD).

Dependency of Integration Profile

There are no dependencies between Integration Profiles.

System Integration Overview

3-2
 Overview

Actors

The section defines an interoperability Actor. Actors and their associated transactions are abstractions of real-world healthcare information
exchange functions. While some of the transactions are traditionally performed by specific product categories (e.g. HIS, EMR, RIS, PACS,
CIS, patient care devices or imaging modalities), we intentionally avoid associating functions or actors with such product categories. Each actor
defines only those functions associated with integrating information systems. The definition of an actor should therefore not be taken as the
complete definition of any product capabilities that might implement it, nor should this Integration Specification itself be taken to
comprehensively describe the architecture of a healthcare information system environment.

Actor Definitions

Actors are functional components of information systems that produce, manage, or act on information associated with operational activities in
the enterprise. Transactions are interactions between actors that transfer the required information through HL7 messages. The following are the
actors defined by this specification and referenced throughout the rest of this document.

Actor Name Description

ADT

Patient Demographics The Patient Demographics Supplier (PDS) actor is the functional role of the ADT system
Supplier (PDS) that supplies patient identification and/or demographics information from this product.
This includes such patient actions as admit, discharge, update, merge, etc.

Patient Demographics The Patient Demographics Client (PDC) actor is the functional role of the ADT
Client (PDC) system that accepts patient identification from a hospital ADT system, or other
product and in the case of this product is only the ICIP product.
Note — This is not done through an HL7 interface and is documented here for
completeness only. It is detailed here as an aid to system integrators so that
incoming patient data connection path can be fully understood.

VSR

System Integration Overview

3-3
Overview

Actor Name Description

Vital Signs Supplier The Vital Signs Supplier (VSS) receives data from medical devices, including
(VSS) those based on proprietary formats, and maps the received patient parameter
data to Vital Signs Client (VSC) providing consistent syntax and semantics.
This actor gathers and transmits patient vital signs data on a configured interval
basis.

Vital Signs Query (VSQ) The Vital Signs Query (VSQ) receives data from medical devices, including
those based on proprietary formats, and upon a query from a Vital Signs Client
(VSC) maps the received patient parameter data to the requesting Vital Signs
Client (VSC) providing consistent syntax and semantics. Proper patient
identification for the data is ensured. The data is sent only when proper queries
are received (e.g. no data is sent without a query received first).

Vital Signs Client (VSC) The Vital Signs Client (VSC) represents the Hospital Information system or any
other consumer of patient vital signs data.

Transactions

Transactions are interactions between actors that transfer the required information through one or more HL7 messages. The following are the
transactions defined by this specification and referenced throughout the rest of this document.

Transaction Name Description

ADT

Communicate Patient The Communicate Patient Demographics Transaction (CPD-1) is used by the Patient
Demographics (CPD-1) Demographics Source actor for communicating Patient Identification and/or
Demographics to the Patient Demographics Client actor.
In a real life example, a PDS (Patient Monitoring) transmits Patient Demographics to a
PDC (ICIP or Hospital ADT system) via the following HL7 messages: ADT A01, A03,
A08, A47, and a combination of A03 / A01 to identify a patient transfer.

System Integration Overview

3-4
 Overview

Transaction Name Description

Communicate Patient The Communicate Patient Demographics Transaction (CPD-2) is used by the
Demographics (CPD-2) Patient Demographics Client to transmit patient demographics information to
the Patient Demographics Source actor.
For example, a PDC (ICIP) transmits patient demographic information to the
PDS (Patient Monitoring product) through direct login and solicitation of
database patient data in the ICIP.
Note — This is not a HL7 transaction. It is documented here, however, to help
system integrators implement the mechanism by which Patient Monitoring
retrieves patient information from another system. It only works with the ICIP
product.

Vital Signs Reporting

Communicate Vital Signs The Communicate Vital Signs (CVS-1) transaction is used by Vital Signs
(CVS-1) Supplier actor to transmit patient vital signs data to enterprise clients on a
configured interval timeframe.
For example, this transaction communicates patient vital signs information
using HL7 ORU^R01 messages on a configured interval.

Query Vital Signs (CVS-2) The Query Vital Signs (CVS-1) transaction is used by Vital Signs Client (VSC)
actor to request patient vital signs data from the Vital Signs Query actor.
This transaction communicates a query request using the HL7 QRF message.
Response is one of 2 possibilities: HL7 ACK message (Acknowledgement
Query Response message) which includes requested vital signs data or HL7
ACK message noting
For example, this transaction communicates patient vital signs information for
the Patient Monitoring product using HL7 message ORU^R04 messages after
receiving a proper query as defined by the HL7 QRY message. A received
faulty HL7 QRY message is responded to with a HL7 ACK message with an
error message

Time Sync Reporting

System Integration Overview

3-5
Overview

Transaction Name Description

Communicate Network The Communicate Network Time (CNT-1) transaction is used by the Vital
Time (CNT-1) Signs Supplier actor and Vital Signs Query actor to transmit current time to a
the Vital Signs Client actor.
For example, this transaction is accomplished by the Patient Monitoring
product HL7 NMD message sent once a minute (if configured) to transmit
current time to clients receiving vital signs data.

Actor / Transaction Diagrams

The following sections diagram the transactions for the actors within the HL7 system for this product.

ADT: Communicating Patient Demographics (CPD-1)

This transaction is for demonstrating how this product transmits patient demographic data.

Patient Demographics
Patient Monitoring product
Supplier (PDS)

Realized by HL7 ADT

Communicate Patient Demographics (CPD-1) A01, A03, A08, A47 and
A01/A03 combination for
patient transfers

Patient Demographics Hospital ADT System / ICIP / Other

Client (PDC) hospital patient system

System Integration Overview

3-6
 Overview

Communicating Patient Demographics (CPD-1)

This transaction is for demonstrating how this product receives patient demographic data

Patient Demographics
Patient Monitoring product
Supplier (PDS)

Realized by direct copy of ICIP internal

Communicate Patient Demographics (CPD-2)
patient demographic data. No HL7
messages are required.

Must be ICIP product. PDS (Patient

Patient Demographics
Monitoring product) can only retrieve
Client (PDC)
patient demographics from ICIP product.

Communicating Vital Signs (CVS-1)

This transaction diagram defines how patient vital signs information is transmitted on an interval basis; unsolicited.

Vital Signs Supplier

Patient Monitoring product
(VSS)

Realized by HL7 ORU^R01 messages

Communicate Vital Signs (CVS-1) which includes patient vital sign data and
alerts. Data is sent on each configured
interval in 2 different modes.

Hospital Information System, ICIP or any

Vital Signs Client (VSC)
other consumer of patient vital signs data.

System Integration Overview

3-7
Overview

Communicating Vital Signs (CVS-2)

This transaction diagram defines how patient vital signs information is transmitted on an interval basis on query.

Vital Signs Supplier

Patient Monitoring product
(VSS)
Realized by HL7 ORF^R04 messages
which includes patient vital sign data
and alerts. Occurs only upon query
HL7 QRY message. HL7 ACK message
Query Vital Signs (CVS-2) Communicate Vital Signs (CVS-2) with error noted is sent upon received
faulty QRY message.
Query is realized by
HL7 QRY message

Hospital Information System, ICIP or any

Vital Signs Client (VSC)
other consumer of patient vital signs data.

Communicating Network Time (CNT-1)

Time Sync Supplier

Patient Monitoring product
(VSS)

Realized by HL7 NMD message sent once

Communicate Network Time (CNT-1)
a minute to configured clients (always the
same as Vital Signs Clients)

Hospital Information System, ICIP or any

Time Sync Client (VSC)
other consumer of patient vital signs data.

System Integration Overview

3-8
 Overview

Implementation Notes

System Integrators have a number of options in implementing actors and transactions in product implementations. The decisions cover four
levels:

For a customer system:

• Identify which actors it could support.

• Identify which transactions can be implemented.
• For each transaction, select which optional features that can be supported.
System Integrators should provide a statement to the customer describing which Integration Profiles, Actors, and Transactions have been
actually implemented.

System Integration Overview

3-9
Overview

Interaction Sequence Overview

Communicate Patient Demographics (CPD-1) Interaction Overview

This diagram shows the Patient Demographic information sequence. It occurs when there is an admit, update, transfer or discharge for a patient.
A merge message is sent when a retrieved patient (done by name) has a different MRN, resulting in a merge.

ADT System PDS PDC This Product

Communicate Patient Demographics (CPD-2)

System Integration Overview

3-10
 Overview

Communicate Patient Demographics (CPD-2) Interaction Overview

This diagram shows the transaction sequence for retrieving patient information from ICIP. This is the only outside source of patient
demographic data. It is not HL7 based but is shown here for system integration purposes only. It occurs upon a Retrieve action within the
Patient Monitoring Admit system.

ICIP System PDS PDC This Product

Communicate Patient Demographics (CPD-2)

System Integration Overview

3-11
Overview

Communicate Vital Signs (CVS-1) Interaction Overview

This diagram shows the transaction sequence for sending patient vital signs (CVS-1). It occurs on configured intervals for clients; usually the
hospital EMR system.

It can be achieved through 2 different modes in the Patient Monitoring HL7:

• Unsolicited
• Auto Unsolicited.

Hospital System /
ICIP / EMR etc. VSC VSS This Product

Communicate Vital Signs (CVS-1)

System Integration Overview

3-12
 Overview

Communicate Vital Signs (CVS-2) Interaction Overview

This diagram shows the transaction sequence for querying for vital signs. A query message is sent and the response is either a HL7 ACK
message indicating a query error or alternatively the vital signs data is sent. Vital signs data is only sent upon a valid query.

ICIP System VSC Communicate Vital Signs (CVS-2) VSS This Product

HL7 QRY message

HL7 ACK message (error)

OR
HL7 ORF^R04 message

System Integration Overview

3-13
Overview

Communicate Network Time (CNT-1) Interaction Overview

This diagram shows the HL7 Network time (NMD) message transaction. It is communicated once a minute to each configured client.

Hospital EMR or
other configured VSC VSS This Product
vital signs client

Communicate Network Time (CNT-1)

System Integration Overview

3-14
 Overview

4
HL7 Message Profile Definitions (Categorized by Integration Profile)

Overview
This section describes the detailed HL7 Message Profile Definitions for each of messages within the scope of this specification. The HL7
Message Profile Definitions are categorized by the Integration Profile categories outlined in the beginning of this document. Each Profile has
the Use Cases, Transactions and Actors that participate within the context of this integration profile scenario.

Patient Administration (ADT) Integration Profile (PHC PAM-1)

The Philips Patient Administration Management Integration Profile consists of HL7 transactions that communicate Patient Identification and/or
Demographics information from a hospital Patient Registration (ADT) system to a Philips system. It is made up of two transactions:
Communicate Patient Demographics (CPD-1) and (CPD-2). CPD-1 is made up of two or more HL7 messages. CPD-2 is a not an HL7
transaction but is included in this document for system integration completeness.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-1
Patient Administration (ADT) Integration Profile (PHC PAM-1)

Mapping PHC CPD-1 Transactions to HL7 Messages

The following table enumerates the messages supporting the CPD-1 transaction.

HL7 Message Source Destination Notes

PHC CPD-1

ADT A.01 Admit Patient PDS PDC

ADT A.03 Discharge Patient PDS PDC

ADT A08 Update Patient PDS PDC

ADT A47 Patient ID Change (MRN) PDS PDC

HL7 Message Profile Definitions

The following section summarizes the message profile definitions for the Communicate Patient Demographics profile.

Patient Register and Update - HL7 ADT A01, A03, A08 and A47

Segment ADT Message Usage Card Chapter DB/XML Notes

MSH Message Header R [1..1] 2

[{SFT}] Software Segment X [0..0] 2

EVN Event Type R [1..1] 3

PID Patient Identification R [1..1] 3

[ PD1 ] Additional Demographics X [0..0] 3

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-2
 Patient Administration (ADT) Integration Profile (PHC PAM-1)

Segment ADT Message Usage Card Chapter DB/XML Notes

MRG Merge RE [0..1] The MRG segment is only

processed in A47 messages.

[{ ROL }] Role X [0..0] 15

[{ NK1 }] Next of Kin / Associated Parties X [0..0] 3

PV1 Patient Visit R [1..1] 3

HL7 Segment Level Profile Definitions

This sub-section describes the profile definition at the Segment level. More specifically, it describes the fields that are required (or optional) for
a particular HL7 Segment Profile. It uses the standard HL7 notations as outlined in HL7 Chapter 2B. In addition, a column is added to denote
additional information (possible values) for each element within the segment. This important for validation / testing purposes.

MSH Segment

See “Common MSH Segment Definition” on page 4-32 for additional details.

EVN Segment

EVN Segment definitions are defined as follows:

SEQ LEN DT Usage Card. Item# Element Name Notes

1 3 ID R [1..1] 0003 Event Type Code Always: Transaction Event Code

2 26 TS R [1..1] Recorded Data/Time Time of transaction. Time Format:

YYY[MM[DD[HH[MM[SS]]]].

3 26 TS X [0..0] Date/Time Planned Event

4 3 IS X [0..0] 0062 Event Reason Code

5 250 XCN X [0..0] 0188 Operator ID

6 26 TS X [0..0] Event Occurred

7 241 HD X [0..0] Event Facility

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-3
Patient Administration (ADT) Integration Profile (PHC PAM-1)

PID Segment

See “Common PID Segment Definition” on page 4-36 for additional details.

PV1 Segment

See “Common PV1 Segment Definition” on page 4-41 for additional details.

MRG Segment

Merge Segment definitions are defined below. MRG segment appears only in A47 messages.

SEQ LEN DT Usage Card. Item# Element Name Notes

1 3 ID R [1..1] 0003 Event Type Code Format: MRNValue^^^^MR

2 26 TS X [0..0] Recorded Data/Time

3 26 TS X [0..0] Date/Time Planned Event

4 3 IS X [0..0] 0062 Event Reason Code

5 250 XCN X [0..0] 0188 Operator ID

6 26 TS X [0..0] Event Occurred

7 241 HD X [0..0] Event Facility

Acknowledgements

Not supported for CPD-1 transactions. ACK messages received are ignored.

Sample Messages

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-4
 Patient Administration (ADT) Integration Profile (PHC PAM-1)

The following sample messages are applicable to CPD-1 transactions.

Action Type Sample Message

Admit A01 MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.133^IP||||20030412235912||ADT^A01|
HP000000000012|P|2.3|1
EVN|A01|20030412235912
PID|||003728598^^^^MR~6FEAE741-950D-11d7-8AEE-0010A4037DE7^^^^JupiterID||Smith^Tom||19790220|M|
PV1||I|CCU^^Bed3

Discharge A03 MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.133^IP||||20030522214503||ADT^A03|

HP000000000021|P|2.3|1
EVN|A01|20030522214503
PID|||215674985^^^^MR~8ABAE741-950D-11d7-8AEE-0010A4037DE7^^^^JupiterID||Doe^Jane^||19110305|F|
PV1||I|ER^^Bed25

Update A08 MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.133^IP||||20030604074654||ADT^A08|

HP000000000032|P|2.3|1
EVN|A08|20030604074654
PID|||009647826^^^^MR~8FEAE555-950D-11d7-8AEE-0010A3967DE7^^^^JupiterID||Lee^Bruce||19660117|M|
PV1||I|ICU^^Bed22

Patient ID (MRN) A47 MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.133^IP||||20040313095011||ADT^A47|

Change HP000000000003|P|2.3|1
EVN|A47|20040313095011
PID|||121314789^^^^MR~8FEAE741-950D-11d7-8AEE-0011B2037DE7^^^^JupiterID||Jones^Pamela||19800310|F|
MRG|18455454^^^^MR

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-5
Patient Administration (ADT) Integration Profile (PHC PAM-1)

Action Type Sample Message

Transfer A03/A01 MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.133^IP||||20031225105011||ADT^A03|
HP000000000003|P|2.3|1
EVN|A03|20031225105011
PID|||121314789^^^^MR~8FEAE741-950D-11d7-8AEE-0011B2037DE7^^^^JupiterID||Jones^Paula||19550310|F
PV1||I|ICU^^Bed1

MSH|^~\&|Philips.PM.IIC.ADT^149.59.185.101^IP||||20031225113544||ADT^A01|
HP000000000006|P|2.3|1
EVN|A01|20031225113544
PID|||121314789^^^^MR~8FEAE741-950D-11d7-8AEE-0010A4037DE7^^^^JupiterID||Jones^Paula||19550310|F|
PV1||I|ICU-South^^Bed2

Sample ACK

Not applicable as acknowledgements received are ignored.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-6
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)
HL7 Parameter Data Interface (PDI) is a software option available for the Information Center (IIC) system. This interface provides a gateway
between a Philips CareNet™ (SDN) network/IntelliVue Clinical Network and a TCP/IP hospital network. Message transmission between PDI
and client systems can take place via the unsolicited messages interface (CVS-1 transactions) or the polling interface (CVS-2 transactions).
These two interfaces are completely independent from each other (although both can be used simultaneously). When working with the
unsolicited messages interface, patient data, bed labels, and vital sign parameter values are distributed to PDI client systems at a time interval
that can be configured (30 seconds is the default), with averaged or the latest (current) values of periodic parameters. When working with the
polling interface, specific patient data, bed labels and vital sign parameters can be requested at any time by PDI client systems. In both cases,
the data format is compliant with the HL7 (Health Level 7) standard version 2.x.

Compatibility with Patient Monitors

IntelliVue Clinical Network Monitors

HL7 output for the M2/M3/M4 bedsides and the IntelliVue Patient Monitors (MP90, MP70, etc.) are available on alerts and INOPs originating
from these monitors, all monitors from M2/M3/M4 beds, monitoring parameters from IntelliVue Patient Monitors (including Vuelink), EEG
measurement and calculation parameters, Essential Gas Module (EGM) and Anesthesia Gas Module (AGM).

PDI uses numeric codes from the Medical Device Interface Language (MDIL) nomenclature to uniquely identify parameter and alert sources. If
EMFC coded parameters are required for HL7 output, there is a configuration option in the Information Center Configuration Wizard to map
the MDIL codes to EMFC codes wherever possible. See "Parameter List" on page 4-5. Refer to the Information Center System Installation and
Service Manual.

MRx

The number of alerts and parameters originating from MRx and available for HL7 export are listed in "MRx Device Parameter List" on page 4-
59.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-7
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

CareNet/SDN Monitors

The CareNet/SDN monitors (CMS, V24, etc.) connected to an Information Center system have limitations with the HL7 export interface. All
SDN alerts and bed parameters displayed with the patient windows of the Information Center are supported and are sent via HL7. Parameters,
from VueLink modules that do not appear at the Information Center display, settings, blood analysis parameters, and physio-calculation
parameters are not available. These require the presence of an M2384 Clinical Data Server in the system in order to be available in HL7 output.

The Vital Signs Reporting Integration Profile consists of two (2) HL7 transactions:

• Communicate Vital Signs (CVS-1)

• Query Vital Signs (CVS-2).
Each communicates patient Vital Signs information from a Patient Monitoring system (this product) to a hospital EMR, Hospital Information
System or other interested client. CVS-1 communicates this automatically on an interval basis. CVS-2 transactions communicate information
only when queried for specific data.

The unsolicited message interface sends only ORU messages to external systems. Also, it does not react to any messages sent to it. Any
messages or data that are sent to the Unsolicited Message Interface are ignored.

HL7 Acknowledgements

The HL7 specification states that the receiving system must acknowledge each message by returning an acknowledgment message back to the
sending system

The returning of acknowledgments does not enhance the reliability of TCP/IP connections because TCP/IP provides error-free transmission.
HL7 PDI treats acknowledgements as optional. Although a receiving system may send acknowledgments, it is recommended that they not send
them. PDI disregards them because they are not required. PDI does not resend messages that have not been acknowledged.

Mapping Communicate Vital Signs (CVS-1) Transaction to HL7 Messages.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-8
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Mapping Communicate Vital Signs (CVS-1) Transaction to HL7 Messages (Unsolicited Observation Reporting)

The following table enumerates the messages supporting the CVS-1 transaction which is Observation Reporting.

HL7 Message Source Destination Notes

VSR CVS-1

ORU^R01 VSS VSC Observation Reporting

Overview History of PDI Operation

The unsolicited observation reporting (ORU) message contains patient data and vital sign parameters, including: patient data (network ID, bed
ID, bed label); all vital sign parameters currently available on the network

One set of messages for each bed is sent at the configured time interval. In the example below:
• PID segment contains patient name and identification number of the patient as entered at the IIC.
• PV1 segment contains bed label, clinical unit name, network ID, and the bed ID. Network ID and bed ID are configured values that have
to be set for each bed in the IIC Config Wizard.
• OBR segment and OBX segment contain observations (may also contain alert information if alert messages are sent). The OBX segment
contains the time stamp for aperiodic parameters.

MSH Message Header

PID Patient Identifier

PV1 Patient Visit

OBR Observations Request

{OBX} Result

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-9
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

When the Information Center system comes online, it waits for client systems to establish TCP/IP socket connections to PDI. Multiple clients
can be online at the same time and may use the unsolicited messages interface and the polling interface at the same time. Data for one bed can
be sent to up to 6 client destinations. The bed to client assignment is configured in the Config Wizard at the Information Center. Refer to the
Information Center System Installation and Service manual.

The unsolicited messages interface and the polling interface use configured TCP/IP port numbers in order to allow external systems to choose
the service they want. PDI receives and only sends current data. Data is not stored, therefore data that has been on the network at an earlier
point in time cannot be retrieved and sent.

Unsolicited Messages Interface (CVS-1 Transactions)

After a connection through the unsolicited messages interface is established, the HL7 Parameter Data Interface performs the following
functions:

• At a configured interval (5, 10, 30 or 60 seconds), transmits periodic parameter data, updates to aperiodic parameters, monitoring status,
alert data from monitoring devices, and patient information to the clients.
The HL7 Parameter Data Interface handles each connection's data independently. As long as the connection exists, PDI sends data. If the
connection is broken or closed in unsolicited mode, the client must re-establish the connection.

Auto-Unsolicited On

If configured in the Information Center Config Wizard, PDI automatically sends HL7 unsolicited data without a request from the client. If the
connection is broken or closed, PDI starts to reestablish the connection and continues to do so until the connection is reestablished or the
system is shut down.

Aperiodic Parameters, Settings, and Configuration

Aperiodic data arrives at the HL7 server at varying, unpredictable intervals. it is sent on change only. If new aperiodic data has arrived at the
end of a sending interval, a set of ORU messages (each of which contains all aperiodic parameters, settings, and configurations from one bed)
is sent.

Some parameters (SpO2 and pTemp) are not always periodic or aperiodic. For example, when a telemetry unit is in SpO2 spot check mode so
that measurements are initiated manually by a clinician rather than an automatic schedule, SpO2 is delivered as aperiodic. When the telemetry
unit is configured for a fixed measurement interval, SpO2 is delivered as a periodic parameter.

HL7 Message Profile Definitions

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-10
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

The following section summarizes the ORU^R01 message profile definition for the Communicate Vital Signs (CVS-1) profile. The message is
for interval based observation reporting.

Note — ORU^R01 messages can be of several configured modes. Normal mode (or default) is not separately noted as this output format is the
base definition. Vista is a 2nd mode of output and this mode requires specific values for fields within the message segments. Other
configured values (patient identifiers, etc) will appear as configured in the HL7 output. Individual segment definitions will note specific values
as necessary.

Observation Reporting - HL7 ORU^R0

Segment ADT Message Usage Card Chapter Notes

MSH Message Header R [1..1] 2

[ { SFT } ] Software Segment X [0..0] 2

EVN Event Type X [0..0] 3

PID Patient Identification R [1..1] 3

[ PD1 ] Additional Demographics X [0..0] 3

MRG Merge X [0..0]

[{ ROL }] Role X [0..0] 15

Next of Kin / Associated

[{ NK1 }] X [0..0] 3
Parties

PV1 Patient Visit R [1..1] 3

[ PV2 ] Patient Visit - Additional Info. X [0..0] 3

[{ ROL }] Role X [0..0] 15

[{ DB1 }] Disability Information X [0..0] 3

[{OBR}] Observation Reporting R [1..1] 7

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-11
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Segment ADT Message Usage Card Chapter Notes

Observation/Result Where n = number of patient parameters and
[{ OBX }] R [1..n] 7
alerts available from monitoring device

HL7 Segment Level Profile Definitions

This sub-section describes the profile definition at the Segment level. More specifically, it describes the fields that are required (or optional) for
a particular HL7 Segment Profile. It uses the standard HL7 notations as outlined in HL7 Chapter 2B. In addition a column is added to denote
additional information (possible values) for each element within the segment. This important for validation / testing purposes.

MSH Segment

See “Common MSH Segment Definition” on page 4-32 for additional details.

PID Segment

See “Common PID Segment Definition” on page 4-36 for additional details.

PV1 Segment

See “Common PV1 Segment Definition” on page 4-41 for additional details.

OBR Segment

See “Common OBR Segment Definition” on page 4-45 for additional details.

OBX Segment

See “Common OBX Segment Definition” on page 4-46 for additional details.

Acknowledgements and Business Logic

Not supported for CVS-1 transactions. ACK messages received are ignored.

Acknowledgements Diagram

Not applicable. Additionally, acknowledgements received are ignored.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-12
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Sample Messages

Unsolicited Observation Reporting (ORU) - Patient data and vital sign parameters. Contains this information:

• patient information distributed on the network (patient name and number)

• bed data (network ID, bed ID, bed label)
• all parameters and device settings available on the network
MSH|^~\&|||||||ORU^R01|HP104220879017992|P|2.x||||||8859/1<CR>
PID|||MRN5733||Smith^John||19550508|M<CR>
PV1||I|^^Doc1&5&1<CR>
OBR|||||||20030110152630<CR>
OBX||NM|0002-4bb8^SpO2^MDIL|0|95|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-5000^Resp^MDIL|0|15|0004-0ae0^rpm^MDIL|||||F<CR>
OBX||NM|0002-4182^HR^MDIL|0|60|0004-0aa0^bpm^MDIL|||||F<CR>
OBX||NM|0002-4a15^ABPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a16^ABPd^MDIL|0|70|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a17^ABPm^MDIL|0|91|0004-0f20^mmHg^MDIL|||||F<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-13
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Mapping Communicate Vital Signs (CVS-2) Transaction to HL7 Messages - Query Mode

The following table enumerates the messages supporting the CVS-1 transaction which is Observation Reporting.

HL7 Message Source Destination Notes

VSR CVS-1

QRD/QRF VSC VSS Query for vital signs data

ORF^R04 VSS VSC Observation Reporting

Overview History of Polling Interface (CVS-2 Transactions)

After a connection through the polling interface is established, PDI transmits data upon request, with every query message generating exactly
one response message.

The response message can only contain data for beds that were assigned to the client performing the query. The maximum query response time
is 20 seconds, assuming that the queries are executed one at a time. If more than one query is executed at a time, the queries will be serialized
and the query response time may increase accordingly. This performance is delivered in parallel to all other services running on the Information
Center.

This section describes the three types (QRY, ORF, and ACK) of HL7 (version 2.x) messages for use with PDI polling interface. The polling
interface is limited to processing these message types in the pattern shown below. Messages are processed one by one with every query

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-14
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

message generating exactly one response message. Periodic parameters are always sent with their current value. Averaged values are not
accessible via the polling interface.

Y)
R
(Q
ge
sa
es
M
ry
ue
Q
PDI polling interface External System

K)
t( r
en F) o
AC
em R
d g (O
le se
ow on
kn sp
ac e
e R
tiv ery
ga u
ne Q
The above picture illustrates how the polling interface operates. The HL7 standard supports many message types, but only three types of
messages are required to support the data sent through the polling interface. The message definitions for the messages used are less restrictive
compared to the original HL7 message definition. This allows the PDI to work even with systems that have a simplified HL7 interface.
Compatibility with HL7 is not reduced through this approach.

The polling interface serves external systems according to a query-response pattern. It processes only three types of messages:

• Query Messages (QRY) - Query results of an observation.

• Observation Reporting Messages (ORF) - Query response. Used to report CareNet data as a reply to a query.
• Acknowledgement Message (ACK) - This message type is only used if the message received from the external system is incorrect or
not supported; it cannot be processed. (The ORF message represents the reply to the corresponding query.)
Messages sent by the PDI Polling interface are either of the type ACK in case of errors or rejects, or of the type ORF for query responses.
Query responses always have the trigger type R04.

If a query asks for data of multiple beds, then the response message contains all data in a single response message. This response message may
become larger than 1MByte in size if data from many beds is requested. Each query returns ALL parameters, settings and device data that is
available for the requested beds. This is due to the fact that the polling interface is not capable of knowing which data has been sent to the
requesting system before. In contrast to the unsolicited messages interface, the polling interface does not store information on which parameters
/ settings have been sent to the external system previously. It is the requesting system's responsibility to check whether any parameter value,
setting or device information has changed since the last query:

• The change of aperiodic parameters can be determined by looking at their time stamp. If the time stamp has changed compared to the last
query, this implies that a new measurement has taken place.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-15
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

• The change of settings can be determined by looking at whether the settings value has changed. If a setting is not sent anymore, the
setting has disappeared (possibly due to the fact that the device it was generated by was turned off) and should be treated as discontinued.
• The existence of devices (coded as CONFIGURATION parameters) can be determined through the existence of this specific parameter
in the message. If a parameter for such a device is not sent anymore on a subsequent query, then the device must be treated as
disappeared.
• The method of sending a NULL value for disappeared settings / devices as with the unsolicited messages interface is not used anymore.

HL7 Message Profile Definitions

The following section summarizes the ORF^R04 message profile definition for the Communicate Vital Signs (CVS-2) profile. The message is
for interval based query mode for vital signs data.

Note — ORF^R04 messages can be of several configured modes. Normal mode (or default) is not separately noted as this output format is the
base definition. Vista is a second mode of output. This mode requires specific values for fields within the message segments. Other configured
values (patient identifiers, etc) will appear as configured in the HL7 output. Individual segment definitions will note specific values as
necessary.

Observation Reporting - HL7 ORU^R04 and QRD / QRF

Segment ADT Message Usage Card Chapter Notes

MSH Message Header R [1..1] 2

[ { SFT } ] Software Segment X [0..0] 2

Message
MSA RE [0..1]
Acknowledgement

QRD Event Type RE [0..1]

QRF Event Type RE [0..1]

EVN Event Type X [0..0] 3

PID Patient Identification R [1..1] 3

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-16
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Segment ADT Message Usage Card Chapter Notes

[ PD1 ] Additional Demographics X [0..0] 3

MRG Merge X [0..0]

[{ ROL }] Role X [0..0] 15

Next of Kin / Associated

[{ NK1 }] X [0..0] 3
Parties

PV1 Patient Visit R [1..1] 3

Patient Visit - Additional

[ PV2 ] X [0..0] 3
Info.

[{ ROL }] Role X [0..0] 15

[{ DB1 }] Disability Information X [0..0] 3

[{OBR}] Observation Reporting R [1..n] 7 Where n = number of beds in the overall message

Observation/Result Where n = number of patient parameters and alerts

[{ OBX }] R [1..n] 7 available from monitoring device for each specific
bed

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-17
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

HL7 Segment Level Profile Definitions

This sub-section describes the profile definition at the Segment level. More specifically, it describes the fields that are required (or optional) for
a particular HL7 Segment Profile. It uses the standard HL7 notations as outlined in HL7 Chapter 2B. In addition a column is added to denote
additional information (possible values) for each element within the segment. This important for validation / testing purposes.

MSH Segment

See “Common MSH Segment Definition” on page 4-32 for additional details.

QRD Segment

The following defines the QRD Segment used in CVS-2 transactions.

SEQ LEN DT Usage Card. Field Name Message Profile: Values

1 26 TS R [1..1] Date / Time of Query CVS-2: Query date/time from received query
2 1 ID R [1..1] Query format code CVS-2: R (record oriented format)
3 1 ID R [1..1] Query priority CVS-2: I (immediate)
4 10 ST R [1..1] Query ID: Some unique CVS-2: Query unique identifier from received query
identifier
5 1 ID X [0..0] Deferred response type
6 26 TS X [0..0] Deferred response date / time
7 10 CQ X [0..0] Quantity limited request: should CVS-2: Always empty (no limit)
be empty for NO LIMIT
8 60 XCN R [1..1] Who subject filter CVS-2: Filter See Section 3.2.2.3.2.1
9 60 CE R [1..1] What subject filter CVS-2: RES (query + response)
10 60 CE X [0..0] What department code
11 20 CM X [0..0] What data code value qualifier
12 10 ID X [0..0] Query results level (ignored)

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-18
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

PDI uses the following fields within the QRD segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

1 26 TS R [1..1] Date / Time of Query Given value from incoming message is used for response
message.
2 1 ID R [1..1] Query format code Must always be R for record-oriented
3 1 ID R [1..1] Query priority Must always be I for intermediate

4 10 ST R [1..1] Query ID: Some unique Unique Identifier

identifier

7 10 CQ X [0..0] Quantity limited request: should Almost empty for NO LIMIT

be empty for NO LIMIT

8 60 XCN R [1..1] Who subject filter HL7PDI uses only the beginning 3 components of this field.
The format is:
<ID number>^<family name>^<given name>

With an incoming query, there are three possibilities for a

match:
• ID, the family name and given name match
• The ID matches and no family name or given name was
set
• Family name and given name match an no ID was set

9 60 CE R [1..1] What subject filter Must be RES for results in query and in response

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-19
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Processing Rules:

• Query date/time is ignored by the PDI polling interface, but the given value is sent back to the sender of the query in the query response.
The external system should supply this value in order to be HL7 compliant.
• Queries must always have query format code "R" and query priority "I". If these fields are empty or have a different content this is
treated as an error condition.
• Query ID must be non-null and not empty. It is not processed but sent back to the query sender in the query response. PDI does not
control whether control IDs are unique.
• The quantity in Quantity limited requests is ignored

Examples:

This message requests data from the patient with the medical record number of MRN331:
MSH|^~\&|||||20041007135100||QRY^R02|HP8565435191|P|2.x.1
QRD|20041007135100|R|I|Q839572||||MRN331|RES
QRF|MON
This message requests data from the patient with the medical record number MRN331 and from the patient with the medical record number
R1443:
MSH|^~\&|||||20041007135100||QRY^R02|HP8565435191|P|2.x.1
QRD|20041007135100|R|I|Q839572||||MRN331~R1443|RES
QRF|MON
This message requests data from the patients Roberta Adams and Thomas Miller:
MSH|^~\&|||||20041007135100||QRY^R02|HP8565435191|P|2.x.1
QRD|20041007135100|R|I|Q839572||||^Adams^Roberta~^Miller^Thomas|RES
QRF|MON

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-20
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

QRF Segment

The following defines the QRF Segment used in CVS-2 transactions.

SEQ LEN DT Usage Card. Field Name Message Profile: Values

1 20 ST R [1..1] Where subject filter CVS-2: MON
2 26 TS X [1..1] When data start date / time
3 26 TS X [1..1] When data end date / time
4 60 ST X [1..1] What user qualifier
5 1000 ST R [1..1] Other query subject filter CVS-2: Bed list to query upon
6 12 ID X [1..1] Which date / time qualifier
7 12 ID X [1..1] Which date / time status qualifier
8 12 ID X [1..1] Date / Time selection qualifier
9 60 TQ X [1..1] When Quantity / Timing qualifier

PDI uses the following fields within the QRF segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

1 20 ST R [1..1] Where subject filter Must always be MON for monitoring data in
queries and in responses
5 1000 ST R [1..1] Other query subject filter Specifies list with beds of interest

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-21
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Processing Rules:

• All qualifiers except for the Other query subject filter are ignored on input and left empty in the query response.
• The Other query subject filter consists of a list of repeated string fields, each of which represents a bed location. Bed locations may either
be specified by the bed label that is assigned to the bed or by a coding scheme that uses a bed ID and a network ID: *<network ID> -
<bed ID>

Specifications by bed label and by bed ID and network ID may be mixed in a single query. Bed ID and network ID uniquely identify the
bed connected. If the bed location list is empty, the query is for all locations. Alternatively, the whole QRF segment can be omitted in
this case. An example of such a bed list follows: *1-11~ICU 12~CCU 4~*2-6. If a bed matches multiple criteria it is included in the
response only once.

MSA Segment

The following defines the MSA Segment used in CVS-2 transactions. This segment is used only to respond to faulted query messages received.

Note — The (ERR) Segment (optional in an ACK message) is never sent by this product.

SEQ LEN DT Usage Card. Field Name Message Profile: Values

1 2 ID R [1..1] Acknowledgement code All: AA (accept), or AE (error)
2 20 ST R [1..1] Message Control ID All: Message ID from query message received
3 80 ST R [1..1] Text Message All: only if MSA.1 = AE; “Incorrect message syntax” string
included.
4 15 NM X [0..0] Expected Sequence Num
5 1 ID X [0..0] Delayed Ack Type
6 250 CE X [0..0] Error Condition

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-22
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

PDI uses the following fields within the QRF segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

1 2 ID R [1..1] Acknowledgement code • AA: Application Accept (positive acknowledgement)
• AE: Application Error (negative acknowledgement)

2 20 ST R [1..1] Message Control ID Contains the message control ID that came with the requesting
QRY query message. This allows the client to map a response
message to the corresponding request.
3 80 ST R [1..1] Text Message In case of errors or rejects, the text message contains a textual
description of the reason for this event. Typical texts would be:
• “Message type not supported”
• “Incorrect message syntax”

Examples:

MSA|AE|ID0815|Error: In segment [QRD],attrib.[Query Format],Illegal Code[KR]!<CR>

MSA|AA|HP8565435191<CR>

PID Segment

See “Common PID Segment Definition” on page 4-36 for additional details.

PV1 Segment

See “Common PV1 Segment Definition” on page 4-41 for additional details.

OBR Segment

See “Common OBR Segment Definition” on page 4-45 for additional details.

OBX Segment

See “Common OBX Segment Definition” on page 4-46 for additional details.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-23
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Acknowledgements and Business Logic

The acknowledgement message (ACK) is only used if the message received is incorrect or not supported and can therefore not be processed. It
has the following structure:
MSH Message Header
MSA Message Acknowledgement

where:
• The MSA segment contains an acknowledgement code and the corresponding message control ID along with an error string in case of an
error.

Example
MSH|^~\&|HP HL7-CE|BAYKPW|||198808181126||ACK^|MSG00002|P|2.x
MSA|AE|MSG00001|Incorrect Message Syntax

The ERR segment (optional in an ACK message) is never sent by PDI.

Error Handling (ACK message processing)

The PDI polling interface implements the following error handling rules.

Error Error Handling

Attempt to connect to wrong TCP/IP socket Connection refused

External system sends HL7 message with incorrect low-level protocol Message is ignored - no further reaction

External system sends HL7 message with incorrect message syntax Message is either ignored (if it is not identifiable as anything like
HL7) or an ACK message with a negative acknowledgement is sent
back

External system sends HL7 message with unsupported message type ACK message with a negative acknowledgement is sent back that
contains description of the error

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-24
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

Sample Messages

QRY Message (using above segment definitions)

The query message (QRY) is used to request current parameter data. It triggers the event R02 (query for results of an observation). QRY
messages have the following structure
MSH Message Header
QRD Query definition
[QRF] Query filter
where:
• The MSH segment contains an acknowledgement code and the corresponding message control ID along with an error string in case of an
error.
• The QRD segment specifies the data and time of the query, the format code, the priority and some query filter information. Most
important is the Who Subject, where data for specific patient information can be requested. See “QRD Segment” on page 4-18.
• The QRF segment specifies the current data from the requested beds.

Examples:

This message requests data from the patient James Miller who has a medical record number of MRN999:
MSH|^~\&|||||20041007135100||QRY^R02|HP8565435191|P|2.x.1
QRD|20041007135100|R|I|Q839572||||MRN999^Miller^James|RES
QRF|MON

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-25
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

ORF Message

The query response message (ORF) is used to report parameter data as a reply to a query. ORF messages have the following structure:
MSH Message Header
MSA Message Acknowledgement
QRD Query definition (from QRY message)
[QRF] Query filter (from QRY message)
{
PID Patient Identification
PV1 Patient Visit
{OBRObservations Report ID
{OBX} Result
}
}
}
where:
• The MSA segment contains an acknowledgement code and the corresponding message control ID along with an error string in case of an
error.
• The QRD segment repeats the corresponding query definition.
• The QRF segment repeats the corresponding query filter definition.
• The PID segment contains the patient ID and name.
• The PV1 segment specifies the bed to be accessed along with the patient class if the query refers to current data from the CareNet.
• The OBR segment contains the timestamp (in ISO format) of the OBX parameters that follow.
• The QBX segment contains the result for the timestamp specified in the preceding OBR segment.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-26
 Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

MDIL Coding Example

MSH|^~\&|||||||ORF^R04|HP104220574117863|P|2.x||||||8859/1<CR>
MSA|AA|HP8565435191<CR>
QRD|20020305121942|R|I|Q839572|||||RES<CR>
QRF|MON||||Bed1~Bed2~*1-12<CR>
PID|||123148||Smith^Robert||19680125|M<CR>
PV1||I|^^Bed2&0&0<CR>
OBR|||||||20030110143541<CR>
OBX||ST|0002-f887^Model^MDIL|0|Monitoring Data||||||F||CONFIGURATION<CR>
OBX||ST|0002-d006^EctSta^MDIL|0|""||||||F<CR>
OBX||ST|0002-d007^RhySta^MDIL|0|SV Rhythm||||||F<CR>
OBX||NM|0002-4bb8^SpO2^MDIL|0|95|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-0301^ST-I^MDIL|0|-1.3|0004-0512^mm^MDIL|||||F<CR>
OBX||NM|0002-0302^ST-II^MDIL|0|-0.8|0004-0512^mm^MDIL|||||F<CR>
OBX||NM|0002-4182^HR^MDIL|0|60|0004-0aa0^bpm^MDIL|||||F<CR>
OBX||NM|0002-4a15^ABPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a16^ABPd^MDIL|0|70|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a17^ABPm^MDIL|0|91|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4261^PVC^MDIL|0|0|0004-0aa0^bpm^MDIL|||||F<CR>
OBX||NM|0002-4a05^NBPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030110052800<CR>
OBX||NM|0002-4a06^NBPd^MDIL|0|80|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030110052800<CR>
OBX||NM|0002-4a07^NBPm^MDIL|0|90|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030110052800<CR>
OBX||ST|0402-f8f5^sMode^MDIL|0|DEMO||||||F||SETTING<CR>
OBX||ST|0002-f887^Model^MDIL|4|VueLink 1||||||F||CONFIGURATION<CR>
OBX||NM|0002-5012^awRR^MDIL|4|46|0004-0ae0^rpm^MDIL|||||F<CR>
OBX||NM|0002-e014^Tblood^MDIL|4|44.7|0004-17a0^°C^MDIL|||||F<CR>
OBX||NM|0002-513c^TV^MDIL|4|0.83|0004-0640^l^MDIL|||||F<CR>
OBX||NM|0002-50b0^etCO2^MDIL|4|7.08|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-538c^etAGT^MDIL|4|29.6|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-5390^inAGT^MDIL|4|29.6|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-50ba^imCO2^MDIL|4|7.1|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-5109^PIP^MDIL|4|42|0004-0f40^cmH2O^MDIL|||||F<CR>
OBX||NM|0002-51a8^PEEP^MDIL|4|1.6|0004-0f40^cmH2O^MDIL|||||F<CR>
OBX||NM|0002-f093^Weight^MDIL|4|25.0|0004-06c3^kg^MDIL|||||F||APERIODIC|20030110143000<CR>
OBX||NM|0402-5012^sAWRR^MDIL|4|34|0004-0ae0^rpm^MDIL|||||F||SETTING<CR>
OBX||NM|0402-513c^sTV^MDIL|4|0.34|0004-0640^l^MDIL|||||F||SETTING<CR>
<FS>
<CR>

SDN Coding Example

MSH|^~\&|||||||ORF^R04|HP856522134|P|2.x

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-27
Vital Signs Reporting Integration Profile (CVS - Communicate Vital Signs Transactions)

MSA|AA|HP8565435191
QRD|19970731145557|R|I|Q839572|||||RES
QRF|MON||||Bed1~Bed2~*1-12
PID|||37584-23||John Smith
PV1||I|^^Bed2&0&0
OBR|||||||19970731145558
OBX||ST|33040^Model^SDN|0|SDN Broadcast||||||F||CONFIGURATION
OBX||NM|96^AWRR^SDN|0|168||||||F
OBX||NM|208^PIP^SDN|0|38||||||F
OBX||ST|32920^sMode^SDN|0|MONITORING||||||F||SETTING
OBX||ST|33040^Model^SDN|1|Hamilton Veolar||||||F||CONFIGURATION
OBX||NM|132^Tblood^SDN|1|31.2|C|||||F
OBX||NM|116^IMCO2^SDN|1|10.0|%|||||F
OBX||NM|65^ABP S^SDN|1|103|mmHg|0^0||||F
OBX||NM|66^ABP D^SDN|1|50|mmHg|0^0||||F
OBX||NM|67^ABP M^SDN|1|103|mmHg|0^0||||F
OBX||NM|112^ETCO2^SDN|1|10.00|%|||||F
OBX||NM|1105^UVP S^SDN|1|100.0|mmHg|0.0^0.0||||F
OBX||NM|1106^UVP D^SDN|1|100.0|mmHg|0.0^0.0||||F
OBX||NM|1107^UVP M^SDN|1|100.0|mmHg|0.0^0.0||||F
OBX||NM|516^Tskin^SDN|1|34.5|C|||||F
OBX||NM|1025^P5 S^SDN|1|200.0|mmHg|100.0^180.0||||F||APERIODIC|19970731144605
OBX||NM|1026^P5 D^SDN|1|100.0|mmHg|20.0^95.0||||F||APERIODIC|19970731144605
OBX||NM|1027^P5 M^SDN|1|150.0|mmHg|100.0^170.0||||F||APERIODIC|19970731144605
OBX||NM|1728^Pmean^SDN|1|1.0|cmH2O|||||F
OBX||NM|1720^MV^SDN|1|18.80|l/min|||||F
OBX||ST|33216^sGasPr^SDN|1|Y-PIECE||||||F||SETTING
OBX||ST|33220^sO2Pr^SDN|1|Y-PIECE||||||F||SETTING
OBX||ST|33224^sCircl^SDN|1|NON REBR||||||F||SETTING
OBX||NM|32776^sTV^SDN|1|1.05|l|||||F||SETTING
OBX||ST|33040^Model^SDN|64|DAP Internal Source||||||F||CONFIGURATION
OBX||ST|136^VPB^SDN|64|Non-paced mode||||||F
PID|||37234-78||Peter Miller
PV1||I|^^&12&1
OBR|||||||19970731145558
OBX||ST|33040^Model^SDN|0|SDN Broadcast||||||F||CONFIGURATION
OBX||NM|96^AWRR^SDN|0|168||||||F
OBX||NM|208^PIP^SDN|0|38||||||F

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-28
 Time Sync Reporting (CNT-1 - Communicate Network Time Transaction)

OBX||ST|32920^sMode^SDN|0|MONITORING||||||F||SETTING
OBX||NM|89^NBP S^SDN|0|140||||||F||APERIODIC|19970731144607
OBX||NM|90^NBP D^SDN|0|80||||||F||APERIODIC|19970731144607
OBX||NM|91^NBP M^SDN|0|110||||||F||APERIODIC|19970731144607
OBX||ST|33040^Model^SDN|64|DAP Internal Source||||||F||CONFIGURATION
OBX||ST|136^VPB^SDN|64|Non-paced mode||||||F

The SDN Coding example message is a response to the previous QRY message example. In case data for a requested bed does not appear in the
ORF response message (i.e. Bed1 in the example) the bedside monitor might be switched off and not delivering data, or the bed might not be
assigned to the client that sent the query. The bed > client assignment is configured in the Information Center Configuration Wizard. Refer to
the IntelliVue Information Center Installation and Service Manual.

The inclusion of a PV1 segment in an ORF message does not conform to the HL7 definition. The inclusion of the PV1 is required as it contains
the identification of the bed. As there is no safe way to identify data through patient name or number, the bed identification is absolutely crucial
and cannot be omitted.

Sample ACK

Example shows error message:

MSA|AE|ID0815|Error: In segment [QRD],attrib.[Query Format],Illegal Code[KR]!<CR>
MSA|AA|HP8565435191<CR>

Time Sync Reporting (CNT-1 - Communicate Network Time Transaction)

This profile consists of time sync messages (if configured) that will be sent for each client. If the Send System time option is set for each
respective client, then the transaction is sent to each configured client.

The network management (NMD) message distributes the current date and time setting of the PDI system. Time information is obtained from
the IIC system.

Syntax:
MSH message header
NCK system clock
[NTE] note/comment
• The NCK segment specifies the time used by the PDI in ISO format (year month day hour minute second).
• The NTE segment is not used.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-29
Time Sync Reporting (CNT-1 - Communicate Network Time Transaction)

Time information is sent in network management messages immediately upon connection startup and every 60 seconds thereafter. The time
information used is configured at the IntelliVue Information Center (IIC); transmission of time information can be turned off by clearing the
Send time Messages checkbox.

Note — These are configuration parameters that are set in IIC Config Wizard. Refer to the IntelliVue Information Center Installation and
Service Guide for detailed information.

Mapping Communication Network Time Transaction (CNT-1) Transactions to HL7 Messages

The following table enumerates the messages supporting the CNT-1 (Communicate Network Time) transaction which is available as an option
for all other transactions except CVS-2 (query mode).

HL7 Message Source Destination Notes

CNT-1

NMD VSS VSC Sent the Time

Sync message

HL7 Message Profile Definitions

The following section summarizes the Network Management (NMD) message profile definition for the Communicate Network Time (CNT-1)
transaction. The message is sent each minute for any configured client.

Communicate Network Time HL7 NMD message

Segment NMD Message Usage Card Chapter Notes

MSH Message Header R [1..1] 2

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-30
 Shared Segment Profile Definitions (Across Integration Profiles)

Segment NMD Message Usage Card Chapter Notes

[{SFT}] Software Segment X [0..0] 2
NCK System Clock R [1..1]

HL7 Segment Level Profile Definitions

This sub-section describes the profile definition at the Segment level. More specifically, it describes the fields that are required (or optional) for
a particular HL7 Segment Profile. It uses the standard HL7 notations as outlined in HL7 Chapter 2B. In addition a column is added to denote
additional information (possible values) for each element within the segment. This important for validation / testing purposes.

MSH Segment

See “Common MSH Segment Definition” on page 4-32 for additional details.

NCK Segment

The following defines the NCK Segment used in CNT-1 transactions.

SEQ LEN DT Usage Card. Field Name Message Profile: Values

1 26 TS R [1..1] System Date / Time Current Time

NMD Example:

The time is sent in ISO format (year month day hour minute second).
MSH|^~\&|||||||NMD|HP104220882017993|P|2.x||||||8859/1<CR>
NCK|20030110152700<CR>

Shared Segment Profile Definitions (Across Integration Profiles)

Configuration options exist for default output or Vista and also to set particular patient identifier fields. These are separately noted in the
following tables in order to capture output that is as-configured.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-31
Shared Segment Profile Definitions (Across Integration Profiles)

Common MSH Segment Definition

The following MSH Segment definition is common across all integration profiles. Specific values for each integration profile are specified and
common values are also noted. Required values not mentioned are system-defined at run time.

SEQ LEN DT Usage Card. Item# Item # Element Name Message Profile: Values
1 1 ST R [1..1] 00001 Field Separator All: | (ASCII 124)

2 4 ST R [1..1] 00002 Encoding Chars All: ^~\& (ASCII 94, 126, 92,
and 38, respectively)

3 227 HD RE [0..1] 0361 00003 Sending CPD-1: Philips.PIC.ADT^IP of

Application network card^IP
CVS-1, CVS-2 (Vista): MDHL-
IN

4 227 HD RE [0..1] 0362 00004 Sending Facility CVS-1, CVS-2 (Vista): Vista also
supports Institution ID set in
Config Wizard

5 227 HD RE [0..1] 0361 00005 Receiving App CVS-1, CVS-2 (Vista): MDHL-
OUT Not used otherwise

6 227 HD RE [0..1] 0362 00006 Receiving Facility CVS-1, CVS-2 (Vista): Vista
Not used otherwise

7 26 TS R [1..1] 00007 Date/Time of Msg All: [MM[DD[HH[MM[SS]]]]

8 40 ST X [0..0] 00008 Security

9 15 R [1..1] 00009 Message Type CPD-1: ADT^EventTypeNumber

MSG CVS-1: ORU^R01
CVS-2: ORF^R04

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-32
 Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. Item# Item # Element Name Message Profile: Values
10 20 ST R [1..1] 00010 Message Control Id CPD-1 and CVS-1, CVS-2: HP
followed by unique alphanumeric
ID

11 3 PT R [1..1] 00011 Processing Id All: P, D, T

Set in IIC Config Wizard

12 60 VID R [1..1] 00012 Version ID CPD-1: 2.3

CVS-1 (default): 2.3
CVS-1, CVS-2 (Vista): 2.4

13 15 NM R [1..1] 00013 Sequence Number

14 180 ST X [0..0] 00014 Continuation

Pointer

15 2 ID X [0..0] 0155 00015 Accept Ack Type

16 2 ID X [0..0] 0155 00016 Application

AckType

17 3 ID X [0..0] 0399 00017 Country Code

18 16 ID R [1..1] 0211 00692 Character Set All: 8859/1

19 250 CE X [0..0] 00693 Principal Lang of

Msg

20 20 ID X [0..0] 0356 01317 Alt Char Set

Scheme

21 427 EI X [0..0] 01598 Msg

MessageSetting
Identifier

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-33
Shared Segment Profile Definitions (Across Integration Profiles)

Supporting Details for CVS-1 Transactions (Unsolicited Reporting)

PDI uses the following fields within the MSH segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

1 1 ST R [1..1] Field Separator Contains the separator between segment ID and the first
real field. Defines the characters to be used as separators
for the rest of the message.

2 4 ST R [1..1] Encoding Characters Contains the component separator, repetition separator,

escape character and subcomponent separator.

9 15 R [1..1] Message Type Either NMD for network time messages or ORU for
MSG parameter reporting messages.

10 20 ST R [1..1] Message Control ID Unique alphanumeric ID that identifies each Control ID

message sent.

11 3 PT R [1..1] Processing ID Always set to P (for Production).

12 60 VID R [1..1] Version ID Version of the HL7 protocol transmitted. Always set to
2.3 but the output is usable with systems expecting
versions 2.3 to 2.5. See “Deviations from HL7 Standard”,
page 1-4.

18 16 ID R [1..1] Character Set Always 8859/1

Example:
MSH|^~\&|||||||NMD|HP104220882017993|P|2.x||||||8859/1<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-34
 Shared Segment Profile Definitions (Across Integration Profiles)

Supporting Details for CVS-2 Transactions (Query Mode)

PDI uses the following fields within the MSH segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

1 1 ST R [1..1] Field Separator Contains the separator between the segment ID and the first
real field; defines the characters to be used as separators for
the rest of the message.

2 4 ST R [1..1] Encoding Characters Contains the component separator, repetition separator, escape
character, and subcomponent separator.

7 26 TS R [1..1] Date/Time of Message Ignored in incoming messages; sent with outgoing messages.

9 15 R [1..1] Message Type Either QRY for query messages or ORF for query response
MSG messages or ACK in case of an error.

10 20 ST R [1..1] Message Control ID Unique alphanumeric ID that identifies each Control ID

message sent. Required in incoming QRY messages; sent with
outgoing ORF messages.

11 3 PT R [1..1] Processing ID Ignored in incoming messages. Always set to P (for

Production) for outgoing messages.

12 60 VID R [1..1] Version ID Ignored in incoming messages. Version of the HL7 protocol
transmitted. Always set to 2.x for outgoing messages.

18 16 ID R [1..1] Character Set Ignored in incoming messages. For outgoing messages always
8859/1 (for the ISO 8859-1 character set)

Example:
MSH|^~\&|||||||ORF^R04|HP8565435191|P|2.x<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-35
Shared Segment Profile Definitions (Across Integration Profiles)

Common PID Segment Definition

The following PID Segment definition is common across all integration profiles. Specific values for each integration profile are specified and
common values are also noted.

SEQ LEN DT Usage Card. TBL# Item # Element Name Message Profile: Values
1 4 SI X [0..0] 00104 Set ID - PID

2 20 CX X [0..0] 00105 Patient ID

3 250 CX R [1..6] 00106 Patient Identifier CPD-1: MRNValue^^^^MR~

List
PatientIdentifierGuid^^^^Jupiter
Id

CVS-1, CVS-2:

MRNValue^^^^MR~VisitNumb
erValue^^^^VN~AlternateIDVa
lue^^^^U

4 20 CX X [0..0] 00107 Alt Patient ID - PID

5 250 XPN R [1..1] 00108 Patient Name CPD-1, CVS-1, CVS-2 :

LastName^FirstName^MiddleN
ame

6 250 XPN X [0..0] 00109 Mother’s Maiden

Name
7 26 TS R [0..1] 00110 Date/Time of Birth CPD-1, CVS-1, CVS-2:
YYYY[MM[DD]]

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-36
 Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. TBL# Item # Element Name Message Profile: Values
8 1 IS R [0..1] 01 00111 Administrative Sex
9 250 XPN X [0..0] 00112 Patient Alias
10 250 CE X [0..0] 0005 00113 Race
11 250 XAD X [0..0] 00114 Patient Address
12 4 IS X [0..0] 289 00115 County Code
13 250 XTN X [0..0] 00116 Phone Number - Home
14 250 XTN X [0..0] 00117 Phone Num - Business
15 250 CE X [0..0] 0296 00118 Primary Language
16 250 CE X [0..0] 0002 00119 Marital Status
17 250 CE X [0..0] 0006 00120 Religion
18 250 CX X [0..0] 00121 Patient Acct. Number
19 16 ST X [0..0] 00122 SSN Number - Patient
20 25 DLN X [0..0] 00123 Driver's License
Number
21 250 CX X [0..0] 00124 Mother's Identifier
22 250 CE X [0..0] 0189 00125 Ethnic Group
23 250 ST X [0..0] 00126 Birth Place
24 1 ID X [0..0] 0136 00127 Mult. Birth Indicator
25 2 NM X [0..0] 00128 Birth Order
26 250 CE X [0..0] 0171 00129 Citizenship
27 250 CE X [0..0] 0172 00130 Vet Military Status
28 250 CE X [0..0] 0212 00739 Nationality

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-37
Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. TBL# Item # Element Name Message Profile: Values
29 26 TS X [0..0] 00740 Patient Death Date/
Time
30 1 ID X [0..0] 0136 00741 Patient Death Indicator
31 1 ID X [0..0] 0136 01535 Identity Unknown
Indicator
32 20 IS X [0..0] 0445 01536 Identity Reliability
Code
33 26 TS X [0..0] 01537 Last Update Date/
Time
34 241 HD X [0..0] 01538 Last Update Facility
35 250 CE X [0..0] 0446 01539 Species Code
36 250 CE X [0..0] 0447 01540 Breed Code
37 80 ST X [0..0] 01541 Strain
38 250 CE X [0..0] 0429 01542 Production Class Code
39 250 CWE X [0..0] 0171 01840 Tribal Citizenship

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-38
 Shared Segment Profile Definitions (Across Integration Profiles)

Supporting Details for CVS-1 Transactions (Unsolicited Reporting)

PDI uses the following fields within the PID segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

3 250 CX R [1..6] Patient Identifier List Contains the patient ID as entered at the Information Center
(IIC)
Can contain any printable character; if no data is entered at the
IIC the field contains NULL value (“”).
Config Wizard may also specify Visit Number and Alternate ID
as additional Patient Identifiers.
For example,
12345^^^^MR~23456^^^^VN~34567^^^^U
-where MR is MRN, VN is Visit Number, and U is Alternate ID

5 250 XPN R [1..1] Patient Name Contains the patient name as entered at the Information Center.
Format depends on the configured Message Type. Refer to the
IIC Installation and Service Guide.
Config Wizard may optionally include Middle Name.
For example,
Lastname^FirstName^MiddleName

7 26 TS R [0..1] Date/Time Birth Contains the date of birth as entered at the Information Center.
The format is YYYYMMDD. If no data is entered at the IIC, the
field contains NULL value (“”).
This field is not used if configured Message Type is PDS
Compatible.

8 1 IS R [0..1] Sex Contains the sex of the patient as entered at the IIC
The format is:
Male: M
Female: F
Unknown: U
This field is not used if configured Message Type is PDS
Compatible.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-39
Shared Segment Profile Definitions (Across Integration Profiles)

With PDS (Patient Data Server) and the Clinical Data Server (CDS), the patient name are not sent in accordance with the HL7 standard. If the
Message Type configuration is not set to PDS Compatible, the HL7 Patient Data Interface uses the field components Family Name and Given
Name for the HL7 output which is in accordance to the HL7 standard.

Example:

PDS Compatible:
PID|||394865||Robert Miller<CR>

Other Configurations (EMFC Coding / MDIL Coding:

PID|||33MR865||Baylor^James||""|U<CR>

PID|||MRNXR||Johnson^Robert||19110508|M<CR>

Supporting Details for CVS-2 Transactions (Query Mode)

The format of certain HL7 output fields depends on the message type setting configured in the Information Center Configuration Wizard (refer
to the Information Center System Installation and Configuration Manual.)

EMFC Coding/
EMFC Coding MDIL Coding
PDS Compatible

PID Segment, FirstName LastName LastName^FirstName^MiddleName LastName^FirstName^MiddleName

Patient Name field

PID Segment, DateofBirth DateOfBirth

Date/Time of Birth field

PID Segment, Sex field Sex Sex

PDI uses the following fields within the PID segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

3 250 CX R [1..6] Patient Identifier List Contains the patient ID as entered at the Information Center.
If no data is entered at the Information Center, this field
contains the NULL value ("").

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-40
 Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. Field Name Description

5 250 XPN R [1..1] Patient Name Contains the patient name as entered at the Information
Center.
The format depends on the IIC Message Type
configuration. PDS format is FirstName LastName,
standard format is LastName^FirstName

If Message Type configuration is VistA Compatible,

MiddleName is also added.
For example, LastName^FirstName^MiddleName

Common PV1 Segment Definition

The following PV1 Segment definition is common across all integration profiles. Specific values for each integration profile are specified and
common values are also noted.

SEQ LEN DT Usage Card. HL7 TBL# Item # Element Name Message Profile: Values
1 4 SI X [0..0] 00131 Set ID - PV1

2 1 IS R [1..1] 0004 00132 Patient Class CPD-1, CVS-1, CVS-2: I

(inpatient)

3 80 PL R [1..1] 00133 Assigned Patient CPD-1: Point of

Location care^ClinicalUnitName^bed
CVS-1, CVS-2:
ClinicalUnitName^bed&Branch
Id&NetworkId

4 2 IS X [0..0] 0007 00134 Admission Type

5 250 CX X [0..0] 00135 Preadmit Number

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-41
Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. HL7 TBL# Item # Element Name Message Profile: Values
6 80 PL X [0..0] 00136 Prior Patient
Location

7 250 X [0..0] 0010 00137 Attending Doctor

XCN

8 250 X [0..0] 0010 00138 Referring Doctor

XCN

9 250 X [0..0] 0010 00139 Consulting Doctor

XCN

10 3 IS X [0..0] 0069 00140 Hospital Service

11 80 PL X [0..0] 00141 Temporary

Location

12 2 IS X [0..0] 0087 00142 Preadmit Test

Indicator

13 2 IS X [0..0] 0092 00143 Re-admission

Indicator

14 6 IS X [0..0] 0023 00144 Admit Source

15 2 IS X [0..0] 0009 00145 Ambulatory Status

16 2 IS X [0..0] 0099 00146 VIP Indicator

17 250 X [0..0] 0010 00147 Admitting Doctor

XCN

18 2 IS X [0..0] 0018 00148 Patient Type

19 250 CX R [0..1] 00149 Visit Number CPD-1: VisitNumber (if

available)

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-42
 Shared Segment Profile Definitions (Across Integration Profiles)

Supporting Details for CVS-1 Transactions (Unsolicited Reporting)

PDI uses the following fields within the PV1 segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

2 1 IS R [1..1] Patient Class Always set to I (for Inpatient)

3 80 PL R [1..1] Assigned Patient Location Format: <point of care>^<room>^<bed>

<point of care> = ClinicalUnit Name
PDI uses its own format for the “bed” component
and divides it into the following sub-components:
<bed label>&<bed id>&<network id>
where:
<bed label> = bed label as configured on the
Information Center
<bed id> = artificial branch number
<network id> = artificial CareNet number

The parameters network id and bed id refer to the SDN/Carenet network number and the branch number where a monitor is connected.

The following pairs describe the same thing:

• network id is the same as bed id

• carenet number is the same as branch number
The terms network id and bed id are generic in HL7PDI because there are no branch numbers for IntelliVue Clinical Network monitors.
Manual configuration of these artificial branch numbers and Carenet numbers for connected monitors are created in Config Wizard.

Example:
PV1||I|ICU^^Bed14&14&1<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-43
Shared Segment Profile Definitions (Across Integration Profiles)

Supporting Details for CVS-2 Transactions (Query Mode)

PDI uses the following fields within the PV1 segment. The description field provides information as to how PDI implements the field.

SEQ LEN DT Usage Card. Field Name Description

2 1 IS R [1..1] Patient Class Always set to I (for Inpatient)

3 80 PL R [1..1] Assigned Patient Location Format: <point of care>^<room>^<bed>

<point of care> = ClinicalUnit Name
PDI uses its own format for the “bed” component and
divides it into the following sub-components: <bed
label>&<bed id>&<network id>
where:
<bed label> = bed label as configured on the
Information Center
<bed id> = artificial branch number
<network id> = artificial CareNet number

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-44
 Shared Segment Profile Definitions (Across Integration Profiles)

Common OBR Segment Definition

The following OBR Segment definition is common across all integration profiles. Specific values for each integration profile are specified and
common values are also noted. The OBR segment is sent in ORU messages to report parameter data. There is OBR for each time stamp (except
for the aperiodic data which has its own) in the message.

SEQ LEN DT Usage Card. HL7 TBL# Item # Element Name Message Profile: Values
1 4 SI X [0..0] 00237 Set ID OBR

2 427 EI X [0..0] 00216 Placer Order

Number

3 427 EI X [0..0] 00217 Filler Order

Number

4 250 CE X [0..0] 00238 Universal Service

Identifier

5 2 ID X [0..0] 00239 Priority

6 26 TS X [0..0] 00240 Requested Date/

Time

7 26 TS R [1..1] 00241 Observation Date/ YYYY[MM[DD[HH[MM]SS]

Time

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-45
Shared Segment Profile Definitions (Across Integration Profiles)

Common OBX Segment Definition

The following OBX Segment definition is common across all integration profiles. Specific values for each integration profile are specified and
common values are also noted.

SEQ LEN DT Usage Card. HL7 TBL# Item # Element Name Message Profile: Values
1 4 SI X [0..0] 00569 Set ID – OBX
2 2 ID R [1..1] 0125 00570 Value Type CVS-1, CVS-2: NM, ST TX
3 250 CE R [1..1] 00571 Observation CVS-1, CVS-2 <MDIL
Identifier identifier>^<text>^<MDIL>
4 20 ST R [1..1] 00572 Observation Sub-ID “Overview History of OBX
Segment Operation (CVS-1 and
CVS-2 Transactions)” on
page 4-47

5 99999 Varies R [1..1] 00573 Observation Value See 3.4.5.2

6 250 CE R [1..1] 00574 Units See 3.4.5.3

7 60 ST X [0..0] 00575 References Range

8 5 IS X [0..0] 0078 00576 Abnormal Flags

9 5 NM X [0..0] 00577 Probability

10 2 ID X [0..0] 0080 00578 Nature of Abnormal

Test

11 1 ID R [1..1] 0085 00579 Observation Result All: F

Status

12 26 TS X [0..0] 00580 Effect Date of Ref

Range

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-46
 Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. HL7 TBL# Item # Element Name Message Profile: Values
13 20 ST RE [0..1] 00581 User Defined All: PERIODIC, APERIODIC,
Access Checks SETTING, CONFIGURATION

14 26 TS RE [0..1] 00582 Date/Time of the All:

Observation YYYY[MM[DD[HH[MM]SS]

Overview History of OBX Segment Operation (CVS-1 and CVS-2 Transactions)

The OBX segment is sent in ORU messages to report parameter data, settings, and device configuration. It is also used for reporting alert states
if the interface has been configured for sending alert messages of the monitor. The format of certain HL7 output fields depends on the message
type setting configured in the Information Center Configuration Wizard (refer to the Information Center System Installation and Service
Manual.)

There is one OBX segment for each value.

• OBX for periodic data is sent at 5, 10, 30 or 60 sec interval. An OBX for aperiodic data is sent only upon change.
• OBX for settings is sent only when connection is first established and when settings change. (The disappearance of a setting or a change
in the validity of a parameter is treated as a change.)

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-47
Shared Segment Profile Definitions (Across Integration Profiles)

• OBX for alerts is sent only when the monitor currently is in alert state and the Information Center is configured to send alerts. Several
alerts can be present at the same time. In this case, all alerts which are present at a certain time stamp specified in the OBR segment are
sent with the following OBX segments. As soon as an alert is not displayed at the monitor anymore (either because it has been
acknowledged or no longer exists), the alert disappears in the corresponding OBX segment. The beginning and the end of an alert can be
determined by its appearance in an OBX segment.
PDI uses the following fields in the OBX segment:

SEQ LEN DT Usage Card. Field Name Description

2 2 ID R [1..1] Value Type NM (numeric) for numeric values,
ST (string) for string data,
TX for textual values

3 250 CE R [1..1] Observation Identifier This field contains a unique identifier for the
observation. The format depends on the Message Type
configuration setting.

See Observation identifier field and “Coding Systems”

on page 4-54 for more information.

4 20 ST R [1..1] Observation Sub-ID Number between 0 and 67 that identifies the device that
provides the data
In case of a MDIL-alert observation, field contains a
sequence number. Alert observations of a certain alert
type will use a sequence number that starts with 1 and
will increase by 1 with each alert observation of the
same alert type.

5 R [1..1] Observation Result Contains the result value or string

99999 Varies In case of an alert observation, field contains the alert
message.

6 250 CE R [1..1] Units Contains unit information

The format depends on the Message Type configuration
setting.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-48
 Shared Segment Profile Definitions (Across Integration Profiles)

SEQ LEN DT Usage Card. Field Name Description

11 1 ID R [1..1] Observation Result Status Always set to F for Final
This field is not used if the Message Type is set to
PDS Compatible.

13 20 ST RE [0..1] User Defined Access Checks Indicates type of parameter

May have the values PERIODIC, APERIODIC,
SETTING, and CONFIGURATION
An empty field indicates a value of PERIODIC. See
Parameter types for more details.

14 26 TS RE [0..1] Date/Time of Observation Date and time of the measurement of the parameter in
ISO format (YYYYMMDDHHMMSS)
Only present with APERIODIC parameters

17 250 CE X [0..0] Observation Method Method used to make the observation

Normally empty -- The observation is made
automatically by the instrument, but for manually
entered parameter values this field will contain the
value, MANUAL.

Observation Field Identifier

This field contains a unique identifier for the observation. The used format is:

<identifier> ^ <text> ^ <name of coding system>

Types of observations supported by PDI are parameter observations or alert observations.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-49
Shared Segment Profile Definitions (Across Integration Profiles)

Observation Sub-ID (Device Identifier)

The table below lists special device ID. The device name sent depends on the IIC HL7 Configuration Message Type setting.

PDS Compatible EMFC Coding/MDIL Coding/VistA Compatible

Data
Device ID Device Name Device Name
Source

Monitor 0 SDN Broadcast Monitoring Data

VueLink 1-4 From monitor From monitor

65 Hemo Calc Source Hemo Calculation

Hemodynamic
Calculation

Oxygenation 66 Oxy Calc Source Oxy Calculation

Calculation

Ventilation 67 Vent Calc Source Vent Calculation

Calculation

Note — EMFC Coding and EMFC with PDS Compatible codes are provided for backward compatibility only and may not be supported
in future releases of the Information Center. MDIL Coding is recommended because more parameters can be mapped. Parameter labels may
be different from original Philips CareNet labels.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-50
 Shared Segment Profile Definitions (Across Integration Profiles)

Parameter Types

• If the User Defined Access Checks field is empty or contains, PERIODIC, the parameter is a periodic parameter sent at the
intervals specified in the configuration.
• A value of APERIODIC indicates an aperiodic parameter that is sent only when a new measurement is made. An aperiodic parameter
usually contains a time stamp.
• A value of SETTING indicates a setting at the monitor or at a device connected via VueLink. Settings are sent when a new connection to
the Unsolicited Message Interface is established and when a change occurs. Settings remain valid until they are explicitly changed or
explicitly disappear. The disappearance of a setting is indicated by the NULL value ("") in the parameter value field. Settings contain no
time stamp.
• If the value is CONFIGURATION, the value type is ST (string) and provides a description of the device from which the parameter
comes. Configuration values are sent only at connection startup or when a new device appears (is attached via VueLink). When a device
disappears, a NULL value (“”) is sent for the device.
Special Parameters:

Two EMFC parameters do not originate from a device, but are generated by the Patient Data Interface to provide additional information.

• sMode (EMFC 32920/MDIL 0402-f85f) - String value setting that provides information about the operating mode of the attached patient
monitor. Values are:
• MONITORING - Monitoring mode (provided data for this bed is real)
• DEMO - Demonstration mode (provided data for this bed is generated artificially by the monitor for demonstrations or training)
• CONFIGURATION - Configuration mode (not available if configured for PDS Compatible)
• SERVICING - Service mode (not available if configured for PDS Compatible)
• Model (EMFC 33040/MDIL 0002-f887) – String-valued configuration parameter that provides information about the device generating
the data (device name shown in Table 2-2). When a device disappears, this parameter is sent again with the same device ID and a NULL
(“”) value.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-51
Shared Segment Profile Definitions (Across Integration Profiles)

The following table shows the possible monitoring mode strings depending on the Message Type configuration option.

Monitoring mode PDS compatible EMFC coding / MDIL coding

Demo mode DEMO DEMO

Monitoring mode MONITORING MONITORING

Configuration mode DEMO CONFIGURING

Servicing mode DEMO SERVICING

OBX Field Message Type Summary

The following table summarizes all OBX fields that are dependent on the Message Type configuration option.

PDS Compatible EMFC Coding MDIL Coding

Parameter Results: OBX EMFC-Code ^ Label ^ SDN EMFC-Code ^ Label ^ SDN MDIL-Code ^ Label ^ MDIL
Segment, Observation ID field

Parameter Results: OBX UnitLabel MDIL-Code ^ UnitLabel ^ MDIL-Code ^ UnitLabel ^ MDIL

Segment, Units field MDIL

Alert results: OBX Segment, Code ^ AlertLabel ^ SDN- Code ^ AlertLabel ^ MDIL- Code ^ AlertLabel ^ MDIL-
Observation ID ALARM ALARM ALARM

OBX segment, Assigned empty ClinicalUnitName ClinicalUnitName

Patient location field, Point of
Care component

OBX segment, Observation empty F (final result) F (final result)

result status field

Parameter Identifiers

HL7 Parameter Data Interface (HL7PDI) uses numeric codes from the Medical Device Interface Language (MDIL) standard nomenclature to
uniquely identify parameter, alert, and unit sources. The identifiers are sent over HL7 with the following format:

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-52
 Shared Segment Profile Definitions (Across Integration Profiles)

<Partition>-<TermCode>

The values for the partition and TermCode are hexadecimal values between 0x0000 and 0xffff, which are separated in the output with a
hyphen.

If required HL7PDI can be configured to send EMFC (Extended Medical Function Codes) for the parameter identifiers, which are known from
the Philips CareNet monitoring system instead of MDIL. This is dependent on the Message Type that is configured in the Information Center
Configuration Wizard. (See Information Center System Installation and Service Guide.) If EMFC Coding or PDS Compatible settings are
configured, EMFC codes are used as the parameter identifiers for all parameters sent in the HL7 output.

The label strings in this chapter are valid only for installations with English language software. When used in other countries, the label strings
vary according to how they are translated into the respective language. Philips recommends that you use the numeric parameter identifiers
instead of parameter labels for parameter identification when using the Parameter Data Interface.

EMFC Coding and EMFC with PDS compatible codes are provided for backward compatibility only and may not be available in future
releases of the Information Center. It is recommended to use the MDIL codes as a limited number of parameters cannot be mapped to an
EMFC. Parameter labels might be different from the original Philips CareNet labels.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-53
Shared Segment Profile Definitions (Across Integration Profiles)

Coding Systems

The following table shows the different coding systems used by the HL7 Parameter Data Interface and the format of the according identifier
and text fields.

Coding System Format of Identifier Format of Text

MDIL Contains a unique parameter/unit identifier that has the following Contains the parameter label string or the
format: <Partition>-<TermCode> unit string
The values for Partition and TermCode are hexadecimal values
between 0x0000 and 0xffff and follow the MDIL standard
nomenclature.
Partition may be one of the following values:
0x0002 - SCADA partition
0x0401 - EMFC partition
0x0004 - Dimension partition (for units)
0x0402 - Settings partition

MDIL-ALERT Contains the alert type (unique ID for the severity of the alert) Contains the alert message
8 - Yellow Inop
7 - Red Inop
6 - Soft Inop
5 - Hard Inop
4 - Severe Inop
3 - Short Yellow Alarm
2 - Yellow Alarm
1 - Red Alarm

SDN Contains the unique EMFC parameter identifier. Numeric decimal Contains the parameter label string
value between 0 and 65535

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-54
 Shared Segment Profile Definitions (Across Integration Profiles)

Coding System Format of Identifier Format of Text

SDN-ALARM Contains the alert type (unique ID for the severity of the alert) Contains the alert message
1 - Red Alarm
2 - Yellow Alarm
3 - Green Alarm

Parameter Flow

Under unusual circumstances, when numerous modules and parameters are active at a particular bedside, there may be some parameters that do
not appear in the HL7 output. To understand these limits, parameters must be divided into two categories:

The first category includes certain high-parameter-count data sources from IntelliVue monitors that are handled specially for HL7 output
(complex parameters). These are VueLink modules, EEG modules, and the monitor’s Hemodynamic, Ventilation, and Oxygenation calculation
screens.

• All parameters from these sources are always present in HL7 output, no matter how many are coming from the bedside monitor and
connected modules.
• The special handling of this category of parameters is only available for IntelliVue monitors (i.e. not CareNet/SDN monitors).
• To collect HL7 data from VueLink, EEG and calculation parameters from CareNet/SDN monitors, it is necessary to use the M2384
Clinical Data Server.
• Parameters that come from VueLink modules have additional characteristics. New VueLink drivers are continuously added, which may
generate new data and parameters not included in the list below. In these cases:
– The label for these parameters can be found for a specific VueLink driver in the latest edition of the Philips M1032A VueLink
External Device Instructions for Use (part number M1032-9001x) or in the instructions provided with the VueLink driver.
– The codes for these parameters can be found by looking for the associated labels in a sample of the HL7 output from the
Information Center when the VueLink module is connected. Note that in a few cases (particularly for devices for which the driver
has not been developed by Philips) these new parameters may not yet have defined static codes. In this case the MDIL codes are
dynamically assigned in the range from 0002-ffc0 to 0002-fff8 (corresponding to 65472 to 65528 decimal). In the Parameter List
table, they are referred to as "Free Text". If the VueLink module is disconnected and then connected to another monitor, the same
parameter may have a different code in this range.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-55
Shared Segment Profile Definitions (Across Integration Profiles)

The second category of parameters includes all other parameters from monitors, modules, and measurement servers not mentioned above
(ordinary parameters). These are generally the parameters that can be seen in the Patient Window of the Information Center.

• There is a fixed limit (currently thirty) to the number of parameters in this category that can be processed at any one time from a
particular bed, and parameters beyond this limit will not appear in the HL7 output. The systolic, diastolic, and mean values associated
with a particular blood pressure measurement together count as only one parameter for this purpose. Similarly the inspired and end-tidal
values for a particular gas measured by the Anesthesia Gas Module together count as only one parameter.
• Measurement unit labels sent in the HL7 output for these parameters are controlled by the general configuration settings of the
Information Center, rather than by the settings of the module or monitor. If not configured correctly, it is possible for the monitors to be
measuring in one unit (bedside pressures in kPa), while the Information Center is configured for a different unit (pressures in mmHg). In
this case, the label mmHg is sent by the IIC in HL7 messages, along with numeric values from the monitors which are measured in kPa.
This can be avoided if unit configurations on the bedsides and on the IICs are consistent.

Parameter List for Possible Coded Values for OBX.5

The following table lists all supported parameter identifier codes with their corresponding physiological source labels. This information
depends on the software revision on the monitor and the connected devices. Data transmitted by way of a VueLink or IntelliBridge device is
designated by a check in the VueLink/IntelliBridge column; the module depends on the version of the IntelliBridge and VueLink drivers and
the specification of the connected external device. With a particular software revision, the patient monitor may or may not export all of the
numerics specified in the table. The configuration of the patient monitor will also determine whether a numeric is exported. A numeric is only
available if the required measurement module is connected and if the specific measurement is activated. Some measurements require the
presence of more than one measurement module or may require special configuration steps to activate them.

Manually entered bedside data is exported as an aperiodic OBX with field 17 indicating the string MANUAL and field 14 contains the
timestamp that is generated by the bedside monitor when the clinical user confirmed the data.

The IIC Column, if checked, indicates support for parameters that do not come from the VueLink module.

Note — The following table e reflects all numerics that are sourced by IPM, Release H or earlier.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-56
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

ETR Ejection Time Ratio 

EVI Ventricular Ejection Index 
LVET Left Ventricular Ejection time 
STR Systolic Time Ratio  
VI Velocity Index numeric  
0002-0100 4 ECG Electrocardiogram numeric  
0002-0101 8 I Lead I - ECG Wave Label numeric  
0002-0102 12 II Lead II - ECG Wave Label numeric  
0002-0103 3400 V1 Lead V1 - ECG Wave Label numeric  
0002-0104 3404 V2 Lead V2 - ECG Wave Label numeric  
0002-0105 3408 V3 Lead V3 - ECG Wave Label numeric  
0002-0106 3412 V4 Lead V4 - ECG Wave Label numeric  
0002-0107 3416 V5 Lead V5 - ECG Wave Label numeric  
0002-0108 3420 V6 Lead V6 - ECG Wave Label numeric  
0002-013d 16 III Lead III - ECG Wave Label numeric  
0002-013e 24 aVR Lead aVR - ECG Wave Label numeric  
0002-013f 20 aVL Lead aVL - ECG Wave Label numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-57
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-0140 28 aVF Lead aVF - ECG Wave Label numeric  

0002-0143 32 V Lead V - ECG Wave Label numeric  
0002-014b MCL Lead MCL numeric 
0002-014c 36 MCL1 Lead MCL-1 numeric 
0002-014d MCL2 Lead MCL-2 numeric 
0002-014e MCL3 Lead MCL-3 numeric 
0002-014f MCL4 Lead MCL-4 numeric 
0002-0150 MCL5 Lead MCL-5 numeric 
0002-0151 MCL6 Lead MCL-6 numeric 
0002-0164 ES Wave l Label Frank Lead (EASI) numeric 
0002-0165 AS Wave l Label Frank Lead (EASI) numeric 
0002-0166 AI Wave l Label Frank Lead (EASI) numeric 
0002-0300 ST ST Amplitude numeric  
0002-0301 1796 ST-I ST lead I numeric  
0002-0302 1800 ST-II ST lead II numeric  
0002-0303 1820 ST-V1 ST lead V1 numeric  
0002-0304 1824 ST-V2 ST lead V2 numeric  
0002-0305 1828 ST-V3 ST lead V3 numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-58
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-0306 1832 ST-V4 ST lead V4 numeric  

0002-0307 1836 ST-V5 ST lead V5 numeric  
0002-0308 1840 ST-V6 ST lead V6 numeric  
0002-033d 1804 ST-III ST lead III numeric  
0002-033e 1808 ST-aVR ST lead aVR numeric  
0002-033f 1812 ST-aVL ST lead aVL numeric  
0002-0340 1816 ST-aVF ST lead aVF numeric  
0002-0343 4604 ST-V ST lead V numeric 
0002-034b ST-MCL ST lead MCL numeric 
0002-0364 ST-ES ST lead ES numeric 
0002-0365 ST-AS ST lead AS numeric 
0002-0366 ST-AI ST lead AI numeric 
0002-3f20 QT QT Interval numeric  
0002-3f24 QTc QT Interval corrected for rate numeric  
0002-4182 40 HR Heart Rate numeric  
0002-418a 1092 btbHR Cardiac Beat-to-Beat Rate. Delivered by the numeric 
ECG

0002-4261 136 PVC Premature Ventricular Counted Beats numeric 

0002-4262 PVC Premature Ventricular Counted Beats numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-59
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-480a 44 Pulse Pulse Rate numeric 

0002-4822 44 Pulse Pulse Rate from Plethysmogram numeric 
0002-4900 584 SVRI Systemic Vascular Resistance Index numeric 
0002-4904 564 LVSWI Left Ventricular Stroke Volume Index numeric 
0002-490c 552 C.I. Cardiac Index numeric 
0002-4908 580 RVSWI Right Ventricular Stroke Work Index numeric 
0002-4a00 2184 P Generic Invasive Pressure numeric 
0002-4a01 Ps Non-specific Invasive Pressure (systolic) numeric 
0002-4a02 Pd Non-specific Invasive Pressure (diastolic) numeric 
0002-4a03 Pm Non-specific Invasive Pressure (mean) numeric 
0002-4a04 88 NBP Non-invasive blood pressure numeric  
0002-4a05 89 NBPs Non-invasive blood pressure (systolic) numeric  
0002-4a06 90 NBPd Non-invasive blood pressure (diastolic) numeric  
0002-4a07 91 NBPm Non-invasive blood pressure (mean) numeric  
0002-4a0c 168 Ao Aortic Blood Pressure numeric  
0002-4a0d 169 AoS Ao (systolic) numeric  
0002-4a0e 170 AoD Ao (diastolic) numeric  
0002-4a0f 171 AoM Ao (mean) numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-60
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-4a10 160 ART Arterial Blood Pressure numeric  

0002-4a11 161 ARTs ART (systolic) numeric  
0002-4a12 162 ARTd ART (diastolic) numeric  
0002-4a13 163 ARTm ART (mean) numeric  
0002-4a14 64 ABP Arterial Blood Pressure numeric 
0002-4a15 65 ABPs ABP (systolic) numeric  
0002-4a16 66 ABPd ABP (diastolic) numeric  
0002-4a17 67 ABPm ABP (mean) numeric  
0002-4a1c 76 PAP Pulmonary Artery Occlusion Pressure numeric  
0002-4a1d 77 PAPs PAP (systolic) numeric  
0002-4a1e 78 PAPd PAP (diastolic) numeric  
0002-4a1f 79 PAPm PAP (mean) numeric  
0002-4a24 128 PAWP Pulmonary Artery Wedge Pressure numeric  
0002-4a28 1100 UAP Umbilical Arterial Pressure numeric  
0002-4a29 1101 UAPs UAP (systolic) numeric  
0002-4a2a 1102 UAPd UAP (diastolic) numeric  
0002-4a2b 1103 UAPm UAP (mean) numeric  
0002-4a30 72 LAP Left Atrial Pressure numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-61
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-4a31 73 LAPs LAP (systolic) numeric  

0002-4a32 74 LAPd LAP (diastolic) numeric  
0002-4a33 75 LAPm LAP (mean) numeric  
0002-4a34 164 RAP Right Atrial Pressure numeric  
0002-4a35 165 RAPs RAP (systolic) numeric  
0002-4a36 166 RAPd RAP (diastolic) numeric  
0002-4a37 167 RAPm RAP (mean) numeric  
0002-4a44 68 CVP Central Venous Pressure numeric  
0002-4a45 69 CVPs CVP (systolic) numeric  
0002-4a46 70 CVPd CVP (diastolic) numeric  
0002-4a47 71 CVPm CVP (mean) numeric  
0002-4a48 1104 UVP Umbilical Venous Pressure numeric  
0002-4a49 1105 UVPs UVP (systolic) numeric  
0002-4a4a 1106 UVPd UVP (diastolic) numeric  
0002-4a4b 1107 UVPm UVP (mean) numeric  
0002-4b00 456 VO2 Oxygen Consumption numeric  
0002-4b04 124 C.O. Cardiac Output numeric  
0002-4b1c Cuff NBP Cuff Pressure displayed during numeric 
measurement

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-62
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-4b24 364 PVR Pulmonary vascular Resistance numeric 

0002-4b28 400 SVR Systemic Vascular Resistance numeric 
0002-4b2c 156 SO2 Oxygen Saturation numeric 
0002-4b34 1352 SaO2 Oxygen Saturation measured in the Artery numeric 
0002-4b3c 192 SvO2 Mixed Venous Oxygen Saturation numeric  
0002-4b40 256 AaDO2 Alveolar- Arterial Oxygen Difference numeric 
0002-4b48 Temp Generic Temperature numeric  
0002-4b50 536 Tart Arterial Temperature numeric  
0002-4b54 1316 Tairwy Airway Temperature numeric  
0002-4b5c 2616 Tbody Patient Temperature numeric 
0002-4b60 532 Tcore Core (Body) Temperature numeric  
0002-4b64 528 Tesoph Esophageal Temperature numeric  
0002-4b68 544 Tinj Injectate Temperature. Cardiac Output numeric 
0002-4b6c 524 Tnaso Nasopharyngeal Temperature numeric  
0002-4b74 516 Tskin Skin Temperature numeric  
0002-4b78 Ttymp Tympanic Temperature numeric 
0002-4b7c 540 Tven Venous Temperature numeric  
0002-4b84 392 SV Stroke Volume numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-63
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-4b90 316 LCW Left Cardiac Work Index numeric 

0002-4b94 372 RCW Right Cardiac Work numeric 
0002-4b9c 320 LVSW Left Ventricular Stroke Volume numeric 
0002-4ba4 376 RVSW Right Ventricular Stroke Work numeric 
0002-4bb0 512 Perf Relative Perfusion numeric 
0002-4bb4 176 Pleth Pulse Oximetry Pleth wave  
0002-4bb8 188 SpO2 Peripheral oxygen saturation (pulse numeric  
oximeter)

0002-4bc4 1960 ΔSpO2 Difference between two SpO2 Values (like numeric  
Left - Right)

0002-4bc8 4596 SpO2 l Arterial Oxygen Saturation (left) numeric 

0002-4bcc 4600 SpO2 r Arterial Oxygen Saturation (right) numeric 
0002-4bdc 220 CCO Continuous Cardiac Output numeric  
0002-4c00 1332 EDV End Diastolic Volume numeric 
0002-4c04 1336 ESV End Systolic Volume numeric 
0002-4c25 3464 dPmax Index of Left Ventricular Contractility numeric 
0002-5000 92 Resp1 Respiration numeric  
0002-500a RR Impedance Respiration Rate numeric  
0002-5000 is the code for the respiration
wave. This is incorrectly sent in place of the
RR code.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-64
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-5012 96 awRR Airway Respiration Rate numeric  

0002-5022 1732 RRaw Airway Respiration Rate. Used by the numeric  
Ohmeda Ventilator

0002-5080 1160 VC Vital Lung Capacity numeric  

0002-5088 284 COMP Generic label Lung Compliance numeric  
0002-508c 1148 Cdyn Dynamic Lung Compliance numeric  
0002-5090 3724 Cstat Static Lung Compliance numeric  
0002-50ac 108 CO2 Carbon Dioxide numeric  
0002-50b0 112 etCO2 End-Tidal CO2 Concentration numeric  
0002-50ba 116 imCO2 Inspired Minimum CO2 numeric  
0002-50cc 120 tcpCO2 Transcutaneous Carbon Dioxide Partial numeric  
Pressure

0002-50d0 152 tcpO2 Transcutaneous Oxygen Partial Pressure numeric  

0002-50d4 216 AWF Airway flow numeric  
0002-50d9 4784 PEF Peak Expiratory Flow numeric  
0002-50dd 4780 PIF Peak Inspiratory Flow numeric  
0002-50e0 1784 VCO2 CO2 Production numeric 
0002-50e4 1668 T.I. Transthoracic Impedance numeric 
0002-50e8 1176 Pplat Plateau Pressure numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-65
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-50f0 204 AWP Airway Pressure wave  

0002-50f2 1292 AWPmin Airway Pressure Minimum numeric 
0002-50f4 1368 CPAP Continuous Positive Airway Pressure numeric 
0002-50f9 1156 NgInsP Negative Inspiratory Pressure numeric  
0002-5100 1780 iPEEP Intrinsic PEEP Breathing Pressure numeric  
0002-5108 1736 AWPin Airway Pressure Wave - measured in the wave 
inspiratory path

0002-5109 208 PIP Positive Inspiratory pressure numeric  

0002-510b 1172 MnAwP Mean Airway Pressure. numeric  
0002-5114 4864 RQ Respiratory Quotient numeric 
0002-5118 1180 I:E 1: Inpired:Expired Ratio numeric  
0002-511c 452 Vd/Vt Ratio of Deadspace to Tidal Volume numeric 
0002-5120 1144 Raw Static Lung Resistance numeric  
0002-5124 1636 Rexp Expiratory Resistance numeric 
0002-5128 1648 Rinsp Inspiratory Resistance numeric 
0002-5130 1308 ApneaD Apnea Duration numeric  
0002-513c 212 TV Tidal Volume numeric  
0002-5140 4876 awVd Airway Dead Space numeric 
0002-5148 324 MINVOL Airway Minute Volume Inspiratory numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-66
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-514c MVexp Expired Minute Volume numeric  

0002-5150 4552 MVin Inspired Minute Volume numeric  
0002-5160 4656 FICO2 Fractional concentration of inspired CO2 numeric 
0002-5164 1248 O2 Airway Oxygen numeric  
0002-5168 1944 ΔO2 Delta O2 Concentration numeric  
0002-517c 344 PECO2 Partial O2 Venous numeric 
0002-518c 1744 AWFin Airway Flow Wave - measured in the numeric 
inspiratory path

0002-5190 1320 VQI Ventilation Perfusion Index numeric 

0002-519c 1776 Poccl Occlusion Pressure numeric  
0002-51a8 348 PEEP Positive End-Expiratory Pressure numeric  
0002-51b0 448 Vd Dead Space Volume numeric 
0002-51b4 1788 relVd relative Dead Space numeric 
0002-51b8 1772 TrpVol Lung Volume Trapped numeric 
0002-51cc 4612 MMV Mandatory Minute Volume numeric 
0002-51d4 1756 DCO2 High Frequency Gas Transport Coefficient numeric 
Value

0002-51d8 1272 DES Gas Analyzer Desflurane numeric  

0002-51dc 1264 ENF Gas Analyzer Enflurane numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-67
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-51e0 1268 HAL Gas Analyzer Halothane numeric  

0002-51e4 1276 SEV Gas Analyzer Sevoflurane numeric  
0002-51e8 1260 ISO Gas Analyzer Isoflurane numeric  
0002-51f0 1252 N2O Gas Analyzer Nitrous Oxide numeric  
0002-5214 1232 etDES Desflurane Concentration - End Tidal numeric  
0002-5218 1216 etENF Enflurane Concentration - End Tidal numeric  
0002-521c 1224 etHAL Halothane Concentration - End Tidal numeric  
0002-5220 1240 etSEV Gas Analyzer Sevoflurane - End Tidal numeric  
0002-5224 1208 etISO Gas Analyzer Isoflurane - End Tidal numeric  
0002-522c 1184 etN2O Gas Analyzer End-Tidal Nitrous Oxide numeric  
0002-5268 1236 inDES Desflurane Concentration - Inspired numeric  
0002-526c 1220 inENF Enflurane Concentration - Inspired numeric  
0002-5270 1228 inHAL Halothane Concentration - Inspired numeric  
0002-5274 1244 inSEV Sevoflurane Concentration - Inspired numeric  
0002-5278 1212 inISO Gas Analyzer Isoflurane - Inspired numeric  
0002-5280 1188 inN2O Gas Analyzer Nitrous Oxide - Inspired numeric  
0002-5284 1196 inO2 Oxygen Concentration - Inspired numeric  
0002-5360 2120 DPosP Duration of Positive Pressure numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-68
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-5368 4820 PEinsp End Inspiratory Pressure numeric  

0002-5370 1748 Leak Leakage numeric  
0002-5374 260 ALVENT Alveolar Ventilation numeric 
0002-5378 1192 etO2 End-Tidal Oxygen Concentration numeric  
0002-537c 3304 N2 Airway Nitrogen numeric  
0002-5380 3320 etN2 N2 End-Tidal numeric  
0002-5384 3316 inN2 N2 Inspired numeric  
0002-5388 1256 AGT Gas Analyzer Agent numeric  
0002-538c 1200 etAGT Gas Analyzer Agent - End Tidal numeric  
0002-5390 1204 inAGT Gas Analyzer Agent - Inspired numeric  
0002-5804 252 CPP Cerebral Perfusion Pressure numeric  
0002-5808 80 ICP Intra-Cranial Pressure numeric  
0002-5809 81 ICPs ICP (systolic) numeric  
0002-580a 82 ICPd ICP (diastolic) numeric  
0002-580b 83 ICPm ICP (mean) numeric  
0002-5880 1116 GCS Glasgow Coma Score numeric 
0002-5882 1120 EyeRsp SubScore of the GCS: Eye Response numeric 
0002-5883 1128 MotRsp SubScore of the GCS: Motoric Response numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-69
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-5884 1124 VblRsp SubScore of the GCS: Verbal Response numeric 

0002-5900 1060 HC Head Circumference numeric 
0002-5924 1108 PRL Pupil Reaction Left eye numeric 
0002-5928 1112 PRR Pupil Reaction Right eye numeric 
0002-592c 2580 EEG Generic EEG and BIS label numeric  
0002-593c 3568 EMG Electromyography numeric  
0002-597c MDF Mean Dominant Frequency numeric 
0002-5984 PPF Peak Power Frequency numeric 
0002-5988 3556 SEF Spectral Edge Frequency numeric 
0002-59ac Bursts Burst Count numeric 
0002-59b4 CSA Compressed Spectral Array numeric 
0002-59b8 3564 TP Total Power numeric  
0002-59d4 Alpha Alpha Relative Frequency numeric 
0002-59d8 Beta Beta Relative Frequency numeric 
0002-59dc Delta Delta Relative Frequency numeric 
0002-59e0 Theta Theta Relative Frequency numeric 
0002-6858 InRate Infusion Rate numeric 
0002-680c 2192 UrFl Urimeter - Urine Flow numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-70
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-6814 4948 U/O Previous Hour - Urine Flow numeric 

0002-6824 444 UrVol Urine Volume numeric 
0002-6830 3324 BagVol Current fluid (urine) in urine bag numeric 
0002-6858 4884 InRate Infusion Rate numeric 
0002-68a4 4888 BolVol Bolus Volume numeric 
0002-68a8 4892 InfVol Fluid Delivery numeric 
0002-68dc 4896 InfTim Remaining Infusion time numeric 
0002-68fc 1664 AccVol Infusion Pump Accumulated Volume. numeric 
Measured value

0002-7004 2620 pHa pH in arterial Blood numeric 

0002-7008 336 PaCO2 Partial Pressure of arterial Carbon Dioxide numeric 
0002-700c 464 PaO2 Partial O2 arterial numeric 
0002-7014 308 Hb Hemoglobin in arterial Blood numeric 
0002-7018 276 CaO2 Arterial Oxygen Content CaO2 numeric 
0002-7034 2624 pHv pH in venous Blood numeric 
0002-7038 2676 PvCO2 Partial CO2 in the venous blood numeric 
0002-703c 360 PvO2 Partial O2 Venous numeric 
0002-7048 296 CvO2 Venous Oxygen Content numeric 
0002-7064 1412 UrpH pH value in Urine numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-71
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-706c 428 UrNa Natrium (Sodium) in Urine numeric 

0002-70d8 388 SerNa Natrium (Sodium) in Serum numeric 
0002-7104 1284 pH pH in the Blood Plasma numeric 
0002-7108 1288 HCO3 Hydrocarbonate concentration in Blood numeric 
Plasma

0002-710c 1624 Na Natrium (Sodium) numeric 

0002-7110 2600 K Kalium (Potassium) numeric 
0002-7114 2608 Glu Glucose numeric 
0002-7118 2604 iCa Ionized Calcium numeric 
0002-7140 2672 PCO2 Partial CO2 numeric 
0002-7168 1632 Cl Chloride numeric 
0002-716c 1280 BE Base Excess of Blood numeric 
0002-7174 2648 PO2 Partial O2 numeric 
0002-717c 1584 Met-Hb Methemoglobin numeric 
0002-7180 1576 CO-Hb Carboxyhemoglobin numeric 
0002-7184 1348 Hct Hematocrit numeric 
0002-7498 148 FIO2 Fractional Inspired Oxygen numeric  
0002-d006 144 EctSta Ectopic Status label string  
0002-d007 140 RhySta Arrhythmia Rhythm Status label string  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-72
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-d02a 312 IMV Intermittent Mandatory Ventilation numeric 

0002-d0bc 4900 PuStat Operational Status of Infusion Pump string 
0002-e004 520 Trect Rectal Temperature numeric  
0002-e014 132 Tblood Blood Temperature numeric  
0002-e018 172 ΔTemp Difference Temperature Label numeric  
0002-efff 2400 (Blank) (Blank) numeric 
0002-f03d STindx ST Index numeric 
0002-f03e SitTim TcGas Site Timer numeric 
0002-f03f SensrT TcGas Transducer Temperature numeric 
0002-f040 3444 ITBV Intrathoracic Blood Volume numeric  
0002-f041 3448 ITBVI Intrathoracic Blood Volume Index numeric  
0002-f042 3452 EVLW Extravascular Lung Water numeric  
0002-f043 3456 EVLWI Extravascular Lung Water Index numeric  
0002-f044 4568 GEDV Global End Diastolic Volume numeric 
0002-f045 4572 GEDVI Global End Diastolic Volume Index numeric 
0002-f046 3440 CFI Cardiac Function Index numeric  
0002-f047 1136 CCI Continuous Cardiac Output Index numeric  
0002-f048 556 SI Stroke Index numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-73
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f049 3460 SVV Stroke Volume Variation numeric 

0002-f04a 3552 SR EEG Suppression Ratio numeric  
0002-f04b Impedc Electrode Impedance numeric 
0002-f04d 1140 SQI BIS Signal Quality Index numeric  
0002-f04e 228 BIS Bispectral Index numeric  
0002-f050 TPrel Total Power Relative numeric 
0002-f051 1096 tcGas Generic Term for the Transcutaneous Gases numeric 
0002-f05d MAC Minimum Alveolar Concentration numeric  
0002-f05e 3732 etMAC Minimum Alveolar Concentration (MAC) numeric  
Value - End Tidal

0002-f05f 3728 inMAC MAC Value - Inspired numeric  

0002-f066 MACawk MAC Value - Awake numeric 
0002-f067 572 PVRI Pulmonary vascular Resistance numeric 
0002-f068 560 LCWI Left Cardiac Work Index numeric 
0002-f069 576 RCWI Right Cardiac Work Index numeric 
0002-f06a 588 VO2I Oxygen Consumption Index numeric 
0002-f06b 340 PB Barometric Pressure = Ambient Pressure numeric  
0002-f06c 596 Sp-vO2 Difference between SpO2 and SvO2 numeric  
0002-f06d 328 DO2 Oxygen Availability numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-74
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f06e 568 DO2I Oxygen Availability Index numeric 

0002-f06f 332 O2ER Oxygen Extraction Ratio numeric 
0002-f070 368 Qs/Qt Percent Alveolar-venous Shunt numeric 
0002-f071 472 BSA Body Surface Area numeric 
0002-f072 592 LI Light Intensity (Numerical value delivered numeric 
by the SvO2 measurement)

0002-f073 LImax Light Intensity Maximum Value numeric 

0002-f074 LImin Light Intensity Minimum Value numeric 
0002-f075 LImean Light Intensity Mean Value numeric 
0002-f076 HeatPw TcGas Sensor Heating Power numeric 
0002-f078 HR-PLS Pulse Deficit: Heart Rate - Pulse numeric 
0002-f079 4564 InjVol Injectate Volume - Cardiac Output numeric 
0002-f07a 3468 ETVI ExtraVascular Thermo Volume Index - numeric 
Cardiac Output

0002-f07b CompCt Generic Numeric Calculation Constant numeric 

0002-f07c CathCt Generic Numeric Calculation Constant numeric 
0002-f081 SQNNvr SDNN Heart Rate Variability Metric numeric 
0002-f08a Perf l Perfusion Left numeric 
0002-f08b Perf r Perfusion Right numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-75
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f08c PLETHr Pleth Right Wave numeric 

0002-f08d PLETHl Pleth Left Wave numeric  
0002-f08f 268 BUN Blood Urea Nitrogen numeric 
0002-f090 BEecf Base Excess numeric  
0002-f091 1168 SpMV Spontaneous Minute Volume numeric 
0002-f092 264 Ca-vO2 Arteriovenous Oxygen Difference numeric 
0002-f093 460 Weight Patient Weight numeric  
0002-f094 304 Height Patient Height numeric  
0002-f099 4632 MAC Minimum Alveolar Concentration numeric 
0002-f09b PlethT Pleth wave from Telemetry numeric 
0002-f09c 188 SpO2T SpO2 Parameter Label sourced by the numeric  
Telemetry System

0002-f09d 44 PulseT Pulse parameter label sourced by the numeric  

Telemetry System

0002-f0a1 NBPs T Non-invasive Pressure - systolic numeric 

0002-f0a2 NBPd T Non-invasive Pressure - diastolic numeric 
0002-f0a3 NBPm T Non-invasive Pressure - mean numeric 
0002-f0a4 48 P1 Invasive pressure P1 numeric 
0002-f0a5 49 P1s Generic invasive pressure P1 (systolic) numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-76
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f0a6 50 P1d Generic invasive pressure P1 (diastolic) numeric  

0002-f0a7 51 P1m Generic invasive pressure P1 (mean) numeric  
0002-f0a8 52 P2 Invasive pressure P2 numeric 
0002-f0a9 53 P2s Generic invasive pressure P2 (systolic) numeric  
0002-f0aa 54 P2d Generic invasive pressure P2 (diastolic) numeric  
0002-f0ab 55 P2m Generic invasive pressure P2 (mean) numeric  
0002-f0ac 56 P3 Non-specific label for Pressure 3 numeric 
0002-f0ad 57 P3s Generic invasive pressure P3 (systolic) numeric  
0002-f0ae 58 P3d Generic invasive pressure P3 (diastolic) numeric  
0002-f0af 59 P3m Generic invasive pressure P3 (mean) numeric  
0002-f0b0 60 P4 Non-specific label for Pressure 4 numeric 
0002-f0b1 61 P4s Generic invasive pressure P4 (systolic) numeric  
0002-f0b2 62 P4d Generic invasive pressure P4 (diastolic) numeric  
0002-f0b3 63 P4m Generic invasive pressure P4 (mean) numeric  
0002-f0b4 IC1 Intracranial Pressure Label IC1 numeric  
0002-f0b5 IC1s Intracranial Pressure Label IC1 (systolic) numeric 
0002-f0b6 IC1d Intracranial Pressure Label IC1 (diastolic) numeric 
0002-f0b7 IC1m Intracranial Pressure Label IC1 (mean) numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-77
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f0b8 IC2 Intracranial Pressure Label IC2 numeric  

0002-f0b9 IC2s Intracranial Pressure Label IC2 (systolic) numeric 
0002-f0ba IC2d Intracranial Pressure Label IC2 (diastolic) numeric 
0002-f0bb IC2m Intracranial Pressure Label IC2 (mean) numeric 
0002-f0bc FAP Femoral Arterial Pressure numeric  
0002-f0bd FAPs Femoral Arterial Pressure (systolic) numeric 
0002-f0be FAPd Femoral Arterial Pressure (diastolic) numeric 
0002-f0bf FAPm Femoral Arterial Pressure (mean) numeric 
0002-f0c0 BAP Brachial Arterial Pressure numeric  
0002-f0c1 BAPs Brachial Arterial Pressure (systolic) numeric 
0002-f0c2 BAPd Brachial Arterial Pressure (diastolic) numeric 
0002-f0c3 BAPm Brachial Arterial Pressure (mean) numeric 
0002-f0c4 3012 Tvesic Temperature of the Urine fluid numeric  
0002-f0c5 Tcereb Cerebral Temperature numeric 
0002-f0c6 2904 Tamb Air Temperature numeric  
0002-f0c7 100 T1 Generic Temperature T1 numeric 
0002-f0c8 104 T2 Generic Temperature T2 numeric  
0002-f0c9 1040 T3 Generic Temperature T3 numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-78
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f0ca 1044 T4 Generic Temperature T4 numeric  

0002-f0d8 84 IUP Intra-Uterine Pressure numeric 
0002-f0df 1640 AWV Airway Volume Wave numeric  
0002-f0e0 1712 TVin Inspired Tidal Volume numeric  
0002-f0e1 1716 TVexp Expired Tidal Volume numeric  
0002-f0e2 RRspir Respiration Rate from Spirometry numeric 
0002-f0e3 4576 PPV Pulse Pressure Variation numeric 
0002-f0e5 Pulse Pulse Rate from NBP numeric  
0002-f0f1 4608 MRR Mandatory Respiratory Rate numeric 
0002-f0f2 4616 MTV Mandatory Tidal Volume numeric 
0002-f0f3 4620 SpTV Spontaneous Tidal Volume numeric 
0002-f0f4 4624 cTnI Cardiac Troponin l numeric  
0002-f0f5 4628 CPB Cardiopulmonary Bypass Flag numeric 
0002-f0f6 4636 BNP Cardiac Brain Natriuretic Peptide numeric 
0002-f0ff 4648 PlatTi Plateau Time numeric 
0002-f100 4644 ScvO2 Central Venous Oxygen Saturation numeric  
0002-f101 4640 SNR Signal to Noise ratio numeric 
0002-f103 4652 Hum Humidity in Incubator numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-79
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f104 ST Bslinr ST Baseline numeric 

0002-f105 4580 GEF Global Ejection Fraction numeric 
Delivered by the Pulsion PiCCO Plus

0002-f106 4592 PVPI Pulmonary Vascular numeric 

Delivered by the Pulsion PiCCO Plus

0002-f110 pToral Oral temperature numeric 

0002-f114 pTrect Rectal temperature numeric 
0002-f118 pTaxil Axillary temperature numeric 
0002-f125 pNN50 pNN50 Heart Rate Variability Metric numeric 
0002-f12a Air T Incubator Air Temperature numeric 
0002-f12c Perf T Relative Perfusion from Telemetry numeric 
0002-f14a RLShnt Right-to-Left Heart Shunt numeric 
0002-f154 QT-HR Averaged HR used for QTc numeric  
0002-f155 QT Bsl QT Baseline numeric 
0002-f156 dQTc Delta QTc numeric  
0002-f157 QTHRBl QT Baseline Heart Rate numeric 
0002-f158 2628 pHc pH value in the capillaries numeric 
0002-f159 2680 PcCO2 Partial CO2 in the capillaries numeric 
0002-f15a 2652 PcO2 Partial O2 in the capillaries numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-80
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f15b 2756 iMg ionized Magnesium numeric 

0002-f15c 1444 SerMg Serum Magnesium numeric 
0002-f15d 1440 tSerCa Total of Calcium in Serum numeric 
0002-f15e 1448 SerPho Serum Phosphate numeric 
0002-f15f 1456 SerCl Serum Chlorid (Chloride) numeric 
0002-f160 1556 Fe Ferrum (Iron) numeric 
0002-f163 1460 SerAlb Serum Albumin numeric 
0002-f164 2708 ’SaO2 Calculated SaO2 numeric 
0002-f165 1580 HbF Fetal Hemoglobin numeric 
0002-f166 2712 'SvO2 Calculated SvO2 numeric 
0002-f167 1488 Plts Platelets (thrombocyte count) numeric 
0002-f168 1480 WBC White Blood Count (leucocyte count) numeric 
0002-f169 1484 RBC Red Blood Count (erithrocyte count) numeric 
0002-f16a 1604 RC Reticulocyte Count numeric 
0002-f16b 356 PlOsm Plasma Osmolarity numeric 
0002-f16c 292 CreaCl Creatinine Clearance numeric 
0002-f16d 468 NsLoss Nitrogen Balance Lab Data numeric 
0002-f16e 1560 Chol Cholesterin (Cholesterol) numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-81
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f16f 1564 TGL Triglycerides numeric 

0002-f170 HDL High Density Lipoprotein Concentration numeric 
0002-f171 LDL Low Density Lipoprotein Concentration numeric 
0002-f172 2744 Urea Urea used by i-STAT numeric 
0002-f173 2780 Crea Creatinine numeric  
0002-f174 2792 Lact Lactate numeric  
0002-f177 1420 tBili Total Bilirubin numeric 
0002-f178 1472 SerPro SerumTotal Protein numeric 
0002-f179 1588 tPro Total Protein numeric 
0002-f17a 1432 dBili Direct Bilirubin numeric 
0002-f17b 1592 LDH Lactic Dehydrogenase numeric 
0002-f17c 1612 ESR Erythrocyte Sedimentation Rate numeric 
0002-f17d PCT Procalcitonin Concentration numeric 
0002-f17f 1540 CK-MM Creatine Kinase isoenzyme MM numeric 
0002-f180 1532 SerCK Serum Creatine Kinase numeric 
0002-f181 1536 CK-MB Creatine Kinase Isoenzyme MB numeric  
0002-f182 1528 CHE Cholinesterase numeric 
0002-f183 CRP C-Reactive Protein Electrolyte Marker numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-82
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f184 1596 AST Aspartate - Aminotransferase numeric 

0002-f185 1520 AP Alkaline Phosphatase numeric 
0002-f186 1524 alphaA Alpha Amylase numeric 
0002-f187 1552 GPT Glutamic-Pyruvic-Transaminase numeric 
0002-f188 1548 GOT Glutamic Oxalacetic Transaminase numeric 
0002-f189 1544 GGT Gamma Glutamyl Transpeptidase numeric 
0002-f18a 3600 ACT Activated Clotting Time numeric  
0002-f18b 1508 PT Prothrombin Time numeric  
0002-f18c 3628 PT INR Prothrombin time - international normalized numeric 
ratio

0002-f18d 3604 aPTTWB Activated Partial Thromboplastin time. WB: numeric 

Whole Blood time

0002-f18e 3608 aPTTPE Activated Partial Thromboplastin time. PE: numeric 

Plasma Equivalent time

0002-f18f 3616 PT WB Prothrombin time. WB: Whole Blood time numeric 

0002-f190 3620 PT PE Prothrombin time. PE: Plasma Equivalent numeric 
time

0002-f191 1512 TT Thrombin Time numeric 

0002-f192 1608 CT Coagulation Time numeric 
0002-f193 1516 Quick Thromboplastine Time - Quick value numeric 
0002-f194 300 FeNa Fractional Excretion of Sodium numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-83
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f195 1408 UrUrea Urine Urea numeric 

0002-f196 416 UrCrea Urine Creatinine numeric 
0002-f197 420 UrK Urine Potassium numeric 
0002-f198 424 UrKEx Urinary Potassium Excretion numeric 
0002-f199 440 UrOsm Urine Osmolarity numeric 
0002-f19a 1464 UrCl Urinary Chloride numeric 
0002-f19b 1568 UrPro Urinary Total Protein numeric 
0002-f19c 1572 UrCa Urinary Calcium numeric 
0002-f19d 3008 UrDens Density of the Urine fluid numeric 
0002-f19e UrHb HB in Urine numeric 
0002-f19f 1428 UrGlu Glucose in Urine numeric 
0002-f1a0 2716 ’ScO2 Calculated ScO2 numeric 
0002-f1a1 2728 ’AnGap Calculated Anion Gap numeric 
0002-f1a4 4868 EE Energy Expenditure numeric 
0002-f1a5 4872 ΔE Energy balance calculated by Metabolics numeric 
0002-f1ac AWVneg Negative Airway Volume numeric 
0002-f1b0 Valv Alveolar Volume numeric 
0002-f1b4 bbVCO2 Breath-by-Breath CO2 Elimination numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-84
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f1b8 4880 appVd Apparatus Dead Space numeric 

0002-f1bc PLTHpr Pre Ductal Pleth numeric 
0002-f1c0 SpO2pr SpO2 Pre Ductal Label numeric 
0002-f1d0 PLTHpo Post Ductal Pleth numeric 
0002-f1d4 SpO2po SpO2 Post Ductal Label numeric 
0002-f1dc PerfPo Relative Perfusion Post Ductal Label numeric 
0002-f1e4 SQI Signal Quality Index of Pre Ductal SpO2 numeric 
Label

0002-f22c PerfPr Relative Perfusion Pre Ductal Label numeric 

0002-f3f4 1024 P5 Non-specific label for Pressure 5 numeric  
0002-f3f5 P5s Non-specific label for P5 (systolic) numeric  
0002-f3f6 P5d Non-specific label for P5 (diastolic) numeric  
0002-f3f7 P5m Non-specific label for P5 (mean) numeric  
0002-f3f8 1028 P6 Non-specific label for Pressure 6 numeric  
0002-f3f9 P6s Non-specific label for P6 (systolic) numeric  
0002-f3fa P6d Non-specific label for P6 (diastolic) numeric  
0002-f3fb P6m Non-specific label for P6 (mean) numeric  
0002-f3fc 1032 P7 Non-specific label for Pressure 7 numeric  
0002-f3fd P7s Non-specific label for P7 (systolic) numeric  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-85
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f3fe P7d Non-specific label for P7 (diastolic) numeric  

0002-f3ff P7m Non-specific label for P7 (mean) numeric  
0002-f400 1036 P8 Non-specific label for Pressure 8 numeric  
0002-f401 P8s Non-specific label for P8 (systolic) numeric  
0002-f402 P8d Non-specific label for P8 (diastolic) numeric  
0002-f403 P8m Non-specific label for P8 (mean) numeric  
0002-F404 IAP Intra Abdominal Pressure numeric 
0002-f411 1844 Rf-I ST Reference Value for Lead I numeric 
0002-f412 1848 Rf-II ST Reference Value for Lead II numeric 
0002-f413 1868 Rf-V1 ST Reference Value for Lead V1 numeric 
0002-f414 1872 Rf-V2 ST Reference Value for Lead V2 numeric 
0002-f415 1876 Rf-V3 ST Reference Value for Lead V3 numeric 
0002-f416 1880 Rf-V4 ST Reference Value for Lead V4 numeric 
0002-f417 1884 Rf-V5 ST Reference Value for Lead V5 numeric 
0002-f418 1888 Rf-V6 ST Reference Value for Lead V6 numeric 
0002-f44d 1852 Rf-III ST Reference Value for Lead III numeric 
0002-f44e 1856 Rf-aVR ST Reference Value for Lead aVR numeric 
0002-f44f 1860 Rf-aVL ST Reference Value for Lead aVL numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-86
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f450 1864 Rf-aVF ST Reference Value for Lead aVF numeric 

0002-f810 3016 Age Actual age of patient, measured in years numeric  
0002-f811 1064 G.Age Gestational Age for neonatal numeric 
0002-f812 1084 BSA(B) BSA formula: Boyd numeric 
0002-f813 1088 BSA(D) BSA formula: Dubois numeric 
0002-f814 3712 r Correlation Coefficient numeric 
0002-f815 1296 SpAWRR Spontaneous Airway Respiration Rate numeric 
0002-f816 3708 TC Time constant numeric 
0002-f817 2752 'BE,B Calculated Base Excess in Blood numeric 
0002-f818 1056 Length Length for neonatal/pediatric numeric 
0002-f819 3744 RSBI Rapid Shallow Breathing Index numeric  
0002-f81a 3704 C20/C Overdistension Index numeric 
0002-f81b 1792 extHR Denotes a Heart Rate received from an numeric 
external device

0002-f81c 4528 HI Heather Contractility Index numeric 

Delivered by C3 Monitor

0002-f81d 1600 ALP Alkaline Phosphatase numeric 

0002-f81e 3312 etAGTs End Tidal Anesthetic Agent -Secondary numeric 
Agent

0002-f81f 3308 inAGTs Inspired Gas Analyzer Agent -Secondary numeric 

Agent

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-87
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f820 3300 AGTs Anesthetic Agent - Secondary Agent numeric 

0002-f821 2724 'BEecf Calculated Base Excess numeric 
0002-f822 3720 iCa(N) Ionized Calcium Normalized (N) numeric 
0002-f823 4372 ’iCa-N Ionized Calcium Normalized numeric 
0002-f824 1436 SerCa Calcium in Serum numeric 
0002-f825 1416 tCO2 Total of CO2 - result of Blood Gas Analysis numeric 
0002-f826 2700 ’tCO2 Calculated total CO2 numeric 
0002-f827 384 SCrea Serum Creatinine numeric 
0002-f828 3060 SpRR Spontaneous Respiration Rate numeric 
0002-f829 1468 SerGlo Serum Globulin numeric 
0002-f82a 1424 SerGlu Serum Glucose numeric 
0002-f82b 2612 'Hb Calculated Hemoglobin numeric 
0002-f82c 1500 MCHC Mean Corpuscular Hemoglobin numeric 
Concentration

0002-f82e 2720 'HCO3 Calculated HCO3 numeric 

0002-f82f 1452 SerK Kalium (Potassium) in Urine numeric 
0002-f830 436 UrNaEx Urine Sodium Excretion numeric 
0002-f832 2688 &PaCO2 Computed PaCO2 at Patient Temperature on numeric 
the arterial blood

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-88
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f833 2696 &PcCO2 Computed PcO2 at Patient Temperature numeric 

0002-f834 2684 &PCO2 Computed PcO2 at Patient Temperature numeric 
0002-f835 2692 &PvCO2 Computed PvCO2 at Patient Temperature numeric 
0002-f836 2636 &pHa Adjusted pH in the arterial Blood numeric 
0002-f837 2644 &pHc Adjusted pH value in the capillaries numeric 
0002-f838 2632 &pH Adjusted pH at Patient Temperature numeric 
0002-f839 2640 &pHv Adjusted pH value in the venous Blood numeric 
0002-f83b 2660 &PaO2 Adjusted PaO2 at Patient Temperature on the numeric 
arterial blood

0002-f83c 2668 &PcO2 Adjusted PcO2 at Patient Temperature numeric 

0002-f83d 2656 &PO2 Adjusted PO2 at Patient Temperature numeric 
0002-f83e 2664 &PvO2 Adjusted PvO2 at Patient Temperature numeric 
0002-f83f 288 COsm Osmolar Clearance numeric 
0002-f840 4504 BSI Burst Suppression Indicator numeric 
0002-f841 2056 LSCALE Scale of the Left Channel EEG wave numeric 
0002-f842 2116 RSCALE Scale of the Right Channel EEG Wave numeric 
0002-f845 2032 LT EEG Left channel EEG wave numeric 
0002-f846 2092 RT EEG Left channel EEG wave numeric 
0002-f849 2036 LT MDF Mean Dominant Frequency, Left Side numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-89
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f84a 2096 RT MDF Mean Dominant Frequency, Right Side numeric 

0002-f84b 2040 LT MPF Median Power Frequency, Left Side numeric 
0002-f84c 2100 RT MPF Median Power Frequency, Right Side numeric 
0002-f84f 2044 LT PPF Peak Power Frequency, Left Side numeric 
0002-f850 2104 RT PPF Peak Power Frequency, Right Side numeric 
0002-f853 2048 LT SEF Spectral Edge Frequency, Left Side numeric 
0002-f854 2108 RT SEF Spectral Edge Frequency, Right Side numeric 
0002-f855 2016 LT AL Absolute Alpha, Left Side numeric 
0002-f856 2076 RT AL Absolute Alpha, Right Side numeric 
0002-f859 2000 LT %AL Percent Alpha, Left (LT) Side numeric 
0002-f85a 2060 RT %AL Percent Alpha, Right (RT) Side numeric 
0002-f85b 2020 LT BE Absolute Beta, Left Side numeric 
0002-f85c 2080 RT BE Absolute Beta, Right Side numeric 
0002-f85f 2004 LT %BE Percent Beta, Left Side numeric 
0002-f860 2064 RT %BE Percent Beta, Right Side numeric 
0002-f863 2024 LT DL Absolute Delta, Left Side numeric 
0002-f864 2084 RT DL Absolute Delta, Right Side numeric 
0002-f867 2008 LT %DL Percent Delta, Left Side numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-90
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f868 2068 RT %DL Percent Delta, Right Side numeric 

0002-f869 2028 LT TH Absolute Theta, Left Side numeric 
0002-f86a 2088 RT TH Absolute Theta, Right Side numeric 
0002-f86d 2012 LT %TH Percent Theta, Left Side numeric 
0002-f86e 2072 RT %TH Percent Theta, Right Side numeric 
0002-f871 2052 LT TP Total Power, Left Side numeric 
0002-f872 2112 RT TP Total Power, Right Side numeric 
0002-f873 4500 AAI A-Line ARX Index numeric 
0002-f874 4508 vECG Vector ECG taken from the ICG “sensor”. numeric 
Delivered by C3 Monitor

0002-f875 1324 O2EI Oxygen Extraction Index numeric 

0002-f876 1312 fgAGT Fresh gas Anesthetic Agent numeric 
0002-f877 4540 fgAir Fresh Gas Flow of Air. Delivered by the numeric 
ADU from Datex VueLink

0002-f878 2132 fgDES Fresh gas agent for DESflurane numeric 

0002-f879 2144 fgENF Fresh gas agent for ENFlurane numeric 
0002-f87a 4560 eeFlow End-Expiratory Flow. Delivered by the numeric  
Servi-I Ventilator

0002-f87b 2140 fgHAL Fresh gas agent for HALothane numeric 

0002-f87c 2148 fgISO Fresh gas agent for ISOflurane numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-91
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f87d 1164 SpPkFl Spontaneous Peak Flow numeric  

0002-f87e 2152 fgN2O N2O concentration in the fresh gas line numeric 
0002-f87f 2156 fgO2 Oxygen concentration in the fresh gas line numeric 
0002-f880 2136 fgSEV Fresh gas agent for SEVoflurane numeric 
0002-f881 4544 fgFlow Total Fresh Gas Flow. Delivered by the numeric 
ADU from Datex VueLink

0002-f882 4548 VCO2ti CO2 Tidal Production. Delivered by the numeric 

Servi-I Ventilator

0002-f883 3032 U/O Daily Urine output numeric 

0002-f884 280 CH2O Free Water Clearance numeric 
0002-f885 1496 MCH Mean Corpuscular Hemoglobin (erythocyte numeric 
hemoglobin content)

0002-f886 2908 Power Power required to the Air & Patient numeric 
Temperature in incubator

0002-f887 33040 Model Enumeration Type - denotes type of setting  

instrument

0002-f888 4512 ICG Impedance Cardiography Waveform numeric 

Delivered by C3 Monitor

0002-f889 4524 ACI Accelerated Cardiac Index. Delivered by numeric  

Philips C3 monitor

0002-f88a 2920 PatID Patient ID string 

0002-f88b 3512 PTC Post Tetatic Count stimulation numeric 
0002-f88d 1300 PlGain Pleth Gain numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-92
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f88e 3716 RVrat Rate Volume Ratio numeric 

0002-f88f 272 BUN/cr BUN Creatinine Ratio numeric 
0002-f890 2784 ’B/Cre Ratio BUN/Creatinine numeric 
0002-f891 2788 ’U/Cre Ration Urea/Creatinine numeric 
0002-f892 412 U/SCr Urine Serum Creatinine Ratio numeric 
0002-f893 432 UrNa/K Urine Sodium/Potassium Ratio numeric 
0002-f894 3040 PaFIO2 PaO2 to FIO2 ratio numeric 
Expressed in mmHg to % ratio

0002-f895 3624 PTrat Prothrombin time ratio numeric 

0002-f896 3612 PTTrat Activated Partial Thromboplastin time Ratio numeric 
0002-f897 3504 TOFrat Train of Four Ratio numeric 
0002-f898 408 U/POsm Urine Plasma Osmolarity Ratio numeric  
0002-f899 1152 Rdyn Dynamic Lung Resistance numeric 
0002-f89a 2124 RRsync Sync Breath Rate numeric 
0002-f89b 1328 REF Right Heart Ejection Fraction numeric 
0002-f89c 2704 'SO2 Calculated SO2 numeric 
0002-f89d 4532 SO2 l Oxygen Saturation. Left side numeric 
Somanetics Open VueLink

0002-f89e 4536 SO2 r Oxygen Saturation. Right side numeric 

Somanetics Open VueLink

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-93
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f8a0 3516 RemTi Remaining time until next stimulation numeric 

0002-f8a1 1644 ExpTi Expiratory Time numeric 
0002-f8a2 2868 Elapse Time to elapse counter numeric 
0002-f8a3 3700 InsTi Spontaneous Inspiration time numeric  
0002-f8a4 1620 KCT Kaolin Cephalin Clotting time numeric 
0002-f8a5 1504 PTT Partial Thromboplastin Time numeric 
0002-f8a7 3520 TOF1 Train of Four first response value numeric 
0002-f8a8 3524 TOF2 Train of Four first response value TOF2 numeric 
0002-f8a9 3528 TOF3 Train of Four first response value TOF3 numeric 
0002-f8aa 3532 TOF4 Train of Four first response value TOF4 numeric 
0002-f8ab 3500 TOFcnt Train of Four (TOF) count - number of TOF numeric 
responses

0002-f8ac 3508 Twitch Twitch height of the 1Hz/0.1Hz stimulation numeric 

response

0002-f8ad 1476 SrUrea Serum Urea numeric 

0002-f8b0 3036 PtVent Parameter which informs whether Patient is string 
ventilated

0002-f8b1 1372 HFVAmp High Frequency Ventilation Amplitude numeric 

0002-f8b2 1696 i-eAGT Inspired - End Tidal Agent numeric 
0002-f8b3 1692 i-eDES Inspired - End Tidal Desflurane numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-94
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f8b4 1680 i-eENF Inspired - End Tidal Enflurane numeric 

0002-f8b5 1676 i-eHAL Inspired - end Tidal Halothane numeric 
0002-f8b6 1684 i-eISO Inspired - End Tidal Isoflurane numeric 
0002-f8b7 1672 i-eN2O Inspired - end Tidal N2O numeric 
0002-f8b8 1704 cktO2 O2 measured in the Patient Circuit numeric 
0002-f8b9 1688 i-eSEV Inspired - End Tidal Sevoflurane numeric 
0002-f8ba 40964 loPEEP Alarm Limit: Low PEEP/CPAP setting 
0002-f8bb 1656 Pmax Maximum Pressure during a breathing cycle numeric 
0002-f8bc 1132 PVcP Pressure Ventilation Control Pressure numeric 
0002-f8bd 1360 RiseTi Rise Time numeric 
0002-f8be 1764 HFTVin Inspired High Frequency Tidal Volume numeric 
0002-f8bf 1768 HFVTV High Frequency Fraction Ventilation Tidal numeric 
Volume

0002-f8c1 1940 AWVexp Expiratory Airway Volume Wave numeric 

0002-f8c2 1760 SpTVex Spontaneous Expired Tidal Volume numeric 
0002-f8c3 3736 TVPSV Tidal Volume (TV) in Pressure Support numeric 
Ventilation mode

0002-f8c4 1492 MCV Mean Corpuscular Volume numeric 

0002-f8c5 4516 TFC Thoracic Fluid Content -Delivered by C3 numeric  
Monitor

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-95
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f8c6 4520 TFI Thoracic Fluid Content Index -Delivered by numeric  

C3 Monitor

0002-f8c7 2160 AGTLev Liquid Level in the anesthetic agent bottle numeric 
0002-f8c8 2176 DESLev Liquid Level in the DESflurane bottle numeric  
0002-f8c9 2168 ENFLev Liquid Level in the ENFlurane bottle numeric  
0002-f8ca 2172 HALLev Liquid Level in the HALothane bottle numeric  
0002-f8cb 2164 ISOLev Liquid Level in the ISOflurane bottle numeric  
0002-f8cc 2180 SEVLev Liquid Level in the SEVoflurane bottle numeric  
0002-f8cd 1752 HFMVin Inspired High Frequency Mandatory Minute numeric 
Volume

0002-f8ce 3004 tUrVol Total Urine Volume of the current numeric 

measurement period

0002-f8cf 2188 UrVSht Urimeter - Urine Shift Volume numeric 

0002-f8d0 1340 EDVI End Diastolic Volume Index numeric 
0002-f8d1 1344 ESVI End Systolic Volume Index numeric 
0002-f8d2 33136 Wave Wave Label setting 
0002-f8d3 3000 BagWgt Weight of the Urine Disposable Bag numeric 
0002-f95c 4848 rSO2-1 Regional Oxygen Saturation (1) numeric 
0002-f95d 4852 rSO2-2 Regional Oxygen Saturation (2) numeric 
0002-f95e 4856 rSO2-3 Regional Oxygen Saturation(3) numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-96
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f95f 4860 rSO2-4 Regional Oxygen Saturation(4) numeric 

0002-f960 4788 StO2 Saturated O2 Tissue numeric 
0002-f961 4792 CSI Cerebral State Index, indicates the level of string 
consciousness

0002-f962 4756 SO2 1 Generic Oxygen Concentration - Channel 1 numeric 

0002-f963 4760 SO2 2 Generic Oxygen Concentration - Channel 2 numeric 
0002-f964 4764 SO2 3 Generic Oxygen Concentration - Channel 3 numeric 
0002-f965 4768 SO2 4 Generic Oxygen Concentration - Channel 4 numeric 
0002-f966 4772 T1Core Core Temperature 1 numeric 
0002-f967 4776 T2Core Core Temperature 2 numeric 
0002-f968 4684 ΔP Pressure Difference numeric 
0002-f96c 4688 ΔP1 Generic Pressure Difference 1 numeric 
0002-f970 4692 ΔP2 Generic Pressure Difference 2 numeric 
0002-f974 4660 HLMfl Mean Corpuscular Hemoglobin - numeric 
Arterial / Main Pump Flow of Heart Lung
Machine

0002-f975 4664 SlvPfl Slave Pump flow of Heart Lung Machine numeric 
0002-f976 4668 SucPfl Suction Pump flow of Heart Lung Machine numeric 
0002-f977 4672 AuxPfl Auxiliary Pump flow of Heart Lung Machine numeric 
0002-f978 4676 PlePfl Main Cardioplegia Pump flow of Heart Lung numeric 
Machine

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-97
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f979 4680 SplPfl Slave Cardioplegia Pump flow of Heart numeric 

Lung Machine

0002-f97a 4696 AxOnTi Auxiliary Pump time since start of the numeric 
ongoing plegia session

0002-f97b 4700 AxOffT Auxiliary Pump time since stop of the numeric 
ongoing plegia session

0002-f97c 4704 AxDVol Auxiliary Pump delivered volume in numeric 

ongoing/last plegia session

0002-f97d 4708 AxTVol Auxiliary Pump Total Volume numeric 

0002-f97e 4712 AxPlTi Auxiliary Pump Total Plegia Time numeric 
0002-f97f 4716 CpOnTi Cardioplegia Main Pump time since start of numeric 
the ongoing plegia session

0002-f980 4720 CpOffT Cardioplegia Main Pump time since stop of numeric 
the ongoing plegia session

0002-f981 4724 CpDVol Cardioplegia Main Pump delivered volume numeric 

in ongoing/last plegia session

0002-f982 4728 CpTVol Cardioplegia Main Pump total volume numeric 

0002-f983 4732 CpPlTi Cardioplegia Main Pump total plegia time numeric 
0002-f984 4736 CsOnTi Cardioplegia Slave Pump time since start of numeric 
the ongoing plegia session

0002-f985 4740 CsOffT Cardioplegia Slave Pump time since stop of numeric 
the ongoing plegia session

0002-f986 4744 CsDVol Cardioplegia Slave Pump delivered volume numeric 

in ongoing/last plegia session

0002-f987 4748 CsTVol Cardioplegia Slave Pump total volume numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-98
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f988 4752 CsPlTi Cardioplegia Slave Pump total plegia time numeric 
0002-f989 4928 AVPU Alert, Voice, Pain, Unresponsive numeric 
0002-f98a 4800 EWS Early Warning Score string 
0002-f98b 4804 Concrn Determines if Caregiver should be concerned string 
about patient status

0002-f98c 4808 Pain Pain level of patient string 

0002-f990 4816 Tin/Tt Ratio of inspiratory time to total breath cycle numeric  
time measurements

0002-f991 4824 tPEEP Total Positive End Expiratory Pressure numeric  

0002-f992 4828 Cpav PAV-based Lung compliance numeric  
0002-f993 4836 Rpav PAV-based Patient resistance numeric  
0002-f994 4840 Rtot Total resistance estimate numeric  
0002-f995 4832 Epav PAV-based Lung elastance numeric  
0002-f996 4844 RSBInm Normalized Rapid Shallow Breathing Index numeric  
0002-f9c0 4904 RRasst Rate of non-spontaneous (-assisted) numeric 
respiration cycles of a ventilated patient

0002-f9f1 4920 MEWS Modified Early Warning Score string 

0002-f9f2 4924 SPS SPS Score string 
0002-f9f3 4796 LOC Level of Consciousness Score (AVNPU) string 
0002-f9f5 4932 Brthng Patient Status, Breathing string 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-99
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0002-f9f6 4936 Airway Patient Status, Airway string 

0002-f9f7 4940 CnsSt Patient Status, Consciousness State string 
0002-f9f8 4944 Urine Observed Urine string 
0002-f9f9 4908 r2 Airway Corr. Coefficient r squared numeric 
0002-f9fa 4912 E Lung Elasticity numeric 
0002-f9fe 4916 Ptrach Trachea Pressure numeric 
0002-faf4 4952 NI Narcotrend Index derived from EEG (100 = numeric 
awake, 0 = very deep hypnosis)

0002-faf5 4956 STI Sharp Transient Intensity derived from EEG numeric 
0402-4b48 33232 sTemp Setting: Desired Temperature for the setting 
Incubator/Warmer

0402-5012 32772 sAWRR Setting: Airway Respiratory Rate setting 

0402-5022 33068 sRRaw Setting: Airway Respiration Rate. Used by setting  
the Ohmeda Ventilator

0402-50dd 32780 sPIF Setting: Peak Inspiratory Flow setting  

0402-50f2 33024 sPmin Setting: Low Inspiratory Flow setting 
0402-50f4 33012 sCPAP Setting: Continuous Positive Airway setting 
Pressure Value

0402-5108 33064 sPin Setting: Inspiratory Pressure. Used by the setting  

Ohmeda Ventilator

0402-5109 33020 sPIP Setting: Positive Inspiratory Pressure setting 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-100
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-5118 33004 sIE 1: Setting: Inspiration to Expiration Ratio setting 

0402-513c 32776 sTV Setting: Tidal Volume setting  
0402-5148 32944 sMV Setting: Minute Volume setting 
0402-5164 33036 sO2 Setting: Oxygen Concentration in % setting 
0402-51a8 32936 sPEEP Setting: PEEP/CPAP setting  
0402-51b8 33080 sTrVol Setting: Trigger Flow/Volume setting 
0402-51cc 33052 sMMV Setting: Mandatory Minute Volume setting 
0402-51d8 33192 sDES Setting: Vaporizer concentration for setting 
DESflurane

0402-51dc 33184 sENF Setting: Vaporizer concentration for setting 

ENFlurane

0402-51e0 33188 sHAL Setting: Vaporizer concentration for setting 

HALothane

0402-51e4 33196 sSEV Setting: Vaporizer concentration for setting 

SEVoflurane

0402-51e8 33180 sISO Setting: Vaporizer concentration for setting 

ISOflurane

0402-536c 33424 sPsens Setting: Pressure sensitivity setting  

0402-6840 33480 sDConc Setting: Drug Concentration setting 
0402-6858 33060 sDRate Setting: Infusion Pump Delivery Rate setting 
0402-686c 33484 sDlvRt Setting: Drug Delivery setting 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-101
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-68a4 33488 sVBol Setting: Fluid Volume Bolus setting 

0402-68bc 33492 sVtot Setting: Fluid Volume setting 
Total Volume to be infused (TBI)

0402-68e0 33496 sKVO Setting: Keep Vein Open (KVO) Flow Rate setting 
0402-68e4 33500 sDosRt Setting: Dose Rate setting 
0402-7498 32784 sFIO2 Setting: Inspired Oxygen Concentration setting  
0402-d00a 33504 sDrug Setting: Drug Name/Type setting 
0402-d0b8 33508 sPuMod Setting: Pump Mode setting 
0402-f0e0 33228 sTVin Setting: Inspired Tidal Volume setting 
0402-f0ff 32792 sPltTi Setting: Plateau Time setting  
0402-f103 33416 sHum Humidity from Incubator setting 
0402-f876 33176 sAGT Setting: Vaporizer concentration setting 
0402-f877 33200 sfgAir Setting: Total fresh gas air flow on the mixer setting 
0402-f87e 33212 sfgN2O Setting: fresh gas N2O flow on the mixer setting 
0402-f87f 33204 sfgO2 Setting: Fresh gas oxygen Flow on the mixer setting 
0402-f881 33208 sfgFl Setting: Total fresh gas Flow on the mixer setting 
0402-f8a6 33288 sRepTi Setting: Preset Train of Four repetition time setting 
0402-f8af 33236 sUrTi Setting: Preset period of time for the UrVol setting 
numeric

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-102
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f8bb 32992 sPmax Setting: Maximum Pressure setting  

0402-f8bc 32824 sPSV Setting: Pressure Support Ventilation setting  
0402-f8bd 33412 sRisTi Rise Time setting  
0402-f8c0 32800 sSghTV Setting: Sigh Tidal Volume setting 
0402-f8d8 32896 sSilnc Setting. Alarm Silence Status setting  
0402-f8d9 33084 sAADel Setting: Apnea Alarm Delay setting  
0402-f8da 40976 liPVAT Pressure Ventilation Apnea time interval setting 
0402-f8db 33120 sCO2Al CO2 Alarm setting 
0402-f8dc 32828 sPWave Setting. Pressure Waveform setting  
0402-f8de 32812 sARR Setting: Apnea Respiration Rate setting  
0402-f8df 33032 sHFVRR Setting: High Frequency Ventilation setting 
Respiration Rate

0402-f8e0 33144 sAgent Enumeration setting: shows current selected setting 

Agent

0402-f8e6 33280 sChrge Setting: Preset stimulation charge setting 

0402-f8e7 33276 sCurnt Setting: Preset stimulation current setting 
0402-f8ea 33076 sExpFl Setting: Expiratory Flow setting 
0402-f8eb 33028 sHFVFl Setting: High Frequency Ventilation Flow setting 
0402-f8ec 33072 sInsFl Setting: Inspiratory Flow setting 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-103
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f8ed 32816 sAPkFl Setting: Apnea Peak Flow setting  

0402-f8f1 33108 sFlCal Apnea Peak Flow setting 
0402-f8f3 33088 sHFVAm Setting: HFV Amplitude setting 
0402-f8f5 32920 sMode Setting: Apnea Pressure Ventilation Oxygen setting 
Concentration

0402-f8f6 33124 sPtCat Enumeration Setting: Patient Category setting  

(Patient Type)

0402-f8f7 40996 sBPAl Rate Volume Ratio setting 

0402-f8fb 33140 loPmax Setting: Low Maximum Airway pressure setting 
alarm setting

0402-f8fd 33128 sOxiAl Apnea Pressure Ventilation Inspiratory setting 

component of I:E Ratio

0402-f8fe 41000 sPStat General status of infusion pump setting  

0402-f900 32904 sPVE Setting: Pressure Ventilation E component of setting  
I:E Ratio

0402-f901 32912 sAPVE Setting: Apnea Pressure Ventilation E setting  

component of I:E Ratio

0402-f902 32900 sPVI Setting: Pressure Ventilation I component of setting  

I:E Ratio

0402-f903 32908 sAPVI Setting: Apnea Pressure Ventilation I setting 

component of I:E Ratio

0402-f904 33160 sSens Setting: Assist Sensitivity. Used by the Bear setting  
1000 Ventilator

0402-f905 32952 sEnTP Setting: Tachy apnea Warning setting 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-104
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f906 32976 sTPDel Setting: Agent Monitoring in warm up mode setting 

0402-f908 33284 sPulsD Setting: Preset stimulation impulse duration setting 
0402-f909 32924 sCycTi Setting: Cycle Time setting 
0402-f90b 33456 sTrgLv Trigger level/sensitivity setting 
0402-f90c 32948 sEnTrg Enable Trigger setting 
0402-f90d 33132 sAGTWm Agent Monitoring in Low Accuracy (Warm setting 
Up)

0402-f90e 32980 sO2Mon Setting: O2 Monitoring setting 

0402-f90f 33168 sBkgFl Setting: Background flow setting. Range is setting 
2-30 l/min

0402-f910 32856 sBasFl Setting: Flow-by Base Flow setting  

0402-f911 32860 sSenFl Setting: Flow-by Sensitivity Flow setting  
0402-f912 33100 sPincR Setting: Pressure Increase Rate setting 
0402-f913 33224 sCircl Setting: Type of circle in the patient system setting 
0402-f914 33248 CO2Cal Enumeration or CO2 Calibration active setting  
0402-f915 33116 sCO2Wm Setting: CO2 Warming setting 
0402-f917 32820 sAFIO2 Setting: Apnea Inspired O2 Concentration setting  
0402-f918 32888 sAPVO2 Setting: Apnea Pressure Ventilation Oxygen setting 
Concentration

0402-f919 40992 highO2 Alarm Limit: High Oxygen (O2) Alarm setting 
Limit

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-105
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f91a 40988 lowO2 Alarm Limit: Low Oxygen (O2) Alarm Limit setting 
0402-f91b 33016 sFlow Setting: Flow setting 
0402-f91c 33272 sFlas Setting: Flow Assist level for the CPAP setting 
mode

0402-f91d 33096 sTrgFl Setting: Flow Trigger - delivered by the setting  

Evita 2 Vuelink driver

0402-f91e 33056 sFWave Setting. Flow Pattern (enumeration type) setting  

0402-f91f 33244 GasCar Selected Gas Carrier setting  
0402-f920 33216 sGasPr Setting: Gas Sample point for the oxygen setting 
measurement

0402-f921 32768 sVMode Setting: Ventilation Mode setting  

0402-f922 33044 sCMV Setting: Controlled mechanical ventilation setting 
0402-f923 32832 sEnSgh Setting: Enable Sigh setting 
0402-f924 33048 sSIMV Setting: Synchronized intermittent setting 
Mandatory Ventilation

0402-f925 32836 sNeblr Setting. Nebulizer setting  

0402-f926 32984 sO2Cal Setting: O2 Calibration setting 
0402-f927 33220 sO2Pr Setting: Gas Sample point for oxygen setting 
measurement

0402-f928 32840 sO2Suc Setting: Suction Oxygen Concentration setting  

0402-f929 32960 BPAPPH BIPAP Pressure Level 2 - High setting  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-106
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f92a 32956 BPAPPL BIPAP Pressure Level 1 - Low setting  

0402-f92c 32940 sSPEEP Setting: Pressure Support setting  
0402-f92d 33260 sPlow Setting: part of the Evita 4 Airway Pressure setting 
Release Ventilation Mode

0402-f92e 33264 sPhigh Setting: part of the Evita 4 Airway Pressure setting 
Release Ventilation Mode

0402-f930 40960 highP Alarm Limit: High Pressure setting 

0402-f931 32892 sAPVhP Setting: Apnea Pressure Ventilation High setting 
Airway pressure

0402-f933 32876 sAPVcP Setting: Apnea Pressure Ventilation Control setting  

pressure

0402-f934 40968 hiSghP Coagulation time setting 

0402-f935 40980 sustP Alarm Limit: Sustained Pressure Alarm setting 
Limit

0402-f937 33292 sfmax Setting Panting Limit setting 

0402-f938 32932 sIMV Setting: Ventilation Frequency in IMV Mode setting 
0402-f939 32928 sIPPV Setting: Ventilation Frequency in IPPV setting 
Mode

0402-f93a 32880 sAPVRR Setting: Apnea Pressure Ventilation setting 

Respiration Rate

0402-f93b 32804 sSghNr Setting: Multiple Sigh Number setting 

0402-f93c 32796 sSghR Setting: Sigh Rate setting 
0402-f93d 32968 BPAPTH BIPAP Pressure Time 2 - High setting  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-107
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f93e 32964 BPAPTL BIPAP Pressure Time 1 - Low setting  

0402-f93f 33000 sExpTi Setting: Exhaled Time setting  
0402-f940 33252 sTlow Setting: Part of the Evita 4 Airway Pressure setting 
Release Ventilation Mode

0402-f941 32996 sInsTi Setting: Inspiratory Time setting  

0402-f942 33256 sThigh Setting: part of the Evita 4 Airway Pressure setting 
Release Ventilation Mode

0402-f943 32872 sPVinT Setting: Pressure Ventilation Inspiratory setting 

Time

0402-f944 32884 sAPVTi Setting: Apnea Pressure Ventilation setting  

Inspiratory time

0402-f946 33008 sALMRT Setting: Alarm Percentage on Rise Time setting 

0402-f947 33112 sVolAl Vaporizer concentration for ENFlurane setting 
0402-f948 33268 sVolas Setting: Volume Assist level for the CPAP setting 
mode

0402-f949 33104 sVmax Setting: Volume warning - delivered by the setting 

Evita 2 Vuelink driver

0402-f94b 41004 highMV Alarm Limit: High Minute Volume Alarm setting 
Limit

0402-f94c 40984 lowMV Alarm Limit: Low Minute Volume Alarm setting 
Limit

0402-f94d 41012 highTV Alarm Limit: High Tidal Volume Alarm setting 
Limit

0402-f94e 41008 lowTV Alarm Limit: Low Tidal Volume Alarm setting 
Limit

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-108
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f951 32808 sATV Setting: Apnea Tidal Volume setting  

0402-f952 33156 sTVap Setting: Applied Tidal Volume setting 
0402-f953 33092 sMVDel Setting: Minute Volume Alarm Delay setting 
0402-f955 32988 sMVAl Setting: Alarm Silence Status setting 
0402-f956 2732 Sample Blood Sample Source setting 
0402-f957 2736 Cartrg Cartridge Type string 
0402-f958 2740 OperID Operator ID string 
0402-f959 2760 Field1 Free Field #1 - permits entry of unspecific setting 
data

0402-f95a 2764 Field2 Free Field #2 - permits entry of unspecific setting 

data

0402-f95b 2768 Field3 Free Field #3 setting 

Permits entry of unspecific data

0402-f98d 33428 sSenEx Expiratory Sensitivity Setting setting  

0402-f98e 4812 PAVsup Proportional Assist Ventilation Support setting  
Level

0402-f98f 33432 sTVsup Target Support Volume setting  

0402-f997 33436 sVent Ventilator Type setting  
0402-f998 33440 sMVent Setting: Mandatory Ventilation Type setting  
0402-f999 33444 sSpVnt Setting: Spontaneous Breath Type setting  
0402-f99a 32788 sTrig Setting: Trigger Sensitivity setting  

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-109
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f99b 33448 sAFWav Setting: Apnea Flow Pattern setting  

0402-f99c 33452 sAMVnt Setting: Apnea Mandatory Type Setting setting  
0402-f9a0 33420 sRRmin Setting: Mandatory Minimum Frequency in setting  
Pressure Support Ventilation mode

0402-f9c4 33512 sRRmax Setting:High limit alarm setting for setting 

spontaneous beating rate

0402-f9c8 33516 sPADel Setting:Delay time of a ventilator (airway) setting 

pressure alarm

0402-f9cc 33520 sRRbak Setting:Backup respiration rate of ventilator setting 

If a patient's spontaneous respiration is
insufficient, the device ventilates the patient
with this backup respiration rate.

0402-f9d0 33524 sPIbak Setting:Backup inspired pressure of setting 

ventilator
If a patient's spontaneous respiration is
insufficient, the device ventilates the patient
with this backup inspired pressure.

0402-f9d4 33528 sTVbak Setting: Backup tidal volume of ventilator setting 

If a patient's spontaneous respiration is
insufficient, the device ventilates the patient
with this backup tidal volume.

0402-f9d8 33532 sTubeC Setting:Tube compensation setting of setting 

ventilator
Part of the ventilator automatic tube
compensation functionality

0402-f9dc 33536 sTubeD Setting:Tube diameter setting of ventilator setting 

Part of the ventilator automatic tube
compensation functionality

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-110
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

0402-f9e0 33540 sTimax Setting:Maximum inspiration time setting. setting 

Indicates the maximum time a ventilator
inspires if no normal respiration cycle has
been detected
This setting is mainly used for non-invasive
pressure supported ventilation.

0402-f9e8 33544 sVSupp Setting:Supplemental setting to Svmode setting 

indicates a supplemental function of the
current ventilation mode (sVMode).
Example:
sVMode = CPAP (continuous positive
airway pressure)
sVSupp = ASB (assisted spontaneous
breathing)

0402-f9ec 33548 sFlCtr Setting: (ventilator) Flow Control setting 

Indicates if ventilator automatic flow control
is on or off

0402-f9ff 33460 sHumid Setting:Humidifier type setting 

0402-fa07 33464 sΔPin Setting:Delta pressure above inspiratory setting 
pressure

0402-fa08 33468 sΔPEEP Setting: Delta pressure above Positive End- setting 
Expiratory Pressure (PEEP)

0402-fa09 33472 sTAmax Setting:Maximum allowed apnea time before setting 

controlled ventilation is activated

0402-fa12 33476 sBreaT Setting:Total Breath time/duration setting 

8003-5401 Pulse Pulse from P numeric 
8003-5402 Pulse Pulse from ABP numeric 
8003-5403 Pulse Pulse from ART numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-111
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

8003-5404 Pulse Pulse from AO numeric 

8003-5405 Pulse Pulse from PAP numeric 
8003-5406 Pulse Pulse from CVP numeric 
8003-5407 Pulse Pulse from RAP numeric 
8003-5408 Pulse Pulse from LAP numeric 
8003-5409 Pulse Pulse from ICP numeric 
8003-540a Pulse Pulse from UAP numeric 
8003-540b Pulse Pulse from UVP numeric 
8003-5422 Pulse Pulse from P1 numeric 
8003-5425 Pulse Pulse from P2 numeric 
8003-5428 Pulse Pulse from P3 numeric 
8003-542b Pulse Pulse from P4 numeric 
8003-542e Pulse Pulse from IC1 numeric 
8003-5431 Pulse Pulse from IC2 numeric 
8003-5434 Pulse Pulse from FAP numeric 
8003-5437 Pulse Pulse from BAP numeric 
800f-5401 2564 EEG1 Electroencephalogram - Channel 1 numeric 
800f-5402 2568 EEG2 Electroencephalogram - Channel 2 numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-112
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

800f-5403 2556 TP1 Total Power - EEG Channel 1 numeric  

800f-5404 2560 TP2 Total Power - EEG Channel 2 numeric  
800f-5405 2500 SEF1 Spectral Edge Frequency - EEG Channel 1 numeric  
800f-5406 2504 SEF2 Spectral Edge Frequency - EEG Channel 2 numeric  
800f-5407 2508 MDF1 Mean Dominant Frequency - EEG Channel 1 numeric  
800f-5408 2512 MDF2 Mean Dominant Frequency - EEG Channel 2 numeric  
800f-5409 2516 PPF1 Peak Power Frequency - EEG Channel 1 numeric  
800f-540a 2520 PPF2 Peak Power Frequency - EEG Channel 2 numeric  
800f-540b 2540 Alpha1 % of Power in the Alpha Band. - EEG numeric  
Channel 1

800f-540c 2544 Alpha2 % of Power in the Alpha Band. - EEG numeric  

Channel 2

800f-540d 2548 Beta1 % of Power in the Beta Band. - EEG numeric  

Channel 1

800f-540e 2552 Beta2 % of Power in the Beta Band. - EEG numeric  

Channel 2

800f-540f 2532 Theta1 % of Power in the Theta Band. - EEG numeric  

Channel 1

800f-5410 2536 Theta2 % of Power in the Theta Band. - EEG numeric  

Channel 2

800f-5411 2524 Delta1 % of Power in the Delta Band. - EEG numeric  

Channel 1

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-113
Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

800f-5412 2528 Delta2 % of Power in the Delta Band. - EEG numeric  

Channel 2

800f-54132 Frequ1 Frequency - EEG Channel 1 numeric 

800f-54141 Frequ2 Frequency - EEG Channel 2 numeric 
800f-54151 Prcnt1 Percent - EEG Channel 1 numeric 
800f-54161 Prcnt2 Percent - EEG Channel 2 numeric 
800f-5417 2572 CSA1 Compressed Spectral Array - Channel 1 numeric 
800f-5418 2576 CSA2 Compressed Spectral Array - Channel 2 numeric 
8015-5401 Pulse SpO2 Pulse Rate - Left numeric 
8015-5402 Pulse SpO2 Pulse Rate - Right numeric 
8015-543d Pulse SpO2 Pulse Rate - Post Ductal numeric 
8015-5440 Pulse SpO2 Pulse Rate - Pre Ductal numeric 
8015-546e SQI Signal Quality Index of Left SpO2 Label numeric 
8015-5471 SQI Signal Quality Index of Right SpO2 Label numeric 
8015-5474 SQI Signal Quality Index of Pre Ductal SpO2 numeric 
Label

8015-5477 SQI Signal Quality Index of Post Ductal SpO2 numeric 

Label

8015-547a SQI Signal Quality Index of Telemetry SpO2 numeric 

Label

805a-5401 AGT1 Gas Analyzer Agent - Channel 1 numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-114
 Shared Segment Profile Definitions (Across Integration Profiles)

VueLink
MDIL Code EMFC Code Parameter Label Description Type IIC
IntelliBridge

805a-5402 AGT2 Gas Analyzer Agent - Channel 2 numeric 

805a-5404 etAGT1 End Tidal Gas Analyzer Agent - Channel 1 numeric 
805a-5405 inAGT1 Inspired Gas Analyzer Agent - Channel 1 numeric 
805a-5406 etAGT2 End Tidal Gas Analyzer Agent - Channel 2 numeric 
805a-5407 inAGT2 Inspired Gas Analyzer Agent - Channel 2 numeric 
1. Respiration appears as both RR and RESP, depending on the bedside type.
2. Label is not SCADA label but privateTextId from the EEG_NAMES set of TextIds.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-115
Shared Segment Profile Definitions (Across Integration Profiles)

MRx Device Parameter List for Possible Coded Values for OBX.5

MDIL code Parameter Label Description Type IIC

0002-4182 HR Heart Rate numeric 

0002-4261 PVC 1 Premature Ventricular Counted Beats numeric 
0002-4bb8 SpO2 SpO2 parameter label numeric 
0002-480a Pulse Pulse Rate numeric 
0002-50b0 etCO2 End-Tidal CO2 Concentration numeric 
0002-5012 AwRR Airway Respiration Rate numeric 
0002-4a05 NBPs Non-invasive blood pressure (systolic) numeric 
0002-4a06 NBPd Non-invasive blood pressure (diastolic) numeric 
0002-4a07 NBPm Non-invasive blood pressure (mean) numeric 
0002-4a15 ABPs ABP (systolic) numeric 
0002-4a16 ABPd ABP (diastolic) numeric 
0002-4a17 ABPm ABP (mean) numeric 
0002-5804 CPP2 Cerebral Perfusion Pressure numeric 
0002-4a11 ARTs ART (systolic) numeric 
0002-4a12 ARTd ART (diastolic) numeric 
0002-4a13 ARTm ART (mean) numeric 
0002-4a0d AoS Ao (systolic) numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-116
 Shared Segment Profile Definitions (Across Integration Profiles)

MDIL code Parameter Label Description Type IIC

0002-4a0e AoD Ao (diastolic) numeric 

0002-4a0f AoM Ao (mean) numeric 
0002-f0a5 P1s Generic invasive pressure P1 (systolic) numeric 
0002-f0a6 P1d Generic invasive pressure P1 (diastolic) numeric 
0002-f0a7 P1m Generic invasive pressure P1 (mean) numeric 
0002-f0a9 P2s Generic invasive pressure P2 (systolic) numeric 
0002-f0aa P2d Generic invasive pressure P2 (diastolic) numeric 
0002-f0ab P2m Generic invasive pressure P2 (mean) numeric 
0002-4a45 CVPs CVP (systolic) numeric 
0002-4a46 CVPd CVP (diastolic) numeric 
0002-4a47 CVPm CVP (mean) numeric 
0002-4a35 RAPs RAP (systolic) numeric 
0002-4a36 RAPd RAP (diastolic) numeric 
0002-4a37 RAPm RAP (mean) numeric 
0002-4a31 LAPs LAP (systolic) numeric 
0002-4a32 LAPd LAP (diastolic) numeric 
0002-4a33 LAPm LAP (mean) numeric 
0002-4a1d PAPs PAP (systolic) numeric 

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-117
Shared Segment Profile Definitions (Across Integration Profiles)

MDIL code Parameter Label Description Type IIC

0002-4a1e PAPd PAP (diastolic) numeric 

0002-4a1f PAPm PAP (mean) numeric 
0002-5809 ICPs ICP (systolic) numeric 
0002-580a ICPd ICP (diastolic) numeric 
0002-580b ICPm ICP (mean) numeric 
0002-4b50 Tart Arterial Temperature numeric 
0002-4b60 Tcore Core (Body) Temperature numeric 
0002-4b64 Tesoph Esophageal Temperature numeric 
0002-4b6c Tnaso Nasopharyngeal Temperature numeric 
0002-4b74 Tskin Skin Temperature Label numeric 
0002-4b7c Tven Venous Temperature Label numeric 
0002-e004 Trect Rectal Temperature numeric 
0002-f0c4 Tvesic Vesical Temperature (bladder temperature) numeric 
1. Not available in AED mode
2. Calculation is done by the MRx device.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-118
 Shared Segment Profile Definitions (Across Integration Profiles)

Physiological Calculation Parameter Identifiers for Possible Coded Values for OBX.5

Oxygenation Calculations

Parameter Label MDIL Code EMFC Code for Calculation Results

VO2 0002-4b00 4160

C.O. 0002-4b04 4100

SvO2 0002-4b3c 4124

AaDO2 0002-4b40 4168

SpO2 0002-4bb8 4116

PaCO2 0002-7008 4112

PaO2 0002-700c 4108

Hb 0002-7014 4128

CaO2 0002-7018 4144

PvO2 0002-703c 4120

CvO2 0002-7048 4148

FIO2 0002-7498 4104

VO2I 0002-f06a 4192

PB 0002-f06b 4132

DO2 0002-f06d 4156

DO2I 0002-f06e 4188

O2ER 0002-f06f 4164

Qs/Qt 0002-f070 4172

BSA 0002-f071 4184

Ca-vO2 0002-f092 4152

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-119
Shared Segment Profile Definitions (Across Integration Profiles)

Parameter Label MDIL Code EMFC Code for Calculation Results

Weight 0002-f093 4140

Height 0002-f094 4136

Ventilation Calculations

Parameter Label MDIL Code EMFC Code for Calculation Results

Resp 0002-5000 4200

COMP 0002-5088 4228

PIP 0002-5109 4212

Vd/Vt 0002-511c 4236

TV 0002-513c 4208

MINVOL 0002-5148 4224

PECO2 0002-517c 4220

PEEP 0002-51a8 4216

Vd 0002-51b0 4232

ALVENT 0002-5374 4240

PaCO2 0002-7008 4204

Hemodynamic Calculations

Parameter Label MDIL Code EMFC Code for Calculation Results

HR 0002-4182 4004

SVRI 0002-4900 4072

LVSWI 0002-4904 4084

C.I. 0002-490c 4064

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-120
 Shared Segment Profile Definitions (Across Integration Profiles)

Parameter Label MDIL Code EMFC Code for Calculation Results

ABPs 0002-4a15 4009

ABPm 0002-4a17 4011

C.O. 0002-4b04 4000

SVR 0002-4b28 4036

SV 0002-4b84 4032

LCW 0002-4b90 4044

LVSW 0002-4b9c 4048

SI 0002-f048 4068

LCWI 0002-f068 4080

BSA 0002-f071 4060

Weight 0002-f093 4028

Height 0002-f094 4024

RVSWI 0002-4908 4092

PAPs 0002-4a1d 4013

PAPd 0002-4a1e 4014

PAPm 0002-4a1f 4015

PAWP 0002-4a24 4016

CVPm 0002-4a47 4023

PVR 0002-4b24 4040

RCW 0002-4b94 4052

RVSW 0002-4ba4 4056

PVRI 0002-f067 4076

RCWI 0002-f069 4088

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-121
Shared Segment Profile Definitions (Across Integration Profiles)

Parameter Label MDIL Code EMFC Code for Calculation Results

ITBV 0002-f040 3444

ITBVI 0002-f041 3448

EVLW 0002-f042 3452

EVLWI 0002-f043 3456

GEDV 0002-f044 4568

GEDVI 0002-f045 4572

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-122
 Shared Segment Profile Definitions (Across Integration Profiles)

Unit Code Identifiers for Possible Coded Values for OBX.6

MDIL Code Unit Label Description

0004-0000 No dimension

0004-0200 No dimension

0004-0220 % Percentage

0004-0360 mol/mol mol/mol

0004-04e0 %PCV %PCV

0004-0500 m Meter

0004-0511 cm Centimeter

0004-0512 mm Millimeter

0004-0560 in Inch

0004-0592 ml/m2 ml/m2

0004-05c0 m2 Square meter

0004-05e0 in2 Square inch

0004-0640 l Liter

0004-0652 ml Milliliter

0004-0672 ml/breath ml/breath

0004-0692 /mm³ /mm³

0004-06b3 /µl /µl

0004-06b4 1/nl 1/Nanoliter

0004-06c0 g Gram

0004-06c3 kg Kilogram

0004-06d2 mg Milligram. Unit for Amount - Drug Calculator

0004-06d3 mcg Microgram. Unit for Amount - Drug Calculator

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-123
Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-06d4 ng Nanogram. Unit for Amount - Drug Calculator

0004-06e0 lb Pound

0004-0700 oz Ounce

0004-0740 g-m g-m. Used for LVSW, RVSW

0004-0743 kg-m kg-m. Used for RCW, LCW

0004-0760 g-m/m2 g-m/m2. Used for LVSWI and RVSWI

0004-0763 kg-m/m2 kg-m/m2. Used for LCWI and RCWI

0004-07a3 kg/m2 kg/m2. Unit for Dosage - Drug Calculator

0004-07f2 mg/cm3 mg/cm3

0004-0800 g/l g/l

0004-0812 mg/l mg/l

0004-0813 mcg/l Microgram per Liter - unit for Cardiac Markers

0004-0814 ng/l Nanogram per Liter - unit for Cardiac Markers

0004-0840 g/dl g/dl

0004-0852 mg/dl mg/dl

0004-0853 mcg/dl mcg/dl

0004-0860 g/ml g/ml. Unit for Dosage - Drug Calculator

0004-0872 mg/ml mg/ml. Unit for Dosage - Drug Calculator

0004-0873 mcg/ml mcg/ml. Unit for Concentration - Drug Calculator

0004-0874 ng/ml ng/ml. Unit for Concentration - Drug Calculator

0004-0875 pg/ml Picogram per Milliliter - unit for Cardiac Markers

0004-0880 sec Second

0004-0892 msec Millisecond

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-124
 Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-0893 µsec Microsecond

0004-08a0 min Minute

0004-08c0 hours Hours

0004-08e0 days Number of Days

0004-0900 weeks Number of Weeks

0004-0920 months Number of Months

0004-0940 years Number of Years

0004-09c0 Hz Hertz

0004-09e0 /min Per Minute

0004-0aa0 bpm Beats per minute. Used for HR/PULSE

0004-0ae0 rpm Respiration breathes per minute

0004-0b12 mm/sec mm/sec. Speed for Recordings

0004-0b20 l/min/m2 l/min/m2

0004-0b32 ml/min/m2 ml/min/m2

0004-0be0 l/sec l/sec

0004-0c00 l/min l/min

0004-0c12 ml/min ml/min

0004-0c32 ml/hour ml/hour

0004-0c40 l/day l/day

0004-0c52 ml/day ml/day

0004-0c72 ml/kg ml/kg

0004-0d00 g/min g/min. Unit for Dosage - Drug Calculator

0004-0d12 mg/min mg/min. Unit for Dosage - Drug Calculator

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-125
Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-0d13 mcg/min mcg/min. Unit for Dosage - Drug Calculator

0004-0d14 ng/min ng/min. Unit for Dosage - Drug Calculator

0004-0d20 g/hr g/hr. Unit for Dosage - Drug Calculator

0004-0d32 mg/hr mg/hr. Unit for Dosage - Drug Calculator

0004-0d33 mcg/hr mcg/hr. Unit for Dosage - Drug Calculator

0004-0d34 ng/hr ng/hr. Unit for Dosage - Drug Calculator

0004-0d80 g/kg/min g/kg/min. Unit for Dosage - Drug Calculator

0004-0d92 mg/kg/min mg/kg/min. Unit for Dosage - Drug Calculator

0004-0d93 mcg/kg/mn mcg/kg/min. Unit for Dosage - Drug Calculator

0004-0d94 ng/kg/min ng/kg/min. Unit for Dosage - Drug Calculator

0004-0da0 g/kg/hr g/kg/hr. Unit for Dosage - Drug Calculator

0004-0db2 mg/kg/hr mg/kg/hr. Unit for Dosage - Drug Calculator

0004-0db3 mcg/kg/hr mcg/kg/hr. Unit for Dosage - Drug Calculator

0004-0db4 ng/kg/hr ng/kg/hr. Unit for Dosage - Drug Calculator

0004-0f02 hPa Hektopascal

0004-0f03 kPa Kilopascal

0004-0f20 mmHg Millimeter mercury

0004-0f40 cmH2O cmH2O

0004-0f72 mbar Millibar

0004-0f83 kJ Kilo Joule

0004-0f84 MJ Mega Joule

0004-0fd2 mW Milliwatt

0004-0fd4 nW Nanowatt

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-126
 Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-0fd5 pW Picowatt

0004-1020 DS/cm5 Dyn-sec/cm5. Used for SVR, PVR

0004-1052 mA Milliampere

0004-1073 µC Microcoulomb

0004-10a0 V Volt

0004-10b2 mV Millivolt

0004-10b3 µV Microvolt

0004-10c0 Ohm Ohm

0004-10c3 kOhm Kiloohm

0004-1140 °F Degree Fahrenheit

0004-11b2 mOsm Milliosmol

0004-11d2 mmol Millimole

0004-11f2 mEq Milliequivalent

0004-1212 mOsm/l mOsm/l

0004-1272 mmol/l mmol/l

0004-1273 µmol/l micromol/l

0004-12f2 mEq/l mEq/l

0004-1352 mmol/kg mmol/kg

0004-1452 mEq/day mEq/day

0004-1560 U Unit. Unit for Amount - Drug Calculator

0004-1572 mU Milliunit. Unit for Amount - Drug Calculator

0004-15c0 Units/l Units/l

0004-15c5 10*9/l 10*9/l

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-127
Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-15e0 U/ml U/ml. Unit for Dosage - Drug Calculator

0004-15f2 mU/ml mU/ml. Unit for Dosage - Drug Calculator

0004-1620 U/min U/min. Unit for Dosage - Drug Calculator

0004-1632 mU/min mU/min. Unit for Dosage - Drug Calculator

0004-1640 U/hr U/hr. Unit for Dosage - Drug Calculator

0004-1652 mU/hr mU/hr. Unit for Dosage - Drug Calculator

0004-16a0 U/kg/min U/kg/min. Unit for Dosage - Drug Calculator

0004-16b2 mU/kg/min mU/kg/min. Unit for Dosage - Drug Calculator

0004-16c0 U/kg/hr U/kg/hr. Unit for Dosage - Drug Calculator

0004-16d2 mU/kg/hr mU/kg/hr. Unit for Dosage - Drug Calculator

0004-1712 ml/cmH2O ml/cmH2O

0004-1720 cmH2O/l/s cmH2O/l/s

0004-1752 ml2/sec ml2/sec

0004-1760 cmH2O/% cmH2O/%

0004-1780 DSm2/cm5 DSm2/cm5. Used for SVRI and PVRI

0004-17a0 °C Degree Celsius

0004-17d2 mAh Milliampere hours

0004-1800 cmH2O/l cmH2O/l

0004-1820 mmHg/% mmHg/%

0004-1843 kPa/% kPa/%

0004-1912 ml/dl ml/dl

0004-1920 dB Decibel

0004-1952 mg/mg mg/mg

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-128
 Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-1972 10*bpm/ml 10*bpm/ml

0004-1980 1/(min*l) 1/(min*l)

0004-19b1 cm/min cm/min. Speed for HiResTrend Recordings

0004-f001 Count. No dimension

0004-f004 µV p-p Microvolt Peak to Peak

0004-f008 lb/in2 lb/in2. Unit for Dosage - Drug Calculator

0004-f009 mmHg/sec mmHg/sec

0004-f00a ml/sec ml/sec

0004-f00b bpm/ml bpm/ml

0004-f026 mm/h mm/h

0004-f060 J/day J/day

0004-f063 kJ/day Kilo Joule/day

0004-f064 MJ/day Mega Joule/day

0004-f080 cal Calorie

0004-f083 kcal Kilo Calorie

0004-f084 Mcal Mega Calorie

0004-f0a0 cal/day cal/day

0004-f0a3 kcal/day kcal/day

0004-f0a4 Mcal/day Mcal/day

0004-f0c0 cal/ml cal/ml

0004-f0c3 kcal/ml kcal/ml

0004-f0e0 J/ml J/ml

0004-f0e3 kJ/ml kJ/ml

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-129
Shared Segment Profile Definitions (Across Integration Profiles)

MDIL Code Unit Label Description

0004-f100 RPM RPM

0004-f120 1/mn*l*kg 1/mn*l*kg

OBX Segment Examples

Note — If Vista is enabled, field 1 is populated with a sequence number. This is shown below in the Single numeric periodic parameters
(MDIL coded) example only.

Single numeric periodic parameters (MDIL coded):

OBX|1|NM|0002-4182^HR^MDIL|0|60|0004-0aa0^bpm^MDIL|||||F<CR>
OBX|2|NM|0002-e014^Tblood^MDIL|0|37.0|0004-17a0^°C^MDIL|||||F<CR>
OBX|3|NM|0002-513c^TV^MDIL|4|1.40|0004-0640^l^MDIL|||||F<CR>
Single numeric periodic parameters (SDN coded):
OBX||NM|92^RR^SDN|0|30<CR>
OBX||NM|44^PULSE^SDN|0|80<CR>
OBX||NM|1204^inAGT^SDN|1|23.3|%|0.0^25.0<CR>
OBX||NM|1200^etAGT^SDN|1|21.3|%<CR>
Triple numeric periodic parameters (MDIL coded):
OBX||NM|0002-4a49^UVPs^MDIL|4|195.0|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a4a^UVPd^MDIL|4|20.0|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a4b^UVPm^MDIL|4|55.0|0004-0f20^mmHg^MDIL|||||F<CR>
Triple numeric periodic parameters (SDN coded):
OBX||NM|65^ABP S^SDN|0|119<CR>
OBX||NM|66^ABP D^SDN|0|1<CR>
OBX||NM|67^ABP M^SDN|0|40<CR>
OBX||NM|1105^UVP S^SDN|1|126.7|mmHg|100.0^180.0<CR>
OBX||NM|1106^UVP D^SDN|1|56.7|mmHg|20.0^95.0<CR>
OBX||NM|1107^UVP M^SDN|1|91.7|mmHg|100.0^170.0<CR>
Single aperiodic parameters (SDN coded):
OBX||NM|124^C.O.^SDN|0|5.8||||||F||APERIODIC|19970128154155<CR>
OBX||NM|460^Weight^SDN|1|155.0|kg|^110.0||||F||APERIODIC|19970131135956<CR>
OBX||NM|1412^UrpH^SDN|1|8.35||||||F||APERIODIC|19970131135958<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-130
 Shared Segment Profile Definitions (Across Integration Profiles)

Single aperiodic parameters (MDIL coded):

OBX||NM|0401-06ac^Patm^MDIL|4|870|0004-0f72^mbar^MDIL|||||F||APERIODIC|20030110143000<CR>
OBX||NM|0002-f093^Weight^MDIL|4|62.4|0004-06c3^kg^MDIL|||||F||APERIODIC|20030110143000<CR>
Triple aperiodic parameters (MDIL coded):
OBX||NM|0002-4a15^ABPs^MDIL|0|16|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a16^ABPd^MDIL|0|21|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a17^ABPm^MDIL|0|8|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
Monitoring mode setting:
OBX||ST|0402-f8f5^sMode^MDIL|0|DEMO||||||F||SETTING<CR>
OBX||ST|0402-f8f5^sMode^MDIL|0|MONITORING||||||F||SETTING<CR>
OBX||ST|0402-f8f5^sMode^MDIL|0|SERVICING||||||F||SETTING<CR>
OBX||ST|0402-f8f5^sMode^MDIL|0|CONFIGURING||||||F||SETTING<CR>
Connected device attached via VueLink:
OBX||ST|0002-f887^Model^MDIL|4|RMA SL||||||F||CONFIGURATION<CR>
Disconnected device attached via VueLink:
OBX||ST|0002-f887^Model^MDIL|4|""""||||||F||CONFIGURATION<CR>
Alerts (MDIL coded):
OBX||TX|6^Soft Inop^MDIL-ALERT|1|ARRHYTHMIA OFF||||||F<CR>
OBX||TX|6^Soft Inop^MDIL-ALERT|2|CCO NO CALIBRATION||||||F<CR>
OBX||TX|2^Yellow Alarm^MDIL-ALERT|1|**CVPm 9 > 4||||||F<CR>
OBX||TX|2^Yellow Alarm^MDIL-ALERT|2|**ABPs 120 > 90||||||F<CR>
OBX||TX|1^Red Alarm^MDIL-ALERT|1|***BRADY 60 < 80||||||F<CR>
OBX||TX|2^Yellow Alarm^MDIL-ALERT|3|**RR 15 < 30||||||F<CR>
Alerts (SDN coded):
OBX||TX|1^Red^SDN-ALARM|0|*** HF > 120<CR>
OBX||TX|2^Yellow^SDN-ALARM|0|** Sp02 < 95<CR>
OBX||TX|3^Green^SDN-ALARM|0|Leads Off<CR>
Calculations:
OBX||NM|0002-4b24^PVR^MDIL|65|672|0004-1020^DS/cm5^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b28^SVR^MDIL|65|-64|0004-1020^DS/cm5^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f048^SI^MDIL|65|35.3|0004-0592^ml/m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f093^Weight^MDIL|65|227.0|0004-06e0^lb^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f094^Height^MDIL|65|77|0004-0560^in^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4182^HR^MDIL|65|60|0004-0aa0^bpm^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a15^ABPs^MDIL|65|16|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a16^ABPd^MDIL|65|21|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-131
Supported Data Types (All Integration Profiles) - Non-Atomic Types

OBX||NM|0002-4a17^ABPm^MDIL|65|8|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b84^SV^MDIL|65|83.3|0004-0652^ml^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a1d^PAPs^MDIL|65|10|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a1e^PAPd^MDIL|65|55|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a1f^PAPm^MDIL|65|98|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b90^LCW^MDIL|65|-3.3|0004-0743^kg-m^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a24^PAWP^MDIL|65|56|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4900^SVRI^MDIL|65|-151|0004-1780^DSm2/
cm5^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b94^RCW^MDIL|65|5.85|0004-0743^kg-m^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f067^PVRI^MDIL|65|1585|0004-1780^DSm2/
cm5^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4904^LVSWI^MDIL|65|-23.1|0004-0760^g-m/
m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b04^C.O.^MDIL|65|5.00|0004-0c00^l/min^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f068^LCWI^MDIL|65|-1.4|0004-0763^kg-m/
m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f069^RCWI^MDIL|65|2.48|0004-0763^kg-m/
m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4908^RVSWI^MDIL|65|41.30|0004-0760^g-m/
m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4b9c^LVSW^MDIL|65|-54.4|0004-0740^g-m^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-490c^C.I.^MDIL|65|2.12|0004-0b20^l/min/
m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-f071^BSA^MDIL|65|2.x6|0004-05c0^m2^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4ba4^RVSW^MDIL|65|97.47|0004-0740^g-m^MDIL|||||F||APERIODIC|20030516150300<CR>
OBX||NM|0002-4a47^CVPm^MDIL|65|12|0004-0f20^mmHg^MDIL|||||F||APERIODIC|20030516150300<CR>

Supported Data Types (All Integration Profiles) - Non-Atomic Types

Each data type below (each component) is utilized in each and every HL7 table defined above. This means that each use of a common data type
for each segment/field, etc results in EACH component of each data type defined below must be made available as permanent storage and for
edit within IIC.

CE Data Type

This section describes constraints of commonly used HL7 data types.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-132
 Supported Data Types (All Integration Profiles) - Non-Atomic Types

CE Coded Element Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 20 ST R [1..1] Identifier
2 199 ST R [1..1] Text
3 20 ID RE [0..1] 0396 Name of Coding System
4 20 ST X [0..0] Alternate Identifier
5 199 ST X [0..0] 0396 Alternate Text
6 20 ID X [0..0] Name of Alternate Coding
System

CX Data Type

CX Extended Composite ID with Check Digit

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 15 ST R [1..1] ID Number

2 1 ST X [0..0] Check Digit

3 3 ID X [0..0] 0061 Check Digit Scheme

4 227 HD R [1..1] 0363 Assigning Authority Represents a component within a

component. This complicates the
MessageSetting data model significantly.
Analysis of the need for this HL7 capability
determined this as not necessary (no known
clients utilize nor will utilize). To simplify,
only Namespace ID of the HD data type is
allowed. This “flattens” the data model.
5 5 ID RE [0..1] 0203 Identifier Type Code

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-133
Supported Data Types (All Integration Profiles) - Non-Atomic Types

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

6 227 HD X [0..0] Assigning Facility
7 8 DT X [0..0] Effective Date
8 8 DT X [0..0] Expiration Date
9 705 CWE X [0..0] Assigning Jurisdiction
10 705 CWE X [0..0] Assigning Agency or
Department

EI Data Type

EI Entity Identifier Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 16 ST R [1..1] Entity Identifier
2 20 IS RE [0..1] 0363 Namespace ID
3 199 ST X [0..0] Universal ID
4 6 ID X [0..0] 0301 Universal ID Type

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-134
 Supported Data Types (All Integration Profiles) - Non-Atomic Types

HD Data Type

HD Hierarchic Designator Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 20 IS R [1..1] 0300 Namespace ID
2 199 ST RE [0..1] Universal ID
3 6 ID RE [0..1] 0301 Universal ID Type

The PCD TF requires that a field of Data Type HD be populated with one of the following:

• The first component “Namespace ID” alone, which in this case contains a local identifier of the object
• All three components: “Namespace ID” containing the name of the object, “Universal ID” containing its universal OID, and “Universal
ID Type” containing the value ISO.
This data type is particularly used in this MessageSetting to identify facilities, applications and assigning authorities: sending and receiving
applications, sending and receiving facilities, last update facility, assigning authority of an identifier, etc.

PL Data Type

PL Person Location Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 20 IS R [0..1] 0302 Point of Care
2 20 IS RE [0..1] 0303 Room
3 20 IS RE [0..1] 0304 Bed

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-135
Supported Data Types (All Integration Profiles) - Non-Atomic Types

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

4 227 HD RE [0..1] Facility Represents a component within a component. This
complicates the MessageSetting data model
significantly. Analysis of the need for this HL7
capability determined this as not necessary (no
known clients utilize nor will utilize). To simplify,
only Namespace ID of the HD data type is
allowed. This “flattens” the data model.
5 20 IS X [0..0] 0306 Location Status
6 20 IS X [0..0] 0305 Person Location Type
7 20 IS X [0..0] 0307 Building
8 20 IS X [0..0] 0308 Floor
9 199 ST X [0..0] Location Description
10 427 EI X [0..0] Comprehensive Location
Identifier
11 227 HD X [0..0] Assigning Authority for
Location

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-136
 Supported Data Types (All Integration Profiles) - Non-Atomic Types

TS Data Type

TS Time Stamp Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 24 DTM R [1..1] Time Format:
YYYY[MM[DD[HH[MM[SS[.S[S[S[S]]]]]
]]]][+/-ZZZZ]

The time zone (+/-ZZZZ) is represented as

+/-HHMM offset from Coordinated
Universal Time (UTC), (formerly
Greenwich Mean Time (GMT)), where
+0000 or -0000 both represent UTC
(without offset). Deprecations of time
stamp resolution is shown in the individual
element definition(s).

2 1 ID X [0..0] Degree of Precision

XPN Data Type

XPN Extended Person Name Data Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 194 FN RE [0..1] Family Name Uses “Surname” only
2 30 ST RE [0..1] Given Name

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-137
Supported Data Types (All Integration Profiles) - Non-Atomic Types

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

3 30 ST RE [0..1] Second and Further Given
Names or Initials Thereof
4 20 ST X [0..0] Suffix (e.g., JR or III)
5 20 ST X [0..0] Prefix (e.g., DR)
6 6 IS X [0..0] 0360 Degree (e.g., MD)
7 1 ID X [1..0] 0200 Name Type Code
8 1 ID X [0..0] 0465 Name Representation Code
9 483 CE X [0..0] 0448 Name Context
10 53 DR X [0..0] Name Validity Range
11 1 ID X [0..0] 0444 Name Assembly Order
12 26 TS X [0..0] Effective Date
13 26 TS X [0..0] Expiration Date
14 199 ST X [0..0] Professional Suffix

XCN Data Type

XCN Extended Composite ID Number and Name for Persons

The table below is an abbreviated version. It shows only supported values.

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 15 ST RE [0..1] ID Number
2 194 FN RE [0..1] Family Name

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-138
 Supported Data Types (All Integration Profiles) - Non-Atomic Types

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

3 30 ST RE [0..1] Given Name
4 30 ST RE [0..1] Second and Further Given
Names or Initials Thereof

MSG Data Type

MSG Message Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 3 ID RE [0..1] Message Code
2 3 ID RE [0..1] Trigger Event
3 7 ID X [0..0] Message Structure

PT Data Type

PT Processing Type

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 1 ID RE [0..1] Message Code
2 1 ID RE [0..1] Trigger Event

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-139
Supported Data Types (All Integration Profiles) - Non-Atomic Types

VID Data Type

VID Version Identifier

SEQ LEN DT Usage Card. HL7 TBL# Component Name Description

1 5 ID RE [0..1] Version Id
2 483 CE X [0..0] Internationalization Code
3 483 CE X [0..0] International Version Id

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-140
 Deviations in Messages from HL7 Standard

Deviations in Messages from HL7 Standard

Queries for current data from PDI interfaces are mostly compliant with the HL7 standard 2.x as it is published today. Deviations include the
following:

• When setting the Message Type configuration to PDS Compatible, the PID segment, Patient Name field contains the patient name in the
format FirstName LastName (separated by a space) which is not standard. If EMFC coding or MDIL coding is chosen, the patient name
format is LastName^FirstName which is standard.
• Polling Interface: The inclusion of a PV1 segment in the query response is not in conformance to the HL7 definition but required for PDI
as it contains the identification of the bed. As there is no safe way to identify data through patient name or number, the bed identification
is absolutely crucial and cannot be omitted.
• Polling Interface: Sending the sequence PID - PV1 - OBR - OBX multiple times for the same patient in a single query response is NOT
compliant to the HL7 specification but required in order to query the parameters of multiple beds in a single query.

International Characters
International characters are provided in the ISO 8859-1 character set, which covers most European languages. This character set is compatible
with the character set used in Microsoft® Windows® and contains equivalents for all characters that can be distributed on the network. East
European and Asian characters are not supported; for these countries, PDI uses the English language.

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-141
International Characters

HL7 Message Profile Definitions (Categorized by Integration Profile)

4-142
 Standard HL7 Message Profile Notations

A
Standard HL7 Message Profile Definition Notation

Standard HL7 Message Profile Notations

An HL7 message profile is an unambiguous specification of one or more standard HL7 messages that have been analyzed for a particular use
case. Each message profile may have a unique identifier.

Acknowledgements

The specific HL7 acknowledgements required and/or allowed for use with the specified static definition of the HL7 message profile shall be
defined. Specifically, the dynamic definition shall identify whether an accept and/or application level acknowledgement is allowed or required.

For any one static definition there may be one or more dynamic definition.

The dynamic definition shall define the conditions under which an accept and/or application level acknowledgement is expected.

Allowed conditions include:

• Always
• Never
• Only on success
• Only on error.

Standard HL7 Message Profile Definition Notation

A-1
Standard HL7 Message Profile Notations

Message Profile Definition Details

The Message Profile definition is a complete specification for an HL7 message. It is based on a message structure defined in the HL7 Standard.
The message code, trigger event, event description, role (Sender or Receiver) and, if applicable, the order control code will be provided. A
complete definition shall be defined at the message, segment, and field levels. A Message Profile definition is compliant in all aspects with the
HL7 defined standard message it profiles. However, the profile definition may define additional constraints on the standard HL7 message.

A message profile identifies only those specific elements of a standard HL7 message that are used in the exchange.

A message profile definition explicitly defines:

• Segments, segment groups, fields and components usage rules

• Cardinalities
• Value sets and coding systems.
The following figure depicts, in a graphical way, the concept that the message profile definition is an overlay of the HL7 message structure
further constraining it. For example, where the HL7 message structure shows unlimited number of NK1 Segments, the message profile
definition allows for only three repetitions. Additionally, fields that are optional in the HL7 message structure may be required within the HL7
static definitions.

Standard HL7 Message Profile Definition Notation

A-2
 Standard HL7 Message Profile Notations

ADT^A01

HL7 Message Structure HL7 Message Profile

MSH MS H
Segments/Segment Groups:
EVN EVN - Segment Usage
PID PID - Cardinality (min, max)
NK1 NK1 NK1 NK1 NK1 ... NK1 NK1 NK1 NK1 NK1 ...
PV1 P V1

... ...
Fields/Components:
- Field Usage (Optionality)
PV2 PV2 - Cardinality (min, max)
OBX
- Value Sets/Coding system
OBX
- Descriptions
AL1 AL1
... ...

Table definition

Table definitions will include statements of table conformance and, if available, the actual table elements supported.

Standard HL7 Message Profile Definition Notation

A-3
Standard HL7 Message Profile Notations

Message Profile Definition Notation Details

This section discusses concepts common to each level of the message profile definition (message, segment and field). It uses the generic term
'element' to refer to segment groups, segments, fields, components and sub-components.

Cardinality

Cardinality identifies the minimum and maximum number of repetitions for a particular element (Segment Group, Segment or Field).
Cardinalities are expressed as a minimum-maximum pair of non-negative integers. A conformant application must always send at least the
minimum number of repetitions, and may never send more than the maximum number of repetitions.

There are two special values for cardinality. If the minimum number of repetitions is 0, the element may be omitted from a message. In certain
circumstances, the maximum number of repetitions may have no practical limit. In this case, it is identified as '*'. Examples of common
cardinality combinations are:

Value Description Comment

[0..0] Element never present

[0..1] Element may be omitted and it can have at most one Occurrence

[1..1] Element must have exactly one Occurrence

[0..n] Element may be omitted or may repeat up to n times

[1..n] Element must appear at least once, and may repeat up to n times

[0..*] Element may be omitted or repeat for an unlimited number of times

[1..*] Element must appear at least once, and may repeat unlimited number of times

[m..n] Element must appear at least "m" and at most" n" times

Standard HL7 Message Profile Definition Notation

A-4
 Standard HL7 Message Profile Notations

Usage

Usage refers to the circumstances under which an element appears in a message. Some elements must always be present, others may never be
present, and others may only be present in certain circumstances. A set of codes has been defined to clearly identify the rules governing the
presence of a particular element.

The rules govern the expected behavior of the sending application and limited restrictions on the receiving application with respect to the
element. These usage codes expand/clarify the optionality codes defined in the HL7 standard.

Value Description Comment

R Required A conforming sending application shall populate all "R" elements with a non-empty value. conforming
receiving application shall process (save/print/archive/etc.) or ignore the information conveyed by required
elements. A conforming receiving application must not raise an error due to the presence of a required
element, but may raise an error due to the absence of a required element.
Any element designated as required in a standard HL7 message definition shall also be required in all HL7
message profiles of that standard message.

RE Required but may be empty The element may be missing from the message, but must be sent by the sending application if there is
relevant data. A conforming sending application must be capable of providing all "RE" elements. If the
conforming sending application knows the required values for the element, then it must send that element.
If the conforming sending application does not know the required values, then that element will be omitted.
Receiving applications will be expected to process (save/print/archive/etc.) or ignore data contained in the
element, but must be able to successfully process the message if the element is omitted (no error message
should be generated because the element is missing).

O Optional This code indicates that the Usage for this element has not yet been defined. A usage of 'Optional' may not
be used in 'implementation' profiles (no-optionality profiles). Conformance may not be tested on an
Optional field. Narrower profiles may be defined based on this profile, and may assign any usage code to
the element.

Standard HL7 Message Profile Definition Notation

A-5
Standard HL7 Message Profile Notations

Value Description Comment

C Conditional This usage has an associated condition predicate (See section 2.B.7.6, "Condition predicate").
If the predicate is satisfied:
A conformant sending application must always send the element. A conformant receiving application must
process or ignore data in the element. It may raise an error if the element is not present.
If the predicate is NOT satisfied:
A conformant sending application must NOT send the element. A conformant receiving application must
NOT raise an error if the condition predicate is false and the element is not present, though it may raise an
error if the element IS present.

CE Conditional but may be empty This usage has an associated condition predicate (See section 2.B.7.6, "Condition predicate").
If the predicate is satisfied:
If the conforming sending application knows the required values for the element, then the application must
send the element. If the conforming sending application does not know the values required for this element,
then the element shall be omitted. The conforming sending application must be capable of knowing the
element (when the predicate is true) for all 'CE' elements.
If the element is present, the conformant receiving application shall process (display/print/archive/etc.) or
ignore the values of that element. If the element is not present, the conformant receiving application shall
not raise an error due to the presence or absence of the element.
If the predicate is not satisfied:
The conformant sending application shall not populate the element.
The conformant receiving application may raise an application error if the element is present.

X Not supported For conformant sending applications, the element will not be sent. Conformant receiving applications may
ignore the element if it is sent, or may raise an application error.

Standard HL7 Message Profile Definition Notation

A-6
 Standard HL7 Message Profile Notations

Relationship Between HL7 Optionality and Conformance Usage

Conformance usage codes are more specific than HL7 Optionality codes. Because of the requirement that message profile definition must be
compliant with the HL7 message definition it is derived from, there are restrictions on what usage codes may be assigned to an element based
on the HL7 Optionality.

HL7 Optionality Allowed Conformance Usage Comment

R - Required R

O - Optional R, RE, O, C, CE, X O is only permitted for constrainable profiles

C- Conditional C, CE, R

X - Not Supported X

B - Backward Compatibility R, RE, O, C, CE, X O is only permitted for constrainable definitions

W - Withdrawn R, RE, O, C, CE, X

Relationship Between Usage and Cardinality

Both usage and cardinality govern the appearance of a field and, therefore, a relationship exists between them. For purposes of message
profiles, the cardinality shall be constrained by the usage code. The constraints are:

• If the usage of an element is Required (R), the minimum cardinality for the element shall always be greater than or equal to 1.
• If the usage of an element is not Required (R) (i.e. any code other than 'R'), the minimum cardinality shall be 0 except in the following
condition:
If the profile author wishes to express a circumstance where an element will not always be present, but when present must have a minimum
number of repetitions greater than one, this may be indicated by specifying the non-required Usage code with the minimum cardinality
representing the minimum number of repetitions when the element is present. This would generally be expressed as (0,n..m), indicating that
permitted occurrences are either zero, or the range of n through m).

Standard HL7 Message Profile Definition Notation

A-7
Standard HL7 Message Profile Notations

Cardinality Usage Interpretation

[1..1] R There will always be exactly 1 repetition present

[1..5] R There will be between 1 and 5 repetitions present

[0..1] RE The element must be supported, but may not always be present

[0..5] C If the condition predicate is true, there will be between 1 and 5 repetitions. If the predicate is
false, there will be 0 repetitions

[3..5] RE If any values for the element are sent, there must be at least 3 and no more than 5 repetitions.
However, the element may be absent (0 repetitions)

Condition Predicate

If the usage code of an element is C or CE, then a conditionality predicate must be associated with this element that identifies the conditions
under which the element must be or is allowed to be present. The predicate must be testable and based on other values within the message. This
predicate may be expressed as a mathematical expression or in text and may utilize operators such as equivalence, logical AND, logical OR and
NOT. The conforming sending and receiving applications shall both evaluate the predicate. When the Usage is not 'C' or 'CE', the conditionality
predicate will not be valued.

Standard HL7 Message Profile Definition Notation

A-8
 Standard HL7 Message Profile Notations

Message Profile Definition - Message Level

The message profile definition shall be documented using the HL7 abstract message syntax, with the addition of specifying cardinality and
usage for each of the segments contained within the message structure.The usage column shall be updated to reflect the usage of the segment or
group within this particular message profile definition.The cardinality column shall accurately reflect the minimum and maximum number of
repetitions of the field allowed for the segment or group within this particular message profile definition.

Database / XML
Segment ADT Message Usage Card Chapter Note Reference
Mapping
MSH Message Header R [1..1] 2 N/A

[{SFT}] Software Segment X [0..0] 2

EVN Event Type X [0..0] 3

PID Patient Identification R [1..1] 3 Patient, Contact

[ PD1 ] Additional RE [0..1] 3 Provider, Contact

Demographics

[{ROL}] Role X [0..0] 15

[{NK1}] Next of Kin / X [0..0] 3

Associated Parties

PV1 Patient Visit RE [0..1] 3 Visit, Location, The PV1 segment is only
Provider processed when PV1-19 is present.

[ PV2 ] Patient Visit - RE [0..1] 3 Visit The PV1 segment is only

Additional Info. processed when PV1-19 is present.

[{ROL}] Role X [0..0] 15

[{DB1}] Disability Information X [0..0] 3

[{OBX}] Observation/Result X [0..0] 7

[{AL1}] Allergy Information X [0..0] 3 Allergy

Standard HL7 Message Profile Definition Notation

A-9
Standard HL7 Message Profile Notations

Database / XML
Segment ADT Message Usage Card Chapter Note Reference
Mapping
[{DG1}] Diagnosis Information X [0..0] 6

[ DRG ] Diagnosis Related Group X [0..0] 6

[{ --PROCEDURE begin

PR1 Procedures X [0..0] 6

[{ROL}] Role [0..*] 15

}] --PROCEDURE end

[{GT1}] Guarantor X [0..0] 6 Guarantor

[{ --INSURANCE begin

IN1 Insurance X [0..0] 6 Insurance Policy,

Insurance Plan,
Insurance Payer

[ IN2 ] Insurance Additional X [0..0] 6

Info.

[{IN3}] Insurance Additional X [0..0] 6

Info. - Cert

[{ROL}] Role [0..*] 15

}] --INSURANCE end

[ACC] Accident Information X [0..0] 6

[UB1] Universal Bill X [0..0] 6

Information

[UB2] Universal Bill 92 X [0..0] 6

Information

Standard HL7 Message Profile Definition Notation

A-10
 Segment Profile Definitions

Segment Profile Definitions

The set of segments and segment groups included within the message profile definition shall be defined. Any segments or segment groups that
are required by HL7 shall be included.

Segment Profile Cardinality

Some segments and segment groups within the HL7 message are allowed to repeat. The cardinality of all the segments and groups within the
message shall be defined.

The segment level profile definition shall be documented using the HL7 segment attribute table format with the addition of specifying length,
usage and cardinality for each of the fields contained within the segment.

• The length column shall be updated to accurately reflect the maximum allowed length for the field within this segment definition.
• The usage column shall accurately reflect the usage of the field within this segment definition.
• The cardinality column shall accurately reflect the minimum and maximum number of repetitions of the field allowed for this segment
definition.

Element
SEQ LEN DT Usage Card. Note Reference
Name
1 4 SI X [0..0] 00104 Set ID not used

2 20 CX X [0..0] 00105
3 250 CX R [1..1] 00106
4 20 CX X [0..0] 00107
5 250 XPN R [1..1] 00108
6 250 XPN RE [0..1] 00109

Standard HL7 Message Profile Definition Notation

A-11
Segment Profile Definitions

Element
SEQ LEN DT Usage Card. Note Reference
Name
7 26 TS RE [0..1] 00110
8 1 IS RE [0..1] 0001 00111
9 250 XPN X [0..0] 00112
10 250 CE RE [0..*] 0005 00113
11 250 XAD RE [0..*] 00114
12 4 IS X [0..0] 0289 00115

13 250 XTN RE [0..1] 00116

14 250 XTN RE [0..*] 00117

15 250 CE RE [0..1] 0296 00118

16 250 CE RE [0..1] 0002 00119

17 250 CE RE [0..1] 0006 00120

18 250 CX RE [0..1] 00121

19 16 ST RE [0..1] 00122
20 25 DLN RE [0..1] 00123

21 250 CX X [0..0] 00124

22 250 CE X [0..0] 0189 00125

23 250 ST X [0..0] 00126

24 1 ID X [0..0] 0136 00127

25 2 NM RE [0..1] 00128
26 250 CE X [0..0] 0171 00129
27 250 CE X [0..0] 0172 00130

Standard HL7 Message Profile Definition Notation

A-12
 Segment Profile Definitions

Element
SEQ LEN DT Usage Card. Note Reference
Name
28 250 CE RE [0..1] 0212 00739
29 26 TS RE [0..1] 00740
30 1 ID X [0..0] 0136 00741
31 1 ID RE [0..1] 0136 01535

32 20 IS RE [0..*] 0445 01536

33 26 TS X [0..0] 01537

34 241 HD X [0..0] 01538

35 250 CE X [0..0] 0446 01539

36 250 CE X [0..0] 0447 01540

37 80 ST X [0..0] 01541

38 250 CE X [0..0] 0429 01542

39 250 CWE X [0..0] 0171 01840

Field Definitions

The set of fields of each segment within the message profile definition shall be specified. If a segment occurs multiple times within a message
profile, it may be represented by different segment profiles. This shall be explicitly defined within the message level definition.

Field Cardinality

Some fields within a segment are allowed to repeat. The cardinality of all the fields within the segment shall be defined.

Standard HL7 Message Profile Definition Notation

A-13
Segment Profile Definitions

Field Usage

The usage of the field within a segment shall be defined consistent with the profile type, and using one of codes identified in the previously
defined Usage tables.

Data Type

The data type of the field within a segment shall be updated to accurately reflect the data type for the field within this segment definition.

Length

The length of the field within a segment shall be updated to accurately reflect the maximum allowed length for the field within this segment
definition.

Table Reference

The name of the table of the field within a segment shall be updated to accurately reflect the table used for the field within this segment
definition.

Database / XML Table Column

This column in the static definition specifies the database table where each segment, field, or component's data will be stored. In cases where a
segment is stored across multiple tables, a list of tables is provided. The value in this column serves as a general pointer to the location where
the data will be stored in the clinical database. This document is not intended to be a data dictionary.

Notes Reference Column

Standard HL7 Message Profile Definition Notation

A-14
 Segment Profile Definitions

This column includes a reference to a note about any conditions or logic that should be considered. This column also contains a reference to
any logic for conditional fields.

Field Profile Definitions

Each individual field within a segment shall be completely defined to eliminate any possible ambiguity. In cases where HL7 2.x field
descriptions are not sufficient, a precise semantic definition shall be specified.

User-Defined and Suggested Field Values

The allowed code sets (table) for many fields within the HL7 Standard are specified as user-defined (data type IS) or HL7-defined (data type
ID) values. In these cases, the exact allowed code set shall be specified. These values shall be defined according to the specified scope of use.

Coded Entry (CE, CF, CWE, and CNE) type fields are specified as being populated based on coding systems. For each of these fields, the
specific coding system used shall be identified. Compliant applications are required to use the specified coding system, but may also use an
alternate coding system as supported by the data type (See the example within each data type definition).

Components and SubComponents

Each component within composite fields shall be profiled. This requires defining the usage, length, data type, and data values of each of the
components. Where there are sub-components of a component, each of the sub-components shall also be profiled using the same method. With
the exception of cardinality, the rules for these definitions follow those for fields.

Standard HL7 Message Profile Definition Notation

A-15
Segment Profile Definitions

Standard HL7 Message Profile Definition Notation

A-16
 Introduction

B
Parameter Data Interface vs. Clinical Data Server

Introduction
HL7 Parameter Data Interface (HL7PDI) is different from the Clinical Data Server HL7 interface in the following ways:

HL7 PDI CDS HL7

Sending Interval Unsolicited data export for periodic data can be configured Unsolicited data export for periodic data can be configured for
for 5, 10, 30 or 60 sec (default). every 15 sec up to every 3600 sec in 1 sec intervals (default is
30 sec)

Parameter Support See the list of parameters in “HL7 Data Output See the list of parameters in “HL7 Data Output
Considerations” on page B-8. Considerations” on page B-8.

Initial Aperiodic message Upon connection of a client to the unsolicited message Upon connection of a client to the unsolicited message
content interface, all current valid data in an initial aperiodic interface, only settings and configuration values is sent.
message (aperiodic parameters, settings, and configuration Aperiodic parameters are not sent in this initial message.
values) is sent

VueLink Parameter Supported Not supported

support for IntelliVue
Patient Monitors

VueLink Free Text Not supported Supported

support

Alarm Limits Not supported Supported: Alarm limits for parameters received through the
DAP protocol

HL7 Data Output Control Allows data from one bed to be sent to one target client. List
of assigned beds is preconfigured

Parameter Data Interface vs. Clinical Data Server

B-1
Introduction

HL7 PDI CDS HL7

Bed ID/Network ID Not read from monitoring network, preconfigured values Read from monitoring network

Triple labels Uses the internal text resources to resolve parameter labels Generated by using the standard label and adding the
that contain triple values in a different format: extension for systolic, diastolic, and mean values:
LABELs LABEL S
LABELd LABEL D
LABELm LABEL M

General Label Internal text resources labels may differ.

Differences

NMD reply NMD messages are used to provide time information and
NOT to inform clients that they are not allowed to receive
data because they are not configured in the list of allowed
hosts. Connection refused socket message to the client is
sent.

DAP device No DAP Protocol support Shows data coming through the DAP protocol channel on a
separate device. Device name is DAP Internal Source, with the
device id of 64.

Monitoring data device Sends all data not coming from a VueLink device or Physio Sends parameters with EMFCs up to 255 (MFCs) on this
(or SDN Broadcast Calculation on the Monitoring Data Device (device ID 0) device 0, unit information non available on this device.
device) Parameter labels in english only

Parameter Data Interface vs. Clinical Data Server

B-2
 Parameter Label Differences

Parameter Label Differences

The following table lists the label differences (for English labels) between the HL7PDI (when EMFC Coding or PDS Compatible setting is
configured) and CDS HL7

EMFC Code MDIL Code HL7PDI Label CDS HL7 Label

44 0002-480a Pulse PULSE

44 0002-4822 Pulse PULSE

49 0002-f0a5 P1s P1 S

49 0401-0031 P_1s P1 S

50 0002-f0a6 P1d P1 D

50 0401-0032 P_1d P1 D

51 0002-f0a7 P1m P1 M

51 0401-0033 P_1m P1 M

53 0002-f0a9 P2s P2 S

53 0401-0035 P_2s P2 S

54 0002-f0aa P2d P2 D

54 0401-0036 P_2d P2 D

55 0002-f0ab P2m P2 M

55 0401-0037 P_2m P2 M

57 0002-f0ad P3s P3 S

57 0401-0039 P_3s P3 S

58 0002-f0ae P3d P3 D

58 0401-003a P_3d P3 D

59 0002-f0af P3m P3 M

Parameter Data Interface vs. Clinical Data Server

B-3
Parameter Label Differences

EMFC Code MDIL Code HL7PDI Label CDS HL7 Label

59 0401-003b P_3m P3 M

61 0002-f0b1 P4s P4 S

61 0401-003d P_4s P4 S

62 0002-f0b2 P4d P4 D

62 0401-003e P_4d P4 D

63 0002-f0b3 P4m P4 M

63 0401-003f P_4m P4 M

65 0002-4a15 ABPs ABP S

66 0002-4a16 ABPd ABP D

67 0002-4a17 ABPm ABP M

69 0002-4a45 CVPs CVP S

70 0002-4a46 CVPd CVP D

71 0002-4a47 CVPm CVP M

73 0002-4a31 LAPs LAP S

74 0002-4a32 LAPd LAP D

75 0002-4a33 LAPm LAP M

77 0002-4a1d PAPs PAP S

78 0002-4a1e PAPd PAP D

79 0002-4a1f PAPm PAP M

81 0002-5809 ICPs ICP S

82 0002-580a ICPd ICP D

83 0002-580b ICPm ICP M

85 0401-0055 IUPs IUP S

Parameter Data Interface vs. Clinical Data Server

B-4
 Parameter Label Differences

EMFC Code MDIL Code HL7PDI Label CDS HL7 Label

86 0401-0056 IUPd IUP D

87 0401-0057 IUPm IUP M

89 0002-4a05 NBPs NBP S

90 0002-4a06 NBPd NBP D

91 0002-4a07 NBPm NBP M

92 0002-5000 Resp RESP

96 0002-5012 awRR AWRR

100 0002-f0c7 T_1 T1

104 0002-f0c8 T_2 T2

112 0002-50b0 etCO2 ETCO2

116 0002-50ba imCO2 IMCO2

136 0002-4261 PVC VPB

140 0002-d007 RhySta RHYTHM

144 0002-d006 EctSta ECTOP

161 0002-4a11 ARTs ART S

162 0002-4a12 ARTd ART D

163 0002-4a13 ARTm ART M

165 0002-4a35 RAPs RAP S

166 0002-4a36 RAPd RAP D

167 0002-4a37 RAPm RAP M

169 0002-4a0d AoS Ao S

170 0002-4a0e AoD Ao D

171 0002-4a0f AoM Ao M

Parameter Data Interface vs. Clinical Data Server

B-5
Parameter Label Differences

EMFC Code MDIL Code HL7PDI Label CDS HL7 Label

172 0002-e018 dTemp T1-T2

512 0002-4bb0 Perf PERF

528 0002-4b64 Tesoph Tesop

1025 0401-0401 P5s P5 S

1026 0401-0402 P5d P5 D

1027 0401-0403 P5m P5 M

1029 0401-0405 P6s P6 S

1030 0401-0406 P6d P6 D

1031 0401-0407 P6m P6 M

1033 0401-0409 P7s P7 S

1034 0401-040a P7d P7 D

1035 0401-040b P7m P7 M

1037 0401-040d P8s P8 S

1038 0401-040e P8d P8 D

1039 0401-040f P8m P8 M

1040 0002-f0ca T_3 T3

1044 0002-f0ca T_4 T4

1096 0002-f051 tcGas tc

1101 0002-4a29 UAPs UAP S

1102 0002-4a2a UAPd UAP D

1103 0002-4a2b UAPm UAP M

1105 0002-4a49 UVPs UVP S

1106 0002-4a4a UVPd UVP D

Parameter Data Interface vs. Clinical Data Server

B-6
 Parameter Label Differences

EMFC Code MDIL Code HL7PDI Label CDS HL7 Label

1107 0002-4a4b UVPm UVP M

1292 0002-50f2 AWPmin MinAwP

2185 0401-0889 BPs BP S

2186 0401-088a BPd BP D

2187 0401-088b BPm BP M

Parameter Data Interface vs. Clinical Data Server

B-7
HL7 Data Output Considerations

HL7 Data Output Considerations

The following table shows which parameter data is supported by HL7PDI and CDS HL7:

Supported Supported
Parameter type
by HL7PDI on CDS HL7

Philips SDN/CareNet SDN Broadcast Data Yes Yes

VueLink Non-resting display parameters and settings No Yes

Blood Analysis parameters No Yes

Physio calculation parameters No Yes

IntelliVue Clinical Network Standard parameter data Yes No

VueLink parameter data Yes No

Physio Calculation data Yes No

Parameter Data Interface vs. Clinical Data Server

B-8