Study Version Template (SVT) Integration

This incremental integration configured at the study version level runs on a schedule to identify study versions created and updated (for a configured study mode) since the last run in Oracle Clinical One Platform and creates corresponding templates in CTMS.

This integration runs first if all four (4) CTMS integrations have been implemented.

Table 2-4 Details

Type of integration	Data flow	Frequency
Multiple file	One-way, from Oracle Clinical One Platform to CTMS	Scheduled

Overview

• The integration retrieves study design metadata and visit schedule information corresponding to the study version, then sends them to CTMS.
• Each study version is imported as a Subject Visit Template in CTMS and includes visits, forms, items of type date/time and Boolean (Yes/No questions), and the visit schedule for each study version.
• Data is integrated in the order the requests are received.
• Data received for multiple study versions is processed in parallel.
• The integration schedule for all visits is calculated starting from the first visit.

Pre-requisites: the following should be confirmed before running the integration

• The protocol should exist in CTMS, and the name should match the study title in Oracle Clinical One Platform.

Integration user and roles

An integration user needs to be created and assigned to a custom role that includes the following permission.

• View Design

For more information about permissions, see Descriptions of permissions in Clinical One.

Exceptions

• Advanced study versioning is not supported.

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.