Healthcare SaaS / Workflow Automation
Patient Journey Automation Engine
- Problem
- Pre-op instructions, consent collection, post-op check-ins, and outcome surveys were coordinated largely by hand, with no consistent way to reach the right patient at the right time.
- What I built
- A state-machine journey engine driven by appointment events, with consent and quiet hours evaluated once, centrally, as gates for every channel.
- My role
- Owned design and implementation, State-machine journey logic, Consent and quiet-hours gating, Handling reschedules, cancellations, readmissions, and out-of-order events
- Node.js
- Express
- MongoDB
- Bull / BullMQ
- Redis
- Twilio