1.

PROJECT PROFILE
1.1 PROJECT TITLE:

 The title of this project is DoctorFinder.

1.2 OBJECTIVE:-

 The main objective is to develop a JAVA based web application named “DoctorFinder” that covers
all the aspects of making appointment of doctors.
 It enables healthcare providers to improve operational effectiveness, reduce costs, reduce medical
errors, reduce time consumption and enhance delivery of quality of care. This system help reduce the
problems occur when using the manual system and helps patients to skip endless queues.
 The important thing is it will become easier for the data record and retrieval. This software also
stores all the patient details, patients profile, prescriptions etc. This system enables doctors and clinic
assistant to manage patient records and appointments. User can enter their details, update their profile
and they can select doctors to make appointments.
 Other than that, the system is user friendly and it can help the clinic to manage their appointments.
The system helps to avoid making duplicate appointments. Users can view available doctors and their
timings and can make appointments according to it.
 Users also get an option to cancel their appointments. Users can view their upcoming appointments
and past appointments are deleted automatically.
 The system also allows doctors to log in. Doctors can edit their profile and view their upcoming
appointments, patients etc.
 The system also has an administrator section, where only a single person can manage the whole
system.
 Administrator can add/remove patients, doctors and departments and search for appointments.

1
 2.REQUIREMENT SPECIFICATION:-
2.1 ABOUT EXISTING SYSTEM:-

 Presently people are making appointments manually.

 This is a time consuming process, patient has to physically go to the clinic in order to make appointment. Some clinics
provide the opportunity to make appointments by placing a phone call.
 But in this case, people are often left unattended.
 Each appointment booking is time consuming and the chances of knowing the exact availability of
doctor is very less.
 This process is very time consuming and the user has to wait a lot.
 There are also limitations in searching of proper and trustworthy doctors.
 By analyzing the existing system, some of its drawbacks are listed.
1. Time consuming.

2. Lack of efficiency.

3. Needs to be physically present at the clinic.

4. Can’t make appointments in advance for long intervals.

2
 2.2 NEED FOR NEW SYSTEM /FEATURES OF THE NEW SYSTEM:-

 I am providing a platform on which the users can search for the doctor online and place an
appointment on web application.

 This will enable making an appointment on the basis of mutual convenience.

 The proposed system will also manage patient’s case file.

3
 3.MINIMUM HARDWARE & SOFTWARE REQUIRMENT
3.1 CLIENT SIDE HARDWARE / SOFTWARE REQUIRMET:-

Hardware

Processor Intel Dual Core Processor

Ram 2GB or above

Hard Disk 250 GB or above

Software

Web browsers Windows explorer 7.0 or above,

Microsoft edge 42.0.2.3367 or above,

Google Chrome 22.0.1229.0 or above,

Mozilla Firefox 2.0.0.11 or above

4
3.2 SERVER SIDE HARDWARE / SOFTWARE REQUIRMET:-

Hardware

Processor Intel Dual Core Processor

Ram 2GB or above

Hard Disk 250 or and above

Software

Frontend Java 8u201

Backend MySql 5.5

Ide Eclipse 4.9, SQLyog 11.11

Framework Hibernate

5
 4.FUNCTION SPECIFICATION
4.1 USER OF THE SYSTEM:-

 Admin
 Doctor
 Patient

4.2 MODULES OF THE SYSTEM:-

6
5.SYSTEM FLOW CHART

7
6.ER DIAGRAM

8
 7.DATA FLOW DIAGRAM (DFD)
 Zero Level Data Flow

9
 First Level Data Flow(Admin)

10
 First Level Data Flow(Doctor)

11
 First Level Data Flow(Patient)

12
 8.DATA DICTIONARY
1) Table Name: - User_Master

Description: - Information about the user.

Primary key: - id

SR NO. FIELD DATA SIZE CONSTRAINT DESCRIPTION

NAME TYPE
1 id int 10 Primary key Defines the unique registration
id
2 email string 30 Unique and not Defines the unique Email id
null
3 fname string 15 Not Null Defines the name of the user

4 lname string 15 Not Null Defines the last name of the user

5 password string 15 Not Null Defines the password with help

of which user will login
6 role string 7 Not Null Describes the role of the user i.e
is the user doctor or patient

13
2)Table Name: - Doctor_Table

Description: - Information about the Doctor.

Primary key: - did

SR NO. FIELD DATA SIZE CONSTRAINT DESCRIPTION

NAME TYPE
1 did int 10 Primary Key Defines the unique doctor id

2 id int 10 Foreign Key Defines the unique registration

id
3 dimage string 255 Not Null This field stores the image of the
doctor
4 fname string 15 Not Null Defines the name of the doctor

5 lname string 15 Not Null Defines the last name of the

doctor
6 gender string 6 Not Null Defines the gender of the user

7 email string 30 Unique and not Defines the unique Email id

null
8 password string 15 Not Null Defines the password with help
of which user will login
9 aadhar no long 12 Not Null Defines the unique aadhar
number of the doctor
10 d_address string 50 Not Null This field stores the address of
the doctors residence
11 c_image string 255 Not Null This field stores the image of the
clinic
12 c_name string 30 Not Null Defines the name of the doctors
clinic
13 contact long 10 Not Null Defines the contact number of
the doctor
14 city string 15 Not Null Defines the city where doctor
resides
15 c_address string 50 Not Null This field stores the address of
the doctors clinic
16 landmark string 20 Not Null Defines a landmark with the
help of which the clinic can be
easily found
17 pincode long 6 Not Null Defines the unique pin code of
doctors clinic
18 city string 20 Not Null Defines the city where doctor
clinic is situated
19 state string 20 Not Null Defines the state where doctor
clinic is situated
14
20 highqualifi string 15 Not Null This field describes the highest
qualification of the doctor
21 mac string 255 Not Null This field stores the Masters
certificate of the doctor.
22 Bac string 255 Not Null This field stores the Bachelors
certificate of the doctor.
23 hsc string 255 Not Null This field stores the Higher
School Certificate of the doctor.
24 ssc string 255 Not Null This field stores the Secondary
School Certificate of the doctor.
25 others string 255 Not Null This field stores the masters
certificate of the doctor.
26 isactive string 10 Not Null Shows the status of the doctor
i.e. isactive or isnotactive
27 isverfing string 12 Not Null Shows is the doctor verified by
admin or not
28 otp long 10 Not Null Saves the otp send by the system
to the doctor

15
 3)Table Name: - Patient_Table

Description: - Information about the Patient.

Primary key: - pid

SR NO. FIELD DATA SIZE CONSTRAINT DESCRIPTION

NAME TYPE
1 pid int 10 Primary key Defines the unique patient id

2 id int 10 Foreign key Defines the unique registration id

3 fname string 15 Not Null Defines the name of the doctor

4 lname string 15 Not Null Defines the last name of the

doctor
5 email string 30 Unique and not null Defines the unique Email id

6 password string 15 Not Null Defines the password with help

of which user will login
7 contact string 10 Not Null Defines the contact number of
the patient
8 isactive string 10 Not Null Shows the status of the patient
i.e. isactive or isnotactive
9 isverified long 12 Not Null Shows the patient verified or not

10 otp long 10 Not Null Saves the otp send by the system
to the patient

16
4)Table Name: - Appointment_Table

Description: - Information about the Doctor.

Primary key: - appoint_id

SR FIELD DATA SIZE CONSTRAINT DESCRIPTION

NO. NAME TYPE
1 pid int 10 Foreign Key Defines the unique patient id

2 did int 10 Foreign Key Defines the unique doctor id

3 appoint_id int 10 Primary Key Defines the id of the

appointment generated
automatically by the system
4 appoint_time string 30 Not Null Shows the time on which the
appointment is scheduled
5 appoint_status string 30 Not Null Shows whether the
appointment has happened as
fixed

17
5)Table Name: - Prescription_Table

Description: - Information about the Doctor.

Primary key: -

SR FIELD DATA SIZE CONSTRAINT DESCRIPTION

NO. NAME TYPE
1 pid int 10 Foreign Key Defines the unique patient id

2 did int 10 Foreign Key Defines the unique doctor id

3 appoint_id int 10 Foreign Key Defines the id of the

appointment generated
automatically by the system
4 created_date string 30 Not Null Shows the date on which
Prescription is generated
5 attach_file string 255 Not Null Defines the type of file attached

6 pay_mode string 30 Not Null Shows the mode of payment i.e.

by cash or online transaction

18
 9.PROCESS DESCRIPTION
1) ADMIN:-

 Step 1:Start
 Step 2:Home Page
 Step 3:Manage Doctors
 Step 4:Manage Patients
 Step 5:View Appointments
 Step 6:Verify Doctor Registration
 Step 7:Stop

2) DOCTOR:-

 Step 1:Start
 Step 2:Register
 Step 3:Login
 Step 4:View Daily Appointments Booked
 Step 5:Manage Appointments
 Step 6:Makes Prescription
 Step 7:View Case History
 Step 8:Stop

3) PATIENT:-

 Step 1:Start
 Step 2:Search Doctor
 Step 3:Register
 Step 4:Login
 Step 5:Make Appointment
 Step 6:Make Appointment
 Step 7:Stop

19
 10.INPUT/OUTPUT DESIGN
1)Admin:-

 Sign In

 This is the first and foremost screen of the admin side.

 Admin has to log in to his dashboard to continue further.

20
 Home Page

 This is the first page that appears to the admin after he logins.
 From home page admin can see and manage the whole site.
 Other than that on the left side of the homepage there is a dashboard from where admin can handle
other things.

21
 Doctor verification

 When doctor fill the form send to his mail id, admin will get the notification in his dashboard, only
after verification done by admin the doctor can use the site.

22
 Admin View of Doctor Form

 This is the form the admin get to see when he gets the notification.
 All the data entered by the doctor is seen and verified by the admin.
 And after the verification by the admin only the doctor gets his rights.

23
 Doctor Table

 This is the doctor table. All the registered doctors can be viewed by the admin from here.
 Admin also has the rights and option to block or remove the doctor from the site.
 The doctor can change or update his details except his mail id and certificates.
 Once uploaded it can be altered only by the admin.

24
 Patient Table

 This is the patient table. All the registered patients can be viewed by the admin from here.
 Admin has the rights and option to block or remove the patient from the site.

25
 Appointment Table

 All the appointments booked on the site can be viewed by the admin from this table.
 Admin can only view this table, no editing can be done by the admin.

26
2)Doctor:-

 Registration

 This is the first page the new doctor who want to register on the site needs to visit.
 The registration page for the patient and the doctor are same. At the time of registration user has to
just select the dedicated radio button.
 After the initial registration the doctor will get an email in which there will be an link for the form for
further details of the doctor.

27
 Doctor Registration Form

 The complete details of the doctor is collected in this form including his certificates.
 After filling the details completely the doctor will click on the submit button given below the form.
 When the submit button is clicked the data is send to the admin for the verification and the doctor
will get an mail in which he will be asked to wait for seven working days and the hr department will
get to him after verifying his details.
 Only after getting an confirmation mail from the admin the doctor can log on to the site as an official
doctor of the site.

28
 Doctor Login

 The login page for the doctor and the user are the same. The respected user has to just select the radio
button given at the starting of the login form.
 By entering the correct mail id and password doctor can login into his portal from where he is going
to control his appointments and patients.

29
 Otp

 At the time of first login the doctor has to enter an otp send to his registered mail id.

30
 Home Page

 This is the homepage of the doctor .

 At homepage there is a to do list where doctor can note down important thinks he needs to remember
that day.
 Other than that there will be an appointment list which shows the appointments taken by the patients
for that day.
 The doctor can update the time of the appointment or he can cancel it if he wants to.

31
 Appointment Table

 The doctor can see all his previous and current appointments from here.

32
3)Patient:-

 Home Page

 This the homepage or we can say the first page user will see.
 The user can search doctor from this page according to his searching choice like name, location and
speciality.

33
 Categories

 From category section the user can find doctors according to their need.

34
 Contact Us

 If there is any issue or complaint user can contact the admin from this page.

35
 User Registration Form

 After viewing the site when the user want to book an appointment if he is nota n user then he has
to first of all register himself.
 Only after registering himself he can go further.

36
  Login

 After successfully registration the user is redirected to the login page.

 Here the user will login using his registered email id and password and only after that user can book
an appointment with the doctor.


37
 Book Appointment

 After finding the required doctor from category user can see the further details of the respected
doctor and after getting full convenience about the doctor user can book an appointment.

38
 At the time of booking the user has to select date and time he intended to book an appointment.
 If the time slot he wish to book is already booked he will not be able to book an appointment at
that time.
 He will be shown the next available time of appointment.

39
 11.TESTING

No. Test Case Expected Actual Pass/Fail

Cases Type Result Result

1. Registration 1.Email Email Fields Fill proper and valid Pass
should not be email id into email
Mail Field Validation NULL field

No. Test Case Expected Actual Pass/Fail

Cases Type Result Result

2. Registration 1.Password Confirm Fill the confirm Pass

Password Fields password field with
Password Field Validation should not be same value as entered
NULL in password fiels

40
1)REGISTRATION PAGE EMAIL VALIDATION:-

 The email field shouldn't be empty. This field is mandatory or else the user will not be allowed to
register on the site.

41
 After filling the mandatory email field the further registration process is allowed.
 So the result of the test is pass.

42
2)REGISTRATION PAGE CONFIRM PASSWORD VALIDATION:-

 Same as email the confirm password field is also mandatory. This field is mandatory so that the site
can confirm the password entered by the user.
 This mandating can also help the user to know his mistake in entering password if any.

43
 After filling both the password field the user can complete his registration process.
 The final test on the registration page is successful.

44
 12.FUTURE ENHANCEMENT
 At present there is no facility of providing medicines to the patients.
 In future we can provide a system in which the user can directly send the prescription received from
the doctor directly to the medical shop he wish to buy medicines from.
 And the medicines will be delivered to his residence within shot period of time.
 Other than that we can also provide home visit facility to the patients by doctors in the site.

45
 13.CONCLUSION

 By building a doctor finder web application where searching of the doctor according to our need and
locality wise makes finding a good doctor an easy task.
 And the features like booking an appointment online with the respective doctor you wish to meet
saves a lot of time.
 This also gives us the convenience of waiting very less time at the clinic.
 Also the case history and prescription is send directly send to the registered mail address of the
patient this reduces the stress of keeping both of the things safely.
 In short in today's fast life this web application helps us to save lots of time that is spend in waiting
at doctors clinic.
 It also reduces the stress suffered by the patient he feels at the time of waiting in his ill condition.
 The prescription can be downloaded anytime and from anyplace whenever it is needed by the patient.
 Thus this web application will be a great help for the patients.

46
 14.BIBLIOGRAPHY
 Books

 2nd Edition, Head First Java by Kathy Sierra & Bert Bates, O Reilly'

 4th Edition, Think Java: How to Think Like a Computer Scientist by Allen Downey and Chris
Mayfield, O Reilly'

 Links
 https://www.academia.edu/32409989/Clinic_Appointment_System
 Stack Overflow (http://stackoverflow.com).
 Tutorials Point (http://tutorialspoint.com
 Wikipedia (http://en.wikipedia.org).
 GitHub (http://github.com).
 JQuery (http://jquery.net)

47