Cliniclick Case Study

Cliniclick | A health network, built on a practice operating system

Two layers, one on top of the other. First, the operating system that runs the practice every day: its own website with online booking, doctor, front-desk and patient panels, a clinical record, e-prescriptions, finance and secure messaging. Second, a health network where patients find a verified doctor near home, and stay connected after the visit. The doctor's specialty decides which tools come first: a dentist sees the tooth and gum charts, a GP sees vitals and history.

36 specialtiesMedical and dental, each with its own tools
4 panels + siteDoctor, front desk, patient, owner; and a website per clinic
1,800+ testsAutomated tests on every change, before it reaches a clinic
Live demo

See Cliniclick from the inside

A live sandbox of the same platform: a fictional dental clinic with two doctors, a front desk and months of synthetic data. Pick a role and use the panel the clinic uses every day. The interface is in Persian.

Every name and number is synthetic and the sandbox resets every few hours. No SMS or payment is ever sent. The platform admin panel and the analytics console are not part of the demo, and the health-network layer (map, doctor profiles, marketplace) lives only on cliniclick.ir.

The second layer: a health network

The same system that runs the practice every day now connects patients and doctors. Trust in this network comes from real visits, not from placement anyone can buy.

For patients

  • «Near me»: in-person doctors on a map, sorted by distance
  • Booking in three steps: visit type, a doctor who offers it, and a time
  • In-person, text and phone visits, each with its own schedule and fee
  • Follow and star doctors, see their updates, and request treatment packages from the marketplace

Rules of trust

  • A public profile only for doctors whose medical council number is verified
  • Ratings only from patients who were actually seen; doctors reply publicly, and review text appears only with the doctor's approval
  • Follower counts shown from 20 upward; names never
  • Messages to the doctor only within 48 hours of a visit, and only if the doctor allows it; ranking and visibility are not for sale

MasterMind: practice growth reports

For Premium practices, monthly and quarterly reports in five layers: current state, trend, cause, the practice's standing among peers in its specialty with no names shown, and three concrete steps for the next month.

One account, several roles

A doctor who is also a patient switches between their panels from one menu. The practice's location goes on the map so nearby patients can find it, and SMS is paid from the practice's own credit, at cost.

Specialty is a product dimension, not a label

Doctors pick their specialty when they sign up and the platform shapes itself around it: which menu, which record tabs, which vitals come first, which tool opens first. A periodontist sees the gum chart first; a GP sees history and vitals.

One clinical core for every specialty

  • Structured visit records: complaint, exam, diagnosis and plan, with the full history of every change
  • E-prescriptions on the doctor's real letterhead; an issued prescription never changes and prints ready
  • Vitals with safe ranges, computed BMI and trend charts
  • Medical history with warning flags, and digital consent signed on screen

Dentistry, complete and separate

  • Tooth chart with international numbering, permanent and baby teeth, five surfaces and 14 conditions, with history
  • Gum chart with six measurement points per tooth; bleeding and plaque percentages computed, trends between exams
  • A ready dental procedure and price catalogue from day one
  • Every dental specialty gets its own first tool

Problem

Appointments, patient follow-up, messaging, and payments were handled in disconnected tools, causing more human error, slower response, and weak management visibility. On the other side, patients chose a doctor from bare listings and unbacked ratings, and doctors had no channel to keep a patient after the visit.

Constraints

  • High sensitivity of treatment data with strict tenant-level isolation needs
  • Mostly non-technical operations team requiring low-friction UX
  • Phased rollout without interrupting active clinic service

Architecture Decision

One platform for every clinic, with each clinic's data fully separated and its own subdomain. A clinic signs up with an application, is provisioned automatically once approved, and its plan decides which modules are on. Every sensitive action is recorded, and every change passes the automated test gate before release.

Operational Modules / Technology Scope

  • In-person and online scheduling core + smart slotting + queue management
  • Structured clinical record, e-prescriptions, vitals and digital consent
  • Dental module: tooth chart, gum chart and procedure catalogue
  • Internal treatment messaging with files, quick replies, and access policy
  • Integrated finance: payment channels, debtors, daily reporting, and SMS credit at cost
  • Expense, inventory and HR management
  • Dedicated website per clinic with OTP-powered public booking

Key Platform Capabilities

  • Multi-tenant SaaS with strict clinic-level data partitioning
  • Role-based panels for doctor, secretary, patient, admin, and owner
  • Several doctors per clinic, each with their own specialty and schedule
  • Subscription plans with real limits, and per-clinic switches for every module
  • Public booking, confirm/cancel/reschedule flows, and pending reservation handling
  • Smart slot generation based on work hours and real appointment conflicts
  • Live clinic queue and patient status tracking from check-in to checkout
  • In-person, text and phone visits, each with its own schedule and fee, and three-step booking for patients
  • Public doctor profiles, follow and star, a feed of updates, and a treatment-package marketplace
  • «Near me»: practice location on a map, in-person doctors sorted by distance
  • A clinical record the patient sees too: history, signed consents and tooth chart
  • Internal clinical messaging with files, reactions, pin/archive/mute, quick reply
  • Role/time-window messaging policy for real treatment-stage access control
  • Finance module: appointment payments, debtors, channels, daily operational finance
  • Transaction ledger, clinic expenses, and inventory thresholds
  • Monthly and quarterly growth reports for Premium practices, in five layers from current state to next step
  • Admin panel for applications, doctor/clinic/user management, support tickets and a record of sensitive actions
  • A platform-owner console: business intelligence, a network map, and a five-layer view of each clinic

Business Impact

Higherdaily intake and reception throughput
Lowerback-and-forth coordination calls
Clearermanagement visibility via daily finance and ops reporting

My Role

  • Mapped real clinic process and defined executable product scope
  • Designed architecture, data model, and access policies
  • Implemented end-to-end scheduling, messaging, finance, clinical core and dental modules
  • Turned specialty into a product dimension, so one platform serves 36 specialties
  • Designed the health-network layer and its trust rules, and the MasterMind growth reports
  • Led phased rollout, monitoring, and post-launch optimization