// Selected Work
Universal Telemedicine
Infrastructure.
A multi-tenant digital hospital platform engineered to unify patient triage, video consultations, and medical records into a single scalable "Operating System."
< 1.2s
Video Latency
Global Edge Network
100%
Compliance
HIPAA/GDPR Ready
3 Clicks
Booking Flow
Conversion Optimized
98/100
Performance
Lighthouse Score
The Fragmentation Problem
Private practices and multi-specialty clinics often rely on a "Frankenstein stack" of disconnected tools—Calendly for booking, Zoom for calls, and paper/EMR for notes.
This fragmentation creates data silos, increases administrative overhead, and forces patients to download multiple apps just to see a doctor.
The Unified Solution
I architected a Zero-Trust Clinical OS that centralizes the entire patient lifecycle.
- Multi-Specialty Routing (Dental, Derma, GP)
- Role-Based Access Control (Patient vs Doctor views)
- Real-time "Up Next" Queue Management
Engineered for Scale
Key technical implementations driving the platform.
Clinician Command Center
A unified dashboard handling patient queues, medical history, and visual triage in real-time.
Zero-Trust Data
Row Level Security (RLS) ensures total isolation between patient records.
Embedded Video
Custom Jitsi implementation with removed "bloat" features for professional use.
Architecture Highlights
01.Strict Type Safety via Supabase
Database schema is automatically introspected to generate TypeScript definitions, ensuring end-to-end type safety from the Postgres DB to the React Client.
interface Appointment {
id: string;
patient_id: string; // FK to auth.users
status: 'scheduled' | 'completed';
}
02.Event-Driven State (Realtime)
Leveraged Supabase's replication log (WAL) to push database changes to the client instantly via WebSockets. This ensures the "Waiting Room" dashboard updates live without polling.
const channel = supabase
.channel('room-updates')
.on('postgres_changes', event => {
refreshQueue(event.new);
})
.subscribe();
03.Server-Side Data Isolation
Sensitive patient records are fetched exclusively via Server Components. This ensures that raw JSON data and authentication tokens are never exposed to the client-side browser bundle.