After a new version is created, and sites have been included in that version, the system will include any future enrolled subjects in that version. Any subjects that already existed at a site will remain on a prior version unless they are migrated to the more recent version.


Important notes when migrating subjects:


  • All changes made to the study will be applied. To prevent unwanted changes or data loss, please keep this in mind and consider the changes made prior to migrating subjects.
  • All conditional actions on the forms will be re-run by the system unless you check the box "Do Not Run Conditional Actions" as shown in #3 below. This includes notifications and edit checks.

To migrate subjects, for each site on a version:
 
1) Ensure the appropriate version is selected.
2) Click the "Migrate Subjects" link.

3) Option to Not Run Conditional Actions. This will bypass running any conditional actions or resaving of every record during migration. Also keep in mind, since subjects are migrated as a whole (i.e. All records), choosing to not run conditional actions will prevent the migration process from getting stamped to the subject's record audit trail, with the exception of the first record - the subject's registration form). When conditional actions are run, the migration gets stamped to each record. For example, "Subject migrated to new version" along with a date/time.

4) Select "Migrate All" if you want to migrate all subjects in site; or
5) Select which subjects to migrate on an individual basis
6) Click the "Migrate Selected Subjects" tab - This may take a couple minutes depending on the number of records the database is migrating.




When subjects are migrated their records are moved to the new version of the forms, possibly only some of which contain actual changes. If there were any changes to the visit schedule or the forms selected to be collected within the visits, those changes can be made directly in the visit schedule setup. Version migration is only related to forms and data.