PHP PHARMACY MANAGEMENT DESIGN

I am building a Pharmacy Management System that is designed to be run on XAMPP

localhost. The system should be developed using HTML, CSS, PHP, MySQL, and

JavaScript. Below are the specific requirements for the system:

1. LOGIN PAGE

The system should have a login page where users can enter their username and password.

The login page should include:

Input fields for Username and Password.

A 'Remember Me' checkbox for user sessions.

A 'Forgot Password' link that redirects users to a page for resetting their password.

The system should authenticate users by checking the credentials from a MySQL database.

There should be role-based access control, meaning the system must recognize whether the user

is a Super Admin, Admin, or Pharmacist after login and redirect them to their respective

dashboards.
2. USER ROLES

The system should support multiple user roles:

Super Admin: Has full control over all system settings, user management, and can view and

manage all pharmacies.

Admin: Manages one or more pharmacies, their inventory, and can add users under their

assigned pharmacy.

Pharmacist: Can manage the inventory and prescriptions within their assigned pharmacy.

3. SUPER ADMIN DASHBOARD

After logging in, the Super Admin should be able to access a dashboard that includes:

User Management: View all users, add new users (Admins and Pharmacists), edit user details,

and assign users to specific pharmacies.

Pharmacy Management: Add new pharmacies, edit pharmacy details, and assign pharmacies to

Admins.

Inventory Management Overview: A consolidated view of all pharmacies' inventories with

options to view detailed reports by pharmacy.

Sales Reports: Ability to generate sales reports across all pharmacies with filters by date,

pharmacy, and user.

System Settings: Control over various system settings like changing the database connection or

system branding (logo, name, etc.).

Pharmacy Overview: Admins should be able to see an overview of the pharmacies they

manage, including inventory levels, sales, and active pharmacists.

Inventory Management: Admins can add, edit, and delete medicines. This includes:

Adding new medicine details such as name, batch number, expiry date, quantity, and price.

Updating inventory when stock arrives or expires.

Alert system for low stock or expired medicines.

Sales Management: Admins should be able to track sales, view receipts, and generate reports

for their assigned pharmacies.

Pharmacist Management: Admins can manage Pharmacists working in their pharmacies by

adding, editing, and removing Pharmacists.

5. PHARMACIST DASHBOARD

Pharmacists should have access to a streamlined interface where they can:

View Inventory: Check the stock of medicines in their assigned pharmacy.

Sell Medicines: Record sales by selecting medicines from the inventory and generating a receipt

for customers.

Manage Prescriptions: View and manage customer prescriptions. Option to mark medicines as

sold based on a prescription.

6. INVENTORY SYSTEM

The inventory system should allow for:

Adding New Medicines: Including name, quantity, expiry date, and purchase price.

Batch Management: Manage medicines by batches (e.g., batch number and expiry).

Search and Filter: Search inventory by name, batch number, or expiration date, and filter based

on low stock or expired medicines.

Real-Time Stock Updates: Whenever a sale is made or new stock is added, the system should

automatically update the inventory.

7. SALES AND PRESCRIPTION SYSTEM

Sales Management: Pharmacists can sell medicines by selecting items from the inventory and

entering the quantity. The system should generate an itemized receipt.

Prescription Management: Pharmacists should be able to associate sales with customer

prescriptions and log information about which medicines were dispensed for which prescription.

Sales Reports: Generate daily, weekly, or monthly sales reports for each pharmacy with the

ability to export the data (e.g., as a PDF or CSV file).

The MySQL database should have tables for:

Users: For storing user details like username, password (hashed), role (Super Admin, Admin,

Pharmacist), and assigned pharmacy (if applicable).

Pharmacies: Details of each pharmacy, including name, location, and contact information.

Medicines: Store medicine information, including name, batch number, expiry date, quantity,

and price.

Inventory: Tracks the stock of medicines in each pharmacy.

Sales: Logs sales transactions, including date, user who processed the sale, medicines sold, and

total amount.

Prescriptions: Stores information about prescriptions filled by Pharmacists.

9. Security

Passwords should be stored in the database using a secure hashing algorithm (e.g., bcrypt).

The system should implement session management to track logged-in users and prevent

unauthorized access.

Admin pages should be protected, and only authorized users should have access based on their

role.
Input validation and sanitization should be in place to protect against SQL injection and XSS

attacks.

10. FRONTEND/BACKEND TECHNOLOGIES

The frontend should use HTML and CSS for structure and styling, while JavaScript will

handle dynamic functionalities (such as form validation, alerts, etc.).

The backend should use PHP to handle server-side logic, including user authentication, inventory

management, and report generation.

AJAX (Asynchronous JavaScript and XML) should be used to allow for real-time updates to

inventory and other data without needing full page reloads.

11. RUNNING ON XAMPP

The system should be designed to run locally using the XAMPP server.

All database operations should connect to a MySQL database hosted locally on XAMPP.

Instructions should be provided on how to configure the php.ini and httpd.conf files if needed to

make the system function properly.

12. ADDITIONAL FEATURES

Search Functionality: A global search bar that allows users to search for medicines,

prescriptions, or sales records.

Notifications System: Notifications for low stock, expired medicine, or upcoming expiry within

30 days.

Backup/Restore Functionality: The ability to back up the database and restore it from a file.
Based on the above requirements, please provide me with the code architecture, folder structure,

and the database schema design to start building this system."