Resolved 2 sorting issues in Data Central’s left navigation within the Data section's domain list:

• The domain list now properly sorts alphabetically based on whether the Domain Names or Domain Labels are displayed, as configured by the user in My Profile.
• The sorting method used now aligns with Mapper, prioritizing underscores before numbers.

Resolved 2 sorting issues in Exporter in the Group By:

• The list of Data Stores will now sort alphabetically.
• The list of Tags will now sort alphabetically.

Resolved 1 issue in Global Issues:

• The filter values under the Module column will now sort alphabetically.

Users were experiencing issues when attempting to query against domains that were mapped from one datastore to another and renamed in the process. Even in scenarios where the column to column domain structure was identical between the original and mapped data; an error would be received when trying to post the query back to EDC. For example: If a domain named AE was mapped from the Clinical datastore to a Safety datastore with a new name AE_Safety, it would not be queryable with the new name AE_Safety.

In order to resolve this, elluminate was enhanced to allow users to add a new column to the mapped domain named FormOID which will allow the user to specify the original name of the domain pre-mapping and allow querying for any fields that are identical in the original and mapped domain. This allows the query to be posted as though it were going back to the original domain in the EDC rather than from a mapped version of that same data.

Resolved an issue in Protocol Deviations where the comment count updated correctly, but not all associated comments were displayed as expected.

Users were experiencing issues where tasks were triggering an hour ahead of their set schedule. This was caused by tasks being scheduled prior to a Daylight Savings Time change where elluminate was adjusting the scheduled time to account for DST unnecessarily. This has been enhanced to better handle time offsets caused by DST changes for all user scheduled tasks.

Users can resolve any identical issues experienced following the deployment of this correction by updating the scheduling of their tasks, and re-saving those tasks to effectively reset the DST offsets causing the problem.

Resolved an issue in CTOA where audit related counts included previously cached records during incremental updates, causing incorrect counts.

Users were experiencing issues where Queries imported from Veeva CDMS was importing less queries than the total available within the EDC. This was caused by issues parsing paging parameters within Veeva CDMS EDC, elluminate has been enhanced to better handle the paging of queries in the target system, ensuring that all queries stored across all pages in EDC are imported as expected.

Resolved an issue where switching studies in Data Central using the study selector did not refresh the data in open panels, causing the prior study’s data to remain displayed.

Users with particular data configurations were experiencing issues where the related query information for domains that are outside of the Data Store configured to be the Related Forms Data Store were not displaying. This has been adjusted to allow these domains to appear as related info and allow query actions on domains that are not explicitly within the Related Forms Data Store.

Resolved an issue in the Graphical Patient Profile (GPP) within Data Central where decimal Min and Max values in the Normal range were rounded, causing an inaccurate interpretation of values falling outside the specified range. This fix ensures precise calculation and display of the range, preventing misclassification of out-of-range values.

Users were experiencing issues accessing the File Information associated with different folders and files stored in the elluminate eDrive. This was caused by the required permission controlling the access of File Information being a Write privilege instead of a Read privilege. This has been corrected to allow users to properly access eDrive File Information without needing a higher-level privilege.

Resolved the data discrepancies when linking investigators with their respective addresses, to ensure that investigators are now accurately linked to their respective addresses. This update enhances data integrity and improves system reliability.

Users were experiencing issues utilizing very large datasets (100,000+ records) in cases where there were numerous validation errors across the large breadth of data being validated. Running validator on these datasets was taking excessive amounts of time to process the data. To address this inefficiency, the processing and data validation error logging within the validator module has been enhanced to better handle these scenarios where potentially hundreds of thousands of errors caught in validation. Users should see better performance running validator against very large amounts of data with numerous issues based on the configured validation rules.

Resolved an issue in Data Central where docked charts were not automatically updating after being edited.

Resolved an issue that caused degrading performance in Listings and the Record Details panel when Data Variance was enabled. This fix addresses the slowness users experienced and optimizes performance as they interact with these features, ensuring faster loading times and a smoother experience.

Users were experiencing a limitation when trying to import data from Medidata Rave’s Lab Admin module that had been configured on their Rave EDC with a different name from the standard “LAB” domain name Rave prescribes. A new URL configuration option has been added to allow a list of custom Lab domain names that will then be importable through the existing Rave Biostats Gateway, allowing users to import these domains identically to all other EDC domains.

Fixed an issue in the Issues module where clicking on the header of the Opened By column, then selecting Filter, returned an empty unique value list.

Users were experiencing issues where the filter badges on domain panels in data central were displaying incorrect counts in scenarios where users had removed any default filters applied to those panels in DC then enabled a Data Cut. This has been corrected so filter badges on domains will respect all active filters and active data cuts on the relevant viewed or docked data.

Fixed an issue in the Record Details panel where column resizing was not retained after switching to different record.

Fixed an issue in listings where column resizing was not retained when navigating to the next page.

In the 24.1 version of elluminate, an enhanced CSV reader was implemented for higher throughput for importing delimited files. This also required enforcing of stricter CSV validation standards (RFC 4180) which has been causing issues for users who have CSV files with missing values and other validation errors that functioned in previous versions of elluminate. The importer has been updated to loosen the validation requirements for importing CSV files that have file structure issues that impact one or more rows, but not the entire dataset.

Users were experiencing issues when creating new user groups and denying nearly all data stores for that particular group. When saving the user group, a SQL limitation was experienced causing existing user groups and the newly configured group to no longer appear in the UI. This SQL issue has been corrected so users should no longer experience issues configuring user groups.

Resolved an issue where when a user’s profile settings were set to show Domain Labels, the right click Filter By Value option in the Issues panel on the Domain column returned no results.

Addressed an issue where users were getting an error exporting filtered subjects via the Workbook Patient Profile from the Subjects panel when filtering by the Subject, Site, or Status columns.

Users were experiencing issues importing SAS files throwing an error that the precision or scale of fields in the ingested file could not be converted to the SQL decimal type in elluminate. This was caused by unique scenarios where the actual precision of the SAS field didn’t exceed the defined precision in the metadata, but the number of digits to the left of the decimal point exceeds the allowed total field length based on the defined scale from that metadata.

The importer has been enhanced to take the actual number of digits to the left of the decimal point in addition to the scale to construct the actual precision to overwrite the incorrect number stored in the SAS metadata. Users should no longer run into issues with these unique scenarios caused by this metadata issue.

Users were experiencing issues with automated tasks being executed twice on their set schedule instead of the intended single execution. This was caused by a logging system receiving an error triggering a re-try for the executed task instead of the expected running status. The logging system then attempted a second attempt at task execution starting after the first task finished running causing the double run of the task.

Internal communication between elluminate and the logging system has been enhanced to handle these scenarios and prevent this incidental duplicate execution of tasks. Users should no longer experience this issue.

Users were experiencing unexpected errors while exporting data caused by the generation of temporary file storage locations to create the files to be exported in the selected format. These backend processes have been enhanced to ensure there are no issues producing files for export, users should no longer experience unexpected file pathing issues during exports.

Users were experiencing errors when importing Veeva CDMS queries caused by the message column in the query structure exceeding the elluminate field length limit. This field has been adjusted to accommodate the full length of Veeva CDMS Query messages, users should no longer experience issues with this error.

Fixed an error caused by invalid or incorrectly formatted dates in forms. Input validation is now in place to ensure the correct date format (e.g., MM/DD/YYYY), preventing errors when users enter incorrect formats through importer.

In ODR Forms, response time and performance has been enhanced, while saving and Updating the data within ODR forms which further resulting in faster interactions and improved performance in the overall ODR forms.

Users were experiencing issues where the configured start time was not being retained for scheduling configurations that included by-minute or by-hour intervals to execute the Automated Task. Enhanced the configuration so the start time should always be retained, users should no longer have issues with inaccurate scheduling of tasks.

Job Automation must be deployed with this fix.

When a data type change occured, Data Variance is triggered, indicating, on a record level in a listing, that there has been a change. However, when opening the Record Details, no indication was given to the user as to which field was changed. We’ve updated this behavior to show an Updated Since Reviewed icon (triangle with an exclamation mark inside) next to the field that had the data type change so the user can clearly see why the record was called out.

Enhanced handling for imported XPT files coming from older versions of SAS. XPT files from previous SAS versions had different structures that caused conflicts in the XPT reader used to ingest their data.

Users should no longer have issues import XPT files generated by older versions of the SAS platform.

Users were experiencing issues where changing aggregate functions from those that originally contained an ORDER BY clause to those that do not utilize an ORDER BY where the previous ORDER BY configuration was being retained on the new aggregate function selected.

Mapper has been enhanced to ensure consistency when updating existing programming for aggregate functions.

In order to accommodate a change in the data model underlying the Operational Insights module, the Operational Oversight analytics application had to be adjusted.
Prior to the data model change, Operational Oversight queried Protocol Deviation data from a particular set of tables in the model. After the change, the Protocol Deviation data was stored in a different set of tables and thus Operational Oversight had to be modified to reference these tables instead of the original ones.
The reason for the change to the data model was the organizing of Protocol Deviation data by Site rather than by Subject as not all deviations are associated with a subject. This change also required modifying the visual objects on the Protocol Deviations sheet of Operational Oversight to present data on a per-site rather than a per-subject basis.

Time tracking