Enterprise engagement · Enterprise Healthcare SaaS
Clinical Assessment Platform — Redesigning Legacy Record Discovery
Transforming a system-oriented clinical research record discovery experience into a clearer, more contextual and workflow-oriented enterprise interface.
Overview
The legacy experience organized clinical research records through a system-oriented navigation structure, basic dropdown filters and a dense table combining concepts, instructions and endpoints. Although records were searchable and their metadata was available, the interface offered limited contextual visibility into how these records related to one another, making discovery and navigation across connected records less intuitive.
The redesign focused on dedicated record libraries, clearer information hierarchy, contextual metadata and a connected Relationship Explorer.
Problem statement
Problem Statement
The legacy experience organized clinical research records through a system-oriented navigation structure, basic dropdown filters and a dense table combining concepts, instructions and endpoints. Although records were searchable and their metadata was available, the interface offered limited contextual visibility into how these records related to one another, making discovery and navigation across connected records less intuitive.
Design goals
Design objectives, not proven business results
The goals were framed as design objectives for making the discovery experience clearer and more contextual.
- Improve record discovery: separate concepts, instructions and endpoints into dedicated libraries.
- Improve contextual understanding: make relevant metadata and selected-record details easier to inspect.
- Clarify relationships: make the Concept → Instruction → Endpoint progression understandable.
- Establish a clearer information architecture: document a more workflow-oriented direction for the broader platform.
Understanding the problem
A dense mixed-record table made relationships harder to read
The supplied legacy screen showed concepts, instructions and endpoints in one dense table, with Module, Therapeutic Area and Status dropdowns. Record types and their relationships were not sufficiently differentiated in the table.
Design decisions
Making record discovery more contextual
The redesign focused on four visible decisions supported by the supplied screens.
- Dedicated Record Libraries: separate Concepts, Instructions and Endpoints into focused discovery views, each presenting relevant information for its record type.
- Scoped Search and Filters: provide record-specific discovery controls and visible classification or status information where demonstrated in the supplied designs.
- Contextual Details: present selected-record information alongside the list, helping users inspect metadata without losing the broader discovery context.
- Relationship Explorer: show the selected concept, its related instructions and the endpoints associated with the selected instruction in a connected three-column workspace.
Before vs After
Three comparisons across the existing screens
The Before vs After view compares the legacy mixed-record table with the redesigned discovery experience without implying that three separate legacy screens were supplied.
- 01 — Record Discovery & List View: before, a dense mixed-record table with limited differentiation between concepts, instructions and endpoints; after, a dedicated Concepts library with classification, related-instruction counts and contextual details.
- 02 — Search & Filter Experience: before, basic dropdown filters applied to a mixed-record table; after, dedicated Concepts, Instructions and Endpoints libraries with record-specific discovery and contextual information.
- 03 — Relationship Explorer & Contextual Details: before, the legacy table did not make relationships between record types immediately apparent; after, the Relationship Explorer shows the selected concept, related instructions and associated endpoints together. The expanded and collapsed sidebar screenshots represent two states of the same workspace.
Information architecture
Platform direction separated from the implemented discovery path
The proposed high-level IA moves from system-oriented navigation toward more workflow-oriented destinations. It is a documented direction, not evidence that every destination was implemented or validated.
The redesigned discovery experience demonstrated in the supplied screens follows Concept → Instruction → Endpoint → Relationships. The Relationship Explorer provides a connected view of the selected records.
Outcomes
Design improvements supported by the supplied screens
The outcomes are described only as improvements supported by the supplied designs, without quantitative claims, time savings, conversion rates, usability test results or validated business impact.
- Dedicated libraries for different record types.
- Clearer presentation of record metadata and contextual details.
- A more explicit Concept → Instruction → Endpoint discovery path.
- A connected workspace for exploring related records.
- A documented, more workflow-oriented direction for the broader information architecture.
Next case study
Clinical Review — Digital Document
Healthcare · Enterprise collaborationContact
Let’s talk about the problem, not just the solution.
I’m open to senior product design, UX leadership, design systems, and AI-native product opportunities.
Get in touch