Flex Databases Product Updates: EDC, IWRS & eCRF Builder Updates That Remove Manual Work From Study Teams

September 14, 2026

Every month, Flex Databases ships updates driven by real friction our clients run into on active studies. July’s release focuses on one theme in particular: removing manual, repetitive work that takes up study teams’ time and creates avoidable errors.

From protecting critical configurations to automating bulk data entry and site-specific workflows, these updates address everyday challenges for data managers, CRAs, and QA teams.

Custom Listing Access Control

What slows study teams down: A data manager spends time building a complex custom listing to reconcile serious adverse events, with dozens of carefully configured fields. The listing becomes a shared source of truth for the monitoring team. Then someone accidentally deletes it, thinking it is a personal draft.

The result? The team loses access to an important configuration, Support gets involved, and the data manager has to recreate work that was already completed. In a live study, even a simple configuration mistake can mean delays, rework, and unnecessary disruption.

How Flex Databases solves it: Shared listing configurations are now protected by default. Only the listing’s author and users with the Administrator role can edit or delete a shared configuration. Everyone else with access can view it and create their own independent copy, free to customize without any risk to the original.

✅ New role–level settings for Update/Delete Listings Configuration, defaulting to Administrator

✅ Any user can duplicate a shared listing into a fully independent, editable copy

✅ Edit/delete buttons are hidden for users without permission

✅ Every action logged in the Audit Trail

Email Recipient Groups

What slows study teams down: Setting up study notifications can mean repeatedly entering the same 15–20 recipients across multiple alerts. This is tedious at setup and becomes a maintenance problem throughout the study.

When a monitor joins the team, a contact changes, or responsibilities shift, someone has to find every affected notification and update it manually. Miss one, and the right person may not receive a critical study notification.

How Flex Databases solves it: Recipient lists can now be managed as reusable Email Recipient Groups. Build the group once, populate it with addresses and roles, then attach it to any notification. Update the group, and every linked notification updates automatically.

✅ Create, edit, duplicate, and delete recipient groups

✅ Combine specific email addresses and system roles in one group

✅ Automatic validation and blinding checks before adding recipients to unblinded notifications

✅ Full Audit Trail on every group change

Bulk Subject Import from Excel

What slows study teams down: Preparing test scenarios or setting up large amounts of study data can require registering hundreds of subjects manually through the interface. One subject at a time means hours of repetitive data entry and more opportunities for typos or inconsistent information.

For study teams working under tight timelines, this creates unnecessary operational work and increases the chance that test data will not match the intended study scenario.

How Flex Databases solves it: Subject View now supports bulk import via Excel. Upload a file, map columns to system fields, validate, and create subjects in bulk, with automatic checks on formats and required fields, and a detailed error report if something doesn’t match.

✅ Guided flow: upload, column mapping, data analysis, import confirmation

✅ Support for required fields (Select List, Screening #, Site #) and optional ones (Sex, Date of Birth)

✅ Automatic recognition of date formats and Cyrillic/Latin input

✅ Error grid at the analysis stage prevents partial imports of bad data

Site Local Time for IWRS Stamps

What slows study teams down: Multi-time-zone studies create a simple but recurring problem: timestamps need to make sense locally at each site.

Without built-in site time zone handling, teams may need custom UTC-to-local conversion logic for individual projects. As sites or time zone settings change, that logic can require updates and re-validation. A wrong conversion can lead to confusing records, reporting issues, and additional QA work.

How Flex Databases solves it: IWRS now includes a built-in Site Local Time parameter. Timestamps on drug assignment and randomization stamps automatically display in the site’s local time zone, with no manual conversion logic required.

✅ Available across all stamp types

✅ Strict conversion priority: site time zone → project time zone → UTC offset as fallback

✅ Automatic fallback with a logged warning if conversion fails, so the process never breaks

Site Metadata Management

What slows study teams down: Global studies need to manage site-specific information such as contact details, drug import requirements, time zones, and regional reporting requirements.

When this information lives across emails, spreadsheets, and separate configurations, keeping everything synchronized becomes difficult. A single change can require several manual updates – and if one is missed, the study team may be working with outdated information.

How Flex Databases solves it: eCRF Builder now includes a full Metadata module, providing a single configuration point for site attributes, with flexible edit modes, built-in notifications, and complete audit tracking.

✅ Three edit modes: Manual only, Manual and Checks, Checks only

✅ Create, edit, and deactivate metadata with unique-code validation and localization support

✅ Metadata can prefill form fields as default values

✅ Configurable email alerts on changes, with placeholder support

✅ Every change logged in the Audit Trail

Why it matters

These updates address a common source of friction in clinical studies: work that has to be done manually, repeatedly, and correctly every time.

For study teams, that means less time spent rebuilding configurations, updating the same information in multiple places, entering data one record at a time, or maintaining custom logic.

The result is simple: less rework, fewer opportunities for error, and more time for the work that actually moves the study forward.