Clinical Informatics
I built a synthetic study workflow that moves from protocol requirements to linked data, record-level checks, operational metrics and an interactive dashboard.

What I was asked
It gives me a concrete way to practise the reasoning between clinical data structures and the decisions people need to make from them.
What I did
- Protocol
The workflow begins with a study-style protocol and translates its population, visit schedule, assessments and operational questions into fields and relationships.
- Linked tables
A fixed seed then generates linked site, participant, visit, laboratory, adverse-event, query, protocol-deviation and milestone tables.
- Validation
Validation happens at record level before the project produces study and site summaries.
- Review
Adverse-event follow-up, missingness and validation issues.
What it changed
The build regenerates the synthetic tables, reports and figures from the same seed.
Tests compare isolated builds and GitHub Actions runs linting, behavioural checks, coverage and the project build.