What's New in 23R2

Pre-Release Date: July 17, 2023 | CDB Pre-Release Date: July 24, 2023 | Release Date: August 4 & 11, 2023

We are pleased to bring you CDMS in 23R2. Read about the new features below. You can find information on enabling new features in the 23R2 Feature Enablement Details. Information on developer features (REST API) is in the Developer Portal.

CDMS

Features in this section are changes that apply to all application areas of Vault CDMS.

Show Sponsor in the My Vaults Page

This feature provides an enterprise-wide, homepage grid view that allows scalability for users who need to navigate and manage tasks across higher numbers of Vaults (500+). Columns within the home page can be sorted, filtered, and searched.

Users can select box or grid view which will display the following columns:

  • Vault Name
  • Sponsor
  • Last Login
  • Application Family (e.g. Clinical, Promomats, RIM, Quality, etc.)
  • Type (e.g. Sandbox, Production, etc.)
  • Domain
  • My Tasks

Column names are translated based on user’s language preference.

Use Case

Veeva CDMS Customers can have access to multiple Vault applications and CRO end users often manage and operate across multiple sets of separate Sponsor Vaults including (Dev, Test, Prod and Train). The new My Vaults page provides a better user interface through an enhanced grid view and quick navigation for all Vault users with access to many Vaults.

Enablement

This feature is automatically available for domains where the MyVaults flag is set by Veeva Admins. The Sponsor and Type objects are only editable by Vault Owners. Filters display by default for users with more than 25 Vault memberships.

Small Screen Size Warning

Vault presents users with a warning dialog in cases where a user’s screen resolution is less than the minimum supported setting of 1280 x 720. The dialog displays to impacted users upon entering the Data Entry, Review, Protocol Deviations, and Assessments tabs for the first time in a session. As part of this change, we made small changes to the shades of some colors in the application.

Enablement

These changes apply automatically.

Data Entry

Features in this section are changes to the Data Entry tab, a working area for investigators and clinical research coordinators to enter study execution data.

All Bookmarks in Detail PDFs are Clickable

In the Detail PDF, all bookmarks are now hyperlinks.

Enablement

This feature is automatically enabled.

Form Not Submitted Dialog to Display Only for Users with Data Entry Permissions

The Form Not Submitted dialog will only display to users with Data Entry permissions when they navigate away from an In Progress form.

Use Case

The Form Not Submitted Dialog will only display to affected users.

Enablement

This feature is automatically enabled.

Clinical Coding

The following are new features for Coder, the clinical coding area for Vault Coder.

Display Third-Party Coding Suggestions

This feature displays third-party suggestions in the Coder UI, which will reduce the time users spend on locating the correct coding.

Use Case

With this feature, Coders can select from a list of curated suggestions rather than trying to locate the correct code directly from the dictionary. Coders can also delete suggestions on a form so that the third-party can generate and post new suggestions for the entire form.

Enablement

Contact Veeva Support to enable this feature.

Learn More

With this release, Verbatims are displayed and grouped in all caps in List View, Group View, and the Properties Panel when the respective study setting is set to “Yes.” The Coder Verbatims page will display the following fields in all caps format only:

  • Verbatim
  • Seriousness (if applicable)
  • Indication (if applicable)
  • Route (if applicable)
  • Any other configured related items

When grouping by these fields, Coder will group in all caps format only.

Use Case

With this feature, Coders can quickly and easily read Verbatims when they are grouped regardless of capitalization. Previously, coders would see duplicates of the same Verbatims and Related Items due to differences in capitalization.

Enablement

This feature is automatically enabled.

Study Design & Configuration

Features in this area apply to Studio, the study design and configuration area for Vault EDC.

Create Procedures via Rules

Procedure definitions can be configured by Study Designers in the new Integration Configuration tab within Studio. The creation of the procedure records can be based on field mappings or by creating user defined rules to evaluate casebook data. Procedure definitions can evaluate eCRF data values, subject status, form submitted date or form status, such as SDV, and also per the subject’s country. Procedures can be determined from a single or repeating form design or from a repeating event group. Configurations can now be validated in TEST as part of user acceptance testing without transmitting test data to CTMS. We added a new Integrations sheet to the SDS and Difference report for studies using this feature.

Use Case

This feature supports a more granular definition of Procedure completeness when automating procedure records to CTMS.

Enablement

This feature is automatically enabled for new studies. For existing studies please contact Veeva Managed Services to enable the appropriate setting.

Learn More

Rules Enhancements

The following enhancements have been made to rules:

  • Subject status rules now allow users to use repeating Event Groups, Forms, and Item Groups in the Rule Action, so long as a sequence number is specified.
  • Added functions:
    • HasDuplicates(): Returns true if any 2+ arrays have equal values for all the identifiers inside
    • SiteDateTime(): Automatically creates datetime from Date item and Time item in Site timezone
    • SiteDateValue(): Returns the date from a datetime item and automatically puts it in Site timezone
  • The Rule Preview job now shows all rules from the job in the rule_details file, to provide clarity for job results where a rule was included in the job but resulted in no change (e.g. Action = None).
  • General enhancements:
    • Study Designers will see updated rule action labels and order of actions when selecting a Rule Action in the rule editor.
      • Query action has been relabeled to Open Query
      • Ready to Randomize has been relabeled to Set as Ready to Randomize
    • A new rule action type called Create Integration Entry has been added to support new Procedures features
    • When changing the Evaluate Rule When property for a rule, the rule editor no longer clears Rule Actions if a valid action has already been set
    • In the SDS, the Date Comparisons tab has been relabeled to Comparison Rules to match Studio

Action Required: Users must fix or inactivate misconfigured rules (specified below) in order to deploy from DEV. Studies that have already been deployed to UAT/PROD won’t be affected but misconfigured rules will be flagged as invalid in the next casebook version.

Additional validations have been added to safeguard against misconfigured rules, including:

  • Derivation rules where the result does not match the target item’s data type
  • Rules using @Form or ‘this form’ identifiers when the associated form in the Rule Details panel doesn’t match in the expression or action
  • Subject status rule actions must be fully qualified

We also downgraded ER-46, ER-20, and ER-19 to warnings. This change is not part of 23R2 pre-release and will only apply at the 23R2.0 general release.

With this release, several functions from the Vault Platform are now exposed in the Rule Editor’s Formula Selector. Many of these functions aren’t applicable to the formulas most commonly used for CDMS rules. We recommend that you only use those functions covered in the CDMS Formula Reference.

Use Case

These rule enhancements reduce errors and provide usability improvements, further validations, and additional rule configurations for Study Designers.

Enablement

Automatically enabled for new and existing studies. End users must revise or inactivate any broken rules the next time they validate study configurations.

Learn More

Study Administration

Features in this section apply to EDC Tools, a study-level administration area for Vault EDC.

Snapshots: Bulk Lock & Freeze

With this release, we’ve added a new tab, Snapshots, to the Review tab where Data Managers can create snapshots of clinical data for analysis during study milestones. Users can use specific filtering to define milestone criteria for the selected subset of data before performing lock/unlock and freeze/unfreeze actions in bulk. This feature also includes a Bulk Action Preview, which allows the user to select which sites and casebooks to preview. The Bulk Action Preview shows both data that is ready for bulk action (the data that meets the milestone criteria), and data that is not ready (data that is within the milestone but doesn’t meet all of the milestone criteria). The resulting bulk action job sends an email notification and provides a report detailing the subjects and events that were bulk actioned.

Use Case

Some data managers lock data for interim milestones, so the enhanced “bulk action” capabilities using the new snapshots feature can provide a more efficient process.

Enablement

This feature is automatically available in Studies using Data Model V2.

Learn More

Query Team Selection Enhancements

This release includes the following updates to the options for assigning a query team in multi-role security vaults:

  • If a user has multiple roles on different query teams and creates a query, the query team dropdown list will only contain teams associated with the roles with the query permission. If a role does not have a query permission, the associated team will not display in the query team dropdown list
  • If a user with multiple roles only has one role with a query permission, the query team will default to that role’s team

Use Case

This update simplifies the query workflow for multi-role security.

Enablement

This feature is automatically enabled.

Event Window Reporting Enhancements

This release updates the calculation for Days Outside Event Window and Event Window Status in the Event Progress Listing and Event Operational Summary report. The calculation now uses Event Date and Planned Date, rather than Event Datetime and Planned Datetime

Additionally, new Event Window Statuses have been added with this release, which will be visible in the Event Progress Listing and event reports.

  • Planned: An event does not yet have an event date.
  • No Defined Window: An event window has not been defined for the event.

Use Case

This update addresses inconsistencies in calculation caused by daylight savings time. It also completes the transition away from datetime fields for Event Date and Planned date in support of the planned deprecation of event datetime fields.

Enablement

This feature is automatically enabled.

CDMS Billing Status Support

This feature supports the tracking of a study’s licensing and billing status. The billing status of a study is set to Deployed automatically upon deployment to production. Through EDC Tools, an organization’s enabled users can modify the study status to On Hold, Locked, or Archived.

As part of this feature, we renamed the Manage Study Lock permission to Manage Study Milestones.

Use Case

This feature provides clients the ability to independently manage billing statuses for studies on hold, locked, or archived.

Enablement

This feature is available immediately. Existing studies that do not yet have a Production Environment created will need to have the licensing status updated by Veeva. Updating Billing Status will be available for any role with the Manage Study Milestones permission. This feature only applies to production (PROD) study environments, and so it is only available in production vaults.

Learn More

Deploy from Template Vault

In System Tools, CRO users with the Manage Deployments permission can now create and edit Deployment Groups in order to deploy role and permission updates from the CRO Template Vault into multiple Sponsor-DEV vaults at the same time. Users can include up to 15 vaults in a single Deployment Group.

Use Case

Previously, any changes made to the CRO standard vault settings needed to be updated separately in each of the CRO-managed Sponsor vaults. With this feature, users can push changes from the CRO Template vault into multiple Sponsor DEV vaults at the same time.

Enablement

Contact Veeva Support to enable this feature in your vault.

Learn More

Job Governor Enhancements

The Audit Trail Export jobs (by Study, by Site, and by Subject) will now be included in the Job Governor. This inclusion ensures that two audit trail jobs of the same type won’t run simultaneously, freeing resources for other jobs. For audit trail jobs, this feature will only keep ad hoc jobs from starting if a job of the same type is running.

Users cannot start any identical extract job covered by the job governor if the job is in the Queued or In Progress status with this feature.

As part of this feature, we introduced the Queued status in the extract job governor to improve processing efficiency.

Use Case

This feature ensures that multiple jobs for the same type of data aren’t scheduled to run concurrently.

Enablement

This feature is automatically enabled.

Learn More

Study Progress Listings Enhancements

The following enhancements have been made to the Study Progress Listing:

  • Study Summary Metrics: Updated several column names to clarify that the data refers to forms that are SDV / DMR Complete
  • Subject Progress Listing: Added columns for form SDV and DMR Completion status
  • Subject Progress Listing: SDV/DMR Complete columns will be blank if SDV/DMR Plan is blank
  • Event Progress Listing: Added new columns for Submitted Forms SDV Required and Submitted Forms DMR Required
  • Event Progress Listing: Event Date SDV Required and Event Date DMR Required columns will only be populated for events with an event date field

We’ve also enabled the Study Progress Listings in the Reports tab feature for all Vaults. Users will still need to schedule listing jobs to populate the corresponding listing reports in the Reports tab.

Finally, we relabeled the columns in the Study Summary Metrics report to include “Forms”.

Use Case

These updates improve the usability of and clarity for Study Progress Listings.

Enablement

This feature is automatically enabled.

Learn More

SDE: Enhancements

The following enhancements have been made to the 23R2 version of the SDE:

  • Item columns in the Clinical Datasets will be sorted based on their order on the form
  • The following columns were added:
    • Form Status to Clinical Datasets
    • Last Modified Date to SYS_SUB dataset
    • Source Form Restricted to SYS_ASM and SYS_ASMR and Restricted to SYS_Q and SYS_QT datasets
    • Created By and Assessment External ID to SYS_ASM and SYS_ASMR datasets
    • Reassessment to SYS_ASM dataset
    • Assessment Name and Question Text Definition to SYS_ASMR dataset
  • Additional error logging when a job fails due to user permissions
  • New option to configure which item display label (default label or short label) will be included in the extract. If no short label exists for an object, the default label will be used. This label can be found in the study definitions file and is used as the SAS label. The allowed length of the short label was also increased to 40 characters to support this update.
  • The Export File Type field is now a selector that allows any combination of the three options: CSV, SAS, and XPT
  • Added Item External ID column to the SYS_ILB, SYS_Q, SYS_PD, and SYS_LINKS datasets
  • Added Event Group External ID column to clinical datasets, SYS_EVT, SYS_FORM, SYS_ILB, SYS_LINKS, SYS_Q, and SYS_PD
  • Added columns to the SYS_LINKS dataset to clarify the Form Created Date and Link Created Date
  • Users must have the View Casebook permission to see and run the SDE job

Use Case

These updates provide additional metadata about forms in the extract.

Enablement

This feature is automatically enabled with SDE version 23R2.

Learn More

Recalculate Normalized Datetime Values Job

This feature includes a job which will update the normalized values for datetime items in a site based on the current site timezone. The job will run automatically when the timezone is changed for a site that has existing subjects. This includes when the timezone is changed through EDC Tools or when the timezone changes come from CTMS. The option to manually run the job is also available out of EDC Tools in cases where jobs may not have completed successfully.

Use Case

A site that has existing subjects with form data containing datetime items that have values were previously impacted when the site’s timezone changed. The forms that contain the datetime items are not usually re-submitted, and the normalized values for the items were not updated based on the new site timezone. This feature avoids the possibility of having incorrect normalized values for datetime items in a study. It is important to have correct normalized values as they are used for rules, extracts, etc.

Enablement

This job is available automatically.

Learn More

Review Plan Job Enhancements

This feature confers performance enhancements to the Review Plan Reorder and SDV/DMR re-assignment jobs, particularly for complex casebook designs and large number of casebooks. In addition to these strictly performance-based enhancements, the Reorder job will now clean up Review Plan Casebook records that have become corrupted due to either a subject transfer or inadvertent deletion of manual assignments when a Review Plan Assignment record is changed. Previously these invalid records would have needed to be removed via CC before a customer could become unblocked.

Enablement

These changes apply automatically.

Integrations

Features in this section are new integrations with Vault CDMS or enhancements to existing integrations.

Safety Integration: Study Drug Level Blinding

Safety Integrations (formerly E2BLink) now classifies the blinding property at the study drug (treatment) level. Prior to this release, blinding was a study level settings. This could cause issues when a study has multiple study drugs, where one is blinded and one is not. This blinding is controlled by the Blinded field in the Study Drug section of Tools > EDC Tools > Safety Configuration.

As part of this feature, we removed the Investigational Product Blinded setting from the General Settings section, as this has been replaced by the new Blinded property in the Study Drug section.

Use Case

Studies may involve more than one study drug, with different blinding requirements. This feature allows organizations to handle those differing requirements when sending study drug information to the safety system.

Enablement

This feature is automatically enabled. Existing studies with a configured study drug will automatically have the blinding property set to No (false).

Safety Integration: Handle Adverse Events with no Term Item Value

Safety Integrations (formerly E2BLink) will now add a default AE term or verbatim where the event in the case no longer has text. This text is “AE term no longer available”. The primary example of this is a form reset by site on mistaken entry of AE form.

Use Case

Prior to this release, import into some safety systems fails when the Item for the term or verbatim is empty on the Adverse Event form.

Enablement

This feature is automatically enabled.

Safety Integration: Enhanced Reporting

Safety Integrations (formerly E2BLink) now include additional fields on the Safety Case for better tracking and referencing. These new fields are only tracking information from the release forward, older safety cases are not updated with information until there is another follow-up generated for the case.

We added the following columns to all existing and new EDC reports on Safety Cases and Safety Messages:

  • Events in Case: All transferred cases.
  • Form Sequence: The Sequence Number of the SAE form.
  • Last Send File Name: Filename of the last sent file. Users can search the safety system for the file.
  • Last Send Safety: Date and time of the most recent Safety Message.
  • Last ACK File Name: The file name with the date and time.
  • Additional Follow-up Pending: This column shows “true” if additional changes were detected, but a previously sent follow-up hasn’t yet triaged into the system.

This new tracking information is only available for Safety Cases and Safety Messages sent from 23R2 and forward.

Use Case

A single report is crucial for the review of safety cases in a study. Previously, one had to cross reference a number of reports and view casebooks in the Data Entry tab to align which Safety Cases and Safety Messages applied to which subject and serious adverse events. Additionally, some safety systems have quick searches by file name sent to them, and showing that information at the safety case level will be useful.

Enablement

This feature is automatically enabled. The template reports in the system for Safety Cases and Safety Messages now contain the new fields. To use these fields in any custom reports, a user will need to add them.

Learn More

Safety Integration Follow Up Processing Changes

With this release, we made follow-up processing more robust, to assure the sending of a follow-up report with any data changes for existing Safety Cases. Vault now uses a recurring job, instead of an integration task on a timer, to do follow-ups. Users can configure this enhanced follow-up processing job to run daily or twice a day. They can also schedule a weekly or monthly scan of all cases, or run on an ad hoc basis, to resolve any potential issues with incremental follow-up reports.

Users with the Manage Safety Integrations permission can make schedule changes to this job from Tools > Safety Integrations > Study Settings in the Job Schedule Settings section.

Use Case

Evaluation of medicinal product safety depends on reliable and up-to-date Safety Case data. Follow-up reporting must be assured for any change to any data of existing cases. A full re-run for follow-up reports allows for the consolidation of all Safety Cases on a regular basis.
With the release of the Duration Inclusion Criteria for Related Forms feature in 23R1 (April 2023), changes to a live study’s design could mean that previously sent Safety Cases now require a follow-up, based on the adjusted rules. With this feature, the scheduled full scan catches those case changes, or a user can run an ad hoc scans immediately after deployment of such changes.

Enablement

This feature is automatically enabled. Veeva will contact customers to discuss this change in more detail. Each existing production Study that has the safety integration enabled will be configured to run the job once daily, at 2:00 AM UTC, and run a full scan monthly, on the 15th of the month, unless otherwise specified. Development, training, validation, and test (UAT) environments will not have any jobs automatically scheduled. In these environment types, this job is typically run on an ad hoc basis. Organizations can continue to review these job configurations and other safety settings as their study progresses from Tools > Safety Integrations.

Learn More

Safety Integration: Vault Safety Inbox

Safety Integrations (formerly E2BLink) includes new additional support with the Vault Safety Inbox, for those integration studies with Vault Safety. Both the Vault Safety and Vault CDMS systems still need one time setup for the connection, as before. But, the ability to direct safety data to the Inbox (vs. AER Inbox) tab no longer needs to be configured on the Vault Safety side. Instead, it is a setting within the CDMS Vault that directs the data to the newer Inbox tab.

Use Case

Connecting safety data from Vault CDMS studies to Vault Safety requires one time configuration in both Vaults. In addition to the one time connection setup (Vault to Vault), a study in Vault CDMS can be optionally pointed to either of the Vault Safety Inbox locations.

Enablement

This feature is enabled automatically. By default all vaults are set to use the AER Inbox for Vault Inbox Type. This is the default behavior from prior to this release. For organizations using the main Safety Inbox, connection properties in CDMS must be adjusted.

Safety Integration: Nullification Mapping & Default Reason

Safety Integrations (formerly E2BLink) now allows mapping to a Reason for Nullification / Amendment (C.1.11.2) from the Serious Adverse Event form. For studies that don’t have this mapping, and a case is nullified, Vault CDMS will add a default reason to the E2B XML sent to the safety system.

Use Case

Nullification follow-up transfers are when a case / event(s) are no longer applicable. Previous to this release, Vault CDMS was not sending anything for reason, and some safety system configurations consider it required, Examples of nullification transfer:

  • Site data entry mistakes, for example, a form reset, where a case previously sent,
  • Downgrading an existing serious AE to non-serious, where a case previously sent.

Enablement

This feature is available automatically, but a study designer must update the study design with a mappable Item in a non-repeating Item Group and deploy that change.

Screen Subjects Outside CDMS

CDMS APIs now have the option to exclude subjects that have not reached an enrolled status in CTMS. Prior to enrollment, subjects will first be created in CTMS, either manually or through an integration with an external system. Once enrolled, the subject will be created in CDMS by the IXRS system and the connection with CTMS will check and match the corresponding subject record in CTMS. The subject’s status will reflect as “Enrolled” in CDMS per the Subject Status rules configured in Studio by the Study Designer.

Use Case

For certain studies, using IXRS and CTMS, the desired workflow is to first process a subject’s pre-screening and screening events in CTMS and then only add the subject in CDMS once they are enrolled into the study. This feature removes the mismatching that can occur between CDMS and CTMS by creating only enrolled subjects in CDMS and automatically connecting them with CTMS.

Enablement

This feature is automatically enabled for studies that are using the 23.2 version of the APIs and where CTMS or a third party system are connected. Existing Live studies would need to update their API version to utilize this feature. To see the new IXRSID field in the SYS_SUB dataset, the 23R2 version of the SDE must be selected when running the extracts.

Developer Features

The following are new features for the CDMS API. See our CDMS Developer Portal's release notes for more detailed feature information.

CDMS API Features

This release includes the following new and updated endpoints for CDMS developers:

  • Start Job - Study Data Extract
  • Start Job - Event Progress Listing
  • Start Job - Audit Trail (New)
  • Update Subject (New)
  • Retrieve Form/Item Data - Frozen/Locked
  • Create Subjects (Casebooks) - IXRS ID and CDMS URL
  • Retrieve Subjects - IXRS ID and CDMS URL
  • Set Coding Suggestions (New)
  • Retrieve Coding Requests - Additional Filters and Suggestions Support

Veeva CDB API Features

We introduced new endpoints to allow for query management outside of CDB:

  • Get Form Data
  • Open Query (Items)
  • Open Query (Events)
  • Answer Query
  • Close Query

Clinical DataBase (CDB)

The following are new features for the CDB application, the Vault CDMS solution for data cleaning and reporting.

Availability: Clinical DataBase (CDB) is only available to CDB license holders. Contact your Veeva Services representative for details.

Advanced Joins in CQL

CQL now supports the definition of direction and criteria for table joins. CQL allows multiple joins within a single CQL statement.

In this release, CQL supports the following join types:

  • LEFT JOIN: All records from the first (left) table and any matching data from the second (right)
  • RIGHT JOIN: All records from the second (right) table and any matching data from the first (left)
  • INNER JOIN: Only records from both tables where a match is found

Users must define the join conditions for advanced joins, including joins to the header. Tables of data can be a form, subquery, or a view.

Use Case

The ability to define the direction of table joins allows for more complex and performant listings, where users can define with more precision which rows of data to return.

Enablement

Advanced joins are automatically available.

Learn More

Conditional Unblinding

Conditional unblinding allows items from third-party data sources that are marked as blinded in the manifest to be unblinded based upon data within the same data set. Only one rule per data set is allowed, but the rule can unblind multiple items, and can have multiple conditions to determine if those items should be unblinded.

This feature introduces the Manage Unblinding Rules permission, which is assigned to the CDMS Super User and CDMS Lead Data Manager study roles by default.

Use Case

This feature allows selected data to be unblinded based on data within the import file from third party sources. For example, lab data may contain values from multiple tests. If some but not all of the test results need to be blinded, this feature allows users with the new Manage Unblinding Rules permission to configure a rule to unblind test results for those tests that do not need to be blinded.

Enablement

This feature requires the Mask Blinded Data feature to be enabled at the Vault level. At the study level, rules can be configured from the new Sources page under Import. Rules are not deployable and must be configured for each study instance separately.

Learn More

Import In Progress Post Submit Data from EDC

The Workbench Export job now includes data from forms in the In Progress Post Submit status for transfer from EDC to CDB. Forms enter this status when the form is submitted then reopened for edits. Prior to this release, the job only included data from forms in the Submitted status.

Use Case

This allows custom listings to include data that was previously available as Submitted, and users can now reference it in the CQL WHERE clause: WHERE @Form.Status in ('submitted__v', 'in_progress_post_submit__v')

Enablement

This feature is automatically enabled. All jobs after the release will include form data in the In Progress Post Submit status.

Learn More

CDB Product Naming

With this release, we’ve updated the header of CDB Workbench and CDB Manifest Builder with logos that reflect their names. As part of this change, we updated the URL of CDB Manifest Builder. The previous URLs will continue to work after the release, redirecting the user to the new URL.

Use Case

This change improves the understanding of the different components of the application through consistent naming.

Enablement

These changes apply automatically.

SDE: Send Data to CDB

With the 23R2 version of SDE, customers with CDB enabled can send SDE datasets to CDB, where they’ll be handled like third-party data in the application. Users can schedule jobs or run them ad-hoc, as well as include specific datasets in the job. SYS datasets with metadata not generally available from EDC and custom object data can be included when configured in the Vault, for example. Note that sending SDE data to CDB allows two additional SDE jobs to be scheduled and doesn’t count against the job governor limit. Attaching a manifest file to the job is required, as the data will be treated like third-party source data in CDB.

Use Case

This feature allows Vault data that isn’t included as part of form data currently transferred via the Workbench export to be sent on a regular schedule to CDB.

Enablement

Contact Veeva Support to enable this feature.

Learn More

Mask Blinded Data

CDB now provides the option at the Vault level to add a mask to blinded data. You can select to mask data in the UI, in exports, or both.

Use Case

This feature displays the column to end users, while keeping the value of the data masked. This is required to enable Conditional Unblinding.

Enablement

This feature must be enabled from CDB > Configurations. Enabling this feature does so for all Studies in the vault.

Learn More

OpenEDC: Support for Non-Veeva EDC Studies

Open EDC allows customers using Legacy EDC systems, with studies outside of Veeva Vault CDMS, the ability to clean their study data using CDB, by importing data from their EDC system into CDB. This feature utilizes the new External study type in Studio when creating a study instance.

This feature introduces the new Manage Sources permission, which is assigned to the CDMS Super User and CDMS Lead Data Manager study roles by default.

Use Case

Customers who have studies outside of Vault CDMS will be able to use a single system for data cleaning from all of their data sources.

Enablement

Contact Veeva Support to enable this feature.

Learn More

Migration Vault

Features in this section are new features for Migration Vault.

Abandon Loads

Users can now stop a step that is in progress from within Migration Vault. Once this happens, Migration Vault abandons the Load, and a user must start a new Load to migrate data.

Use Case

Prior to this release, there wasn’t a way to stop a step after it started. Users could only stop the Execute All workflow, which prevented the next step from starting. This inability was troublesome for steps that take longer to complete, such as Run or Dynamic Rules. Users can now stop steps whenever needed, instead of waiting for the step to complete.

Enablement

This feature is automatically enabled and available on any In Progress steps.

Study Decomissioning & Database Clean-up

After a Study has finished migrating or after a release, there is no formal process in place that removes a Study’s data from the applicable databases, which can lead to performance issues. After a Study has successfully migrated and after a release, this process ensures the appropriate environments and databases are cleaned up and that the migrated study is decommissioned.

Use Case

As part of Veeva’s partner agreement, Veeva is required to delete all of a customer’s DEV and UAT/TEST study data after migration is complete. This feature ensures that the data is automatically deleted, rather than depending entirely on human intervention.

Enablement

This feature is enabled automatically.

Migration Vault: General Enhancements

During Step 2 of the migration process, it is best to deactivate any system rules first to prevent a mass amount of system queries from being triggered. As part of this feature, any system generated rules and queries will be deactivated as part of Step 2 in the migration process. Once migration is completed, the rules and queries will be reactivated so that they will fire if new data is entered or a form is submitted.

Use Case

These features and enhancements are necessary in order to successfully migrate a study though its DEV, UAT, or even PROD cycle.

Enablement

These changes apply automatically.

Migration Vault: Reconcile Listings

Currently, there is an existing defect in CDMS in which the UI and the Database records can get out-of-sync after a successful migration due to the amount of migrating data and CDMS’ inability to process it all. When this occurs in Production, there is a “Sync-job” that repairs any discrepancies, but there is no job that will sync the data in DEV and UAT/TEST environments. This new feature and step will allow users to run the Reconcile Listings job from within the Migration Vault after a Load is complete to ensure that the UIand Database records in CDMS are synchronized.

Use Case

Ensures that the data is synchronized so that Professional Services can determine whether the data successfully migrated. By making it available as another optional Step (for UAT & PROD Loads) in the workflow, it offers the following advantages:

  • It may not always need to run, so we can avoid extending the length of the Load.
  • With the new vault-per-study, the job is run every day at 6 PM PST. So if a Load is executed before but around that time, it may not need to be executed via the MigVault.
  • If the issue is ever fixed in CDMS so that the job is no longer required, then the MigVault UI does not have to be redesigned. The job can be kept as back-up.

Enablement

These changes apply automatically.