Enterprise · Healthcare AI · Anonymized case study

From a questionto an evidence-backedinsight.

An intelligence workspace for a global pharmaceutical company — unifying research, prescribing, referral and account data into a single trusted, AI-assisted experience.

Client
Global pharmaceutical company
Product
AI Insights Hub
Platform
Enterprise web application
Industry
Healthcare & life sciences
Role
Product / UX Designer
Duration
3 months
Scope: IA · user flows · wireframing · interaction design · UI · prototyping · design-system development.Primary users: field representatives, medical teams, insight teams, regional leadership.
01Overview

An intelligence workspace, not another dashboard.

A global pharmaceutical company was building a scalable AI platform to help teams access business and medical insights without navigating multiple disconnected systems.

It brought together qualitative research, quantitative data, field interactions, prescribing behaviour, referral activity and account-level intelligence in one enterprise experience. I designed an integrated platform combining natural-language AI conversation, HCP and account search, prescribing and patient insights, referral-network visualisation, pre-engagement planning, contextual filters and comparisons, evidence and feedback controls, and administrative tools.

The objective: move beyond static dashboards to a workspace where users explore data, ask follow-up questions, and understand the evidence behind every insight.

02Design Problem

Make complex intelligence easy to access — without oversimplifying it.

Medical and field teams worked with information distributed across several systems and formats. Preparing for an engagement meant manually searching, comparing and interpreting from many sources.

Fragmented information

Prescribing data, patient activity, account relationships, field notes and referral patterns lived in different places — no unified view of an HCP or account.

Complex data exploration

Users needed to move fluidly between account-, HCP- and network-level information while keeping the context of their original question.

High information density

Referral networks, eligibility, prescribing and time-based comparisons carry huge amounts of information that must be surfaced without overwhelm.

Limited trust in AI answers

In enterprise healthcare, an answer can't be an unsupported recommendation. Users need its source, scope, timeframe and limitations.

Multiple roles & use cases

Field, medical and insight teams need different depth — quick pre-engagement prep and deeper analytical exploration alike.

How might we

…create a trusted AI-assisted workspace that helps healthcare teams move from a question to an evidence-backed insight without searching across multiple systems?

03Process

An iterative enterprise-product process.

Existing-experience audit. The earlier experience was heavily form-based — users configured several fields before an answer appeared, with dense, text-heavy results and little support for exploration or follow-up.

Requirements & use-case mapping. Searching for an HCP or account, preparing for engagements, natural-language Q&A, prompt suggestions, conversation history, prescribing/patient summaries, referral exploration, comparisons, contextual filtering, response feedback, and administration — organised into one shared architecture, not independent dashboards.

Information architecture. Three primary layers:

  • Entity selection — search for an HCP or account
  • Insight exploration — structured summaries, charts and networks
  • Conversational investigation — ask and follow up without losing context

Iteration & cross-functional review. The file carried multiple workflow states and separate annotations for design, development and business stakeholders — so behaviour, data needs and edge cases were reviewed before handoff.

04Wireframes

Architecture first, visuals later.

Wireframes established the product architecture and validated the relationship between search, dashboards and AI conversation before applying the visual system.

  • Entity search — name, type, identifiers, recent entities and previous conversations, so answers always attach to the correct entity
  • Conversational workspace — persistent composer, suggested prompts, history, bookmarks, responses, follow-ups, sources and feedback
  • Insight dashboards — summary → key metrics → AI insight cards → charts → referral networks → detailed tables → contextual chat
  • Filter & comparison flows — default, open, applied, custom, account vs. account, period vs. period, reset
  • Safety & feedback flows — intended-use acknowledgement, limitations, sources, disclaimers, thumbs feedback and optional written feedback
05UI Design · Interface

The product, screen by screen.

Key flows recreated and fully anonymized for portfolio presentation — conversation, explainable responses, entity intelligence and the referral network.

app.insights-hub.internal
AI Insights Hub
Your intelligence assistant
Ask a question, or start from a suggestion
What are the key insights for this healthcare professional?
Summarise prescribing trends from the past six months.
What factors may be influencing treatment behaviour?
Summarise recent field interactions.
How has the account changed vs. the previous period?
Which HCPs are most connected in this network?
Ask about an HCP, account or network…Ask
Conversational workspace · prompt suggestions
app.insights-hub.internal
AI Insights Hub
Summarise prescribing trends for this account over the past six months.

Prescribing for this account increased steadily across the period, led by two high-volume specialists. Referral inflow from the regional network also rose.

Key signals
  • • Volume up vs. prior period [1]
  • • Strong in-network referrals [2]
  • • Two emerging prescribers identified [3]
Sources · Timeframe · Disclaimer
AI-assisted · verify against source before acting
AI response · sources, disclaimer & feedback
app.insights-hub.internal
AI Insights Hub
Dr. A. Rivera — HCP Intelligence
Cardiology · Metro Health System · Territory 4
Filters
1,284
Patients
312
Referrals in
97
Referrals out
+8%
Trend
Prescribing over time
AI key insight

Growth is concentrated in two indications; referral strength suggests expansion potential.

HCP intelligence dashboard
app.insights-hub.internal
AI Insights Hub
Referral Network
Network Map Table
Metro Health System
In-network · 312 patients · 6 connected HCPs · Territory 4
Referral-network visualisation
Interaction principles

Trust, built into the workflow.

Explainable by default

Every response can expose its sources, timeframe and a usage disclaimer — AI positioned as support, not absolute guidance.

Progressive disclosure

Summary-first cards, collapsible sections, tabs, drawers and detail-on-demand tables keep complexity accessible.

Filters as comprehension

Active filters stay visible so users always know which data is shaping a chart or answer.

Context that persists

The selected HCP, account, filters and timeframe carry across dashboards and conversation.

Design system

One system across chat, analytics & admin.

A component-led foundation — so the platform can extend to new data domains and AI agents without redesigning its patterns.

Semantic colour roles
Primary · info · states · surfaces
Components
ButtonsInputsDropdownsTablesCardsTabsChartsDialogsFeedbackEmpty states
Coverage
  • Conversational patterns
  • Analytical dashboards
  • Administration & config
06 · Impact

A unified framework for accessing and interpreting intelligence.

Reduced movement between disconnected reports and systems
Shortened the path from entity search to actionable insight
Combined structured dashboards with natural-language exploration
Made complex referral & patient relationships easier to interpret
Preserved context across search, filtering, analysis & conversation
Improved confidence in AI outputs via visible sources & disclaimers
Supported multiple roles through progressive levels of detail
Created a scalable foundation for additional intelligence modules

Described as product & usability outcomes — the file contains no verified production metrics, so no quantified results are claimed.

07Learnings
  • AI trust must be designed in — sources, limits and feedback belong in the core workflow, not a footer.
  • Conversational and analytical modes serve different needs; together they beat either alone.
  • Context (HCP, account, filters, timeframe) must persist across dashboards and chat.
  • Progressive disclosure is essential for dense enterprise dashboards.
  • Filters explain what you're viewing — keeping them visible prevents misreading a subset.
  • Feedback should be low-effort: quick thumbs, with optional written detail.
  • Scalable AI products need reusable interaction patterns for search, prompting, evidence and feedback.
This case study is fully anonymized. The client is referred to only as a global pharmaceutical company, all screens and data are recreated with generic placeholders, and no confidential names, brands or metrics are shown.