DEV3Technologies
All case studies

DEV3 Technologies · own product

ClinicPro: a multi-tenant clinic management SaaS with fail-closed tenant isolation

Our own product: one Next.js + MongoDB platform that runs many clinics — patients, appointments, live queue, EMR, lab, pharmacy, billing, HR and a patient portal — with tenant isolation enforced in the data layer.

Next.jsReactTypeScriptMongoDBMongooseAuth.jsTailwind CSSStripeGemininext-intlMulti-tenantRBAC
Industry
Healthcare SaaS
Services
Custom SaaS EngineeringCustom SoftwareWeb DevelopmentAI Implementation

Live project preview

DEV3 Technologies · own product — screenshots
Open live demo
Public website with the animated 3D hero, edited through the built-in CMS

Public website with the animated 3D hero, edited through the built-in CMS

The challenge

Small and mid-size clinics usually stitch together separate tools for booking, records, lab, pharmacy stock and invoicing, which means re-keying, stock that expires on the shelf and invoices that miss lab or pharmacy lines. For a vendor serving many clinics there is a second problem: one isolated install per customer is expensive to run, yet a shared database must never leak one clinic’s health records to another.

Our solution

We built ClinicPro as a single Next.js 15 application on MongoDB where one installation serves many clinics, and designed the safety properties into the data layer rather than leaving them to code review.

Key design decisions

  • Shared database, enforced tenancy. 24 of the 39 Mongoose models are tenant-scoped. A schema plugin throws on any find, update, delete, count or aggregate that lacks a clinicId filter; cross-tenant access needs an explicit option used only by the Super Admin console.
  • One mutation pipeline. Every server action is built from guarded wrappers (read-only check → session and tenant → permission → zod validation → handler → audit → revalidate). A repo script fails the build if an action skips them.
  • Scoped RBAC. 9 roles and 20 permission keys, each granted at an all, read or self scope, shared by the server guards and the UI.
  • Money done in integer cents. USD storage, a per-clinic display currency, an exchange-rate snapshot on every invoice and largest-remainder allocation so ledger rows always sum exactly.
  • Integrity in the database. A unique partial index prevents double-booking; pharmacy dispensing picks batches first-expiry-first-out with optimistic concurrency.
  • Health-data protection. AES-256-GCM field encryption for identifiers and clinical notes, rate-limited sign-in, session revocation and an audit trail.
  • AI as an assistant only. ICD suggestions and prescription safety checks are schema-validated, labelled as suggestions and never applied automatically.

Architecture

React Server Components render the staff app, patient portal, kiosk and waiting-room display. Server Actions and route handlers (/api/v1 for staff, /api/admin, PDF streams, the portal, a public queue endpoint, a daily cron and the Stripe webhook) call domain services in lib/services, which use Mongoose on MongoDB. Integrations sit beside the services: Stripe Checkout, Cloudinary, SMTP and Google Gemini. A Super Admin console provisions clinics, gates modules by plan and edits the CMS-driven public website.

Results

ClinicPro ships as a complete, sellable product with a public read-only demo. By the numbers, counted from the source:

  • 15 plan-gateable modules
  • 9 roles and 20 permission keys with all/read/self scopes
  • 4 languages, 2 of them right-to-left
  • 65 pages, 54 API routes and 39 Mongoose models (24 tenant-scoped)
  • 73 automated test cases in 23 Vitest files

It installs through a 4-step web installer or Docker Compose, and is available on the DEV3 marketplace.

Related case studies