What data is migrated across data centers?

Oracle InForm CRF Submit includes the following features and a command line utility to support migration across data centers (from GBUCS 1.0 to GBUCS 3.0) without impacting regulatory data.

• Requests are migrated.
  • Request Settings are available for migrated requests.
• Migrated requests:
  • Are displayed as part of the Completed Requests, and their status shows as Migrated. Users cannot click on the Migrated request name, and therefore they cannot navigate to the Request Details page.
  • Always stay in the Completed Requests section regardless of their status, and do not auto-purge.
  • Cannot be downloaded.
• There is a new Migrated status for Requests and Audit Reports. The Request name must be unique per study.

Command line utility

Oracle InForm CRF Submit supports a command line utility for migrating Regulatory and Administration data for a study from the GBUCS 1.0 to GBUCS 3.0 data center. Prior to migration, the PDFs and History Reports must be downloaded by the user.

The utility migrates the following information:

• Study settings (Sponsor settings are not migrated because they are not specific to a study)
• Regulatory data
  • Download log
  • Site Confirmation log
• Administration data
  • CRFS Settings—Study Settings
  • Admin Tool—Study Data

  • CRF Submit rights for the study and the rights history

    For Oracle InForm pre-6.2 studies, CRF Submit rights are migrated.

    For Oracle InForm 6.2 and later studies, CRF Submit rights are not migrated.

All migration requests have a status of Migrated (instead of, for example, Completed or Deleted).

Previously generated files (for example, PDFs or CSVs) in GBUCS 1.0 are not migrated and there are no links to them in the Downloaded requests.