Healthcare SSO & On-Prem Admin Platform

Problem

SSO at Ceiba was an internal product, not a clinician-facing one — a centralized customer- and user-management surface for the ops team to provision hospitals, beds, clinicians, and permissions across the product line. Two pressures shaped it. Every hospital required SSO before going live, so the admin surface had to handle on-prem provisioning at the bring-up step rather than as an afterthought. And the clinical products downstream had to share identity and data cleanly: a clinician seeing a consultation request inside the eClinics product needed to address it inside Telehealth without re-auth, with near-zero data latency between the two.

Approach

Built the React/Redux/TypeScript admin frontend end-to-end — architecture, UX, state management, API integration. Permission matrices and admin forms cover hospital, bed, clinician, and role management under HIPAA-aligned access-control rules — and KVKK-aware controls for the Turkish-side deployment. SSO flows bind the admin platform, the clinical product, and the remote-care product under one identity over OIDC, so the cross-product handoff is a routing change rather than a re-login.

Result

Required at every Ceiba customer site — running across all 50 US hospitals and 100+ hospitals in Turkey. The eClinics-consultation to Telehealth-resolution handoff carries near-zero data latency, which is the metric the clinical workflow actually cares about.