Skip to content

FlashEDC · Protocol → eCRFs → EDC

Turn a clinical trial protocol into an EDC study — and capture the data.

FlashEDC reads a clinical trial protocol and produces a review-ready study design — visits, forms, fields, CDASH-aligned codelists and edit checks — then runs the study on its own EDC runtime. Sites enter data against the design a reviewer approved, and every change is versioned.

Illustration of a study builder reviewing a clinical protocol while generated visit, form, and field structure appears as a study design.
Illustration. The study builder reviews the generated design; the protocol stays the source of truth.

Workflow

What FlashEDC does, in order.

The protocol goes in at the top. A reviewable study design comes out at the bottom — with two points where a person has to look at it before the next stage runs.
  1. Protocol

    Protocol supplied in PDF, DOCX, TXT or RTF.

  2. Protocol analysis

    Assessments, endpoints and collection intent extracted.

  3. Study skeleton

    Visits and the assessment matrix drafted for review.

  4. Review

    A study builder corrects the skeleton before expansion.

  5. eCRFs & fields

    Forms, fields, controls and codelists generated.

  6. Edit checks

    Check specifications and programming code generated.

  7. Second-eye QC

    Adversarial review; unresolved issues go to a human.

  8. EDC study

    The reviewed design runs on FlashEDC's EDC runtime.

  9. Data collection

    Sites enter data against the approved, versioned design.

Capabilities

What it produces.

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
  • Database specifications
  • Own EDC runtime
  • Versioned designs
  • Human review
  • Second-eye QC

Protocol Analyzer

Reads the protocol document as supplied and extracts the schedule of assessments, endpoints and data-collection intent that define the study.

AI eCRF Designer

Turns that reading into a panel-style study design: visits, forms, fields, controls and CDASH-aligned codelists. Alternative layouts are supported, and manually built forms can be reorganised automatically.

Design assistant

A conversational assistant drafts and revises design elements. The user always has the final say; every suggestion is editable and reviewable before it reaches the study.

Study workspace

Sponsors sign in, open an existing study or load a new protocol. Each study keeps its own design, versions and review history.

Versioning

A published design is never edited in place. Updates create a new version, so the design a site collected against remains reconstructable.

EDC data collection

FlashEDC includes its own EDC runtime. Sites and subjects enter data against the approved design, with the structure that was reviewed at build time being the structure data is captured against.

Standards

CDASH field identifiers, codelists and eCRF naming are applied at design time, so the study starts aligned with the standards its submission will need.

Review and QC

Generated work arrives as a draft. A qualified reviewer corrects it, a second adversarial pass looks for defects, and approval is an explicit act by a named person.

Study build, then data collection

One design, from protocol to the site's screen.

The structure that was reviewed at study build is the structure data is captured against. There is no second build in another system, and no translation step between design and collection.
Illustration of a protocol document entering a study-build machine and emerging as visit, form and lab-panel artifacts, with a clock reading 10–30 minutes and a stack labelled ten weeks of manual processes behind it.
Illustration. A protocol becomes a review-ready study build; the time shown is to a review-ready build, not to a live study. Live studies follow the same review, approval and validation path.

Minutes, not weeks

A review-ready study design is drafted from the protocol in minutes in our internal benchmarks, rather than assembled by hand over weeks. The review and approval path is unchanged.

Standards at design time

CDASH field identifiers, codelists and eCRF naming are applied while the study is designed, not retrofitted before submission.

Versioned by default

A published design is never edited in place. Updates create a new version, so the design a site collected against stays reconstructable.

Its own EDC runtime

The study runs on FlashEDC's EDC data collection. Sites enter data against the design a reviewer approved.

The speed figure is time to a study build ready for human review, not time to a live study. A study going live still follows the same review, approval and validation path.

Human review

Generation is the fast part. Review is the point.

A study design that nobody checked is not an asset. FlashEDC is built so the output arrives as a draft a study builder can correct — not as a finished artifact to be accepted or rejected.
  1. Generate

    The pipeline produces a draft: skeleton first, then eCRFs, fields and edit checks.

  2. Review

    A study builder reads the draft and corrects it directly in the artifact.

  3. Second-eye QC

    An adversarial pass looks for defects, resolves what is safe to resolve, and escalates the rest.

  4. Approve

    Nothing is finalized until a named reviewer approves it.

Corrections are made in the artifact itself. Re-running the pipeline to get a different answer is not the workflow, because the reviewer's judgement has to survive into the final design.

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.

Where it is today

Available today.

FlashEDC is a finished product: protocol analysis, eCRF design and the EDC runtime that collects the data. It is demo-ready now.

Status describes the product, not commercial traction. There are no customers or case studies to point to yet.

Next step

See FlashEDC against your own protocol or dataset.

Bring a study and we will walk through what the platform produces — and where a human still has to decide.