CASE STUDY · SYSTEM
Clinic HolisticHubPro
Modernization of a Laravel 5.6 Blade clinic CRM into Laravel 13 + Vue 3: same clinical and billing rules, new API/SPA surface.
TECHNICAL PUBLICATION
How it is built
USE CASE
Business challenge
3D Lifestyle’s appointment CRM (fat Blade controllers, Passport, jQuery DataTables) could not move to PHP 8 / Laravel 12+ without a rewrite. Business rules had to stay identical.
SYSTEM ARCHITECTURE
Architecture & data
Lead → Patient → Appointment → Package/Invoice → Wallet → Reports. Schema meaning preserved; controllers thinned into services; Vue lists replace DataTables. Sanctum replaces Passport for admin and optional mobile APIs.
BACKEND
API design & authentication
Sanctum, Spatie roles/permissions, Google 2FA. Branch mapped to clinic centre.
IMPLEMENTATION
Implementation & stack
Clean Laravel 13 migrations conceptually aligned with the old tables. Vue CRUD for masters, leads, appointments, bundles, invoices, refunds, wallet ledger, reports. Meezan payment port retained as a wallet/payment path.
SCALING
Performance & operations
Same operational dataset, modern query patterns and API pagination. No invented clinical metrics.
STACK
As shipped
7 components
What this system runs on
The stack as deployed for Clinic HolisticHubPro — chosen for the system's constraints, not for fashion.
RELATED WORK
More systems
ENGAGE
Need a system like this?
Operational platforms, APIs, and AI-integrated systems — scoped as an engineer, with a stack and a boundary.