Remote Patient Care — Web Client
Telehealth clinician interface — Zoom SDK + Twilio fallback.
Highlights
- Built the clinician-facing UI for live remote consultations: scheduling, rostering, session lifecycle
- Integrated Zoom Meeting SDK for in-browser AV and Twilio Voice for fallback calling
- Bridged React state to Phoenix channels for live presence, messaging, and session events
- Introduced Jotai for atomic state management; replaced heavier legacy patterns with lightweight composable stores
- Hardened error paths with Sentry session tracking and Zod-validated API boundaries fed through TanStack Query
- Shipped multi-tenant i18n (en/tr) with runtime HTTP backend for per-hospital overrides
Problem
The browser side of the remote-care product is where clinicians actually live — scheduling visits, picking up consultations, running sessions, charting after. The product had to host live AV in the browser without giving up the rest of the workflow surface, talk to a Phoenix backend that already owned channels for presence and session events, and survive multi-tenant hospital deployments where each site overrides translations, branding, and policy at runtime.
Approach
React frontend with TanStack Query as the API boundary, every response Zod-validated so contract drift surfaces at the boundary instead of mid-render. Atomic state via Jotai — replaces a heavier legacy store layout with composable per-feature atoms. AV is dual-vendor: Zoom Meeting SDK for in-browser video, Twilio Voice as the fallback path when the patient can’t get video to work. Phoenix channels carry presence, messaging, and session lifecycle events, bridged into React state through a thin adapter so component code never sees the channel API directly. Multi-tenant i18n loads translations over an HTTP backend at runtime, so per-hospital overrides ship without a redeploy. Sentry session tracking on the error path; HIPAA-aligned access control on the data path.
Result
The clinician web surface for the same remote-care deployment as the bedside cart and practitioner desktop — running across 50 US hospitals. The dual-vendor AV path means a session that can’t establish video doesn’t end the visit, it falls back to voice and continues.