Clinical Research Philadelphia
Private · view-only

What we built

A look at the operations platform we built for our research site on the Claude Code CLI — so we can compare notes across the three sites: where we overlap, and where someone's doing something the others aren't.

For the two of you only. Please don't redistribute — this page is access-gated to your emails.

The short version

The day-to-day operations of our site, mostly on autopilot — so the team handles the exceptions, not the busywork.

Getting patients in

Auto-collect leads from website + ads, auto-check who qualifies for which study, book online with reminders, and win back no-shows.

Running the day

One screen for every visit and what's missing — and it catches scheduling mistakes (double-bookings, wrong site, wrong time) before they happen — and we're adding a cross-site duplicate-enrollment guard.

Handling the messages

Reminders/confirmations sent automatically with guardrails, AI reads & routes faxes + voicemails, and (early) an AI voice pre-screen.

Getting paid

Track revenue / invoices / what's owed, show profit per study, a bot updates the billing system, and (built, off) auto-collections.

Safe & compliant

Role-based access + patient-data protection, daily auto data-checks with an audit trail, and an automatic test behind every rule.

Not drowning in busywork

Dozens of scheduled jobs run all of this, and assistant agents flag what needs attention — a human approves before anything goes out.

Go deeper (optional)

Add your own column

Want to see your site next to ours? One paste into your Claude Code reads your repo and builds your map (and, if you like, your own decks) — then it lands on the comparison above automatically. Nothing to fill in by hand.

Clinical Research Philadelphia, LLC · Aneesh Vaze · aneesh@phillyresearch.com
This is a private, view-only page shared with you directly. Nothing proprietary here — capability level only.