New Features in 18R1.0.14: Codelist Item Values from Vault Custom Object Records and more...
Release Date: May 10, 2018
We are pleased to bring you the following new features in this week’s release. See details about each feature’s enablement below.
See Fixed Issues in the May 10 Release (18R1.0.14) for a list of issues fixed in this release.
Codelist Item Values from Vault Custom Object Records
Studio users can now control the Codelist Item values that display in a drop-down for an Item field based on records in a Vault custom object. This feature extends Vault EDC codelist capabilities with the availability of value options that are made available over the course of a Study, managed outside of study design and not fully predefined or fixed at the start.
The system now includes three EDC REST API endpoints for the purpose of integrating with other systems.
This action creates a new Subject in the specified Study Site. This endpoint initiates the same actions as when a user clicks the + New Casebook button in the Vault EDC UI, creating the new subject Casebook and the first Event Group (and its Events) in the casebook schedule.
Add Event Group
This action adds an Event Group to an existing subject Casebook. This action also adds the Events in the Planned status within the Event Group to the Casebook.
Set Event Date
The action adds a casebook Event and set the Event Date on the event. This action, like the in the Vault EDC UI, seeds all of the Form and Item (field) records below the Event. This action also initiates a run of the appropriate Review Plans. An integration user may also call this endpoint to change an Event Date and can pass an optional Reason for Change as part of the update.
Feature Enablement Details
|Codelist Items from Vault Custom Object Records
|1 In this release, this feature is visible only to Veeva Services.
See the following explanations for feature enablement options:
|Automatically activated and no configuration is required before using the feature; note that in some cases, a new feature is dependent on another feature that must be enabled or configured.
|Admins must turn on the feature with an Admin checkbox. Note that some “Auto-On” features have a checkbox setting that hides the feature; these will show “Auto-On.”
|Admins must configure the feature (separately from an Admin checkbox) before it is available to use or is active; for example, a Clinical Programmer must create an Item Definition of a certain new Item Type.
|On/off option controlled by Support.