04 / Clinical workflow

Trial Coordinator

How can someone turn a public trial record into a manageable list of studies, notes and next actions?

Personal study organizer · TypeScript / React / SQLite
Trial Coordinator prototype interface
Workflow diagram of the current study organizer: public trial lookup, saved context and dated tasks. Browser-local work or optional private account storage. This is a diagram, not a product screenshot. Open full-size visual ↗

Working result

Find public studies, organize tasks and notes, and optionally save a private account workspace.

Review status

Local account and conflict checks recorded. Hosted cross-device and coordinator review remain open.

Design decision

Protect work across sessions

  1. Load account revision
  2. Edit a personal workspace
  3. Save or retain a conflicting draft

A stale session cannot silently overwrite newer work. A rejected save keeps the draft available for backup and recovery.

The question

How can someone turn a public trial record into a manageable list of studies, notes and next actions?

What I built

A personal workspace for finding recruiting studies, saving public trial records and organizing the work around them. Search by condition and location or open an NCT identifier, add notes and dated tasks, mark work complete, and keep a calendar or backup copy. An optional signed-in account stores the workspace on the server.

How it works

A typed adapter validates ClinicalTrials.gov records. Saved studies retain public study information and facility contacts; users can refresh records and archive or restore studies. Task owners are labels, not invitations or notifications.

The default workspace saves in the current browser. The account workspace uses authenticated identity and a per-user SQLite record. Moving existing work into an account is explicit: export a backup, restore it in the account workspace, then save. No existing browser data is moved automatically.

Every account save carries a revision. If another session has saved newer work, the server rejects the stale write and the interface retains the unsaved draft. Failed saves also preserve the draft and offer backup guidance. Account records are private to their owner; this is not a shared team workspace.

Calendar downloads and validated JSON backups let someone retain their work outside the page. The earlier synthetic screening exercise remains separately available at /demo. Neither workspace accepts patient records or establishes trial eligibility.

Result

The public organizer supports real study lookup, notes, tasks, archive and restore, calendar download and backup recovery. Browser checks exercised these actions and reload persistence. The account release passed type checking, build checks, seven planner tests and three SQLite storage tests.

Local account-preview checks verified save and reload, isolation in storage tests, and two-session conflict handling without silently overwriting newer work. Hosted sign-in and phone-to-laptop use still need a real-device check. Coordinator feedback and measured impact remain open.

Repository

Browse the public repository ↗. The local source includes setup instructions, the application, tests and database migrations. Published migration history is preserved.

What I'd do next

Verify hosted account use across devices, then observe someone managing their own study tasks. Define membership and recovery before adding shared team access.

Next project ↗Entero