The Kure app on a phone held in one hand, greenery behind

Healthcare / Enterprise SaaS / Complex workflows

Kure

Designing a Healthcare Platform That Supports Clinical and Business Operations

Role
Sr. Product Designer, with product ownership across the web platform
Scope
Product strategy, UX, DS, cross-stakeholder workflows
Platform
Web + mobile
Product type
Internal B2B SaaS / Healthcare operations

Kure is an internal healthcare platform built to support the operational backbone of clinics and hospitals. I led product design across web and mobile, owning experience strategy, system foundations, and multi-stakeholder workflows for a highly regulated, high-complexity environment.

My role focused on translating fragmented, manual processes into a coherent platform that could scale across organizations without breaking trust, reliability, or operational clarity.

A patient's record in the browser: demographics, guardian, insurance, copay and claims, each a set of fields

How we got to a 60% reduction of time to complete form across the board, on all verticals.

Challenges

Healthcare operations involve multiple user types working under strict regulatory, time, and reliability constraints. At Kure, the challenge was not building features, but designing a system that could support:

  • patients
  • nurses and doctors
  • administrative staff
  • recruiters and HR
  • financial analysts and executives
A doctor at his desk fills in a patient's form while she waits across from him; an open laptop beside them

Each group had different goals, permissions, and mental models, yet all needed to operate within the same platform.

The existing processes were fragmented, heavily manual, and difficult to scale.

Expectations vs. Reality

A surface-level solution would have optimized individual workflows in isolation. In reality, improving one role’s experience often created friction elsewhere.

Designing Kure required a system-level view: understanding how decisions made for one user type impacted others across the organization, both operationally and financially.

The operational model, mapped. Point at a step (or tap it) to follow where it leads and what leads to it.

Design Strategy & Key Decisions

Decision 1

Designing the system before individual workflows

Rather than starting with screens, I mapped the underlying operational model: roles, permissions, dependencies, and data flows.

This allowed the platform to remain coherent even as complexity increased and new use cases were introduced.

Decision 2

Prioritizing clarity over density

Healthcare systems often collapse under their own complexity.

I intentionally designed for clarity: progressive disclosure, strong hierarchy, and predictable patterns, even when it meant resisting feature density.

This reduced cognitive load for frontline staff while keeping the system powerful enough for advanced users.

The page layout as a wireframe: one page in three columns, named information, action, and preview or detailed info
One layout for every record: information, action, preview.
A therapist's record in the browser: details on the left, work history in the middle, pay details on the right
A therapist's record: information, action, preview.

Decision 3

Building reusable patterns across web and mobile

Kure needed to function consistently across devices without duplicating effort or logic.

I focused on shared patterns, components, and interaction principles that could scale across web and mobile while respecting each platform’s constraints.

This improved maintainability and reduced long-term design debt.

Wireframe

LocationUser NameSpecialtyDATA PARAMETERDataACTIONABLE BUTTON

Therapist

GastoniaATAnthony TurnerABA TherapistATCMCJDODMEKGDIFKMMOPTHOURS67hrsSCHEDULED HOURS12hrs 30minGO TO THERAPIST

Patient

LincolntonMandy ExampleWed, 8 Jan 2020Arr: 1:30pmATAnthony TurnerAPPROVED UNITS16/25/256/125/60GO TO PARENTSESSION NOTES

Design tokens

Colour

  • Ink#3a437d
  • Action#27b4db
  • Band#eaf5f7
  • Line#b9cfd4
  • Arrived#78c14e
  • Canceled#e1573f
  • Scheduled#9cc2cb
  • Claim open#6196cf
  • Claim approved#749e56
  • Claim denied#dac038

Chip states

  • Visit Arrived/Completed
  • Visit Canceled/No Show
  • Visit Scheduled
  • Claim for Visit Not Released
  • Claim Released | Status Pending Approval
  • Claim Approved | Status Approved Amount Column Filled
  • Claim Paid | Status Paid Amount Column Filled
  • Claim Denied | Status - Not Worked
  • Claim Denied | Status - In Queue
  • Claim Denied | No More Reconciliation
One card, as a wireframe and in two versions, with the design tokens extracted from the design system.
A grid of low-fidelity wireframes for the mobile app: profile, job details, terms and time entry
The mobile app in low fidelity, before any colour.
Low-fidelity wireframes of chat, contacts and calendar screens, linked by flow lines
Chat, contacts and calendar, with the paths between them.

Impact

$12M+
in annual revenue supported through improved operational efficiency
13+
Clinics in North Carolina, US, using the platform
3+
Hospitals in India using the platform
60%
Reduction of time to complete form across the board, on all verticals

From Strategy to Execution

Design execution focused on supporting real operational workflows, not idealized user journeys.

Operational Dashboards

Designed to surface the right information at the right time for different roles, reducing dependency on manual reporting.

  1. Clinics and billing dashboard

    Performance, denials by code and the billings ready for release, on one page.

Clinics and billing dashboard

The clinics and billing dashboard in the browser: performance, denials by code, billings ready for release and services offered
The claims screen: a denied claim with its reason, the fields to correct and an Add to claim queue button
Working on claims.

Staffing & Recruitment Flows

Clear, role-aware flows that balanced speed with compliance and accuracy.

Web screens by role: payroll approvals, therapist, patient, payer and CPT code
Screens by role: payroll approvals, therapist, patient, payer, CPT code.

Mobile Support for On-the-Go Roles

Mobile experiences optimized for quick actions and visibility without sacrificing data integrity.

  1. Provider profile

    Who the provider is, with the two things an agency does next: invite to a job, or message.

A provider's profile: photograph, name, speciality, Invite to job and Message buttons

Reflection

Kure reinforced the importance of system thinking in complex domains. Designing for healthcare operations isn’t about perfect flows, it’s about creating resilient structures that hold up under real-world pressure.

The principles applied here: clarity, systems over one-offs, and decision-making at scale, translate directly to any complex B2B or regulated product environment.