New Features in 24R3 Limited Releases

24R3 Planned General Availability: November 30 & December 6, 2024

24R2.4   Release Date: October 18, 2024 

24R2.3   Release Date: September 27, 2024 

24R2.2   Release Date: August 23, 2024 

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.

CDMS

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

Support for CDMS Vault Domain Move 24R2.4

In this release, we’ve made updates to Vault EDC to support domain reparenting, which include:

• The ability to move DEV, TST, and PROD vaults from one domain to another
• Support for moving users from one domain to another through automating the creation of new users accounts (referencing the new domain) and locking/inactivating old accounts (referencing the previous domain).
• Ability to reassociate Vault functional records to the new user reference, including Enrollment Completion, Learning System users, Role associations, and Email group assignments. Other user references are left untouched by the process.

Use Case

CDMS Vaults can be moved to a different Vault domain to support various business needs such as Organizational rename or rebranding, business acquisitions, vendor or partnership changes, and others.

Enablement

Contact your Veeva Services representative to ask about reparenting.

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.

Undo SDV/DMR on Event, Form, and Item Group Reset 24R2.3

After this release, when the Reset action is performed, the SDV and DMR that was applied will be automatically set to false in cases where items have blank values. Previously, if SDV and DMR had been set on items that were left blank, the SDV and DMR had remained set as true when the site performed a reset action. As the sites re- entered data on the events, forms and items, then the SDV and DMR were automatically updated to false.

• Event Reset: the SDV/DMR is cleared from the Event Date and Visit Method
• Form Reset: the SDV/DMR is cleared from all items on that form
• Item Group Reset: the SDV/DMR is cleared from the items in that item group

Event and form data that is populated by APIs as external owned sources will remain, and therefore any SDV and DMR will also remain, unless the user clicks “Reset External Data Values”.

Use Case

This enhancement keeps reset behavior consistent for items with and without values, where the SDV/DMR will be set to false when the form is reset.

Enablement

This feature 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.

Direct Query Navigation Updates 24R2.2

Users will now be directed to the query location in Review when selecting the Query Name or Query Message (VV-#####) from within a report.

Use Case

CRAs and DMs can more easily navigate to queries from reports, allowing them to immediately take action on queries in Review.

Enablement

This feature is automatically available.

First Event SDV/DMR Completion Date 24R2.3

In this release, we’ve added additional new columns to the Event Progress Listing for First Event Review Date and implemented the following changes:

• First Event SDV Complete Date and First Event DMR Complete Date columns display the initial date when SDV/DMR is complete for all forms, event date, and visit method (where required). The value is a roll-up of Review State > First Review Date
• After being set, the First Event Review Date will not be updated if a review value changes, however, it will be cleared if the Event is reset
• The roll-up will be re-evaluated if review states are added, removed, or updated
• For studies where First Review Date is enabled, the First Event SDV/DMR Completed Date value will be backfilled for all events since the 23R3 release when First Review Date began being captured

Use Case

This update provides CRAs and other Review users the ability to see the date when SDV was first completed at an event.

Enablement

These updates are available for studies on Review Rollup V2 with First Review Date enabled.

More Granular Calculation for Query Caused Data Change 24R2.2

Previously, in rare cases, items were not included in the Query Caused Data Change field of the Query Detail Listing when data was changed within the same minute that the query was opened. The calculation now considers seconds when determining if the query caused the data to change, and more accurately reflects these cases within the listing.

Use Case

Evaluating the timing down to the level of seconds ensures a more granular and accurate inclusion of these cases within the listing.

Enablement

This feature is automatically available.

Synchronous Creation of Review States 24R2.3

This feature streamlines the creation of backend SDV and DMR records, creating them when an Item or Event is created. This change addresses past issues in which plan assignment was incomplete due to partial failure of the Reevaluate Plan Assignment job. With this release, if any part of the job fails, the entire job will fail.

Use Case

This update improves the user experience by preventing partial failures of the Reevaluate Plan Assignment job.

Enablement

Contact Veeva Support to enable this feature in the 24R2.3 limited release.

Show Blank Repeating Forms in the Review Tab 24R2.3

Prior to this release, Vault only showed repeating forms in the Review UI when data was present. With this release, the Review UI display will match the Data Entry display. An empty form icon will display, along with an indicator that no form instances exist. When selected, the form name will show in the right panel with an indication that there are no records to display.

Use Case

This feature provides clarity to CRAs and Data Managers by allowing them to see that a repeating form is available for the site to fill out.

Enablement

This change applies automatically.

Clinical Coding

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

Coder - Allow change of Dictionary Release & "Downversioning" 24R2.3

Coder now supports the ability to update the Dictionary Release field in Coder Tools > Study Settings even after code requests exist, as long as no coding has been completed. Additionally, Dictionaries can now be downversioned as well as upversioned. To support this change, display text in several areas (labels, email notifications, dialogs, etc.) has been updated to reference “Dictionary Versioning” when applicable for both Upversioning and Downversioning actions.

Use Case

Customers can now independently resolve issues related to selection of the wrong version or unintended upversioning.

Enablement

These updates are automatically available.

Coder - Allow Approve Mode from List View 24R2.3

Coder now supports the use of Approve Mode while in List View. When a Coder User switches to Approve Mode, the system will no longer auto filter to codes that are in the Pending Approval status. When a user approves a code request with the Apply to Synonym List option checked, any new synonym list detail records that are created will be in the Active status, without need for further approval.

Use Case

This feature provides code approvers with the option to use List View during the approval process, which provides additional context including Coded By, Notes, and Queries.

Enablement

These updates are automatically available.

Coder - Set Coding from External Suggestions 24R2.3

The external coding suggestions functionality is enhanced to allow direct coding of a verbatim from a posted suggestion. Using the API Set Coding Suggestions endpoint, one external suggestion source can be flagged to set coding. If the verbatim is neither excluded by the Do Not Autocode List nor already auto-coded from the Dictionary or Synonym List, the flagged suggestion will be used for auto-coding. To enable direct coding from an external suggestion for a study, the study must have Enable Approval Workflow set to Yes in Coder Tools > Study Settings. After the verbatim is autocoded with the applied external suggestion, the verbatim will have the status of Pending Approval, requiring review by a user. While this introduces significant efficiencies, the approval workflow is required to review AI-supported external coding to enforce regulatory compliance. Externally autocoded terms can be added to the synonym list, for further improvement to efficiency.

Use Case

External coding suggestions received via API can now be used as a first-line coding solution.

Enablement

These updates are automatically available.

Coder - Dictionary Versioning Impact Report Enhancements 24R2.2

This release introduces several enhancements to the Impact report available when dictionary versions and Synonym Lists are updated. Changes include:

• A Study column has been added to the Form Impact report.
• Highlighting and text formatting have been added to identify each cell that changed in the source (red, italicized) and target (green, bolded) release.
• Translations have been added for all Impact Report Column Header labels and the Summary tab.

Use Case

These updates improve usability and readability.

Enablement

These updates are automatically available.

Study Design & Configuration

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

Blank CRF Update for Repeating Item Groups 24R2.3

When generating the Blank CRF from Studio, only one copy of the repeating Item Group will be created in cases where there is no default configured for the Item Group.

Use Case

Previously, when generating the Blank CRF, any repeating item group that had no defaults configured showed five copies of the item group. Showing one instance of the item group helps reduce confusion around how repeating item groups with no defaults display within the Blank CRF, providing a more clear and concise rendition.

Enablement

This feature is automatically enabled for new studies only.

Compress and Flatten PDFs 24R2.3

There is now a reduction in file size when generating the Blank and Annotated PDFs from Studio. PDFs have been optimized in order to reduce file sizes by approximately 20-30%. The reduction in the PDF file size will vary per study.

Use Case

This feature helps customers who are merging or copying pages from multiple PDFs by minimizing the file size for both the zip and the extracted files, which helps with overall performance.

Enablement

This feature is automatically available.

Extract Enhancements: Queries in User Language 24R2.2

We’ve added columns that show the translated value of query text to the following extracts to support the Queries in User Language feature released in 24R2:

• Query Detail Listing Report v2 Template
• Query Detail Listing
• SDE SYS_Q and SYS_QT data sets

Use Case

This feature provides the user with translated query text in data extracts and reports.

Enablement

This feature is automatically available.

Learn More

• Study Data Extracts
• Job Types for Study Administrators

Item Default Length for Codelists 24R2.2

When creating an Item or changing an Item Type to a Codelist data type in Studio, the length of the Item will default to 100. If required, the item length can be further revised to reduce or expand the item length per the values from the codelist.

Use Case

The default item length has been made smaller to reduce the character lengths during the design of the study while still providing flexibility for designers to adjust the item length as needed.

Enablement

This feature is automatically available.

Studio Medical Coding Improvements 24R2.3

When utilizing the study copying functionalities or running difference reports in Studio, Vault will ignore Medical Coding definition records that have been deleted or inactivated.

Use Case

Previously, medical coding configuration that was set to inactive or deleted caused errors when performing study copy actions or generating a difference report. This update helps to prevent errors during new study setup.

Enablement

This feature is automatically available.

Study Administration

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

Data Extract Job Enhancements 24R2.2

We’ve added an error message to the Core Listings job log when a Form is deleted or changed to Restricted for scheduled jobs.

Use Case

This error provides actionable information to the user as to why a scheduled job might fail, and how to address the issue.

Enablement

This feature is automatically available.

Deployment Date Added to Vault and Study Deployment History File Name 24R2.2

The timestamp of the deployment date is included in the file name when the File and Log are downloaded from the Vault Deployment or Study Deployment History pages.

Use Case

This change makes it easier for users to identify which deployment downloaded Files and Logs are from.

Enablement

This feature is automatically available.

EDC Numeric Value Conversions 24R2.3

This release includes two updates to numeric value formatting and conversions to support EDC data ingestion to CDB and Clinical Reporting:

• When full-width numeric characters are entered into EDC, they will be converted to half-width numeric characters when the data is saved.
• Scientific notation is not a supported format for EDC number fields. We have added a validation in data entry to not allow scientific notation.

Use Case

The entry of full-width numeric characters into EDC causes ingestion errors for downstream systems that can’t ingest the embedded style of these characters. Downstream systems can expand numbers in scientific notation to the full value upon ingestion which doesn’t conform to the configured length and precision for items. The transformations and validation introduced by this update prevent errors downstream caused by unsupported data.

Enablement

These updates are automatically available for studies using Data Model 2.

EDC Study Progress Listing Enhancements 24R2.2

We’ve made the following changes to non-versioned study progress listings:

Event Progress Listing:

• Added new columns to track Event-level SDV/DMR Required, Complete, Complete Date, and % Complete. These values will be blank for log events and will only populate for studies using Review Rollup V2
• Relabeled existing column for Event SDV/DMR Completion Date to Forms SDV/DMR Completion Date, as these columns only take forms into account.
• Added a new column for Marked for Removal

Subject Progress Listing:

• Added new columns for Subject SDV/DMR required & complete. These values will only populate for studies using Review Rollup V2.
• Relabeled columns for SDV/DMR Complete to Subject SDV/DMR Complete. Additionally, the logic for these columns has been updated to use the Casebook Operational Summary instead of calculating from other columns in the listing.
• For studies using Review Rollup V2, we have updated the logic for displaying the Frozen, Locked, and Signed columns

Form Progress Listing:

• Added a new column for Marked for Removal

Use Case

These enhancements improve the usability of study progress listings.

Enablement

This feature is automatically available.

Learn More

• Job Types for Study Administrators

Job Selections Retained After Validation Error 24R2.2

If a validation error occurs when a scheduled job is initially saved, the selections are no longer cleared out prior to saving, allowing the user to adjust the settings.

Use Case

This change makes it easier to correct selections when saving scheduled jobs.

Enablement

This feature is automatically available.

Copy to PPT Job Does Not Include Signature History 24R2.2

When data is copied to Post Production Test (PPT) environments, Signature History records will no longer be included as part of the copy operation.

Use Case

This change excludes records from the copy to PPT operation that could cause the job to fail.

Enablement

This feature is automatically available.

Rules Enhancements: Show Sequence Numbers in EDC Tools 24R2.3

Sequence numbers in rule actions that pertain to specific instances of repeating Event Groups, Forms, and Item Groups are now displayed in the dialog when viewing rule details in EDC Tools.

Use Case

Sequence numbers were not previously displayed in EDC Tools. Sequence numbers provide users clarity on how a rule operates when viewing rules and managing rule jobs in EDC Tools.

Enablement

These feature is automatically available.

Enhanced Options when Running User Reports 24R2.2

The following enhancements have been added for User Reports:

• A date picker has been added as an option when running the User Training Report, allowing users to select a range for the ‘Date Assigned to Study’ values in the report.

• When “Select Studies” is chosen while running the User Training, User Access, and User Activity reports, the selected studies are displayed in alphabetical order.

Use Case

These enhancements provide additional selections and usability improvements with the User Reports.

Enablement

These updates are automatically available.

Vault Configuration Report File Name Update 24R2.2

The format of the file name has been updated when running the Vault Configuration Report. It now includes the Vault name. The new format is as follows:

Vault_Configuration_Report_$VaultName_$Date-$Time-$TzAbbr.xlsx

Use Case

Including the Vault Name in the file name provides clarity on which Vault this report was generated.

Enablement

These updates are automatically available.

Vault Level FTP Connections Configuration 24R2.3

We’ve added a new page for FTP Connections in System Tools that allows Vault Administrators to create connections to FTP servers that can be used by all studies. In EDC Tools, Vault-level connections will appear as a new group so that the connection can be utilized by a study job. When defining an export from EDC Tools, a new section in the dropdown will show available study and vault connections.

Use Case

This feature allows external connections for exports to be defined in one location, with one username and password to update if needed, and can be accessed by all studies on the vault.

Enablement

This feature is automatically available and can be configured in System Tools.

Labs

Features in this section are new features for the Labs module of Vault EDC.

Labs: Hide Analyte Functionality 24R2.3

Users can now hide analytes in the Analyte Library in DEV to prevent an analyte from being selected in future Lab Panel configurations. Existing uses of the hidden analyte are not impacted and can continue collecting data. As part of this update, the Analyte Library export has been updated to include the Analyte Status. This column will be ignored if used in an analyte import.

Use Case

This update provides sponsors with additional flexibility to prevent future use of an analyte. Previously, analytes could only be archived, which is not supported once an analyte is in use.

Enablement

This update requires enablement by Veeva Support for limited releases, but will be immediately available in 24R3 general release. The Analyte Library export update is immediately available with the release of 24R2.2.

Learn More

• Managing Analytes, Units, & Codelists

Clinical DataBase (CDB)

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

Listings Enhancements for Builder and Grid 24R2.3

Listings in CDB Workbench and Clinical Reporting have been updated with the following enhancements:

• In the Listing Builder, codelist items now have the option to include the decoded value.
• When multiple items with the same name are included in a listing, the item group name has been added to the display in the Listing Builder Columns section to provide clarification of where each item is used.
• New options have been added to filter using Not In functions for text and numeric data types. These options are available in both the Listing Builder and the listing grid display.

Use Case

These updates provide additional information to include in a listing, or to help when defining a union with identical item names.

Enablement

These enhancements are automatically enabled.

Learn More

• Creating Listings, Checks & Views with the Listing Builder
• Creating Custom Listings
• Clinical Query Language (CQL) Reference

Display Indicators for Disabled Review Listings 24R2.2

For long-running Review Listings that have been disabled, we added additional indicators:

• In a Review Listing, we added iconography to show if the listing is disabled or at risk of becoming disabled.
• In the Review tab, we added review warning icons.
• On the dashboard, we moved the warning to the left of the Review Listing title.
• On the dashboard, we added quick filters for review listings that are disabled or at risk of becoming disabled.

Use Case

Improved visibility to review listings that are disabled or at risk of becoming disabled enables users to more quickly identify these long running listings and take action to improve the performance of the listing.

Enablement

This feature is enabled automatically.

Learn More

• Review Dashboard
• Review Listings

New Columns for Sys_Events, Sys_Forms & Sys_ILB Call Functions 24R2.2

With this release, we’ve added new columns to the following CALL functions:

• Sys_Events:
  • Study.Label
  • Site.CountryName
  • EventGroup.Label
  • EventGroup.ExternalID
  • Event.Label
  • Event.ExternalID
  • Event.VisitMethod
  • Event.PlannedDate
  • Event.EventDateModifiedDate
  • Casebook.Version
  • Event.ChangeReason
  • Event.WindowStatus
  • Event.DaysOutsideWindow
  • Event.ExpectedForms
  • Event.FormEntryOverdue
  • Event.Frozen
  • Event.FrozenDate
  • Event.Locked
  • Event.LockedDate
  • Event.Signed
  • Event.SignedDate
• Sys_Forms:
  • Study.Label
  • Site.CountryName
  • EventGroup.Label
  • EventGroup.ExternalID
  • Event.Label
  • Event.ExternalID
  • Form.Label
  • Form.FirstSubmissionDate
  • Form.SDVOverridePlan
  • Form.SDVCompleted
  • Form.FirstSDVDate
  • Form.SDVLastModifiedDate
  • Form.SubmitToSDV
  • Form.DMROverridePLan
  • Form.DMRCompleted
  • Form.FirstDMRDate
  • Form.DMRLastModifiedDate
  • Form.SubmitToDMR
  • Form.SubmitToFrozen
  • Form.SubmitToLocked
  • Form.SubmitToSign
  • Form.EventToSubmit
• Sys_ILB:
  • Study.Label
  • Site.CountryName
  • EventGroup.Label
  • EventGroup.ExternalID
  • Event.Label
  • Event.ExternalID
  • Form.Label
  • Form.ExternalID
  • ItemGroup.Label
  • ItemGroup.ExternalID
  • Item.Label
  • Item.ExternalID
  • LABANALYTENAME

Enablement

These changes apply automatically.

Learn More

• Exporting Data

Query Listing Usability Improvements 24R2.2

Query Listings in Clinical Reporting and CDB Workbench now support data type aware filters:

• Created on and modified on columns display a calendar in the filter
• Boolean (e.g., True/False or Yes/No) types show the options in a picklist

Use Case

Improved filter options makes it easier for a user to select the data they wish to view.

Enablement

This feature is enabled automatically.

Export Enhancements 24R2.3

Exports from CDB Workbench and Clinical Reporting have been updated with the following new features:

• New columns have been added to listings of the Raw export type to show the decoded value for codelist items.
• System (SYS) Listings can now be added to an export of type None.
• A new group has been added to the Select Listings shuttle for SYS listings under Raw export types. If these listings are removed from the definition, they will appear as Available Listings.

Use Case

Additional export options provide flexibility in determining which export type is best for your downstream systems.

Enablement

This feature is automatically available to Export Listings. Existing scheduled exports of Raw type will not have the new decode columns included, these will only be added to new or modified export definitions. Existing None or Raw type scheduled exports will need to be updated to include or remove any System Listings.

Learn More

• Exporting Data (CDB)
• Exporting Data (Clinical Reporting)

Study File Format 24R2.4

The Study File Format (SFF) export option provides data in an easy to consume format for downstream systems. It includes a manifest file that defines the data and a series of CSV files. SFF takes advantage of the Vault Direct Data API, allowing access to incremental packages if licensed.

The SFF API Access permission provides access to the new SFF API endpoints generated by CDB. By default, this permission is assigned to the CDMS Super User role.

For CDB customers, third-party data is available in the full extract but not in incremental loads.

Use Case

SFF allows users to keep their downstream systems in sync with data that is available through 15 minute incremental exports of EDC data.

Enablement

Enable SFF by Study in EDC Tools. This feature is only available to production environments. Incremental data export requires a special license, contact Veeva Support for more information.

Third Party & OpenEDC Strict Manifest 24R2.3

A new optional parameter in the manifest .json file and manifest builder allow customers and third party data providers to restrict data ingested into CDB to only those items that are defined in the manifest. Previously, any items not defined were ingested as text fields, and all fields were ingested when included in the CSV file. Using a strict manifest setting for either the entire package, or for individual CSV files included in the package, the system will restrict the columns for import to only those defined. File level settings will override the package level setting for strict manifest.

Use Case

This feature ensures that only defined data is ingested into CDB.

Enablement

This feature is automatically available, and it does not require any changes to existing manifest files unless users want to incorporate the strict manifest concept.

Show Date for Dashboard & CPT Refresh Times 24R2.3

In the Workbench Review Dashboard and Clean Patient Tracker, the date has been added to the refresh time, to better show when the data was refreshed.

Use Case

Adding the date ensures that if something has not refreshed for a long period of time, it is clear to the end user that a support investigation is needed.

Enablement

This feature is automatically available.

Third Party Data Import Enhancements 24R2.3

Third party data import now supports these additional date time formats:

Rejected third party import packages will now display in the audit log.

Use Case

Additional datetime formats support external system output that no longer needs to be transformed before being ingested into CDB.

Enablement

This feature is enabled automatically.

New Standard Study Roles for CDB 24R2.3

This release provides two new standard roles to support CDB processes: CDMS CDB Programmer and CDMS CDB Read Only. The CDB Programmer role is designed to be used in Workbench in both Production and Test environments. Used alone in Production, the role cannot modify public listings, checks, or views, but can test production data using private listings. This provides greater control in the Production environment and avoids accidental updates to deployed listings. In a TST study environment, provide the user with the CDB Programmer role and CDMS Lead Data Manager (if Restricted data access is needed) or CDMS Data Manager to allow them to create and deploy Public listings, views, and checks. In both environments, the user can set up scheduled exports, manage key mappings of third party data, and access CDB Tools. CDB Read Only can access both the Workbench and Clinical Reporting applications, allowing a user to view listings, and import and export information, but without the ability to create or mark listings as reviewed, to create queries, or to create export definitions.

Use Case

New standard roles allow customers to reduce the number of custom roles they need to create, and reduce the testing burden with each release. Standard roles are validated, and new permissions may be added as new functionality is incorporated into the application.

Enablement

These new roles are available to be assigned to users after the release.

Role Management & Security

Features in this section are enhancements to the System Tools > Role Management and System Tools > Users areas, as well as changes to standard Study Roles, security, and access control in Vault CDMS.

UI Updates to Role Management 24R2.2

The following improvements have been made to the Role Management area:

• The CDMS Auditor Read Only role now has the View Query permission checked which was inherently part of the View Casebook permission and needed to view query data in the Query Detail Listing report.
• By default, the Role Management page in System Tools has all groups expanded.
• When expanding or collapsing role groups, the state of the groups is remembered in the UI.
• Hovering over a row, column or cell within the Role Management grid will highlight that row, column, or role/permission intersection.
• The “Number of Users” label has been changed to “Number of User Assignments” to better describe the information contained therein
• The “User Assignments” dialog now contains all applicable user assignments, regardless of whether the user’s study access is enabled or not.

Use Case

These enhancements improve usability to provide a better user experience.

Enablement

These updates are automatically available.

Integrations

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

Clinical Operations-EDC Connection: Manual Data Refresh 24R2.3

To support the management of the Clinical Operations-EDC Connection, EDC Vault Owners can now manually trigger an integration refresh. A new Rerun Integration menu option will be available in Admin > Connections > User Exception Messages. Triggering the rerun will re-sync EDC with CTMS data on demand, as if a change had been made in CTMS that would have automatically triggered the refresh. This feature includes a corresponding functionality in CTMS at the User Exception Message level, allowing the reprocessing of a Study Refresh Request.

Use Case

Users will be able to correct issues in EDC that are causing errors with the Connection, such as a mapping issue for Country or Site. They can then immediately resolve discrepancies, preventing potential downstream issues.

Enablement

This feature is automatically enabled for studies using the Clinical Operations-EDC Connection.

Learn More

• Refresh the Connection

Clinical Operations-EDC Connection: Automatically Match Countries by Country Code 24R2.3

The country mapping of the Clinical Operations-EDC Connection now leverages the standardized country codes across Vaults. Manual country mappings between CTMS and EDC will remain intact for existing connections and can still be used to override auto-mapping. The new functionality is recommended for establishing new connections and adding countries to existing setups.

Use Case

The auto-mapping of countries using the Vault-wide country code significantly reduces the effort involved in connection setup across environments and lowers the risk of potential discrepancies.

Enablement

This feature is automatically enabled for studies using the Clinical Operations-EDC Connection.

Learn More

• Mapping the Country Object

E2B Link: Safety Case ID from ACK file in EDC UI 24R2.3

With the release of the Safety Case Banner, site users receive feedback on their submitted safety cases directly on the adverse event form, including the CDMS case ID and the Last Send datetime. The information will now be supplemented also for the E2B Link with the Safety Case ID as returned with B.r.7 from the ACK file. If available, the exact text from B.r.7 will be extracted and presented as Safety Case ID in the Safety Case Banner to EDC users with the “View Safety Case” permission. Note, no other text from the ACK file can be inserted as Safety Case ID.

Use Case

While the Safety-EDC Connection was built to back-propagate the Safety Case ID from Vault Safety to Vault EDC, external Safety systems do not natively allow for this. By using the information from the ACK file, we now also enable the E2B Link to display the Safety Case ID to Site users, and ease communication with Sponsor personnel on safety information.

Enablement

This feature is automatically enabled for studies using the E2B Link.

Safety-EDC Connection: Multi-Vault Support 24R2.3

The Safety-EDC Connection can now be established between one Vault Safety and multiple Vault EDC while they are hosted on the same Domain. The interchange of information between Vault Safety and each Vault EDC will be restricted to only those records that belong to the respective Vault EDC. Safety cases are identified in Vault Safety and attributed to the appropriate Source Vault EDC for Safety Case management.

Use Case

A single Vault Safety might be used to manage data from several different EDC systems. To increasingly use the efficiencies of Vault Safety, the Safety-EDC Connection can now be established from one Vault Safety to one or more Vault EDC instances. The information is marked with the EDC source and can be managed accordingly in Vault Safety.

Enablement

Contact Veeva Support to enable this feature.

E2B Link: NullFlavor for Name, Source and Method of Study Drug, and Additional Document Availability 24R2.3

For E2B Link studies, the Safety Settings in Studio have been additionally expanded to include the following settings and functionality:

• The Name or Initials nullFlavor (D.1) can now be specified as MSK, ASKU, NASK or UNK. Not asked (NASK) will be set automatically as the new default for new studies.

• The Source of Study Drug Assessment (G.k.9.i.2.r.1) and Method of Study Drug Assessment (G.k.9.i.2.r.2) can now be added as a static value. Any set value will appear in the E2B XML together with the Result of the Assessment (G.k.9.i.2.r.3), which can be mapped on the Study Drug or Concomitant Medications Form Types.

• Additionally, the indication for Additional Document Availability (C.1.6.1) will now be transferred as “false” with every new Safety message without causing Follow-Up sends for any Safety Case of live studies.

Use Case

Expanding the general Safety Settings and the standard data transfer options for E2B Link studies complements the information that is sent to the Safety system and thereby reduces the burden for Safety users to manually set these values for each incoming Safety Case.

Enablement

This feature is automatically enabled for studies using the E2B Link. Note: When modifying any Safety Settings the default Name or Initials nullFlavor (D.1) will be a required field. Saving the new nullFlavour default or adding Source/Method of Study Drug Assessment for a live study will result in Follow-Up Safety Messages for all existing Safety Cases.

Safety Integrations: Details of the Reporter as Primary Source of Information 24R2.3

In the Safety Settings in Studio, “Principal Investigator Only” (previously “Principal Investigator”) or “Full Site Information” can now be chosen as Reporter. Accordingly, either the Principal Investigator Name and Country only or now additionally Organization (C.2.r.2.1), Address Lines (C.2.r.2.3), City (C.2.r.2.4), State (C.2.r.2.5), and Postal Code (C.2.r.2.6) of the initial reporter are transferred with each Safety message. For all new Safety Cases after 24R3, the Reporter information will be marked as unchangeable for all Safety Messages after the first send for both the Safety-EDC Connection as well as the E2B Link. If changes to erroneous Reporter details are required after the first send, please contact Veeva Support. For the Safety-EDC Connection the transfer will prioritize any Reporter information that is mapped for the Adverse Event Form Type to Adverse Event form items. When using the Adverse Event Form Type mapping, the Connection additionally allows the transfer of Email and Phone number.

Use Case

Entering site information for each safety case when reporting an adverse event is burdensome for the site. Maintaining this information in EDC and submitting it automatically with each case will reduce redundant work and improve the data quality. Additionally, keeping the information of the first reporter in place will ease compliance with regulatory requirements.

Enablement

This feature is automatically enabled for studies using the Safety-EDC Connection or E2B Link. Note: Configuration for a live study might result in Follow-Up Safety Messages for existing Safety Cases.

E2B Link: Standardized EDC Data Transfer via Reporter or Sender Comment 24R2.3

Sending data from EDC to a 3rd party Safety system is based on the transfer of E2B XML files. The E2B format has limitations in regards to the data fields and formats that can be sent from EDC to a Safety system (e.g. Cohort or Toxicity Grade). This information might, however, be critical for the Safety team to assess a Safety case. To overcome the E2B restrictions, we now offer the mapping of EDC items to the Reporter Comments (H.2) or Sender Comments (H.4) field in the E2B XML. The values of the selected items for mapping will be added and listed as Notes in a standardized way to either Comment field, and appended to any actual Reporter or Sender Comments text. The setup is identical and similarly straightforward as for the general Safety Form Types. The new configuration options will be reflected in the SDS.

Use Case

Not all safety-relevant EDC data can be transferred to a Safety system when using the E2B format. Adding this EDC information in a standardized way to the Report or Sender Comment field will support the transfer of non-E2B data values and reduce the need for the Safety team to access EDC data by other means than the E2B Link.

Enablement

This feature is automatically enabled for studies using the E2B Link. Note: Configuration for a live study might result in Follow-Up Safety Messages for existing Safety Cases.

Safety-EDC Connection: Severity 24R2.3

For the Safety-EDC Connection, Severity was added as a new standard field for mapping on the Adverse Event Form Type.

Use Case

Expanding the set of standard fields for mapping from Vault EDC to Vault Safety further increases the ease of use of the Safety-EDC Connection.

Enablement

This feature is automatically enabled for studies using the Safety-EDC Connection. Note: Configuration for a live study might result in Follow-Up Safety Messages for existing Safety Cases.

Safety Integrations: Study Drug information by Subject Group 24R2.3

The inclusion of study drug information into a Safety Case can now be based on Subject Groups. When configuring the Study Drug Form Type and mapping to the respective study drug exposure forms in EDC, the ‘Only Include When Subject Group is’ setting can be used as a new filter for study drug data inclusion into the Safety Case.

Use Case

For studies using Arms, Cohorts and Substudies, usually multiple drug exposure forms are being configured to cover all study drugs. While subjects are never exposed to a subset of those study drugs, the respective information will still be transferred as “Drug Not Administered”. With the option to select Study Group-specific information for transfer, only the relevant drug exposure information for the given subject will be added to the Safety Case

Enablement

This feature is automatically enabled for studies using the Safety-EDC Connection or E2B Link. Note: Configuration for a live study might result in Follow-Up Safety Messages for existing Safety Cases.

E2B Link: Study Drug Indication & Pharmaceutical Dose Form 24R2.3

On the Study Drug Form Type, a Study Drug Indication can now be either specified as a static value or mapped to an item value. The static value will be applied to all Safety Cases in the study. The mapped item must be unique in the subject’s casebook and will be transferred for all Safety Cases of the subject. Pharmaceutical Dose Form (G.k.4.r.9.1) is now available for mapping on the Concomitant Medications Safety Form Type.

Use Case

Expanding the set of configurable and mappable fields on Safety Form Types increases the flexibility to transfer EDC data using the E2B Link.

Enablement

This feature is automatically enabled for studies using the E2B Link. Note: Configuration for a live study might result in Follow-Up Safety Messages for existing Safety Cases.

Safety Integrations: Study Type of Reaction & Medical Confirmation by Healthcare Professionals 24R2.3

The Safety Settings in Studio for both Safety-EDC Connection and E2B Link studies have been expanded to include the following settings and functionality. The Study Type of the Reaction (C.5.4) can now be specified as “Clinical trials”, “Individual patient use” or “Other studies”. “Clinical trials” will be set automatically as the new default without causing Follow-Up sends for any Safety Case of live studies. The Auto Set Medically Confirmed will determine the inclusion of the Medical Confirmation by Healthcare Professionals (E.i.8). “No” will be set automatically as the new default, omitting this addition to the Safety Message and not causing Follow-Up sends for any Safety Case of live studies.

Use Case

Expanding the general Safety Settings and the standard data transfer options for studies using the EDC Safety integration complements the information that is sent to the Safety system and thereby reduces the burden for Safety users to manually set these values for each incoming Safety Case.

Enablement

This feature is automatically enabled for studies using the Safety-EDC Connection or E2B Link. Note: Changing the default Study Type (C.5.4) or the Auto Set Medically Confirmed setting for a live study will result in Follow-Up Safety Messages for all existing Safety Cases.

Developer Features

The following are new features for the CDMS API. See our CDMS Developer Portal's release notes for more detailed feature information (click Beta from the release note drop-down for LR notes).

CDMS API Features 24R2.3 24R2.4

This release includes the following features for CDMS developers:

• Retrieve Event Definitions
• Retrieve Event Group Definitions
• Set Coding Suggestions

CDB Developer Features

The following are new features for the CDB API. See our CDMS Developer Portal's release notes for more detailed feature information (click Beta from the release note drop-down for LR notes).

CDB API Features 24R2.2 24R2.3 24R2.4

This release includes the following features for CDB developers:

• CDB Query Source
• Batch Limit for Open Query on Item API
• Return Individual Failures for CDB API Calls

Migration Vault

Features in this section are new features for Migration Vault.

Migration Vault: YAML Builder Enhancements 24R2.3

When a migration user initiates the YAML Builder job, Migration Vault will now:

• Create a new transformer selector for submitting Forms and Events with Visit Methods
• Create a new transformer selector for Events with Visit Methods
• Insert mappings for Lab Panel data within the form YAML
• Create YAML files for the study’s Event Groups and Events
• Create YAML files specific to Studies designed in Studio
• Create a YAML template for Events marked as Did Not Occur (DNO)

Use Case

These enhancements increase efficiency by automating tasks that used to be manually created.

Enablement

These enhancements are immediately available.

Learn More

• YAML Builder 

Applying Frozen & Locked Statuses to Event Dates & Visit Methods 24R2.2

In order to support the migration of visit methods, Migration Vault now allows configuration specialists to apply the Frozen and Locked statuses to Event Dates and Visit Methods.

The “attributes.csv” file now has a “field” column, which configuration specialists can use to indicate if the status should be applied to an Event Date (event_date) or Visit Method (visit_method). This field should be left blank if the attribute should be applied to both the Event Date and Visit Method. These statuses are now also applied when an ancestor object, such as a casebook, has the status applied.

Use Case

This enhancement provides support for Visit Method within Migration Vault.

Enablement

This feature is immediately available.

Learn More

• Migrating Data Attributes 

Migration Vault: Migrate Closed Queries 24R2.3

With this release, Migration Vault has been updated to ingest and migrate closed queries into CDMS. Upon ingestion, these queries remain in the closed state.

Use Case

Previously, any queries in the closed status were reopened upon ingestion, requiring users to review and reclose them.

Enablement

This feature is immediately available.

Learn More

• Migrating Queries