Healthcare SaaS / Workflow Automation
Patient Journey Automation Engine
A state-machine-driven engine that schedules and sends patient communications across the surgical journey, based on appointment events, consent status, and quiet-hours rules.
- Node.js
- Express
- MongoDB
- Bull / BullMQ
- Redis
- Twilio
The 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
Technical highlights
- Consent and quiet hours enforced as platform-wide policy, not per-feature checks
- Handles rescheduling, cancellation, readmission, revoked consent, and out-of-order EHR events
- Communication runs in background jobs, outside the request/response cycle