StudyChaser

StudyChaser is a read-only portfolio demo of a regulatory training tracker for clinical study teams. It uses synthetic demo data to show how coordinators could monitor protocol and amendment training, spot overdue acknowledgments, and preview follow-up emails for study staff.

This public deployment is not production clinical or regulatory software. The hosted demo blocks data writes; local development can still exercise create, update, and delete routes.

Live Demo

https://studychaser.katalinalondono.com/

Why This Exists

Clinical trial teams often track protocol and amendment training through a mix of spreadsheets, inbox follow-up, shared drives, and memory. That makes it easy to lose sight of who still owes training, which study is affected, what was last sent, and what should be filed for audit readiness.

StudyChaser turns that workflow into a small product surface: study-level status, staff-level accountability, overdue training, coordinator ownership, and previewable follow-up language.

Project Structure

frontend/   React and Vite web app, route views, API client, and production redirects
backend/    Node.js API, data store, tests, and Cloudflare Worker deployment config

What It Does

• Shows a dashboard of overdue, awaiting, completed, and active-study training counts.
• Lists synthetic active studies with PI, coordinator, sponsor, and IRB details.
• Tracks each training item by staff member, status, last contact date, and filing note.
• Shows staff-level outstanding and completed training counts.
• Generates preview-only synthetic follow-up emails from backend templates.

Run Locally

Start the backend API:

cd backend
npm install
npm start

The backend runs at:

http://127.0.0.1:4000

Start the frontend app in a second terminal:

cd frontend
npm install
npm run dev

The frontend usually runs at:

http://localhost:5173

If that port is busy, Vite will choose the next available local port.

Backend API

The hosted Cloudflare Worker is read-only for portfolio review. It allows safe dashboard/review flows and email preview generation while blocking mutation routes in production.

Public demo routes are:

GET  /api/health
GET  /api/dashboard/summary
GET  /api/studies
GET  /api/people
GET  /api/trainings
POST /api/email/generate

Local development also includes write routes for experimenting with the workflow. See backend/README.md for the local route list and example requests.

Architecture Notes

• The frontend is a Vite/React app with route views for dashboard, studies, staff, training records, and email preview workflows.
• The backend exposes a small Node.js API that can run locally as an HTTP server or deploy as a Cloudflare Worker.
• Production/demo mode uses synthetic data and read-only protections so hiring reviewers can explore the workflow without creating or changing records.
• The data model is intentionally domain-specific: studies, people, training records, staff status, PI/coordinator ownership, IRB details, last-contact dates, and filing notes.
• Email generation is preview-only in the demo: it produces coordinator-ready follow-up language without sending real messages.

What I Would Build Next

• Authentication and role-based permissions for coordinators, PIs, regulatory staff, and read-only reviewers.
• An audit trail for training status changes, follow-up attempts, and filing notes.
• Notifications for overdue training and amendment acknowledgments.
• CSV/PDF export for monitoring visits, sponsor requests, and internal QA review.
• Integrations with CTMS/eTMF or document-management systems so training evidence and filing notes can connect to the rest of the clinical operations stack.
• More robust validation, pagination, filtering, and search for larger study teams.

Verification

Run backend tests:

cd backend
npm test

Build the frontend:

cd frontend
npm run build

Tech Stack

• React 18
• React Router
• Vite
• Node.js HTTP server
• JSON-backed local data store
• Plain CSS

Status

The frontend is connected to the backend API for dashboard data, studies, people, trainings, and email generation. The production build is configured as a read-only synthetic demo. The API can run locally with Node or on Cloudflare Workers with KV-backed storage.