7-1

ORD Interface (HL7)

The ORD interface processes inventory re-order information.
A customer’s Materials Management department can choose to have inventory re-order
information sent from the Omnicell system to the Materials Management system. A pick list
information is generated in Omnicell and sent to the Materials Management system via an
interface.
Par levels and re-order levels are stored on the Omnicell system. They are used to calculate re-
order quantities for each item. A pick list file of the reorder quantities is generated whenever a
user at the OmniCenter chooses to generate a pick list. At that time, the pick list information is
communicated to the materials management system either as individual records or as a batch file
containing information on the complete pick list.

Hospital
System Interface services OmniCenter
Application Application
Application

Socket or batch file ORD

Interface Messages sent over MSMQ

Figure 7-1. ORD interface

General Information
 Communication mode: Batch file via file transfer protocol (FTP) or network drive mapping
 HL7 v2.1-5 formats supported
 Omnicell configuration: Send file on a scheduled basis

© 2015 Omnicell, Inc. Supply Interface Specifications/67-3078 Rev H

7-2 ORD Interface (HL7)
ORD Message Segments

ORD Message Segments

The following Master File Notification (MFN) message segments for a Pick List File (ZPL) are
used:

Name Definition
FHS HL7 file header
BHS HL7 batch header
MSH Message Header
MFI Master File Identification
{
MFE Master File Entry
[ZPL] Pick List File Record
}

The segments listed under each message are the segments that the Omnicell system processes
unless specified otherwise. If additional segments (Z-segments or segments not in the HL7
specification) are sent within the messages, Omnicell ignores them. Fields within a segment are
ignored if the Omnicell system does not process them. Complete messages and segments may be
sent by the sending system. The Omnicell system handles the filtering of segments and fields that
it does not need.
The length of the data fields used by Omnicell is based upon the maximum length defined in the
Omnicell data dictionary. Length of the data fields not used by Omnicell follows the length as
defined in the HL7 standard document.

Note: The following tables have OmniCenter tokens in bold under Comments.

FHS – HL7 file header

Required/
Sequence Length Optional Element Name Comments
0 3 R Segment Name FHS
1 1 R Field Separator Use default of “|” (pipe character)
2 4 R Encoding Characters ^~\&
3 15 O Sending Application Sending application; defined in file node.ini
4 20 R Sending Facility Hospital facility; defined in file node.ini
5 15 O Receiving Application Vendor system name; defined in file node.ini
6 30 R Receiving Facility Hospital facility; defined in file node.ini
7 16 R Date/Time of Message Format: YYYYMMDDHHMMSS
Table 7-1. File header

Supply Interface Specifications/67-3078 Rev H © 2015 Omnicell, Inc.

 ORD Interface (HL7) 7-3
ORD Message Segments

BHS – HL7 batch header

Required/
Sequence Length Optional Element Name Comments
0 3 R Segment Name BHS
1 1 R Field Separator Use default of “|” (pipe character)
2 4 R Encoding Characters ^~\&
3 15 O Sending Application Sending application; defined in file node.ini
4 20 R Sending Facility Hospital facility; defined in file node.ini
5 15 O Receiving Application Vendor system name; defined in file node.ini
6 30 R Receiving Facility Hospital facility; defined in file node.ini
7 16 R Date/Time of Message Format: YYYYMMDDHHMMSS
Table 7-2. Batch header

MSH – Message Header

Refer to “MSH - Message Header” on page 6-2 for a complete segment definition.
MSH.9.1 = MFN
MSH.9.2 = None

MFI – Master File Identification Segment

Required/
Sequence Length Optional Element Name Comments
1 60 R Master File Identifier PLF^Pick List File
3 3 R File Level Event Code UPD
4 19 O Entered Date/Time Format: YYYYMMDDHHMMSS
5 19 Effective Date/Time Not currently used by Omnicell
6 6 R Response Level Code NE – no application level response
Table 7-3. Master file identification segment

© 2015 Omnicell, Inc. Supply Interface Specifications/67-3078 Rev H

7-4 ORD Interface (HL7)
Sample Pick List Message

MFE – Master File Entry

Required/
Sequence Length Optional Element Name Comments
1 3 R Record Level Event Code MAD – add record to master file
MDL – not currently supported
MUP – not currently supported
2 20 MFN Control ID Not currently used by Omnicell
3 19 Effective Date/Time Not currently used by Omnicell
4 60 R Primary Key Value OmniSupplier Name (osi)
Table 7-4. Master file entry

ZPL – Pick List File Record

Required/
Sequence Length Optional Element Name Comments
1 4 R Location OmniSupplier Name (osi)
-- O Uses OmniSupplierIgnore map
2 16 R Item ID Item ID
3 8 R Requested Restock Quantity (qor / csi) – in restock unit of measure
4 20 R Purchase Order Number Restock ID (pon)
5 20 R Unit of stock Unit of stock (usk)
7 20 R Restock route Remote restock route (rrt)
Table 7-5. Pick list file record

Sample Pick List Message

FHS|^~\&|OMNIMEDS-IN|UTMH|HNAM|HNAM|20070926090015
BHS|^~\&|OMNIMEDS-IN|UTMH|HNAM|HNAM|20070926090015
MSH|^~\&|OMNIMEDS-IN|UTMH|HNAM|HNAM|20070926090015||MFN|##|P|2.3
MFI|PLF^Pick List File||UPD|20070926090015||NE
MFE|MAD|||SV5TWR
ZPL|SV5TWR|125761S|1|CPC01-0000058075|EA||>5T: M-F 900
ZPL|SV5TWR|125902S|2|CPC01-0000058075|EA||>5T: M-F 900
ZPL|SV5TWR|125979S|6|CPC01-0000058075|EA||>5T: M-F 900

Supply Interface Specifications/67-3078 Rev H © 2015 Omnicell, Inc.