HC_ORP_O10 Collaboration Template

The HC_ORP_O10 collaboration template processes MTORP business objects. The HC_ORP_O10 collaboration template uses data contained in the MTORP business object to build and populate an MQWF_ORP_O10 workflow response business object. The collaboration is generally used as one of a pair of closely coupled request/response collaborations. Data stored by HC_OMP_O09 (the request) is used by the HC_ORP_O10 collaboration (the response). The OMP/ORP request/response message pair is used to process pharmacy orders.

IBM WebSphere MQ Workflow context data is stored in the PROCESSCONTEXT table.

This collaboration object performs the following tasks:

HC_ORP_O10 uses the generic MTORP business object to represent an HL7 Pharmacy Order response message.

Collaboration object setup

This section includes information on port bindings and required steps for setting up collaboration objects based on HC_ORP_O10. For information on standard features, ports, and configuration properties for collaboration templates, and for general information on creating collaboration objects, refer to the documents listed in Required Documents for Creating Collaboration Objects.

Port information

The following diagram illustrates HC_ORP_O10's ports:

Note: To keep the collaboration object from using a port, bind that port to the Port connector. Doing so indicates that the port is unused without causing the collaboration object to provide additional functionality.

DestinationAppRetreive
Business object Bound to Function Verbs used
MTORP Source application's connector or calling collaboration object Sends a reference-valued business object to retrieve the full-valued business object. The result determines which verb to use. Retrieve
From
Business object Bound to Function Verbs used
MTORP Source application's connector or calling collaboration object Receives the triggering business object Create
To
Business object Bound to Function Verbs used
MQWF_ORP_O10 Destination application's connector Sends the WebSphere MQ Workflow response business object out of the collaboration object. Create

Setting up HC_ORP_O10 as a stand-alone object

To set up HC_ORP_O10 as a stand-alone collaboration object, complete the following steps:

  1. Create the HC_ORP_O10 collaboration object.
  2. Bind all ports as described in Port information.
  3. Configure HC_ORP_O10 as described in Configuration properties.

Collaboration template processes

This section illustrates the business processing logic for this collaboration template:

Overall process logic

This section illustrates this collaboration template's process logic for the supported verb, Create.

Create

The following diagrams show the process logic for this collaboration template's Create verb.

Diagram showing this collaboration's SyncLogic process

     SYNC_LOGIC diagram

Diagram showing this collaboration's Process HL7 message

     Process HL7 Message diagram

Diagram showing this collaboration's Retrieve Workflow Process Context flow

     Retrieve Workflow Process Context diagram

Diagram showing this collaboration's Update Process Context Table flow

     Update Process Context Table diagram

Diagram showing this collaboration's Create MQ Workflow Response process

Create WorkFlow Response diagram

Standard process logic

This collaboration template uses the following standard business processes:

Configuration properties

This section describes the standard and specific configuration properties for this collaboration:

Standard properties

This collaboration template uses the following standard configuration properties:

Collaboration-specific properties

This collaboration template has the following configuration properties specific to it:

DB_CONN_POOL_NAME

This property specifies the database connection pool.

DB_CONN_POOL_NAME configuration property
Default value Usage
HEALTHCARE_DB Defines the database connection pool used by the collaboration.

CLEANCONTEXTTABLE

This property specifies whether the collaboration object should perform a soft deletion or hard deletion on the process context entry on the PROCESSCONTEXT table. A hard deletion removes the entry. A soft deletion enters a timestamp and status code that allows database maintenance of used entries as a batch or off-hours operation.

Possible values Usage
true Causes this collaboration object to delete the row
false (default value) Causes this collaboration object to update the row as a soft deletion

Related reference

Copyright IBM Corp. 2002, 2003