Setting Up Siebel Clinical

This chapter covers setting up Siebel Clinical. It includes the following topics:

About Setting Up Siebel Clinical

This chapter lists the administrative tasks that are specific to Siebel Clinical. Use this chapter in combination with the main guide for performing administrative tasks, Siebel Applications Administration Guide.

Siebel Applications Administration Guide covers the setup tasks that are common to all Siebel Business Applications, such as using license keys, defining employees, and defining your company’s structure. It also provides the information that you need to implement, configure, and monitor the Sales, Service, and Marketing products and to perform Data Administration and Document Administration tasks.

Some tasks listed in this chapter might replace tasks in Siebel Applications Administration Guide. Other tasks might be additional tasks. Make sure you review Administrative Setup Tasks for Siebel Clinical before following the procedures in Siebel Applications Administration Guide.

This guide assumes that you already installed Siebel Clinical or completed an upgrade from another Siebel Business Application. If you have not, then refer to the Installation/Upgrade section of the Siebel Bookshelf, and click the links to the guides that are relevant to your company’s implementation.

The Siebel database server installation script creates a Siebel administrator account that you can to perform the tasks described in this guide. For information about this process, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.

Note: Do not perform system administration functions on your local database, as these functions can cause data conflicts, an overly large local database, or a large number of additional transactions to route.

Configuring Properties for Siebel Clinical in Siebel Tools

User properties are object definitions that are added to an applet, business component, control, field, or list column to enable and configure specialized behavior. User properties drive some Siebel Clinical features. You can customize these features through their respective user properties. With user properties, you can control behavior in the user interface, change default settings or leave them as they are, and enable or disable features. For information about enabling and configuring the Siebel Tools object definitions required for Siebel Clinical, see Developer’s Reference for Siebel Clinical.

Enabling or Disabling Siebel Open UI for Siebel Clinical

To enable or disable Siebel Open UI for Siebel Clinical, you must configure the EnableOpenUI parameter for the eClinicalObjMgr_enu Object Manager. Siebel Open UI is disabled by default. For information about configuring the Object Manager to enable Siebel Open UI, see the Siebel Installation Guide for the operating system you are using.

Enabling Siebel Server Component Groups for Siebel Clinical

This system administration task describes how to activate the component groups that are required for Siebel Clinical.

To enable Siebel Server component groups for Siebel Clinical

Navigate to the Administration - Server Configuration screen, then the Component Groups view.
Complete the following steps to set the component groups:
1. Query for the Workflow Management Component Group.
2. On the Component Groups applet, click Enable.
3. Query for the EAI Component Group.
4. On the Component Groups applet, click Enable.
Navigate to the Administration – Server Management screen, then the Servers and Component Groups view.
Verify that the State value for the Workflow Management and EAI Component Groups is set to Online.
Navigate to Administration – Server Configuration screen, then the Enterprises and Synchronize view.
Click Synchronize.
Restart the Siebel Server.

Activating Workflow Policies for Siebel Clinical

This system administration task describes how to activate the workflows and workflow policies required for Siebel Clinical. Workflows in Siebel Clinical shows a list of workflows for Siebel Clinical.

To activate the workflow policies for Siebel Clinical

Navigate to the Administration - Business Process screen, then the Workflow Deployment view, and perform the following steps:
1. Query for all the workflows using the following criteria, and activate the workflows:
  - *Clinical*
  - SWI - Protocol*
2. Verify that each activated workflow is added to the Active Workflow Processes list view at the end of the screen.
Navigate to the Administration - Runtime Events screen, click Menu (the cogwheel icon), and select Reload Runtime Events.
Navigate to the Administration - Business Process screen, then the Workflow Policies view, and perform the following steps:
1. Query workflow policies for LS Clinical*
2. Set the activation date to one day before today’s date for all policies.
3. Check that expiration date is NULL for all policies.
Navigate to the Administration - Server Management screen, then the Jobs view, and perform the following steps to generate triggers for the workflow policies returned from your query:
1. Define a job for Generate Triggers component with the following parameters:
  - EXEC: True
  - Mode: ALL
  - Privileged User: <%SADMIN%>
  - Privileged User Password: <%PASSWORD%>
2. Start the job and query until the status is Success.
From the srvrmgr command utility, perform the following steps:
1. Create a component definition for the LS Clinical Rollup policy group as follows:
  - Component definition: LSCLIN
  - Component type: WorkMon
  - Component group: Workflow
  - Run mode: Background
  - Full name: LS Clinical
  - Description: Monitors LS Clinical Workflow Manager events
  - Parameter DfltTasks=1, GroupName=LS Clinical Rollup, SleepTime=30
  Note: When working with component definition commands, launch and run the srvrmgr program for the enterprise; that is, do not start srvrmgr with the back slash s ( /s) (or -s for UNIX).
  The component alias must be unique across the enterprise, and must not be more than 30 characters in length. Also be careful not to use keywords in the component description, such as for or component, unless the words are enclosed in quotes.
  The component definition command starts a task to perform actions on LS Clinical Rollup group policy as a result of updates on the corresponding tables that the database triggers monitor.
  The SleepTime parameter represents the time in seconds for processing requests. The default value is 20 seconds. Setting the SleepTime parameter to a low value or zero can have serious negative performance consequences.
2. Enter the following command to enable the LS Clinical Rollup component:
  enable component definition LSCLIN
Navigate to the Administration - Server Configuration screen, then the Synchronize view, and perform the following steps:
1. Click Synchronize.
2. Verify that the Workflow Monitor Agent is running.
  If it is not activated, then start the Workflow Monitor Agent task again.
Navigate to the Administration - Server Management screen, then the Tasks view, and perform the following steps to set the action interval for the Workflow Monitor Agent task:
1. Navigate to the Parameters view.
2. In the Tasks list, query for the Workflow Monitor Agent in the Component field.
3. In the Task Parameters list, query for Action Interval in the Parameter field and set the value to 10.

Configuring Web Services for Siebel Clinical

This task describes how to configure Web services for Siebel Clinical. 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.

To configure Web services for Siebel Clinical

Navigate to the Administration - Web Services screen, then the Inbound Web Services view.
Query for the ClinicalSubject Inbound Web service.
On the Service Ports applet, update the Address variable to point to your Web server, and configure the Language variable.
Query for the SWILSClinicalQueryProtocolSite_SiteVisits Web service.
On the Service Ports applet, update the Address variable to point to your Web server, and configure the Language variable.
Query for the SWILSClinicalCreateSiteVisitGeoLocation Web service.
On the Service Ports applet, update the Address variable to point to your Web server, and configure the Language variable.
Click Clear Cache on the Inbound Web Services applet.

Administrative Setup Tasks for Siebel Clinical

The following information lists the administrative setup procedures that are specific to Siebel Clinical and procedures that might differ from the procedures of the other Siebel Business Applications. The table also refers to documentation containing information about each task.

When setting up Siebel Clinical, use the table in combination with the main resource, Siebel Applications Administration Guide.

Table Tasks for Siebel Clinical Administration

Administrative Task	Description	For More Information
Managing accounts contacts in Siebel Life Sciences	Activating workflows for accounts contacts Enabling server components for accounts contacts Generating column maps for accounts contacts list Creating product data to appear in accounts contacts list	Siebel Life Sciences Guide
Creating a clinical program	Creating protocols Revising protocols (Optional) Setting up regions Defining a subject visit template	Setting Up Clinical Trials Administering Clinical Subjects and Clinical Visits Managing Sites and Contacts for Clinical Trials
Managing sites	Creating protocol site templates Creating assessment templates for contacts and accounts Maintaining contact and account information Setting up contracts for sites	Managing Sites and Contacts for Clinical Trials
Setting up clinical payments	Setting up standard payment amounts in subject visit templates Adjusting payment amounts and generating payments for sites	Setting Up and Making Clinical Payments
Creating trip report templates	Creating trip report templates Approving trip report templates	Administering and Using Clinical Trip Reports
Creating activity templates for projects	Creating activity templates for projects	Managing Clinical Projects
Importing data	Importing data with Siebel Enterprise Integration Manager Importing, extracting, and routing syndicated data Charting denormalized syndicated data	Siebel Life Sciences Guide
Configuring Siebel Clinical	Configuring user properties for business components Configuring user properties for business services Configuring applet properties Configuring field properties Configuring workflows Customizing Web services	Developer’s Reference for Siebel Clinical

About the My Team’s Filter

The visibility filter appears on many screens. It provides a list of filters, such as My Contacts, My Team’s Contacts, and All Contacts. These filters determine the records that appear in the view.

The behavior of the My Team’s filter varies from screen to screen. In some screens, this filter displays those records where the primary member of the team reports to the user. In other screens, this filter displays records where any of the team members report to the user.

The Manager List Mode user property in the business component determines this behavior. If the Manager List Mode user property is active and set to Team, then the My Team’s filter displays all records where the user’s subordinate is on the team but is not necessarily the primary member.

The following information lists the default setting of the Manager List Mode user property for some Siebel Clinical screens and business components.

Table The Default Setting for the Manager List Mode User Property

Screen	Business Component	Manager List Mode
Accounts	Accounts	Inactive
Contacts	Contact	Inactive
Protocols	Clinical Protocol	Active
Site Management	Clinical Protocol Site	Active

Using Siebel Assignment Manager in Siebel Clinical

Siebel Assignment Manager allows the Siebel administrator to automatically assign tasks to specific people. For this assignment, however, the Siebel administrator must first define assignment rules for each task. For more information about using and implementing Siebel Assignment Manager, see Siebel Assignment Manager Administration Guide. For additional information about creating territories and running territory realignments, see Siebel Territory Management Guide.

This topic provides Siebel Assignment Manager information that is specific to Siebel Clinical.

Predefined Assignment Objects

Some of the predefined assignment objects and underlying criteria described in Siebel Assignment Manager Administration Guide are modified in Siebel Life Sciences to support pharmaceutical business processes. The following table describes the assignment objects that are changed in Siebel Life Sciences.

Note: Assignment Item Type Industry Name is not supported. This assignment rule is defined for Siebel Business Applications and currently conflicts with Siebel Life Sciences assignment rules. Siebel Life Sciences uses the assignment item type SIC (Standard Industrial Classification) Code.

Table Assignment Object Changes in Siebel Life Sciences

Assignment Object	Modifications
Account	The assignment criteria SIC Code is renamed Account Class of Trade. Its assignment criteria include: Account City State Country Account Brick The source table for Account Brick is changed to S_CON_ADDR, and the source column for Account Brick is changed to BRICK_ID.
Contact	This assignment object is created specifically for Siebel Life Sciences and is not described in Siebel Assignment Manager Administration Guide. Its assignment criteria include: Contact Contact Medical Specialty Code Contact Wildcard Contact City Contact State Contact Country Contact Zip Code Contact City State Country Contact Brick Medical Specialty Organization Position

Assignment Object

Modifications

Account

The assignment criteria SIC Code is renamed Account Class of Trade.

Its assignment criteria include:

Account City State Country
Account Brick

The source table for Account Brick is changed to S_CON_ADDR, and the source column for Account Brick is changed to BRICK_ID.

Contact

This assignment object is created specifically for Siebel Life Sciences and is not described in Siebel Assignment Manager Administration Guide.

Its assignment criteria include:

Contact
Contact Medical Specialty Code
Contact Wildcard
Contact City
Contact State
Contact Country
Contact Zip Code
Contact City State Country
Contact Brick
Medical Specialty
Organization
Position

Contact Assignments in Siebel Clinical

In most Siebel Business Applications, contact assignment is based on the primary address. This process is different for Siebel Life Sciences. A contact in Siebel Life Sciences can have multiple addresses, and each representative on the contact’s sales team can indicate a different primary address for the same contact. For this reason, do not base the contact assignment on the primary address.

For example, Representative A might indicate a hospital address as the primary address, while Representative B might indicate a private-office address as the primary address. In the All Contacts and My Team’s Contacts views, the primary address that appears is the address that the primary team member assigns. For more information, see Predefined Assignment Objects.

Contact Denormalization Mode in Siebel Life Sciences

Contact Denormalization mode in Siebel Life Sciences differs from the description of the mode in Siebel Assignment Manager Administration Guide in the following ways:

This mode denormalizes positions from the account team table to the contact team table for all contacts directly affiliated with an account. Users can specify a direct affiliation between a contact and an account by selecting:
- The Direct field in the Account Affiliations view of the Contacts screen.
- The Direct field in the Contact Affiliations view of the Accounts screen.
For more information, see Siebel Life Sciences Guide.
This mode does not denormalize positions from the opportunity team table to the contact team table.
You must run this mode after separately running batch mode jobs for contacts and accounts. Run the batch mode jobs in the following order:
1. Contacts
2. Accounts
3. Contact Denormalization

Contact Denormalization in Siebel Life Sciences has the following additional important rules, requirements, and exceptions:

Running Contact Denormalization mode in Dynamic mode. To activate the Contact Denormalization Policy, set the expiration date to a future date or leave it blank. Then generate the database triggers by running Generate Triggers.
Running Contact Denormalization mode in Batch mode. Remember to specify the following parameters:
Object Name=Contact Denormalization
Assignment Mode=Denorm
Contact Denormalization mode does not evaluate rules. Therefore, you do not have to create a rule-based object for Contact Denormalization to run Assignment Manager in this mode. Also, because it does not evaluate rules, Contact Denormalization mode does not set the primary team position.
Contact Denormalization assigns contacts to employees who are on the account team to which the contacts are directly affiliated. To reduce the number of contact-to-position relationship (S_POSTN_CON) rows routed to the manager's local database, the value of the ASGN_DNRM_FLG field is set to "N". With this default setting, the contacts that the Contact Denormalization process assigns to team members are not visible to managers on their local databases. However, if you want managers to see all contacts that are assigned to their team members, regardless of the assignment method, then set ASGN_DNRM_ "Y".

Setting Up Mobile Web Clients for Position Rollup

In Siebel Clinical, a CRA (clinical research associate) can create sites and assign employees to positions at the site level. When the CRA clicks the Position Rollup button, these positions become visible at the region and protocol levels. Typically, the CRA works in a disconnected mode, on a laptop computer.

The administrator must set up each mobile Web client to allow position rollups. The setup requires the following steps in Siebel Clinical:

The administrator exports workflow processes and data maps from the server database to XML files.
The administrator connects to a local client, imports the XML files to the client database and activates the workflow processes on the local client.

Note: Users of the local client must have Workflow Process Definition, EAI DATA Map View, and EAI Data Map Editor in their user responsibilities to accept imported workflow processes and data maps.

Exporting Workflow Processes to the Local Client

Complete the procedure in this topic to export the workflow processes to the local client.

To export the workflow processes to the local client

Export the Clinical Assign Position From Region and Clinical Assign Position From Site workflows to XML files.
Import the two XML files to the local client, and activate the workflows.
For information about exporting and importing workflow processes, see Siebel Business Process Framework: Workflow Guide.

Exporting DTE Data Maps From the Server Database to an XML File

Complete the procedure in this topic to export DTE data maps from the server database to an XML file.

To export DTE data maps from the server database to an XML file

In Siebel Clinical, connect to the server database.
Navigate to the Administration - Integration screen, then the Data Maps view.
In the Integration Object Map list, query for Clinical*.
The query returns the following records: Clinical Region Position to Protocol Position Map, Clinical Site Position to Account Position Map, Clinical Site Position to Protocol Position Map, and Clinical Site Position to Region Position Map.
Click Menu (the cogwheel icon), and select Export Data Map.
In the dialog box, check Export All Rows in Current Query and click Export.
In the dialog box, select Save to Disk, select a location, and save the data maps as PositionRollupDataMap.xml.

Importing DTE Data Maps to a Local Client From an XML File

Complete the procedure in this topic to import DTE data maps to a local client from an XML file.

To import DTE data maps to a local client from an XML file

In Siebel Clinical, connect to the local client.
Navigate to the Administration - Integration screen, then the Data Maps view.
In the Integration Object Map list, click Menu (the cogwheel icon), and select Import Data Map.
In the dialog box, select Browse and find PositionRollupDataMap.xml.
For information about creating this file, see Exporting DTE Data Maps From the Server Database to an XML File.
In the Integration Object Map list, query for Clinical*Position*.