Dialysis Safety Interface

India's Dialysis Crisis: A System on the Verge of Collapse

The independent dialysis sector is caught in a perfect storm. While confronting a catastrophic treatment gap and soaring mortality rates, operators are simultaneously bleeding razor-thin margins through documentation failures, and buckling under the weight of archaic compliance reporting.

97%

Treatment Gap

7.8M Indians need dialysis.
Fewer than 250,000 receive it.

100k+

Annual Deaths

Due to systemic failure, not lack of clinical tech.

45–55

Median Age

Patients are active breadwinners, compounding the economic cost.

What's Broken Operationally

Why This Moment Specifically? (The Timing Is Right)

Haemodialysis: The Clinical Workflow

Haemodialysis is a procedure that replicates kidney function by removing waste products and excess fluid from the blood. The patient's blood is drawn through a needle or catheter, circulated through a dialyser (an artificial kidney membrane), cleaned against a carefully prepared dialysate solution, and returned to the body. A typical session runs 3–5 hours, three times per week, for the rest of the patient's life.

Tasks at a Dialysis Clinic

As-Is Service blueprint

Mapping the complex interplay between clinical actors, the patient, and infrastructure throughout the dialysis journey.

What People Are Really Trying to Accomplish

The JTBD framework strips away features and asks: what is the person trying to make happen in their life? What does 'done' look like for them? This framing produces more durable design decisions because it anchors to human goals, not technology.

What's Broken Operationally?

Placeholder — Heuristic evaluation of the current system. Annotated screens with severity ratings (Critical / Major / Minor). Where was the biggest friction? What surprised you?

Benchmarking the Ecosystem: Solutions Evaluated

To understand the strategic gap in the Indian dialysis market, we evaluated five distinct platforms across the global and local spectrum. From premium German engineering to the paper-based reality of rural India, these benchmarks provided the "north star" for my design goals.

Feature Comparison Matrix: Identifying the Strategic Gap

By mapping these solutions against five key criteria — Safety, Documentation, Clinical depth, Admin efficiency, and Technical agility — we identified where the system was buckling under pressure.

Who and what are all the actors in this system?

Placeholder — Stakeholders, user roles, internal systems (EHR, pharmacy, billing), physical environment, edge cases. This is the full picture before you design anything.

What does the current state actually look like, end to end?

Placeholder — As-is journey map or process flow. Where are the handoffs? Decision points? Moments of ambiguity? Where does the system assume things it shouldn't?

What did we hear, see, and uncover in the field?

Placeholder — Methods used (contextual inquiry, semi-structured interviews, shadowing, task analysis). Sample size, sites, how participants were recruited.

Placeholder — Key themes that surfaced. Synthesis method (affinity clustering, thematic analysis, etc.).

How does the designed solution sit inside the full delivery system?

Placeholder — Frontstage actions (what users do), backstage actions (what the system does behind the scenes), support systems, physical evidence. This shows the designed solution, not the current state.

What is the design bet we're making?

Placeholder — The HMW statement. The POV. The guiding principle that shaped every decision that follows.

Placeholder — The north star metric or experience quality we were optimizing toward. What does "winning" look like from the user's perspective?

What patterns emerged from the data?

Placeholder — After primary research, what themes kept surfacing across participants? What were the unexpected findings? How did you reconcile contradictions in the data?

What exactly are we offering — and to whom?

Placeholder — Define the core value prop of the redesigned interface. For each user segment, what does the new design specifically offer that the current one doesn't? Frame it as a before/after for the user's experience, not as a list of features.

Who had a seat at the table — and what did they each need?

Placeholder — Map the key internal and external stakeholders. What were their competing priorities? Who had veto power? Who was a quiet blocker? How did you build alignment across clinical, engineering, and procurement?

How did we go from insight to interface?

Placeholder — Walk through the key design decisions. Not just "here's the final design" — explain the forks in the road. What was the alternative? Why was this the right call?

What changed between V1 and what shipped — and why?

Placeholder — Show 2–3 meaningful design pivots. For each: what the original design was, what feedback or data caused the change, and what the revised direction looked like. This is where design thinking becomes visible.

How did we take this from prototype to rollout?

Placeholder — Describe the rollout strategy. Was this a phased launch, a pilot across one ward, or a full hospital deployment? Who were the internal champions? What training or change management was needed?

What actually changed?

Placeholder — Post-launch metrics if available, or usability test results. Stakeholder reception. What was shipped vs. what was designed. The delta that mattered.

What would I do differently?