Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

27 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Organ donation icon

web-based-organ-donation-system

Role-based organ donation workflow app powered by PHP, MySQL, Bootstrap, and jQuery.

Version 1.0.0 MIT License Organ donation app

PHP MySQL Bootstrap jQuery Apache

Project intro Install guide Entry points

web-based-organ-donation-system β€” README

Role-based PHP/MySQL web application for organ request management, doctor review, admin approval workflow, and prescription-to-medicine fulfillment.

Table of Contents

πŸš€ Project intro

web-based-organ-donation-system is a multi-role healthcare workflow app with:

  • User registration/login and organ application submission
  • Admin review, doctor assignment, and final approve/reject actions
  • Doctor recommendation and prescription generation
  • Pharmacist medicine inventory and order processing
  • End-to-end medicine ordering and delivery status tracking

It is designed as an academic/project-friendly foundation for organ donation and associated treatment operations.

πŸ“ Project structure

Web-based-Organ-Donation-System/
β”œβ”€β”€ index.html
β”œβ”€β”€ style.css
β”œβ”€β”€ README.md
β”œβ”€β”€ LICENSE
β”œβ”€β”€ Image/
β”œβ”€β”€ admins/
β”‚   β”œβ”€β”€ dashboard.php
β”‚   β”œβ”€β”€ adminsignin.php / adminsignup.php
β”‚   β”œβ”€β”€ accept.php / doctorassign.php / assign.php
β”‚   β”œβ”€β”€ addpharmacy.php
β”‚   β”œβ”€β”€ userdelete.php / doctordelete.php / applicationdelete.php
β”‚   β”œβ”€β”€ inc/
β”‚   β”‚   β”œβ”€β”€ config.php
β”‚   β”‚   └── head.php
β”‚   β”œβ”€β”€ css/ js/ images/ fonts/
β”‚   └── ...
β”œβ”€β”€ users/
β”‚   β”œβ”€β”€ dashboard.php
β”‚   β”œβ”€β”€ signin.php / signup.php
β”‚   β”œβ”€β”€ organ.php
β”‚   β”œβ”€β”€ ordermedicine.php / ordermedicinepannel.php
β”‚   β”œβ”€β”€ usercomment.php / userpriceacceptreject.php
β”‚   β”œβ”€β”€ css/ images/ fonts/
β”‚   └── ...
β”œβ”€β”€ doctors/
β”‚   β”œβ”€β”€ doctorshomepage.php
β”‚   β”œβ”€β”€ doctorsignin.php / doctorsignup.php
β”‚   β”œβ”€β”€ accept.php
β”‚   β”œβ”€β”€ prescription.php
β”‚   β”œβ”€β”€ inc/
β”‚   β”‚   β”œβ”€β”€ config.php
β”‚   β”‚   └── head.php
β”‚   β”œβ”€β”€ css/ js/ images/ fonts/
β”‚   └── ...
└── pharmacist/
    β”œβ”€β”€ dashboard.php
    β”œβ”€β”€ pharmacistsignin.php / pharmacistsignup.php
    β”œβ”€β”€ addmedicine.php / medicinedetailsupdate.php
    β”œβ”€β”€ priceupdate.php / deliverystatuschange.php
    β”œβ”€β”€ inc/
    β”‚   β”œβ”€β”€ config.php
    β”‚   └── head.php
    β”œβ”€β”€ css/ js/ images/
    └── ...

⭐ Differentiators

  • Full role separation (Admin, User, Doctor, Pharmacist) with dedicated dashboards
  • Practical workflow from organ request β†’ doctor recommendation β†’ admin decision
  • Integrated post-approval prescription and pharmacy order lifecycle
  • Bootstrap-based UI with modal-driven dashboard operations

πŸ”§ Features

Core features

Feature Status Notes
User authentication βœ… Current Signup/signin/logout for users
Admin authentication βœ… Current Admin account management and dashboard access
Doctor authentication βœ… Current Doctor signup/signin and assigned application view
Pharmacist authentication βœ… Current Pharmacist signup/signin and medicine/order handling
Organ application βœ… Current Users submit organ requests with date/reason
Doctor assignment βœ… Current Admin assigns doctors to pending applications
Application decision βœ… Current Admin approves/rejects applications
Recommendation flow βœ… Current Doctors write recommendation/decision for assigned cases
Prescription flow βœ… Current Doctors create prescriptions for approved cases
Medicine order flow βœ… Current Users place orders from prescriptions
Pharmacy operations βœ… Current Stock updates, pricing, comments, delivery updates

🧭 Flow diagrams

1) End-to-end application journey

flowchart TD
  A[Visitor] --> B[Landing page]
  B --> C{Has account?}
  C -- No --> D[Register]
  D --> E[Login]
  C -- Yes --> E
  E --> F[User dashboard]
  F --> G[Submit organ request]
  G --> H[Admin reviews request]
  H --> I{Doctor assigned?}
  I -- No --> H
  I -- Yes --> J[Doctor reviews case]
  J --> K[Admin approve or reject]
  K -- Reject --> L[Notify user]
  K -- Approve --> M[Create prescription]
  M --> N[User places medicine order]
  N --> O[Pharmacist processes order]
  O --> P[Update delivery status]
  P --> L
Loading

2) User request flow

flowchart TD
  A[User signs in] --> B[Open organ request form]
  B --> C[Fill personal and request details]
  C --> D[Submit request]
  D --> E[Track application status]
  E --> F{Approved?}
  F -- No --> G[Wait for admin or doctor action]
  F -- Yes --> H[View prescription]
  H --> I[Order required medicine]
  I --> J[Track delivery]
Loading

3) Admin, doctor, and pharmacy workflow

flowchart TD
  A[Admin dashboard] --> B[View pending applications]
  B --> C[Assign doctor]
  C --> D[Doctor accepts case]
  D --> E[Doctor adds recommendation]
  E --> F{Admin decision}
  F -- Reject --> G[Delete or close application]
  F -- Approve --> H[Generate prescription]
  H --> I[Pharmacist updates stock and price]
  I --> J[Process medicine order]
  J --> K[Update delivery status]
  K --> L[User receives completion notice]
Loading

4) Route access control flow

flowchart TD
  A[Request enters app] --> B{Authenticated?}
  B -- No --> C[Send to public pages]
  B -- Yes --> D{Role}
  D -- User --> E[/users/* routes/]
  D -- Doctor --> F[/doctors/* routes/]
  D -- Admin --> G[/admins/* routes/]
  D -- Pharmacist --> H[/pharmacist/* routes/]
  E --> I[User dashboard and organ flow]
  F --> J[Doctor assignment and prescription flow]
  G --> K[Admin moderation and assignment flow]
  H --> L[Inventory and delivery flow]
Loading

Route protection behavior

  • Public entry: /index.html
  • Admin routes: /admins/* (requires admin session)
  • User routes: /users/* (requires user session)
  • Doctor routes: /doctors/* (requires doctor session)
  • Pharmacist routes: /pharmacist/* (requires pharmacist session)

🧰 Tech stack

  • Backend: PHP (procedural style with mysqli)
  • Database: MySQL / MariaDB
  • Frontend: HTML, CSS, Bootstrap, JavaScript, jQuery
  • Hosting target: Apache + PHP runtime (XAMPP/WAMP/LAMP compatible)

βš™οΈ Install methods

πŸ“¦ XAMPP / WAMP / LAMP (Apache + PHP + MySQL)

Prerequisites:

  • PHP 7.4+ (or newer)
  • MySQL/MariaDB
  • Apache web server
git clone https://github.com/rootcode-creator/Web-based-Organ-Donation-System.git
cd Web-based-Organ-Donation-System
  1. Copy project into your web root (htdocs / www).

  2. Create/import the MySQL database schema used by this project.

  3. Configure database connection in each role config file:

  • admins/inc/config.php
  • doctors/inc/config.php
  • pharmacist/inc/config.php
  1. Start Apache + MySQL.

  2. Open http://localhost/Web-based-Organ-Donation-System/.

πŸ” Configuration

This project does not use .env by default. It uses direct DB config in PHP files:

$host = "localhost";
$dbUsername = "your_db_user";
$dbPassword = "your_db_password";
$dbName = "your_db_name";

Notes:

  • Keep all role config files synchronized.
  • Never commit real production credentials.
  • Rotate any exposed credentials before deployment.

πŸ—„οΈ Database structure

Main tables used in codebase:

  • users
  • admins
  • doctors
  • pharmacist
  • pharmacy
  • organ
  • prescription
  • ordermedicine
  • stockmedicine

Typical workflow:

  • users submit to organ
  • admins assign doctor (organ.doctor_info) and set application status
  • doctors write recommendations and insert into prescription
  • users place orders into ordermedicine
  • pharmacist updates stockmedicine, pricing, comments, and delivery status

πŸ“œ Entry points

  • Landing page: index.html
  • Admin login: admins/adminsignin.html
  • User login: users/signin.html
  • Doctor login: doctors/doctorsignin.html
  • Pharmacist login: pharmacist/pharmacistsignin.html

πŸš€ Deployment notes

  • Ensure all module-level config.php files point to the same database.
  • Use HTTPS and secure session settings in production.
  • Add server-side validation/sanitization hardening before public deployment.
  • Move credentials from source files to environment variables for safer operations.

🀝 Contributing

  • Fork the repository and create a focused feature branch.
  • Keep pull requests scoped and include verification steps.
  • Never commit credentials, secrets, or production config.

πŸ“„ License

This project is licensed under the MIT License. See the LICENSE file for details.

Releases

Packages

Used by

Contributors

Languages