How hashenudara/edoc-doctor-appointment-system works
Project Type and Purpose
• The project is a web-based, multi-role appointment booking system built using PHP, HTML, and CSS.
• Its purpose is to allow patients to make online appointments; enable doctors to manage schedules and appointments; and allow an administrator to handle doctor details, schedules, and overall system management.
• Additionally, the project is containerized (it includes a Dockerfile and docker-compose.yml) and uses a MySQL database (as indicated by SQL_Database_edoc.sql).
File Structure
• The file tree shows separate directories for the three main user roles – admin, doctor, and patient – each containing role-specific PHP pages for functionalities like appointments, profile editing, and schedule management.
• There are shared resources such as CSS files (organized in a dedicated “css” folder with additional assets like fonts and animations), connection.php (which likely defines database connectivity), and public-facing pages like index.html, login.php, and signup.php.
• Presence of Docker-related files suggests container deployment and possible separation between the web server environment (Apache/PHP) and the database service (MySQL).
Core Components
• Client/Browser Layer: Representing the end-user accessing the application via web pages.
• Role-based UI Modules:
▪ Admin Panel: (admin/* files) – where the administrator manages doctors, sessions, and patient details.
▪ Doctor Dashboard: (doctor/* files) – for handling appointment views, session management, and settings.
▪ Patient Portal: (patient/* files) – for making appointments, account management, and viewing bookings.
• Web Server / Application Layer:
▪ The PHP application, which includes all logic across various directories. It connects to the database using connection.php.
▪ Static assets (CSS, images, HTML) used to render the interface.
• Database Layer:
▪ MySQL database (as defined by SQL_Database_edoc.sql) which stores user details, appointments, doctor schedules, etc.
• Containerization:
Relationships and Interactions
• Clients (Admins, Doctors, and Patients) interact with the system via their respective web interfaces.
• The PHP backend handles requests and communicates with the MySQL database for operations such as booking, editing, and deleting appointments or sessions.
• Authentication flows (login.php, logout.php) tie into the user role distinction and should be shown as directional data flows.
Instructing the Principal Software Engineer
• Web Clients (Browsers) accessing the system.
• The central PHP application layer that processes requests.
• The MySQL database with which the application interacts.
• From the client to the PHP server.
• From the PHP server to the database for CRUD operations.
• From the database back to the PHP server for response generation.
• If needed, include deployment components indicating how Docker and docker-compose are used to run the Apache/PHP and MySQL containers.