Problem
Clinzo360 explores how clinic teams can coordinate account access and daily operations in one product. It is in development and has not been released.
Role & scope
I own and develop the backend and frontend. Current implementation covers authentication, clinic onboarding, memberships, team invitations, and settings. Clinical workflows remain in development.
Architecture
A Next.js frontend connects to a NestJS API, with TypeORM and PostgreSQL for persistence. User identity is separate from clinic membership, so a user can have a role within a specific clinic.
Security & tenancy
The API includes clinic-scoped session context, membership checks, and role guards.
Workflow prototypes
The patient, queue, and consultation interfaces use in-memory mock data. They explore the intended experience; they do not yet represent connected clinical workflows.
Technical decisions
Clinic onboarding groups related writes in a transaction. Separating identity, membership, and roles keeps clinic access context distinct from the user account.