Skip to content

FlashAnalysis · Clinical data → SDTM → ADaM → TLFs

From Clinical Data to Analysis and Submission.

FlashAnalysis takes clinical data from FlashEDC, another EDC, or the sponsor's own specifications and produces CDISC SDTM and ADaM datasets, tables, listings and figures, independent QC code, and the submission artifacts that describe them. It works with any EDC's raw data, so a sponsor does not have to switch systems.

Illustration of the ClinDaddy character at a console showing raw clinical data flowing through SDTM and ADaM to results, with a separate QC rail converging on a match and lineage traced back to source rows.
Illustration. One dataset path from raw data to results, a QC run kept deliberately separate, and every value traceable to the row it came from.

Workflow

What FlashAnalysis does, in order.

Collected data enters at the top. Submission artifacts come out at the bottom, having passed through standards transformation, analysis, and two independent checks.
  1. Clinical data

    FlashEDC data, any EDC export, or sponsor specifications.

  2. SDTM

    Deterministic mapping to CDISC SDTM domains.

  3. ADaM

    Analysis-ready datasets and recorded derivations.

  4. TLFs

    Tables, listings and figures with source traceability.

  5. Independent QC

    Separate implementation in SAS, R and SQL.

  6. Submission artifacts

    Define-XML, aCRF, cSDRG, ADRG, eCTD package.

  7. Review

    Differences and outputs reviewed and approved by a person.

Capabilities

What it produces.

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
  • Define-XML
  • aCRF
  • cSDRG
  • ADRG
  • eCTD-ready package
  • Pinnacle 21 clean-up

Inputs at every step

Accepts FlashEDC data, an export from any other EDC, or the sponsor's own specifications. A study does not have to start on FlashEDC to use FlashAnalysis.

SDTM

Maps collected data into CDISC SDTM domains using deterministic processing, with the mapping recorded against each source variable.

ADaM

Builds analysis-ready datasets and the derivations behind them, with each derivation tied to its specification.

TLFs

Generates tables, listings and figures from specifications, with every value traceable to the records that produced it.

Independent QC

QC re-implements the computation by a different route and compares results. Downloadable SAS, R and SQL QC code is produced at each step, rather than a second run of the production code.

Traceability page

Inputs, process files and outputs are exposed per step as downloads, so a reviewer can follow any number back to its source.

Submission artifacts

Define-XML, aCRF, cSDRG, ADRG and an eCTD-ready clinical data package are assembled from the same sources as the datasets they describe.

Pinnacle 21 clean-up

Submission datasets are checked and cleaned against Pinnacle 21 rules before the package is handed over.

Sold separately

Keep your EDC. Add the analysis layer.

FlashAnalysis is not a reason to migrate systems. It accepts data from FlashEDC, any other EDC, or the sponsor's own specifications, and produces the submission package from there.

Many small sponsors already have an EDC they are comfortable with, and a programming gap downstream. FlashAnalysis can be bought as one deliverable — an SDTM/ADaM/TLF package, an independent QC run, or a submission-readiness check — without changing where the data is collected.

FlashEDC and FlashAnalysis connect when a sponsor uses both, but neither depends on the other to be useful.

Independent QC

A second run of the same code is not a second opinion.

If QC re-executes production, it agrees with production by construction — including when production is wrong. FlashAnalysis separates the two computations on purpose, then compares the results and hands the differences to a reviewer.

Source data

Collected clinical data

Production

Executes the approved specification

Independent QC

Re-implements the computation

Compare

Differences surfaced, never silently reconciled

Review

A person resolves what the comparison found

Production executes the approved specification. Independent QC re-implements the computation from the same specification by a different route. The comparison between the two results is the evidence — not the fact that both runs finished.

Cross-artifact QC extends that check beyond a single output: datasets, specifications, and the documents that describe them are compared against each other, which catches the inconsistencies that per-artifact review cannot see.

Differences are surfaced for review. They are never reconciled silently, and nothing is released on the assumption that a discrepancy was benign.

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.

FlashAnalysis · Standards pipeline · Study SYN-014

Illustrative

VS · Vital signs

USUBJIDVSTESTCDVSORRESVSSTRESN
1001SYSBP128128
1001DIABP8282
1002SYSBP134134
1002DIABP8686

Load data

Provenance record attached to each delivered dataset.

Illustrative walkthrough. Datasets, tables and figures shown are synthetic.

Where it is today

Available today — and sold on its own.

FlashAnalysis is a finished product: SDTM, ADaM, TLFs, independent QC and submission artifacts, covered by approximately 2,500 automated tests.

It works with FlashEDC data, any other EDC's export, or the sponsor's own specifications. A sponsor does not have to switch EDC to use it.

Next step

See FlashAnalysis 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.