From a 22% failure rate and paper faxes — to a trusted, audit-ready clinical platform

A global biopharmaceutical client needed to digitise a fragmented, paper-based clinical onboarding process — reducing task completion time, eliminating compliance risk, and accelerating clinical trial activation across global sites. Each role required carefully controlled access, visibility, and permissions.

HCPs and Designees operated in what internal teams called the 'Paper Era'. Knowledge assessments were printed, signed by hand, and faxed with no confirmation of receipt. A 22% failure rate, zero status visibility, and persistent audit anxiety defined every trial activation cycle.

Before — Paper era

Prescriber Knowledge Assessment (paper form)

📠Print, sign by hand, and fax — no digital submission path

🕳Zero visibility after submission — a "black hole" with no tracking

⚠️22% failure rate — not from lack of knowledge, but poor form design

😰Persistent FDA audit risk from missing signatures and lost faxes

→

After — Digital portal

Welcome, Jennifer Williams — personalised, role-aware, step-visible

✅Personalised welcome — name, role context, and full 3-step certification path visible from step one

📊Assessment expectations set upfront — "10 MCQs, Approximately 10–15 Minutes, Answer all 10 Correctly to Pass"

📚Educational materials accessible as a prerequisite gate — not buried or optional

⚡98% first-time pass rate — confidence-first design, not speed-first

This wasn't a typical SaaS redesign. Every design decision operated under strict regulatory oversight. Rather than treating these as blockers, I reframed them as the design brief — each constraint became a feature the system had to make legible, not invisible.

All three roles share one navigation shell — but the content surface changes entirely based on who is authenticated. Pre-certification: Home, Resources, Contact Us only. Post-certification: My Patients, My Teams added. The nav itself signals completion status without any additional UI.

HCP PRODUCT FLOW · WORKING ARTEFACT Single-screen Multi-screen

KA & Enrolment branch

Multi-screen flow — the multi-screen designation directly informed the decision to design it as a gated, progressive flow rather than a single form.

My Teams — 4 Designee sub-flows

Invite Designee · Invite Support Staff · Manage Designee · Manage Support Staff. Structural evidence that justified elevating the Designee hub to P0 in Sprint 3.

Dashboard + Patient flows

Home/Dashboard → Enroll Patient + Create New Status Form → My Patients. The two core recurring workflows that became the Dashboard notification types and Status Form modal.

Before wireframing a single screen, I mapped the full HCP & Designee journey across 5 phases. The pain points row became the direct input to the three insights that shaped the entire design direction.

Healthcare Provider & Designee Journey Map — Dr. Jennifer Williams

RESEARCH ARTEFACT · PRE-DESIGN

Phase 1 — Sign-up

"Need for clear expectations around assessment length and estimated time of completion."

→ Insight 3: Users fear mistakes, not complexity

Phase 2 — Team Mgmt

"Would like to add non-licensed staff as designees to help with the workload."

→ Insight 2: Designees are the primary users

Phase 3 — Enrolment

"Users are unable to plan ahead for future echocardiograms while looking ahead on the calendar."

→ Dashboard: Calendar + Monitoring tabs

Phase 4 — Status Form

"Care teams need to carefully manage dozens of patients a month."

→ Insight 1: Visibility anxiety drives helpdesk volume

Phase 5 — Notifications

"Information fatigue — HCPs receive an influx of emails for each patient they oversee."

→ My Patients list: status + deadlines in one view

The Knowledge Assessment was the highest-stakes interaction — a formal FDA-required test HCPs must pass before prescribing. Research Insight 3 shaped every iteration.

Before — the paper form that created the 22% failure rate

PAPER ERA ARTEFACT

What the paper form told me before talking to anyone: Prescriber info, fax number, and 10 questions all on a single dense scroll — designed for print. The failure wasn't the users. It was a form built for single-session/single-person that was actually multi-person and multi-session. The journey map confirmed it.

After — the guided digital knowledge assessment flow (all 10 questions)

LIVE PROTOTYPE RECORDING

What changed: Same regulatory content, redesigned around how HCPs actually work. Personalised welcome. Assessment time and question count set upfront. One question at a time. Reference materials always in the right panel. 10/10 completion — then "Congratulations, you have successfully completed certification in the CAMZYOS REMS program."

Every screen addresses a user anxiety mapped in the journey map. The annotations connect the design decision to the pain point that drove it.

1 / 2

SCREEN 01 / ACCOUNT CREATION → PERSONALISED WELCOME

The entry point — role declared, path visible from step one

Sign-up requires NPI# — immediately establishing medical authority before the system invests in onboarding. The welcome screen that follows shows the full 3-step certification path (Education → Assessment → Enrollment) before any work begins. No hidden complexity. This directly addresses Phase 1 journey map pain: "need for clear expectations around assessment length."

Driven by Insight 3 — expectations set before commitment

1 / 4

SCREEN 02 / ASSESSMENT → CERTIFICATION COMPLETION

One question to "Congratulations" — the full arc

Questions 2, 6, and 9 show the range: multi-choice clinical questions and True/False regulatory knowledge, all in isolation with the reference panel always accessible. The completion screen — "Congratulations, you have successfully completed certification in the CAMZYOS REMS program" — is the most important screen in the entire flow. It's the moment the nav changes: My Patients and My Teams become visible for the first time.

98% first-time pass rate — up from 78%

1 / 2

SCREEN 03 / HCP ENROLLMENT FORM → SIGNATURE

Practice information + the deliberate final commitment

The enrollment form collects practice information (NPI, specialty, facility, contact preference) — all pre-populated where possible from the sign-up data. The signature screen closes with a legal-weight checkbox: "By checking this box... I acknowledge that this constitutes the equivalent of a hand-written signature." The date pre-fills to today. "Submit Enrollment" — not "Submit" — names the action precisely.

0 missing-signature compliance incidents post-launch

1 / 2

SCREEN 04 / MY PATIENTS LIST — COMPLIANCE COORDINATION HUB

7 patients, 3 status states, every deadline visible

This screen is the direct answer to Phase 4 & 5 journey map pain — "care teams managing dozens of patients a month" and "information fatigue." Seven patients sorted by submission deadline. Status badges in three states: Overdue (red), Eligible to Submit (green), Upcoming (amber). "Status Form Due" CTA per row. "Create a New Status Form" and "List of Certified Pharmacies" in the right panel. Export to Excel for offline compliance tracking.

Directly addresses Phase 4 & 5 journey map pain points

1 / 3

SCREEN 05 / DASHBOARD + PATIENT STATUS FORM

Notification surface → in-context coordination modal

The dashboard surfaces 5 named-patient notification types — each with a single CTA. "Complete Enrollment", "View Request", "Dismiss" — no ambiguity about what action is required. Clicking opens the Patient Status Form as an in-context modal, patient attributed by name ("Patient: Debbie A Min"), 4-step breadcrumb showing progress. Designees never lose their coordination context.

Designee hub elevated from P2 → P0 in Sprint 3

SCREEN 06 / CERTIFICATION COMPLETION STATE

The nav change that signals system trust — earned, not assumed

The certification completion screen does more than confirm success. It changes the nav. Before this screen: Home, Resources, Contact Us. After: My Patients and My Teams appear. The navigation expansion is the system communicating certification status — no separate notification, no modal, no badge. The product itself unlocks. "Download Document" preserves the signed certification record. "You are now eligible to enrol your patients."

Nav expansion as trust signal — no additional UI needed

In regulated enterprise UX, design decisions rarely live in a vacuum. When users asked "why can't I just fix a typo?" and Compliance said "signed records must remain immutable" — the conflict wasn't about permissions. It was about mental models of what 'editing' means in a regulated context.

All metrics compare the paper-based baseline against post-launch performance across a 3-month window.