Telehealth Product
An online healthcare platform for the Israeli market. I led development of the Next.js application covering appointment scheduling and video consultations, spanning both patient-facing and provider-facing modules.
Senior Frontend Developer
- Next.js and server-side rendering
- Video consultation workflows
- Storybook component library
- Azure and Docker delivery
What I personally owned
- Led development of the Next.js appointment scheduling and video consultation application.
- Applied server-side rendering to improve initial-load performance.
- Established a Storybook component library for patient-facing and provider-facing modules.
- Architected secure patient-facing workflows for personal health data.
Context
The product connects patients with providers for scheduled appointments and video consultations. Two distinct audiences use it, with different needs but overlapping interface building blocks.
What made the frontend hard
Healthcare interfaces carry personal health data, which raises the cost of a sloppy workflow. At the same time the first load matters: someone joining a consultation should not be waiting on a JavaScript bundle.
- Two audiences, patient-facing and provider-facing, sharing components.
- Personal health data in the workflows.
- Initial-load performance on scheduling and consultation entry points.
Architecture and rendering
Server-side rendering was used to improve initial-load performance. A Storybook component library gave the patient-facing and provider-facing modules a shared, documented set of components rather than two diverging implementations.
- Next.js with server-side rendering.
- Storybook component library shared across modules.
- Secure patient-facing workflows for personal health data.
Delivery
The application was deployed on Azure using Docker.
What was delivered
- Appointment scheduling and video consultation application.
- Server-side rendered entry points.
- Storybook component library covering patient-facing and provider-facing modules.