- 1
Natural-language question
e.g. how persistent are patients on drug X after first line
- 2
LLM interpretation
parsed intent and time windows, kept separate from code
- 3
Cohort specification
editable assumptions with validation checks
- 4
Deterministic SQL + stats
DuckDB cohort build, persistence estimates
- 5
Auditable output
results with review flags and provenance
Question → auditable answer, in five steps
Independent project
In evaluationRWE Insight Copilot
I built an AI-powered copilot that translates natural-language treatment-persistence questions into structured cohort specifications, connecting pharmaceutical analytics needs with reproducible study workflows. An auditable workflow separates LLM interpretation from deterministic cohort and statistical code, with editable assumptions, instrumented validation checks, and analyst review flags.
Editable assumptions, review flags
Analysts can adjust time windows and inclusion rules, and see validation checks before trusting any output.
Evaluated on 30 hand-checked questions
Specification accuracy, clarification behavior, and summary faithfulness measured before any release.
- Python
- DuckDB
- Claude API
- Streamlit
