PROFORMA FOR THE APPROVAL PROJECT PROPOSAL
(Note: All entries of the proforma of approval should be filled up with appropriate and complete
information. Incomplete proforma of approval in any respect will be summarily rejected.)
PNR No:-2018016400786233 Rollno:- 44
1. Name of the Student:-
Prajapati Sudheer Kapildev
2. Title of the Project :- Online Eye clinic
3. Name of the Guide :- Sweta Bhandari
4. Teaching experience of the Guide
5. Is this your first submission? Yes No
Signature of the Student Signature of the Guide
Date: ………………… Date:……………….
Signature of the Coordinator
Date: …………………
1
ONLINE EYE CLINIC
A Project Report
Submitted in partial fulfillment of the
Requirements for the award of the Degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)
By
Prajapati Sudheer
44
Under the esteemed guidance of
Ms. Sweta Bhandari
Assistant Professor
DEPARTMENT OF INFORMATION TECHNOLOGY
GURU NANAK COLLAGE
(Affiliated to University of Mumbai)
MUMBAI, 400037
MAHARASHTRA2019-2020
GURU NANAK COLLAGE
2
(Affiliated to University of Mumbai)
MUMBAI-MAHARASHTRA-400037
DEPARTMENT OF INFORMATION TECHNOLOGY
CERTIFICATE
This is to certify that the project entitled, "ONLINE EYE CLINIC", is bonafied work of
SUDHEER PRAJAPATI bearing Seat.No:(3103337) submitted in partial fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from University of Mumbai.
Internal Guide Coordinator
External Examiner
Date: College Seal
3
Abstract
Doctor Patient Communication System (DPCS) is an Android app which sets up online
communication between a doctor and a patient. This app is helpful to patients to ask
questions and state their concerns to doctors regarding their health condition. This app
will facilitate the patients to interact with doctors without making any physical
appointments, but the patients are restricted to only one message per day before receiving
a reply. If the patient gets a response from the corresponding doctor, the patient is
allowed to send another message. In addition using this app, the patient can make an
appointment to meet the doctor in clinic/hospital. DPCS app would also facilitate the
patient’s pharmacy selection to pick up the medication. Similarly, this app is beneficial to
doctors by providing the following functionalities: patient interaction through
messaging, sending prescription to pharmacies, confirming appointments, information
sharing with other doctors, and patient referrals. Unlike other similar kinds of apps in the
android play store, DPCS has unique features such as issuing online prescription to
patients, referring patients to a specialist, sending health tips to patients, and effectively,
reducing the cost of customer service and providing a vrital communication link between
doctors and patients.
ACKNOWLEDGEMENT
4
After the completion of this work, words are not enough to express feelings about all those who
helped us to reach goal.
It’s a great pleasure and moment of immense satisfaction for me to express my profound
gratitude to Project guide “PROF.SWETA BHANDARI” whose constant encouragement
enabled us to work enthusiastically. His perpetual motivation, patience and excellent expertise in
discussion during progress of the project work have benefited me to an extent, which is beyond
expression.
I would also like to give our sincere thanks to Head of Department PROF.HARPREET
SAINI from Department of Information of Technology, SIWS COLLEGE and Project guide
“PROF. SWETA BHANDARI” for their guidance, encouragement and support during a project.
DECLARATION
5
I here by declare that the project entitled, “ONLINE EYE CLINIC” done at place where the
project is done, has not been in any case duplicated to submit to any other university for the
award of any degree. To the best of my knowledge other than me, no one has submitted to any
other university. The project is done in partial fulfillment of the requirements for the award of
degree of BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) tobe submitted as
final semester project as part of our curriculum.
PRAJAPATI SUDHEER
TABLE OF CONTENTS
1:Introduction…………………………………………………………………………….8
6
1.1:Banckground…………………………………………………………………………8
1.2:objectives…………………………………………………………………………….8
1.3:Purpose and Scope……………………………………………………………………8-9
2:System Analysis………………………………………………………………………..12
2.1:Existing System……………………………………………………………………….12
2.2:Proposed System………………………………………………………………………12
2.3:Requirement Analysis………………………………………………………………..12-13
2.4:Hardware Requirement………………………………………………………………13
2.5:Software Requirement………………………………………………………………13-14
2.6:Justification of selection of technology…………………………………………….14
3:System Design…………………………………………………………………………15
3.1:Module Division……………………………………………………………………..15
3.2:Database……………………………………………………………………………..16-19
3.3:Diagram………………………………………………………………………...20-31
4:Impementation and Testing……………………………………………………………32
4.1:code…………………………………………………………………………………32-43
4.2:Testing Approach……………………………………………………………………44
5:Result and Discussions………………………………………………………………..45-51
6:Conclusion …………………………………………………………………………..52
7:References……………………………………………………………………………. 53
CHAPTER.1
7
INTRODUCTION
1.1.Background:
As the name suggests, the Online Eye Care System is an application that will
help in maintaining the details in the eye care clinic with great ease. The manual operations can
also be done through this automated system. It will also help in maintaining the patients records
without any difficulty. The treatment records can also be got through this application with great
ease.
The user interface must be simple and easy to understand even by the common man. This will be
one of the applications that will help in maintaining the details of the treatment that are given to
the patients just with one mouse click. This will be one of the interesting applications that one
can work on.
1.2Objectives of the Project: The objective of “Online Eye Care System” is to provide a system
where the user will feel easy to give an eye check up, order for specs or lens through online. The
registered user has more benefits because of the system.
The ordered lens or spectacles will be delivered to the customer’s home address and they pay
either through online or cash on delivery. Paper consumption and time consumption is less by
using this systematic software. Database is used to store the data’s and is cleared periodically.
The system is free of bugs and is very easy to use. The system directs the user to carry on with
the next step just by a few simple help lines.
1.3.Purpose:
This Document includes software requirements for the “eye care system” Project. The
purpose of this document is to detail the user requirements for all the functionality in “eye care
system”. This document is meant to serve as a guide to the developers and users.
The purpose of the requirement document is to specify and provide all the information
required to design, develop and test the system. This document ensures that the person reading the
document understands what she/he is looking for.
1.3.Scope:
8
This project is useful for the users to book for an appointment for an eye check
up through the system rather than manually. The appointment details will be booked and on the
prescribed date they can directly visit to the clinic. Ordering for lens or spectacles is easy just by
providing the power of lenses
1.4.Overall descripion:
There are three types of users in this system.
• Administrator
• Doctor
• Patient
Customer: First the customer needs to register to the website. After the registration customer
can login to the site. Patient can view his appointment details and product order details in the
patient dashboard. Patient can book appointment and he has option to cancel his appoinement.
Admin: In the Admin dashboard admin can view order details. Administrator can update his
profile and he can change his existing password. Admin can view patient details and doctor
details. Admin can set appoint schedule for patient and he can cancel the appointment.
Administrator can add branch details, Other admin records, Doctor details, Patient details and
product details. Admin can manage product inventory details.
Doctor: In the doctor panel doctor can view his appointment details. In the doctor dashboard he
can update his profile and doctor can change his password. Doctors can view appointment
details. and he can place order for patients.
The functions that are included in the online eye care system application are as follows:
• Appointment details: The appointments that are placed by the patients on the particular day
and time can be recorded through this application.
• Patient details: The details of the patients like name, address, treatment details and the other
medication details can be maintained with great ease.
• Eye problems and diseases: The eye problems and the related diseases that a patient has can
be maintained through this application.
9
• Treatment details: The treatment details and the medications that are given to the patients can
be obtained in just one mouse click without any difficulty.
• Medical problem: The medications that are given to the patients for the particular eye
problem can also be entered through this application.
• Reports: The daily, weekly or monthly reports of the patients can be generated through this
application.
• Billing details: This will help in maintaining the billing details like the fees of the doctors can
be maintained with great ease through this application.
1.4.1.Performance Requirements:
Performance requirements define acceptable response times for system functionality.
• The system is supposed to be having good memory space and RAM should be Above 256 MB
preferably.
• The sound card and graphics card will have to be of good quality and capacity.
• The load time for user interface screens shall take no longer than three seconds.
• The log in information shall be verified within three seconds.
• Queries shall return results within three seconds.
1.4.2.Safety Requirements:
• In case the customer forgettheir password, they can recover the password in the Forgot
Password panel
• The password stores in the database in the format of encrypted password.
8.2.Security Requirements:
• Only authenticated users can access this system.
1.4.3.Software quality attributes:
10
• Reliability:
This system is designed to have very simple database just to cater the exact need of
“online eye clinic”. It is tested for all the constraints at development stage.
• Availability:
This system will only available till the system on which it is installed is running.
• Security:
This system is provided with authentication without which no user can pass. So only the
legitimate users are allowed to use the application. If the legitimate users share the
authentication information then the system is open to outsiders.
• Maintainability:
There is maintenance required for the website. The database is provided by the
Administrator as well as the end-use.
• Portability:
The system works anywhere with the internet connection.
CHAPTER.2
System Analysis
11
2.1.Existing System:
Complexity in managing the data related to the eye problem, treatment , etc.
2.2Proposed system:
The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.
• Reduce complexity in managing the data related to the eye problem, treatment , etc.
• Current system provides different access levels for security.
• Rich user interface is provided in order to interact with application.
• Patients can eassly take appointment This system save the time of patients
2.3.Requirement Analysis:
A clinic may be defined as a place of professional practice with facilities for
outdoor consultation and treatment during scheduled hours by one or more physicians and staff
and equipment essential for the services provided. It may or may not have the facilities for
limited investigations specific to the scope of services provided.
A large percentage of the population, in rural as well as urban areas, is dependent on private
clinics and, therefore, the quality of healthcare services provided by them is very important. At
present there is no system of registration of private clinics by health authorities in India. The
Clinical Establishments (Registration and Regulation) Bill, 2007 is still pending in the
parliament.
Presently, the operation of private clinics is being governed by the Indian Medical Council
(Professional Conduct, Etiquette and Ethics) Regulations 2002 and certain other legislations as
outlined below.
1. Registration/Requirement of Licenses
• Registration with health authorities is not mandatory for private clinics but the clinic will
be subject to inspections in case of any complaints. If and whenever the Clinical
Establishments (Registration and Regulation) Bill, 2007 is passed by the parliament and
implemented by the states, registration of all clinics (Private/Public) of all systems of
medicine will become mandatory;
12
• Registration with the municipal authorities (Delhi Shops and Establishments Act, 1954);
• Recognition for usage of narcotic drugs (Delhi Narcotic Drugs (Amendment) Rules,
2002;
• Authorisation for generation of Bio-Medical Waste, if treating 1,000 or more patients per
month;+
• Permit for procurement/usage of spirit;
Registration under the Medical Termination of Pregnancy (MTP) Act 1971, the Pre-Natal Diagnostic
Techniques (PNDT) Act, 1994, as applicable
2.4.Hardware Requirements:
• Operating System: Windows XP, 7 OR 8
• Processor: Intel Core Duo 2.0 GHz or more
• RAM: 1GB or more
• Hard Disc: 80GB or more
• Monitor: 15 inches CRT or LCD Monitor
• Keyboard: Normal or multimedia keyboard
• Mouse: Compatible Mouse
2.5.Software Requirements:
• XAMPP ,WAMPP
• APACHE Server 5.4.19
• MySQL Server 5.4
• Adobe Dreamweaver CS 6.0
• Browser: Google Chrome, Mozilla Firefox
2.6.Justification of selection technology:
13
This technology is very easy to use and it is protable technology .This technology solve
the problem of patient and save the times of the patient. Patient can take appointment our doctors
and patient can also take the our medicine .This site solve the many problem of the patient.
CHAPTER.3
System Design
3.1.Modules Division:
• Customer account module
• Appointment details module
• Patient module
• Eye problems and diseases module
• Treatment details module
14
• Medical problem module
• Report module
• Billing details module
3.2Database table
Structure of Table “admin”:
Field Name Field Type Size Description
admin_id Int 10 Admin ID
admin_name Varchar 25 Admin Name
login_id Varchar 20 Login ID
Password Varchar 50 Password
Status Varchar 10 Status
Structure of Table “appointment”:
15
Field Name Field Type Size Description
appointment_id Int 10 Appointment ID
appointment_type Varchar 25 Appointment type
appointment_date Date Publishing date of the appointment
Title Varchar 100 Title of the appointment
appointment_description Text 100 Description of the appointment
16
Field Type
Structure of Table “branch”:
Field Name Size Description
branch_id Int 10 Branch ID
branch_name Varchar 25 Branch_name
Address Varchar 100 Address
Structure of Table “doctor”:
Field Name Field Type Size Description
doctor_id Int 10 Doctor ID
doctor_name Varchar 10 Doctor name
doctor_type Varchar 10 Doctor ID
City Varchar 25 City
Structure of Table “Patient”:
1
7
Field Type
Field Name Size Description
patient_id 10 Patient ID
Int
patient_name Varchar 25 Patient name
Description Text Description
Address Varchar 100 Address
Structure of Table “product”:
Field Name Field Type Size Description
product_id Int 10 Product ID
seller_id Int 10 Seller ID
category_id Int 10 Category ID
Product_type Varchar 25 Product Type
Title Varchar 100 Title
Structure of Table “doctor_bill”:
1
8
Field Type
Field Name Size Description
product_purchase_bill_id Int 10 Product purchase bill ID
patient_name Varchar 25 Patient Name
patient_contact_number Varchar 15 Patient Contact Number
purchase_date Date Purchase Record
Structure of Table “order”:
Field Name Field Type Size Description
order_id Int 10 Order ID
product_id Int 10 Product ID
order_date Date Date of order
order_time Time Time of order
order_amt Float 10,2 Amount of order
quantity Float 10,2 Quantity of order
1
9
20
3.3.Diagram
Gantt chart
A Gantt is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start finish dates of the terminal elements and summery elements of a
project. Terminal elements and summary elements comprises the work breakdown
structure of the project.
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements
of a project.
Although a Gantt chart is useful and valuable for small projects that fit on a single
sheet or screen, they can become quite unwieldy for projects with more than about
30activities. Larger Gantt charts may not be suitable for most computer displays. A
related criticism is that Gantt charts communication relatively little information per
21
unit area of display. That is projects are often considerably more complex than can
be communicated effectively with a Gantt chart.
ER diagram
22
ER diagram: This is ER diagram in that four attributes location , user , purchase and upload .Its
work like that user first login the web application if have account either register then after user
can purchase the product or he can also upload our product of this site .Relation between user
and purchase is many to many similler to upload
Dataflow diagram
23
Sequence diagram
24
Sequence diagram:In this diagram have user , system ,and database in this diagram
user first create account or login verify by the database if it is valid then move
further.then system request option to related site .user can view card or news and
user purchase product then system again request the option of the payment (card or
cash) .user pay with our choice then after system update the database and generate
the bill.
Activities diagram
25
Activity diagram: In this diagram customer login the our account if the id is in invalid then it is
directly exit if valid id then he can move further .user saerch or view card then he can upload our
product or purchase the product .If user purchase the product then he can pay with card or cash
if payment operation faild then it return to the payment module if valid then system update the
database and generate bill the process is complete.
Use case diagram
26
Use case diagram:there three module admin(administator), customer and seller.In that admin create
our account and admin can view the all module of the project and he can also able to make any
changes in project and other customer can view the all module but he not able to make any
changes in project(web site) but he able to purchase product and other things etc. he can also
contact us .seller can upload our product and sell the our product through this site but he first
create our account on the site.
Class diagram
27
Class diagram:In this diagram of class diagram I define user , patient , report ,appointment and
billing.user have name ,id ,password, address and email and function is login and logout.
patient have patient_id, ,patient_name ,patient_type and operational function is Add and Delete
user have user_id, ,user_name ,user_password, user_address, user_mail and operational function
is Add and Delete
Flow chart d diagram
28
State chart diagram
29
Collaboration diagram
30
Component diagram
31
Component diagram:In this diagram have user , system ,and database in this diagram user first
create account or login verify by the database if it is valid then move further.then system request
option to related site .user can view card or news and user purchase product then system again
request the option of the payment (card or cash) .user pay with our choice then after system
update the database and generate the bill.
Deployment diagram
32
Deployment diagram:In this diagram have user , system ,and database in this diagram user first
create account or login verify by the database if it is valid then move further.then system request
option to related site .user can view card or news and user purchase product then system again
request the option of the payment (card or cash) .user pay with our choice then after system
update the database and generate the bill.
Block diagram
33
.
34
CHAPTER.4
Implementation and Testing
4.1Code: <?php
include("includes/header.php");
include("includes/conn.php");
if(isset($_POST['submit']))
$dt=date("Y-m-d");
$sql="INSERT INTO patient (pat_name, email_id, password,gender, contact,created_at)
VALUES
('$_POST[fname]
$_POST[lname]','$_POST[emailid]','$_POST[password]','$_POST[gender]','$_POST[contact]','$
dt')";
if (!mysqli_query($con,$sql))
{ die('Error: ' .
mysqli_error($con));
if(mysqli_affected_rows($con) == 1)
35
echo "<script>alert('Patient registered successfully..');</script>";
echo "<script>window.location='login.php';</script>";
?>
<div id="templatemo_main">
<div id="sidebar" class="float_l">
<div class="sidebar_box"><span class="bottom"></span>
<h3>Existing Users</h3>
<div class="content"> <a href="login.php"><img src="images/login.jpg" width="222"
height="167" /></a> </div>
</div>
</div>
<div id="content" class="float_r">
<h2>Patient Registration</h2>
<p> <?php if($rcsucc
!= "") { echo $rcsucc;
} else
36
?></p>
<script type="application/javascript" > function
validation()
//Validation for Email ID em =
document.reg.emailid.value; pos1 =
em.indexOf("@") pos = em.indexOf(" ") pos2
= (pos1+1) server = em.substring(pos2);
server_pos = server.lastIndexOf(".") reqtype =
server.substring(server_pos+1) type_end =
reqtype.substring(reqtype.length-1)
if(document.reg.fname.value == "")
{ alert("Enter the First
Name.");
document.reg.fname.focus();
return false;
if(document.reg.lname.value == "")
37
{ alert("Enter the Last
Name.");
document.reg.lname.focus();
return false;
} if(document.reg.gender.value ==
"")
{ alert("Select Gender");
document.reg.gender.focus()
; return false;
} if(em ==
"")
document.reg.emailid.focus(); alert("Email
cannot be blank");
return false;
else if(em.length<8)
{ document.reg.emailid.focus(); alert("Email length
cannot be less than 8 characters"); return false; }
else if(em.indexOf("@")==-1)
38
{ document.reg.emailid.focus(); alert("The Email
Address must contain '@' sign");
return false;
} else if(pos1<1)
{ document.reg.emailid.focus(); alert("Email
address cannot start with '@' sign"); }
else if(em.indexOf(".")==-1)
{ document.reg.emailid.focus(); alert("The
Email Address must contain '.' sign"); return
false;
} else if(pos!=-
1)
} else if(server.indexOf("@")!=-
1)
39
}
else if(server.indexOf(".")==0)
} else
if(reqtype=="")
} else if(type_end.toUpperCase()<"A" ||
type_end.toUpperCase()>"Z")
40
} if(document.reg.password.value ==
"")
{ alert("Enter the
Password.");
document.reg.password.focu
s(); return false;
if(document.reg.password.value.length<8 || document.reg.password.value.length>15 )
alert("Minimum charaters for password is 8 and Maximum character is 15");
document.reg.password.focus();
return
false;
if(document.reg.cpassword.value == "")
{ alert("Please Confirm the
Password.");
document.reg.cpassword.focus(); return
false;
41
if(document.reg.password.value != document.reg.cpassword.value)
{ alert("Password not
matching."); return false;
if(document.reg.contact.value == "")
{ alert("Enter the Contact.");
document.reg.contact.focus();
return false;
if(document.reg.contact.value.length < 10 || document.reg.contact.value.length>11)
{ alert("Enter proper
Contact."); return false;
</script>
42
<form id="reg" name="reg" method="post" action="" onsubmit="return validation()">
<table width="478" border="0">
<tr>
<td width="171" height="55">First Name:</td>
<td width="300"><input class="right" name="fname" type="text" id="fname" size="50"
/></td>
</tr>
<tr>
<td height="43">Last Name:</td>
<td><input class="right" name="lname" type="text" id="lname" size="50" /></td>
</tr>
<tr>
<td height="40"><label for="dob" class="left">Gender:</label>
<label></label></td>
<td><label>
<input type="radio" name="gender" value="Male" id="gender" />
Male
<input type="radio" name="gender" value="Female" id="gender" />
Female</label></td>
</tr>
<tr>
<td height="49">Email-ID:</td>
43
<td><input class="right" name="emailid" type="text" id="emailid" size="50" /></td>
</tr>
<tr>
<td height="49">Password:</td>
<td><input class="right" name="password" type="password" id="emailid4" size="50" /></td>
</tr>
<tr>
<td height="43">Confirm Password:</td>
<td><input class="right" name="cpassword" type="password" id="emailid2" size="50"
/></td>
</tr>
<tr>
<td height="43">Contact:</td>
<td><input class="right" name="contact" type="text" id="emailid3" size="50" /></td>
</tr>
<tr>
<td height="39" colspan="2" align="center"><input type="submit" name="submit"
id="submit" value="Register" class="buttonabc"/></td>
</tr>
</table>
<?php
44
<p> </p>
</form>
<div id="content_main"><form id="form1" name="form1" method="post" action="">
<p>
<center>
</center>
</p>
</form>
</div>
</div>
<div class="cleaner"></div>
</div> <?php
include("includes/footer.php");
?>
4.2.Testing Approach
4.2.1.Unit Testing:
45
The unit testing of the source code has to be done for every individual unit of
module that was developing part of the system and some errors were found for every turn and
rectified. This form of testing was use to check for the behavior signified the working of the
system in different environment as an independent functional unit.
4.2.2.Integration System:
From the individual parts to the cohesion of each part to make the system as a
whole, there is need to test the working between the assembled modules of the system. The
modules are integrated to make up the entire system. The testing process is concerned with
finding errors that result from unanticipated interaction between the sub-system and system
component. It is also concerned with validating the system meets its functional and
nonfunctional requirement.
CHAPTER.5
Results and Discussions
46
1. Home page
47
2. Registration page
3. Login page
4. View Spectacles & Lenses page
48
5. Frames page
6. Lens page
49
7. Contact Lens page
8. Doctors / Admin Login page
50
9. View Patients page
10. Set Appointment Page
51
1. View Appointment page
12.Patient Record Page
52
CHAPTER.6
Conclusion
Eye Care System management report in php is developed to support the
clinic daily operation before this is done manually. This system will involve
all the clinic operation starting from patient registration until billing the
patient. The important thing is it will become easier for the data record and
retrieval. This system will be able to generate report regarding the clinic
operation. For example, the number of patient per day and total collection
per day. This system is able to check the inventory for the medicine in the
clinic. The target user for this system is staff of the clinic, doctor and also
the management. Prototyping approach is applied while developing this
system.
53
CHAPTER.7
Reference
www.google.com
www.w3school.com
www.wikipedia.com
www.stackoverflow.com
www.hignchart.com
54
