New Features in 25R1 Limited Releases
25R2 Planned General Availability: July 25 & August 1, 2025
25R1.4 Release Date: June 20, 2025
25R1.3 Release Date: May 30, 2025
25R1.2 Release Date: April 25, 2025
We are pleased to bring you new functionality with each limited release. These release notes are updated with upcoming new features one week before the limited release date.
Enablement Changes: The enablement of each feature is subject to change from release to release. For limited releases in the same general release, we will update this page. Enablement may also change before the general release. Refer to the Release Impact Assessment for the most up to date enablement for a general release.
Clinical Data
Features in this section are changes that apply to all application areas of Veeva Clinical Data.
Clinical Data Naming Update in PDF Export 25R1.2
Use Case
For clarity and simplicity, we have updated the name of the system to Veeva Clinical Data.
Description
This release updates PDF exports in the Clinical Data system to reflect the name change.
Enablement & Configuration
This feature is automatically enabled with the release.
Screen Size Warning Adjustment 25R1.2
Use Case
This update reduces the occurrences of the screen size warning dialog displaying to end users to provide a better UI/UX experience.
Description
The threshold has been lowered for triggering display of the screen size and resolution warning dialog, which will now display to users for screen widths < 1270 or heights < 550. The warning is now displayed when the application becomes unusable rather than when it’s sized below the recommended screen size.
Enablement & Configuration
This update applies 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.
Edit Value Button Hidden for Answered Queries 25R1.2
Use Case
This update changes the query dialog to help site users easily identify queries that have already been answered.
Description
When a query is in an answered state, the Edit Value button will now be hidden. Note, the user will still be able to edit the value where the query is shown by clicking the Edit Form button. Similarly per the existing behavior, when the query is in an Open state, the Edit Value button will be enabled.
Enablement & Configuration
This update is automatically available.
Data Review
Features in this section are changes to the Review tab, a working area for clinical research associates and data managers, or to review functionality within the Data Entry tab.
Updates to Form Summary Fields 25R1.2
Use Case
This update ensures consistency across all cycle time calculations and supports reporting on cycle time metrics in Workbench and Clinical Reporting.
Description
The following Form Summary Cycle Time metrics will now return null values if the cycle time calculation is negative:
- Update Visit to Form Submit Cycle Time
- Update Submit to Signature Cycle Time
- Update Submit to SDV Cycle Time
- Update Submit to DMR Cycle Time
- Update Submit to Frozen Cycle Time
- Update Submit to Locked Cycle Time
In addition, the calculation for the Submit to Signature Cycle Time metric has been updated to use two decimal places.
Enablement & Configuration
This update is automatically available.
Clinical Coding
The following are new features for Veeva Coder, the clinical coding area for Veeva Coder.
Option to Include Autocoding for Approval 25R1.2
Use Case
In order to support coding consistency and the accuracy of review in Veeva Coder, when the approval workflow is enabled for a Study, Coder Administrators can now configure Autocoded terms to also go through the approval workflow. This update removes the need to rely on reports or extracts to perform these reviews externally.
Description
This feature adds a new Coder Tools Study/Default Study setting to Include Autocoding in Approval Workflow, which is enabled only when the existing setting Enable Approval Workflow is set to Yes.
This setting can be implemented as a Default Study Setting or individual Study Setting. When set to Yes, any terms that are autocoded due to a Synonym List or exact dictionary match will move to the Pending Approval status, and upon approval will move to a final status of Autocoded. The default value for this setting is No.
To support this addition of this field to the UI and provide more clarity to user administrators, we’ve also reorganized the settings layout and added additional tooltips. Tooltips are visible when hovering over the options while in Edit mode.
Enablement & Configuration
These updates are automatically available after the release. Existing and new studies will have a default vault of “No” for the “Include Autocoding in Approval Workflow” setting.
Sync Coder Lists Enhancements 25R1.3
Use Case
This update supports improved synonym list maintenance for customers managing studies across multiple production vaults using the EDC Sync Coding Lists Vault connection.
Description
Prior to this release, customers with multiple PROD vaults using the EDC Sync Coding Lists Vault connection could only use the options to Apply to Synonym List when approving a code and the Propagate Code function in the primary Prod Vault. This release makes these functions available in the secondary Prod Vault, supporting bi-directional updates to the synonym list.
Additionally, the connection name has been updated from CDMS Sync Synonym List to EDC Sync Coding Lists, since the connection includes Do Not Autocode lists.
Enablement & Configuration
This feature is automatically available in vaults using the EDC Sync Coding Lists connection across multiple Production vaults.
Imaging
The following are new features for Veeva EDC Imaging, the imaging exam module for Veeva EDC.
Imaging: Patient Name Assigned as SubjectID During De-Identification 25R1.2
Use Case
To provide traceability within downstream viewing applications, the metadata for Patient Name contained in uploaded DICOM files is now assigned the Subject ID value during the de-identification process.
Description
During the process of uploading DICOM file(s), the system automatically de-identifies specific PI/PII metadata including the Patient Name. Previously, the system assigned an anonymized value for the Patient Name as part of the de-identification process. With this release, the Subject ID is now assigned to this field. The Subject ID will be seen when the file is downloaded or viewed outside of EDC.
Note: Within EDC there is no visible change in the UI for Data Entry or Imaging end users. In EDC, the Patient Name will show the De-Identified tag:
This update applies only to the metadata value seen when viewing the file in downstream systems.
Enablement & Configuration
This update is automatically available for studies using Veeva EDC Imaging.
Assessments
The following are new features for the Assessments area of Veeva EDC.
Subject Filter Added to Assessments Grid 25R1.2
Use Case
We’ve added a new Subject filter to make locating and searching for subjects within the Assessments tab easier.
Description
The Assessment grid now includes a Subjects filter, which is located between the existing Site Number and Reassessments filters. The new text search is not case sensitive, alphanumeric, and will search subject IDs from left to right.
Enablement & Configuration
This update is automatically available.
Study Design & Configuration
Features in this area apply to Studio, the study design and configuration area for Veeva EDC.
Schedule Grid Improvements for Dynamic Rules 25R1.2
Use Case
These enhancements for viewing dynamic rules provide better usability and clarity for study designers when working within the Studio Schedule Grid.
Description
Updates seen within the Studio Schedule Grid include:
- A new icon for dynamic Forms, Events, and Event Groups where no rule is configured. On hover over the icon, the tooltip message displays “No rule. Click to add.” and opens directly to the Rule Editor on click.
- Count of rules (active + inactive) configured for the dynamic object: “View rules (#)” appears when hovering over the dynamic rule icon ().
- New dialogue when clicking the dynamic rule icon displays additional details of the rule(s).
Enablement & Configuration
These updates are automatically available in Studio.
Repeating Item Group Data in Email Notifications 25R1.2
Use Case
Additional configuration options for email notification rules provide better visibility into data for email recipients.
Description
Email notification rules now support data coming from repeating item groups. When configuring a rule, study designers can add tokens for items located within repeating item groups to the Message area of the Send Email rule action. New tool tips for the Rule Action help guide study designers when including data from repeating item groups.
Email recipients will see the applicable data within one email notification for all item group repeats where the rule logic evaluates to true.
Enablement & Configuration
This update is automatically available in Studio.
Rule Editor Supports Country Code on @StudyCountry 25R1.2
Use Case
This feature allows study designers to program rules based on Veeva Vault Platform’s standardized country code values. The standard country codes, added as part of the 24R3 general release, provide a seamless connection between countries across different applications regardless of differing country names. These codes can now be used in the Rule Editor to ensure the rule always references the correct study country, even if the country name is changed by the Clinical Operations - EDC connection.
Description
The country code, @StudyCountry.country_code__v, is now available when creating rule identifiers in the Studio rule editor. As a best practice, study designers should use this reference instead of the country name text string when configuring User Defined Rules.
Enablement & Configuration
This update is automatically available in Studio. For Vaults created prior to 24R3, please contact Veeva Support to ensure the latest country codes are updated for the Vault.
Study Administration
Features in this section apply to EDC Tools, a study-level administration area for Veeva EDC.
Enhanced Tooltip for Audit Trail Export Jobs 25R1.2
Use Case
Tooltip enhancements provide added details to help end users quickly identify which job options were included in the audit job.
Description
Hovering over the information icon next to the Audit Trail Export job within Job History will display the details of the job. The selected Date ranges, Users, Sites, Subjects, and options for Include the Definition, Relationship and Facade Audit Changes; and Include Medical Coding Audit Trail will be seen within the tooltip. When no selections are made, then the information icon will be hidden. The selections can be seen in the following jobs:
- Audit Trail Export by Subject
- Audit Trail Export By Site
- Audit Trail Export by Study
Enablement & Configuration
This update is automatically available.
Hide origin_site_for_ctms__v from Audit Trail 25R1.2
Use Case
This update improves the readability of audit trails by no longer displaying unhelpful ID values that provide no meaning to the user.
Description
In 25R1, we released updates to the Move Subject function, including stamping the origin site on Events and Protocol Deviations to support site payments handled in Clinical Operations Vaults. In 25R2, we will no longer include the ‘origin_site_for_ctms_v’ value in the Event or Protocol Deviation audit trail UI, Detail PDF, or Audit Trail Export output, as the displayed ID value provides no value to the end user. The action of moving the subject to a new site remains in the audit trail.
Enablement & Configuration
This update is automatically available.
Clinical DataBase (CDB) & EDC Clinical Reporting
The following are new features for the Veeva CDB application, EDC Clinical Reporting (the Veeva Clinical Data solution for data cleaning and reporting), or both.
Availability: Clinical DataBase (CDB) is only available to CDB license holders. Contact your Veeva Services representative for details.
Enhanced Conditional Unblinding Rules 25R1.2
Use Case
To support more complex rules for unblinding data, we added additional operators for conditional unblinding rules.
Description
Conditional unblinding rules for text and number items (integer, float) now support the IN and NOT IN operators. This allows rules to easily check if an item’s value matches (or does not match) any value within a single comma-separated list. This enhancement overcomes the previous limitation where a rule could combine a maximum of six (6) distinct conditions or condition groups, as one IN or NOT IN condition can now efficiently test against multiple values simultaneously.
Enablement & Configuration
This feature is automatically available with the release.
Exports: New Columns Added to Raw Core Listings 25R1.2
Use Case
Additional Lab and Coding data offer more details in standard exports.
Description
The standard export now includes the Lab Modifier and Drug Code when using the Raw export type. The Lab Modifier provides, for example, greater than or less than modifiers for lab values. The Drug Code shows as DrugCD in forms that use the WHODrug dictionary for medical coding. These changes will be highlighted with change detection for existing exports.
Enablement & Configuration
This feature is automatically available with the release.
Manual Refresh of Non-Production Review Listings 25R1.2
Use Case
To reduce the system processing for test studies that don’t need to be continuously refreshed, we removed the job that runs hourly to refresh review listings. Instead, users can refresh listings on demand in non-production study environments.
Description
This release introduces a new Refresh option for Review Listings in non-production study environments to allow study builders and testers to refresh the listing on demand. This will reduce the burden on the system of continuously running hourly jobs that are not needed, and speed up processing time for testers and study programmers to get a listing refreshed as needed, instead of waiting for the queue to process the listing
Enablement & Configuration
This feature is automatically available with the release.
Integrations
Features in this section are new integrations with Veeva Clinical Data or enhancements to existing integrations.
E2BLink: Study Drug Indication on Study Drug Safety Type 25R1.2
Use Case
The Indication as Reported by the Primary Source (G.k.7.r.1) captures the reporter’s description of the indication for the study drug use. While this might be a single value for all subjects in a study, or per subject, this new option allows the configuration for the indication to vary from dispense to dispense on the main study drug. If multiple values are used across the subject casebook, all will be included in the E2B XML.
Description
For E2BLink studies, from Studio > Form Configurations > Item Configuration, users can now map G.k.7.r.1 (Indication as Reported by the Primary Source) to an Item Definition on the Study Drug form type.
Enablement & Configuration
This feature is automatically enabled for studies using the E2BLink. Configuration for a live study might result in follow-up safety messages for existing safety cases.