Application-connector communication method

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.

Message request

Figure 2 illustrates a message request communication.

  1. The connector framework receives a business object representing an healthcare message from an integration broker.
  2. The connector passes the business object to the data handler.
  3. The data handler converts the healthcare business object into an HL7/NCPDP-compliant message.
  4. The connector dispatches the HL7/NCPDP-compliant message to the WebSphere MQ output queue.
  5. 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


Event delivery

Figure 2 illustrates the message return communication.

  1. The polling method retrieves the next applicable message from the WebSphere MQ input queue.
  2. The data handler converts the message into a business object.
  3. 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.
  4. 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.

Copyright IBM Corp. 1997, 2003