Spec → Code

Load spec from plain text

Paste raw spec text (Notepad, Word, email — anything unstructured), or upload a .txt file. Fields below will be populated for you to review and edit.

Migrate from existing SAS code (optional)

Only relevant if this client is migrating off legacy SAS-based reporting. Paste or upload SAS code that's already been written and confirmed working -- it will be reverse-engineered into the same spec fields below, so it can then be regenerated for whichever target (CQL, SAS, R, Python) this client actually needs. This does NOT translate SAS syntax directly -- see the migration notes for why.

Study metadata (optional)

Loading real Form/Item metadata for a study grounds generation in actual names instead of inferred CDISC convention, and lets guardrails verify Forms actually exist.

Study ID

Metadata CSV (columns: form, item, label, data_type)

Report specification

EDC system

Language

Only Veeva/CQL and Veeva/Python have a verified generation path today.

Report ID*

Supporting document (optional)

Upload this report's real View/Column mapping (e.g. an RID_supp_doc.csv export) to ground Understand Logic and Generate in the exact column names this report actually uses, instead of inferred ones. Keyed to the Report ID above -- fill that in first.

Supporting document CSV (columns: VIEWNAME, COLUMNNAME, ITEMQUESTION, ORIGINAL ITEMQUESTION, CONTROLLEVEL, PREFIX)

Study ID (optional — links to uploaded metadata above)

Description*

Column heading

Logic

Report scenarios

Sorting