About the ClearTrial Clinical Trial Management System Connector

The ClearTrial Clinical Trial Management System Connector provides integration between ClearTrial Plan and ClearTrial Track, cloud-hosted Software as a Service (SaaS) applications, and Siebel Clinical. The connector extracts data from Siebel Clinical by invoking the ASI SOAP (Application Service Interface Simple Object Application Protocol) Web services. It then transfers the data into ClearTrial Track by invoking the ClearTrial Web services API hosted in the cloud at

https://cleartrial-api.oracleindustry.com/cleartrial-ws

Table A-1 describes the required applications for connector processing.

Table A-1 Required Applications for Connector Processing

Application	Description
ClearTrial Plan	A cloud-hosted SaaS application that you use to plan a clinical trial. In ClearTrial Plan, you can run different scenarios and arrive at a satisfactory budget and date milestones.
ClearTrial Track	A cloud-hosted SaaS application you use to enter the actual data from a clinical trial. In ClearTrial Track, you see how the clinical trial planned in ClearTrial Plan progresses during execution.
Clinical Trial Management System	An application that records the details of a clinical trial.
ClearTrial Clinical Trial Management System Connector	An application that provides an automated way of importing the actual data in Siebel Clinical into ClearTrial Track.

For more information about ClearTrial Plan and ClearTrial Track, access Oracle Health Sciences ClearTrial Cloud Service documentation at

http://docs.oracle.com/cd/E40601_02/index.htm

Supported Integration Points for the ClearTrial Clinical Trial Management System Connector

ClearTrial Track supports a large number of data points in the user interface. The connector supports a subset of data points or the actual data that can be automatically imported. Consequently, a large amount of actual data is included in the automatic import of the connector.

For ClearTrial Track, the week begins on a Monday for all integration points, such as sites approved, subjects enrolled, and CRF (case report form) pages collected.

For example, a site approved on Sunday, February 16, 2014 at 11:59 P.M. is counted against the week starting on Monday, February 10, 2014. Therefore, it is important to capture the accurate dates for the site initiated, subject enrolled, and source verified events in the user interface for Siebel Clinical.

Table A-2 describes the supported integration points for the ClearTrial Clinical Trial Management System Connector.

Table A-2 Supported Integration Points for the ClearTrial Clinical Trial Management System Connector

Integration Point	Description
Sites Approved	The number of sites that are approved (or initiated) and recorded in Siebel Clinical, rolled up by week, location, and region. Note: The connector ignores initiated sites without a corresponding date.
Subjects Enrolled	The number of subjects that are enrolled and recorded in Siebel Clinical, rolled up by week, location, and region. You must capture the accurate dates for the subject enrolled event in the Status field. For information about navigating to this field, see "Creating Records for Clinical Subjects".
CRF Pages Collected	The number of CRF pages that are source verified in Siebel Clinical, rolled up by week, location, and region. You must capture the accurate dates for the Source Verified event in the Source Verified Date field. For information about navigating to this field, see "Tracking Case Report Forms".

About Logging for the ClearTrial Clinical Trial Management System Connector

You can configure logging for the ClearTrial Clinical Trial Management System Connector, if required, in the log4j.properties file in the User Home/ClearTrialCtmsData directory. When the connector executes, it creates logs at the command prompt or shell window in which it executes. You can view these logs in the connector.log file in the User Home/ClearTrialCtmsData/logs directory. The logs are automatically rotated according to their size.