Demos
Which tool does what
Eleven tools is too many to guess at. This is what each one is for and when you
would actually reach for it — in pipeline order, raw data on the left.
Raw data → SDTM
| Tool | What it is for | Reach for it when |
|---|
| SDTM Mapper | Raw study data → SDTM | You have raw datasets and need SDTM domains, and you want to see what it refused to map. |
| SDTM Automation Agent | The mapping engine itself | You want the agent behind the mapper rather than the UI. |
| Define-XML Maker | Produce define.xml | You need define.xml with its stylesheets, not a stub. |
SDTM → ADaM → TLF
| Tool | What it is for | Reach for it when |
|---|
| ShellForge | TLF shells → runnable programs | You have shells and need the programs, across 35 output classes. |
Language & packages
| Tool | What it is for | Reach for it when |
|---|
| RLab | Learn R for clinical work | You know SAS and need R. Run real code in the browser, no install, no login. |
| PyLab | Learn Python for clinical work | Same as RLab, Python track — pandas for ADaM-shaped data. |
| R-Forge Studio | Read and build pharmaverse packages | You need to understand, compare or document an R package before trusting it in GxP. |
| ShinyForge Studio | Build clinical Shiny apps | You need a reviewable Shiny app, not a prototype. |
| Clinical R Packages | Ten ready R packages | You want the packaged functions rather than a studio. |
Submission
| Tool | What it is for | Reach for it when |
|---|
| ClinTrial Explorer | Explore trial data structures | You are orienting in an unfamiliar study. |
Therapeutic area
| Tool | What it is for | Reach for it when |
|---|
| Safety Monitor | Watch safety signals | You need safety review over study data. |
Every link above answered an HTTP request on the last check. Tools that did not
answer are listed on the tools page rather than hidden.