Each tool below is deployed, monitored, and serving production-grade clinical programming workflows — designed to be the foundation a team would build on at scale.
AI · Shell Annotation · Paired Codegen
ShellForge — ADaM Shell Annotation Studio
Upload any table shell (DOCX/XLSX/RTF/PDF/TXT) → auto-annotate every row to ADaM dataset.variable.where.statistic using a 5-pass rule engine + LLM fallback → generate paired SAS deliverable + R validator programs + annotated PDF with red mapping callouts.
FastAPIPythonSASRreportlabCDISC
Impact: Collapses manual shell annotation from hours to seconds — every row mapped to its ADaM variable, with SAS deliverable and R validator generated from a single spec by construction.
CDISC ARS · Conformance
ARS Validator
Paste or upload a CDISC Analysis Results Standard (ARS) JSON and validate it against a 21-rule conformance engine — structure, references, and controlled terminology — returning severity-graded findings (FAIL / WARN / INFO) with CDISC citations for each rule.
FastAPIPythonCDISC ARSConformancedefine.xml
Impact: Catches ARS spec defects before they reach production — a working conformance checker for the emerging Analysis Results Standard, with citations a reviewer can trust.
ARS · TLF Render
TLF Viewer
Import an ARS JSON spec and render the table/listing shell instantly — a spec-to-output preview with a sample fixture, so you can see the TLF an ARS definition produces without running SAS.
FastAPIPythonCDISC ARSTLFRendering
Impact: Turns an abstract ARS JSON into a visible table in one click — closing the loop between spec and output for reviewers and programmers.
CDISC ARS · TLF Engine
ARDflow — ARS TLF Engine
Turn a CDISC Analysis Results Standard (ARS) spec into a complete, traceable TLF — computes the Analysis Results Dataset (ARD) and renders submission RTF + Dataset-JSON + HTML with a full spec→result trace. An ARS-driven TLF reviewer running live R.
RShinyCDISC ARSr2rtfDataset-JSON
Impact: Makes the Analysis Results Standard executable — one ARS spec produces the dataset, the RTF, and the traceability, end to end.
AI Pipeline · SDTM · Accuracy Gate
SDTM Mapper — Raw Data → CDISC SDTM XPT
Upload raw clinical CSV/SAS7BDAT → auto-classify SDTM domain → LLM generates variable-by-variable mapping spec → SAS+R+Python programs generated in parallel → Python executed server-side → SDTM CSV+XPT produced → 10-rule Pinnacle-21-style CDISC validation. Accuracy gate: DeepSeek first, auto-escalate to Opus only on failure.
FlaskPythonSDTMIG v3.4SAS+RClaude OpusDeepSeek
Impact: Cuts SDTM mapping from days to minutes — variable-by-variable spec, 3 executable programs, and a CDISC conformance report produced end-to-end from a single raw file upload.
R Shiny · QC Workflow · bslib v5
QC Cockpit — Clinical TLF QC Dashboard
Enterprise R Shiny 4-tab QC dashboard for clinical programmers and reviewers. Records, tracks, and signs off on table-level QC discrepancies against CDISC ADaM ground truth. Progress gauges, filterable discrepancy log, and append-only sign-off audit trail.
R Shinybslib v5reactableplotlyCDISC ADaM
Impact: Gives QC teams a structured, auditable workspace — discrepancy tracking and sign-off with a CSV audit trail, replacing ad-hoc email and spreadsheet QC workflows.
AI Governance · Human-in-the-Loop · 21 CFR Part 11
AI Governance & Validation Framework
A 5-stage human-in-the-loop pipeline for using LLMs on regulated clinical data: Input Validation → Constrained Generation → Automated QC → Human Sign-Off → Audit Trail. Every generated output is traceable, automatically checked, and gated behind human approval before it can be trusted — mapped to ALCOA+, 21 CFR Part 11, and CSV lifecycle expectations. Includes a client-side privacy layer that strips sponsor names and protocol IDs before any text leaves the browser, so it runs inside pharma firewalls.
GenAILLMRAGHITL21 CFR Part 11ALCOA+
Impact: Answers pharma's #1 GenAI-adoption blocker — how to use LLMs without leaking protocol/sponsor data and without losing regulatory traceability. Governance built into the tool, not bolted on.
R Shiny · Pharmacovigilance · Safety
ClinSafe Monitor — Pharmacovigilance Signal Detection
Enterprise R Shiny safety dashboard with 5 interactive tabs: AE overview metrics, AE Explorer, Signal Detection (PRR/ROR/Chi² per preferred term using Evans 2001 WHO criteria), Time Trends (KM time-to-first-AE + AE onset by week), and Subject Gantt timeline. CLINSAFE-001: 200 subjects, 681 AEs, 10 SOCs.
R Shinybslib v5survivalplotlyPRR/RORCDISC ADaM
Impact: Production-grade pharmacovigilance dashboard — signal detection with regulatory-standard Evans 2001 thresholds, KM curves, and subject-level AE Gantt timelines in a single R Shiny deployment.
Program-Driven QC · Subject-Level Verification
RTF QC Workbench
Independent Python QC that re-derives every count in a clinical TLF from subject-level ADSL and verifies it against the production RTF — cell by cell, with drill-down to the exact subject IDs behind each number. Program-driven double-programming, not visual review. 100% synthetic CDISC demo data.
PythonFastAPISQLiteADaMRTF parseDouble-Prog QC
Impact: Automates independent-programming QC of TLF outputs — every displayed count is re-derived from subject data and reconciled against the RTF, with full subject-level traceability.
Open-Source R
R Packages — clinassist & ardflow
Two production R packages: clinassist generates validated SAS+R code from a shell via RAG, and ardflow turns a CDISC ARS spec into a complete TLF (RTF + Dataset-JSON + HTML) with full traceability.
RpharmaverseadmiralARSr2rtf
Impact: Packaged, tested, documented R — internal tooling shipped the way a tool-development function should deliver software.
AI Pipeline
SDTM Automation Agent
6-agent AI pipeline: raw clinical data + specs → 8 SDTM datasets + 8 SAS programs + MCP server with 7 tools. Metadata-aware, CT-validated, submission-ready output.
PythonAI AgentsSASMCPSDTM
Impact: Cuts SDTM programming timeline from weeks to hours by generating datasets and validation programs from raw data + specifications.
AI Assistant
Ask a Clinical SAS Programmer
Free 15-minute expert sessions: CDISC, SDTM, ADaM, TLF and define.xml questions answered with references — grounded in a curated standards knowledge base, gated by email.
LLMRAGCDISCLead-gen
Impact: Gives any programmer instant standards answers — and turns every visitor into a qualified conversation.
AI Assistant
ClinAssist
Turns a TLF shell specification into submission-ready SAS + R code through a RAG engine. Browser-side sanitization keeps compound names off the LLM, and every output carries a GAMP 5 audit header.
LLMRAGCDISCSAS+R
Impact: Collapses shell-to-code from hours of manual programming to seconds — with built-in CDISC validation and synthetic test data, so no real patient data is needed.
ARS-Aligned Pipeline
ARDflow — ARS TLF Engine
Spec-driven TLF generator in pure R that produces ARS-compliant outputs: HTML table, FDA-style RTF, and CDISC Dataset-JSON ARD — all from a single structured specification.
RARSDataset-JSONRTF
Impact: Bridges the emerging CDISC Analysis Results Standard to production TLF output, with full traceability logging.
Submission Package
Oncology CDISC Demo
End-to-end oncology submission package with SDTM, ADaM, TLF outputs, define.xml, KM/PFS/waterfall/swimmer plots, and AE/ORR tables — all generated from CDISCPILOT01 data.
SASROncologydefine.xmlGraphics
Impact: Working demonstration of what a complete oncology submission package looks like — from raw to regulatory-ready.
R Packages · pharmaverse
Clinical R Packages — ten-package family
Ten R packages, each closing one gap that current open-source clinical R tooling leaves to hand-written study code: IQ/OQ evidence, validation findings traced back to source, Define-XML 2.1, trial design and SUPPQUAL derivation, submission packaging, shell-to-RTF, higher-level ADaM wrappers, SAS-parity displays, exposure-response datasets, and reviewer guides. Built on pharmaverse, not instead of it.
RpharmaverseCDISCDefine-XMLpkgdown
Impact: 2,321 tests across the family, every package clean at 0 errors / 0 warnings / 0 notes — verified by independent re-run rather than by trusting the build reports.
CDISC SDTM · Delivery Conformance
sdtm-check — SDTM Delivery Conformance
Four deterministic checks over an SDTM delivery — structural completeness, cross-field consistency, visit & date coherence, and CDISC controlled terminology — with one consolidated report. No model and no API key, so the same delivery and the same CT release always yield the same findings. Ships as a CLI, and as script steps in a workflow with a human review gate and an audit trail.
RCDISC CTSDTMDockerMediforce
Impact: Separates the blocking violations a sponsor cannot justify from the sponsor extensions that are legitimate — so a reviewer reads a short list of real defects instead of a wall of noise.