CHAMELEON EMR
Redesigning a high-density clinical system around attention, context, and speed.
A concept redesign exploring how clearer information hierarchy and more connected workflows could reduce cognitive load across patient records, scheduling, and clinical decision-making.
ROLE
Product Designer
FOCUS
UX Research · Information Architecture · Interaction Design · UI Design
PROJECT TYPE
Concept redesign based on real physician workflows
WHY THIS PROJECT MATTERED
Growing up with a physician in my family exposed me to how fragmented clinical systems can pull attention away from patient care.
That made workflow clarity feel less like a visual design problem and more like an operational one.
THE CHALLENGE
Reduce cognitive overload in a complex hospital EMR without removing the information clinicians depend on.
Clinical systems need to surface large amounts of information while supporting fast, high-stakes decisions.
The challenge was not to make the system simpler by hiding complexity — it was to make that complexity easier to understand and navigate.
CONTEXT & CONSTRAINTS
Designing for an environment where attention is limited, but information cannot simply disappear.
Several constraints shaped the design direction:
High information density
Clinical interfaces need to surface large amounts of patient data without overwhelming the user.
Time-sensitive decisions
Physicians often need to understand patient status quickly while managing multiple tasks.
Frequent context switching
Patient history, medication, appointments, vitals, and reports often live across separate areas of the system.
Existing mental models
A redesign still needs to feel predictable to users already familiar with established clinical workflows.
These constraints changed the goal of the project.
Instead of minimizing information, I focused on improving hierarchy, proximity, and predictability.
RESEARCH
Understanding where complexity becomes friction.
I conducted an expert interview with a practicing physician and reviewed existing clinical workflows to understand where information overload and context switching created the most friction.
Rather than focusing only on preferences, I looked for recurring workflow questions:
-
What information needs to be understood immediately?
-
Which data is checked repeatedly throughout the day?
-
Where do clinicians lose context?
-
Which actions require unnecessary navigation?
-
What can remain secondary until it becomes relevant?
The research revealed three patterns that directly shaped the redesign.
INSIGHT 01
Physicians scan before they read.
In time-sensitive workflows, users often need to understand patient status before reading individual data points in detail.
This meant the interface needed to communicate priority visually.
Design implication
Critical information should be recognizable at a glance through hierarchy, grouping, and contrast.
INSIGHT 02
Every screen change has a cognitive cost.
When related information lives across separate areas of the system, users need to repeatedly rebuild context.
The problem was not simply the number of clicks — it was the mental effort required after each transition.
Design implication
Related information and high-frequency actions should stay closer to the workflow where they are needed.
INSIGHT 03
Equal visibility does not mean equal importance.
Dense interfaces can technically expose all necessary information while still making the most important information difficult to find.
Design implication
The first layer of the interface should prioritize immediate decisions, while supporting information remains available progressively.
FROM INSIGHTS TO STRATEGY
The research led to three priorities for the redesign:
1. Strengthen information hierarchy
Help users identify what deserves attention first.
2. Reduce unnecessary context switching
Keep related information and actions closer together.
3. Preserve access to complexity
Simplify the experience without oversimplifying the underlying clinical information.
PRIORITIZATION
I focused on the workflows where information density and context switching had the highest impact.
An EMR contains far more workflows than could reasonably be redesigned within the scope of this project.
Instead of treating every screen as equally important, I prioritized four areas that represented different types of complexity:
Dashboard
The orientation problem
The dashboard is the clinician’s starting point and needs to answer one question quickly:
What requires my attention right now?
This made it the right place to explore prioritization, hierarchy, and scanning behavior.
Patient Records
The information-density problem
Patient records bring together medical history, medications, vitals, laboratory results, and other clinical information.
This workflow became the main test for whether the redesign could improve scanability without hiding necessary detail.
Scheduling
The context-switching problem
Scheduling often connects administrative actions with patient-related decisions.
I used this workflow to explore how common actions could remain closer to the clinical context instead of forcing users through disconnected areas of the system.
Reports
The interpretation problem
Reports require users to move between high-level patterns and detailed data.
This made them a useful test for progressive disclosure and information hierarchy at a different level of complexity.
SCOPE DECISION
I intentionally did not attempt to redesign the entire EMR.
The goal was to establish a set of reusable interaction and information principles across representative workflows first.
If the concept were developed further, I would validate those patterns before extending them to additional modules.
This helped keep the project focused on system-level decisions rather than the number of screens produced.
DESIGN PRINCIPLES
Four principles guided every design decision.
Surface critical information first
Important patient information should be visible without requiring users to search for it.
Preserve context
Related information and common actions should remain close to the workflow where they are needed.
Make patterns predictable
Navigation, layout, and interaction patterns should behave consistently across the system.
Reveal complexity progressively
Supporting information should remain accessible without competing with the user's immediate task.
DESIGN DIRECTION
One question guided every screen:
What does a physician need to understand in the first three seconds?
That question became a filter for deciding what deserved immediate visual priority.
Critical information appears first.
Supporting information remains available without dominating the interface.
Common actions stay visible and predictable.
This created a consistent hierarchy across workflows rather than treating every screen as an independent design problem.
KEY SCREENS
Each one rethought around the same question: what does a doctor need to see in the first three seconds?
BEFORE
AFTER
DECISION 01 — DASHBOARD
Make the starting point of the day immediately understandable.
Problem
The original dashboard presented many elements at similar levels of importance, forcing users to scan the interface before understanding what required attention.
Decision
I reorganized the dashboard around three priorities:
-
Today's patients
-
Urgent alerts
-
Frequently used actions
Secondary modules were moved lower in the hierarchy.
Trade-off
Showing more information above the fold could provide faster access to secondary tools, but it would also recreate the competition for attention I was trying to solve.
I prioritized orientation over maximum information visibility.
Why it matters
The dashboard now establishes a clearer starting point and reduces the amount of information competing for attention at once.
BEFORE
AFTER
DECISION 02 — PATIENT RECORDS
Improve scanability without hiding clinical detail.
Problem
Medical history, medication, laboratory data, and other patient information were visually dense and difficult to distinguish quickly.
Design decision
I introduced a stronger hierarchy by:
-
Structuring patient history into distinct sections
-
Increasing the priority of medication information
-
Grouping laboratory information by relevance
-
Increasing typographic contrast
-
Reducing competing visual elements
Trade-off
A visually minimal patient record would be easier to scan, but removing or excessively hiding information could make clinical work slower. Instead of reducing the amount of information available, I reduced the amount competing for first attention.
Why it matters
The interface helps users identify important information first while keeping supporting data accessible.
DECISION 03 — SCHEDULING
Keep scheduling actions connected to the clinical workflow.
Problem
Scheduling actions existed separately from surrounding patient workflows, creating additional navigation and context switching.
Design decision
I designed the calendar around:
-
Quick appointment actions
-
Visible conflict indicators
-
Shallower navigation
-
Clearer transitions between appointments and patient records
Trade-off
Adding every possible scheduling action directly to the calendar would reduce navigation but increase interface density.
I kept only high-frequency actions immediately available and preserved deeper actions for secondary layers.
Why it matters
Common scheduling tasks remain closer to the context in which users need them without turning the calendar into another overloaded screen.
DECISION 04 — REPORTS
Help users identify the signal before exploring the data.
Problem
Reports contained large amounts of information without enough visual prioritization.
Design decision
I reorganized reporting around:
-
Visual summaries
-
Charts
-
Clear filtering
-
Progressive disclosure of detailed data
Trade-off
Charts can improve pattern recognition, but relying too heavily on visualization can make precise values harder to inspect.
The design therefore uses summaries for orientation while keeping detailed data available for deeper analysis.
Why it matters
Users can understand the overall pattern first and investigate specific details only when needed.
WHAT I INTENTIONALLY DIDN'T DO
Making the interface look simpler was never the goal.
I avoided three shortcuts that could have made the redesign appear cleaner without actually improving the workflow.
I didn't remove information simply to reduce visual density.
Clinical complexity still needs to be available when users need it.
I didn't redesign every part of the system.
I focused the concept on four workflows where information hierarchy and context switching had the greatest relevance.
I didn't present speculative business metrics.
Because this is a concept redesign rather than a launched product, I separated design outcomes from product impact.
DESIGN OUTCOME
A more coherent system built around attention, context, and consistency.
Across the four redesigned workflows, the same principles create:
Clearer hierarchy
Critical information is visually separated from supporting details.
Less context switching
Related information and actions stay closer together.
More predictable navigation
Consistent patterns reduce the need to relearn each part of the interface.
Faster scanning
Layouts prioritize the information most likely to require immediate attention.
4 core workflows redesigned
Dashboard · Patient Records · Scheduling · Reports
HOW I WOULD MEASURE SUCCESS
Because this project was not shipped, I would not use hypothetical product metrics as proof of impact.
If the redesign were implemented, I would evaluate:
-
Time required to locate critical patient information
-
Number of navigation steps required for high-frequency tasks
-
Task completion rate
-
Errors or missed information during patient review
-
Time required to move between scheduling and patient workflows
-
Perceived cognitive effort during core tasks
This would help determine whether the redesign was not only visually clearer, but operationally more effective.
REFLECTION
Designing complex systems is not about removing complexity — it is about deciding where complexity belongs.
Chameleon changed the way I think about information-heavy products.
The strongest design decisions were not about adding new functionality or making individual screens visually simpler.
They were about deciding:
-
What deserves attention immediately
-
What can remain secondary
-
Which information belongs together
-
When users need detail
-
How to preserve context as they move through the system
That mindset became the foundation of the redesign and a principle I now apply when working with complex workflows.
