CareFusion™ Coordination Engine

ROWA™ Adapter v1.4

Specifications Guide

March 2016
DME: 10000231106 Ver 04
CareFusion, Pyxis, ROWA CareFusion™ Coordination Engine ROWA™ Adapter
and the CareFusion logo are
trademarks or registered v1.4 Specifications Guide
trademarks of CareFusion
Corporation or one of its Changes in equipment, software, or procedures occur periodically; information
subsidiaries. describing these changes will be included in future editions of the guide.
All other trademarks are the The information in this document is subject to change and does not represent a
property of their respective
commitment on the part of CareFusion to provide additional services or
owners.
enhancements.

CareFusion Corporation Documentation provided with this product might reference product not present in
San Diego, CA your facility or not yet available for sale in your area.
United States
888.876.4287
858.617.2000
carefusion.com

© 2013–2016
CareFusion Corporation
or one of its subsidiaries
All rights reserved.
 Contents

About this guide

Acronyms.................................................................................................. vii

Chapter 1—Communications considerations

Network connection ...............................................................................................2
Minimal lower layer protocol.................................................................................3
Minimal blocked message example................................................................3
Message structure ...................................................................................................4
Encoding characters................................................................................................5
Escape formatting codes.........................................................................................6
Escape format example...................................................................................6
Field data population ......................................................................................6
Data element maintenance support.................................................................6
Message trigger codes and event types ..................................................................8
Message header segment—MSH ...........................................................................9
Message acknowledgments ..................................................................................11
MSA—Message Acknowledgement ............................................................11
MSA–1 Acknowledgment code—CCE replies with an original mode
application accept code: AA.........................................................................11

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide iii

Contents

Chapter 2—Data Types

Basic data types ....................................................................................................14
Complex data types ..............................................................................................15

Chapter 3—ROWA Adapter v1.2 Specifications

ROWA messages..................................................................................................18
ROWA to host message structures ...............................................................19
Host to ROWA message structures ..............................................................20
QRD segment ...............................................................................................20
ZFX segment ................................................................................................24
ZPM segment................................................................................................27
DSC segment ................................................................................................31
Segment field details by message.........................................................................32
Input request .................................................................................................32
Input response...............................................................................................32
Input Message...............................................................................................32
Output Request .............................................................................................32
Output Response...........................................................................................32
Output Message ............................................................................................32
Stock Info Request........................................................................................32
Stock Info Response .....................................................................................32
Status Request...............................................................................................33
Status Response ............................................................................................33
Task Info Request.........................................................................................33
Task Info Response ......................................................................................33
Task Cancel Request ....................................................................................33
Task Cancel Response ..................................................................................33
ArticleMasterSetRequest ..............................................................................33
AricleMasterSetResponse.............................................................................33
StockDeliverySetRequest .............................................................................33
StockDeliverySetResponse...........................................................................33
ConfigurationGetRequest .............................................................................33
ConfigurationGetResponse...........................................................................34
StockLocationInfoRequest ...........................................................................34
StockLocationInfoResponse.........................................................................34
InitiateInputRequest......................................................................................34
InitiateInputResponse ...................................................................................34
InitiateInputMessage ....................................................................................34
Message flow........................................................................................................35

Appendix A—Sample messages

Sample InitiateInputMessage message on page 46Sample StatusRequest message
38
Sample StatusResponse message ........................................................................38
Sample InputRequest message ............................................................................38
Sample InputResponse message ..........................................................................39

iv CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Contents

Sample InputMessage message ...........................................................................39

Sample StockInfoRequest message .....................................................................40
Sample StockInfoResponse message ..................................................................41
Sample OutputRequest message .........................................................................42
Sample OutputResponse message .......................................................................42
Sample OutputMessage message ........................................................................42
Sample TaskInfoRequest message ......................................................................43
Sample TaskInfoResponse message ....................................................................43
Sample TaskCancelRequest message ..................................................................43
Sample TaskCancelResponse message ...............................................................43
Sample ArticleMasterSetRequest message .........................................................44
Sample ArticleMasterSetResponse message .......................................................44
Sample StockDeliverySetRequest message ........................................................44
Sample StockDeliverySetResponse message ......................................................44
Sample ConfigurationGetRequest message ........................................................45
Sample ConfigurationGetResponse message ......................................................45
Sample StockLocationInfoRequest message .......................................................45
Sample StockLocationInfoResponse message ....................................................45
Sample InitiateInputRequest message .................................................................46
Sample InitiateInputResponse message ..............................................................46
Sample InitiateInputMessage message ................................................................46

Appendix B—Mosaic message configurations

Mosaic StockInputOrchestration & InitiateStockInputOrchestration
Configurations ......................................................................................................48

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide v

Contents

vi CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 About this guide

This guide describes the requirements for implementing an electronic interface

between ROWA™ and associated healthcare information systems. Messages sent
to ROWA are processed by the CareFusion Coordination Engine (CCE), which
includes a ROWA adapter that provides data mapping specific to the needs of
ROWA.
This document is not intended to be a stand-alone technical reference. You should
be familiar with the HL7 Messaging Standard, which provides the base technical
HL7 specifications.
For additional support information, contact the CareFusion Technical Support
Center (TSC) for ROWA products at 800.876.4287 from North America. From all
other locations, call 858.617.2000.

Acronyms
• CCE —CareFusion Coordination Engine
• PIS —Pharmacy information system

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide vii

About this guide

viii CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Chapter 1
Communications
considerations

This chapter describes communications considerations. The following topics are

discussed.
Network connection................................................................................... 2
Minimal lower layer protocol.................................................................... 3
Message structure...................................................................................... 4
Encoding characters ................................................................................. 5
Escape formatting codes ........................................................................... 6
Message trigger codes and event types ..................................................... 8
Message header segment—MSH............................................................... 9
Message acknowledgments ..................................................................... 11

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 1

Chapter 1—Communications considerations

Network connection
The CareFusion Coordination Engine (CCE) can participate in the network as a
client or server. In either of these roles, standard TCP/IP addresses and port
numbers must be established before any communication takes place using the
protocols defined in this document.
The CCE typically acts as a server for Pharmacy Information systems (PIS).You
must configure the server/client mode before participating in any networked
communication (no default is assumed).

2 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Minimal lower layer protocol

Minimal lower layer protocol

The CareFusion Coordination Engine (CCE) communicates using the HL7
minimal lower layer protocol. The message consisting of several HL7 segments is
the data unit transferred. The message is enclosed in a wrapper, which starts with
< S B > start-of-block notation, and ends with < E B > end-of-block notation,
followed by a carriage return character. Processed characters:

Minimal lower layer protocol

HL7 block ASCII characters HEX characters

<SB> <VT> 0x0B
<EB> <FS> 0x1C
<CR> <CR> 0x0D

Minimal blocked message example

The following is a blocked medication order segment. Refer to the message
segment descriptions for segment content details.
<0x0B>
Message header segment<CR>
Patient Identifier Segment<CR>
Patient Visit Segment<CR>
<0x1C><0x0D>

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 3

Chapter 1—Communications considerations

Message structure
In HL7, a message is the smallest unit of data transferred between systems. A
message is composed of a group of segments in a defined sequence. A segment,
which may be required or optional, is a logical grouping of data fields. The fields
may appear once or may repeat. A unique three-character segment ID code
identifies each segment. All segment ID codes beginning with Z are for user-
defined messages. This specification defines several Z segments.
As in the HL7 guideline, segments are introduced in the order of occurrence in a
message. In addition, each message is defined in notation, which lists the segment
IDs in the order they would appear in the message.
• Braces {...} indicate one or more repetitions of the enclosed segment or group
of segments.
• Brackets [...] show that the enclosed segment or group of segments is
optional.
• If a group of segments is optional and may repeat, it is enclosed in brackets
and braces {[...]} or [{...}]. The repeating segments processed by the CCE are
identified in their chapters.
The valid component segments processed by the CCE are identified in their
respective chapters.

Note
This specification contains segment definitions that are similar to the HL7
specification but with different and superseding field lengths.

4 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Encoding characters

Encoding characters
The standard message encoding characters shown in the table below are adopted
from the HL7 specification.

Encoding characters
Character HL7 message encoding characters
| Field separator
^ Component separator
& Subfield separator
~ Repeat
\ Escape

When generating HL7 messages for the host, the interface uses the standard
message encoding characters as the encoding characters in the message.
When parsing the HL7 message from the host, the interface parses based on the
encoding characters in the message being parsed.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 5

Chapter 1—Communications considerations

Escape formatting codes

Escape codes can be used in TX, FX, ST, and CF fields where standard HL7
message encoding characters must be sent as part of the messages.

Escape formatting codes

Escape codes Character HL7 message encoding characters

\F\ | Field separator
\S\ ^ Component separator
\T\ & Subfield separator
\R\ ~ Repeat
\E\ \ Escape

Escape format example

The instructions from the pharmacy indicate that the medication should be
swished in the mouth before swallowing. This instruction is selected from a list
and the format is Swish & Swallow. The ampersand is the subfield delimiter; and,
therefore, it is represented by the escape \T\.
RXE||MYCO001|5||ML|SUSP|HOLD FOR
NAUSEA||G|1|CUP||AS1212121|RX1^PILLROLLER,TOM||||||
|SWISH\T\SWALLOW|||||||||||||||

Field data population

The contents of a field can exist in the following three states:
• Populated—a value sent in the field.
• Not populated—the field is not valued. The sender may not have the
information or has elected not to supply it.
• Null—a value was previously communicated and should now be deleted. In
compliance with HL7, the null is represented using double quotes between
delimiters.

Data element maintenance support

• Action Code—Some segments use a specific action code. For example, the
IAM segment action code indicates whether the information is to be added,
updated, or deleted.
• Snapshot—The snapshot must be used for repeating segments without action
codes and for repeating fields without components. In both of these situations,
a change cannot be uniquely identified. To communicate the change, the

6 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Escape formatting codes

entire group of active data must be resent. For example, if pharmacy-encoded

order administration notes are changed, all retained notes are resent.
In the case of a field with repeating content where all content is to be omitted,
a null value can be sent.
• Null—The use of double quotes in a component or subcomponent indicates
that the previously communicated data is to be cleared. If an update message
is sent with an empty field and the message is not part of a snapshot set or has
an action code, the previously communicated data is not changed.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 7

Chapter 1—Communications considerations

Message trigger codes and event types

The HL7 defined trigger events supported by the CCE are detailed in the message
chapters. The trigger event provides notice that an event (such as patient
admission, patient observation, or a test result) has occurred and is being reported.
The trigger event is coupled with a message type to define the message format
used to convey the information.

8 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Message header segment—MSH

Message header segment—MSH

The master header segment (MSH) is contained in all HL7 messages. The MSH
defines the applications and facilities involved in the message, the message
processing parameters and message security.

Message header segment–MSH

Seq Segment: MSH Max

# HL7 Description Data type OPT length
MSH R 3
1 Field Separator ST R 1
2 Encoding characters ST R 4
3 Sending application HD R 15
4 Sending facility HD R 15
5 Receiving application HD R 15
6 Receiving facility HD R 15
7 Date/time of message TS R 26
8 Security ST X 0
9 Message type MSG R 7
9.1 Message code MSG R 3
9.2 Message trigger event MSG R 3
10 Message control ID ST RE 0
11 Processing ID PT R 1
12 Version ID VID R 8
13 Sequence number NM X 15
14 Continuation pointer ST X
15 Accept acknowledgement type ID O 2
16 Application acknowledgement type ID O 2
17 Country code ID X
18 Character set ID X
19 Principal language of message CE X
20 Alternate character set handling ID X
scheme
21 Command ST R
22 Source NM O 3
23 Destination NM O

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 9

Chapter 1—Communications considerations

• MSH–1–2 separator and encoding—The field separator and encoding

character define where message information breaks occur. Standard encoding
characters are defined in the encoding character section of this document.
• MSH–3 Sending application—Defines the application from which the
message was originated.
By default, this field provides the name of the health information system used
by the CareFusion™ Coordination Engine ROWA™ Adapter v1.4 to identify
the sender. The Pyxis™ Enterprise Server uses this information to partition
the information received from different IDN systems.
• MSH–4 Sending facility—Defines the organization, building, and operation
unit responsible for sending the message.
• MSH–5 Receiving application—“CareFusion” is the receiving application.
• MSH–6 Receiving facility—Lists the organization where the CareFusion
system receiving the message is located.
• MSH–7 Date/Time of message—Lists the timestamp field indicating when
the message was created. The minimum format required is c c y y m m d d .
• MSH–9 Message type—The format for the message type field is x x x ^ y y y.
° MSH–9.1 Message code—The message type code for the message. This
is the x x x portion of the message type.
° MSH–9.2 Message trigger event—The event code for the message. This
is the y y y portion of the message type.
• MSH–10 Message control ID—Uniquely identifies the message. This field
is echoed back in the MSA when the message is acknowledged.
• MSH–11 Processing ID—CareFusion expects a P. CareFusion can configure
the outbound ID to accommodate a receiving systems requirement.
• MSH–12 Version ID—Defines the HL7 version level at which the message is
encoded.
• MSH–13 Sequence number—CareFusion optionally processes sequence
orders.
• MSH–15 Accept acknowledgement—Controls the accept acknowledgement
type.
• MSH–16 Application acknowledgement type—Controls the application
acknowledgement type.
• MSH–21 Command—ROWA message type.
• MSH–22 Source—The subscriber ID for the receiving MBM of the message.
This is used for routing with CCE.IE:100.
• MSH-23 Destination—Destination ID of the system receiving the message.

10 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Message acknowledgments

Message acknowledgments
The CareFusion Coordination Engine (CCE) responds to all inbound messages
using the standard acknowledgment. The acknowledgment is a transmission
acceptance, not an application acknowledgment. Likewise, the CCE expects that
all transmitted messages be acknowledged in the same manner.
The standard HL7 acknowledgment message consists of an MSH segment
followed by a message acknowledgment (MSA) segment.
The Message Type field of the message header segment in an acknowledgment
message contains either ACK or QCK, and the Message Control ID is the same as
that provided by the host. The Message Header segment description defines the
other MSH fields. See Message header segment—MSH on page 9.
MSH. . . MSA
The MSH message type field is ACK or QCK and the control ID is host message
control ID. The other MSH fields are defined in the Message Header Segment
description.

MSA—Message Acknowledgement
The MSA segment contains the fields shown in the following table.

MSA–Message Acknowledgment

Segment: MSA Data Max

Seq # HL7 Description type RO RPT length
MSA R 3
1 Acknowledgment code ID R 2
2 Message control ID ST R 20
3 Text message ST O
4 Expected sequence number NM O
5 NOT USED W
6 Error condition CWE O

MSA–1 Acknowledgment code—CCE replies with an

original mode application accept code: AA
• MSA–2 Message control ID—The message control ID from the MSH
segment is echoed to the sending system.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 11

Chapter 1—Communications considerations

12 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Chapter 2
Data Types

This chapter describes the data types used in this specification., and includes
information on the following topics:
Basic data types....................................................................................... 14
Complex data types ................................................................................. 15

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 13

Chapter 2—Data Types

Basic data types

Basic data types

Data
type Name Length Category Comment
ID Coded value HL7 Var Identifier
IS Coded value user 20 Identifier
identifier
MSG Message type 15 Identifier
NM Numeric 16 Numerical
ST String 199 Alphanumeric
TS Timestamp 24 Numerical YYYY[MM[DD[HH[MM[SS]]]]]
VID Version identifier 973 Identifier Identifier

14 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Complex data types

Complex data types

CE—Coded Elements

Data
Seq Len type Usage Element name
1 20 ST R Identifier
2 199 ST R Text
3 20 ID RE Name of coding system
4 20 ST RE Alternate identifier
5 199 ST RE Alternate text
6 20 ID RE Name of alternate coding system

CWE-Coded with Exceptions

Data
Seq Len type Usage Element name
1 20 ST R Identifier
2 199 ST R Text
3 20 ID R Name of Coding System
4 20 ST RE Alternate Identifier
5 199 ST RE Alternate Text
6 20 ID RE Name of Alternate Coding System
7 10 ST X Coding System Version ID
8 10 ST X Alternate Coding System Version
ID
9 199 ST X Original Text

CX—Extended Composite ID

Seq Length Data type Usage Element name

1 15 ST R ID number
2 1 ST X Check digit
3 3 ID X Check digit scheme
4 227 HD R Assigning authority
5 5 ID R Identifier type code
6 227 HD X Assigning facility

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 15

Chapter 2—Data Types

CX—Extended Composite ID

Seq Length Data type Usage Element name

7 8 DT X Effective date
8 8 DT X Expiration date
9 705 CWE X Assigning jurisdiction
10 705 CWE X Assigning agency or department

EI—Entity identifier

Seq Length Data type Usage Element name

1 16 ST R Entity Identifier
2 20 IS RE Namespace ID
3 199 ST RE Universal ID
4 6 ID RE Universal ID Type

HD—Hierarchic designator

Seq Length Data type Usage Element name

1 20 IS R Namespace ID
2 199 ST X Universal ID
3 6 ID X Universal ID type

16 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Chapter 3
ROWA Adapter v1.2
Specifications

This chapter describes the message specifications for communicating ROWA

messages via the CCE and pharmacy systems. The following topics are discussed.
ROWA messages...................................................................................... 18
Segment field details by message ............................................................ 32
Message flow ........................................................................................... 35

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 17

ROWA Adapter v1.2 Specifications

ROWA messages
The ROWA messages are communications between one pharmacy and one robot.
These messages are asynchronous. The HL7 for the communication is a
combination of four segments: MSH, QRD, ZFX and ZPM. The MSH segment is
standard across all messages; for more information, see Communications
considerations on page 1.

18 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

ROWA to host message structures

Message type HL7 segment
Command (MSH.21) (MSH.9) layout
InputRequest QRY^Q02 MSH
QRD
InputMessage ZPM^ MSH
{ZPM}
StatusResponse QRY^Q03 MSH
QRD
OutputResponse QRY^Q03 MSH
QRD
{ZPM}
OutputMessage DFT^ MSH
QRD
{ZFX}
StockInfoResponse ZPM^ MSH
{ZPM}
DSC
TaskInfoResponse QRY^Q03 MSH
{QRD}
ZPM
TaskCancelResponse QRY^Q03 MSH
{QRD}
ArticleMasterSetResponse QRY^Q02 MSH
QRD
StockDeliverySetResponse QRY^Q02 MSH
QRD
ConfigurationGetResponse QRY^Q02 MSH
QRD
StockLocationInfoResponse ZPM^ MSH
ZPM
InitiateInputResponse DFT^ MSH
QRD
InitiateInputMessage DFT^ MSH
QRD

Note
Brackets { } indicate a repeatable segment.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 19

ROWA Adapter v1.2 Specifications

Host to ROWA message structures

Message type HL7 segment
Command (MSH.21) (MSH.9) layout
InputResponse MFN^ MSH
{ZFX}
StatusRequest QRY^Q02 MSH
QRD
OutputRequest QRY^Q02 MSH
QRD
[{ZPM}]
StockInfoRequest QRY^Q02 MSH
QRD
[{ZPM}]
TaskInfoRequest QRY^Q02 MSH
{QRD}
TaskCancelRequest QRY^Q02 MSH
{QRD}
ArticleMasterSetRequest MFN MSH
{ZPM}
StockDeliverySetRequest MFN MSH
{ZPM}
ConfigurationGetRequest QRY^Q02 MSH
StockLocationInfoRequest QRY^Q02 MSH
InitiateInputRequest QRY^Q02 MSH
QRD

Note
Brackets { } indicate a repeatable segment and brackets [ ]indicate an optional
segment.

QRD segment
Data Max
Seq# HL7 description type R/O length
0 QRD R 3
1 Query Timestamp TS R 24
2 Command ST O
3 Details Priority ST O
4 NOT USED ST O
5 Details Status ST O
6 Output Destination ID O

20 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

Data Max
Seq# HL7 description type R/O length
7 State ST O
8 State Description ST O
9 Include Pack Data ST O 5
10 Package Index NM O 16
11 ScanCode ST O
12 Task Id NM O 16
13 Task Type ST O
14 Task Status ST O
15 Packing Indicator ST O 5
16 New Delivery ST O 5
17 Box Number ST O
18 Delivery Number ST O
19 Expiry Date ST O 10
20 Sub Item Quantity ST O
21 Value ST O
22 Text ST O
23 Batch Number ST O

24 Stock Location Id ST O
25 Machine Location Id ST O
26 External Id ST O
27 Include Details ST O
28 Output Point ID O
29 Include Task Details ST O
30 Type ST O
31 Description ST O
32 State ST O
33 State Text ST O
34 Input Source ST M
35 Input Point ST O
36 Depth NM O
37 Width NM O

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 21

ROWA Adapter v1.2 Specifications

Data Max
Seq# HL7 description type R/O length

38 Height NM O
39 Shape ST O

• QRD.2 – Command – The command of the message. IE: InputRequest

• QRD.3 – Details Priority – Priority of the output process. Possible values are:
° Low
° Normal
° High
• QRD.5 – Details Status – Defines the status of the output process. Possible
values are:
° Queued
° Rejected
° Complete
° Incomplete
° Aborted
• QRD.6 – Output Destination – Number which defines the output destination.
• QRD.7 – State – Current state of the system. Possible values are:
° Ready
° NotReady
• QRD.8 – State Text – Additional free text field for English debugging and
logging information.
• QRD.9 – Include Package Data – Should the package data be included in
messages. Possible values are:
° True
° False
• QRD10 – Pack Index – Unique index of the package within the command.
• QRD.11 – Scan Code – Complete scan code of the package.
• QRD.12 – Task Id - Identifier of the task.
• QRD.13 – Task Type – Type of task. Always “Output”.
• QRD.14 – Task Status - Status of the task. Possible value are:
° Unknown
° Queued
° InProcess
° Aborted
° Completed

22 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

° Incomplete
° Cancelled
° CancelError
• QRD.15 – Packing Indicator - Enforce the redefinition of the pack article as
storage system article. Possible values are:
° True
° False
• QRD.16 – New Delivery - Defines whether this belongs to a stock deliver.
Possible values are:
° True
° False
• QRD.17 – Box Number - Number of the box.
• QRD.18 – Delivery Number - Delivery number for this pack.
• QRD.19 – Expiry Date - Expiry date of the pack in the format “YYYY-MM-
DD”
• QRD.20–Sub Item Quantity–Number of units (e.g., pills or ampules)
currently in the pack.
• QRD.21–Value–Displays the result of the master data process. Possible
values: “Accepted” if the articles were accepted as a master article,
“Rejected” if the articles were not accepted as a master article.
• QRD.22–Text–Any text for debugging and logging information. Can be used
here for detailed error messages if the articles were not accepted.
• QRD.23–Batch Number–By setting this filter, only packs with the specified
batch number are included.
• QRD.24–Stock Location Id–ID of the selected stock location in the
automated storage and retrieval system. This is only used when an automated
storage and retrieval system is divided into several virtual stock locations.
• QRD.25–Machine Location–Identification of the requesting machine
intended to be used for storing the pack. This is only relevant if the automated
storage and retrieval system consists of several physical stand-alone
machines.
• QRD.26–External Id–This is an additional identifying attribute. This can be
used, for example, to store additional information about the pack (e.g. the
serial number).
• QRD.27–Include Details– Optional data, indicates whether the
StatusResponse is intended to contain component information. The default
value is “True”
• QRD.28–Output Point–Detailed information on the requested output location
(e.g. belt number).

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 23

ROWA Adapter v1.2 Specifications

• QRD.29–Include Task Details–This flag specifies whether detailed task

information like outputted packs, etc. are to be returned. Contains the
following possible values:
• “True” if details of the tasks are to be sent.
• “False” if no task data is to be sent.
NOTE: The default value is “False”.
• QRD.30–Type–Contains the following possible values:
• StorageSystem
• BoxSystem
• QRD.31–Description–This text can be displayed on program interfaces.
• QRD.32–State–Designates the current status of the component. Contains the
following possible values:
• Ready
• NotReady
• QRD.33–State Text–Any text for debugging and logging information.
• QRD.34–Input Source– Identifies the transfer point to the automated storage
and retrieval system intended to be used for the stock input.
• QRD.35–Input Point– Detailed information on the output location used (e.g.
belt number). If this property was not defined in the associated
InitiateInputRequest, the automated storage and retrieval system can here
return the detailed transfer point that was automatically determined.
• QRD.36–Depth–Depth of the pack in mm.
• QRD.37–Width–Width of the pack in mm.
• QRD.38–Height–Height of the pack in mm.
• QRD.39–Shape–Form factor of the pack. The default is “Cuboid”. “Cylinder”
is also supported.

ZFX segment
Data Max
Seq# HL7 description type R/O length
0 ZFX R 3
1 NOT USED ST X
2 Article Info CE O
2.1 Article Id ST O
2.2 Article Name ST O
2.3 New Delivery ST O 5
3.9 NOT USED ST X

24 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

Data Max
Seq# HL7 description type R/O length
10 Dosage Info CE O
10.1 Dosage Form ST O
10.2 Packaging Unit ST O
11 Package Info CE O
11.1 Package Index NM O 16
11.2 Package Id ID O
11.3 Batch Number ST O
11.4 External Id ST O
11.5 Expiry Date ST O
11.6 Box Number ST O
11.7 Delivery Number ST O
11.8 Depth NM O
11.9 Width NM O
11.10 Height NM O
11.11 Shape ST O
11.12 Is In Fridge ST O 5
11.13 Handling Input ST O
11.14 Handling Description ST O
12.3 Sub Item Quantity ST O
12.4 Max SubItem Quantity ST O
12.5 Stock Location Id ST O
12.6 Machine Location ST O
12.7 Output Destination ID M
12.8 Output Point ID O
12.9 Label Status ST O
12.10 State ST O
12.11 Type ST R
12.12 Text ST O
12.13 Scan Code ST M

• ZFX.2.1 – Article Id – The article identifier to use when storing the article in
the storage system.
• ZFX.2.2 – Article Name – Name of the article.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 25

ROWA Adapter v1.2 Specifications

• ZFX.2.3 – New Delivery – Defines whether this belongs to a stock deliver.

Possible values are:
° True
° False
• ZFX.10.1 – Dosage Form – The dosage form of the article.
• ZFX.10.2 – Packaging Unit – Packaging unit information of the article.
• ZFX.11.1 – Package Index –Unique index of the pack in the message.
• ZFX.11.2 – Package Id – The storage system internal package identifier.
• ZFX.11.3 – Batch Number – Commercial batch number.
• ZFX.11.4 – External Id – Additional identifier of the pack.
• ZFX.11.5 – Expiry Date – Expiry date of the pack in the format “YYYY-
MM-DD” extracted from the pack scan code.
• ZFX.11.6 – Box Number - Number of the box.
• ZFX.11.7 – Delivery Number - Delivery number for this pack.
• ZFX.11.8 – Depth – Depth of the pack in mm.
• ZFX.11.9 – Width – Width of the pack in mm.
• ZFX.11.10 – Height – Height of the pack in mm.
• ZFX.11.11 – Shape – Shape definition of the pack. Possible values are:
° Cuboid
° Cylinder
• ZFX.11.12 – Is In Fridge – Flag whether this pack is stored in a refrigerator.
Possible values are:
° True
° False
• ZFX.11.13 – Handling Input – Handling instruction for the package. Possible
values are:
° Allowed
° AllowedForFridge
° Rejected
° RejectedNoExpiryDate
° RejectedNoPickingIndicator
° Completed
° Aborted
• ZFX.11.14 – Handling Description – Free text field for additional English
descriptive information regarding the handling instructions.
• ZFX.12.3–SubItemQuantity–Number of units (e.g., pills or ampules)
currently in the pack. The value “O” means that the pack is full (unbroken).

26 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

• ZFX.12.4–Maximum SubItem Quantity–Maximum number of units (e.g.,

pills or ampules) which might be contained in a full pack of the article. The
value “O” means that the number of units is unknown.
• ZFX.12.5–Stock Location Id–ID of the selected stock location in the
automated storage and retrieval system. This is only used when an automated
storage and retrieval system is divided into several virtual stock locations.
• ZFX.12.6–Machine Location–Identification of the requesting machine
intended to be used for storing the pack. This is only relevant if the automated
storage and retrieval system consists of several physical stand-alone
machines.
• ZFX.12.7–Output Destination–Number of the output point to which the pack
was sent. A possible error case is output to a point other than the one
requested, for example because the requested output point was not
operational.
• ZFX.12.8–Output Point–Detailed information on the output location (e.g. belt
number) used for pack output.
• ZFX.12.9–Label Status–Status of the labeling of the outputted pack. This is
only relevant in conjunction with labeling. Possible values: "Labelled" if the
pack was labeled correctly with the data predefined by the pharmacy IT
system "NotLabelled" if the pack was not labeled (e.g. because no printer was
available) "LabelError" if an error occurred during labeling.
• ZFX.12.10–State– Status of the pack. This data is required when multiple
automatic storage machines are connected. The default value "Available"
means that the pack is currently available for output. "NotAvailable" is also
supported.
• ZFX.12.11–Type– Detailed error that occurred during stock input.
• ZFX.12.12–Text– Any text for detailed error information.
• ZFX.12.13–Scan Code–Barcode of the pack being placed into stock. This
code is checked by the pharmacy IT system and compared against internal
data. Based on the information contained in the code, the pharmacy IT system
can decide whether the pack can be placed into stock. Here the same value is
to be seen as in the associated InitiateInputRequest.

ZPM segment
Data Max
Seq# HL7 description type R/O length
0 ZPM R 3
1..5 NOT USED ST X
6 Article Id ST R
7 Article Name ST O
8..10 NOT USED ST X

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 27

ROWA Adapter v1.2 Specifications

Data Max
Seq# HL7 description type R/O length
11 Article Quantity NM O 16
12..34 NOT USED ST X
34 Dosage Form ST O
35..56 NOT USED ST X
57 Packaging Unit ST O
58 Batch Number ST O
59 External Id ST O
60 Package Index ST O
61 Package Id NM O 16
62 Expiry Date ST O
63 Delivery Number ST O
64 Depth NM O
65 Width NM O
66 Height NM O
67 Shape ST O
68 Is In Fridge ST O 5
69 State ST O
70 New Delivery ST O 5
71 Handling Input ST O
72 Handling Description ST O
73 Sub Item Quantity ST O
74 Max Sub Item Quantity ST O
75 Stock Delivery Number ST O
76 Requires Fridge ST O
77 Batch Number ST O
78 External ID ST O
79 Expiry Date ST O

80 Stock Location Id ST O
81 Machine Location ST O
82 Template Id ST R
83 Content ST R
84 Output Destination ID R
85 Output Point ID O

28 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

Data Max
Seq# HL7 description type R/O length

86 Label Status ST O
87 Number ST R
88 Location Id ST R
89 Location Description ST O

• ZPM.6 – Article Id – The article identifier to use when storing the article in
the storage system.
• ZPM.7 – Article Name – Name of the article.
• ZPM.11 – Article Quantity – A quantity count.
• ZPM.34 – Dosage Form – The dosage form of the article.
• ZPM.57 – Packaging Unit – Packaging unit information of the article.
• ZPM.58 – Batch Number – Commercial batch number.
• ZPM.59 – External Id – Additional identifier of the pack.
• ZPM.60 – Package Index – Unique index of the pack in the message.
• ZPM.61 – Package Id – The storage system internal package identifier.
• ZPM.62 – Expiry Date – Expiry date of the pack in the format “YYYY-MM-
DD” extracted from the pack scan code.
• ZPM.63 – Delivery Number – Delivery number for this pack.
• ZPM.64 – Depth – Depth of the pack in mm.
• ZPM.65 – Width – Width of the pack in mm.
• ZPM.66 – Height – Height of the pack in mm.
• ZPM.67 – Shape – Shape definition of the pack. Possible values are:
° Cuboid
° Cylinder
• ZPM.68 – Is In Fridge – Flag whether this pack is stored in a refrigerator.
Possible values are:
° True
° False
• ZPM.69 – State – Available state of the pack. Possible values are:
° Available
° NotAvailable
• ZPM.70 – New Delivery – Defines whether this belongs to a stock deliver.
Possible values are:
° True
° False

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 29

ROWA Adapter v1.2 Specifications

• ZPM.71 – Handling Input – Handling instruction for the package. Possible

values are:
° Allowed
° AllowedForFridge
° Rejected
° RejectedNoExpiryDate
° RejectedNoPickingIndicator
° Completed
° Aborted
• ZPM.72 – Handling Description – Free text field for additional English
descriptive information regarding the handling instructions.
• ZPM.73–Sub Item Quantity–Number of units (pills or ampules) currently in
the pack. The value “O” means that the pack is full (unbroken).
• ZPM.74–Max Sub Item Quantity–Maximum number of units (pills or
ampules) which might be contained in a full pack of the article. The value “O”
means that the number of units is unknown.
• ZPM.75–Stock Delivery Number–ID of the stock delivery. This must be a
unique number within all active or pending stock deliveries. This number is
used by the automated storage and retrieval system to assign packs placed into
stock to a stock delivery.
• ZPM.76–Require Fridge–Flag indicating whether the article has to be stored
refrigerated (“True”). The default value is “False”.
• ZPM.77–Batch Number–Batch number which must be assigned to the packs
of the article in the stock delivery.
• ZPM.78–External ID–External ID which must be assigned to the packs of the
article in this stock delivery.
• ZPM.79–Expiry Date–Expiry date in format YYYY-MM-DD which must be
assigned to the packs of the article in this stock delivery.
• ZPM.80–Stock Location Id–ID of the selected stock location in the
automated storage and retrieval system. This is only used when an automated
storage and retrieval system is divided into several virtual stock locations.
NOTE: The Output Request and Output Response messages, filter for packs
having the specified ID of the selected stock location in the automated storage
and retrieval system.
• ZPM.81– Machine Location–Identification of the machine used for storing
the pack. This is only relevant if the automated storage and retrieval system
consists of several physical stand-alone machines.
NOTE: The Output Request and Output Response messages, filter for packs
having the specified identification of the requesting machine intended to be
used for storing the pack.

30 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 ROWA messages

• ZPM.82– Template Id–ID of the label template to be used by the label printer
for correct output of the label content.
• ZPM.83– Content–Label content to be printed. This data is embedded in the
message as a CDATA XML block.
• ZPM.84–Output Destination–This data is only required for the “Output” task
type. Number of the output point to which the pack was sent. A possible error
case is output to a point other than the one requested, for example because the
requested output point was not operational.
• ZPM.85–Output Point–This data is only required for the “Output” task type.
Detailed information on the output location (e.g. belt number) used for pack
output.
• ZPM.86–Label Status–This data is only required for the " Output " task type.
Status of the labeling of the outputted pack. This is only relevant in
conjunction with labeling. Possible values:
• Labelled–if the pack was labeled correctly with the data predefined by the
pharmacy information system.
• NotLabelled–if the pack was not labeled (e.g. because no printer was
available).
• LabelError – if an error occurred during labeling.
• ZPM.87–Number– Number of the container to which the pack was outputted.
The data is only required for the "Output" task type if an automatic box filler
is being used.
• ZPM.88–Id–Identification of the stock location.
• ZPM.89–Description–Optional description of the stock location.

DSC segment
DS

Data Max
Seq# HL7 description type R/O length
0 DSC R 3
1 Continuation Pointer ST O

• DSC.1-Continuation Pointer-Pointer to identify the response continuation.

NOTE: A response message with no DSC segment is a complete response. A
response with a DSC segment is a partial response with more data to follow.

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 31

ROWA Adapter v1.2 Specifications

Segment field details by message

For MSH type codes and commands, see ROWA to host message structures on
page 19.

Input request
[QRD.10, QRD.11, QRD.15, QRD.16, QRD.18, QRD.19, QRD.20, QRD.23,
QRD.24, QRD.25, QRD.26]

Input response
[ZFX.2.1, ZFX.2.2, ZFX.2.3, ZFX.10.1, ZFX.10.2, ZFX. 11.1, ZFX. 11.3, ZFX.
11.4, ZFX.11.5, ZFX.11.7, ZFX.11.13, ZFX.11.14, ZFX.12.3, ZFX.12.4,
ZFX.12.5]

Input Message
[ZPM.6, ZPM.7, ZPM.34, ZPM.57, ZPM.58, ZPM.59, ZPM.60, ZPM.61,
ZPM.62, ZPM.63, ZPM.64, ZPM.65, ZPM.66, ZPM.67, ZPM.69, ZPM.70,
ZPM.71, ZPM.72, ZPM.73, ZPM.74, ZPM.80, ZPM.81]

Output Request
[QRD.3, QRD.6, QRD.17, QRD.28, ZPM.6, ZPM.11, ZPM.58, ZPM.59,
ZPM.61, ZPM.62, ZPM.73, ZPM.80, ZPM.81, ZPM.82, ZPM.83]

Output Response
[QRD.3, QRD.5, QRD.6, QRD.17, QRD.28, ZPM.6, ZPM.11, ZPM.58, ZPM.59,
ZPM.61, ZPM.62, ZPM.73, ZPM.80, ZPM.81, ZPM.82, ZPM.83]

Output Message
[QRD.3, QRD.5, QRD.6, QRD.28, ZFX.2.1, ZFX.11.2, ZFX.11.3, ZFX.11.4,
ZFX.11.5, ZFX.11.6, ZFX.11.7, ZFX.11.8, ZFX.11.9, ZFX.11.10, ZFX.11.11,
ZFX.11.12, ZFX.12.3, ZFX.12.5, ZFX.12.6, ZFX.12.7, ZFX.12.8, ZFX.12.9]

Stock Info Request

[QRD.9, QRD.27, ZPM.6, ZPM.58, ZPM.59, ZPM.80, ZPM.81]

Stock Info Response

[ZPM.6, ZPM.7, ZPM.11, ZPM.34, ZPM.57, ZPM.58, ZPM.59, ZPM.61,
ZPM.62, ZPM.63, ZPM.64, ZPM.65, ZPM.66, ZPM.67, ZPM.68, ZPM.69,
ZPM.73, ZPM.74, ZPM.80, ZPM.81, DSC.1]

32 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Segment field details by message

Status Request
[QRD.2, QRD.27]

Status Response
[QRD.7, QRD.8, QRD.30, QRD.31, QRD.32, QRD.33]

Task Info Request

[QRD.12, QRD.13, QRD.29]

Task Info Response

[QRD.12, QRD.13, QRD.14, ZPM.6, ZPM.11, ZPM.58, ZPM.59, ZPM.61,
ZPM.62, ZPM.63, ZPM.65, ZPM.66, ZPM.67, ZPM.68, ZPM.73, ZPM.80,
ZPM.81, ZPM.84, ZPM.85, ZPM.86, ZPM.87]

Task Cancel Request

[QRD.12, QRD.13]

Task Cancel Response

[QRD.12, QRD.13, QRD.14]

ArticleMasterSetRequest
[ZPM.6, ZPM.7, ZPM.34, ZPM.57, ZPM.74, ZPM.76]

AricleMasterSetResponse
[QRD.21, QRD.22]

StockDeliverySetRequest
[ZPM.6, ZPM.7, ZPM.11, ZPM.34, ZPM.57, ZPM.74, ZPM.75, ZPM.76,
ZPM.77, ZPM.78, ZPM.79]

StockDeliverySetResponse
[QRD.21, QRD.22]

ConfigurationGetRequest
[QRD is not required]

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 33

ROWA Adapter v1.2 Specifications

ConfigurationGetResponse
[QRD.22]

StockLocationInfoRequest
[QRD is not required]

StockLocationInfoResponse
[ZPM.88, ZPM.89]

InitiateInputRequest
[QRD.10, QRD.15, QRD.16, QRD.18, QRD.19, QRD.20, QRD.23, QRD.24,
QRD.25, QRD.26, QRD.34, QRD.35, QRD.36, QRD.37, QRD.38, QRD.39]

InitiateInputResponse
[QRD.5, QRD.15, QRD.16, QRD.34, QRD.35, ZFX.2.1, ZFX.2.2, ZFX.10.1,
ZFX.10.2, ZFX.11.1, ZFX.11.3, ZFX11.4, ZFX.11.5, ZFX.11.7, ZFX.11.8,
ZFX.11.9, ZFX.11.10, ZFX.11.11, ZFX.12.3, ZFX.12.4, ZFX.12.5, ZFX.12.13]

InitiateInputMessage
[QRD.5, QRD.34, QRD.35, ZFX.10.1, ZFX.10.2, ZFX.11.1, ZFX.11.3, ZFX11.4,
ZFX.11.5, ZFX.11.7, ZFX.11.8, ZFX.11.9, ZFX.11.10, ZFX.11.11, ZFX.12.3,
ZFX.12.4, ZFX.12.5, ZFX12.6, ZFX.12.10, ZFX.12.11, ZFX.12.12]

34 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Message flow

Message flow
The thirteen message flow sequences are as follows:
1. Initialization of Connection
a. HelloRequest (initiated by Pharmacy)
b. HelloResponse (from ROWA)
2. Active Connection Check
a. KeepAliveRequest (can be initiated by Pharmacy or by ROWA)
b. KeepAliveResponse (can be sent by Pharmacy or by ROWA)
3. Status of System
a. StatusRequest (initiated by Pharmacy)
b. StatusResponse (from ROWA)
4. Input of Packs
a. InputRequest (initiated by ROWA)
b. InputResponse (from Pharmacy)
c. InputMessage (from ROWA)
5. Ensure Packs Positioning
a. InitiateInputRequest (initiated by Pharmacy)
b. InitiateInputResponse (from ROWA)
c. InputRequest (from ROWA)
d. InputResponse (from Pharmacy)
e. InputMessage (from ROWA)
f. InitiateInputMessage (from ROWA)
6. Stock Synchronization
a. StockInfoRequest (initiated by Pharmacy)
b. StockInfoResponse (from ROWA)
7. Output of Packs
a. OutputRequest (initiated by Pharmacy)
b. OutputResponse (from ROWA)
c. OutputMessage (from ROWA)
8. Manual Pack Output
a. OutputMessage (initiated by ROWA)
9. Query State of a Task
a. TaskInfoRequest (initiated by Pharmacy)
b. TaskInfoResponse (from ROWA)
10. Cancellation of Tasks
a. TaskCancelRequest (initiated by Pharmacy)
b. TaskCancelResponse (from ROWA)

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 35

ROWA Adapter v1.2 Specifications

11. Master Data

a. ArticleMasterSetRequest (initiated by Pharmacy)
b. ArticleMasterSetResponse (from ROWA)
c. StockDeliverySetRequest (initiated by Pharmacy)
d. StockDeliverySetResponse (from ROWA)
12. Configuration Checking of ROWA
a. ConfigurationGetRequest (initated from Pharmacy)
b. ConfigurationGetResponse (from ROWA)
13. Check Configured Stock Locations
a. StockLocationInfoRequest (initated from Pharmacy)
b. StockLocationInfoResponse (from ROWA)

36 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Appendix A
Sample messages

This appendix contains the following examples:

• Sample InitiateInputMessage message on page 46Sample StatusRequest
message on page 38
• Sample StatusResponse message on page 38
• Sample InputRequest message on page 38
• Sample InputResponse message on page 39
• Sample InputMessage message on page 39
• Sample StockInfoRequest message on page 40
• Sample StockInfoResponse message on page 41
• Sample OutputRequest message on page 42
• Sample OutputResponse message on page 42
• Sample OutputMessage message on page 42
• Sample TaskInfoRequest message on page 43
• Sample TaskInfoResponse message on page 43
• Sample TaskCancelRequest message on page 43
• Sample TaskCancelResponse message on page 43

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 37

Appendix A—Sample messages

• Sample ArticleMasterSetRequest message on page 44

• Sample ArticleMasterSetResponse message on page 44
• Sample StockDeliverySetRequest message on page 44
• Sample StockDeliverySetResponse message on page 44
• Sample ConfigurationGetRequest message on page 45
• Sample ConfigurationGetResponse message on page 45
• Sample StockLocationInfoRequest message on page 45
• Sample StockLocationInfoResponse message on page 45
• Sample InitiateInputRequest message on page 46
• Sample InitiateInputResponse message on page 46

on page 46Sample
Sample InitiateInputMessage message
StatusRequest message
With Component Information
MSH|^~\&|||||20130709102506||QRY^Q02|1002|P|2.2|||NE|NE|||||StatusRequest|1
00
QRD|20130617|StatusRequest|
Without Component Information
MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.2|||NE|NE|||||StatusRequest|100|999|
QRD|20130617|StatusRequest|||||||||||||||||||||||||False|

Sample StatusResponse message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q03|1003|P|2.3|||NE|NE|||||StatusResponse|999|100
QRD||StatusResponse|||||NotReady|||||||||||||||||||||||StorageSystem~StorageSystem~Bo
xSystem|Vmax 1~Vmax 2~Box System|Ready~Ready~NotReady|Box system plc
is turned off.~Box system plc is turned off.~Box system plc is turned off.||
ZPM|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Sample InputRequest message

1 package with optional data
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q02|1002|P|2.3|||NE|NE|||||InputRequest|999|100
QRD|20160122142802|InputRequest||PYX||||||0|0004-56-034-
G\F\00007\F\T\F\Omepra0004\F\PalH09051200001\F\051112\F\XXXXXX|||||Tr
ue||DeliveryNumber11|ExpiryDate11|10|||
B9898|StockLocationId11|MachineLocation11|ExternalId11|||||||||||||

38 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 3 packages
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q02|1002|P|2.3|||NE|NE|||||InputRequest|999|100
QRD|20160122143353|InputRequest||PYX||||||Index1~Index2~Index3|ScanCode1
~ScanCode2~ScanCode3|||||True||DeliveryNumber1~DeliveryNumber2~Delivery
Number3|ExpiryDate1~ExpiryDate2~ExpiryDate3|SubItemQuantity1~SubItemQ
uantity2~SubItemQuantity3|||
B9897~B9898~B9899|StockLocationId1~StockLocationId2~StockLocationId3|
MachineLocation1~MachineLocation2~MachineLocation3|ExternalId1~External
Id2~ExternalId3|||||||||||||

Sample InputResponse message

1 Article and 1 Package
MSH|^~\&|||||20130617||MFN|1009|P|2.3|||NE|NE|||||InputResponse|100|999
ZFX||0004-56-034-G00007T^ACCU CHEK AVIVA|True|||||||LOE^1X2.5
ML|1^^Omepra0004^PalH09051200001^2012-11-
05^^delivery12^^^^^^Allowed^Pack input allowed|^^1^2|
1 Article and 1 Package
MSH|^~\&|||||20130617||MFN|1009|P|2.3|||NE|NE|||||InputResponse|100|999|
ZFX||0004-56-034-G00007T^ACCU CHEK AVIVA|True|||||||LOE^1X2.5
ML|1^^Omepra0004^PalH09051200001^2012-11-
05^^delivery12^^^^^^Allowed^Pack input allowed|^^0^10^StockLocation|
2 Articles and 3 Packages
MSH|^~\&|||||20130617||MFN|1009|P|2.3|||NE|NE|||||InputResponse|100
ZFX||0004-56-034-G00007T^ACCU CHEK AVIVA^True ||||||||LOE^1X2.5
ML|1^^Omepra0004^PalH09051200001^2012-11-05^^^^^^^^Allowed^Pack
input allowed
ZFX||0004-56-034-G00025T^ACCU CHEK AVIVA^True ||||||||LOE^1X2.5
ML|2^^Omepra0024^PalH09051200002^2012-11-02^^^^^^^^Allowed^Pack
input allowed~3^^Omepra0034^PalH09051200003^2012-11-
03^^^^^^^^Allowed^Pack input allowed

Sample InputMessage message

1 Package
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20151127164605||ZP
M|2147483647|P|2.3|||NE|NE|||||InputMessage|2147483647|2147483647
ZPM||||||Id1|Name1|||||||||||||||||||||||||||DosageForm8|||||||||||||||||||||||PackingUnit3|BatchNu
mber9|ExternalId3|0||||||||||||||||||||StockLocationId1|MachineLocation1||||||||
1 Package with optional data

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 39

Appendix A—Sample messages

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1002|P|2.3|||NE|NE|||||InputMessage|999|100 ZPM||||||0004-56-034-
G00007T|ACCU CHEK AVIVA|||||||||||||||||||||||||||LOE|||||||||||||||||||||||1X2.5
ML|Omepra0004|PalH09051200001|0|565362|2012-11-
05||50|50|50|||||Completed|Pack input completed.|||||||||||||||||
2 Packages
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20151127164605||ZP
M|2147483647|P|2.3|||NE|NE|||||InputMessage|2147483647|2147483647
ZPM||||||Id1|Name1|||||||||||||||||||||||||||DosageForm8|||||||||||||||||||||||PackingUnit3|BatchNu
mber9~BatchNumber2|ExternalId3~ExternalId2|0~0||||||||||||||||||||StockLocationId1
~StockLocationId2|MachineLocation1~MachineLocation2|||||| 3 Packages
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20151127164605||ZP
M|2147483647|P|2.3|||NE|NE|||||InputMessage|2147483647|2147483647
ZPM||||||Id1|Name1|||||||||||||||||||||||||||DosageForm8|||||||||||||||||||||||PackingUnit3|BatchNu
mber9~BatchNumber2~BatchNumber2|ExternalId3~ExternalId2~ExternalId2|0~
0~0||||||||||||||||||||StockLocationId1~StockLocationId2~StockLocationId2|MachineL
ocation1~MachineLocation2~MachineLocation2||||||||
3 Packages
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20151127164605||ZP
M|2147483647|P|2.3|||NE|NE|||||InputMessage|2147483647|2147483647
ZPM||||||Id1|Name1|||||||||||||||||||||||||||DosageForm8|||||||||||||||||||||||PackingUnit3|BatchNu
mber9~BatchNumber2~BatchNumber2|ExternalId3~ExternalId2~ExternalId2|0~
0~0||||||||||||||||||||StockLocationId1~StockLocationId2~StockLocationId2|MachineL
ocation1~MachineLocation2~MachineLocation2||||||||

Sample StockInfoRequest message

Specific Specific Article with Article details and with Packs
MSH|^~\&|||||20130617||QRY^Q02|1010|P|2.3|||NE|NE|||||StockInfoRequest|100
QRD|20130617|StockInfoRequest|||||||True||
ZPM||||||0004-56-034-
G00025T||||||||||||||||||||||||||||||||||||||||||||||||||||batchnumber2|externalid8||||
Specific Article with Article and Packs details
MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.3|||NE|NE|||||StockInfoRequest|100|9
99 QRD|20130617|StockInfoRequest|||||||True||||||||||||||||||True|
ZPM||||||0004-56-034-
G00025T||||||||||||||||||||||||||||||||||||||||||||||||||||batchnumber2|externalid8||||
All Articles without Packs
MSH|^~\&|||||20130617||QRY^Q02|1010|P|2.3|||NE|NE|||||StockInfoRequest|100
QRD|20130617|StockInfoRequest||||||| ||
All Articles with Article details and without Packs

40 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.3|||NE|NE|||||StockInfoRequest|100|9
99 QRD|20130617|StockInfoRequest||||||| ||||||||||||||||||True
All Articles with Packs from specific Machine Location
MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.3|||NE|NE|||||StockInfoRequest|100|9
99| QRD|20130617|StockInfoRequest||||||| ||||||||||||||||||True| ZPM||||||0004-56-034-
G00025T||||||||||||||||||||||||||||||||||||||||||||||||||||batchnumber2|externalid8||||||||||||||||||||||Vmax 1|

Sample StockInfoResponse message

1 Article 1 Pack
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1003|P|2.3|||NE|NE|||||StockInfoResponse|999|100 ZPM||||||0004-56-034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004|PalH09051200001||4536|2015-
11-05||50|50|50
1 Article 1 Pack with DSC Segment
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1002|P|2.3|||NE|NE|||||StockInfoResponse|999|100 ZPM||||||0004-56-034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004|PalH09051200001||4536|2015-
11-05||50|50|50 DSC|SIR1002-1 1 Article 2 Packs
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1003|P|2.3|||NE|NE|||||StockInfoResponse|999|100 ZPM||||||0004-56-034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004~Omepra0004|PalH090512000
01~PalH09051200001||4536~4536|2015-11-05~2015-11-
05||50~50|50~50|50~50|Cuboid~Cuboid||Available~Available
1 Article 2 Packs
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1003|P|2.3|||NE|NE|||||StockInfoResponse|999|100ZPM||||||0004-56-034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004~Omepra0004|PalH090512000
01~PalH09051200001||4536~4536|2015-11-05~2015-11-
05||50~50|50~50|50~50|Cuboid~Cuboid||Available~Available
2 Article 2 Packs
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|1003|P|2.3|||NE|NE|||||StockInfoResponse|999|100 ZPM||||||0004-56-034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004~Omepra0004|PalH090512000
01~PalH09051200001||4536~4536|2015-11-05~2015-11-
05||50~50|50~50|50~50|Cuboid~Cuboid||Available~Available ZPM||||||0004-56-
034-
G00007T|||||3|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004~Omepra0004|PalH090512000
01~PalH09051200001||4536~4536|2015-11-05~2015-11-
05||50~50|50~50|50~50|Cuboid~Cuboid||Available~Available

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 41

Appendix A—Sample messages

Sample OutputRequest message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q03|1004|P|2.3|||NE|NE|||||OutputRequest|999|100|
QRD|20130617|OutputRequest|Normal|||3|||||||||||box456|||||||||||outputpoint||||
ZPM||||||Criteria1|||||1|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||StockLocationId1|Machin
eLocation1|TemplateId1_Label1_Criteria1~TemplateId1_Label2_Criteria1|<![C
DATA[ <Label1_Criteria1> ]]>~<![CDATA[ <Label2_Criteria1> ]]>|
ZPM||||||Criteria2|||||1|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||StockLocationId2|Machin
eLocation2|TemplateId1_Label1_Criteria2~TemplateId1_Label2_Criteria2|<![C
DATA[ <Label1_Criteria2> ]]>~<![CDATA[ <Label2_Criteria2> ]]>|
ZPM||||||Criteria3|||||1|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||StockLocationId3|Machin
eLocation3|TemplateId1_Label1_Criteria3~TemplateId1_Label2_Criteria3|<![C
DATA[ <Label1_Criteria3> ]]>~<![CDATA[ <Label2_Criteria3> ]]>|
ZPM||||||Criteria4|||||1|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||StockLocationId4|Machin
eLocation4|TemplateId1_Label1_Criteria4~TemplateId1_Label2_Criteria4|<![C
DATA[ <Label1_Criteria4> ]]>~<![CDATA[ <Label2_Criteria4> ]]>

Sample OutputResponse message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q03|1005|P|2.3|||NE|NE|||||OutputResponse|999|100
QRD||OutputResponse|Normal||Queued|3|||||||||||bx3366|||10||||StockLocationId1|M
achineLocation1|||||||||||||| ZPM||||||0004-56-034-
G00025T|||||1||||||||||||||||||||||||||||||||||||||||||||||||||7744||||||||||||10|||||||StockLocationId1|Machin
eLocation1|TemplateId1_Label1_Criteria1|<![CDATA[ <Label1_Criteria1>
]]>||||bx3366|| ZPM||||||0004-56-034-
G00007T|||||2|||||||||||||||||||||||||||||||||||||||||||||||Omepra0004|PalH09051200001||7744|2015-
11-
01||||||||||||||||||StockLocationId2|MachineLocation2|TemplateId1_Label1_Criteria2|
<![CDATA[ <Label1_Criteria2> ]]>||||||

Sample OutputMessage message

Completed
MSH|^~\&| | | |
|20130618151915||DFT|1015|P|2.3|||NE|NE|||||OutputMessage|999|100 |
QRD||OutputMessage|||Complete|3||||5~9|||| |
ZFX||0004-56-034-G00007T|||||||||^5^BatchNumber9^ExternalId3^2016-07-
10~9^BatchNumber9^ExternalId6^2016-06-06|^^0|
ZFX||0004-56-034-G00025T|||||||||^9^BatchNumber3^ExternalId9^2014-01-
27^box987^delivery99^50^50^50^ Cylinder^True|^^0|
With optional data
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||DFT
|1004|P|2.3|||NE|NE|||||OutputMessage|999|100

42 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 QRD||OutputMessage|Normal||Completed|detailOutputDestination_1||||||||||| ||| ||| | | |
||detailOutputPoint||||||||||| ZFX||0004-56-034-
G00025T|||||||||^5637^Omepra0004^PalH09051200001^2015-11-
05^Box1^^50^50^50^Cuboid^False|^^SubItemQuantity1^^StockLocation_1^Ma
chineLocation_1^packOutputDestination_1^OutputPoint_1^LabelStatus_1
ZFX||0004-56-034-G00007T|||||||||^8563^Omepra0004^PalH09051200001^2015-
11-
05^Box2^^70^70^70^Cuboid^True|^^SubItemQuantity2^^StockLocation_2^Ma
chineLocation_2^packOutputDestination_2^OutputPoint_2^LabelStatus_2
Incompleted
MSH|^~\&| | | | |20130710154856||DFT|1113|P|2.3|||NE|NE|||||OutputMessage|100
QRD||OutputMessage|Normal||Incomplete|3||||||||

Sample TaskInfoRequest message

Without detailed information
MSH|^~\&|||||20130617||QRY^Q02|3001|P|2.3|||NE|NE|||||TaskInfoRequest|100
QRD|20130617|TaskInfoRequest||||||||||9921|Output|
With detailed information
MSH|^~\&|||||20130617||QRY^Q02|3001|P|2.3|||NE|NE|||||TaskInfoRequest|100|99
9| QRD|20130617|TaskInfoRequest||||||||||9921|Output||||||||||||||||1

Sample TaskInfoResponse message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q03|3330|P|2.3|||NE|NE|||||TaskInfoResponse|999|100
QRD||TaskInfoResponse||||||||||1004|Output|Completed|||BoxNumber1|||SubItemQ
uantity1|||BatchNumber1|StockLocation1|MachineLocation1|ExternalId1||||||||||De
pth1|Width1|Height1|Shape1
ZPM||||||ArticleId|||||Quantity|||||||||||||||||||||||||||||||||||||||||||||||BatchNumber1|ExternalId1||P
ackId|2015-11-
05|DeliveryNumber1|Depth1|Width1|Height1|Shape1|IsInFridge1|||||SubItemQua
ntity1|||||||StockLocation1|MachineLocation1|||OutputDestination1|OutputPoint1|L
abelStatus1|BoxNumber1||

Sample TaskCancelRequest message

MSH|^~\&|||||20130617||QRY^Q02|3232|P|2.3|||NE|NE|||||TaskCancelRequest|100
QRD|20130617|TaskCancelRequest||||||||||9922|Output|

Sample TaskCancelResponse message

MSH|^~\&| | | | |20130618111330||QRY^Q03|3232|P|2.3|||NE|NE||||

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 43

Appendix A—Sample messages

|TaskCancelResponse|100
QRD||TaskCancelResponse||||||||||2299|Output|Cancelled

Sample ArticleMasterSetRequest
message
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||MF
N|1003|P|2.3|||NE|NE|||||ArticleMasterSetRequest|100|999|
ZPM||||||0004-56-034-G00007T|ACCU CHEK
AVIVA|||||||||||||||||||||||||||LOE|||||||||||||||||||||||1X2.5 ML|||||||||||||||||2||False|||
ZPM||||||56473627|PREDNISOLO|||||||||||||||||||||||||||TAB|||||||||||||||||||||||20|||||||||||||||||0|||||

Sample ArticleMasterSetResponse
message
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y
^Q02|1003|P|2.3|||NE|NE|||||ArticleMasterSetResponse|999|100
QRD|20140428170815|ArticleMasterSetResponse||PYX|||||||||||||||||Accepted|Master
Articles accepted.|

Sample StockDeliverySetRequest
message
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||MF
N|1003|P|2.3|||NE|NE|||||StockDeliverySetRequest|100|999|
ZPM||||||0004-56-034-G00007T~56473627|ACCU CHEK
AVIVA~PREDNISOLO||||15~5|||||||||||||||||||||||LOE~TAB|||||||||||||||||||||||1X2.5
ML~20|||||||||||||||||0|1234|False~True|~BAT918271|~XT11725|~2014-04-05|

Sample StockDeliverySetResponse
message
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20140425102910||QR
Y
^Q02|11|P|2.3|||NE|NE|||||StockDeliverySetResponse|999|100
QRD|20140428170925|StockDeliverySetResponse||PYX|||||||||||||||||Accepted|Maste
r Articles accepted.|

44 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Sample ConfigurationGetRequest
message
MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.2|||NE|NE|||||ConfigurationGetReque
st|100|999

Sample ConfigurationGetResponse
message
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q02|3335|P|2.3|||NE|NE|||||ConfigurationGetResponse|999|100
QRD|20160106162035|ConfigurationGetResponse||PYX||||||||||||||||||<![CDATA[
<ConfigurationValue Name="abc" Value="dddd"/> <ConfigurationValue
Name="ccc" Value="ffff"/> <ConfigurationValue Name="ddd" Value="dfdf"/>
]]>|||||||

Sample StockLocationInfoRequest
message
MSH|^~\&|||||20130617||QRY^Q02|1002|P|2.2|||NE|NE|||||StockLocationInfoRequ
est|100|999

Sample StockLocationInfoResponse
message
1 StockLocation
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|3335|P|2.3|||NE|NE|||||StockLocationInfoResponse|999|100
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ID1|Description1
2 StockLocations
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|3335|P|2.3|||NE|NE|||||StockLocationInfoResponse|999|100
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||463563|Narcotics
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||674638|SmartDrugs
3 StockLocations
MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||ZP
M|3335|P|2.3|||NE|NE|||||StockLocationInfoResponse|999|100
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ID1|Description1
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ID2|Description2
ZPM||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||ID3|Description3

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 45

Appendix A—Sample messages

Sample InitiateInputRequest message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||QR
Y^Q02|ID|P|2.3|||NE|NE|||||InitiateInputRequest|Source|Destination|
QRD||InitiateInputRequest||||||||Index|ScanCode||||SetPickingIndicator|IsNewDeliv
ery||DeliveryNumber|ExpiryDate|SubItemQuantity|||BatchNumber|StockLocation
Id|MachineLocation|ExternalId||||||||InputSource|InputPoint|Depth|Width|Height|S
hape|

Sample InitiateInputResponse message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||DFT
|ID|P|2.3|||NE|NE|||||InitiateInputResponse|Source|Destination
QRD||InitiateInputResponse|||Status|||||Index1~Index2|ScanCode1~ScanCode2||||S
etPickingIndicator|IsNewDelivery||||SubItemQuantity1~SubItemQuantity2|||Batch
Number1~BatchNumber2|StockLocation1~StockLocation2|MachineLocation1~
MachineLocation2|ExternalId1~ExternalId2||||||||InputSource|InputPoint|Depth1~
Depth2|Width1~Width2|Height1~Height2|Shape1~Shape2
ZFX||ArticleId1^Name1^IsNewDelivery||||||||DosageForm1^PackagingUnit1|Inde
x1^^BatchNumber1^ExternalId1^ExpiryDate1^^DeliveryNumber1^Depth1^Wid
th1^Height1^Shape1~Index2^^BatchNumber2^ExternalId2^ExpiryDate2^^Deliv
eryNumber2^Depth2^Width2^Height2^Shape2|^^SubItemQuantity1^MaxSubIte
mQuantity^StockLocation1^MachineLocation1^^^^^^^ScanCode1~^^SubItemQ
uantity2^^StockLocation2^MachineLocation2^^^^^^^ScanCode2

Sample InitiateInputMessage message

MSH|^~\&|PYXIS|PYXIS|HOSTAPPL|HOSTFACILITY|20130416164400||DFT
|1003|P|2.3|||NE|NE|||||InitiateInputMessage|999|100
QRD||InitiateInputMessage|||Status|||||Index1~Index2||||||||||SubItemQuantity1~Sub
ItemQuantity2|||BatchNumber1~BatchNumber2|StockLocation1~StockLocation2
|MachineLocation1~MachineLocation2|ExternalId1~ExternalId2||||||||InputSource|
InputPoint|Depth1~Depth2|Width1~Width2|Height1~Height2|Shape1~Shape2
ZFX||ArticleId1^Name1||||||||DosageForm1^PackagingUnit1|Index1^PackId1^Bat
chNumber1^ExternalId1^ExpiryDate1^^DeliveryNumber1^Depth1^Width1^Hei
ght1^Shape1~Index2^PackId2^BatchNumber2^ExternalId2^ExpiryDate2^^Deliv
eryNumber2^Depth2^Width2^Height2^Shape2|^^SubItemQuantity1^MaxSubIte
mQuantity^StockLocation1^MachineLocation1^^^^State1~^^SubItemQuantity2
^^StockLocation2^MachineLocation2^^^^State2

46 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Appendix B
Mosaic message
configurations

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 47

Appendix B—Mosaic message configurations

Mosaic StockInputOrchestration &

InitiateStockInputOrchestration
Configurations
The Configuration Checking and Stock Input message flows are mutually
exclusive of the Stock Delivery message flow. The Mosaic configuration must be
changed to switch from one type of message processing to the other.
The following table lists messages and the settings under which they are valid and
invalid:

StockInputOrche StockInputOrch StockInputOrche StockInputOrche

stration > OFF estration > ON stration > OFF stration > ON

StockInputProxy StockInputProxy StockInputProxy StockInputProxy

Orchestration > Orchestration > Orchestration > Orchestration >
ON OFF ON OFF

InitiateStockInput InitiateStockInp InitiateStockInpu InitiateStockInpu

Orchestration > utOrchestration tOrchestration > tOrchestration >
ON > ON OFF OFF

Hello workflow
request successful successful successful successful
response successful successful successful successful
InputMessage workflow
request manual input manual input manual input manual input
manual input to manual input to manual input to manual input to
response CCE CCE CCE CCE
message successful failed successful failed
asks for pack Article ScanCode Please position Article ScanCode
note dimensions invalid on ROWA pack invalid on ROWA
InitiateInputMessage
workflow
request successful successful successful successful
response successful successful failed failed
ConfigurationGetResponse
workflow
request successful successful successful successful
response successful successful failed failed

48 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide

 Mosaic StockInputOrchestration & InitiateStockInputOrchestration Configurations

StockInputOrche StockInputOrch StockInputOrche StockInputOrche

stration > OFF estration > ON stration > OFF stration > ON

StockInputProxy StockInputProxy StockInputProxy StockInputProxy

Orchestration > Orchestration > Orchestration > Orchestration >
ON OFF ON OFF

InitiateStockInput InitiateStockInp InitiateStockInpu InitiateStockInpu

Orchestration > utOrchestration tOrchestration > tOrchestration >
ON > ON OFF OFF

Complete Complete
message message
note NA NA conversion conversion
StockDeliverySetRequest
workflow
request successful successful successful successful
response failed successful failed successful
Complete
Complete message message
note conversion NA conversion NA
ArticleMasterSetRequest
workflow
request successful successful successful successful
response successful successful successful successful
OutputRequest workflow
request successful successful successful successful
response successful successful successful successful
message successful successful successful successful
StatusRequest workflow
request successful successful successful successful
response successful successful successful successful
StockLocationInfoRequest
workflow
request successful successful successful successful
response successful successful successful successful
StockInfoRequest workflow
request successful successful successful successful
response successful successful successful successful

CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide 49

Appendix B—Mosaic message configurations

StockInputOrche StockInputOrch StockInputOrche StockInputOrche

stration > OFF estration > ON stration > OFF stration > ON

StockInputProxy StockInputProxy StockInputProxy StockInputProxy

Orchestration > Orchestration > Orchestration > Orchestration >
ON OFF ON OFF

InitiateStockInput InitiateStockInp InitiateStockInpu InitiateStockInpu

Orchestration > utOrchestration tOrchestration > tOrchestration >
ON > ON OFF OFF

TaskCancelRequest
workflow
request successful successful successful successful
response successful successful successful successful
TaskInfoRequest workflow
request successful successful successful successful
response successful successful successful successful

50 CareFusion™ Coordination Engine ROWA™ Adapter v1.4 Specifications Guide