← All work

Medical Case Diary

SaaS · Windows desktop application · licensed distribution

Clinic case documentation for single-doctor practices, built as a Windows desktop app because that's where the records already live. The interesting engineering is in licensing and offline behaviour: software that has to keep working without a connection, but can't be copied to the clinic next door.

The app, running

Screens

Patient names and the clinic's identity are blanked out here — this is a live install with real records behind it.

The work

Problem
A doctor documenting cases needs something fast, local and private — one doctor per clinic, working on the machine already at the desk, not a browser tab depending on clinic wifi.
Access
PIN login — the right weight of security for a single-operator desktop app, where a full account system is friction nobody asked for.
Licensing
Hardware-locked licence codes with a Supabase-backed kill switch. A licence binds to the machine, and access can be revoked remotely for non-payment or misuse.
Offline design
An offline backstop timer with a case cap: the app keeps working with no connection, so a clinic never loses a day's documentation to an outage — but it can't run indefinitely unlicensed either. The cap is the compromise that makes both true.
Transcription
Whisper running offline for dictated notes. Medical audio doesn't leave the machine — the privacy requirement decided the architecture, not the other way round.
Output
Google Drive sync producing formatted Google Docs, so case records land somewhere the doctor can read, search and share without the app in the loop.
Shipped
Blueprint v3.0, Terms & Conditions, and a Phase 1 build specification — documented as a product for distribution, not just code.
Roadmap
Razorpay billing automation once past roughly 50 clinics. Below that, manual invoicing is genuinely cheaper than the integration.
Stack
  • Windows desktop
  • Supabase
  • Google Drive API
  • Whisper (offline)
  • Hardware licensing

This is one of a few projects shown here — a small sample of what I've built. Happy to walk through the licensing model or the offline strategy.

Contact

Currently exploring AI filmmaking and automation roles. Happy to walk through any of these systems in detail — architecture, trade-offs, and what broke along the way.

Résumé (PDF) ← All work