<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Jaime Yan — Research &amp; Writing</title><description>AI/LLM automation for clinical trial statistical programming: papers, preprints, and technical writing.</description><link>https://jaimeyan.com/</link><item><title>LLM Agents in Clinical Trials: What&apos;s Real Beyond the Demos</title><link>https://jaimeyan.com/blog/llm-agents-clinical-trials-reality.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/llm-agents-clinical-trials-reality.html</guid><description>How to tell demo-ware from deployable agentic AI in clinical trials: determinism, audit trails, 21 CFR Part 11, constrained architectures, and vendor questions.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>llm-agents</category><category>clinical-trials</category><category>gxp</category><category>audit-trail</category><category>agent-architecture</category></item><item><title>AI Coding Assistants for Clinical Programmers: What Works in GxP</title><link>https://jaimeyan.com/blog/ai-coding-assistants-sas-gxp.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/ai-coding-assistants-sas-gxp.html</guid><description>Where ChatGPT, Claude, and Copilot genuinely save time in SAS and R clinical programming, where they fail, and how to use them inside auditable GxP workflows.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>ai-coding-assistants</category><category>sas-programming</category><category>gxp</category><category>clinical-programming</category><category>llm-tools</category></item><item><title>CDISC CORE Explained: Open-Source Validation for SDTM/ADaM Programmers</title><link>https://jaimeyan.com/blog/cdisc-core-validation-explained.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/cdisc-core-validation-explained.html</guid><description>CDISC CORE is a free, open-source rule engine for SDTM and ADaM validation. How its YAML rules work, how to run it, and where rule-based checking stops.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>cdisc-core</category><category>sdtm</category><category>adam</category><category>clinical-data-validation</category><category>open-source</category></item><item><title>Temperature 0 Doesn&apos;t Buy You Reproducibility</title><link>https://jaimeyan.com/blog/note-temperature-zero.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/note-temperature-zero.html</guid><description>Setting temperature to zero feels like determinism. It isn&apos;t — and in GxP work the difference will find you during an audit, not during development.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>llm</category><category>reproducibility</category><category>gxp</category><category>statistical-programming</category></item><item><title>SAS to R Migration in Clinical Programming: A Practical Field Guide</title><link>https://jaimeyan.com/blog/sas-to-r-migration-field-guide.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/sas-to-r-migration-field-guide.html</guid><description>Why pharma is moving from SAS to R, what breaks in practice (procedures, XPT files, QC), and how to migrate a validated macro library without a rewrite.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>sas-to-r</category><category>pharmaverse</category><category>admiral</category><category>clinical-programming</category><category>xpt</category><category>validation</category></item><item><title>One Number That Explains Where Rule-Based Validation Stops</title><link>https://jaimeyan.com/blog/note-core-coverage-boundary.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/note-core-coverage-boundary.html</guid><description>69.7% of oncology CORE rules port cleanly to a graph constraint language. The 30% that don&apos;t are exactly where the dangerous errors live.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>cdisc</category><category>sdtm</category><category>validation</category><category>core</category></item><item><title>LLMs in Clinical Statistical Programming: Proven vs Hype (2026)</title><link>https://jaimeyan.com/blog/llm-clinical-statistical-programming-state-2026.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/llm-clinical-statistical-programming-state-2026.html</guid><description>A tiered survey of LLM evidence in clinical trial statistical programming: benchmarked results, promising single-team studies, vendor hype, and open gaps for 2026–2027.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>llm</category><category>clinical-trials</category><category>statistical-programming</category><category>survey</category><category>benchmarks</category><category>gxp</category></item><item><title>The Contradictions Your Validator Can&apos;t See</title><link>https://jaimeyan.com/blog/graph-constrained-validation-cdisc-oncology.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/graph-constrained-validation-cdisc-oncology.html</guid><description>Rule-based SDTM validators structurally miss cross-domain contradictions. SHACL-SPARQL graph constraints plus a deterministic agent layer catch all 20 archetypes.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><category>cdisc</category><category>sdtm</category><category>shacl</category><category>recist</category><category>clinical-data-validation</category></item><item><title>Double Programming Without the Duplication: AI-Generated QC Code</title><link>https://jaimeyan.com/blog/eliminating-qc-programming-duplication.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/eliminating-qc-programming-duplication.html</guid><description>Independent QC re-programming costs 30–50% of clinical programming effort. An AI framework matched 97.1–100% of variables while keeping independence intact.</description><pubDate>Tue, 25 Aug 2026 00:00:00 GMT</pubDate><category>qc-programming</category><category>clinical-trials</category><category>llm-agents</category><category>adam</category><category>validation</category></item><item><title>Benchmarking RAG for Clinical TLF Templates: 1,999 Experiments</title><link>https://jaimeyan.com/blog/benchmarking-rag-clinical-tlf-templates.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/benchmarking-rag-clinical-tlf-templates.html</guid><description>Five LLM generation methods benchmarked across 1,999 bootstrap experiments on ICH E3-conformant TLF templates: hybrid RAG with reranking beats direct prompting.</description><pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate><category>rag</category><category>llm-benchmarking</category><category>tlf-templates</category><category>clinical-trials</category><category>r-code-generation</category></item><item><title>Why LLM Agents Fail at Regulated Programming — the Process-DAG Fix</title><link>https://jaimeyan.com/blog/why-llm-agents-fail-regulated-programming.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/why-llm-agents-fail-regulated-programming.html</guid><description>Free-form agent loops break down in GxP clinical programming. Structuring the work as a typed process DAG makes LLM agents reliable, replayable, and auditable.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>llm-agents</category><category>clinical-trials</category><category>gxp</category><category>statistical-programming</category></item><item><title>Five Years of Automation Evidence: Real Gains, Mostly Low Grades</title><link>https://jaimeyan.com/blog/evidence-automation-clinical-statistical-programming.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/evidence-automation-clinical-statistical-programming.html</guid><description>A GRADE-rated review of 2020–2025 automation evidence in statistical programming: real gains, mostly Low to Very Low quality evidence.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>statistical-programming</category><category>automation</category><category>evidence-quality</category><category>clinical-trials</category></item><item><title>Modernizing a 558-Macro SAS Library Without Touching Validated Code</title><link>https://jaimeyan.com/blog/non-destructive-legacy-modernization-sas.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/non-destructive-legacy-modernization-sas.html</guid><description>A bridge map, typed IR, and orchestrator wrap a legacy SAS TFL library unchanged — AI-ready JSON on day one, 80%+ cell-level parity, optional 92% code cut.</description><pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate><category>sas</category><category>legacy-modernization</category><category>clinical-trials</category><category>llm-integration</category><category>statistical-programming</category></item><item><title>CAVE-Onc: Graph-Constrained Agentic Validation for Cross-Domain Contradictions in CDISC Oncology Submissions</title><link>https://jaimeyan.com/papers/cave-onc.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/cave-onc.html</guid><description>PLOS One — Regulatory submissions in oncology must remain consistent across interdependent CDISC SDTM domains, yet cross-domain contradictions routinely survive conventional validation. CAVE-Onc introduces a graph-constrained agentic validation framework that models SDTM submission datasets as an RDF knowledge graph, combining declarative SHACL-SPARQL graph constraints with a deterministic LangGraph-based agent layer to detect cross-domain contradictions that domain-scoped rule-based validators cannot express. In a pre-registered evaluation, CAVE-Onc detected all 20 clinician-reviewed injected contradiction archetypes (vs 8/20 for the CDISC CORE engine and 6/20 for the Pinnacle 21 FDA engine, both 0/10 on cross-domain RECIST contradictions) — a construction validation of expressiveness — and stayed specific (0.06–0.09 flags/subject) on two real Project Data Sphere oncology trials mapped to SDTM, detecting 10/11 and 16/18 of applicable injected archetypes. CAVE-Onc writes all validation traces to a Merkle-chained, tamper-evident audit store, providing a foundation for 21 CFR Part 11 compliance.</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><category>CDISC</category><category>SDTM</category><category>SHACL</category><category>SPARQL</category><category>RDF knowledge graph</category><category>RECIST 1.1</category><category>oncology</category></item><item><title>Thin MCP, Thick Skills: Five Layers for Clinical Programming Agents</title><link>https://jaimeyan.com/blog/five-layer-architecture-clinical-agents.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/five-layer-architecture-clinical-agents.html</guid><description>ClinAgent splits clinical programming capability into five layers, keeping MCP tools stateless and packaging domain expertise as testable skills.</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate><category>llm-agents</category><category>mcp</category><category>clinical-trials</category><category>statistical-programming</category><category>agent-architecture</category></item><item><title>Synthetic ADaM That Survives a Join: Knowledge Graphs, LLMs, Faker</title><link>https://jaimeyan.com/blog/synthetic-adam-datasets-llm-knowledge-graph.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/synthetic-adam-datasets-llm-knowledge-graph.html</guid><description>Schema-only synthetic ADaM generation plateaus at 0.45 overall quality; enriching schemas from protocol/SAP/CRF knowledge graphs plus templates reaches 0.70.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>synthetic-data</category><category>adam</category><category>knowledge-graphs</category><category>llm</category><category>statistical-programming</category></item><item><title>Fine-Tuning Llama 3.1 8B for admiral R Code: From 0.36 to 0.82</title><link>https://jaimeyan.com/blog/fine-tuning-small-llms-admiral-r.html</link><guid isPermaLink="true">https://jaimeyan.com/blog/fine-tuning-small-llms-admiral-r.html</guid><description>Base Llama 3.1 8B scores 0.36 on admiral code generation. LoRA fine-tuning plus knowledge-graph validation gets it to 0.82 — without sending data to an API.</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>fine-tuning</category><category>lora</category><category>admiral</category><category>adam</category><category>small-llms</category></item><item><title>A Non-Destructive Methodological Framework for Modernizing Legacy Clinical Reporting Systems for AI-Driven Pharmacoinformatics: A SAS Case Study</title><link>https://jaimeyan.com/papers/legacy-modernization-framework.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/legacy-modernization-framework.html</guid><description>arXiv — Legacy SAS macro libraries resist AI integration because they emit opaque RTF with no machine-readable layer, yet source-level change triggers re-validation. This preprint presents a non-destructive framework — a bridge map, typed Intermediate Representation, and orchestrator that wrap the legacy library unchanged — applied to a 558-component industrial SAS library. Coexistence mode delivers AI-ready JSON output on day one; optional consolidation achieved a 92% SAS code reduction. Parity validation reached at least 80% cell-level parity on 11 of 14 reports from an internal Phase III study and 100% parity (4,764 cells) on the public CDISCPilot01 benchmark, and LLM experiments demonstrated IR-based table summarization, anomaly detection, and configuration generation.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><category>legacy modernization</category><category>clinical reporting</category><category>SAS</category><category>intermediate representation</category><category>pharmacoinformatics</category><category>parity validation</category><category>AI readiness</category></item><item><title>ClinAgent: A Five-Layer Architecture for Autonomous Clinical Trial Statistical Programming</title><link>https://jaimeyan.com/papers/clinagent-five-layer.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/clinagent-five-layer.html</guid><description>medRxiv — This preprint presents the five-layer ClinAgent architecture — A2UI rendering, skill router, thick skills, thin MCP tools, and compliance infrastructure — under a &quot;Thin MCP, Thick Skills&quot; design that augments any MCP-compatible AI coding agent (Augment Code, Claude Code, Cline, Cursor) with clinical programming capabilities rather than acting as an autonomous agent itself. Skills are independently testable, and the infrastructure layer provides audit logging and data masking for GxP compliance. Nine skills (SK-001–SK-009) were validated on a production Phase 2 cardiovascular study (11 ADaM domains, 93,239 synthetic observations): log analysis achieved 100% precision (1 error, 7 warnings over 10 logs), all 56 ADSL variables were matched, and specification generation reached 72.1% derivation accuracy overall and above 96% on simple domains.</description><pubDate>Fri, 16 Jan 2026 00:00:00 GMT</pubDate><category>ClinAgent</category><category>Model Context Protocol</category><category>agent architecture</category><category>CDISC</category><category>ADaM</category><category>statistical programming</category></item><item><title>ClinAgent: AI-Assisted Methodology for Clinical Trial Data Processing and Statistical Programming</title><link>https://jaimeyan.com/papers/clinagent-methodology.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/clinagent-methodology.html</guid><description>Biology Methods and Protocols — Clinical trial statistical programming remains labor-intensive: ADaM dataset derivation, TLF generation, and QC programming consume substantial effort per submission. ClinAgent is a skill-and-tool layer that augments any MCP-compatible AI coding agent with clinical-programming capabilities: nine skills (SK-001 Study Setup through SK-009 eSub Packaging) package prompts, deterministic rule engines, and decision trees, while thin MCP tools provide stateless I/O for SAS datasets, Excel specifications, and log files. All nine skills passed functional validation on artifacts from a single production Phase 2 study — deterministic components matched all 56 ADSL variables, and prompt-based specification generation reached 72.1% derivation accuracy (&gt;96% on simple domains, &lt;55% on complex domains, with wide confidence intervals making these point estimates upper bounds) — while end-to-end productivity gains were not measured and remain future work. Human review gates and deterministic audit trails preserve the traceability and reproducibility required for regulatory submissions.</description><pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate><category>clinical trials</category><category>statistical programming</category><category>Model Context Protocol</category><category>AI coding agents</category><category>CDISC</category><category>ADaM</category><category>automation</category></item><item><title>Eliminating QC Programming Duplication Through Claude AI-Assisted Independent Code Generation: A Practical Framework for Regulatory-Compliant Validation</title><link>https://jaimeyan.com/papers/pharmasug-2026-ai-201.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2026-ai-201.html</guid><description>PharmaSUG 2026 — Independent QC programming — recreating production programs from specifications alone — accounts for an estimated 30–50% of total clinical programming effort. This paper presents a Claude AI-assisted workflow that generates independent QC code in Python directly from ADaM specifications, combining a QC Trace Tree, a Decision Router, Agent Skills, and an automated code review engine to reduce duplication between production and QC streams while preserving operational independence through isolated AI instances, with the human QC programmer as the genuinely independent review layer. On the CDISCPilot01 benchmark, the framework achieved 97.1%–100% variable-level match across five ADaM domains and passed all 13 assertions. Companion code is publicly available.</description><pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate><category>QC programming</category><category>Claude</category><category>ADaM</category><category>CDISC</category><category>AI agents</category><category>automated code review</category></item><item><title>Schema-Preserving Generation of Clinical TLF Templates and Executable R Code via Iterative LLM-Guided Debugging</title><link>https://jaimeyan.com/papers/pharmasug-2026-ap-211.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2026-ap-211.html</guid><description>PharmaSUG 2026 — Manual authoring of CSR TLF templates is resource-intensive, and naive LLM prompting suffers schema drift and regulatory inconsistencies. This paper compares five LLM generation methods for producing ICH E3/CDISC-conformant TLF templates across 1,999 instance-matched bootstrap experiments on three LLM providers, using JSON Patch (RFC 6902) to preserve schema fidelity, and separately evaluates iterative LLM-guided debugging for translating the templates into executable R code. A hybrid RAG approach with reranking significantly outperformed direct prompting (mean quality score 85.7 vs 81.7, p &lt; 0.05, consistent across providers and therapeutic areas), and iterative LLM-guided debugging raised R-code execution success from a low zero-shot rate to 70% within 3–5 rounds, with higher-fidelity templates needing fewer iterations.</description><pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate><category>TLF templates</category><category>retrieval-augmented generation</category><category>LLM debugging</category><category>clinical study reports</category><category>ICH E3</category><category>ADaM</category><category>R code generation</category></item><item><title>GxP-Agent: Process-DAG Topology for Reliable Clinical Trial Programming with LLM Agents</title><link>https://jaimeyan.com/papers/gxp-agent.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/gxp-agent.html</guid><description>arXiv — LLM agents fail in regulated programming work when their execution is unstructured. GxP-Agent organizes clinical trial programming as a process DAG — typed nodes for data ingestion, derivation, validation, metadata application, and export — so that agent behavior is constrained, replayable, and auditable. The topology yields measurably higher task reliability than free-form agent loops and produces the evidence trails GxP review requires.</description><pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate><category>LLM agents</category><category>process DAG</category><category>GxP</category><category>clinical trial programming</category><category>reliability</category><category>CDISC-Bench</category><category>pharmaverse</category></item><item><title>Evidence Behind the Automation of Clinical Trial Statistical Programming: A Scoping Review of Technology Adoption, Validation Frameworks, and AI/ML Integration (2020–2025)</title><link>https://jaimeyan.com/papers/automation-scoping-review.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/automation-scoping-review.html</guid><description>medRxiv — This scoping review (reported per PRISMA-ScR) maps the 2020–2025 evidence base on automating clinical trial statistical programming — from macro-based tooling to LLM-driven approaches — characterizing study types, claimed efficiency gains, evaluation rigor, and open gaps. From 1,247 records, 262 studies were included; reported gains include 15–25% development-time reduction for pharmaverse TLF tools, 30–50% effort reduction for risk-based validation with CI/CD, and 75–85% SDTM conversion-time reduction for REDCap2SDTM, alongside 88–93% F1 for domain-specific LLMs on clinical NLP versus 60–85% code-generation accuracy for general models. Evidence quality is predominantly Low to Very Low: only 12 of 527 validation papers (2.3%) report quantitative outcomes, and no RCTs comparing validation approaches exist, defining the critical research priorities for the field.</description><pubDate>Mon, 29 Dec 2025 00:00:00 GMT</pubDate><category>scoping review</category><category>TLF automation</category><category>validation</category><category>statistical programming</category><category>clinical trials</category><category>automation</category><category>LLM</category></item><item><title>An End-to-End Approach to Fine-Tune Small LLMs for Generating Admiral R Code in Statistical Programming</title><link>https://jaimeyan.com/papers/phuse-2025-os08.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/phuse-2025-os08.html</guid><description>PhUSE US Connect 2025 — Base small LLMs perform poorly on Admiral code generation (OPS 0.36), and even strong general-purpose LLMs offer no built-in correctness verification for ADaM compliance. This paper presents an end-to-end pipeline for fine-tuning small, locally deployable LLMs on curated Admiral examples — fine-tuning LLaMA 3.1 8B with LoRA and validating output through a knowledge-graph system built from Admiral documentation. The pipeline covers data preparation, training, and evaluation, achieving reliable ADaM code generation without sending proprietary data to external APIs.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>fine-tuning</category><category>small LLMs</category><category>admiral</category><category>R</category><category>ADaM</category><category>LoRA</category><category>knowledge graph</category></item><item><title>Automating SAS and R Code Interpretation and Debugging: A Practical Pipeline for Statistical Programmers</title><link>https://jaimeyan.com/papers/phuse-2025-et01.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/phuse-2025-et01.html</guid><description>PhUSE US Connect 2025 — Statistical programmers spend substantial effort writing and debugging SAS and R code. This paper describes an LLM-based pipeline that translates natural-language queries into executable SAS, R, or Python code, runs it in a Jupyter kernel, captures runtime errors from the kernel, and feeds them back to the LLM for iterative repair until the code succeeds or a retry limit is reached, exposed through a Gradio-based user interface. Evaluated on a factorial corpus of 2,700 runs across Python, R, and SAS with injected syntax, runtime, and logical/statistical errors, the system achieved success rates above 96% across languages, resolving about 95% of syntax and 90% of runtime errors versus about 88% and 87% for logical and statistical errors.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>SAS</category><category>R</category><category>code generation</category><category>debugging</category><category>LLM</category><category>Jupyter kernel</category><category>statistical programming</category></item><item><title>Enhancing Clinical Trial Data Queries with LLMs and Neo4j: A Flexible Framework for ADaM Dataset Management</title><link>https://jaimeyan.com/papers/phuse-2025-dh03.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/phuse-2025-dh03.html</guid><description>PhUSE US Connect 2025 — This paper models CDISC ADaM datasets in a Neo4j graph database via a reusable graph schema derived from ADaM specification files, and uses LLMs with LangChain to translate natural-language questions into both Cypher and SQL queries, making data checking more flexible, particularly for ad hoc tasks. Benchmarked head-to-head on 90 protocol-derived questions over synthetic ADaM datasets (ADSL, ADAE, ADCM, ADLB, ADVS) held in both PostgreSQL and Neo4j, LLM-generated Cypher achieved higher accuracy than SQL (73.33% vs 66.67% overall), with the advantage holding across difficulty tiers.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>Neo4j</category><category>Cypher</category><category>graph database</category><category>ADaM</category><category>LLM</category><category>SQL benchmarking</category><category>LangChain</category></item><item><title>A Novel Pipeline for Generating Realistic Synthetic CDISC ADaM Datasets Using Large Language Models and Knowledge Graphs</title><link>https://jaimeyan.com/papers/phuse-2025-ml12.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/phuse-2025-ml12.html</guid><description>PhUSE US Connect 2025 — Creating synthetic ADaM data that faithfully represents real trial characteristics is challenging. This paper combines knowledge graphs built from clinical trial documentation (protocols, SAPs, CRFs) with Faker-based generation, using LLMs to enrich and reorganize the JSON schemas that drive data generation. A three-way comparison of direct JSON, LLM-enhanced JSON, and template-based generation shows the template-based variant achieving the highest overall quality score (0.70 vs 0.45 for direct JSON-schema generation), with improved structural integrity and cross-dataset relationships.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>synthetic data</category><category>ADaM</category><category>CDISC</category><category>knowledge graphs</category><category>LLM</category><category>Faker</category></item><item><title>GenAI Assisted Code Conversion: From SAS to R Standard ADaM Templates</title><link>https://jaimeyan.com/papers/pharmasug-2025-ai-239.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2025-ai-239.html</guid><description>PharmaSUG 2025 — As clinical trial Analysis &amp; Reporting shifts toward open-source languages, our organization needed to convert its SAS-based ADaM standards library to R. This paper presents a GenAI-assisted conversion methodology using a structured workflow of source pre-processing, logical code segmentation, and iterative prompt engineering that accumulates conversion instructions from previously converted templates, followed by human validation comparing converted R outputs against the validated SAS-generated ADaM datasets. Using ChatGPT-4o and Claude 3.5 Sonnet, the effort converted about 78% of the SAS ADaM templates, with about 66% of the converted code used without modification, though macro-heavy templates still required significant human intervention.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>SAS to R</category><category>code conversion</category><category>GenAI</category><category>ADaM</category><category>migration</category><category>prompt engineering</category></item><item><title>Comparing SQL and Graph Database Query Methods for Answering Clinical Trial Questions with LLM-Powered Pipelines</title><link>https://jaimeyan.com/papers/pharmasug-2025-si-342.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2025-si-342.html</guid><description>PharmaSUG 2025 — Should clinical data exploration use SQL or graph databases? This paper benchmarks both query paradigms behind LLM-powered natural-language pipelines on 150 representative clinical trial questions over synthetic ADaM data, comparing accuracy, latency, and the classes of questions each paradigm handles well. The proposed RagQL-Nav framework — query decomposition, intelligent routing, and dual-query validation — reached 91% accuracy on complex queries, roughly 12 points above single-system approaches, offering practical guidance on when graph approaches earn their complexity.</description><pubDate>Wed, 01 Jan 2025 00:00:00 GMT</pubDate><category>SQL</category><category>graph database</category><category>LLM pipeline</category><category>benchmark</category><category>clinical data</category><category>ADaM</category><category>query routing</category></item><item><title>AI-Enhanced Chatbot for Streamlined Clinical Trials Analysis and Document Management</title><link>https://jaimeyan.com/papers/phuse-2024-ic08.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/phuse-2024-ic08.html</guid><description>PhUSE US Connect 2024 — Statistical programming teams lose hours searching specifications, protocols, and analysis documentation. This paper describes a retrieval-augmented chatbot that indexes clinical trial documents and analysis artifacts and answers natural-language questions against the retrieved content, with a local-deployment option that keeps confidential documents and data in-house. A fine-tuned LLM also maps mock table shells to SAS macro calls for end-to-end TLF generation, with a SAS kernel executing the generated code.</description><pubDate>Mon, 01 Jan 2024 00:00:00 GMT</pubDate><category>chatbot</category><category>RAG</category><category>document management</category><category>clinical trials</category><category>LLM</category><category>fine-tuning</category><category>TLF generation</category></item><item><title>LLM-Enhanced Training Agent for Statistical Programming</title><link>https://jaimeyan.com/papers/pharmasug-2024-si-160.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2024-si-160.html</guid><description>PharmaSUG 2024 — This paper presents an LLM-enhanced training agent for statistical programming, implemented as a custom GPT-4 GPT built via prompt engineering with uploaded reference documents (SDTMIG, ADaMIG, ICH E9, and internal SAS guidance) and a slash-command interface. The agent guides learners through personalized curricula, lessons, and real-world simulation projects, tests their knowledge with quizzes and coding exercises, and gives immediate, personalized feedback, with positive feedback from a pilot testing phase.</description><pubDate>Mon, 01 Jan 2024 00:00:00 GMT</pubDate><category>training</category><category>LLM agent</category><category>statistical programming</category><category>CDISC</category><category>SAS</category><category>prompt engineering</category></item><item><title>Methodology for Automating TOC Extraction from Word Documents to Excel</title><link>https://jaimeyan.com/papers/pharmasug-2024-mm-226.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2024-mm-226.html</guid><description>PharmaSUG 2024 — Programmers tracking clinical study deliverables often transcribe the table of contents of SAP mock-shell Word documents into Excel trackers by hand. This paper presents an Excel-based VBA tool — chosen because company policy bars external tools — that extracts the TOC from Word mock-shell documents into an Excel tracker at the click of a button, locating the TOC field programmatically and stripping page numbers from entries. The resulting trace system supports monitoring each study deliverable’s progression and validation status.</description><pubDate>Mon, 01 Jan 2024 00:00:00 GMT</pubDate><category>VBA</category><category>TOC extraction</category><category>Word</category><category>Excel</category><category>mock shells</category></item><item><title>JSON Data Generation: Linking Statistical Analysis with Large Language Models</title><link>https://jaimeyan.com/papers/css-2024-pp02.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/css-2024-pp02.html</guid><description>PHUSE/FDA Computational Science Symposium (CSS) 2024 — This poster presents a framework that extracts schema from structured clinical datasets (e.g., CDISC ADaM) into JSON, uses it to design a graph-based database (Neo4j) with graph embeddings stored in a vector database, and enables LLMs to answer natural-language questions by retrieving relevant variables and generating SQL or Cypher queries — automating clinical data analysis workflows.</description><pubDate>Mon, 01 Jan 2024 00:00:00 GMT</pubDate><category>JSON</category><category>CDISC ADaM</category><category>Neo4j</category><category>Cypher</category><category>LLM</category><category>vector database</category></item><item><title>A Macro Utility for CDISC Datasets Cross Checking</title><link>https://jaimeyan.com/papers/pharmasug-2023-sd-084.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2023-sd-084.html</guid><description>PharmaSUG 2023 — CDISC validation tools such as Pinnacle 21 check standards compliance but not dataset content, and A&amp;R programmers need study- and therapy-area-specific checks throughout the analysis lifecycle. This paper presents a configurable SAS macro utility that systematizes cross checking across SDTM and ADaM datasets; its modular sub-macro framework lets users plug in custom checking rules, extensible beyond CDISC datasets. The macro generates a formatted Excel discrepancy report with a hyperlinked summary tab and one sheet per issue category, supporting faster data review cycles.</description><pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate><category>SAS macro</category><category>CDISC</category><category>cross checking</category><category>data quality</category><category>ADaM</category><category>SDTM</category><category>Excel report</category></item><item><title>Tips to Read In and Output Excel Spreadsheets in SAS</title><link>https://jaimeyan.com/papers/pharmasug-2023-qt-085.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/pharmasug-2023-qt-085.html</guid><description>PharmaSUG 2023 — Excel is widely used in clinical trials to save and transfer data, and analysis &amp; reporting programmers routinely receive spreadsheets and produce customized Excel reports for other departments. This paper collects practical techniques for reading different Excel formats (xls, xlsx, xlsm, xlsb, csv) into SAS via LIBNAME engines and PROC IMPORT — including how to choose between them by environment and format — and for writing well-formatted outputs with PROC EXPORT and ODS EXCEL. It offers practical decision tips for choosing import/export methods and output formats.</description><pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate><category>SAS</category><category>Excel</category><category>ODS EXCEL</category><category>PROC IMPORT/EXPORT</category><category>data exchange</category></item><item><title>A Framework for Interactive Ad-hoc Request Handling: Empowering Clinical Insights through Interactive Plots</title><link>https://jaimeyan.com/papers/css-2023-pp20.html</link><guid isPermaLink="true">https://jaimeyan.com/papers/css-2023-pp20.html</guid><description>PHUSE/FDA Computational Science Symposium (CSS) 2023 — This poster presents a framework for producing interactive plots to handle ad-hoc analysis requests in the clinical domain. It standardizes the end-to-end process — Anaconda-based environment setup, package version control via renv/pipenv lock files, Jupyter Lab as the IDE, interactive visualization with Plotly (Python) and ggplot2 plus Plotly/htmlwidgets (R), and portable self-contained HTML output — with results validated by crosschecking between SAS, R, and Python. Example outputs include swimmer, waterfall, and Kaplan-Meier plots with drop-downs and range sliders.</description><pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate><category>ad-hoc requests</category><category>interactive plots</category><category>Plotly</category><category>statistical programming</category><category>HTML output</category></item></channel></rss>