INTRODUCTION

This application is designed and developed in such a way that user can easily operate it
without any problem. The application “DrNearMe” is a convenient way of taking doctor
appointment in an easy manner. The design of the application is done in such a way that the user
would not have any problem in operating it even for first time. The design is done with the
common user in mind and it hardly needs any modification.
This application is created to reduce the human efforts by taking doctor appointment
online. If the patient not using this application he/she must go to the hospital or clinic to check; is
there any available doctor at the time. If the doctor is available, he/she can take appointment
otherwise he/she must leave or wait for amount of time till the doctor come or become available.
Another problem is that the patient doesn’t know that the hospital or clinic he is going has the
specific doctor that he/she need. Also, the patient must record the previous appointment he/she
booked and this is not an easy job.
By using this application, the patient can check the nearest doctor to him/her with the
needed specification. The patient easily can check the doctor is available or not; if available is
which time and on base of the doctor scheduling and himself/herself can take appointment. This
application helps the user to check the previous appointment that he/she booked and easily can
manage them. If the doctor set another appointment for the patient in another date it will get
automatically set in the user’s application and will notify the user one day before the
appointment and the user also can set reminder for himself/herself.
The application would be trendsetter in its own way because of its simplicity and the hard
work put behind it by the developers to make it such a user efficient application. We try to make
this application as much as user friendly for user to use it easily for the first time.
This project was developed in order to provide a good and efficient application and thus
it has generated and has become successful in achieving the aim since the application provide
basic functionality to the user.
 PROBLEM DEFINITION

Avoid the time-consuming process of going to the hospital or clinic for taking doctor
appointment if the doctor is available for the date that the patient wants. It will help you to
manage your time by checking available time for the doctor that you want or also can cancel the
appointment. And the data can be managed on the real time database with firebase service.

The management faces many problems in manual system Like

1. The patient must go to hospital or clinic for taking appointment.

2. Maybe the specific doctor is not available or he/she on leave.

3. Storing the appointment records is difficult.

4. The overall process manually.

5. Time consuming process.

 EXISTING SYSTEM

In the existing system the patient needs to visit the doctor for booking we need to wait
and the booking will be done manually so to maintain everything is always a problem. there is a
huge trend of private hospitals. Doctors run their own private clinics and consult patients during
the evening or any time of the day depending on their availability. Some are popular and known
to all while some are known by few people. This situation proves to be a challenge for new
practitioners as they are known to very few people even if they have a good academic
background. On the other side, patients also face difficulty in finding and choosing a nearby
doctor. Unscheduled appointments, long waiting lines and keeping medical files in physical form
are also the common problems faced by the people/ patients.

Determination of Problem:

1. Challenge for new practitioners: Starting a private clinic can be a challenge for new
practitioners. For example, if a new doctor wants to open his clinic there is no platform exist, by
which or from where people can get to know about his clinic.
2. The problem for a new individual in a city: In the same way, the same problem goes
for any person new to the city as he is unknown, who is the best or closest doctor/clinic to go for
a medical checkup.
3. Long waiting lines: To get doctor's consultation, patients come twice to the clinic once
for taking the appointment and second time for the checkup. Some patients visit the doctor
without any prior appointment resulting in a long waiting time. There is also a possibility that
they don't consultation by the doctor even after a long waiting line.
4. Managing paper-based medical files :Patients must carry their medical related report or
files every time they visit a doctor. And sometimes they lost their files too.
 PROPOSED SYSTEM

Proposed system software would be miniature of “DrNearMe” website. The user of the
application can easily be taking doctor appointment at any time which he/she is comfortable. The
proposed system full computerized. The user also can cancel the appointment and if the doctor
schedule suddenly changes, the user will be notifying by notification and if he wants the
appointment will change as the user wants.
The information and notification can be easily being accessed by one touch on android
application. The application provides notification to patient about next appointment if the doctor
assign next appointment.
The user can check the history of his previous appointments and can directly taking
appointment form the previous appointment at history. The user also can take appointment for
another his/her relative.
If the doctor assign for patient another appointment it will automatically set for the user
and one day before the date of appointment, the application will notify the user about the next
appointment; the user also can set reminder for himself/herself.
 NEED OF PROPOSED SYSTEM

The need of proposed system will avoid the problems of existing system.and also get a new
system of managing information under the online appointments.

There are various requirements of users, these all requirements are fulfilled in the proposed
system.

 The application must show all the nearest doctor form current location patient.

 User can filter all the available doctor by their category and the range.

 The user can book doctor appointment according the scheduling that specifies
application.

 User can cancel the appointment.

 If the doctor cancels the appointment user must get notified.

 User can set reminder for the next appointment.

 User must notify if the doctor changes the appointment scheduling.

 User can check all the previous appointment that he/she booked.
 SCOPE OF SYSTEM

Proposed system software would be miniature of “DrNearMe” website. The user of the
application can easily be taking doctor appointment at any time which he/she is comfortable. The
proposed system full computerized. The user also can cancel the appointment and if the doctor
schedule suddenly changes, the user will be notifying by notification and if he wants the
appointment will change as the user wants.

The information and notification can be easily being accessed by one touch on android
application. The application provides notification to patient about next appointment if the doctor
assign next appointment.

The user can check the history of his previous appointments and can directly taking appointment
form the previous appointment at history. The user also can take appointment for another his/her
relative.

If the doctor assign for patient another appointment it will automatically set for the user and one
day before the date of appointment, the application will notify the user about the next
appointment; the user also can set reminder for himself/herself.
 HARDWARE AND SOFTWARE SPECIFICATION

Hardware Specification:

Processor : Core i3
RAM : 4 GB OR Above
Hard Disk : 500 GB OR Above
Net Connection : Any

Software Specification:

Software : NetBean

Operating system : Windows XP, 7, 8, 8.1, 10 etc

Front End : HTML,CSS,JSP

Back End : MYSQL

 FACT FINDING TECHNIQUES

To study the system you need to collect facts. Facts expressed in quantitative form can
termed as data. Success of any requirement investigation depends upon availability of accurate
and reliable data. These depend on the appropriateness of the method chosen for data collection.
The specific methods used for collecting data are called fact-finding techniques.
Following are the methods of fact finding techniques:

i) Interview:
Interviews are held to collect the information about the existing system among various
ideas with many people. Sudden feedback is possible due to face-to-face communication with the
people. Problem is solvable in minimum period of time Due to direct contact with people.

ii) Questionaries:
Some people hesitate to tell about the problems occurred into the existing system this
problem can solve using this fact-finding technique. There are various people’s questions
presents that’s solving all the information about existing system.

iii) Observations:
We carried out observation under organization. He has good technique to get information
about the existing system. The user’s specifications were taken into consideration.
 FEASIBILITY STUDY

A feasibility study was an evaluation of the proposed designed to determine the difficulty
in carrying out a designed task. Generally, a feasibility study precedes technical development
and project implementation.

Problem Definition:
Avoid the time-consuming process of going to the hospital or clinic for taking doctor
appointment if the doctor is available for the date that the patient wants. It will help you to
manage your time by checking available time for the doctor that you want or also can cancel the
appointment. And the data can be managed on the real time database with firebase service.

Economic Feasibility:
To develop the proposed system, it need no extra facilities and devices. All
dependencies are satisfied from the open source project. All tools used are free, open source and
the programming language is java and android and hence its development is economically.

Technical Feasibility:
Proposed application is technically feasible because the proposed application requires
only those H/W and S/W tools are available in the android device. It requires the installation of
application which can be done for free. More over expandability will be maintained in the new
system. New module can be added later on the application, if required in the future. Additionally,
the application has user friendly web page and screen.

Behavioral Feasibility:
Behavioral feasibility determines how much effort will go in the proposed information
application, and in education and training the users on the new system. Since the user interface is
very simple and easily understandable, no training is required for using this application.
ENTITY RELATIONSHIP
DIAGRAM
 ER DIAGRAM

1 M feedbacks
Admin view
M
view M
M Locations
Schedule
give
M
using
add

M
M M
Doctors search Patients

M M M M M

treat
take

M
Appointments

Generate M
e

M views
Reports

M
gives
Pay
M M
M
View by Receptionists

M
to Payments
NORMALIZATION OF
DATABASE
 DATA DICTIONARY

1. Doctor Details:

Sr.No Fields Data types Constraints Description

1 Doctor_Id Integer Primary key Doctor id

2 Doctor_Name Varchar(MAX) Not null Name of doctor

3 Doctor_Username Varchar(MAX) Not null Doctor username

4 Password Varchar(MAX) Not null Doctor password

5 Clinic_Name Varchar(MAX) Not null Name of clinic

6 Clinic_Address Varchar(MAX) Not null Address of clinic

7 Personal_Phone_No Integer Not null Phone no

8 Clinic_Phone_No Integer Not null Phone no of clinic

9 Clinic_Landline_No Integer Not null Landline no of clinic

10 Doctor_Email_Id Varchar(MAX) Not null Email id of doctor

11 Doctor_Qualification Varchar(MAX) Not null Qualification of doctor

12 Doctor_Experience Varchar(MAX) Not null Doctor experience

14 Gender Varchar(MAX) Not null Gender of doctor

15 Address_Coordinate Varchar(MAX) Not null Address of doctor

16 Category_Name Varchar(MAX) Not null Name of category

2. Schedule_Details:
Sr.No Fields Data types Constraints Description

1 Schedule_Id Integer Primary key Schedule id

2 Doctor_Name Varchar(MAX) Not null Name of doctor

3 Available_Days Varchar(MAX) Not null Doctor’s available days

4 Start_Time Time Not null Start time of doctor

5 End_Time Time Not null End time of doctor

6 Per_Patient_Time Time Not null Time of per patient

3. Appointment_Details:

Sr.No Fields Data types Constraints Description

1 Appointment_Id Integer Primary key Appointment id

2 Patient_Name Varchar(45) Foreign key Patient name

3 Doctor_Name Varchar(45) Foreign key Doctor name

4 Appointment_Date Date Not null Date of appointment

5 Appointment_Time Time Not null Time of appointment

4. Feedback_Details:

Sr.No Fields Data types Constraints Description

1 Feedback_Id Integer Primary key Feedback id

2 Patient_Name Varchar(MAX) Foreign key Patient name

3 Doctor_Name Varchar(MAX) Foreign key Doctor name

4 Feedback Varchar(MAX) Not null Feedback

5. Payment_Details:
Sr.No Fields Data types Constraints Description

1 Payment_Id Integer Primary key Payment id

2 Patient_Name Varchar(MAX) Foreign key Patient name

3 Doctor_Name Varchar(MAX) Foreign key Doctor name

4 Payment_Date Date Not null Date of payment

5 Card_Cheque_No Integer Not null Card or cheque no

6 Receipt_No Integer Not null Receipt no

7 Payment_Paid Varchar(MAX) Not null Paid payment

8 Payment_Remaining Varchar(MAX) Not null Remaining payment

6.Department_Details :

Sr.No Fields Data types Constraints Description

1 Department_Id Integer Primary key Department id

2 Department_Name Varchar(MAX) Not null Department name

3 Department_Details Varchar(MAX) Not null Department details

UML DIAGRAMS

Class Diagram
 Patient Doctor Report

+id: int +Did: int +Pid: int

+name: varchar(25) +Dname: varchar(25) +Did: int

+address: varchar(25) +Daddress: varchar(25) +date: varchar(25)

1
+mbno: varchar(25) +speciality: varchar(25)

disease: varchar(25) +Submit () +Submit ()

+Submit () +Cancel () +Cancel ()

+Cancel () 1…*
manage 1
1
1
view
Admin

take +username: varchar(25)

1 1
+password: varchar(25)
Appointment Receptionist

+Srno: int +Rid: int

+Submit ()
+Pid: int +Pid: int
+Cancel ()
+Departname: varchar(25) +Did: int
1
+Dname: varchar(25) +Aid: int
*...1 manage
+Adate: varchar(25) +Submit ()

+Cancel ()

+Submit () Payment
+Cancel () +pid: int

+Did: int

+paymentmode: varchar (25)

1 +Submit ()
Pay
+Cancel ()
Object Diagram
 Patient Doctor
Report
+id : 11 +Did : 101
+Pid: 11
+name : Ramesh +Dname : dr. shukala
+Did: 101
+address : pune +Daddress: pune
+date: 25/04/2019
1
+mbno : 913010078 +speciality: general serj

disease :cancer +Submit();

+Submit ();
+Submit(); +Cancel();
+Cancel () ;
+Cancel();
1.. *
1
1 manage
view
1
Admin
take
1 1
+username: admin
Appointment Receptionist
+password: admin
+Sino: 111 +Rid: 2
+Submit ()
+Pid: 11 +Pid: 11
+Cancel ()
+Departname: neurology +Did: 101
1
+Dname: dr.shukala +Aid: 111
*…1 manage
Use Case Diagram
+Adate :25/04/2019 +Submit ()

+Cancel ()

+Submit () Payment

+Cancel () +pid: 11
Registration
+Did: 101

+paymentmode: cash
Login
Pay +Submit ()

+Cancel ()
Search
LoginLocation
Login Doctor

t
Add schedule
Search Location

TakeLogin
Appointment
 Admin

Patient

Activity Diagram
Start
Start

Registration

Login

No
verify Enter username & password

Doctor Admin Yes

Patient
 Add schedule Manage doctor Search location

Give appointment Update data Take appointment

Attend patient
Collect report
Attend patient View feedback

Pay payment
Generate report

Give feedback
View all appointment

View payment
status

View feedback
Sequence Diagram
Stop

: : Admin : Doctor : Receptionist : Patient : Database

Manage

Register to

Login
Verify

Valid
Check
Add schedule Store schedule details

Manage Take appointment

Give appointment
 Give Report
Store report details
De
View report

Give feedback

Store feedback
Pay payment

Store details

View feedback

View feedback

Component Diagram

DataBase

System
DNM.war
 Login.Jsp Registration.
Jsp

Admin Doctor Patient

Collaboration Diagram

1.1 Login Successfully

Admin System
1. Login
2. Store Data

4. Registration
5. Login
6. Add schedule
7. view feedback
3. Manage
4.1 Registration
Successfully
 8. Manage patient

Doctor Patient

9. Take appointment

10. View schedule

11. Collect Report
12. Pay Payment
13. Give Feedback

Deployment Diagram

Browser
Web Server

HTTP
chrome Apache

User

TCP/IP

Database Server

Mysql
INPUT/OUTPUT SCREENS
Department_Form :
Department_Table:

Doctor_Form:
;

Doctor_Table:

Patient_Form:
Patient_Table:
Appointment_Form:
Payment_Form:

Schedule_Table:
Feedback_Table:

LIMITATIONS
The limitation of the system is:

 The system required internet to connect to the server for searching for doctor.
 The user must check the application before going to the doctor because maybe the doctor
canceled the appointment.
 The user can find only those doctor in the application who they register to the DrNearMe
website.
 The user must have android phone and the version must be at least 5.0(Lollipop).
 Conclusion

The DrNearMe application is a good choice for every patient that they want to book
appointment online. The application provides for them the facilities of searching, booking,
viewing the pervious appointment, setting reminder and booking appointment for friend or
family with this application.
REFERENCES

WEB REFERENCES