The connector makes use of IBM's WebSphere MQ implementation of
the Java Message Service (JMS). The JMS is an open-standard API for
accessing enterprise-messaging systems. It is designed to allow
business applications to asynchronously send and receive business
data and events.
Figure 2 illustrates a
message request communication.
- The connector framework receives a business object representing
an healthcare message from an integration broker.
- The connector passes the business object to the data
handler.
- The data handler converts the healthcare business object into
an HL7/NCPDP-compliant message.
- The connector dispatches the HL7/NCPDP-compliant message to the
WebSphere MQ output queue.
- The JMS layer makes the appropriate calls to open a queue
session and routes the message to the MQ Series input queue.
Figure 2. Application-connector
communication method: Message request

Figure 2 illustrates the
message return communication.
- The polling method retrieves the next applicable message from
the WebSphere MQ input queue.
- The data handler converts the message into a business
object.
- The HL7 data handler receives the business object and sets the
verb in it to the default verb specified in the data
handler-specific meta-object.
- The connector then determines whether the business object is
subscribed to by the integration broker. If so, the connector
framework delivers the business object to the integration broker,
and the message is removed from the in-progress queue.
