Senior UI / UX Designer
Prototype, animation, user research, and product interface direction.
Healthcare platform
OutcomeMD
A clinical UX/UI redesign for clearer patient data, calmer assessments, and faster decision-making.
Figma, Sketch, Jira, Confluence
Supported by Illustrator, Photoshop, and After Effects for visual assets.
Product, design, and engineering
Collaborated with Lukasz Szymanski, Sourena Mansouri, and Farzad Moghbel.
Redesign the EHR dashboard around clarity.
Make OutcomeMD more intuitive and efficient so healthcare professionals can navigate patient data and assessments with less friction.
Reduce UI complexity without losing clinical depth.
I focused on insight visibility, data-driven workflows, calmer navigation, and faster decision-making across the healthcare product.
Electronic Health Records
User-centric design for dense clinical work.
OutcomeMD needed to feel less like a static record system and more like a working surface for care teams. The redesign focused on simplifying complex processes, reducing frustration, and helping clinicians manage patient tasks with confidence.
Research archive
The process behind the product decisions.
A guided carousel of research boards, flow maps, personas, tooling, and solution framing that explains how the UX direction was shaped.
Research inputs
User research and data collection
Clinician interviews, task analysis, and platform data gave the redesign a measurable starting point.
Discovery flow
How clinicians find the data they need
The search path was mapped from login to dashboard, filters, patient list, assessment review, and return actions.
Design process
From research signal to shipped interface
The process moved through synthesis, sitemap, wireframe, experiment, high-fidelity design, testing, and delivery.
Tooling
The execution system behind the work
Design, project management, collaboration, and research tools were organized around handoff and decision tracking.
Project rhythm
A managed cadence for clinical product work
Sprint rituals, responsibilities, risk management, and communication practices kept research and delivery aligned.
User personas
Who the product had to support
Personas clarified the needs of primary care, specialist, administrator, and patient-facing workflows.
Solutions
What changed in the product experience
The redesign focused on persistent filters, calmer assessments, clearer navigation, and a more usable layout system.
Challenge
Make clinical complexity feel calm, legible, and actionable.
In clinical software, every extra moment of hesitation matters. The redesign reduced scanning effort, clarified the hierarchy of patient data, and made long assessment workflows feel less mentally expensive.
Put the clinical signal in the first scan path
The dashboard was reorganized so outcomes, patient scope, and follow-up status could be understood before users dug into details.
Turn dense form work into a guided task
Assessment selection, long forms, and record detail views were structured around progress, state, and next-action clarity.
Keep evidence connected from summary to patient
Filters, result summaries, export actions, and patient lists share the same logic so users do not rebuild context at every step.
SiteMap
Structure came before surface polish.
Before moving into detailed UI, I mapped the dashboard ecosystem so the product could support real clinical movement instead of isolated screens.
Dashboard entry points, assessments, reports, filters, and patient details were connected first so the interface could behave like one system.
Map the dashboard before wireframes
The sitemap clarified how dashboards, assessments, reports, and patient details needed to connect before visual design started.
Identify the core clinical objects
Centers, providers, patients, assessments, diagnoses, filters, and reports became the organizing structure for the product.
Design navigation around real tasks
The final structure supported easier movement between scanning outcomes, filtering cohorts, and reviewing patient-level evidence.
Experimentation
Testing how clinical data should be presented.
We explored multiple dashboard directions and used research feedback to understand which patterns made the data easier to find, compare, and trust.
Research showed that mixed colors, gradients, and competing panels made some users work harder to understand the hierarchy.
The top navigation and left icon system needed to become quieter so clinicians could find the data faster.
Behind OutcomeMD filters
Filters became the operating system for the product.
OutcomeMD needed clinicians to segment patient data, move into reporting, and return to detail views without losing trust in the state of the system. The filter model was redesigned to stay persistent, visible, and easier to reason through.
Persistent context lowered the mental cost of clinical analysis.
- Filter state stays visible in the sidebar, tabs, and report outputs.
- Include and exclude logic supports real clinical segmentation instead of a generic search box.
- The UI moves from population-level signal to patient-level evidence without resetting context.
And/or, include/exclude, select-all, and long diagnosis lists are exposed as deliberate choices for cohort building.
Life events, injuries, laterality, compliance ranges, and selected chips live beside the data they affect.
Provider, center, team, and patient selectors establish scope before completion gauges and outcome cards appear.
The dashboard compares baseline, follow-up, improved, and worsened values without making users decode raw tables first.
Outcome categories inherit the same scope, making it easier to compare clinical signals across a selected cohort.
Reporting actions remain beside the filtered view, so evidence can move directly into review or follow-up.
Patient names, status, scores, and movement are grouped so teams can inspect the evidence behind a trend.
Filtered rows, report fields, and notification setup give teams a traceable path from cohort to patient follow-up.
Assessment flow
Assessment work became a guided clinical path.
The work moved between overview dashboards, selection states, and long-form clinical tasks. The interaction model had to stay predictable even as density increased.
Available forms, selected assessments, and progress states are separated so clinicians can decide what to open next.
Closed sections reduce visual noise while preserving the structure needed for long clinical questionnaires.
Assessment inputs, patient information, and reporting context share one surface so completion feels grounded.
Exploration and system thinking
The interface was designed from the flow up.
Beyond the shipped screens, the project included workflow maps, care-management explorations, and monitoring concepts that helped align the broader product behavior.
The flow shows where clinicians need to move from care management context into individual patient review without losing the thread.
Alerts, result movement, and patient lists transform outcome tracking from passive reporting into a follow-up workflow.
Outcome
A more usable clinical product, not just a cleaner UI.
The strongest result was a calmer working surface for clinicians: less visual noise, clearer priorities, and a product language that could support serious healthcare work with more confidence.
Strong healthcare UX reduces hesitation at the exact moment people need clarity.
- Clarified dashboards for faster scanning and follow-up decisions
- Assessment surfaces that feel calmer under dense clinical content
- A more coherent product language across reporting, records, and workflows