SAP-Genie

One protocol in. The whole submission package out.

SAP-Genie reads the study design straight from the protocol, generates the statistical analysis plan as an ARS ReportingEvent, and builds every downstream CDISC deliverable from that same structured object. Accurate, consistent and traceable to the study design.

The Network Map: click any node to see its lineage from protocol to endpoint, analysis, SDTM and ADaM variables and the table it ends up in.

Nine deliverables from one governed pipeline

Each output is generated, validated against its standard and traced to the same protocol.

SAP
ARS ReportingEvent with analyses, analysis sets and methods.
json
SDTM specifications
SDTMIG 3.4 domains with every derivation.
json
ADaM specifications
ADaMIG 1.3 datasets with consumed-by links back to the analyses.
json
Table of contents
The output plan and numbering.
json
TLF shells
Mock tables, listings and figures.
rtf
TLFs
Populated outputs, consistent with their shells.
rtf
Annotated CRF
Collection fields mapped to their SDTM origins.
pdf
SAS programs
Drop-in SDTM and ADaM program skeletons.
sas
Define-XML
Define 2.1 submission metadata.
xml

Specs, shells, programs and metadata stay aligned by construction, not by reconciliation.

How it works

Two layers. The generation pipeline turns the protocol into USDM 4.0, then the SAP, specifications and Define-XML, while the data path runs from CRF through synthetic data to SDTM, ADaM and TLFs. The standards layer checks every artifact before it moves downstream.

The annotated CRF feeds the SDTM specifications with collection origins. The SAP and SDTM specs converge on ADaM: the analyses set which variables are needed, and SDTM sets where they come from.
Conformance is built in, not corrected later. Three human checkpoints catch what conformance cannot.
  1. Origin confirmation

    A reviewer confirms the aCRF-to-SDTM origins.

  2. Analysis adjudication

    The statistician confirms SAP intent against the ADaM derivations.

  3. Submission sign-off

    The Define-XML package is attested before it leaves.

  • CDASH 2.3
  • USDM 4.0
  • Biomedical Concepts
  • Controlled Terminology, version-pinned
  • SDTMIG 3.4
  • ADaMIG 1.3
  • ARS 1.0
  • Define-XML 2.1
  • Sponsor standards

From new project to traced SAP

One workspace, one study, one click.

  1. Create a project

    One project per study. Every uploaded file and generated artifact lives in it, versioned and traceable to the study.

  2. Work from the overview

    The study's files, the generation steps that have run, lineage and artifacts in one place, with the parameters of each run recorded.

  3. Upload the protocol

    SAP-Genie reads the study design directly. Nothing is re-typed by hand, so the protocol stays the single origin.

  4. Generate the SAP

    One click produces an ARS-conformant ReportingEvent: a structured object, not a Word file, so everything downstream is generated from it.

  5. Pin the configuration

    The section template and generation settings are fixed, so the same protocol and configuration give the same structure every time.

  6. Review the artifacts

    The ARS ReportingEvent, the USDM study definition and the rendered SAP, each downloadable and traced to the sources that informed it.

  7. Inspect the SAP as data

    Machine-checkable JSON that every downstream stage consumes directly. When a reviewer asks why it says something, the traceability panel answers.

Shared across studies

Knowledge Base

Protocols, SAPs and standards documents are chunked, embedded and searchable. Every generation records which sources informed it and how strongly.

Metadata Repository

Specifications, controlled terminology and Define metadata, searchable across studies instead of rebuilt for each one.

See SAP-Genie on your protocol

Send a note and we'll set up a walkthrough.

Email hello@sap-genie.dev