Let's connect
All work

01 · Work · CuraLife

CuraLife.

CuraLife is client work, not my own product: an outpatient platform built for small clinics in Tier-2 and Tier-3 India.

One visit runs across two apps. Patients decide who can read their records. Doctors speak the consultation and seal the note, and the prescription plays back in Hindi.

Role
Client demo
Team
Solo, for a client
Stack
  • React 18
  • Vite
  • Tailwind
  • FastAPI
  • SQLite
  • WebRTC
  • Sarvam AI
FIG. 02 · Doctor OS
FIG. 03 · Patient app
2
apps, one visit
20
screens across both apps
38
API endpoints

02 · Story

Why it exists.

  1. The problem

    Small clinics, paper records, many languages.

    Outpatient clinics in smaller Indian cities run on paper and a mix of languages. The brief was one visit that works for the patient and the doctor alike.

Who stays in controlPatients decide who reads their records, and can take access back at any time.

03 · What it does

What it does.

  • Patient-held consent

    A doctor gets two hours to read a patient's records only after the patient grants it. The patient can slide to revoke at any time, and access expires on its own when the window closes.

  • Ambient voice scribe

    The doctor records the consultation in Hindi, English or a mix. Sarvam AI transcribes it and drafts a structured SOAP note with medications. The doctor edits and approves, and the scribe never finalises a note on its own.

  • Sealed, hash-chained records

    Approving a note links it into an HMAC-SHA256 hash chain. Database triggers reject any later edit or delete of an approved record.

  • Audio prescriptions and video visits

    Approved prescriptions play back as a spoken voice note in Hindi or English with a readable script. Online visits run peer to peer over WebRTC, and the backend bills only connected minutes.

04 · Features

What it does.

  • Doctor OS

    The day's OPD queue, walk-ins, live consultation, prescriptions, billing and analytics in one place, with a Cmd or Ctrl+K palette that jumps to any patient or page.

  • Patient app

    Find a doctor, book an in-clinic or online visit, join the video call, and upload or read your own records.

  • One number, one role

    Sign-in is an OTP to a phone, and each mobile number belongs to one role, so a patient number cannot sign in as a doctor.

  • AI that drafts, never decides

    Voice form-fill, facts pulled from an uploaded report, Hindi and English translation, and a plain-language visit summary. The doctor approves everything.

  • Billed by connected minutes

    Video visits bill only while both sides are on the call, and the clock pauses when the network drops.

  • Runs without a key

    The whole flow works offline in mock mode, and a failed live AI call falls back and is marked as degraded instead of breaking the visit.

05 · Scenarios

Where it's used.

  1. A busy OPD

    A walk-in at the front desk.

    The doctor registers a new patient in one step, or by voice, and gets two hours of access straight away.

  2. A patient in another town

    A follow-up without the trip.

    They book an online visit, grant two hours of access, and pay only for the minutes the call was connected.

  3. A Hindi-speaking patient

    After the visit.

    They play the spoken prescription and read a plain-language summary of what the doctor said.

  4. A patient switching doctors

    Taking access back.

    One slide revokes consent, and the previous doctor can no longer open the records.

Let's connect.

I am not looking for work. I am looking for good people to know.

Index

  1. 1Home
  2. 2Work
  3. 3Security
  4. 4About