Back to work
Healthcare2025NDA — client withheld

Healthcare Patient Management Platform

HIPAA-compliant patient care & equipment logistics

A healthcare provider running diagnosis, therapy and medical-equipment delivery was juggling separate systems, phone scheduling and filing cabinets. We built a single HIPAA-compliant platform covering the whole patient lifecycle — scheduling, equipment logistics, communications and documents — with role-based access for office staff and field technicians.

RoleSenior full-stack engineer — architecture & build
Timeline2025
PlatformHIPAA-compliant web app · desktop
ClientUS healthcare provider
ReactTypeScriptAWS Cognito (MFA)Socket.ioREST APIsEDI ClearinghouseTwilioGmail APIAWS S3
01 — Discovery

Following a patient from referral to follow-up

I traced the real journey of a patient — referral, diagnostic study, equipment fitting, recurring supplies, follow-ups — and counted how many disconnected systems each step had to touch.

The care itself was good; the tooling fought it. Records, scheduling and equipment tracking lived in different places that didn’t talk to each other.

  • Mapped the full patient lifecycle, not just appointments
  • Watched where staff re-keyed the same data across systems
  • Pinpointed equipment logistics as the workflow no generic tool covered
02 — Pain points

Disconnected systems, manual everything

The provider was holding the whole operation together by hand — and on a compliance-sensitive process, every manual gap was a risk as well as a delay.

  • Phone-based scheduling causing double-bookings and missed appointments
  • No system for equipment deliveries, fittings or recurring supply orders
  • Patient comms scattered across personal email and text, with no history
  • Forms, prescriptions and authorisations in filing cabinets and shared folders
  • No visibility into field-technician availability for home visits
  • Manual processes that made HIPAA compliance hard to maintain and audit
03 — The hard part

Medical-device therapy isn’t a generic clinic

This domain has workflows a general EHR simply doesn’t model: multiple external provider portals that all need to exchange records over REST APIs and EDI clearinghouse protocols, equipment delivery tickets, recurring-supply schedules tied to insurance replacement rules, and technician routing for home visits.

Rather than bend a generic tool to fit, I built the EDI/provider-portal integration layer alongside the full patient status workflow and the equipment-and-supply lifecycle, so records moved between systems without manual re-entry.

04 — Experience

Everything about a patient in one place

The interface had to make a dense clinical workflow feel calm and obvious for office staff and field technicians alike.

  • Multi-view calendar (day/week/month) with colour-coded appointment types and conflict detection
  • Technician availability and capacity built into scheduling
  • One patient dashboard: details, full email + SMS history in context, appointments and a categorised document library
  • Integrated Gmail + Twilio SMS with automated reminders — the feature that quietly does the most work
05 — Build & outcome

Secure, real-time, role-aware

React + TypeScript over AWS Cognito with MFA, Socket.io for live notifications, REST/EDI clearinghouse integrations across multiple provider portals, encrypted S3 document storage, Gmail + Twilio integrations, and audit logging throughout.

Three roles — admin, office staff and field technician — each see exactly what they need. The provider moved from juggling systems and paper to one secure place, with automated reminders replacing manual follow-up calls.

// the result
One recordFull patient lifecycle
HIPAACompliant by design
AutomatedReminders & comms

Got a manual workflow worth automating?

This kind of focused, end-to-end tool is exactly what I like building. Let's talk about yours.