03Healthcare platform for clinical workflows2025 — Present

HekaBio

Role
Front-End Lead
Goal
Build accessible, compliance-sensitive interfaces for clinical data visualization and analytics.
Outcome
WCAG-compliant front end in production, delivered by an 11-person distributed team under my lead.
HekaBio homepage — the HekaBio wordmark and “Miracles through Partnership” tagline over a Mount Fuji sunset, above a line describing the company as a biopharma and MedTech in-licensing platform for Japan and APAC
Visit staging.heka.bio/sign-in

Problem

Clinical software carries constraints most products never face: dense medical data that must be legible at a glance, WCAG accessibility as a requirement rather than a nice-to-have, and compliance rules that shape even small UI decisions. The product needed complex, form-heavy modules that clinicians could trust — built by a distributed team.

Approach
  1. 01

    Architecture for accessibility

    As front-end lead I set the architecture so accessibility is structural, not decorative — semantic components, keyboard-first interaction patterns, and data visualizations that remain readable to assistive technology.

  2. 02

    Compliance-sensitive modules

    Delivered the platform's hardest surfaces: form-heavy clinical workflows where validation, audit-ability, and error prevention matter, plus an interactive in-platform chat interface.

  3. 03

    Leading a distributed team

    I manage code reviews, releases, and coordination across an 11-person distributed engineering team — keeping quality consistent when the team never shares a room.

Results
  • WCAG-compliant, accessible interfaces for medical data visualization and analytics.
  • Complex, compliance-sensitive clinical modules and an in-platform chat shipped to production.
  • Consistent release cadence and review discipline across a distributed team.
  • React
  • Next.js
  • TypeScript
  • Data Viz
  • Accessibility (WCAG)
Next projectToolHaven

Want the full story? rahulkrsingh321998@gmail.com