Skip to content

Echo: Workflow Redesign

Optimizing Clinical Trial Matching Through Real-World Workflow Validation

Clinical trials depend on finding the right patients, a process called eligibility screening. Echo is a system that automates this matching using AI-generated eligibility criteria.

Echo 2.0 is a workflow-driven redesign of that system, informed by interviews with trial managers and clinical research coordinators. Rather than a visual refresh, it restructures how eligibility logic is defined, reviewed, and safely executed within a single interface.

My Role
UX/UI Designer

User research synthesis, workflow redesign, interaction logic, high-fidelity prototyping

Team

Hua Xu, Robert T. McCluskey Professor
Huan He, Research Scientist
Ahmed Abdelhady, Software Engineer

Timeline & Status

3 months · handed off for implementation

Why Echo 2.0?

Interviews with professionals actively working on trial matching revealed that Echo 1.0 did not fully reflect real-world workflows.
Unclear Workflow

No clear path from defining eligibility criteria to producing a matched patient list, leaving coordinators without a reliable process to follow.

Insufficient Granularity

Eligibility criteria lacked the depth needed for real clinical decision-making, limiting how precisely a trial's requirements could be expressed.

The Core Problem

How can increasingly granular eligibility logic be supported within a single interface without overwhelming expert users?

The Redesigned Workflow

01
Define Criteria
Set minimum and specific eligibility criteria with inclusion and exclusion logic
02
Convert to SQL
Each criterion is translated into a validated SQL query that must match the text definition
03
Execute & Monitor
Queries run row by row with real-time progress and patient counts revealed only after completion
04
Review Matched Patients
Coordinators move to manual chart review with a filtered cohort ready for evaluation

Key Design Changes

01 — Reframing the Criteria Structure

Eligibility criteria were reorganized into two logical layers:

  • Minimum Criteria (MC): baseline eligibility requirements
  • Specific Criteria (SC): study-specific refinements

Each layer maintains explicit inclusion and exclusion logic. This structure mirrors how cohorts are progressively narrowed in real trial matching workflows.

Criteria structure redesign
02 — Managing Information Density at the Row Level

Each criteria row contains multiple states, actions, and outputs, making information density a core design challenge. To keep the interface scannable, primary information remains visible at all times while secondary actions are progressively disclosed.

Inclusion and exclusion logic is communicated through subtle color indicators with labels revealed only on hover. This lets users compare criteria, understand the impact, and take action without unnecessary cognitive load.

Row-level information density
03 — Treating Save, Convert, and Execute as Distinct Steps

Designing for safe execution required treating saving, SQL conversion, and execution as distinct actions rather than a single step. Criteria cannot be executed unless the generated SQL matches the textual definition, ensuring logical consistency before any results are produced.

Execution status, progress, and outcomes are always visible, making system behavior explicit and traceable. This approach prioritizes transparency and trust in high-stakes clinical workflows.

Interaction Highlights

Color-coded Eligibility

Inclusion and exclusion logic uses subtle color indicators with hover labels, letting coordinators scan criteria without reading every row in detail.

Deferred Patient Counts

Counts stay hidden until criteria are fully executed, preventing premature decisions before the logic has been validated end-to-end.

Row-level Progress

Execution status appears directly on each criteria row, keeping system activity visible at the point of action rather than a separate status panel.

These patterns are currently being further developed and validated on the MarketScan dataset.

Key Takeaways

  • Expert-facing systems demand different priorities than consumer products. Clarity and trust matter more than delight.
  • Complexity is best made legible, not reduced. The goal was to expose eligibility logic transparently, not simplify it away.
  • In high-stakes workflows, transparency and validation are core features. Every visible system state is a trust signal.