Skip to content

Platform

One platform. Two engines. One clinical data lifecycle.

Clinical data work is one continuous chain of translation: protocol to study design, collected data to standards, standards to analysis, analysis to submission. ClinDaddy splits that chain into two engines that meet in the middle — on one shared data model.

Illustration of the clinical data lifecycle running from protocol through FlashEDC data collection and FlashAnalysis to submission.
Illustration. Protocol, eCRFs and EDC at the front; SDTM, ADaM and TLFs downstream.

The lifecycle

Protocol to TLFs, without re-describing the study.

Because the platform designed the eCRF, it already knows the SDTM mapping. The study is described once, at design time, and the same description carries into data collection and the submission datasets.

FlashEDC

Protocol → eCRFs → EDC

01

Protocol

The protocol and its amendments define what the study must collect.

02

eCRFs

The protocol is read once and turned into CDASH-aligned visits, forms and fields.

03

EDC

Sites enter data into FlashEDC's own runtime, against the reviewed design.

FlashAnalysis

Clinical data → SDTM → ADaM → TLFs

04

SDTM

Collected data is mapped to CDISC SDTM submission datasets.

05

ADaM

Analysis-ready datasets and their derivations are produced.

06

TLFs

Tables, listings and figures are generated with traceability to source.

The two engines

Each engine owns a clearly bounded piece of the work.

Neither product is a general-purpose assistant. Each takes a defined input, produces a defined artifact, and stops at a point where a person can review it.
01Protocol → eCRFs → EDC

FlashEDC

An AI protocol analyzer, an eCRF designer with a review assistant, and ClinDaddy's own EDC runtime for data collection.

  • Protocol Analyzer
  • AI eCRF Designer
  • Design assistant
  • Review-ready study builds
  • CDASH field IDs and codelists
  • Edit-check generation
  • +5 more
Explore FlashEDC

FlashEDC · Study builder · Protocol SYN-014

Illustrative

Form · Demographics

FieldTypeCode list
BRTHDTCDateISO 8601
SEXRadioCDL_SEX
RACECheckboxCDL_RACE
COUNTRYDropdownCDL_COUNTRY
02Clinical data → SDTM → ADaM → TLFs

FlashAnalysis

SDTM, ADaM and TLF automation with independent QC, traceability and submission artifacts — from FlashEDC data or any EDC export.

  • Any EDC input
  • SDTM
  • ADaM
  • TLFs
  • Independent QC in SAS, R and SQL
  • Traceability
  • +6 more
Explore FlashAnalysis

FlashAnalysis · Standards pipeline · Study SYN-014

Illustrative

VS · Vital signs

USUBJIDVSTESTCDVSORRESVSSTRESN
1001SYSBP128128
1001DIABP8282
1002SYSBP134134
1002DIABP8686

Interfaces shown are illustrative and built with synthetic values. They are not customer systems, and no study data is reproduced anywhere on this site.

How the two connect

A single chain of custody, rather than two handoffs.

Point tools create the gap they were meant to close: the design lives in one system, the datasets in another, and the submission documents in a third. The platform is built so the same study identity runs through both engines.

One study identity

A study is identified once. The design produced at study build and the datasets produced downstream belong to the same study, not to two disconnected tools.

Specifications carry forward

Visits, forms, fields, codelists and edit checks are the same specification that governs downstream processing — so the SDTM mapping starts from what was designed.

One governance model

Audit logging, independent QC and human approval apply across both engines instead of being re-implemented per tool.

One protocol read, many systems

The study model is the product. EDC is its first projection.

The protocol is read once into a system-neutral study model: visits, forms, fields, codelists and edit checks, each carrying the protocol source behind it. EDC is the first system projected from that model — RTSM follows in 2027, then patient-facing capture and trial operations.
See what is available now
Illustration of the ClinDaddy character holding one study model card that projects into EDC, RTSM, eSource, CTMS, eTMF, ePRO, eCOA and eConsent panels.
Illustration. One study model, projected outward. EDC is available today; RTSM is in development for 2027; the rest are planned.

Human in the loop

AI drafts. A qualified user approves.

Automation should remove mechanical work, not accountability. The platform is built so a person is always the last step.
  • AI drafts

    The model reads the protocol and drafts specifications. It never writes the final clinical value.

  • A qualified person approves

    Every AI suggestion is editable and reviewable, and approval is an explicit act by a named person.

  • Every suggestion is logged

    AI output, corrections and approvals sit in an append-only audit trail, so the reasoning survives the decision.

Read the governance model

Demonstration

See the workflow, step by step.

Evidence is more useful than adjectives. Walk the pipeline each product runs, and the artifact it produces at every stage.

FlashEDC · Study builder · Protocol SYN-014

Illustrative

Form · Demographics

FieldTypeCode list
BRTHDTCDateISO 8601
SEXRadioCDL_SEX
RACECheckboxCDL_RACE
COUNTRYDropdownCDL_COUNTRY

Upload protocol

Document intake with format detection and job initialization.

Illustrative walkthrough using a synthetic protocol. No customer or confidential study material is shown.

Next step

See the platform against a study you already know.

We will walk through one protocol and one dataset, and show exactly where the automation stops and a reviewer takes over.