Site Integration
This cumulative integration runs on a schedule to retrieve a list of sites from CTMS based on their status. The integration then creates the sites in Oracle Clinical One Platform if they do not already exist or applies updates if they do.
This integration runs second if all four (4) CTMS integrations have been implemented.
Table 2-5 Details
Type of integration | Data flow | Frequency |
---|---|---|
Multiple file | One-way, from CTMS to Oracle Clinical One Platform. | Scheduled |
Overview
- Each time the integration runs, a job is created for each site retrieved from CTMS.
- Sites created in CTMS have a different status once created in Oracle Clinical One Platform
Table 2-6 Site statuses
Status in CTMS Status in Oracle Clinical One Platform Initiated New Enrolling Active Terminated Retired - The Upsert functionality is enabled by default, and uses the unique site IDs in Oracle Clinical One Platform to determine what action to take.
- If the site does not exist, it is created.
- If the site does exist, then information for the site is updated.
- If the Site ID itself is updated, a new site is created in Oracle Clinical One Platform because it is a new site from the perspective of the integration.
CTMS site details
Table 2-7 CTMS site details
CTMS Field | Details |
---|---|
Time Zone | Site Time Zone is specified in the Site Management/Target Site/More Info/Site
info section in CTMS.
Note: If the source CTMS system did not define a time zone for a site, the Oracle Clinical One Platform defaults the setting to UTC. |
Primary Site Address |
Primary Site Address is specified in the Site Management/Accounts tab in CTMS. The integration can be configured to define which Address type in CTMS is to be used as the Site address in Oracle Clinical One Platform. |
Shipping Site Address |
Shipping Site Address is specified in the Site Management/Addresses tab in CTMS. Shipping site address is not required when executing the Site integration. If the Shipping Site Address is not defined, the Site primary address is mapped to Oracle Clinical One Platform shipping address. |
Pre-requisites: the following should be confirmed before running the integration
- Country names in CTMS match the template codelist values. If they do not, the job fails with an error: Country not found: <country>.
Integration user and roles
- Answer Queries
- Create and Manage Sites
- View Sites
For more information about permissions, see Descriptions of permissions in Clinical One
Exceptions
- Site status is not updated in Oracle Clinical One Platform if it is updated in CTMS.
Configuration
Working with the customer, the Oracle integration team creates a Configuration Setup Details Document (CSDD), which details the configuration specifications defined for integrations between Oracle Clinical One Platform and CTMS.
Parent topic: Oracle's Siebel Clinical Trial Management System (CTMS)