DAR ES SALAAM INSTITUTE OF TECHNOLOGY

DEPARTMENT OF ELECTRONICS AND TELECOMMUNICATION

ENGINEERING

BACHELOR OF ENGINEERING

NTA LEVEL 8

SENIOR FINAL PROJECT

PROJECT TITLE: ONLINE DOCTOR’S APPOINTMENT RESERVATION

SYSTEM FOR HOSPITAL

PROJECT TYPE: PROBLEM SOLVING

STUDENT NAME: RODRICK SAIMON LULU

ADMISSION NUMBER: 190640722194

ACADEMIC YEAR: 2021/2022

PROJECT SUPERVISOR: DR. MATIKO

JUNE, 2022
 DECLARATION

I, Rodrick Saimon Lulu, a student of Bachelor of Engineering in Electronics and

Telecommunication, declare that all works described in this report is my original work and has not
been copied from anywhere or presented elsewhere. Where information from other source has
been used, a proper citation and complete reference of the sources has been given to clearly show
what was quoted from other sources.

Candidate name: RODRICK SAIMON

Signature …………….

Date …………………

ii
 CERTIFICATION

As the candidate’s supervisor, I have approved this project report for submission.

Supervisor’s name: DR. MATIKO

Signature…………………………………...

Date………………………………………...

iii
 ABSTRACT

Recently, increasing number of hospitals have been an obvious trend in many Countries. This is
mainly because the needs to providing medical services to increasing patients due to various forms
of diseases. Such scenario needs careful attentions from the hospital management in order
to provide appropriate services to patients. One of the important tasks to ensure efficient health
care services is booking for medical appointments. With increasing number of patients, a
systematic appointment booking is crucial in order to provide an accurate and fast medical
treatment to patients. Conventional way of booking appointment is time consuming since it
requires patients to go to the hospital, in which eventually resulting in an increase in cost and effort.
To overcome such problem, the appointment booking system can be made online via the internet.
With an internet-based booking system, appointment booking can be done from anywhere and at
any time without having to go to the hospital, therefore is time- and cost-effective.

The aim behind this project is design and implement a smart appointment booking system that
provides patients or any user an easy way of booking a doctor’s appointment online. This is a web-
based application that overcomes the issue of managing and booking appointments according to
user’s choice or demands. The task sometimes becomes very tedious for the compounder or doctor
himself in manually allotting appointments for the users as per their availability. Hence this project
offers an effective solution where users can view various booking slots available and select the
preferred date, time and Doctor to see.

This project focuses on developing web-based appointment system to reduce waiting time and
improve upon the efficiency plus quality of delivering health care service.

After implementation of the objective the project were achieved, booking system can be used in
less populated hospital and referral ones. It gives chance for patient to view and selected doctor
based on their professional and date available. It ended in local hosting on implementation only
but it can be used for more advanced level by doing modification and allow webhosting for future
studies.

iv
 ACKNOWLEDGEMENT

Firstly, I would like to give thank GOD for health, and strength to write this report because it was
not an easy job. All praises, glory, and honour I give to him.

Secondly. I would like to take this opportunity to thank my mentor and project supervisor DR.
MATIKO, for his assistance from the recommendation of title idea and when I started this project
until it ended. His comments and assistance had made this project to reach where it was supposed
to reach, may GOD bless him. On the other hand, I would also like to thank Ms HAULE P. and
Dr. MKIRAMWENI who are the project coordinators of the department for their comments
concerning on project.

Thirdly, I would like to thank students of BENG 19 ETE especially my college whom we were
under same project supervisor for providing some ideas and information concerning the project,
since they all contributing on general overview ideas for the features that will make the system
more effective.

Lastly, I would like to thank the Doctors and patients / non patients that helped me during project
execution, data collection and system development.

v
 TABLE OF CONTENTS
DECLARATION ............................................................................................................................ ii

CERTIFICATION ......................................................................................................................... iii

ABSTRACT ................................................................................................................................... iv

ACKNOWLEDGEMENT .............................................................................................................. v

LIST OF ABBREVIATION .......................................................................................................... xi

LIST OF SYMBOLS .................................................................................................................... xii

LIST OF TABLES ....................................................................................................................... xiii

LIST OF FIGURES ..................................................................................................................... xiv

CHAPTER ONE ............................................................................................................................. 1

INTRODUCTION .......................................................................................................................... 1

1.1 Introduction ....................................................................................................................... 1

1.2 Background Information ................................................................................................... 2

1.3 Problem Statement ............................................................................................................ 2

1.4 Objectives ......................................................................................................................... 3

1.4.1 Main objective ....................................................................................................... 3

1.4.2 Specific objectives ................................................................................................. 3

1.5 Significance of the Project ................................................................................................ 3

1.6 Scope of the Project .......................................................................................................... 4

1.7 Project Limitation ............................................................................................................. 4

1.8 Project Methods ................................................................................................................ 4

1.8.1 Literature review .................................................................................................... 4

1.8.2 Data collection ....................................................................................................... 5

vi
 1.8.3 Data analysis .......................................................................................................... 5

1.8.4 System design and building prototype ................................................................... 5

1.8.5 System evaluation by users .................................................................................... 5

1.8.6 Refining prototype ................................................................................................. 6

1.8.7 Complete system .................................................................................................... 6

1.8.8 Writing report and submission ............................................................................... 6

1.8.9 Chapter conclusion................................................................................................. 6

1.9 Chapter Summary ............................................................................................................. 6

CHAPTER TWO ............................................................................................................................ 7

LITERATURE REVIEW ............................................................................................................... 7

2.0 Introduction ....................................................................................................................... 7

2.1 Background Information ................................................................................................... 7

2.2 Physical Booking System ................................................................................................. 7

2.3 Mobile Booking ................................................................................................................ 8

2.4 Interactive Voice Response (IVR) .................................................................................... 8

CHAPTER THREE....................................................................................................................... 10

PROPOSED SYSTEM ................................................................................................................. 10

3.0 Introduction ..................................................................................................................... 10

3.1 Proposed System ............................................................................................................. 10

3.2 Proposed System Block Diagram ................................................................................... 10

3.3 Components of Proposed System ................................................................................... 11

3.3.1 Computer.............................................................................................................. 11

3.3.2 Internet ................................................................................................................. 11

vii
 3.3.3 System (Online Doctor’s Appointment Reservation System) ............................. 12

3.3.5 Patient registration module .................................................................................. 12

3.3.6 Login module ....................................................................................................... 12

3.3.7 Patient management module ................................................................................ 12

3.3.8 Doctor management module ................................................................................ 12

3.3.9 Doctor schedule management module ................................................................. 12

3.3.10 Appointment management module .................................................................... 13

3.3.11 Web server ......................................................................................................... 13

3.3.12 Database server .................................................................................................. 13

3.4 Significance of the Proposed System .............................................................................. 13

3.5 Applications of the Proposed System ............................................................................. 13

CHAPTER FOUR ......................................................................................................................... 14

DATA COLLECTION ................................................................................................................. 14

4.0 Introduction ..................................................................................................................... 14

4.1 Collected Data ................................................................................................................. 14

4.2 Primary Data Collection ................................................................................................. 14

4.2.1 Interview .............................................................................................................. 14

4.2.2 Questionnaire ....................................................................................................... 15

4.3 Secondary Data Collection ............................................................................................. 17

4.3.1 Journals Reviewed ............................................................................................... 17

4.3.2 Article Reviewed ................................................................................................. 18

4.4 Design Requirement........................................................................................................ 18

CHAPTER FIVE........................................................................................................................... 20

viii
SYSTEM ANALYSIS .................................................................................................................. 20

5.0 Introduction ..................................................................................................................... 20

5.1 System Analysis .............................................................................................................. 20

5.2 Modules of Online Doctor Appointment Management System ..................................... 20

5.3 Proposed System Design Flow ....................................................................................... 21

5.4 Features of Online Doctor Appointment Management System ...................................... 21

5.4.1 Admin or Master Users ........................................................................................ 21

5.4.2 Doctor Users ........................................................................................................ 22

5.4.3 Patients Users ....................................................................................................... 22

5.4.4 Case Diagram for Admin, Doctor and Patient relation ........................................ 23

5.5 Database management system analysis .......................................................................... 24

5.5.1 Relational Data Model ......................................................................................... 24

CHAPTER SIX ............................................................................................................................. 27

SYSTEM IMPLEMENTATION AND TESTING ....................................................................... 27

6.1 Introduction ..................................................................................................................... 27

6.2 System Implementation .................................................................................................. 27

6.2.1 Database Implementation..................................................................................... 27

6.2.2 System functionality ............................................................................................ 29

6.3 Admin user page ............................................................................................................. 29

6.4 Doctor user page ............................................................................................................. 30

6.5 Patient user page ............................................................................................................. 30

6.5.1 Appointment page ................................................................................................ 32

6.5.2 Appointment form download ............................................................................... 33

ix
 6.6 System summary ............................................................................................................. 33

CHAPTER SEVEN....................................................................................................................... 34

CONCLUSION AND RECOMMENDATION ............................................................................ 34

7.1 Introduction ..................................................................................................................... 34

7.2 Conclusion ...................................................................................................................... 34

7.3 Recommendation ............................................................................................................ 34

7.4 REFERENCES ............................................................................................................... 35

APPENDIX A: PROJECT ACTIVITY ........................................................................................ 36

APPENDIX B: COST ESTIMATIONS ....................................................................................... 38

APPENDIX C: QUESTIONNAIRES ........................................................................................... 39

APPENDIX D: INTERVIEW ....................................................................................................... 41

APPENDIX E: DATABASE CODES .......................................................................................... 42

x
 LIST OF ABBREVIATION

DIT - Dar es salaam Institute of Technology

DFD - Data Flow Diagram

UML - Unified Modelling Language

HTML - Hyper Text Mark-up Language

PHP - Hypertext Pre-processor

SMS – Short Message Service

IVR – Interactive Voice Response

IDE - Integrate Development Environment

PSTN – Public Switch Telephone Network

ERD – Entity Relationship Diagram

SQL – Structured Query Language

CSS – Cascading Style Sheet

ICT – Information and Communication Technology

GUI – Graphical User Interface

DBMS – Database Management System

MySQL – My Structure Query Language

UML – Unified Modelling Language

PDF – Portable Document Format

DFD – Data flow diagram

xi
 LIST OF SYMBOLS

Web Server

Database Server

Internet

Computer

Data Flow

Entity

Condition / decision

Process

xii
 LIST OF TABLES

Table 1: Interview questions response .................................................................................. 15

Table 2: Questionnaire response ........................................................................................... 16

Table 3 Existing verses proposed system response .............................................................. 17

Table 4: Hardware requirements .......................................................................................... 19

Table 5: Software requirement: ........................................................................................... 19

Table 6 Admin table.............................................................................................................. 24

Table 7 Doctor table.............................................................................................................. 25

Table 8 Patient table.............................................................................................................. 25

Table 9 Doctor schedule table............................................................................................... 26

Table 10 Appointment table.................................................................................................. 26

Table 11 Activity Table senior project I ............................................................................... 36

Table 12: Activity Table senior project II............................................................................. 37

Table 13 Project cost estimation ........................................................................................... 38

Table 14: Questionnaire question ......................................................................................... 39

Table 15: Interview Questions .............................................................................................. 41

xiii
 LIST OF FIGURES

Figure 2. 1 Block diagram IVR system Seema (2012) ........................................................... 9

Figure 3. 1 Block diagram of proposed system. .................................................................. 11

Figure 4. 1 Questionnaire Feedback ..................................................................................... 16

Figure 5. 1 Proposed System Design Flow ........................................................................... 21

Figure 5. 2 General case diagram of the system ................................................................... 23

Figure 6. 1 MySQL server localhost (phpMyAdmin) .......................................................... 28

Figure 6. 2 Tables used in doctor appointment database ...................................................... 28

Figure 6. 3 Admin user page ................................................................................................. 29

Figure 6. 4 Doctor user page ................................................................................................. 30

Figure 6. 5 DIT zahanati home page (patient user page) ...................................................... 31

Figure 6. 6 New Patient (user) registration page .................................................................. 31

Figure 6. 7 Patient dashboard page after login ..................................................................... 32

Figure 6. 8 Patient appointment foam (appointment page)................................................... 32

Figure 6. 9 Downloaded appointment form for patient ........................................................ 33

xiv
 CHAPTER ONE

INTRODUCTION

1.1 Introduction

Globally, health care sector is the pivot and integral part of human lives. Thus, any error
committed in the clinical services might leads to defect or termination of life. Recently,
information and Communication has been used extensively to improve the various operations
and services in the field of the health care service. Patient appointment with the Doctor is one
of the clinical services that have been automated. Healthcare providers are motivated to reduce
operation cost while improving the quality of service. This has given rise to preventive
medicine in order to avoid disease, lessening the demand for emergency department and
hospital stays for sick people. The importance of Patient Scheduling cannot be underestimated
in the health care delivery landscape.

The current health care landscape desired efficiency and patient satisfaction for optimal
performance. The outpatient of most clinics / hospital in developing countries are faced with
plethora of issues. These include: overloading for doctors and nurses during clinic sessions,
long waiting time for patients, and peak workloads for counter personnel. The quality of health
care delivery has been threatened by overtime and peak work load. This project focuses on
developing a system to improve upon the efficiency and quality of delivering a web-based
appointment system to reduce waiting time.

The proposed project is a smart appointment booking system that provides patients or any user
an easy way of booking a doctor’s appointment online. This is a web-based application that
overcomes the issue of managing and booking appointments according to user’s choice or
demands. The task sometimes becomes very tedious for the compounder or doctor himself in
manually allotting appointments for the users as per their availability. Hence this project offers
an effective solution where users can make booking on Doctor’s slots available based on the
preferred date and time. The already booked space will be filled and time slot covered, next
patient will occupy next slot based on doctor consultation interval. This system also allows
users to choose doctor, date and time they desire to attend for medical reasons.

1
1.2 Background Information

Nowadays, there have been an increasing number of hospitals and medical complexes in many
places of the world. These facilities are meant to provide medical services to people suffering
from various diseases. One of the important components in providing medical services is
medical appointment reservation. The conventional way of doing this is patients need drop by
the hospital to make appointment. This means patients need to spend time, effort and money
to reach the hospital before the appointment can be made. This causes difficulty for old and
sick patients in getting medical treatment, particularly when their houses are far away from
the hospitals. Internet has been a new form of communication technology available in many
parts of the world. Such technology can be very useful to retrieve medical records of patients
stored in a database. The issues regarding the appointment booking can be improved if we can
utilise the internet to make appointment reservation. Such system is more efficient than the
traditional one where the patient no longer needs to go to the hospital physically which causes
difficulty especially to old and sick people besides also cost-, effort- and time-effective.
Patients can make reservation from anywhere and at any time by remotely assessed the internet
using mobile devices provided there is a network service available.

1.3 Problem Statement

If patient / ill wants to visit a doctor for check-up, he or she needs to visit the hospital and waits
until the doctor is available, which leads to time consuming. When the doctor cancels the
appointment for some emergency reasons then the patient is not able to know about the cancelation
of the appointment unless or until he or she visits the hospital.

Therefore, this study aims to represent a medical online reservation system based on a web
architecture in which expected to be a timely solution and more practical for health care
requirements. This study is to develop, design and implement a reservation system on the Internet
using the database system.

2
1.4 Objectives

1.4.1 Main objective

Developing online doctor’s appointment system for hospital to improve upon the efficiency and
quality of delivering service using a web-based appointment system to reduce waiting time and
Frustration for patients.

1.4.2 Specific objectives

The specific objectives of this project are;

i. To develop Appointment Management Module

ii. To develop Doctor Schedule Management Module

iii. To develop Patient Management Module

iv. To develop Doctor Management Module

v. To develop Login Module

vi. To develop Registration Module

vii. To create data base for the patients and doctors’ information

1.5 Significance of the Project

This aims of this project is therefore to develop an online reservation system for use at all
hospitals in Tanzania. The significant benefits of this system include:

i. Speed in appointment reservation for patients through internet.

ii. Reduce effort for both patients and doctors
iii. Increase the accuracy of appointment reservation.
iv. Reduce operation time.

v. Reduce operation cost.

vi. Clarity and precision to patient documents

3
1.6 Scope of the Project

The scope of the project will center on the design and implementation of Online Doctor’s
Appointment Reservation System for Hospital with outpatient, inpatient, access control, booking
generation and patient information storage.

1.7 Project Limitation

This system can be used only by people with access to the internet. Also, it can be used to people
who are registered to the specified hospital. Also, it is mostly applicable to hospital with few
numbers of patient such as Referral hospitals and for public it requires large database

1.8 Project Methods

For the accomplishment of the project, different methods will be used which are listed below

i. Literature review.

ii. Data collection.

iii. Data analysis.

iv. System design and building prototype.

v. System evaluation by users

vi. Refining prototype

vii. Complete system

viii. Report writing and submission.

ix. Chapter conclusion

1.8.1 Literature review

This section will involve the study of existing systems and critical evaluation of different research
reports done concerning online doctor’s appointment system suggested by different authors.

4
1.8.2 Data collection

This section will include systematic gathering of data from various sources. Data collection has
been categorized into two sections; primary and secondary data collection. This section will show
the need of the proposed system, the information of the existing system and essential parameters
for the proposed system to be successful.

For this project the following are methods that will be conducted for data collection

i. Interviews

ii. Questionnaire

1.8.3 Data analysis

This process will involve evaluation of data collected with aim of the obtaining useful information
that will help in drawing conclusion on what to be used in system design. This involves critical
analysis and evaluation of information obtained through interview and Questionnaire. We use
tables and Microsoft Excel to represent the analyzed data collected.

1.8.4 System design and building prototype

Design phase deals with creating physical models that satisfy all the requirements documented for
the system. In this project, the tools that is used to design is Microsoft Visio 2010 since it has
many functionalities and includes UML diagrams (use case, DFD Sequence Diagram, ER-
Diagram, etc.). In the Building the prototype the tools that are used are Adobe Dreamweaver and
phpMyAdmin IDE for the development of the database which handles better administration of
MySQL database. The development programing languages used is PHP and HTML.

1.8.5 System evaluation by users

The developed prototype is submitted to the customers for evaluation and collects the feedback
from them, then we analyze those new inputs from the customers, if the customer satisfies with
the prototype the project is move to the last phase, either, if the customer does not satisfy with the
prototype, the project is move to the Refining prototype phase in order to implement those changes.
We have got from the customer then we move again to the design and building prototype phase.

5
1.8.6 Refining prototype

In this phase, any changes made by users are taken into account for further customization.

1.8.7 Complete system

In this phase is the complete system is delivered to the user and the user testing is conducted which
includes user acceptance testing and the user trainee.

1.8.8 Writing report and submission

The report will finally be written to explain what have been done from the start of the project to
the end of it showing clearly what have been achieved.

1.8.9 Chapter conclusion

This chapter will describe the procedural steps which are undertaken to solve the existing system
problem. In order to develop a new system to solve the existing problems a lot of information
needs to be known so as to provide awareness on how previous works with its drawbacks.

1.9 Chapter Summary

This chapter describes the background of the problem, problem statement, objectives of the
proposed system with its respective objectives and significance. Also, methods that will helps to
attain the goal of this project such as literature review, data collection and analysis have been
composed in this chapter.

6
 CHAPTER TWO

LITERATURE REVIEW

2.0 Introduction

This section reviews previous works related to the conventional medical booking system and
current booking systems that made use the web pages on the Internet. This includes the algorithms
and data used by these systems.

Finally, this chapter provides a detailed description of the background of previous works relating
to rules of operational data associated with doctor’s patient appointment and the discussion of the
ideas related to previous project system. Also, it discusses the applications of booking
appointments and managing medical data for patients enrolled in the database of Hospital using
Internet applications. This includes the types, advantages and disadvantages.

2.1 Background Information

Online booking doctor’s appointment system are becoming common in some developing countries
that implemented to improve quality and efficiency of health services. Most of the system are not
advanced enough compare to developed counties which have given health sectors first priority
based on the advance of Information technology and use of internet in service delivering / health
care in the hospitals. The proposed project is a smart appointment booking system that provides
patients or any user an easy way of booking a doctor’s appointment online. This is a web-based
application that overcomes the issue of managing and booking appointments according to user’s
choice or demands.

2.2 Physical Booking System

This involves physical interaction of doctor and patient. Patient has to attend the hospital and seek
for the appointment either for the same day or schedule for a specific day. This consumes a lot of
time and has no guarantee since the doctor has no permanent database to store all the appointment
he agreed with the patient. This is one of the popular methods used in most of the hospitals. The

7
system sometimes led to congestion of patients in some of the day and also cannot alert the patient
if doctor has an emergence to attend, which results to time wasting

The arrival time of the first patient is assumed to be same as the doctor attending time. The
scheduled patient is assigned based on 3- main intervals and are also informed about their
appointed arrival times (su, 2003). If the scheduled patient does not appear on time, the next
available patient receives consultation immediately. The management operating philosophy of
services here is based on “first in, first seen” to limit patient waiting time. Therefore, patient can
walk in to see a physician, when patient shows up at the appointed time.

2.3 Mobile Booking

This is mobile system in which it involves sending SMS to hospital care centre and schedule the
appointment to the desired department and doctor. This is much applicable to the most recently
patient to a particular hospital, the nurse has to prepare the file of the appointed patient and send
to the previous doctor. The main concept of this system is contacting, screening and scheduling
appointment with the health care centre initially by an expert nurse or reception nurse for providing
doctor’s appointment for a particular day.

2.4 Interactive Voice Response (IVR)

Interactive Voice Response (IVR) is an automated telephony system that interacts with callers and
gathers information and provides the required information to the caller. IVR system accepts a
combination of voice or input from the keyboard and provides appropriate responses. User is
moved to different states according to his/her answer to the questions that being asked by the
system. Touch tone IVR systems are used where a menu is read for the user and he/she uses the
buttons on the phone keypad to interact with the system according to the read menu.

8
Figure 2.1 Block diagram IVR system Seema (2012)

Doctor is able to view his next scheduled appointments, also he can access and generate the
patient's diagnosis reports. After the generation of patient's diagnosis report, the server sends it on
the registered mobile number of the patient. For booking new appointment through IVR, patient
call the hospital then transferred to the server. Server automatically directs the call and guides the
caller. By calling on hospital phone, doctor can cancel his appointment.

9
 CHAPTER THREE

PROPOSED SYSTEM

3.0 Introduction

This chapter describes the function of each block in the proposed. It also explains the function of
the whole system and signal flow from one end to another and the significance of the proposed
system is also mentioned.

3.1 Proposed System

Online doctor’s Appointment Reservation System for Hospital is Web based platform that makes
the task of making an appointment to the doctor easy and reliable for the users. It provides patients
or any user an easy way of booking a doctor’s appointment online. This is a web-based application
that overcomes the issue of managing and booking appointments according to user’s choice or
demands. The task sometimes becomes very tedious for the compounder or doctor himself in
manually allotting appointments for the users as per their availability. Hence this project offers an
effective solution where users can view various booking slots available and select the preferred
date and doctor. This system also allows users to cancel their booking anytime.

Online Doctor Appointment System using PHP and MySQL is developed with point of manage
the list of data of doctors, patients, appointment bookings, doctor available schedule information
etc. Web based online doctor appointment application contains three modules: Doctor, Patient and
Admin

3.2 Proposed System Block Diagram

The proposed block diagram system as shown on figure below is developed to form an online
doctor’s appointment system for hospital to improve upon the efficiency and quality of delivering
health care service.

10
 Web Server Internet

SYSTEM

Patient Registration Module

Login Module

Patient Management Module

Doctor Management Module

Doctor Schedule Management

module

Appointment Management Module Computer/Phone

Database Server

Figure 3.1 Block diagram of proposed system.

3.3 Components of Proposed System

The following are the components which make up the proposed system: -

3.3.1 Computer

A computer is a machine or device that performs processes, calculations and operations based on
instructions provided by a software or hardware program. It is designed to execute applications
and provides a variety of solutions by combining integrated hardware and software components.
This computer will be used to provide interaction between the user and the system through internet.

3.3.2 Internet

The internet is a globally connected network system that uses TCP/IP to transmit data via various
types of media. The internet is a network of global exchanges – including private, public, business,

11
academic and government networks – connected by guided, wireless and fiber-optic technologies.
Internet will be used to provide connection between the computer and the system.

3.3.3 System (Online Doctor’s Appointment Reservation System)

Online doctor’s appointment reservation is the system that will be used to make booking for patient
at Hospital or clinic. The system contains the components that will be used to manage and process
user requests. The following are the parts of the system: -

3.3.5 Patient registration module

This is page where the patient is registering and fill all his / her details as required. It also creates
the details and account to get access to the hospital appointment system

3.3.6 Login module

This is page that grant permission to the patient or user to check doctors and their availability on
schedule.

3.3.7 Patient management module

This is page in which all the details such as name, age, gender and further descriptions of the
patient are recorded and stored. This can be access by admin, doctor or patient.

3.3.8 Doctor management module

This is page where the doctor is registered by admin and all his / her details are indicated and stored.
It also creates the details and account to get access to the hospital appointment system. Only admin
have access to add doctor.

3.3.9 Doctor schedule management module

This is page where by all the doctors schedule are shared so as the patients can see their availability.
Doctor is the one’s filled the time and date slot based on their monthly routing at hospital.

12
3.3.10 Appointment management module

These is the page that display all the time slot with vacancy or booked already by patient. This can
be accessed by all user.

3.3.11 Web server

This component will be used to manage and serve all web pages they will be requested from the
browser by the users of the system.

3.3.12 Database server

This component will be used to manage the database management system which will be used to
store all patient and system data like logs and stuff information.

3.4 Significance of the Proposed System

i. Speed in appointment reservation for patients through internet.

ii. Reduce effort, time and saving cost.

iii. Increase the accuracy of appointment reservation

3.5 Applications of the Proposed System

i. The project can be implemented in hospitals and clinics

ii. It can be utilized by companies and organizations (hospitals, schools, colleges) to

automate their parking system.

13
 CHAPTER FOUR

DATA COLLECTION

4.0 Introduction

This chapter gives insight on data collected from various sources; it includes information that is
useful for the project progress. Some data were collected from various sources including direct
data from the field by interviewing and questionnaires but also other from various sources
including books, journals, reports, and websites. These collected data will guide towards analysis
and designing and development of online doctor’s appointment reservation system.

4.1 Collected Data

Data collection is the process of gathering and measuring information on variables of interest, in
an established systematic fashion that enables one to answer stated research questions, test
hypotheses, and evaluate outcomes.

The following types of data collection performed in this project:

i. Primary data:

ii. Secondary data:

4.2 Primary Data Collection

In this method, data were collected from doctors, nurses and patients from various hospitals
through interview, questionnaires for Doctor’s appointment method used and the challenge,
significances and solutions.

4.2.1 Interview

A conversation between two people or more where questions are asked to a person to get the required
responses or answers. The interview is conducted through doctors, nurses and patients from hospitals
there were 20 interviewees. A summary of response is shown is table

14
Table 1: Interview questions response

S/N Interview Questions Answers

1 Which way used to make appointments in hospital • Physical appointment

• Mobile appointment

• Referral appointment

• Critical emergency
appointment

2 What is the average time for patient can wait for It depends on doctor attending and
his or her appointment patient disease

3 How do you inform the patient about the It depends on the availability of
appointment has been canceled contact information and for the ones
in hospital are informed through a
Nurse

4.2.2 Questionnaire

A set of questions that composed of both structured and unstructured questions was well designed
for obtaining data and was chosen to increase reliability of the response. The questionnaire was
used to 20 hospital users mostly patients to validate the existence of the problem which can be
solved with the new system.

The reason behind poor health care during the doctor’s appointment is poor utilization of time,
workforce from doctors and management. A response from the questionnaire is being summarized in
table

15
Table 2: Questionnaire response

S/N QUESTIONARE YES NO % Validating

existing of
problem

1 Are you happy with current appointment availability? 5 15 75%

2 Are you happy with the times of clinics? (Usually 8.30am 2 18 90%
to 11am, 2pm to 5pm)

3 Are you happy with the wait time for an appointment with 6 14 70%
your chosen doctor or nurse?

4 Are you aware that there is a doctor available daily who 7 13 65%
can deal with urgent problems over the phone?

5 Do you feel that this was an appropriate length of time to 1 19 95%

wait for the problem that you had?

6 Will online doctor’s appointment be useful 16 4 20%

The bar graph shows the response on the different question from the sample concerning the
doctor’s appointment system

QUESTIONARE FEEDBACK
18 19
20
15 16
14 13
15

10 7
5 6
4
5 2 1
0
QN1 QN2 QN3 QN4 QN5 QN6
YES NO

Figure 4.1 Questionnaire Feedback

16
The response on existing waiting time versus the new proposed system waiting time

Table 3 Existing verses proposed system response

S/N QUESTION RESPONSE AVERAGE

WAITING TIME

existing system Less a 2 to 5 6 to 10 2/3 days

day days days

1. How long did you have to wait for 3 14 3 70%

your last appointment?

proposed system in 30 1 to 2 3 to 5 30 min

min hours hours

2. How long would you 18 2 0 90%

have preferred to wait for your
appointment?

4.3 Secondary Data Collection

Secondary data collection involves the review of written document and online content such as
articles and journals.

4.3.1 Journals Reviewed

“Application of Smart Technologies for Mobile Patient Appointment System”, International

Journal of Advanced Trends in Computer Science and Engineering, august 2013.[3], Life is
becoming too busy to get medical appointments in person and to maintain a proper health care.
The main idea is to provide ease and comfort to patients while taking appointment from doctors
and it also resolves the problems that the patients have to face while making an appointment. The
android application Mr. Doc acts as a client whereas the database containing the doctor’s details,
patient’s details and appointment details is maintained by a website that acts as a server.

17
“Design and Development of Online Doctor Appointment System” [4], this paper focuses on
developing a system to improve upon the efficiency and quality of delivering a web-based
appointment system to reduce waiting time. In this paper, a patient appointment and scheduling
system is designed using Angular JS for the frontend, Ajax framework for handling client-server
request and Sqlite3 and MYSQL for the backend. Keywords: Patient, Appointment, Scheduling,
Angular JS.

4.3.2 Article Reviewed

‘Online reservation system for Al-kindi general hospital’ by Hasan bdair hashim, 2015.
[5]. in this study, I developed online reservation system at Al-Kindi General Hospital in Iraq. This
system can be remotely accessed by users from anywhere, anytime, using internet applications
from mobile devices for booking appointments. The development made use SQL server 2008
database and Microsoft visual studio 2008. The mobile devices include laptop computers and
mobile phones. Mobile application allows users to use the information technology without being
bound to a single location.

4.4 Design Requirement

These are data shown in tables below that will help design system for Doctor’s Appointment and
also help meeting the specific objectives intended.

18
Table 4: Hardware requirements

S/N HARDWARE Minimum System Requirement

01 Processor 2.4 GHz processor speed

02 Memory 2 GB RA
03 Disk Space 500 GB

Table 5: Software requirement:

S/N Software Minimum system Requirement

01 Operating System Window Server: window 10
02 Database Management System Microsoft SQL server: Adobe Dreamweaver and
phpMyAdmin IDE
03 Runtime Environment Visual Studio team system:
Microsoft Visio 2010
04 Programming language PHP and HTML.

19
 CHAPTER FIVE

SYSTEM ANALYSIS

5.0 Introduction

This chapter gives details about data analysis and system design of the proposed system. Data
analysis involves analytical and logical reasoning of data collected during data collection so as to
give a meaningful conclusion that will help accomplishing this project. The system design part
gives details on the system architecture and its operation flow.

5.1 System Analysis

The analysis is based on the data collected in the fourth chapter. Data analysis involves both
qualitative and quantitative analysis. Data analysis will follow the composed elements of the block
diagram of a proposed system as seen figure 3.1 in chapter 3.

5.2 Modules of Online Doctor Appointment Management System

Following are the main Modules of Online Doctor Appointment Management System.

i. Appointment Management Module

ii. Doctor Schedule Management Module

iii. Patient Management Module

iv. Doctor Management Module

v. Login Module

vi. Registration Module

20
5.3 Proposed System Design Flow

Figure 5.1 Proposed System Design Flow

5.4 Features of Online Doctor Appointment Management System

This system has three users. Admin, Doctor and Patients. So, all feature has been divided between
these three users.

5.4.1 Admin or Master Users

i. Admin can add Edit Delete and view Doctor Data.

ii. Admin can view all patient data.

21
 iii. Admin can Schedule any Doctor Availability data and manage that data (edit / delete).

iv. Admin can view all doctor appointment data and he or she can also process appointment.

v. Admin can login into this system and edit profile details.

vi. Admin can see Analytics data.

5.4.2 Doctor Users

i. Doctor can Add Edit Delete their availability data under this system.

ii. Doctor can view only his or her appointment data, they cannot see other doctor
appointment data.

iii. Doctor can see appointment patient’s details

iv. Doctor can write comment in patient appointment.

v. Doctor can edit profile details.

vi. Doctor can login into this system.

5.4.3 Patients Users

i. Patient can view Doctor Availability data on web page.

ii. Patient can register and login into this system.

iii. Patient can book appointment and they can also cancel appointment.

iv. Patient can download appointment in PDF format also.

v. Patient can change their profile details also.

22
5.4.4 Case Diagram for Admin, Doctor and Patient relation

Login / check into

website

patient registration

Change profile information

Patient View Doctor’s availability

and appointment data
Doctor

Make appointment

Download appointment data

View patient and

appointments information

Login into system

Add / delete Doctor

and Patient data
Admin

View all patient and

doctor data

Confirm
appointment

Logout into website /

system

Figure 5.2 General case diagram of the system

23
5.5 Database management system analysis

Database was designed using the MYSQL due to the level of functionalities database offers.
MYSQL is open-source relational database management system also offer high level of control
over the operations of stored data and structural communication between the backed language used
in the system (PHP). The phpMyAdmin has been used to handle the administration of a MySQL
since it is free software tool written in PHP.

5.5.1 Relational Data Model

Based on the three used module we require to create some of the relational data model using tables.
For our system we have created 5 tables in the doctor’s appointment database;

• Admin table: Store admin login details and hospital information

• Doctor table: Stores doctors login details and other profile details information

• Patient table: Stores patient login details and other profile details information

• Doctor schedule table: Stores doctor availability time details and dates

• Appointment table: Stores all the appointment details information

Table 6 Admin table

Name Data type Other attributes

admin_id int (11) Primary key Not Null
admin_email_address varchar (200) Not Null
admin_password varchar (100) Not Null
admin_name varchar (200) Not Null
hospital_name varchar (200) Not Null

hospital_address medium text Not Null

hospital_contact_no varchar (30) Not Null

hospital_logo varchar (200) Not Null

24
Table 7 Doctor table

Name Data type Other attributes

doctor_id (Primary key) Int (11) Primary key Not Null
doctor_email_address Varchar (200) Not Null
doctor_password Varchar (100) Not Null
doctor_name Varchar (100) Not Null
doctor_profile_image Varchar (100) Not Null
doctor_phone_no Varchar (30) Not Null
doctor_address Medium text Not Null
doctor_date_of_birth date Not Null
doctor_degree Varchar (200) Not Null
doctor_expert_in Varchar (100) Not Null
doctor_status Enum ('Active', 'Inactive') Not Null
doctor_added_on datetime Not Null

Table 8 Patient table

Name Data type Other attributes

patient_id Int (11) Primary key Not Null
patient_email_address Varchar (200) Not Null
patient_password Varchar (100) Not Null
patient_first_name Varchar (100) Not Null
patient_last_name Varchar (100) Not Null
patient_date_of_birth date Not Null
patient_gender Enum ('Male', 'Female', Not Null
'Other')
patient_address Medium text Not Null
patient_phone_no Varchar (30) Not Null
patient_maritial_status Varchar (30) Not Null

25
 patient_added_on datetime Not Null
patient_verification_code Varchar (100) Not Null
email_verify Enum ('No', 'Yes') Not Null

Table 9 Doctor schedule table

Name Data type Other attributes

doctor_schedule_id Int (11) Primary key Not Null
doctor_id Int (11) Not Null
doctor_schedule_date date Not Null
doctor_schedule_day Enum ('Sunday', 'Monday', 'Tuesday', Not Null
'Wednesday', 'Thursday', 'Friday', 'Friday')
doctor_schedule_start_time Varchar (20) Not Null

doctor_schedule_end_time Varchar (20) Not Null

average_consulting_time Int (5) Not Null

doctor_schedule_status Enum ('Active', 'Inactive') Not Null

Table 10 Appointment table

Name Data type Other attributes

appointment_id Int (11) Primary key Not Null
doctor_id Int (11) Not Null
patient_id Int (11) Not Null
doctor_schedule_id Int (11) Not Null
appointment_number Int (11) Not Null

reason_for_appointment Medium text Not Null

appointment_time time Not Null

status Varchar (30) Not Null

patient_come_into_hospital Enum ('No', 'Yes') Not Null

doctor_comment Medium text Not Null

26
 CHAPTER SIX

SYSTEM IMPLEMENTATION AND TESTING

6.1 Introduction

This chapter emphasizes the actual system implementation. The system was transformed from
theory requirement into a working system product. The purpose of system implementation was to
make sure, that the system serves our main target and meet all the specified objectives. It is giving
confidence on the new system for the users that it will work efficiently and effectively

6.2 System Implementation

Developing online doctor’s appointment system for hospital to improve upon the efficiency and
quality of delivering service has involved different process. It involves careful planning,
investigation of the current system and its constraints on implementation, design of methods to
achieve the changeover, an evaluation of change over methods. The implementation was dived
into two parts; database part and system functionality.

6.2.1 Database Implementation

New Database (Doctor Appointment) was created using MySQL language and database
management system (DBMS) interface – phpMyAdmin. phpMyAdmin act as user interface which
allow ability to input queries to a database without using the query language itself. It is web client
that runs on desktop computer.

The main interface is used together with the types and form of link with existing programs and
web pages to call database that was designed in the MySQL server.

27
 Figure 6.1 MySQL server localhost (phpMyAdmin)

Figure 6.2 Tables used in doctor appointment database

28
6.2.2 System functionality

This Doctor Booking management system has more functionality like patient login, doctor login
and complete system manage by admin. Our system / website consists of three major users with
various module. The language used in coding and integrating the web pages is PHP language.
Different pages were coded based on particular requirements and combined together to attain one
complete system and ensure all sub-pages function together as a complete function system.

Online Doctor Appointment Booking system, all of its features have been divided into three users
in system (Admin, Doctor and Patient).

6.3 Admin user page

Admin is the role with the highest level of access to your website. Admins can add content on all
pages and access all items in the Admin Toolbar. This is the page appears after a successful login
in frontend of software system. It contains a list of links that help the admin to navigate to different
areas of the system like managing patients, doctors, doctors schedule, appointment and dashboard
summary of the appointment in seven days.

Figure 6.3 Admin user page

29
6.4 Doctor user page

This is page which allow the doctor after successful login to access patients’ appointment details
and schedule his/her availability schedule. It gives full function to the doctor in managing the
dedicated patient appointments and his schedules.

Figure 6.4 Doctor user page

6.5 Patient user page

This is home page of the website in which the patient can view the hospital details and allocated
doctors in respective date and time. Only the authorized user with the right or correct user name
and password has a right to access the services of the making appointment.

30
 Figure 6.5 DIT zahanati home page (patient user page)

When the wrong user’s name and password are used, the system rejects access to the service. And
when the correct username and password are used and Login button pressed, the login page will
direct to dashboard page and allow patient to access the service.

A new user has to first register and do email verification to have valid access on the service on
making appointment. After he will login to the dashboard page to proceed with service required.

Figure 6.6 New Patient (user) registration page

31
6.5.1 Appointment page

This page allows the patient to make appointment to desired doctor and date after successful login
into a valid account.

Figure 6.7 Patient dashboard page after login

After accessing dashboard page of the patient, one can easily see all the doctor available, check
previous appointment if any, download previous and new appointment details in pdf. For selecting
new appointment, he needs to select doctor and indicate the reason for appointment.

Figure 6.8 Patient appointment foam (appointment page)

32
6.5.2 Appointment form download

This is downloaded form report by the patient in PDF format which consist of the appointment
details of respective patient and appointment number in particular which will act as identity when
visiting the hospital.

Figure 6.9 Downloaded appointment form for patient

6.6 System summary

According gathered information from the data analysis, it was realized that the current system has
challenges of doctor appointment making in both public and referral Hospitals. The researcher was
able to define requirements for the Doctor’s appointment management system and develop new
system on the data collected and analysed.
In developing the new system, data flow and case diagram were useful to describe the flow of the
information in the new system and entity relation diagram was used to show the relationships
between the entities and logical connections was made. PHP Dreamweaver was used to design the
graphical user interface, while PhpMyAdmin was useful in developing the database. Testing was
carried out on each module as each module been implemented to detect any defect and make
corrections to ensure that each module is compatible and the system was integrated and tested
which conform to the user requirements specifications.
33
 CHAPTER SEVEN

CONCLUSION AND RECOMMENDATION

7.1 Introduction

This chapter gives out overall summary of the proposed system and conclusion made concern the
project proposed.

7.2 Conclusion

This online Doctor appointment system have the special capacity to increase efficiency and quality
of delivering service and fill up appointment gaps from the number of people who go to Hospital
or clinic every fixed interval. This system has only 3 simple steps for find a Doctor, Book Doctor
Appointment and consult with the Doctor. This system is mobile responsive, so patients can book
appointments from any place by using any internet device.

The appointment system will pave the way for easy and quick access to better healthcare. It can
be implemented in probably in referral Hospital only, for domestic / public hospital which
normally receive large number of patients in a time will be much complex to be used.

7.3 Recommendation

It is with a vital concern that my recommendation goes directly to all hospital with such challenges
and student / researchers. They can evaluate and improve the system based on their essential
requirements. By using the proposed system “online doctor’s appointment system for hospital”
will help to improve upon the efficiency and quality of delivering service for the hospitals or clinic.

System gives chance for patient to view and selected doctor based on their professional and date
available. Also probably used in less populated hospital and referral ones and implementation
ended in local hosting on only. Proposed modification; doctor’s time slot display (start menu to
select options available), Patient appointment cancellation or changing time/day/doctor and online
webhosting so as to be accessed over the internet by each user.

34
7.4 REFERENCES

[1] Arthur Hylton III and Suresh Sankaran arayanan “Application of Intelligent Agents in Hospital
Appointment Scheduling System”, International Journal of Computer Theory and Engineering,
Vol. 4, August 2012, pp. 625-630.

[2] Deepti Ameta, Kalpana Mudaliar and Palak Patel “Medication Reminder And Healthcare – An
Android Application”, International Journal of Managing Public Sector Information and
Communication Technologies (IJMPICT) Vol. 6, June 2015, pp. 39-48.

[3] Yeo Symey, Suresh Sankaran arayanan, Siti Nurafifah binti Sait “Application of Smart
Technologies for Mobile Patient Appointment System”, International Journal of Advanced Trends
in Computer Science and Engineering, august 2013.

[4] “Design and Development of Online Doctor Appointment System”

https://www.academia.edu/26066176/Design_and_Development_of_Online_Doctor_Appointme
nt_System, [Online] retrieved on December 2021.

[5] ‘Online reservation system for al-kindi general hospital’ by Hasan Bdair Hashim, 2015.

[6] International Advanced Research Journal in Science, Engineering and Technology, ISO
3297:2007 Certified, Vol. 4, Issue 12, December 2017

[7] “Doctor appointment booking-system” Doctor Appointment Booking Project

(nevonprojects.com) [Online] retrieved on 13 January 2022

35
 APPENDIX A: PROJECT ACTIVITY

The following is the project duration activity conducted in senior project 1 to complete the project.

A. – Selection of project title (Week 1-2)

B. – Title defending and re-defending. (Week 3-4)

C. – Re-writing the proposal according to the approved title (week 5)

D. – Data collection (Week 5-8).
E. – Literature review (Week 1-12)

F. – Data analysis (Week 9-10)

G. - Report writing (Week 11-13)

Table 11 Activity Table senior project I

Activity Duration of the senior project I in weeks

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

The following is the project duration activity conducted in senior project II to complete the project.

A. Data Analysis (Week 1-4)

B. System design and building prototype (Week 4-8)

36
 C. System evaluation by users (Week 4-8)

D. Refining prototype (Week 7-16)

E. Consultation and completing the system (Week 1-16)

F. Report writing (Week 1-13)

G. Report assessment and submission (Week 14-16)

Table 12: Activity Table senior project II

Activity Duration of the senior project II in weeks

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

37
 APPENDIX B: COST ESTIMATIONS

The cost estimation for this project to be accomplished is represented as shown on table below:

Table 13 Project cost estimation

ITEM PRICE TOTAL COST

Communication and internet 100,000/= 100,000/=

Questionnaires Printing 500 @ interviewee 10,000/=

Printing project book 50,000 @ Semester 100,000/=

Transport 25,000 @ Semester 50,000/=

Contingency 40,000/= 40,000/=

TOTAL COST 300,000/=

38
 APPENDIX C: QUESTIONNAIRES

DEPARTMENT OF ELECTRONICS AND TELECOMMUNICATION

ENGINEERING.

BACHELOR OF ENGINEERING

NTA LEVEL 8

Dear respondent; I am RODRICK SAIMON LULU, a bachelor student at Dar Es Salaam

Institute of Technology (DIT) undertaking a final year project on the Online Doctor’s
Appointment Reservation System for Hospital. I kindly request you to assist by filling the
required information as honestly as possible.

This research is carried out in partial fulfilment of the award of Bachelor of electronics and
telecommunication engineering. This information will be kept confidential and will be used only
for my project work. Thank you in advance.

Table 14: Questionnaire question

S/N QUESTIONARE YES NO % Validating

existing of problem

1 Are you happy with current appointment

availability?

2 Are you happy with the times of clinics? (Usually

8.30am to 11am, 2pm to 5pm)

3 Are you happy with the wait time for an

appointment with your chosen doctor or nurse?

39
4 Are you aware that there is a doctor available daily
who can deal with urgent problems over the phone?

5 Do you feel that this was an appropriate length of

time to wait for the problem that you had?

6 Will online doctor’s appointment be useful

S/N QUESTION RESPONSE AVERAGE

WAITING TIME

existing system Less a 2 to 5 6 to 10 2/3 days

day days days

1. How long did you have to wait for

your last appointment?

proposed system in 30 1 to 2 3 to 5 30 min

min hours hours

2. How long would you

have preferred to wait for your
appointment?

40
 APPENDIX D: INTERVIEW

DEPARTMENT OF ELECTRONICS AND TELECOMMUNICATION

ENGINEERING.

BACHELOR OF ENGINEERING

NTA LEVEL 8

Dear respondent; I am RODRICK SAIMON LULU, a bachelor student at Dar Es Salaam

Institute of Technology (DIT) undertaking a final year project on the Online Doctor’s
Appointment Reservation System for Hospital. I kindly request you to assist by filling the
required information as honestly as possible.

This research is carried out in partial fulfilment of the award of Bachelor of electronics and
telecommunication engineering. This information will be kept confidential and will be used only
for my project work. Thank you in advance.

Table 15: Interview Questions

S/N Interview Questions Answers

1 Which way used to make appointments in

hospital

2 What is the average time for patient can wait

for his or her appointment

3 How do you inform the patient about the

appointment has been canceled

41
 APPENDIX E: DATABASE CODES

The MySQL codes used to create our database (Doctor Appointment);

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";

-- Database: `doctor_appointment`
--

-- Table structure for table `admin_table`

--

CREATE TABLE `admin_table` (

`admin_id` int(11) NOT NULL,
`admin_email_address` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`admin_password` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`admin_name` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`hospital_name` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`hospital_address` mediumtext COLLATE utf8_unicode_ci NOT NULL,
`hospital_contact_no` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`hospital_logo` varchar(200) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `admin_table`
--
INSERT INTO `admin_table` (`admin_id`, `admin_email_address`, `admin_password`,
`admin_name`, `hospital_name`, `hospital_address`,
`hospital_contact_no`, `hospital_logo`) VALUES
(1, 'johnsmith@gmail.com', 'password', 'John smith', 'Mount Hospital', '115, Last
Lane, NYC', '741287410', '../images/15001.png');

--
-- Table structure for table `appointment_table`
--

CREATE TABLE `appointment_table` (

`appointment_id` int(11) NOT NULL,
`doctor_id` int(11) NOT NULL,
`patient_id` int(11) NOT NULL,
`doctor_schedule_id` int(11) NOT NULL,

42
 `appointment_number` int(11) NOT NULL,
`reason_for_appointment` mediumtext COLLATE utf8_unicode_ci NOT NULL,
`appointment_time` time NOT NULL,
`status` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`patient_come_into_hospital` enum('No','Yes') COLLATE utf8_unicode_ci NOT NULL,
`doctor_comment` mediumtext COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `appointment_table`
--

INSERT INTO `appointment_table` (`appointment_id`, `doctor_id`, `patient_id`,

`doctor_schedule_id`, `appointment_number`,
`reason_for_appointment`, `appointment_time`, `status`,
`patient_come_into_hospital`, `doctor_comment`) VALUES
(3, 1, 3, 2, 1000, 'Pain in Stomach', '09:00:00', 'Cancel', 'No', ''),
(5, 1, 4, 2, 1002, 'For Delivery', '09:30:00', 'Completed', 'Yes', 'She gave
birth to boy baby.'),
(6, 5, 3, 7, 1003, 'Fever and cold.', '18:00:00', 'In Process', 'Yes', ''),

--
-- Table structure for table `doctor_schedule_table`
--

CREATE TABLE `doctor_schedule_table` (

`doctor_schedule_id` int(11) NOT NULL,
`doctor_id` int(11) NOT NULL,
`doctor_schedule_date` date NOT NULL,
`doctor_schedule_day`
enum('Sunday','Monday','Tuesday','Wednesday','Thursday','Friday','Saturday')
COLLATE utf8_unicode_ci NOT NULL,
`doctor_schedule_start_time` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`doctor_schedule_end_time` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`average_consulting_time` int(5) NOT NULL,
`doctor_schedule_status` enum('Active','Inactive') COLLATE utf8_unicode_ci NOT
NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `doctor_schedule_table`
--

INSERT INTO `doctor_schedule_table` (`doctor_schedule_id`, `doctor_id`,

`doctor_schedule_date`,

43
`doctor_schedule_day`, `doctor_schedule_start_time`, `doctor_schedule_end_time`,
`average_consulting_time`, `doctor_schedule_status`) VALUES
(2, 1, '2021-02-19', 'Friday', '09:00', '14:00', 15, 'Active'),
(3, 2, '2021-02-19', 'Friday', '09:00', '12:00', 15, 'Active'),
(7, 5, '2021-02-22', 'Monday', '18:00', '20:00', 10, 'Active'),
(8, 2, '2021-02-24', 'Wednesday', '09:30', '12:30', 10, 'Active'),
(9, 5, '2021-02-24', 'Wednesday', '11:00', '15:00', 10, 'Active'),

--
-- Table structure for table `doctor_table`
--

CREATE TABLE `doctor_table` (

`doctor_id` int(11) NOT NULL,
`doctor_email_address` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`doctor_password` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`doctor_name` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`doctor_profile_image` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`doctor_phone_no` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`doctor_address` mediumtext COLLATE utf8_unicode_ci NOT NULL,
`doctor_date_of_birth` date NOT NULL,
`doctor_degree` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`doctor_expert_in` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`doctor_status` enum('Active','Inactive') COLLATE utf8_unicode_ci NOT NULL,
`doctor_added_on` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `doctor_table`
--

INSERT INTO `doctor_table` (`doctor_id`, `doctor_email_address`,

`doctor_password`, `doctor_name`, `doctor_profile_image`,
`doctor_phone_no`, `doctor_address`, `doctor_date_of_birth`, `doctor_degree`,
`doctor_expert_in`, `doctor_status`, `doctor_added_on`) VALUES
(1, 'peterparker@gmail.com', 'password', 'Dr. Peter Parker',
'../images/10872.jpg', '7539518520',
'102, Sky View, NYC', '1985-10-29', 'MBBS MS', 'Sergen', 'Active', '2021-02-15
17:04:59'),
(2, 'adambrodly@gmail.com', 'password', 'Dr. Adam Broudly',
'../images/21336.jpg', '753852963',
'105, Fort, NYC', '1982-08-10', 'MBBS MD(Cardiac)', 'Cardiologist', 'Active',
'2021-02-18 15:00:32'),
(3, 'sophia.parker@gmail.com', 'password', 'Dr. Sophia Parker',
'../images/13838.jpg', '7417417410',

44
'50, Best street CA', '1989-04-03', 'MBBS', 'Gynacologist', 'Active', '2021-02-18
15:05:02'),
--
-- Table structure for table `patient_table`
--

CREATE TABLE `patient_table` (

`patient_id` int(11) NOT NULL,
`patient_email_address` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
`patient_password` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`patient_first_name` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`patient_last_name` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`patient_date_of_birth` date NOT NULL,
`patient_gender` enum('Male','Female','Other') COLLATE utf8_unicode_ci NOT
NULL,
`patient_address` mediumtext COLLATE utf8_unicode_ci NOT NULL,
`patient_phone_no` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`patient_maritial_status` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`patient_added_on` datetime NOT NULL,
`patient_verification_code` varchar(100) COLLATE utf8_unicode_ci NOT NULL,
`email_verify` enum('No','Yes') COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `patient_table`
--

INSERT INTO `patient_table` (`patient_id`, `patient_email_address`,

`patient_password`, `patient_first_name`,
`patient_last_name`, `patient_date_of_birth`, `patient_gender`,
`patient_address`, `patient_phone_no`,
`patient_maritial_status`, `patient_added_on`, `patient_verification_code`,
`email_verify`) VALUES
(3, 'jacobmartin@gmail.com', 'password', 'Jacob', 'Martin', '2021-02-26', 'Male',
'Green view, 1025, NYC',
'85745635210', 'Single', '2021-02-18 16:34:55',
'b1f3f8409f7687072adb1f1b7c22d4b0', 'Yes'),
(4, 'oliviabaker@gmail.com', 'password', 'Olivia', 'Baker', '2001-04-05',
'Female', 'Diamond street, 115, NYC', '7539518520', 'Married',
'2021-02-19 18:28:23', '8902e16ef62a556a8e271c9930068fea', 'Yes'),
--
-- Indexes for dumped tables
--
-- Indexes for table `admin_table`
--

45
ALTER TABLE `admin_table`
ADD PRIMARY KEY (`admin_id`);
--
-- Indexes for table `appointment_table`
--
ALTER TABLE `appointment_table`
ADD PRIMARY KEY (`appointment_id`);
--
-- Indexes for table `doctor_schedule_table`
--
ALTER TABLE `doctor_schedule_table`
ADD PRIMARY KEY (`doctor_schedule_id`);
--
-- Indexes for table `doctor_table`
--
ALTER TABLE `doctor_table`
ADD PRIMARY KEY (`doctor_id`);
--
-- Indexes for table `patient_table`
--
ALTER TABLE `patient_table`
ADD PRIMARY KEY (`patient_id`);
--
-- AUTO_INCREMENT for dumped tables
--
-- AUTO_INCREMENT for table `admin_table`
--
ALTER TABLE `admin_table`
MODIFY `admin_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `appointment_table`
--
ALTER TABLE `appointment_table`
MODIFY `appointment_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8;
--
-- AUTO_INCREMENT for table `doctor_schedule_table`
--
ALTER TABLE `doctor_schedule_table`
MODIFY `doctor_schedule_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=15;
--
-- AUTO_INCREMENT for table `doctor_table`
--
ALTER TABLE `doctor_table`
MODIFY `doctor_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7;

46
--
-- AUTO_INCREMENT for table `patient_table`
--
ALTER TABLE `patient_table`
MODIFY `patient_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
COMMIT;

47