Appearance
What is MedRegia?
MedRegia is a web-based pharmaceutical vendor-management platform designed for pharmacies to manage their entire supplier ecosystem from one place.
Purpose
Pharmacies deal with dozens of vendors — manufacturers, wholesalers, dealers, and agencies. Keeping track of who you owe money to, how much, and when it's due is critical. MedRegia centralises:
- Vendor records — all supplier details including drug license numbers
- Purchase invoices — what was bought, for how much, and when it's due
- Payment transactions — every payment made against each invoice
- Team access — who can do what, controlled through roles and permissions
Core Concepts
| Concept | Description |
|---|---|
| Vendor | A pharmaceutical supplier (manufacturer, wholesaler, dealer, agency, or your own pharmacy) |
| Invoice | A purchase invoice raised against a vendor with an amount and due date |
| Transaction | A payment recorded against an invoice (Cash / UPI / Net Banking) |
| Outstanding Balance | The total unpaid amount across all active invoices for a vendor |
| Role | A named set of permissions assigned to users (e.g. Admin, Pharmacist) |
| Policy | A named bundle of permissions that can be attached to roles or individual users |
| Permission | A Collection:Action pair (e.g. Vendor:Read) that controls a specific API action |
Tech Stack
| Layer | Technology |
|---|---|
| API | .NET 10, ASP.NET Core, Dapper, MySQL |
| Frontend | Vue 3, TypeScript, Vite, Tailwind CSS v4 |
| Auth | JWT (HS256), BCrypt password hashing |
| Database | MySQL 8, schema managed by DbUp |
| Infrastructure | Docker, Nginx (reverse proxy) |
Documentation Sections
- Guide → — Local setup, architecture overview
- Backend → — Module structure, conventions, migrations
- Frontend → — Feature-Sliced Design, components, conventions
- API Reference → — Every endpoint documented
- User Manual → — How to use the application
- Deployment → — Docker, environment variables, production