DOCTOR - PATIENT

APPOINTMENT SYSTEM

(WEB BASED SYSTEM )

I
 CHAPTER ONE

1. INTRODUCTION AND PROBLEM DESCRIPTION

1.1 BACKGROUND

In the real world the patient is facing numbers of significant problems during the OPD related to
appointment, registration, searching OPD location and waiting for doctor checkup. (Nidhi Malik,
O. K. Belwal (2016).

Due to increasing health care expenditures and an ever-rising demand for health care services,
hospitals face a continuous challenge to increase the efficiency of their operations. Countless
attempts have therefore been made in recent years to develop new planning or patient admission
techniques. Patients who are scheduled using a single-resource algorithm may for example not be
available as they are still queuing for another resource type. Also, if two or more departments use
single-resource scheduling algorithms, patients might have to wait a substantial amount of time
between two consecutive appointments on two different resources. In the case of inpatients, this
behavior results in an increased length of stay (LOS), while outpatients may need to visit the
hospital multiple times for a set of procedures that could have been performed in a single day. It
is clear that for both patient groups these disadvantages will result in elevated health care costs,
while at the same time patient satisfaction will be low.

In Our country there are many problems that affect people due to an immediate health problem
which require to go far to check for Doctors or to get an advice from a Doctor regarding the
problem that patients have and also to make an appointment. And when we have the system all
of the patients which have the problem regarding health from different area can go to the system
and make appointment with doctor of their choice. Also in today patient can go far for doctor
appointment due to low specialist in many Tanzania hospitals.

This process of making appointments being initiated by the patients and who have to visit the
Hospital for the process. Also amongst the services offered currently for many patients to go far
for the services. This is one of the important system in many hospitals since it handles all the
appointment for years now, but the problem with the current system is the usability of the system
and awareness also cost for many patients.

Also when Patients Go to the hospital for making an appointment with doctor, and the doctor
give his/her the answer on what time the patient can get all of the services, but the problem come
when doctor during the day of appointment get the emergency and once patient arrive the doctor
tell his/her that sorry for today we can’t meet please came after three days, so this became the

1
problem so we must have the system which doctor can cancel the appointment also schedule the
appointment so patients can get to know the feedback from the doctor accordingly.

Most of the doctors use files to check which patients make appointment and delay to provide the
feedback, but when doctor use the system can provide timely feedback to the patients and the
patients meet doctor accordingly. Since we move from paper based format and now we use the
technology for creating solutions in the society and one of the problem is the system of managing
patient’s appointment in many hospitals in the country, and during that we must have the system
which can control all the appointment so the doctors get to know the time accordingly and
schedule the patient’s appointments so the system create and awareness and the patients serve
time and cost during making appointments process.

1.2 PROBLEM STATEMENT

Patient Appointment to doctor currently done under the hospital in which patients travel from
one place to the hospital to check with doctor and doctor provide the date and time for the
appointment. The current system used to process patient details which done with doctor at the
hospital which is manual based system, which is too cost full and wastage of time as well due to
congestion of patients which came from far away to make the appointment. Patients are required
to travel from their home to the Hospital to make the appointment with the Doctor of their
interest and know what time the appointment will be approved.

The existence of this problem is of years and affects so much Patients compared to Doctors. The
developed system provides a solution to the existing problem. With DPAS, patients are able to
view their appointment, check for the available doctors and make the appointment of the doctor
of their interest, But at the end, this system come to reduce several problems such as cost,
wastage of time and at last it increases efficiency.

1.3 PROJECT OBJECTIVES

The main objective this project is to develop the Web based System with a sense of reaching
many patients and to link with doctors which may reduce some of the difficulties which
happening in their daily life. And through the platform user can use their devices to access the
System in any Operating System. Which will help the Patients view their Appointment easily
with an interface that is user friendly and responsive compared with the current system being
used which is Paper Based.

2
Therefore, the following is Specific Objectives of the System

• To establish an efficient way to join Doctors and users together.

• To help user to get service and Quick advice.
• To provide anytime, anywhere service for users.
• To get help from Doctors through the system and to find out how quick she/he
will do.
• To manage all patients related information.
• To provide emergency information in critical situation.

1.4 SIGNIFICANCE AND SCOPE

1.4.1 Significance

The implementation of this system is for better user experience. This system is very easy to
access. Also for establish real time communication, using modern and updated technology. So,
user can see the update without reload or refresh. This system will compatible with user device
such as PC, laptop, tab & smart phone. So user can easily access the system anytime anywhere.
This system is very simple & user friendly so, any user can use this system easily.

1.4.2 Scope
The scope of this Project is to enable the Doctor and Patients to get information through the
system, also Doctor have the huge area of collecting patient’s information.

1.4.2.1 Assumptions

In assumptions of the system is that, an patient who make appointment must comply with the
following criteria’s:
- Must Register to use the System.
- Must have access to the all of the possible appointment through the system.
- Must have a reason of making an appointment.

CHAPTER TWO

3
 2. LITERATURE REVIEW

2.1. TOPIC REVIEW

Literature review is a very important element that of any project since it contains the relevant
knowledge and information to help in project implementation and system development. As the
patient’s population of Many Areas grows over time, the number of patients who makes an
appointment as well. Also as technology gets to be updated daily, people using websites decrease
and so the use of websites decreases while the use of mobile application increases.
A web is made up of page that is commonly known as web page or web site, and a web site is a
computer program that runs a web server that provides access to a group of related web pages
(Alex, 2000). A system is a set of independent components working together to achieve a
common objective. Therefore, a web based system is a system that is accessible over the internet
by a user in order to achieve a particular task for a given purpose. The Internet is a system that is
use to connect computers and computer networks. It helps to link millions of computer networks
all over the world and it allows the users to get information stored on other computers from a
long distance (James, 1999). According to Chua (2010) the public demand for better healthcare
system and the alarming number of missed appointments have forced the healthcare sector to
recognize how they deliver care services. With the advance of IT technology today and seen
healthcare system as a critical system, appointment system lies at the intersection of delivering
efficient, dependable and timely access to health services. The conventional way of appointment
booking is via fax, phone or email. But with the growing internet penetration, healthcare industry
is moving towards the use of an online appointment booking system. A web-based appointment
system is used in Taiwan; everyone is required to enroll in the national health insurance program.
When one needs health service, he shows his health insurance card to doctors in a hospital to
start with. There are several ways of making an appointment. A person can either go to the
hospital directly for consultation day by day or make an appointment from home through phone
call or email if his condition is not emergent (Gruca, 2004). The Internet provides a wide range
of technologies that enable hospitals to communicate with their patients. Recently, as the
prevalence of Internet increasing, many hospitals initiated the website appointment system.
Electronic patient-provider communication promises to improve efficiency and effectiveness of
clinical care (Wakefield, 2004)

As technology becomes part of human life, there are so many applications that have been
developed to make one’s life easier. Nowadays many systems, applications (desktop and mobile)
to make and easy way for the users to do their work for example the E-Learning System where
students and lecturers meets electronically. The Patient Appointment process is a service
function for patient, that provides a mechanism for reasonable review of the appointment which
doctor deals with. (Hospital, 2009).
Irin Sherly. S, Mahalakshmi. A, Menaka. D, Sujatha. R (2016): “Online Appointment
Reservation and Scheduling for Healthcare- A Detailed Study”, International Journal of

4
Innovative Research in Computer and Communication Engineering, Volume 4, Issue 2, ISSN
2320-9798. This research represents online Appointment reservation and scheduling systems in
healthcare are used to maintain and manage the access to the hospitals. This system allows
individuals to securely and safely make their appointment reservations online.

Pradipti Verma, Dr. Risha Saxena(2015): “An Effective Time Motion Study (Tms) On Opd
Patients Of A Tertiary Care Hospital In September 2015 In Goa”, International Journal Of
Research Science & Management, Volume 2, No. 12, ISSN: 2349- 5197. The paper is based
upon the monitoring the waiting time of patient visiting the Outpatient department of a hospital
using the concept of Time and Motion study.
Aswar Nandkeshav R, Kale Kalpana M, Rewatkar Mangesh P, Jain Akanksha, Barure Balaji S
(2014): “Patients’ Waiting Time and Their Satisfaction of Health Care Services Provided at
Outpatient Department of Government Medical College, Nanded (Maharashtra, India)”,
International Journal of Health Sciences and Research, Volume 4, Issue 4, ISSN: 2249-9571.
This describes the improvement of patient’s satisfaction towards health care services by reducing
their waiting time, attending the patient in time and sympathetic approach will create a positive
image of hospital in the mind of people and also will help hospital image building in the
community.
According to Dexter (1999), managing patient appointment system is a computer application
used to manage and reduce the patient waiting time in the health care center. Some health care
centers do not use any appointment system. So it has a longer average patients’ waiting time than
the health care center that adopts the patients’ appointment system. While patients can wait for
more than one hour to be attended to by a physician in a health care center, they also can feel that
they are being disregarded and treated unfairly. So when patients are given the time of
appointment in a health care centre, they can evaluate the quality of service in the centre (Dexter,
1999). Hence, developing patients’ appointment process for health care centres necessitates the
use of a sophisticated queuing model that captures much of the real system’s features (saving
time, reducing idle time, etc). Therefore, the appointment schedule represents the real situation in
the health care centre faced by patient appointment schedulers (Rohleder, 2002). On the other
hand, the standard practice for scheduling and processing patient appointments are based on the
nature of treatments of the patients and that better approaches more sensitive to patient needs are
desirable (Klassen, 2002).
Waiting time simply means a period of time which one must wait in order for a specific action to
occur, after that action is requested or mandated (Fernandes et al., 1994). Patients’ waiting time
has been defined as “the length of time from when the patient entered the outpatient clinic to the
time the patient actually received his or her prescription” (Jamaiah, 2003). It is defined as the
total time from registration until consultation with a doctor. There were two waiting times, the
first is time taken to see a physician and the second is time to obtain medicine (Suriani, 2003).
This paper deals with the waiting time to see physicians. Long waiting times are a serious
problem for patients using urban health centres in developing countries (Bachmann, 1998). A
block appointment system was introduced and evaluated in a large South African health centre.

5
Waiting times of all patients were measured over one-week period before and after the
implementation of appointments. Focus groups and individual interviews were conducted with
staff and patients. After introducing appointments, patients with acute and chronic illnesses and
having appointments had significantly shorter waits time than similar patients without
appointments (Mahomed, 1998). Appointments had no benefits for patients not seeing doctors or
collecting repeat medication. There was, however, an overall increase in patients' waiting times
after introducing the system, mainly due to one typical day in the follow-up study. Focus groups
and interviews revealed that staff were skeptical at baseline but at follow-up were positive about
the system. Patients were enthusiastic about the appointment system at all stages. The study
shows that block appointments can reduce patients’ waiting times for acute patients, but may not
be suitable for all patients. Staff and patients had different views, which converged with
experience of the new system (Mahomed, 1998).

The technologies involved in the development and deployment of the System are: -
a) Hyper Text Markup Language(HTML): - Is a markup language used in
structuring and presenting contents in a web. It is a web technology which can
access (store data) Local Storage directly compared to other versions of HTML

b) Cascading Style sheet (CSS): - Cascading Styling Sheet, it is used to style up the
application (front-end view). It is easily integrated with HTML5

c) Materialize: - Material Design is a design language that combines the classic

principles of successful design along with innovation and technology. Google's
goal is to develop a system of design that allows for a unified user experience
across all their products on any platform.

d) Hypertext Preprocessor (PHP): - A server side scripting language that is used as

a backend interface of the mobile application, though its communication with the
interface is parsed through Json. It is used through the communication to the
database of the application.

e) MYSQL database:- This is the database of the application, consists of the tables
that holds whole data of the system. MySQL is lightweight and can easily
integrate with PHP.

f) JavaScript: - This is an object-oriented computer programming language

commonly used to create interactive effects within web browser.

6
 2.2. DOMAIN REVIEW

Currently many Hospitals are still using the manual system for processing patient appointment
and all appointment is done by the respected doctor.
Due to this, there are problems in maintaining the patient records and appointments and hence
the need of upgrading to the use of Computer Based Information System (CBIS). According to
Irin Sherly. S, Mahalakshmi. A, Menaka. D, Sujatha. R (2016), The researcher describes all
reasons of delay in patient treatment.
Also emphasize that the use of the system allows individuals to securely and safely make their
appointment reservations and with the advance of IT technology today and seen healthcare
system as a critical system, appointment system lies at the intersection of delivering efficient,
dependable and timely access to health services.

2.2.1. Review of existing Hospital appointment systems.

The following is a case study of an appointment system specifically located in

Dares-Salaam Tanzania. It includes part of the view, its strength and weakness.

REGENCY HOSPITAL APPOINTMENT SYSTEM

Figure 6. Regency Hospital System

Regency hospital, allows different people to make appointment to their hospital. The
appointment system is basically located or can do on the hospitals ‘website.

7
 Strength
• The system allows for multiple activities. It is not basic and limited to an
appointment function. Different people can also obtain hospitals’
information just by visiting their website and not necessarily make
appointment

Weakness
• Patient can not directly communicate with the doctor. The system allows a
patient to make an appointment to the hospital which will plan a visit for you
and a doctor.
• The website is not responsive
• Limited to one hospital
The gap between Regency hospital appointed system and Doctor patient appointment system is
that, in the Doctor-patient system, a patient directly communicates with the doctor. The system is
made available to many hospitals as a patient can make appointed to the hospital that are
included or integrated with the system.

2.3. PROBLEM CONCLUSION AND CONCEPTUAL FRAMEWORK

The explained literature review has helped to improve the analysis on how the Doctor-Patient
appointment system (WEB BASED) is going to be developed from the beginning stage of
research, data collection and design. It also helped to widen mind with many aspects such as
Web development by which as another developer could think developing something as a solution
to the society, And the system can enable all patients to make the appointment in the way which
doctor provide the feedback easily at a really time and patients be able to attend at a certain
hospital in the special area of treatment.

CHAPTER THREE

3. REQUIREMENT ELICITATION AND SYSTEM ANALYSIS

3.1. INTRODUCTION TO REQUIREMENT ELICITATION

Several system developments must meet the intended requirements, where by the requirement
elicitation plays the major role in system development. It is recognized as the first stage many
system development/design engineering processes. Requirement elicitation combines the
elements of problem solving, elaboration, negotiation and specification. In order to encourage a
collaborative, team-oriented approach to requirements gathering, stakeholders work together to

8
identify the problem, propose elements of the solution, negotiate different approaches and
specify a preliminary set of solution requirements (Pressman, 2005).

In meeting the objectives of the system, it has to carry a number of functionalities both functional
and non-functional requirements. This part is going to elaborate the analysis of the current
platforms, the investigation of the performance and how the elicitation was done in order to fill
the gap with the implementation of the new application. The success of the requirements
elicitation activity leads to the development of correct application which involves collecting of
the information from users of the system. The information collected enhanced the designer to
design the or come with the product that suit the user needs. At this stage, the system developer
and system designer work together in order to: -

• Find out more about the problem to be solved

• To describe the functionality of the system
• Performance of the system
• Hardware constraints
• System User Experience
• System user Requirement
• System Usage
• System Testing

Figure 1: Requirement elicitation process - Source: (Gabry, 2016).

9
System analysis is a process of figuring out the basic element of the project and decides to
combine them in the best way to solve problem. It is the second of five phases in the System
Development Life Cycle (SDLC) with the purpose of building logical model of the application.
In this chapter, there will be explanation about identification of users and use cases, specification
of the system functional and non-functional requirements. System requirement is a characteristic
or feature that must be included in an information system to satisfy business requirements and be
acceptable to users (Shelly & Rosenblatt, 2012). It defines what the system should do and
functions.

3.2. CLASSIFICATION OF SYSTEM REQUIREMENTS

Requirement is a careful assessment of the needs that a system is to fulfil, during requirement
classification number of question must be considered such as why the system is needed based on
the current system, which maybe the internal operations, what system feature will serve to satisfy
the user needs and also must say how the system is to be constructed. Basically, system
requirement is classified into functional requirements and non-functional requirements.
3.2.1. Functional Requirements

In system design and development, functional requirements define the functions of the
system or its components. This may be calculations, data manipulation and processing and
specific functionalities that a system has to accomplish to solve a particular problem.

In Doctor Patient Appointment system, the following are the Functional Requirements.

• Accept of submissions in form of raw patients

• Perform analysis to authenticate the users of the system.
• Provide User feedback.
• User shall be able to check for the appointment
• The system shall generate each day, a list of patients who are expected to attend
appointments that day.
• Each staff member using the system shall be uniquely identified by his or her employee
number.

3.2.2. Non-Functional Requirements

These are the requirements which specifies criteria that can be used to judge the operation of
a system rather than specific behaviors. Such requirements affect the system response time, up
time, confidentiality, integration and so many more.

10
In Doctor Patient Appointment system, the following are the Non Functional Requirements.

 Performance Requirements

The system shall be able to support up to twenty people within a Local Area Network
with a response time under six seconds. The performance of the Internet connection
cannot be guaranteed, but with a time-out mechanism.

 Availability

The system has to be available at all times.

 Security

DPAS will handle sensitive medical/personal data so security is the utmost concern.
Being able to prove to customers that the system is very secure will be essential for
the
future success of the system. Also the system has to provide secure internet
connections (SSL) for the transfer of private data. The web hosting service should
provide security services so that third parties cannot modify the information hosted
on the web site. Users will have to login to the system. Logging in will determine
what level of access the user has with the system and the views with which they are
provided. Security also means that user’s personal information shall be guarded very
closely and all passwords shall be encrypted in the database by using MD5 function.

 Maintainability

The system should be completely remote administrable. This means that system
statistics (number of appointment processed in days/months) and system functions.

3.2.3. Interface requirement

The interface should be easy and straight forward. With the new technologies, the interface is
responsive and can adopt to any device screen whether a small screen or a big screen (smart
phones, tablets, pads). This ensures that very little knowledge is needed to make use of the
system in different platforms. Also it easy to integrate the system with other programming
languages such as C#, C++, C, Java and so on.

11
 3.2.3.1. Response Time

The system performs faster on a faster network bandwidth. Guarantee response time is only 3
seconds to 1 and 45 seconds minute from the point of logging in to the point a user has full
access of the system

3.2.3.2. Requirement and Functionality

Currently the system is focused to improve the usability, experience and security of the
system. This makes sure that there will be no access to the application resources to users who fail
to provide the authentication details (username and password). The basic need of the system is to
have the browser which support any search engine such as Mozilla Firefox, Google Chrome,
internet explorer and so on.

3.2.4. Operational requirements

This consists of the hardware and software components of any computer or smart phones
devices that is required in order to use the System efficiently.
3.2.4.1. Hardware requirements

I. Processor and Processing speed: Qualcomm Snapdragon 650 or above with

1.8GHz or MediaTEK Helio Soc X10 or above with 1.8GHz.
II. RAM: 1GB RAM or above
III. Storage (ROM): Depends on the Device used but the system needs only 100MB. IV.
Cache Size: 512KB

3.2.4.2. Software requirements

i. Operating System: Windows Server 2008, Windows7, Window 8, Window 10 and any Mac Os ii.
XAMPP or MAMP as the webserver software.
iii. Database: MySQL iv.
Technology: Web based.

12
 Different analysis model can be used to getting the requirement of the system, these models are
functional and dynamic model. The functional model can be described by use case diagram and
Dynamic model can also be described in terms of Sequence Diagram.

3.3. SYSTEM ANALYSIS

3.3.1. Use Case Model

Use case is a methodology used in system analysis to identify, clarify and organize the system
requirements. A use case is a list of actions or event steps, typically defining the interactions
between a role (known in the Unified Modeling Language (UML) as an actor) and a system, to
achieve a goal. An actor can be a human or other external system. It is used to explain and
document the interaction that is required between user and system to accomplish user task. With
the main purpose of capturing the dynamic aspect of the system.

List of Actors in Doctor Patient Appointment System (DPAS).

I. System Admin
II. Doctor
III. Patient

List of Use Case

i. Login ii. Change
Account Password iii. Manage
Appointment iv. Manage
Schedule v. Manage Patients
vi. Manage Doctors
vii. Manage User And Full Specification
viii. View Related Patient ix. Check Appointment x. Provide
Feedback xi. Request For appointment xii. Check
Appointment Status xiii. Cancel the appointment xiv. Logout

13
Figure 2: DPAS use case model

14
 3.3.2. Sequence Diagram

Sequence Diagram is another important diagram in UML to describe the dynamic aspects of the
system. Sequence Diagrams are interaction diagrams that detail how operations are carried out.
They capture the interaction between objects in the context of a collaboration. Sequence
Diagrams are time focus and they show the order of the interaction.

Figure 3: DPAS Sequence Diagram

CHAPTER FOUR

15
 4. SYSTEM DESIGN

4.1. INTRODUCTION TO SYSTEM DESIGN

System design is the process of defining the architecture, components, modules, interfaces and
data for a system to satisfy specified requirements. This chapter of system design focuses on the
design model and architecture of the intended system. Also explain the structure of the system
internal interaction and the system architecture. The goal of the design is to provide a clear
picture for implementation and maintenance activities and to provide a blue print for
implementation testing and maintenance activities.

4.2. SYSTEM DESIGN METHODOLOGY AND TECHNOLOGIES

In this section we will look at different design methodologies, which are Architectural design,
Logical design and Physical design where by architectural design is the design of the system that
emphasizes on the design of the system architecture which describes the structure, behavior and
more views of the system and analysis (Eppinger & Ulrich, 2000)

4.2.1 Iterative Model

An iterative life cycle model does not start with a full specification of requirements. In this
model, the development begins by specifying and implementing just part of the software, which
is then reviewed in order to identify further requirements. Moreover, in iterative model, the
iterative process starts with a simple implementation of a small set of the software requirements,
which iteratively enhances the evolving versions until the complete system is implemented and
ready to be deployed. Each release of Iterative Model is developed in a specific and fixed time
period, which is called iteration.

Figure 4: Iterative Structure model

4.2.2 Technologies used in the system Deployment

16
The technologies involved in the development and deployment of the System are: -
a) Hyper Text Markup Language(HTML): - Is a markup language used in
structuring and presenting contents in a web. It is a web technology which can
access (store data) Local Storage directly compared to other versions of HTML

b) Cascading Style sheet (CSS): - Cascading Styling Sheet, it is used to style up the
application (front-end view). It is easily integrated with HTML5

c) Materialize: - Material Design is a design language that combines the classic

principles of successful design along with innovation and technology. Google's
goal is to develop a system of design that allows for a unified user experience
across all their products on any platform.

d) Hypertext Preprocessor (PHP): - A server side scripting language that is used as

a backend interface of the mobile application, though its communication with the
interface is parsed through Json. It is used through the communication to the
database of the application.

e) MYSQL database: - This is the database of the application, consists of the tables
that holds whole data of the system. MySQL is lightweight and can easily
integrate with PHP.

f) JavaScript: - This is an object-oriented computer programming language

commonly used to create interactive effects within web browser.

4.3. DATABASE DESIGN

It is a process of modelling an enterprise in the real world. In fact, a database itself is a model of
real world that contains selected information needed by the enterprise. Database design is the
process of designing database by using three different phases of database design such as
Conceptual model design, Logical model design and Physical model design from the database
structure.
The following are the three phases of database design which I used during designing of the system.

4.3.1. Conceptual Database Design

Once all the requirements have been collected and analyzed, the next step is to create conceptual
schema for the database using a high level conceptual data model. This phase is called
conceptual design. The result of this phase in an Entity-Relationship (ER) diagram or UML class
diagram. It is a high-level data model of specific application area. It describes how different

17
entities (objects, items) are related to each other. It also describes what attributes (features) each
entity has. It includes the definitions of all the concepts (entities, attributes) of the System.

4.3.2. Logical Database Design

The result of the logical design phase (or data model mapping phase) is a set of relation schema.
The ER diagram or class diagram is the basis for these relation schema. To create the relation
schema is quite a mechanical operation. There are rules how the ER model or class diagram is
transferred to relation schema. The relation schema are the basis for table definitions. In this
phase (if not done in previous phase) the primary keys and foreign keys defined.

18
Figure 5: DPAS ER model (Class diagram)

19
4.3.3. Physical Database Design

The goal of the last phase of database design is to implement the database. At this phase one
must know which Database Management System (DBMS) is used. For example, different
DBMS’s have different names for data types and have different data types as well. The SQL
clauses to create the database are written, the integrity constraints (rules) and the users access
rights are defined. Finally, the data to test the database is added in.

4.4. USER INTERFACE DESIGN

User Interface design is the design of websites, computers, appliances, machines, mobile
communication devices and software application with the focus on the user’s experience and
interaction. The goal of user interface design is to make the user's interaction as simple and
efficient as possible in terms of accomplishing user goals what is often called user-centered
design.

CHAPTER FIVE

20
 5. SYSTEM IMPLEMETATION

5.1. INTRODUCTION

System implementation is the realization of the technical specifications or algorithm as a

program software component or other computer system through programming and deployment.
Implementation may exist for given specification or standard. For example, web browser
contains implementation of world wide web consortium recommended specifications and
software development tool contains implementation of programming language. Also in
implementation phase, the two earlier component of software development stated in this
document namely analysis and design, have been put into practice. I have implemented this
system (Web Based System) by using HTML5, CSS, Materialize as front end technologies and
PHP, MySQL, JavaScript as back end technologies.

5.2. FUNCTIONALITIES OF IMPLEMETATION

i. Login
This is the first functionality, the system provides a login page for authentication of
the user (Doctor, Patient and Admin) where a user provides username and password
and password is encrypted by using MD5 function.

ii. Make Appointment

This functionality enables the Patient to make the appointment to the doctor of
His/her interest from the hospital and from the area of specialization.

iii. View Feedback

Also is the functionality which enables the Patient to view the feedback in case the
doctor provides the feedback to the one who is interest with.

iv. Cancel the Appointment

This Functionality enables the patient to Cancel the appointment after make the
appointment and doctor does not provide the feedback.

v. View Appointment
This functionality is for Doctor that enables the doctor to view the appointment and
once his/her appointment is received can provide the feedback to the one who make
the appointment.

21
 vi. Reschedule the Appointment
This functionality is for doctor also which help the doctor to reschedule the
appointment in case the time provided is not fit in the time provided before.

vii. Provide Feedback

This functionality helps Doctor to provide the feedback to the one who make the
appointment

viii. Change password

This functionality enabled a Patient and Doctor to change his/her password anytime
regarding that the password should be remembered.

ix. Logout
After all this is the last and final functionality for Patient and Doctor which closes the
whole session and gets back to Home Page which is Login Page.

5.3. DATABASE IMPLEMENTATION

This is the database that is accessed by the user of the system rather than the application
programming stored in the database itself. The system has been implemented with Eleven (11)
tables using MySQL as DBMS that used to manage all the data related to Patient and Doctor.
The database has been developed in reference to the ER diagram in figure 5.

5.4. USER INTERFACE IMPLEMENTATION

Implementation of the user interface is the practice of producing an interface by using web
technologies so as a user can see and use the resources with an abstraction from the sophisticated
components of the system. It is the part of the information system that is directly accessed and
interacted by the user of the system. It enables a user to request services of underlying
information system. The user interface has been implemented using HTML5, CSS, and
Materialize.

Login Page and Error Page:

22
This is where a user logs in by providing the username and password. And when the credentials
are not correct, gives out such an error as pictures below

23
 Figure 8 Login Page

Figure 9 Login Error Page

The Landing page view of Patient:
View below is the View which patient see at the first time, which include the hospital which are
in the system and patient be able to choose one of his/her choice.

24
 Figure 10 Patient landing Page

Feedback Result and Appointment form for patient

Below is the view of two pages which Patient make appointment and feedback result
respectively.

Figure 11 Appointment form of Patients

25
 Figure 12 Feedback view for Patient

Doctor landing page if there is an appointment

Below is the view which doctor at the first time enter the system view incase there are
any appointment which patient make

Figure 13 Doctor landing Page

Doctor Page for Providing Feedback To the Patients

Below is the view which doctor use to provide the feedback to the patients

26
Figure 14 Doctor feedback form View

27
Password Change
Below is the view for Password change for Both Doctor and Patients

Figure 15 Change password View

5.5. SYSTEM TESTING AND EVALUATION

System testing is testing conducted to evaluate the system compliance with the specified
requirements. It verifies the system to be delivered, meets the specification and its purpose by
investigating both functional and non-functional requirements. DPAS has been tested under the
following categories.

• Preliminary Test (Unit testing)

Refers to the technique by which individual units are tested to determine if it fits for use. It is
basically written and executed by a system developer to make sure that the code meets its design
perspective. This includes testing every unit piece of code during programming process where
each piece of code was tested before moving forward. i. Test Plan
The test plan is basically the way the final product is being tested and how it responds. I
tested the application in a way that all input/output are pushed to the application and wait for the
response. ii. Test Cases

28
 The case through testing my system is that, I uploaded my database to a free hosting
webserver online and I access it from there. In case that I am not available or near my PC, I can
just access. Previously, I was using my PC as a local server but I got problem in accessing it
since if someone have to otherwise it is on a network. As long as I shift network, then I have to
change the IP address again and again. iii. Comment
I suggest that, anyone can test the system by anyhow with the authentication, verification,
runtime, response time and the result got will be of positive one.

• Integration testing
It is the process whereby integration between component and interaction of different part of the
system are tested to verify its compatibility. The purpose of integration testing in DPAS is to
verify functional, performance and reliability requirement of the system. Basically integration
testing is done after Unit testing and before validation testing.

• Validation testing
Validation testing is done toward the end of the development process and it is performed after
the verification is complete. It is used to determine if the system complies the requirement and
perform the function as it is intended to meet the user need
CHAPTER SIX

6. CONCLUSION AND RECOMMENDATION

6.1. SUMMARY OF ACHIEVED OBJECTIVES

This chapter concludes the project by summarizing various aspects of the DPAS project
development including challenges, solutions and recommendations for the users. The project was
intended to develop a Web based system that will enable Patients choose the hospital and doctor
who is interested with, make an appointment anytime and anywhere.
The system was also designed in a proper way that every user who is responsible for using DPAS
can use the system without any special training.

6.2. CONCLUSION

Conclusively, the development of DPAS provide great advantage to Any Hospitals. Since the
manual system has now been converted into electronic from the use of DPAS. All the costs that
were experienced to Patients have been eliminated, also has solved the problem of accumulating
too much papers that resulted to wastage of work space and consumes time when decided to
collect them.

29
6.3. RECOMMENDATIONS
I recommend that, this system should be implemented and used by many hospitals in our country
as one of the mean of solving problem using technology. There is a great need of using this
system since the world is moving and technology is moving forward as well. It’s time to move
from outdated technology to the updated technology.

REFERENCES.

Shelly, G.B. and Rosenblatt, H.J. (2012) Essentials of Systems Analysis and Design. 9th ed.,
Course Technolgoy, Cengage Learning, Boston, USA.

Robinson LW, Chen RR, Scheduling doctors’ appointments: Optimal and empirically-based
heuristic policies. IIE Transactions, 2003, 35 (3):295-307.
Edwards RH, Clague JE, Barlow J, Clarke M, Reed PG, Rada R, Operations research survey
and computer simulation of waiting times in two medical outpatient clinic structures. Health
Care Analysis, 1994, 2 (2):164-169.
Rising EJ, Baron R, Averill B, A systems analysis of a university-health-service outpatient
clinic. Operations Research, 1973, 21 (5):1030-1047.
Jacobson SH, Hall SN, Swisher JR, Discrete-event simulation of health care systems.
Operations Research & Management Science, 2006, 91:211-252.
Klassen KJ, Yoogalingam R, Strategies for appointment policy design with patient
unpunctuality. Decision Sciences, 2014, 45 (5):881-911.
Samorani M, LaGanga LR, Outpatient appointment scheduling given individual day-
dependent noshow predictions. European Journal of Operational Research, 2015, 240 (1):245-
257.
Saremi A, Jula P, ElMekkawy T, Wang GG, Appointment scheduling of outpatient surgical
services in a multistage operating room department. International Journal of Production
Economics, 2013, 141(2):646-658.

30
 Vink W, Kuiper A, Kemper B, Bhulai S, Optimal appointment scheduling in continuous time:
The lag order approximation method. European Journal of Operational Research, 2015,
240(1):213-219.
Chang K-H, Hong LJ, Wan H, Stochastic trust-region response-surface method (STRONG)—
A new response-surface framework for simulation optimization. INFORMS Journal on
Computing, 2013, 25(2):230-243.
Weerawat W, Pichitlamken J, Subsombat P, A generic discrete-event simulation model for
outpatient clinics in a large public hospital. Journal of Healthcare Engineering, 2013, 4
(2):285305.
Berg BP, Denton BT, Erdogan SA, Rohleder T, Huschka T, Optimal booking and scheduling
inoutpatient procedure centers. Computers & Operations Research, 2014, 50:24-37.
Ho C-J, Lau H-S, Minimizing total cost in scheduling outpatient appointments. Management
Science,1992, 38 (12):1750-1764.
Ho C-J, Lau H-S, Evaluating the impact of operating conditions on the performance of
appointment scheduling rules in service systems. European Journal of Operational Research,
1999, 112 (3):542-553.
Yokouchi M, Aoki S, Haixia S, Run Z, Takakuwa S, Operations analysis and appointment
scheduling for an outpatient chemotherapy department. In: Laroque C, Himmelspach J,
Pasupathy R, Rose O, Uhrmacher AM (ed). The Proceedings of the 2012 Winter Simulation
Conference, 2012, 1-12.
Cayirli T, Veral E, Outpatient scheduling in health care: A review of literature. Production and
Operations Management, 2003, 12 (4):519-549.
Wijewickrama A, Takakuwa S, Simulation analysis of appointment scheduling in an
outpatient department of internal medicine. In: Kuhl ME, Steiger NM, Armstrong FB, Joines JA
(ed). The
Proceedings of the 2005 Winter Simulation Conference, 2005, 2264-2

31
32