We are pleased to bring you the following additions and enhancements to EDC & CDB Developer features in 25R3.
EDC API features added in 25R3 only affect API v25.3, unless otherwise specified.
Release Date: August 22, 2025, 25R2.2 Limited Release NEW
Four new endpoints allow you to manage protocol deviations in EDC via API.
You can retrieve:
You can create protocol deviations:
The Update Protocol Deviations endpoint supports full or partial updates to deviations.
The Inactivate Protocol Deviation endpoint inactivates with a specified change_reason or with the default, which is "Action performed via the API."
Release Date: August 22, 2025, 25R2.2 Limited Release UPDATE
To support the new configuration for study builders to set a minimum number of repeating forms, the following endpoints have been adjusted:
For any form in an event referenced by the Update Event or Set Event Date endpoints that has a minimum number of repeating forms configured, the first repeat of the form will now be automatically created for the event.
The Retrieve Form Definitions endpoints will now return the repeat_minimum parameter.
The CDE will be updated with the following new parameters for form_def:
* repeat_minimum (on schedule and form level)
* override_repeat_minimum (on schedule level)
* override_repeat_maximum (on schedule level)
Release Date: Oct 3, 2025, 25R2.3 Limited Release NEW
The following new vault-level endpoints allow you to manage vault-level jobs:
The respective endpoints show analogous behavior to study-specific job management endpoints, such as those used for listings or audit trail retrieval.
Additionally, EDC vault-level jobs can now be started with the Start Job (vault-level) endpoint using the user_access_report__vand user_training_report__v parameters:
User Access Report: The User Access Report (user_access_report__v) can be run for all or specific studies with a time window of a minimum of one hour to a maximum of six months.
User Training Report: The User Training Report (user_training_report__v) can be run for specific studies, with a time window of a minimum of one hour and a maximum of six months.
Release Date: Oct 2, 2025, 25R2.0.21 Maintenance Release NEW
In some cases, the Activate User - Vault(s) API endpoint can reactivate non-VeevaID site user accounts. This bypasses new validations that were implemented to ensure a consistent site user experience. In this release, we address this issue by updating the user activation logic and providing a new URL for the Activate User - Vault(s) API endpoint. This endpoint is the recommended method for activating inactive accounts for both site and sponsor users.
CDB API features added in 25R3 only affect API v25.3, unless otherwise specified.
Release Date: Oct 3, 2025, 25R2.3 Limited Release NEW
The new 25.3 version of the Study File Format (SFF) API allows customers to define if they want the system to generate the 1.0 or 2.0 SFF package version. Changes to the package version will require a new full SFF package generation. A study cannot use multiple versions at the same time but can change from one version to another.
It is possible to set the package version for all studies within the vault and then individually set a study to a different version if needed. If a package version is set for a study, this overrides the vault-level package version.
There are five new endpoints to support package versioning:
Currently, the difference between 1.0 and 2.0 is the inclusion of deduplicated columns in the 2.0 version. If an export does not want column deduplication, they can set the package generation to the 1.0 package version.
Release Date: Oct 3, 2025, 25R2.3 Limited Release UPDATE
Third-party data extracts included in the SFF will now populate the form last submit date in the SYS_FORMS CSV file. This feature ensures that the form last submit date in the SYS_FORMS CSV file is consistent with the clinical data for all third-party data extracts within the SFF.