Managing Change with an In Progress Study Design


From time to time, you may need to make a change in your Study while you still have a larger change “in process”. You can make this change without deploying your in process changes by using a process called “hotfix and merge”.

Note that this process is still subject to the Study Update Restrictions listed here.

Create a Secondary Development Environment

To create a new Study Instance:

  1. Navigate to Tools > EDC Tools.
  2. Click your Study Master’s Name in the Study Listing.
  3. From the Actions menu, select + Development. + Development action

  4. In the Create Environment dialog, select a Vault to create your Study Environment in. This is typically the same vault that contains your primary development environment.
  5. Click Continue.
  6. In the Create Environment confirmation dialog, click Create.

Restore from Production

Next, you can restore your secondary development environment from your production environment. This creates your Study as it exists in your production environment in your development environment, copying everything over (except for those changes not included in the study package, listed here).

To restore from production:

  1. Navigate to EDC Tools > Deployments for your study.
  2. Locate your secondary development environment in the list of Environments.
  3. Hover over the environment to display the Actions menu.
  4. From the Actions menu, select Restore. Vault opens the Restore Study Design dialog. Restore action

  5. Select your production environment for Source Environment. Restore Study Design dialog

  6. Optional: Enter a Reason for Change.
  7. Click Restore. Vault begins a job to restore your environment from your production environment. When finished, Vault sends you an email notification.

Make & Deploy Changes

A study designer can now make the required changes. They can create a new casebook version in Studio and work through your organization’s change process.

When changes are finished, you can deploy your study from your secondary development environment into UAT, and then from UAT into production.

Merge Secondary Development Environment into Primary

A study designer can use Studio’s Copy Event Groups, Events, and Forms feature to move the altered design from your secondary development environment into your primary development environment. Learn more here.

Which permissions control your access depends on when your vault was created. If your vault uses the Role by Study feature, see the first section, Role by Study Permissions. If your vault does not use the CDMS Role by Study feature, see the second section, Profile Permissions.

Role by Study Permissions

Users with the standard CDMS Deployment Administrator can create and restore environments and deploy a study. Users with the CDMS Study Designer study role can make changes to study design.

Type Permission Label Controls
Functional Permission EDC Tools Tab

Ability to access the EDC Tools tab

Functional Permission Manage Study Deployments

Ability to create and manage study Environments and deploy Studies from EDC Tools

Learn more about Study Roles.

Profile Permissions

Users with the Vault Owner security profile or EDC Deployment Administrator role security profile, or a copy of that role and security profile, can perform the actions in EDC Tools described above.