Zus health - A healthcare tool on a mission to make healthcare data less intimidating for their users.

Overview

Overview

At Zus Health, the goal was to make scattered patient data easier to access, understand, and use. And the solution is to build an Aggregated Profile, a smart, modular view that brings together a patient’s full health history into one place.

We also made it easy for other healthcare platforms to use this data by offering it through a simple API, so they can embed it into their own tools without starting from scratch.

Zus design system

Product

Web | Saas Application

My Role

Lead Product Designer - I led the design strategy and execution for this project from user research and concept development to Visual design & build design system from ground up and developer handoff.

Timeline

2021 - 2022

Team

Bharat Pothula & Bhanu Kalyan (UXDs), Naveen Chevuru (PM)

Impact

Increased customer adoption of Zus FHIR APIs + UI

As of June 2025, over 60 healthcare organizations have adopted the Zus Health platform to enhance data interoperability and streamline patient care.

Source link

How this tool works at a glance

How this tool works at a glance

Why there is a need for new tool?

Why there is a need for new tool?

Zus health already solves the problem of fragmented data by gathering patient's data from many trusted sources like EHRs, Pharmacy data, Labs data and many more government sources in one single place.

Zus health already solves the problem of fragmented data by gathering patient's data from many trusted sources like EHRs, Pharmacy data, Labs data and many more government sources in one single place.

But this is all backend infrastructure and raw data which is very hard for their target users (Care givers, doctors) to consume.

But this is all backend infrastructure and raw data which is very hard for their target users (Care givers, doctors) to consume.

This is how Zus FHIR stores all the patient data from different sources in one place. But this is still difficult for users to digest since they must navigate through various tabs on the left to view different types of data.

This is how Zus FHIR stores all the patient data from different sources in one place. But this is still difficult for users to digest since they must navigate through various tabs on the left to view different types of data.

And this is where our design expertise comes in.

"I have to bridge this gap by designing a workspace UI that transforms raw data into structured & actionable patient information"

"I have to bridge this gap by designing a workspace UI that transforms raw data into structured & actionable patient information"

Process

Process

User Research & Pattern Analysis

User Research & Pattern Analysis

I partnered with PM, Head of Design to conduct stakeholder & expert interviews to understand our target users, pain points & opportunities that this new tool can build :

Care coordinators and Builders (Developers). What emerged was clear: different roles valued different data.

  • A care coordinator might prioritize care plan and care team members details.

  • A provider might want the timeline of encounters and labs.

  • An admin needs clear configuration options.

  • A developer wants an API to embed this info to their tool without doing heavy lifting.

Everyone wanted signal, not noise. So I have to reduce noise :)

Everyone wanted signal, not noise. So I have to reduce noise :)

A high level view of what different users want from this tool.

A high level view of what different users want from this tool.

#1 Core feature : Widget-Based Architecture

#1 Core feature : Widget-Based Architecture

#1 Core feature : Widget-Based Architecture

Introduced a modular based widget system where

  • Each major data type conditions, meds, care plan, care team became a widget.

  • Widgets could be collapsed, expanded, or reordered by the user.

  • Admins can configure default views for their organization.

  • Designed a clear visual hierarchy and iconography improved scan-ability and reduced cognitive load.

Introducing a configurable, modular based widget system.

Introducing a configurable, modular based widget system.

I have designed a manual entry/update workflow that translates this input into valid FHIR resources, seamlessly integrating them into the patient’s timeline and the backend FHIR store.

I have designed a manual entry/update workflow that translates this input into valid FHIR resources, seamlessly integrating them into the patient’s timeline and the backend FHIR store.

Detailed configurations to control what users can see on widgets

Detailed configurations to control what users can see on widgets

#2 Core feature : Customization Without Chaos

#2 Core feature : Customization Without Chaos

#2 Core feature : Customization Without Chaos

Customization in healthcare shouldn't be complex. To avoid confusion, I focused on:

Customization in healthcare shouldn't be complex. To avoid confusion, I focused on:

  • Simple affordances for reordering, Expand & Collapse widgets

  • Simple filters to identify what to see vs not to see.

Detailed configurations to control what users can see on widgets

Detailed configurations to control what users can see on widgets

Admin Features: Role Management & Data Entry

Admin Features: Role Management & Data Entry

Admin Features: Role Management & Data Entry

Why role entry :

Health organizations have different users (e.g., physicians, nurses, billing staff, IT admins). Not everyone should see or edit all data. Without granular control, there's risk of error or privacy violations (HIPAA risk).

Solution : Design UI that allows Role-based access control (RBAC), that lets admins assign permissions by role (e.g., view-only, edit, admin) and it makes the tool scalable across organizations with varied responsibilities.

Solution : Design UI that allows Role-based access control (RBAC), that lets admins assign permissions by role (e.g., view-only, edit, admin) and it makes the tool scalable across organizations with varied responsibilities.

Solution : Design UI that allows Role-based access control (RBAC), that lets admins assign permissions by role (e.g., view-only, edit, admin) and it makes the tool scalable across organizations with varied responsibilities.

Why data entry :

Not all patient data exists in external systems or FHIR networks (e.g., local intake info, handwritten notes, undocumented history). Admins and care teams need to add or correct data manually.

Solution : Designing a form or schema-based entry tools for admins to enter or batch-upload patient data (e.g., address, gender, language). And Auto-convert that data into valid FHIR resources behind the scenes.

Solution : Designing a form or schema-based entry tools for admins to enter or batch-upload patient data (e.g., address, gender, language). And Auto-convert that data into valid FHIR resources behind the scenes.

Solution : Designing a form or schema-based entry tools for admins to enter or batch-upload patient data (e.g., address, gender, language). And Auto-convert that data into valid FHIR resources behind the scenes.

Data Modelling for power users

Data Modelling for power users

Data Modelling for power users

Data modeling in Zus is essential to structure and customize FHIR-based patient data, enabling accurate, usable, and compliant health records.

Data modeling in Zus is essential to structure and customize FHIR-based patient data, enabling accurate, usable, and compliant health records.

Data modeling in Zus is essential to structure and customize FHIR-based patient data, enabling accurate, usable, and compliant health records.

I designed the end-to-end data modeling experience from 0 to 1 for clinical admins and implementation teams to visually define and manage patient data schemas without writing code. The interface includes a tree-based schema navigator, contextual editing panel, and real-time FHIR validation to make complex configurations intuitive and error-proof.

I designed the end-to-end data modeling experience from 0 to 1 for clinical admins and implementation teams to visually define and manage patient data schemas without writing code. The interface includes a tree-based schema navigator, contextual editing panel, and real-time FHIR validation to make complex configurations intuitive and error-proof.

Designed a switch to allow technical users to view/export the real-time JSON equivalent of their model.

Designed a switch to allow technical users to view/export the real-time JSON equivalent of their model.

User Research & Pattern Analysis

User Research & Pattern Analysis

I partnered with PM, Head of Design to conduct stakeholder & expert interviews to understand our target users, pain points & opportunities that this new tool can build :

Care coordinators and Builders (Developers). What emerged was clear: different roles valued different data.

  • A care coordinator might prioritize care plan and care team members details.

  • A provider might want the timeline of encounters and labs.

  • An admin needs clear configuration options.

  • A developer wants an API to embed this info to their tool without doing heavy lifting.

Everyone wanted signal, not noise. So I have to reduce noise :)

Everyone wanted signal, not noise. So I have to reduce noise :)

A high level view of what different users want from this tool.

A high level view of what different users want from this tool.