Radhika Autade

Triagen

AI-assisted haematology triage for faster, safer clinical decision-making

View Live Prototype

RoleUX Designer & Researcher

Timeline12 weeks

PlatformDesktop website

ScopeResearch → Concept → Prototype → Expert Testing → UI

Triagen interface on laptop
01Overview

The Triage Workflow That Made Clinical Decisions Harder

Haematology triage is the process of reviewing incoming referrals and deciding how urgently each patient needs specialist care. In the current workflow, nurses and clinicians manually review referral letters, lab values, scanned reports, and clinical notes before assigning a triage pathway.

The problem was not a lack of clinical data.

  • The problem was that the data was scattered, unstructured, and cognitively heavy to process under time pressure.
  • Nurses had to read long referral letters, cross-check abnormal lab results, judge urgency, and document decisions without a consistent interface designed for haematology triage. This created risk around missed patterns, inconsistent decisions, and delayed prioritisation.
  • Triagen was designed as an AI-assisted clinical decision-support interface that helps clinicians quickly prioritise referrals, understand AI reasoning, and retain full control over the final decision.
  • The system does not automate triage.
  • It structures clinical information, suggests a triage pathway, explains the reasoning, and lets the clinician accept or modify the decision with documentation.

DESIGN CHALLENGE

How might we design an AI-assisted haematology triage interface that helps clinicians quickly prioritise referrals, understand AI reasoning, and maintain full control over clinical decisions?

Why It Mattered

This was a high-stakes workflow design for clinical decision-making. When haematology referrals are difficult to scan, clinicians lose time, cognitive load increases, and urgent cases can be harder to identify. For conditions such as suspected leukaemia or malignant haematology cases, triage delays can directly affect patient care.

High cognitive load

Clinicians had to manually scan referral text, lab results, and reports while managing multiple complex cases.

Inconsistent decisions

Triage decisions could vary across clinicians, shifts, and institutions because there was no standardised support layer.

Low trust in AI

AI suggestions alone were not enough. Clinicians needed transparent reasoning, source evidence, and control before trusting any recommendation.

02Research Approach

A Structured 12-Week Process, Sequenced To Build Evidence

The project began with an experience audit of the current site, followed by a heuristic evaluation to surface usability problems before any users were involved. I then ran a survey with 23 respondents to validate and expand on those issues, used the findings to build personas and a journey map, and moved into moderated usability testing to observe real planning behavior. Design decisions followed directly from that evidence.

Discovery

01

Literature Review

Reviewed AI triage, clinical workflows, and decision-support research.

Research

02

Clinician Survey

Identified triage pain points, trust gaps, and AI workflow needs.

Ideation

03

Concept Ideation

Explored dashboard and AI decision-support concepts.

Prototype

04

Co-Creation

Mapped dashboard, case review, and clinical decision flows.

Validation

05

Expert Testing

Tested workflow clarity with three practising doctors.

Output

06

Final Interface

Refined AI reasoning, actions, documents, and Ask AI support.

03Key Findings

Clinicians Did Not Need More Information. They Needed Clearer Decision Support.

The research showed that haematology triage was not failing because clinicians lacked data. It was failing because the available data was hard to interpret quickly. Referral information was often long, inconsistent, and unstructured. Lab values and scanned reports existed, but clinicians still had to manually connect the evidence to the final triage decision.

The strongest finding was simple:
AI support would only be useful if clinicians could verify it.

Critical Finding

Clinicians did not want AI to make the decision for them.

They wanted AI to reduce the burden of finding, structuring, and explaining clinical evidence so they could make the final decision with more confidence.

What Was Breaking The Experience

The biggest problems clustered around four areas.

01

Unstructured referral review

Clinicians had to scan long referrals manually, increasing cognitive load and slowing urgent signal detection.

High Severity

02

Weak Prioritisation Support

Referrals lacked clear urgency, pathway, and document-completeness cues, forcing clinicians to prioritise manually.

High Severity

03

Need for AI Reasoning

Clinicians needed AI support that explained urgency, highlighted key clinical factors, and showed confidence behind each recommendation.

High Severity

04

clear Decision Actions

Clinicians needed accountable actions: accept the AI recommendation or modify it with a documented clinical reason.

medium Severity
Where Triage Nurses Got Stuck
01

Reviewing Referral Information

Clinicians had to read through long referral notes to find the important details. This made it harder to spot urgent clinical signs quickly.

02

Connecting Evidence To Urgency

Key details like lab results, history, mutations, and risk factors felt disconnected. Clinicians needed a clearer explanation of why a case was marked urgent.

03

Making The Final Decision

The prototype needed to clearly show that triage nurses make the final decision. AI could support the review, but nurses needed clear actions to confirm or modify the decision with a reason.

04Collaborative Concept Development

Fixing The Workflow Before Refining The UI

The early wireframes focused on workflow structure, information hierarchy, and decision logic. The goal was to validate whether clinicians could move through the triage process without unnecessary context switching.

Wireframe and concept sketches
05Expert Testing

Clinical Feedback Made The Design Sharper

Think-aloud testing with three practising doctors helped evaluate whether the interface matched real clinical reasoning. The testing was especially useful because doctors could identify where the prototype looked clear from a UX perspective but still failed clinical expectations.

What experts told us :

01

AI Transparency Was Not Optional

Doctors wanted clinical factors, sources, and reasoning behind each recommendation.

02

Workflow Fit Needed Improvement

The interface had to support scan PDFs, appointment type, and triage notes.

03

Decision Actions Were Unclear

Clinicians wanted clear authority to accept or modify the AI recommendation.

04

Quick Reasoning Support Was Useful

Experts wanted an Ask AI feature for fast case-specific questions.

Testing Signals That Changed The Design

01

Before: AI reasoning was presented as a short explanation.

After: Added "Why This Urgency?" with clinical factors and confidence.

02

Before: Decision actions felt overlapping and unclear.

After: Used two actions: Accept AI Decision or Modify AI Decision.

03

Before: Lab values were not visually distinct enough.

After: High and low lab values were marked with directional indicators to improve scanability.

04

Before: Reports and scans were not easy to access.

After: Scans and PDF reports were added into the case review workflow.

06Design Strategy

Explainable AI. Clinician-Led Decisions.

Based on the research and testing, the design strategy focused on reducing cognitive load while preserving clinician authority. The interface needed to help clinicians understand urgency quickly without making the system feel like a black-box decision-maker.

01

Prioritisation Clarity

The dashboard needed to organise incoming referrals around clinical urgency, triage pathway, and document completeness.

CRITICAL
02

Explainable AI Reasoning

Every AI suggestion needed visible evidence, confidence level, and clinical reasoning.

CRITICAL
03

Clinician Control

Clinicians needed clear accept or modify actions, with required documentation when changing the AI suggestion.

CRITICAL
04

Document Completeness

The interface needed to show whether supporting documents were available before decisions were finalised.

HIGH
05

Workflow Continuity

The experience had to keep overview, evidence review, AI reasoning, and final decision-making connected in one workflow.

MEDIUM
07Final Design

Making AI-Assisted Triage Easier To Review, Trust, And Control.

The final desktop interface focused on helping triage nurses review referrals faster, understand AI recommendations, and make accountable clinical decisions. The design was not created to let AI decide independently. It was designed to make urgency, evidence, documentation, and final nurse-led decisions easier to manage in one connected workflow.

Case Dashboard: Clearer Referral Prioritisation

The dashboard gives triage nurses a structured view of all incoming cases. Cases are organised by triage decision, status, referral reason, assigned clinician, and completion level. This helps nurses identify urgent referrals faster instead of manually scanning disconnected case information.

Case Dashboard: Clearer Referral Prioritisation

Workspace Controls: Better Shift And Case Management

The workspace panel supports real clinical triage work beyond the case list. Nurses can control visible columns, manage alerts, pin doctors, set refresh preferences, and write shift handover notes. This makes the dashboard more useful during active clinical shifts.

Workspace Controls: Better Shift And Case Management

Case Review: Evidence And AI Reasoning In One View

The case review screen connects patient details, referral notes, lab values, AI assessment, and triage reasoning in one place. The "Why This Decision?" section explains the clinical factors behind the recommendation instead of only showing a confidence score.

Case Review: Evidence And AI Reasoning In One View

Accepted Decision State: Clear Nurse Accountability

After the nurse accepts the AI triage decision, the interface shows the decision status and who accepted it. This makes the final clinical action visible, documented, and accountable.

Accepted Decision State: Clear Nurse Accountability

Modify Decision Flow: Controlled Override With Reason

When the nurse disagrees with the AI recommendation, the modify flow requires an alternative triage decision and a reason. This keeps clinician authority clear while making changes traceable.

Modify Decision Flow: Controlled Override With Reason

Modified Decision State: Updated Triage Outcome

After modification, the case updates to show the final nurse-selected decision and documentation. The interface keeps the original AI reasoning visible while clearly showing the nurse's final decision.

Modified Decision State: Updated Triage Outcome
09Outcome & Reflection

PRIORITISATION

Referrals were organised by urgency, decision type, assignment, and status so nurses could identify high-risk cases faster.

AI EXPLAINABILITY

AI recommendations showed clinical factors, lab trends, and reasoning instead of only giving a summary.

CLINICIAN CONTROL

Nurses had clear actions to accept or modify the AI recommendation, keeping the final decision clinician-led.

DECISION TRACEABILITY

Any modified decision required a reason, making changes visible, trackable, and clinically accountable.

What I Learned

This project taught me that AI in healthcare should not be designed to replace clinical judgment. It should reduce the effort required to review complex information while keeping the clinician fully in control of the final decision. The most important design challenge was creating trust through visibility. A confidence score alone was not enough. Clinicians needed to see the evidence, understand the reasoning, review the source information, and know exactly how to act on the recommendation. I also learned that safety-critical interfaces need restraint. More features do not automatically make the product better. The value came from simplifying the workflow, making urgent information easier to scan, and turning AI output into something clinically reviewable, explainable, and accountable.

Coffee? Let's Build Something Thoughtful.

I’m open to conversations about product design, UX strategy, AI experiences, and teams building work that genuinely helps people.

Radhika Sunil Autade

Phoenix, Arizona

© 2026 Radhika Sunil Autade. All rights reserved.