CHAPTER ONE

INTRODUCTION

1.1 BACKGROUND OF THE STUDY

Appointment scheduling systems are used by primary and specialty care
clinics to manage access to service providers, as well as by hospitals to schedule
elective surgeries. Many factors affect the performance of appointment systems
including arrivals and service time variability, patient and provider preferences,
available information technology and the experience level of the scheduling
staff. In addition, a critical bottleneck lays in the application of industrial
engineering and operations research (IE/OR) techniques. The most common
types of health care delivery systems are described in this article with particular
attention on the factors that make appointment scheduling challenging. For each
environment relevant decisions ranging from a set of rules that guide schedulers
to real-time responses to deviations from plans are described. A road map of the
state of the art in the design of appointment management systems is provided
and future opportunities for novel applications of IE/OR models are identified.
Appointment management system is a desktop application that is designed to
help fix schedule and appointment from the management of organization and
the customers, send messages to customers either by phone or email. With this
computerized system there will be no loss of record or member record which
generally happens when a non-computerized system is used. It is designed in
visual studio and the database used is Microsoft SQL server 2005.
What is an online appointment system? Boiled down, it’s a self-service
program that allows patient to schedule an appointment on your website. Then,
the job automatically enters your calendar. It seems simple on the surface, but
the benefits of an online appointment system run deep! An easy scheduling

1
process results in more job bookings. When patients help themselves, teams like
yours benefit from organized workflows, more productive workdays, and
happier customers.

With an efficient scheduling process working in the background, your

office staff can spend time on more important tasks, and your field team can
accomplish.

1.2 Statement of Problem

The following are some of the problems faced:
 An increase in the waiting time for appointments.
 Frustration for customers, patients and staff.
 A loss of valuable resources.
1.3 Aims and Objectives of the Study

Aim and objectives of this project is to create doctor patient handling

management system that will help doctors in their work and will also help
patients to book doctor appointments and view medical progress. The system
allows doctors to manage their booking slots online. Patients are allowed to
book empty slots online and those slots are reserved in their name.

The main objectives of the research are:

 To Create Web based online doctor appointment management system.

 To resolve contact issue.

 To resolve issue of missing booking or appointment.

 To view appointment list, read time online, everywhere, anywhere.

2
1.4 Significance of the Study

Accessibility: Online doctor appointment systems enable patients to

access healthcare services more conveniently. This is particularly beneficial for
individuals with limited mobility, those residing in remote areas, or those who
have busy schedules. It eliminates the need for physical travel and allows
patients to seek medical advice from the comfort of their own homes.

Cost Effectiveness: Implementing online doctor appointment systems can

potentially reduce healthcare costs. By providing virtual consultations,
unnecessary visits to hospitals or clinics can be minimized, resulting in cost
savings for both patients and healthcare providers.

1.5 Research Questions

1. What are the key factors influencing patient trust and acceptance of online
doctor appointment systems?

2. How can the design of online doctor appointment systems be improved to

enhance user experience and encourage greater engagement?

3. What features and functionalities should be prioritized in the design of

online doctor appointment systems to ensure confidentiality and data
security?

4. What are the barriers and challenges associated with the implementation
and adoption of online doctor appointment systems among healthcare
providers and patients?

5. How does the use of online doctor appointment systems impact healthcare
accessibility and patient-doctor communication?

3
1.6 Scope and Limitation of the Study

Patient-Doctor Relationship: Building a strong patient-doctor relationship

is crucial for effective healthcare. Online appointments may lack the personal
connection and rapport that can be established during face-to-face interactions.
This can impact patient trust, satisfaction, and the overall quality of care
provided. While online appointments can be suitable for certain medical
conditions, there are limitations in their applicability to all healthcare needs.
Emergencies, complex surgical procedures, and certain specialized treatments
may still require in-person consultations and interventions.

Considering these limitations is essential when conducting a study on the

design and appointment of online doctors. Addressing these challenges and
finding ways to mitigate their impact can help improve the effectiveness and
acceptance of online healthcare services.

1.7 Justification of Study

We implement this system for better user experience. This system is very
easy to access. Also, we 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 and smart
phone. So user can easily access the system anytime anywhere. This system is
very simple and user friendly so, any user can use this system easily.

4
 CHAPTER TWO

LITERATURE REVIEW

2.1 Waiting Time

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, 2013). 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, 2008). This paper deals with the waiting time
to see physicians. Long waiting times are a serious problem for patients using
urban health centers in developing countries (Bachmann, 2007). A block
appointment system was introduced and evaluated in a large South African
health centre. 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, 2009). Appointments had no benefits for patients not
seeing doctors or collecting repeat medication. 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).

5
2.2 Patients’ Appointment System

A patient appointment system or appointment schedule for health care

center started long time ago (Harper, 2003). Management of patients’
appointments has earlier worked and has developed simplified queuing models
and fairly static scheduling conditions. Another attempt was made to calculate
the waiting time between patient and doctor using the mathematical queuing
models to minimize waiting time (Gamlin, 2007). However; traditionally the
appointment system has considered that the doctor time is more important than
patient time (Wijewickrama, 2005). So an appointment system was designed to
minimize the doctor idle time but current designing of an appointment system is
based on decisive factors with respect to both the patient and doctor (Takakuwa,
2005).

2.2.1 Appointment Delay

Past research shows that the longer the appointment delay which is
defined as the time between the day a patient requests an appointment and her
actual appointment date, the higher the chances that he/she will cancel or not
show up (Gallucci et al. 2005). This suggests an obvious way of minimizing no-
shows and cancellations: this is done by asking the patients to come right away
or make appointment requests on the day they want to be seen (Murray, 2000).
This is called an open access (OA) or advanced access policy (Tantau, 2000),
and of late it has become a popular paradigm in practice and the subject of
active research. Several authors report on their experiences in implementing
OA, both positive and negative (Dixon et al. 2006). Some practitioners strongly
advocate OA (Murray and Tantau 2000), and there are some who are strongly
against it (Lamb, 2002).

6
2.2.2 Managing Patients’ Appointment System

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).

2.3 Online Booking System

An online system is also known as a web-based system. 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
7
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 booking 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 an 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).

2.4 Existing Hospital Appointment Schemes

One application developed to manage patients’ appointment scheduling

has used exponential enter arrival times. This model assumes that the
exponential enter arrival times could not be directly validated by date, and it is
limited due to the nature of the appointment scheduling (Rohleder, 2002). Since
appointments are scheduled in the future, the exact model of call arrivals will
only have limited impact on measures related to the time between the call and
the appointment time. For this reason, the challenge for making appointment
system is designing a suitable system based on the health care procedure

8
environment (Klassen, 2002). Many studies about patients’ appointment have
found that there are rules or policies for scheduling appointment system such as
no scheduling for more than 20 or 30 clients and the best schedule is to place
two patients in the first appointment and spread the rest consistently over a
period based on average service times (Klassen, 2004). On the other hand, a
patient can call for an appointment without knowledge of the type of
appointment and appointment queue number and the patient is not aware
whether the appointment is variable or not. Sometimes the exact duration for
each patient can be known but at other times this is unknown (Rohleder, 2004).
Another system developed by Mustafa, (2004) allows a registered patient,
having user name and password, to access and explore the list of physicians
alphabetically and select a physician whose email contact and profile are also
provided. A patient can also view the physician working calendar to find out
his/her working and non working day to make an appointment. When the
patient selects, view calendar the patient can then choose any valid day in any
month to make an appointment (Mustafa, 2004). After that, the patient will
receive an e-mail from the system to confirm the appointment time or to inform
the patient that the selected time is already taken by another patient or blocked
by the physician. In general, the patient appointment system provides all the
choices and the capabilities to the patients, such as selecting a physician,
selecting the time of appointment, and allows them to access the health care
system day or night and schedule their own appointments using the Internet
without spending time holding for a nurse or having lengthy phone calls. Porta-
Sales et al. (2005) developed another system. The main concept of the system is
contacting, screening and scheduling appointment with the health care center
initially by an expert nurse and the patient initiating contacting with the health
care center using the telephone. Moreover, the health care center can be

9
accessible from different places. So there should be PC resources and PC
consultations to be accessed from different sources, from other hospitals, from
general practitioners, or even from the patients themselves. The main reason
given for the scheduled visits was admission into the health care; the median
time-lapse between the first and second visit was 21 days, between the second
and third was 27.5 days and between the first and third was 48 days. Comparing
patients, who did not attend the three consecutive visits with those who did,
indicated that the former had (at the first visit) a lower performance status. Su et
al. (2003) studied in a private hospital which has several clinics. For each clinic,
the average patient load is 20 per consultation section (morning or afternoon)
and the health care system adopts both a patient appointment model and patient
registration model. The system allows patients to have self-selected specific
physicians for consultation and registration (Shih, 2003). The management
appointment system studied by Su and Shih, (2003) is based on the first 20
reserved for scheduled patients, after that, only seven are offered for scheduling.
Odd numbers after 20 are left for walk-ins. The arrival time of the first patient is
assumed to be the same as the clinic starting time. The scheduled patients are
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. It will also enable the
patients to view and monitor their medical records online.

10
 CHAPTER THREE

RESEARCH METHODOLOGY
3.0 Introduction

Research methodology is the architecture or the layout of the research

framework. According to Leech, & Onwuegbuzie, (2008) methodology refers to
ways of obtaining, organizing and analyzing data. This chapter contains
research design, population, sample frame, sample size, and method of data
analysis. The chapter also covers the research ethical issues to be observed.

3.1 Research Design

The descriptive research methods were used for this study. The method
aims to discussing data and describing it in a systematic manner and presenting
it by using table of frequencies and percentage scores (Nworgu,1991).

3.2 Population and Sample

The target population of the study comprises all doctors that get online
appointment which has an average population of two hundred (120) designing
and implementing an online appointment. Disproportionate sampling is adopted
to select Seventy (70) respondents with in the target population for this study.

3.3 Instrument for Data Collection

The data was collected from the respondents through a self-developed

questionnaire which has seven (7) questionnaire items. Section ‘A’ is design to
collect information personal bio-data, section ‘B’ is how online doctor
appointment system is designed and implemented. Section ‘C’ is to access the
level of designing and implementing online doctor appointment. Section “D” is

11
executed on the level of designing and implementing online appointment with
doctors at Federal Teaching Hospital Gombe.

3.4 Validity of the Instrument

The instrument will be validated by the researcher’s supervisor, lecturers

in the department and colleagues who are vested on the field for necessary
suggestions, modifications and corrections.
3.5 Reliability of the Instrument
Reliability is concerned with the consistency with which an instrument
measured what it tends or supposed to measure. It also finds out whether
respondents understand the question asked and its relevancies to the variable of
the study (Collins, 2003).
3.6 Method of Data Collection

The researcher will visit the Federal Teaching Hospital Gombe to access
the level of designing and implementing online appointment will be
administered personally the questionnaires.

In addition, the researcher will be explaining the questions to the

respondents and collect the completed copies of the questionnaires on the spot
after filling.

This will be done in order to ensure a Hundred percent return of the

questionnaires and also to eliminate unnecessary influence and also to avoid
comparison of responses among the respondents.

12
3.7 Procedure for Data Analysis

The data collected for the study analyses by using frequency and
percentage table, taking into consideration the research questions. It will be
used to translate the information with tables for better understanding of the data.

3.8 Justification of Methodology

Every software developed is different and requires a suitable SDLC approach

to be followed based on the internal and external factors. Some situations
where the use of Waterfall model is most appropriate are:

 Requirements are very well documented, clear and fixed.

13
 Product definition is stable.

 Technology is understood and is not dynamic.

 The project is short.

 Simple and easy to understand and use

 Easy to manage due to the rigidity of the model . each phase has specific
deliverables and a review process.

 Phases are processed and completed one at a time.

 Easy to arrange tasks.

14
 CHAPTER FOUR

ANALYSIS, DESIGN AND DEVELOPMENT

4.0 Introduction

The chapter describes the system study, analysis, design strengths and
weaknesses of the current system, Contest level diagrams, Entity Relationship
Diagram, Architectural design.

4.1 System Analysis

During the system study phase, requirements of Online Doctor

Appointment System (ODAS) were categorized into user requirements, system
and hardware requirements.

After interpretation of the data, tables were drawn and process of data
determined to guide the researcher of the implementation stage of the project.
The tools, which were employed during this methodology stage, where mainly
tables, Data Flow Diagrams and Entity Relationship Diagrams. The design
ensures that only allows authorized users to access the systems information.

Table 1: Biodata of the Respondents

S/N Variables Variable classification Frequency Percentage
1 Age 15-29years 14 28%
20-24years 8 16%
25-29years 17 34%
30andabove 11 22%
Total 50 100%
2. Educational Primary School 9 10%
background
15
 Secondary School 12 24%
Tertiary 7 14%
None 13 26%
Total 50 100%
3. Marital status Married 29 58%
Single 8 16%
Divorce 5 10%
Widow 8 16%
Total 50 100%
4. Department Record 16 32%s
Radiography 11 22%
Laboratory 5 10%
Accident & Emergency 18 36%
Administration 50 100%

Table 2: How Online Doctor Appointment is Implemented and Designed

S/N Variables Variable classification Frequency Percentage

1. Have you ever Yes 43 86%
heard of Online
Doctor No 7 14%
Appointment Total 50 100%
Design and
Implement?
2. Does the system Yes 75 80%
work 100% in your
department or unit? No 25 20%
Total 100%W

16
The above table shows that most of the respondent having 86% heard about the
online doctor appointment design and implementation while only 14% do not
heard about it and 80% agreed that the system works in their department of unit
while 20% disagreed.

Existing Online Doctor Appointment Systems

Refer to the literature review, observation, interviews and questionnaires

as explained in chapter three it should be noted that at Hospital doctor
maintenance, we were able to analyze existing systems as discussed below.

The current system was manual where data is written on different papers
and transferred to the different departments, human errors were vulnerable
since it was paper based and retrieval of files was time consuming as they had
to manually locate patient some of which were even lost and thus finding such
information was hard. Per the statistics carried 90% of the users were not
contented with the system reason that it was not secure in terms of security and
storage as it was prone to damages like loss of important information, worn out
papers, outbreak of lire. The speed of recording and retrieval Patient’s
information was average yet 10% were some ok with the system reason that the
paper work can used for future reference.

Requirements Specifications

After analyzing the data collected, we formulated a number of

requirements namely user requirement, system hardware software attribute.
These were grouped as user, functional, non-functional and systems
requirements.

17
User Requirement

During data collection, the we investigated and found out how the current
system operates, not only that but also tried out which problems are faced and
how best they can be settled. The users described some of the basic
requirements of the system this includes Search for Patients, Register Patient,
Update record, Doctor information record, view doctor availability record and
view all types of reports.

Functional and Non-Functional Requirements

The following is the desired functionality of the new system.

Accept of submissions in form of raw patients; perform analysis of financial to

authenticate the users of the system.

And non-functional requirement includes the following

The system must verify the validate all user input ant user must be notified in
case of errors detected in the database, the system should allow room for
expansion.

System Requirement

This section describes the hardware components and software

requirements needed for effective and efficient running of the system

18
Logical Model

Fig: 4.1.3 Logical Model

19
System Architecture

This gives a high-level view of the new system with the main
components of the system and the service they provide and how they
communicate. The system is implemented using a three-tier architecture that
comprises of our interface, process management and DBMS as illustrated
bellow.

20
Entity Relationship (E-R) Diagram

An entity relationship diagram (ERD) shows the relationships of entity sets

stored in a database. An entity in this context is a component of data. In other
words, ER diagrams illustrate the logical structure of databases. An entity
relationship diagram is a means of visualizing how the information a system
produces is related.

Entity: Which are represented by rectangle. An entity is an object or concept

that has its existence in the real world. It includes all those things about which
data is collected. A weak entity is an entity that must defined by a foreign key
relationship with another entity as it cannot be uniquely identified by its own
attributes alone.

Attributes: Which are represented by ovals. A key attribute is the unique,

distinguishing characteristic of the entity. For example, an employee's social
security number might be the employee's key attribute.
An Entity Set: It is a set of entities of the same type that share the same
properties, or attributes.
Process: A process shows a transformation or manipulation of data flows
within the system.
Actions: Which are represented by diamond shapes, show how two entities
share information in the database.

21
Fig: Entity Relationship Diagram

Data Flow Diagram

Fig. Data Flow Diagram

4.4 Database Diagram

22
Fig: 4.4 Database Diagram I

Fig: Database Diagram II

23
Fig: Database Diagram III

System Development

System development we are used the tools visual studio dot net 2008, C #
language, ASP dot net language and data store we are database used to
Microsoft SQL server database 2014.

Introducing Visual Studio .NET 2008

Visual Studio .NET is a complete set of development tools for building ASP
Web applications, XML Web services, desktop applications, and mobile
applications. Visual Basic .NET, Visual C++ .NET, Visual C# .NET, and
Visual J# .NET all use the same integrated development environment (IDE),
which allows them to share tools and facilitates in the creation of mixed-
language solutions. In addition, these languages leverage the functionality of the
.NET Framework, which provides access to key technologies that simplify the
development of ASP Web applications and XML Web services.

24
Fig: Introducing Visual Studio .NET 2008

Introduction to the C# Language

C# is an elegant and type-safe object-oriented language that enables

developers to build a variety of secure and robust applications that run on
the .NET Framework. You can use C# to create Windows client applications,
XML Web services, distributed components, client-server applications, database
applications, and much, much more. Visual C# provides an advanced code
editor, convenient user interface designers, integrated debugger, and many other
tools to make it easier to develop applications based on the C# language and the
.NET Framework.

C# syntax is highly expressive, yet it is also simple and easy to learn. The
curly-brace syntax of C# will be instantly recognizable to anyone familiar with
C, C++ or Java. Developers who know any of these languages are typically able
to begin to work productively in C# within a very short time. C# syntax
simplifies many of the complexities of C++ and provides powerful features such
as nullable value types, enumerations, delegates, lambda expressions and direct
25
memory access, which are not found in Java. C# supports generic methods and
types, which provide increased type safety and performance, and iterators,
which enable implementers of collection classes to define custom iteration
behaviors that are simple to use by client code. Language-Integrated Query
(LINQ) expressions make the strongly-typed query a first-class language
construct.

As an object-oriented language, C# supports the concepts of

encapsulation, inheritance, and polymorphism. All variables and methods,
including the Main method, the application's entry point, are encapsulated
within class definitions. A class may inherit directly from one parent class, but
it may implement any number of interfaces. Methods that override virtual
methods in a parent class require the override keyword as a way to avoid
accidental redefinition. In C#, a struct is like a lightweight class; it is a stack-
allocated type that can implement interfaces but does not support inheritance.

In addition to these basic object-oriented principles, C# makes it easy to

develop software components through several innovative language constructs,
including the following:

 Encapsulated method signatures called delegates, which enable type-safe

event notifications.

 Properties, which serve as accessors for private member variables.

 Attributes, which provide declarative metadata about types at run time.

 Inline XML documentation comments.

 Language-Integrated Query (LINQ) which provides built-in query

capabilities across a variety of data sources.
26
 If you have to interact with other Windows software such as COM
objects or native Win32 DLLs, you can do this in C# through a process called
"Interop." Interop enables C# programs to do almost anything that a native C++
application can do. C# even supports pointers and the concept of "unsafe" code
for those cases in which direct memory access is absolutely critical.

The C# build process is simple compared to C and C++ and more flexible
than in Java. There are no separate header files, and no requirement that
methods and types be declared in a particular order. A C# source file may
define any number of classes, structs, interfaces, and events.

The following are additional C# resources:

 For a good general introduction to the language, see Chapter 1 of the C#

Language Specification.

 For detailed information about specific aspects of the C# language, see

the C# Reference.

 For more information about LINQ, see LINQ (Language-Integrated

Query).

 To find the latest articles and resources from the Visual C# team, see
the Visual C# Developer Center.

.NET Framework Platform Architecture

C# programs run on the .NET Framework, an integral component of

Windows that includes a virtual execution system called the common language
runtime (CLR) and a unified set of class libraries. The CLR is the commercial
implementation by Microsoft of the common language infrastructure (CLI), an

27
international standard that is the basis for creating execution and development
environments in which languages and libraries work together seamlessly.

Source code written in C# is compiled into an intermediate language (IL)

that conforms to the CLI specification. The IL code and resources, such as
bitmaps and strings, are stored on disk in an executable file called an assembly,
typically with an extension of .exe or .dll. An assembly contains a manifest that
provides information about the assembly's types, version, culture, and security
requirements.

When the C# program is executed, the assembly is loaded into the CLR,
which might take various actions based on the information in the manifest.
Then, if the security requirements are met, the CLR performs just in time (JIT)
compilation to convert the IL code to native machine instructions. The CLR
also provides other services related to automatic garbage collection, exception
handling, and resource management.

Fig: Introduction to the C# Language

28
 Language interoperability is a key feature of the .NET Framework.
Because the IL code produced by the C# compiler conforms to the Common
Type Specification (CTS), IL code generated from C# can interact with code
that was generated from the .NET versions of Visual Basic, Visual C++, or any
of more than 20 other CTS-compliant languages. A single assembly may
contain multiple modules written in different .NET languages, and the types can
reference each other just as if they were written in the same language.

In addition to the run time services, the .NET Framework also includes an
extensive library of over 4000 classes organized into namespaces that provide a
wide variety of useful functionality for everything from file input and output to
string manipulation to XML parsing, to Windows Forms controls. The typical
C# application uses the .NET Framework class library extensively to handle
common "plumbing" chores.

Introduction to ASP.NET

ASP.NET is a web development platform, which provides a

programming model, a comprehensive software infrastructure and various
services required to build up robust web applications for PC, as well as mobile
devices.

ASP.NET works on top of the HTTP protocol, and uses the HTTP
commands and policies to set a browser-to-server bilateral communication and
cooperation.

ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are

compiled codes, written using the extensible and reusable components or
objects present in .Net framework. These codes can use the entire hierarchy of
classes in .Net framework.
29
 The ASP.NET application codes can be written in any of the following
languages:

 C#

 Visual Basic.Net

 Jscript

 J#

ASP.NET is used to produce interactive, data-driven web applications

over the internet. It consists of a large number of controls such as text boxes,
buttons, and labels for assembling, configuring, and manipulating code to
create HTML pages.

Introduction to SQL Server Management Studio

SQL Server Management Studio (SSMS) is the main administration

console for SQL Server.

SSMS enables you to create database objects (such as databases, tables,

stored procedures, views etc), view the data within your database, configure
user accounts, perform backups, replication, transfer data between databases,
and more.

SQL Server Management Studio is a graphical user interface; so many

tasks are "point and click". It is also the interface that enables you to run SQL
scripts, so there are also tasks that require programming/scripting. However,
many tasks can be performed either via GUI or SQL script, so it's your choice
which one you use. For example, you can create a database using the GUI or by

30
running a SQL script. Having said that, you still need the GUI in order to run
the script.

Connect to Server

When you open up SQL Server Management Studio, you will be

prompted to connect to SQL Server with a log in screen that looks like the
following screenshot. You can either keep the default authentication settings or
change them.

Fig: Connect to Server

Here's what SQL Server Management Studio looks like once you've connected
(and opened a new query):

31
Query Interface

Fig: Query Interface

The left pane contains the Object Explorer. The Object Explorer provides
navigation to databases, server objects (such as triggers), log files, and more.

The right pane will change depending on what task you're performing.
For example if you're modifying a table, you might see the table design and
properties in the right pane. In this screenshot I have opened a blank query by
clicking the New Query button. Many database tasks can be performed either
via this window (i.e. progamatically), or via a GUI equivalent (i.e. "point and
click").

You can use SQL Server Management Studio to create as many databases as
you like. You can also connect to as many databases on as many servers as you
like. These all appear in the Object Explorer. So you could run a query on your
development environment, then switch to your test or production environment
32
and run a query there. Because of this, you need to be careful that you don't
accidentally run a script against the wrong server.

Most of the tasks performed with SQL Server Management Studio are initiated
either from the top menu, or by right-clicking on an icon/object.

33
 CHAPTER FIVE

RESULT

5.1 System Interfaces

All System interfaces in this chapter were created in ASP dot net and C#
coder while creating ASP and Visual Studio Dot Net 2008 Integrated
Development Environment (IDE) interfaces.

5.2 Login Form for the Different Users

Only authorized user with the right user name and password has right to
access the services to particular department as like Patients, Doctors and
Hospital he or she intern to view. When wrong user name and password is used
the System rejects access to the services.

5.3 System Administration Home Page

The system administrator can add, edit system user and has access to
view the services offered by the different for easer tracking in cases of
mismanagement in the Hospital.

5.4 Patient Appointment Home Page

This page is patient can access the appointment and view the doctor
available time and can known the time to views the doctor actual time. Then the
system is patient not a more time queue.

34
5.5 Doctor Registration Page

This page is Doctor Registration to the system. Doctor Name, Designation,

Department, Available Time, Chamber Time and more information registration this page.

35
 CHAPTER SIX

SUMMARY, CONCLUSION AND RECOMMENDATIONS

6.0 Introduction

This Chapter describes discuss the objectives of the system stipulated in

earlier chapters, limitation of the system conclusion and recommendation of the
System.

6.1 Summary

As discussed in the previous chapters the main problem that we addressed was
dealing with patient, doctor and hospital document. It is the above situation that above us
to techniques of developing this Online Doctor Appointment System to be used the
Patient, Doctor and Hospital to enable them to handle details on policies efficiently and
effectively. The Project has implemented most of the objectives stipulated in earlier
chapter. The Online Doctor Appointment System offers a number of benefits to the user
and can capture data, store, view, add and delete the records entered the data cal also be
posted information to the database.

Problems Encountered during Data Collection: sensitive information released to us,

few projects and books written about Online Doctor Appointment System.

Problem Encountered during System Design: Limited time to finish up to work, but
we are finally finished to our system design the projects.

36
6.2 Limitations:

This section describes those services that are not provided by the system and those
included the following. It is always connected to the Internet connection. It Support to
Microsoft Windows Platform and not support to others platform as like MAC or Linux.

6.3 Conclusions

The core reason for the establishment of computerizing Online Doctor

Appointment System is to enable the hospital administrators in a convenient, fair and
timely manner. Therefore, the IT used should support the core objective of the system if it
is to remain relevant to the hospital. A lot still needs to be done in the IT department in
order to make available technology effective. This may involve training of the hospital
staffs on how to enter data in the right and relevant data in the system and the
management to keep updating the hardware and software requirements of the system. IT
and computer systems need to be kept being upgraded as more and more IT facilities
software are introduced in to days IT market. The researcher acknowledges the fact this
system does not handle all patient doctor and hospital. The researcher therefore suggests
that for further research, the following can be researched on. The most cost-effective way
of handling all Hospital Patient management system process.

6.4 Recommendations

Thanking of all the members of hospital staff in the hospital to get

accustomed to the system will be a priority. This being a new system the
computerized Online Doctor Appointment System will replace their jobs.

37
 APPENDIX I

DEPARTMENT OF COMPUTER SCIENCE

Questionnaire

The purpose of the questionnaire is to identify and specify functional

requirements of our proposed Online Doctor Appointment System (ODAS) to
be used by Patient, Doctor & Hospital.

By

AMIR SULAIMAN BABAN NANA ND/CPS/021/138

AMINA YA’U SHU’AIBU ND/CPS/021/133

JIBRIL AHMAD ND/CPS/021/155

USAMA IBRAHIM ND/CPS/021/163

38
APPENDIX II

The Organizational Structure

This section describes the flow of powers of delegation in the hospital, patient
& doctor.

Fig: The Organizational Structure

39