Validcare · vcflow · eCOA Slice 1

Clinician Per-Participant View — Reviewer Walkthrough

Thanks for taking the time to look at this. The mockup below shows what a study coordinator would see when they open one enrolled participant's record in vcflow. The goal of your review is to flag what feels foreign or unfamiliar against the way you work today, and what reads as a real improvement. Everything you see uses synthetic data — there is no real patient information anywhere in this walkthrough.

Open the interactive mockup

Five participant states + a Coordinator / Monitor role toggle. ~10–15 min to walk fully. Best viewed on a desktop or laptop.

Walk the mockup →

How to walk it (suggested order)

  1. Switch fixtures in the top bar. Fixtures 1–5 show different stages of one participant's trial journey (newly enrolled → visit in progress → awaiting PI signature → overdue → out-of-window handling). Watch how the journey rail (left) and the work surface (right) re-scope for each state.
  2. Toggle Coordinator → Monitor. The top bar has a role pill. Monitor mode hides coordinator action buttons and reveals an in-context "Raise query" affordance per form row. Click one to see the pre-filled composer.
  3. Click the recommendation banner. In fixtures 2, 3, 4 the banner is a pointer — it highlights the zone where the recommended action lives, and clicking scrolls there.
  4. In fixture 5, expand the Past tier. See the three sub-states that can coexist: Complete, Data outstanding (soft window — still collectable), and Missed (hard window — read-only). Click the Visit 2 — Missed row to see the record-deviation-reason flow.
  5. Try the route-to-signature flow. In fixture 3, click "Route to signature." The pre-submit confirmation summarizes what's being signed before the e-signature request fires.

Most things on screen are clickable; nothing actually submits anywhere. Resize the browser window — text reflows dynamically (it isn't fixed-height images).

Conventions Honored vs. Broken

~5 min read. The deliberate design choices the mockup makes against Veeva Vault EDC and Medidata Rave, classified by why we made each break (wedge, deliberate simplification, scope-deferral, or matching convention).

Full design rationale (deep dive)

~15 min read. The complete v2 design doc — premises, the eight design questions, the journey-engine model, and all the design decisions behind what's in the mockup. Optional; skim if a specific choice surprises you.

Feedback

Send observations, questions, and "this would never work at a site because…" candidly to shardin@validcare.com. Specific is better than general — name the fixture, the zone, and the concern.

Heads-up: What you're looking at is a design mockup, not a working app. Buttons that look interactive may open a dialog or scroll a zone, but no data is saved anywhere. Treat anything you click as a sketch.