uzaam07/hospital-management-system

How uzaam07/hospital-management-system works

This PHP/MySQL hospital system serves patients, doctors, and administrators. The visible workflow starts at the role-selection/registration page, routes form submissions to authentication or registration handlers, then presents role-specific dashboards for appointments, patient records, and prescriptions. Patient booking and doctor prescription entry are distinct clinical stages backed by MySQL. The README also describes bill downloads and payment, but no implementing source appears in the tree; that capability is shown as unverified. Connections reflect the excerpts and README, not an inspection of unsampled files.

Main entry points: database.php Database connection · patient/dashboard.php Patient dashboard · index.php Role entry · doctor/dashboard.php Doctor dashboard

Components 16

Entry and Identity

Role entry index.php
Patient registration includes/func2.php
Patient login includes/func.php
Doctor login includes/func1.php
Admin login includes/func3.php

Patient Care

Patient dashboard patient/dashboard.php
Appointment booking and history patient/dashboard.php
Prescription history patient/dashboard.php
Bills and payment patient

Clinical Work

Doctor dashboard doctor/dashboard.php
Prescription authoring doctor/prescribe.php

Administration

Admin dashboard admin/dashboard.php

Persistence

Doctor and specialty lookup includes/newfunc.php
Database connection config/database.php

Other components

Hospital user
MySQL database

Connections 30

Hospital user → Role entry: opens README.md
Role entry → Patient registration: submits registration index.php
Role entry → Doctor login: submits login index.php
Role entry → Admin login: submits login index.php
Role entry → Patient login: login documented README.md
Patient registration → Database connection: uses connection includes/func2.php
Patient login → Database connection: uses connection includes/func.php
Doctor login → Database connection: uses connection includes/func1.php
Admin login → Database connection: uses connection includes/func3.php
Patient login → Patient dashboard: redirects to includes/func.php
Doctor login → Doctor dashboard: redirects to includes/func1.php
Admin login → Admin dashboard: redirects to includes/func3.php
Patient dashboard → Appointment booking and history: provides patient/dashboard.php
Patient dashboard → Prescription history: provides patient/dashboard.php
Patient dashboard → Database connection: uses connection patient/dashboard.php
Patient dashboard → Doctor and specialty lookup: calls lookup helpers patient/dashboard.php
Appointment booking and history → MySQL database: writes and reads patient/dashboard.php
Prescription history → MySQL database: reads patient/dashboard.php
Doctor dashboard → Database connection: uses connection doctor/dashboard.php
Doctor dashboard → Prescription authoring: links to doctor/dashboard.php
Doctor dashboard → MySQL database: reads doctor/dashboard.php
Prescription authoring → Database connection: uses connection doctor/prescribe.php
Prescription authoring → MySQL database: reads and writes doctor/prescribe.php
Admin dashboard → Database connection: uses connection admin/dashboard.php
Admin dashboard → Doctor and specialty lookup: calls count helpers admin/dashboard.php
Admin dashboard → MySQL database: reads and deletes admin/dashboard.php
Doctor and specialty lookup → Database connection: uses connection includes/newfunc.php
Doctor and specialty lookup → MySQL database: queries includes/newfunc.php
Database connection → MySQL database: connects to config/database.php
Patient dashboard → Bills and payment: bill access documented

Drawn by GitDiagram on November 14, 2026 from the repository's file tree, README and source files. Read as Markdown ·