TITLE OF PROJECT

Appointment Management System

Page | 1
Introduction
 Reference

This is web based portal for any patient who wants appointment to Doctor or for
any Diagnostic Test can use this portal. The main reason to use this System to
remove nearly the headache to maintain the appointment of patient with Doctor and
its diagnostic test prescribed by the Doctor. The User can directly choose the
Appointment with doctor according to his/her choice. When user (h/she) has a time
according to his/her preference when they are free not depend on the hospital or
doctors.

 Purpose

The Appointment Management System gives the fast & effective service to the
patient, through this portal the patients can select their Doctors & timing according
to his/her choice rather than to wait in a Queue on the Reception Desk or on calling
waiting for schedule and checking the availability of Doctors and their timing.

 Scope

Appointment Management System work under the following scope:

 The user (patient) can make & cancel appointment with Doctor.
 The Doctor can access the Patient details & his medical history.
 The user (patient) makes appointment for Diagnostic test prescribed by the
doctor.
 The Doctor can see their daily appointment.

 Information Description

Appointment Management System provide health care appointment facility

through Online Portal. The User(Patient) who is looking for an OPD appointment of
a Doctor or the Diagnostic Test prescribed by the Doctor make an appointment at
the time s/he(Doctors) is available in the hospital. The User (patient) needs to first
register for the Website. In the registration form user fill all the necessary details
given on the form. After registration a Unique Appointment ID will generate & and

Page | 2
password the user can perform login. The user first select for Category of Diseases
or Department in which h/she want to make an appointment and according to the
choice of category the Doctors name display the user can select doctors by its choice
and the after that the availability days of doctor and their time and days will display
to user and user make an appointment when h/she want. For the Diagnostic Test user
has to give their details and Test Category prescribed by the Doctor with name or
Designation. The user can also see his profile and update it according to time to time
for maintain medical history. The Doctor can also perform login with the given ID
and password and they check their appointments in a day they can access the patient
history and they also add prescription in the patient details. When all task complete
the user (patient) have to pay all bills on the account desk here they have the choice
for payment like cash, credit, debit, net banking. The all details are stored in the
database. He may also perform login. The admin have all the rights to access the
patient details and payment details. Admin can Update and add new Doctor in the
list.

Page | 3
Objective of the Project
The Appointment Management System is design for any Hospital to provide the
better facilities, manifolds & benefits to the hospital. The main Objectives for using
this portal are as follows:

 Procedure for timely & effective care.

 The patient can select the time & day or Doctor according to his/her
preference and choice.

 Through this module (System) they can calculate the earn by a Doctor in a
single day.

 A user friendly system through this User also can directly access the
appointment for the diagnostic test.

 Its remove the waiting Queue of patient for appointment on Info Desk &
Registration window.

 Reducing the papers work & easily maintain the large amount of information
through computerize way which is better and faster.

Page | 4
CATEGORY OF THE PROJECT

RDBMS stands for Relation Database Management System. The RDBMS is

responsible for:

1.) Maintaining the relationships between data in the database.

2.) Ensuring that data is stored correctly- that the rules defining the
relationships between data are not violated.
3.) Recovering all data to a point of known consistency in the event of a
system failure
4.) RDBMS also provides referential integrity i.e. Primary Key-Foreign Key
and Unique Key-Foreign Key.
SQL Server is designed to be a client server system. Client server systems are
constructed so that the database can reside on a control computer known as a
Server and be shared among several users.

SQL Server can work with thousands of client applications simultaneously.

Transact-SQL:-

SQL Server user Transact-SQL as its database query and programming language SQL
is a set of commands that allows the user to specify the information to be retrieved
or modified with Transact SQL. We can access data and query, update and manage
relational database system.

Page | 5
Module Description
The Appointment Management System work on the following module:

ProfileGenerator
This module is the first module for make an appointment with a Doctor or for
a Diagnostic Test. The User (patient) must fill the form and give all the necessary
details like: Name of Patient, UserID, Password, Picture etc. All the information
given by the user is stored in the database at the time whenever its need its can fetch
from the Database.

DoctorsInfo
This module holds the all information of doctors, their name their timing, Doc
Id and their Department etc. along with the specify Date, time schedule and Days
when they are available in the Hospital. Doctors have to must login first with the
unique ID and password then they can access the details of patient and daily
appointment. This information is stored in the database at the time of login it fetch
from the database.

DiagnosticTest
This module works as individual Unit if patient want to make appointment
h/she can directly make an appointment for test. The details of test along with the
patient details are stored in the database. The doctors can access the report for
examine. All the information as a result of test is stored in the database at the time
when patient and doctors need it they can access from the database.

Category
This module is define the category in which the patient wants to appointment
like:- BONE, ENT, SKIN etc. when user select the category the available doctors in
particular department are shown user select one of them according to his/he
preference.

Appointment
This module is responsible for Appointment Operation. Any patient want to
take appointment then first of all perform login and select appointment type like
Appointment for Doctors and Appointment for Test. If patient can select

Page | 6
appointment for Doctor, then select Doctors name from Doctor’s list and check when
they free and select the date for appointment. If user select appointment for Test then
select test categories and find the test for available list and make appointment for
that Test, through the UserID (patient Id).In future user select appointment with help
of Patient ID which is previously generated.

PaymentMoode
This is the payment module. This module contains the invoice records of
patient from how does the payment pay y the patient like cash, net banking etc. This
all information is stored in database.

QueryInfo
This module is responsible for any query about doctors, diagnostic test their
reports etc. This module is works as a reception or Information desk from which user
can make any query related to Appointment and etc. all this query is handled by the
Admin of the System and this information also stored in database.

Admin
The admin module is the Administrator module all rights are reserved for this
module. This module contains all the necessary details of Admin like Name,
Department, ID etc. The admin can access the patient details & medical history he
can also access the Doctors details and their timing and update the timing of doctors
day to day. Admin have to must login first with the unique ID and password then
they can access the whole panel. This information is stored in the database at the
time of login it fetches from the database.

Page | 7
Database Design
1. UserDetails

S.No. Attribute Datatype Size

1 UserID varchar 20

2 Password varchar 20

3 UserName varchar 20

4 Age int

5 Sex varchar 10

6 Address varchar 500

7 Country varchar 20

8 PIN int

9 Phone int

10 Email varchar 20

11 Photo image

2. DoctorsDetails

S.No. Attribute Datatype Size

1 DoctorsID varchar 20

2 DoctorsName varchar 20

3 DoctorsPassword varchar 20

4 Qualification varchar 50

Page | 8
5 Department varchar 50

6 Experience varcahr 50

7 PhoneNo. int

8 Email varchar 20

9 DoctorsPhoto image

3. DiagnosticTestDetails

S.No. Attribute Datatype Size

1 TestID varchar 20

2 TestName varchar 20

3 TestCost int

4 ReferedBy varchar 20

5 Date date

6 Time time

4. CategoryDetails

S.No. Attribute Datatype Size

1 CategoryID varchar 20

2 CategoryName varchar 50

3 DoctorsID varchar 20

Page | 9
5. AppointmentDetails

S.No. Attribute Datatype Size

1 AppID varchar 20

2 UserID varchar 20

3 DoctorsID varchar 20

4 CategeoryID varchar 20

5 DateOfAppointment date

6 TimeOfAppointment time

7 PayID varchar 20

6. PaymentDetails

S.No. Attribute Datatype Size

1 PayID varchar 20

2 AppID varchar 20

3 Amount int

4 DateOfPayment date

5 TimeOfPayment time

Page | 10
7. QueryDetails

S.No. Attribute Datatype Size

1 QuerryNo. varchar 20

2 UserID varchar 20

3 AdminID varchar 20

4 DateOfQuery date

5 Message varchar 500

6 ResponseMessage varchar 500

8. AdminDetails

S.No. Attribute Datatype Size

1 LoginID varchar 20

2 Password varchar 20

3 AppID varchar 20

4 DoctorsID varchar 20

5 CategoryID varchar 20

6 TestID varchar 20

7 QueryID varchar 20

8 PayID varchar 20

Page | 11
DATA FLOW DIAGRAM: - It is a graphical representation of flow
of data through a system. In this diagram, the external entities provide input data
for the processing. During the processing, some intermediate data is generating.
After final processing, the final output data is generating.

Rules of making DFD: - there are following seven rules for the construction of
data flow diagram

1) Arrow should not cross each other.

2) Square, circles, and files must bear names.
3) Decomposed data flow must be balance.
4) No two data flows, square or circles can have the same name.
5) Draw all data flows around the outside of the diagram.
6) Choose meaningful names for data flows processes and data stores.
7) Control information such as record counts, passwords and validation
requirements are not pertinent to a data flow diagram.

DFD are describe for different level

e.g.:

i. 0 level DFD
ii. 1 level DFD
iii. 2 level DFD

Page | 12
 0’Level

ProfileGenrator

DoctorsInfo

DiagnosticTest

User Categeory
Appointment
Doctor Management Appointment
System
Admin PaymentMode

QueryInfo

Page | 13
 1’Level

Staff AdminDetails

Admin
DiagnosticTestDetai

Category
Doctors
CategoryDe
Details
tails
ls

Diagnos
ticTest
Doctors
Info

User/Doctors

Appointment AppointmentDetails

Profile
Generator
UserDetails
Payment
make

PaymentDetai
Query ls
Perform Access

QueryDetails

Page | 14
2nd Level

1. ProfileGenerator

User Select ID
&
Password
Fill New User
Interact with

Registration
Form
UserDetails

Profile Check Existing Check

Generator or Not Login
Login
Details

Welcome!Name
of User,you can
select
appointment for
Doctor or Test

Page | 15
2. Admin
Existing

Staff Admin

CreateProfile
& take ID

Perform
Login
AdminDetails

Check Login UserDetails

or Not

Sorry! Your Correct

LoginID is
wrong
Appointment Doctorsdetail
please try
s
again!

Page | 16
3. Appointment

Doctor

Date/Time/Days

Appointment

AppointmentDetails

Access
AppDettails

User See
appointment
details and
select

Page | 17
ENTITY RELATIONSHIP DIAGRAM

An ER diagram is a model that identifies the concept or entities that exist in a

system and the relationships between those entities. An ERD is often used as a way

to visualize a relational database: each entity represents a database table and the

relationship lines represents the key in one table that point to specific records in

related tables.

Advantages of ER diagram

 Professional and faster Development.

 Productivity Improvement.

 Fewer Faults in Development.

 Maintenance becomes easy.

Page | 18
ERD
UserDetails 1 M DoctorsDetails
Select
1
1

Update
M
DiagnosticTest
update
Details

categeoryID

CategeoryDetails
M

M
AppointmentDetails

M 1
categeoryID AdminDetails

1
make 1
PaymentDetails

N
QueryDetails

Page | 19
Process Logic
User
Start

User

Select
Appointment
for Doctor or
Test

Selection DoctorsDetails
of test
DiagnosticTestDetails CategoryDetails

Select Test Select Categeory &

Doctor

Apoointment Appoinment
AppointmentDetails

End

Page | 20
TESTING
Testing is the process to uncover the errors.

Objectives of Testing: -There are following objectives:

i. Testing is the process of executing the program to find error.

ii. A group test has a high probability of finding the errors.
iii. A successful test uncovers the all errors that have not been found.

Testing Principal: -There are following objectives:

i. The test should be according to the customer’s requirement.

ii. There should be a planning for testing before it starts.
iii. Poreto principle implies that 80 percent of all errors uncover during testing
will likely be traceable to 20 percent of all program components.
iv. Testing should begin ‘in the small’ and progress toward testing ‘in the large’.

There are two types of testing: -

1. Black Box Testing

2. White Box Testing

1. Black Box Testing: -It is also called behavioral testing. The program is
directly run by the computer to find the errors.

Objective of the Black Box Testing

i. Incorrect or missing function.

ii. Interface error.

Page | 21
iii. Errors in data structures on database access.
iv. Performance error.
v. Initialization and termination error.

2. White Box Testing: -It is also called glass box testing. It traces all the paths
of a program manually to find the errors.

Advantage of White Box Testing

i. It guarantees that all independent paths have been checked at least once.
ii. It chicks all logical decisions for true and false.
iii. Executes all loops at their boundary values.
iv. Checks internal data structures.

Reasons for White Box Testing

i. It can find logical errors, which cannot be found by ‘black box’.

ii. We often believe that a logical path is not likely to be executed when, in fact,
it may be executed on a regular basis.
iii. Typographical errors are random. The block box testing can find out typing
error but typing error but typing error are in the program.

Page | 22
Input/Output Generation
Registrtion page
This page is design for the registration. The new user interact with it and fill the necessary
details like Name, address, age, sex, phone and A unique Id and password for the for the login.

LoginPage
This page is design for the security purpose. User, Admin, Doctors they have to perform
login with their Unique ID and password then they access the next page or module and do whatever
they want according to the authorization and authentication.

Appointment Page
This page is design for the appointment purpose either it is related to doctor or the
diagnostic test. User select category, doctor, and their date/time and book appointment for OPD.
If they select the appointment for the diagnostic test the user select it then take necessary details
and book appointment for Diagnostic test.

Page | 23
TOOLS AND PLATFORM

HARDWARE USED

PROCESSOR- I55th generation

RAM- 4GB

Monitor – HCL LCD

Hard disk – 500 GB

Key board – HCL

Mouse – HCL

SOFTWARE USED

Visual studio -2015

SQL server 2012

Operating System – windows 10

Ms Office -2013

Page | 24
Future Scope
The Appointment Management System for Diagnostic test or Doctor is flexible enough to meet
the requirement of the customer such as:-

 Home delivery of reports may be provided.

 Online booking of seat for test should be provided.
 Any institute/school/office can book their seat for routine diagnostic test on which they can
get discount.
 Provide health report o the patient with there remedies.

Page | 25
Biblography

1. An Integrated Approach to Software Engineering: PANKAJ JALOTE

2. Microsoft visual studio 2015 Unleashed Publication(Third Edition)
3. HTML: Sams Teach Your Self: Dick Oliver
4. SQL Server 2012, Database Design Study Guide: Kevin Hough
5. Structured Analysis and Design (MCS-14) of IGNOU
6. http://webdev.wrox.co.uk

Page | 26