MediManage is a full-stack application designed to streamline the management of small clinics. It provides an intuitive interface for handling patient records, scheduling appointments, and overseeing other essential administrative tasks. With its robust features and user-friendly design, MediManage ensures efficient and organized clinic operations.

📚 Features

• Multi-role medical management system with support for patients, doctors, attendants and admins.
• Appointment scheduling and management (create, update, cancel, list).
• Medical records and prescription management with versioned entries.
• Articles, notices and category management for clinic communications.
• Built-in user authentication and role/permission management (Spatie Permission, Fortify).
• Server-side rendering support via Inertia and optional SSR flows.
• Auditing and activity logging for sensitive operations.

🚀 Built with

• PHP 8.4+ and Laravel 12
• Inertia.js + React (frontend views)
• TailwindCSS for styling
• SQLite / MySQL (configurable) for database
• Spatie Laravel Permission for roles & permissions
• Barryvdh DOMPDF for PDF generation
• Pest / PHPUnit for tests

🛠️ Project setup

This section explains how to set up the project on a development machine (Windows/XAMPP example). If you're on macOS or Linux, the same steps apply but replace XAMPP with your preferred PHP stack and adapt shell commands accordingly.

Requirements

• PHP 8.4 or later
• Composer
• Node.js (LTS recommended) and npm
• XAMPP (or another local PHP/MySQL stack) for Windows
• Git

Initial setup (Windows + XAMPP + PowerShell)

Or, on Unix-like systems (macOS / Linux with bash): examples are provided below where relevant.

1. Clone the repository:

git clone https://github.com/Barata-Ribeiro/MediManage.git
cd MediManage

2. Install PHP & Node dependencies

composer run setup

3. Configure environment

The command above already copies .env.example to .env and generates the application key. However, you may need to further edit .env to set database connection and other environment variables.

The most important ones are:

APP_NAME='YourAppName'
APP_ADMIN_EMAIL='[email protected]'
APP_ADMIN_NAME=Administrator
APP_ADMIN_PASSWORD='123456A#'
APP_ADMIN_FIRST_NAME='Sr. Admin'
APP_ADMIN_LAST_NAME='of Site'

If you plan to use MySQL instead of the default SQLite, update the DB_* variables accordingly; uncomment the relevant lines and provide your MySQL credentials.

4. Database File (Optional)

• If you're using the default sqlite in .env (DB_CONNECTION=sqlite), create the database file:

# Windows PowerShell
New-Item -Path database\database.sqlite -ItemType File -Force

# macOS / Linux (bash)
mkdir -p database
touch database/database.sqlite

5. Database migrations & seeders

php artisan migrate --seed

6. Start the local server (Laravel development server):

composer run dev
#SSR:
composer run dev:ssr

Notes about XAMPP

• If you prefer to use Apache from XAMPP, point your virtual host or DocumentRoot to the project public folder.
• Ensure the PHP version bundled with XAMPP meets the project's PHP requirement (8.4+). If not, use a more recent PHP installation or update XAMPP.

Common environment variables you should set in .env

• APP_URL — base URL for the application
• DB_CONNECTION, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, DB_PASSWORD — database connection
• MAIL_* — mailer settings
• APP_ADMIN_EMAIL, APP_ADMIN_PASSWORD — initial administrator credentials used by seeders (check .env.example)

Troubleshooting tips

• If you see permission errors writing to storage or bootstrap/cache, ensure Windows user has write access to those folders.
• If assets don't load, ensure you ran npm install and npm run dev (or npm run build for production) and that public/build exists.

🗂️ Folder structure

High-level overview of important folders and files in this repository:

• app/ — Laravel application source (Models, Controllers, Services, Providers, etc.).
• bootstrap/ — Framework bootstrap files and cache.
• config/ — Configuration files for Laravel and packages.
• database/ — Migrations, factories and seeders.
• public/ — Document root; compiled assets and index.php.
• resources/ — Frontend assets, views, Inertia React components, styles and JS entry points.
• routes/ — Route definitions split by responsibility (web, api, admin, appointments, etc.).
• storage/ — Logs, compiled Blade views, file uploads and cache.
• tests/ — Pest/PHPUnit tests (Feature & Unit).
• vendor/ — Composer dependencies (do not edit).

Important files

• .env.example — Example env, copy to .env and edit for local environment.
• artisan — Laravel CLI.
• composer.json & package.json — PHP and Node package manifests.
• vite.config.ts — Frontend bundler config.

Try it (quick start)

Option 1 — Full setup using the composer script (recommended):

composer run setup

Or manually, Option 2 — Manual setup:

1. Copy .env and set DB to sqlite (or configure MySQL). Create sqlite file if needed:

# Windows PowerShell
composer install
Copy-Item .env.example .env
php artisan key:generate
New-Item -Path database\database.sqlite -ItemType File -Force
php artisan migrate --seed
npm install
npm run dev
php artisan serve

# macOS / Linux (bash)
composer install
cp .env.example .env
php artisan key:generate
mkdir -p database
touch database/database.sqlite
php artisan migrate --seed
npm install
npm run dev
php artisan serve

2. Open http://127.0.0.1:8000 in your browser.

🪲 Bugs / ToDo

There are bugs and/or implementations that require some attention.

• Adjust user's home dashboard with better info.
• Implement route for notice details view.
• Implement route for notice deletion.
• Implement route for contract creation.
• Implement route for contract editing.
• Implement delete functionality for roles.
• Add delete confirmation modals for some actions.

🤝 Contributing

Contributions, issues, and feature requests are welcome! Feel free to check the issues page if you want to contribute.

📜 License

This project is free software available under the GPLv3 license.