Karmaveer Shankarao Kale Education Society’s

GAUTAM POLYTECHNIC INSTITUTE, GAUTAMNAGAR

A Final Report On
“Online Doctor Appointment
Booking System”

Submitted By
Mr. SAYYED REHAN AMIN (2216690061)
Ms. BORSE VAISHANAVI SITATAM (2216690016)
Ms. WAGH SHRADDHA NANAJI (2216690017)
Ms. JADHAV SANCHITA RAOSAHEB (2216690020)

Co-Ordinator
(Prof. Mr. Mapari S.A.)
YEAR 2024-25
Online Doctor
Appointment Booking
System
Project Overview
Problem Statement Proposed Solution
• Inefficiencies in traditional booking • Streamline appointment scheduling
• Time-consuming phone calls • 24/7 availability
• Scheduling conflicts • Automated reminders
• Limited accessibility • Centralized system

Online system improves scheduling with 24/7 access and automated reminders.
Objectives
1 Develop User-Friendly System
Achieve a SUS score of 70 or higher.

2 Enhance Patient Access

Increase rural area bookings by 20%.

3 Reduce Administrative Burden

Decrease workload by 15%.

4 Improve Patient Satisfaction

Achieve a satisfaction score of 4.5/5.

Primary objective: Efficient online appointment booking.

System Architecture
Front-End Back-End
HTML, CSS, JavaScript, PHP 7.4 or later.
Bootstrap.

Database
MySQL for data storage.

Scalable design for up to 100,000 patient records.

Key Features
Patient Module

Doctor Module

Admin Module

Patient, doctor, and admin modules for comprehensive functionality.

Advantages for Patients
1 Convenience
24/7 access from anywhere.

2 Reduced Wait Times

Eliminate phone calls.

3 Transparency
Clear view of doctor availability.

4 Appointment Reminders
Minimize missed appointments.

Easy access to details and medical history.

Advantages for
Doctors/Administrators
Streamlined Scheduling
Automated booking.

Reduced Workload
Less time on calls.

Improved Efficiency
Optimize schedules.

Data-Driven Insights
Access to reports.

Automated reminders and notifications to patients improve communication.

Implementation & Testing
Unit Testing
1 PHPUnit.

Integration Testing
2 Module interaction.

User Acceptance Testing

3 Real user testing.

Cloud-based server deployment for scalability and reliability.

Challenges & Enhancements

System Integration
2 Integrate with EHR/EMR.

Data Security 1
Address privacy concerns.

User Adoption
Provide training.
3

Future: Telemedicine, mobile app, AI chatbot.

Online Doctor
Appointment Booking
System Testing
This presentation summarizes the testing phase of our online
doctor appointment booking system. We focused on ensuring
reliability, functionality, and security. This was a final year project
developed using PHP. We will cover testing methodologies, results,
and future work.
Testing Objectives and Scope
Goal

Ensure system reliability and security before deployment.

Scope
• User registration and login
• Doctor profiles
• Appointment scheduling

Out of Scope
• Server infrastructure testing
• Third-party API performance
Testing Methodologies Employed
Unit Testing
Verified individual functions in isolation using PHPUnit.

Integration Testing
Tested interactions between different modules. Used Selenium.

System Testing
Evaluated the entire system against specified requirements.

We employed a comprehensive testing strategy to ensure all parts of the system

worked correctly.
Test Case Design and Execution

Test Case Test Data Execution

Management Environment
Created realistic test data
Designed 150+ test for various scenarios. PHP 8.1, MySQL 8.0,
cases, managed using Apache 2.4.
TestRail.
Each test case included detailed steps and expected results. For example, verifying
successful appointment booking.
Bug Reporting and Tracking
Bug Tracking System Severity Classification
Jira was used to manage reported Classified bugs as Critical, High,
issues. Medium, or Low.

Resolution Workflow
Defined a clear bug resolution workflow.

We reported and tracked 75 bugs, prioritizing them based on their severity.

 Security Testing

Authentication and
Authorization Testing

Vulnerability Assessment

Data Validation

We used OWASP ZAP and Nikto for vulnerability assessment. We tested for SQL injection, XSS, and CSRF vulnerabilities.
Testing Results and Analysis
99.9% 75
System uptime during testing Total bugs reported

85%
Code coverage

Key issues were identified and resolved. The system showed good stability and
performance.
Conclusion and Future Work
Achievements Future Enhancements
Successfully tested all core modules and delivered a • Advanced security testing
stable system. • Performance testing tools
• Automated testing scripts
Online Doctor
Appointment System:
HW/SW Requirements
This presentation outlines the necessary hardware and software
components. We'll focus on building a scalable, secure, and user-
friendly online doctor appointment system. Let's explore the key
elements required for successful deployment and operation.
System Architecture Overview
Client-Server Model Key Components

The system follows a client-server architecture. The Essential components include a web server, application
front-end consists of patient and doctor interfaces. The server, and a robust database server. These elements
back-end manages the server and database. work together seamlessly for optimal performance.
Server-Side Hardware
CPU RAM
Intel Xeon E3-1200 series Minimum 8GB, but 16GB
(or equivalent) with 4+ is recommended.
cores and 3.0 GHz+ is Sufficient RAM is needed
recommended. This for caching and
handles appointment concurrent user sessions.
scheduling and user
authentication.

Storage
A 500GB SSD minimum is required for the operating system,
applications, and database. Consider an NVMe SSD for faster
I/O.
Server-Side Software
Operating System
Linux (Ubuntu 20.04 LTS, CentOS 8) or Windows Server 2019 ensures stability.

Web Server
Nginx or Apache serves content and provides load balancing.

Application Server
Node.js, Python (Django/Flask), or Java (Spring Boot) handles business logic.
Database Requirements
Storage
Scalable solution (cloud-based) with
1TB+ capacity. Depends on data
DBMS 2
retention policies.
MySQL (v8.0+), PostgreSQL
(v13+), or MongoDB (v5.0+). 1
Stores patient data and Backup & Recovery
appointment schedules. Regular backups and a disaster
3 recovery plan are crucial. Daily full
and hourly incremental backups
recommended.
Client-Side Hardware
Desktop/Laptop
Intel Core i3 or equivalent, 4GB RAM, 128GB SSD is
needed.

Mobile
iOS (v13+) or Android (v8+) device for app or web
browser.

Network
Broadband internet (10Mbps+). A stable connection is
essential for video calls.
Client-Side Software
Web Browser Operating System
Latest versions of Chrome, Windows 10+, macOS
Firefox, Safari, or Edge are 10.15+, iOS 13+, Android
required. Supports HTML5, 8+ are compatible.
CSS3, JavaScript.

Video Conferencing
WebRTC or Zoom/Skype integration enables real-time
communication.
Security Requirements
Authentication
1 Multi-factor authentication (MFA) is essential.

Authorization
2 Role-based access control (RBAC) limits access.

Encryption
3 End-to-end encryption secures data.

Compliance
4 HIPAA and GDPR compliance is mandatory.
Online Doctor
Appointment System:
PHP-Based Overview
This presentation provides an overview of a PHP-based online
doctor appointment system. It covers the purpose, features, and
technologies used. The system targets patients, doctors, and
administrators. Key functionalities include appointment scheduling
and user authentication.
System Architecture
and Code Structure
The system follows an MVC (Model-View-Controller) architecture. The
directory structure includes `models`, `views`, `controllers`, and
`config`. Tables include `users`, `doctors`, and `appointments`. Core
files include `index.php`, `config.php`, `UserController.php`, and
`AppointmentController.php`.

Models Views
Data representation and User interface templates
database interaction

Controllers
Handle user requests and logic
Code Snippet: User Authentication
User authentication involves registration and login. Registration uses `password_hash()` for secure storage. Validation logic checks for empty fields
and valid email format. Login verifies credentials with `password_verify()` and session management.

Registration
Secure user account creation.

Login
Verifying credentials and user access.

Security
Protecting user data and preventing attacks.
Code Snippet: Appointment Scheduling
Appointment scheduling validates time slots. It then inserts data into the `appointments` table. Code checks doctor
availability. Retrieval uses `JOIN` queries to fetch user and doctor information. Use MySQL's `DATE_ADD` to
calculate time slots.

Creating Appointments Retrieving Appointments

Validating time slots and availability. Querying and displaying appointment data.
Error Handling: Input Validation
Common input validation errors include missing fields and invalid formats. PHP functions include `filter_var()` and
`htmlspecialchars()`. Validate email addresses using `filter_var($email, FILTER_VALIDATE_EMAIL)`. Client-side
validation improves user experience.

Prevention
1 Client-side validation

Sanitization
2 `htmlspecialchars()`

Validation
3 `filter_var()`
Error Handling: Database Connection
and Queries
Common database errors include connection failure and invalid SQL syntax. PHP uses `try-catch` blocks for
database operations. Use `mysqli_error()` to catch errors. This helps manage errors during database interactions.

Connection Queries
Establish a secure connection. Handle SQL exceptions.
ER Diagram
Interface Of DAMS
 Appointment Booking Section For
Users.
Login Page For Doctor
 Dashboard OF Doctor For Review
Appointment
 Conclusion
The project entitled Doctor Appointment system was completed

successfully. The system has been developed with much care and free of

errors and at the same time it is efficient and less time consuming. The

purpose of this project was to develop a web application and an android

application for purchasing items from a shop. This project helped us in

gaining valuable information and practical knowledge on several topics

like designing web pages using html & css, usage of responsive

templates, designing of android applications, and management of

database using MySQL. The entire system is secured. Also the project

helped us understanding about the development phases of a project and

software development life cycle. We learned how to test different features

of a project. This project has given us great satisfaction in having

designed an application which can be implemented to any nearby shops or

branded shops selling various kinds of products by simple modifications.

There is a scope for further development in our project to a great extent.

A number of features can be added to this system in future like providing

moderator more control over products so that each moderator can

maintain their own products. Another feature we wished to implement

was providing classes for customers so that different offers can be given

to each class. System may keep track of history of purchases of each