Back to Media
Industry Insights

eCRF build tools for clinical trials in 2026: form designers, eSource and protocol-to-EDC generation compared

Zach Sawaged6 min read

Search for an eCRF build tool or an eSource build tool and the results mix four kinds of product: EDC form designers, metadata and standards platforms, eSource capture systems, and protocol-to-EDC generators. They sit at different points in study startup and most teams are shopping for one of them without knowing the others exist. Here is how the categories differ, with the tools named and what each vendor says its product does.

EDC form designers

Every electronic data capture system ships with a way to build its forms. REDCap uses an Online Designer and an Excel data dictionary that can be uploaded to define instruments. Castor offers a low-code eCRF builder with pre-built validated templates. OpenClinica has a drag-and-drop Study Designer and a library of CDASH-based CRF templates. Viedoc Designer is a browser-based drag-and-drop tool built on CDISC ODM. Medidata Rave EDC has Architect and, more recently, Designer. Veeva EDC has an in-product specification studio.

In every case a data manager or study builder reads the protocol, decides which forms and fields each visit needs, builds them, writes the edit checks and tests the result. The tool determines how fast a skilled person can build; it does not remove the person from the loop. Vendor figures for a build range from days for a simple study to the 8 to 12 weeks Viedoc quotes for a professional-services build.

Metadata and standards platforms

A clinical metadata repository holds an organization's standard forms, variables and controlled terminology so that studies are assembled from governed, reusable content rather than built fresh. Certara's Pinnacle 21 Enterprise, which absorbed Formedix, is the clearest example: its CRF Creator builds study files for Rave and Veeva from library metadata, and the platform carries CDASH, SDTM and Define.xml automation with it.

These platforms make a sponsor's builds consistent and submission-ready. They are still driven by a person selecting content from a library. The protocol document itself is not the input.

eSource capture systems

An eSource system is not a build tool at all, although it appears in the same searches. RealTime eSource, Jeeva eSource and Wemedoo's oomnia eSource replace paper source documents with electronic forms that coordinators fill in at the point of care, with edit checks, e-signatures and an audit trail, and then transfer the data to the EDC. By each vendor's own description, the visit templates in these systems are configured to the protocol by the site or the vendor. Jeeva describes visit-specific forms built to your protocol schedule and configured in days. RealTime describes protocol-specific templates built out in the eSource template.

eSource changes where the data is first recorded. It does not change how the forms are created. Someone still turns the schedule of assessments into a set of forms, in the eSource system and again in the EDC.

Protocol-to-EDC generators

A protocol-to-EDC generator takes the finished protocol and produces the study build from it. Several products now make this claim, and they differ in what they output and where it lands.

Lifio's Clinical Study Automation Tool reads the protocol with NLP and generates eCRF specifications, edit check specifications and SDTM mappings, exported as a Rave ALS or an Oracle InForm CSML file for a data manager to load. Clincove's Protocol AI generates CDASH-aligned forms and edit checks inside Clincove's own platform; the vendor reports roughly 80% of CRF content generated accurately from the protocol, with the remainder handled by data managers. Harbor's Magic Build produces a draft database build in its own EDC from a protocol PDF. Marvin EDC generates forms, item groups and fields from an uploaded protocol for review inside Marvin. Medidata's Designer adds AI that translates study plans into forms and edit-check logic for Rave. Veeva announced a Study Builder Agent in September 2026 that configures Veeva EDC from a protocol using CDISC USDM, with early-adopter availability planned for December 2026.

The pattern across all of them is that the protocol is parsed once and forms are generated for a specific EDC, with a person reviewing before anything goes to production. The differences are which EDC the build lands in, whether the output is a live study or a specification, and whether the same model also feeds the site's other startup documents.

Concordare's approach is built for the second question. Apta, its conversion engine, reads the protocol PDF and converts it into the Clinical Trial Protocol Model (CTPM), a structured model of every visit, procedure, eligibility criterion, lab panel and assessment. The study team reviews and approves the model. Porta, Concordare's connector, then builds the EDC forms, fields and edit checks in the system the site already uses, starting with REDCap, in minutes rather than weeks. Because Structura generates the source documents and Censa produces the billing grid from the same approved model, the database, the visit worksheets and the budget cannot drift apart, and every site in a network is built from the same protocol. In a June 2026 third-party assessment across 3,171 protocol data elements, Apta scored 99.62% precision. AI is used only at conversion; every build is generated deterministically from the approved model.

Concordare is not an eSource system and not an EDC. It does not capture participant data at the point of care and it does not hold participant data. It builds the eCRF in the EDC the site runs, and generates the source documents the site fills in however it already does, on paper or in its existing eSource platform.

How to tell which one you need

  • You have an EDC and a data manager and want to build faster by hand: your EDC's form designer, plus a CDASH template library.
  • You are a sponsor standardizing builds across many studies and vendors: a metadata repository.
  • You want coordinators to record source data electronically instead of on paper: an eSource system, with the forms still built separately.
  • You want the build produced from the protocol, in the EDC you already use, together with the source documents and the billing grid: a protocol-to-EDC generator that outputs to your systems rather than its own.
  • You want the AI to own the build without review: none of the above. Every vendor in the generator category keeps a human sign-off, and regulators expect one.

Definitions

Electronic case report form (eCRF). The electronic form on which a site records each participant's protocol-required data for the sponsor, hosted in an EDC.

Electronic data capture (EDC). The system that hosts eCRFs, applies edit checks, manages queries and holds the study database. REDCap, Rave, Veeva EDC, Castor, OpenClinica and Viedoc are EDCs.

eSource. Source data captured electronically at the point of care, in a system with an audit trail, rather than on paper. An eSource system records source data; it is not a build tool.

Edit check. A rule attached to an eCRF field that flags an out-of-range, missing or inconsistent value at entry.

Clinical Trial Protocol Model (CTPM). Concordare's machine-readable digital clinical trial protocol, extracted from the protocol PDF, reviewed by the study team, and used to generate source documents, EDC builds, billing grids and CTMS configuration. Full definition.

Concordare publishes how the CTPM is defined and how accurately it is extracted. To see a protocol converted and a REDCap build generated from it, request a demo.

Back to Media

Related posts