Clinic Management System (Full Stack)
Full-Stack Healthcare Workflow Platform for Patient Records, Visits, Prescriptions, Billing, and Real-Time Queue Management

System Context & Value Proposition
The Clinic Management System (CMS) is an end-to-end healthcare operations engine engineered to replace fragmented paper registers, disorganized physical prescription pads, and uncoordinated appointment queues with a centralized, role-protected digital platform. Designed with a clean two-column canvas interface, the system connects receptionists, doctors, pharmacists, and clinic admins into a synchronized clinical pipeline.
Outpatient and private medical clinics frequently struggle with manual record keeping that compromises patient safety and operational throughput.
System Architecture & Execution Flow
User (Browser)
↓
React Frontend (Vite + Context API)
↓
Axios API Client
↓
Express REST API Gateway
↓
Auth (JWT) + RBAC Middleware
↓
Service Layer (Patients, Cases, Visits, Rx, Billing, Queue)
↓
SQLite Database (WAL Mode Concurrency)Multi-Tier Architectural Layers
React, Vite, Context API, Tailwind CSS
Two-column canvas layout, role-based route guards, real-time consultation queue board, and print-friendly A4/thermal styling.
Express.js, JWT, bcrypt
Token authentication, role-based permission verification (Admin, Doctor, Receptionist), request validation, and CORS enforcement.
Node.js Modular Services
Domain-driven services managing patient indexing, clinical case grouping, prescription formulation, and invoice balance tracking.
SQLite in WAL Mode
Relational database with foreign key cascades, migration-based schema evolution, and Write-Ahead Logging for high-concurrency read operations.
Core Engineering Modules & Workflows
Fast indexed search by name, phone, or MRN. Stores comprehensive demographics, chronic conditions, and emergency contacts.
Groups recurring visits under medical cases. Captures chief complaints, clinical diagnoses, vitals (BP, pulse, temp), and doctor notes.
Digital prescription builder linking drug names, dosage templates, frequency timings, and durations directly to clinical visits.
Calculates consultation fees, medications, and procedural charges. Supports partial payments, cash/UPI/card tags, and balance receipts.
Live status tracker enabling receptionists to queue arrivals and doctors to transition states (Waiting → In Consultation → Completed).
Granular route protection ensuring doctors only view medical data while reception staff handle bookings and cashiering.
Print-optimized CSS templates rendering clean, branded A4 medical summaries and compact thermal payment receipts with zero UI clutter.
Persistence Schemas & Execution Contracts
Database Schema & Entity Structure
Patient (id, name, phone, age, gender, address, created_at)
└── Case (id, patient_id, title, status, started_at)
└── Visit (id, case_id, diagnosis, vitals, doctor_notes, visit_date)
├── Prescription (id, visit_id, medicine_name, dosage, frequency, days)
└── Billing (id, visit_id, total_amount, paid_amount, payment_mode, status)Key Endpoints & Query Interfaces
Engineering Challenges & Specifications
Technical Obstacles Solved
Resolution: Configured SQLite Write-Ahead Logging (WAL) mode, separating write transactions from concurrent read operations across staff workstations.
Resolution: Created isolated @media print stylesheets stripping interactive buttons, navigation headers, and shadows for crisp A4 documentation.
Technology Stack Matrix
| Category | Tooling & Frameworks |
|---|---|
| Frontend Framework | React with Vite bundler |
| State & Routing | React Router, React Context API |
| Backend Runtime | Node.js, Express.js REST API |
| Database Engine | SQLite with WAL Concurrency |
| Authentication | JSON Web Tokens (JWT) + bcrypt |
| Deployment | Windows Service, Localhost HTTPS Daemon |