Master User List (MUL)—User Integration

This integration is responsible for creating users in Oracle Clinical One Platform and performs site and role association asynchronously.

Overview

The MUL User Integration retrieves files placed on the Oracle sFTP server, creates users in Oracle Clinical One Platform, and assigns them to their study, study roles, sites, and depots.

Configuration Service details

B92664: Oracle Life Sciences Clinical One Digital Gateway Configuration Service, up to 40 Data Points.

For more information, see Oracle Life Sciences Cloud Consulting Professional Services, Service Descriptions and Metrics.

Reach out to your Oracle point of contact if more information is needed.

Workflow

Below is the standard data flow for the MUL Site Tenant integration.
  1. The integration runs on a schedule and picks up files based on each file's timestamp.
  2. Each file generates an integration job in Oracle Clinical One Digital Gateway. Each job is responsible for creating users and assigning them to their study, study roles, sites, and depots in Oracle Clinical One Platform.
  3. Users are also created in Oracle Identity Cloud Service (IDCS) and in the Identity and Access Management Service (IAMS), where they are assigned to a study.
    If a user already exists, details like email address, first name, and last name can be updated, as long as their username (unique ID) remains unchanged. If the username of an existing user is changed, then a new user is created.

    Table 2-30 Transaction type details

    Transaction Type Action
    INSERT

    The user is created, and an activation email is sent to the address associated with them.

    Note: If a user already exists, the job updates their site and study role assignments if applicable.
    UPDATE

    Updates are applied to existing users.

    Note: If the user does not exist, they are created.
    DELETE

    The user is deactivated.

    Note: If a user does not exist, they are created in a deactivated state.

    If a deactivated user is included in a subsequent file with the UPDATE tag, the user details are updated, and the status of the user is changed to active.

Import validation checks

The integration performs validation checks to ensure users get created/updated as expected. The validation checks include:
  • Valid email address format

    Valid format: maximum_of_64_characters@domain.com with a total maximum email length not exceeding 256 characters

  • The site ID in the file corresponds to a site in Oracle Clinical One Platform.
  • The study role in the file corresponds to a study role in Oracle Clinical One Platform.

    Note:

    A record is not processed if the study role defined in the file does not exist in Oracle Clinical One Platform.
  • If a file contains duplicate columns, the integration uses the value from the first column of the same name.

Notifications

  • If any validation check fails, the associated job fails. This results in the sending of error notification emails to the configured email addresses.
  • If the Oracle Clinical One Digital Gateway job itself fails, not due to validation checks, notification emails are sent to users assigned to a study role that includes the Run the User Upload Error Report permission.

Parent topic: Study Administration