Process of Setting Up Clinical Data Capture and Query Management System Integration

To set up clinical data capture and query management system integration for Siebel Clinical, perform the following tasks:

• "Activating Workflows for Clinical Data Capture and Query Management System Integration"

• "Setting Up LS Clinical Integration Workflow Monitor Agent for Clinical Data Capture and Query Management System Integration"

• "Configuring Web Services for Clinical Data Capture and Query Management System Integration"

Activating Workflows for Clinical Data Capture and Query Management System Integration

This task describes how to activate the workflows that are required for clinical data capture and query management system integration. You can use Siebel Business Process Designer to modify the workflows to suit your own business model. For more information, see Siebel Business Process Framework: Workflow Guide.

This task is a step in "Process of Setting Up Clinical Data Capture and Query Management System Integration".

To activate workflows for clinical data capture and query management system integration  

1. Navigate to the Administration - Business Process screen, then the Workflow Deployment view.

2. Query for and activate each of the following workflows:

   • SWI LS Clinical Subject Inbound - Subject

   • SWI LS Clinical Subject Inbound - Activity

   • SWI - Protocol Number Lookup

   • LS Clinical - DeleteNonAppVisits Process

3. Verify that each activated workflow is added to the Active Workflow Processes view at the bottom of the screen.

Setting Up LS Clinical Integration Workflow Monitor Agent for Clinical Data Capture and Query Management System Integration

This topic describes how to set up the LS Clinical Integration workflow monitor agent for clinical data capture and query management system integration.

This task is a step in "Process of Setting Up Clinical Data Capture and Query Management System Integration".

To set up the LS Clinical Integration workflow monitor agent for clinical data capture and query management system integration  

1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

2. Navigate to the Component Definitions view, and query for Workflow* in the Component field.

3. Make a copy of the Workflow Monitor Agent component definition, and complete the following steps:

   1. Change the Component field to LS Clinical Integration.

   2. Change the Alias field to LSClinicalInteg.

   3. Set the Component Group field to Workflow Management.

4. In the Component Parameters list, complete the following steps:

   1. Change the value of the Group Name parameter to LS Clinical Site Integration.

   2. Change the value of the Action Interval parameter to 5.

   3. Click Advanced, change the value of the Sleep Time parameter to 15, and change the value of the Default Tasks parameter to 1.

5. Click Activate to change the status of the new component to Active.

6. Synchronize the components.

7. Restart the Siebel server.

Configuring Web Services for Clinical Data Capture and Query Management System Integration

This task describes how to configure the Web services that are required for clinical data capture and query management system integration. For more information about configuring Web services, see Integration Platform Technologies: Siebel Enterprise Application Integration.

Note: It is recommended that you use HTTPS authentication. For information about configuring Secure Sockets Layer (SSL) for HTTPS authentication, see Siebel Security Guide.

This task is a step in "Process of Setting Up Clinical Data Capture and Query Management System Integration".

To configure Web services for clinical data capture and query management system integration  

1. Navigate to the Administration - Web Services screen, then the Inbound Web Services view.

2. Query for each of the following Web services, and update the language and address variables:

   • ClinicalSubject Inbound Web service.

   • LS Clinical Protocol Site Interface Service

3. Click Clear Cache on the Inbound Web Services applet.