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.
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.
- 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.
Origin confirmation
A reviewer confirms the aCRF-to-SDTM origins.
Analysis adjudication
The statistician confirms SAP intent against the ADaM derivations.
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.
-
Create a project
One project per study. Every uploaded file and generated artifact lives in it, versioned and traceable to the study.
-
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.
-
Upload the protocol
SAP-Genie reads the study design directly. Nothing is re-typed by hand, so the protocol stays the single origin.
-
Generate the SAP
One click produces an ARS-conformant ReportingEvent: a structured object, not a Word file, so everything downstream is generated from it.
-
Pin the configuration
The section template and generation settings are fixed, so the same protocol and configuration give the same structure every time.
-
Review the artifacts
The ARS ReportingEvent, the USDM study definition and the rendered SAP, each downloadable and traced to the sources that informed it.
-
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.
See SAP-Genie on your protocol
Send a note and we'll set up a walkthrough.