1.

Introduction
1.1. Project Overview
It observed that people in unknown area are in severe danger if they don't
able to find hospital quickly. In emergency case a single minute counts so it is very important
that automatic applications must be used for decision making, maintain up to date status of the
hospital and doctors. Also gives the ratings to the doctors according to their performance and this
ratings are given by the people who attends the doctor previously so this approach saving the
time which can be save life of the patient. When the doctor or family receives the alarm message,
they can immediately take measures to rescue the user. It can also manage the health record of
the user. The user can take online medical to send their physical condition and then get
prescription from doctor who will send the prescription on the user's phone. The proposed
system locates nearest available hospital, contacts its ambulance emergency system, accesses a
Electronic Health Record of emergency patient that can critically assist in hospital treatments.

1.2. Technology Overview

World Wide Web Web Technologies: The World Wide Web is an open ended information
system where the information can be retrieved and is designed to use in the Internets distributed
environment. It contains Web pages that provide information and controls. The World Wide Web
initially started as a text only medium but now ranges of features are added like graphics, sounds,
animation and video. A large portion of internet is organized as the worldwideweb. A Web
application is defined as multi tier application based on the internet standards, using a web
browser as client. The rule making body of the web is W3C. W3C stands for World Wide Web
Consortium. W3C puts together specifications for Web standards. The most essential Web
standards are HTML, CSS and XML. The latest HTML standard is XHTML 1.0.
Hyper Text Transfer Protocol: The standard web transfer protocol is HTTP. Each interaction
consists of one ASCII request, followed by one RFC 822 MIME like response. Although the
use of TCP for the transport connection is very common, it is not formally required by the
standard. HTTP is constantly evolving. Several versions are in use and others are under
development.
TCP/IP Protocol: The most basic internet standard is the TCP/IP protocol. This protocol defines
the rules for establishing connections between computers, that is between client and server
hardware.

Three Tier Architecture: A web application follows a 3 tier model. The first tier consists of
presentation layer, the second tier consists of the application layer and the third tier provides the
data. A web application will collect the data from the client and sends the request to the web
server. In a web application the first tier includes the web browser and the web server. The
1

relevant script let program runs and gets the data (second and the third tier) and sends the data to
the Web server. The web server sends the data back to the client (first tier).
Apache Web Server: Apache was originally based on the code and ideas found in the most
popular HTTP server of the time. NCSA httpd1.3 (early 1995). It has since evolved into a far
superior system which can rival( and probably surpass) almost any other UNIX based HTTP
server in terms of functionality, efficiency and speed. Since it began, it has been completely
rewritten and includes many features. Apache is, as of January 1997, the most popular WWW
server on the Internet, according to the Net craft Survey.
Why Apache? To address the concerns of a group of WWW providers and part time http
programmers that http didnt as they wanted it to behave. Apache is an entirely volunteer effort,
completely funded by its members, not by commercial sales. Apache has been show to be
substantially faster than many other free servers.
Hypertext Markup Language (HTML): HTML is a collection of platform independent styles
used to create a web document. Html can be used to display any type of document on the host
computer, which can be geographically at different location. It is a versatile language and can be
used on any platform or desktop being platform independent, HTML indicates the manner in
which the document to be read by the interpreter. This can be done with the set of HTML
elements and tags which mark up the document and inform the browser, such as Internet
Explorer, about the action to be taken when a certain element or tag is specified.
Java Script: JavaScript is a scripting language that was created by Netscape. It was originally
called LiveScript. Despite the similarities in name and syntax, JavaScript is not related to the
Java programming language. JavaScript is supported by a wide range of Web browsers,
including both Microsoft Internet Explorer and Netscape Navigator. The Internet Explorer 3.0
supports JavaScript directly through a scripting engine in the file jscript.dll. Perhaps the bestknown scripting language prior to the introduction of VBScript was JavaScript. It is used to
create interactive web applications supported by the Netscape browser. JavaScript offers many of
the same advantages as VBScript. JavaScript is simple to use, lightweight, and dynamic.
Developers can easily embed code functionality for interactive applications inside a web page.
SYNTAX:
<SCRIPT LANGUAGE="JavaScript">
var rtn=false; function push_me()
{
alert ("Hello, World!");
return true;
2

}
</SCRIPT>

1.3. Project Organization

1.3.1. Activity Diagram
1.3.1.1. Login Diagram

1.3.1.2. Edit Profile Diagram

1.3.1.3.Doctor Access

1.3.
6

2. Software Process Model

1.3.3. Use Case Diagrams

1.3.3.1. Patient Use Case Diagram

Get appointment

Search hospital

Edit profile
Patient

Get prescription

Make comment
7

1.3.3.2.Doctor Use Case Diagram

Set appointment
Edit profile
Doctor

Send prescription

2. Preliminary Investigation
2.1.1. Identification Of need
This concept of online Healthcare management system and domain search of nearest Medical
services fulfills the following requirements:

The user can search nearest doctor from its location.

Patient data management.

Search doctor according to specialization, disease etc.

Clinic management & appointment.

Separate panel for each doctors and patients.

2.1.2. Feasibility Study

Feasibility study defines all the requirements to
performance characteristics of system. For system to be feasible, the design needs to undertake
various factors or performance requirements by which the system will be operated. A feasibility
study is short, focused study which aims at selecting the best system that meets performance
requirements. Information is gathered regarding the general requirements of the proposed
8

system. If feasibility study is to serve as the decision document, it answers a number of

questions.
Like
Is it beneficial?
Does it save time and money?
Can it be integrated with other systems already in place?
Planning resources is a very vast concept and we are beginners, thus including each and every
aspects of web, Integrate and automate them in every respect was not feasible for us.Hence we
perform feasibility study to make our project compatible for present environment. The concept of
nearest hospital search is newer. The project is built with the help of JAVA technology which is
reliable and efficient platform to work upon. This concept saves time and lessens the teachers
and students frustration.

Technical feasibility
Technical feasibility takes of the all the issues concerned with the design and the development
part of the project. It concerns itself with the software, hardware and the platform related issues.
The following are the technical specifications for our project. The project would require a lot of
space for storage of static as well as dynamic content. As the number of project available
increases the space required for storing them increases.

Economic feasibility
It provides an efficient and reliable platform to work upon.
It saves time and is thus a faster means of examination.
It is less costly than the other means of examination.

3.1. Existing System

Existing system refers to the system that is being followed till now. Presently all the hospital
functionalities are done manually. That is if a patient want to consult a doctor he can visit their
till his chance called. This is make the person very difficult. Out_Patient and In_Patient tickets
are distributed directly. The main disadvantage is time consuming.

LIMITATIONS OF EXISTING SYSTEM

Lack of security of data.

Time consuming.
Consumes large volume of paper work.
Manual work
No direct role for the higher officials.
To avoid all these limitations and make the system working more accurately it needs to be
computerized.

3.2. Proposed System

9

The Nearest hospital search application is user-friendly application. The main objectives of
the system is which shows and helps you to collect most of the information about Hospitality and
Medical Services The system is very simple in design and to implement. The system requires
very low system resources and the system will work in almost all configurations.
The main objectives of the proposed system can be enumerated as follows:
Patients are easily allocated to the doctors.
Doctors Search is possible.
Todays patient list help doctors to search their patients

ADVANTAGES OF PROPOSED SYSTEM

The system is very simple in design and to implement.

The system requires very low system resources and the system will work in almost all
configurations.
Security of data.
Ensure data accuracys.
Administrator controls the entire system.
Reduce the damages of the machines.
Minimize manual data entry.
Greater efficiency.
User friendly and interactive.
Minimum time required.

3.3. System Requirement Specification(SRS)

Software Requirement Specification (SRS) is the starting point of
the software developing activity. AS system grew more complex it became evident that the goal
of the entire system cannot be easily comprehended. Hence the need for requirement phase
arose. The software project is initiated by the client needs. The SRS is the means of translating
the ideas of the minds of the clients (the input) into a formal document (the output of the
requirement phase). The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis: The process is order and more nebulous of the two, deals
with understanding the problem, the goal and constraints.

2) Requirement Specification: Here, the focus is on specifying what has been found giving
analysis such as representation, specification languages and tools, and checking the specifications are
addressed during this activity
The Requirement phase terminates with the production of the validate SRS document. Producing the
SRS document is the basic goal of this phase.
10

Role of SRS:
The purpose of the Software Requirement Specification is to reduce the communication gap
between the clients and the developers. Software Requirement Specification is the medium
through which the client and the user needs are accurately specified. It forms the basis of the
software development. A good SRS should satisfy all the parties involved in the system.

4. System Design
4.1. Design Objectives & Constraints
The main plan for the system developed is to upgrading
existing system to the proposed system. There are mainly 4 methods of upgrading the existing system
to proposed

Parallel Run System

Direct Cut-Over System

Pilot System

Phase-in Method

Parallel Run System: It is the most secure method of converting from an existing to new system. In
this approach both the systems run in parallel for a specific period of time. During that period if any
serious problems were identified while using the new system, the new system is dropped and the
older system is taken at the start point again.
Direct Cut -Over Method: In this approach a working version of the system is implemented in one
part of the organization such as single work area or department. When the system is deemed
complete it is installed through out the organization either all at once (direct cut-over) or gradually
(phase-in).
Phase-in Method: In this method a part of the system is first implemented and over time other
remaining parts are implemented.
These are the requirements that are not directly related to the functionality of the
system. These should be considered as mandatory when the system is developed. The following
Constraints were arrived at for the system:
1. The system should be available over the intranet so that the Users like the candidates can use the
system from their system which was assigned to him.
2. For gaining entry into the system the users should be registered and should be able use login &
passwords for gaining access to the system.
11

3. The users should be able to change their passwords for increased security.
4. The system should conform to the requirement specified and final deliverables of the project
before some date.
5. The system should be easy to understand and organized in a structured way. The users should also
receive feedback about any errors that occur.
6. There should be no limitation about the hardware platform that is to be used to run the system.
7. Data integrity should be maintained if an error occurs or the whole system comes down.
8. A user should to be registered in the system once in 6 months only.
9. A user can take-up the next level test once he clears previous level.

4.2. Design Methodology/Technique

Design of website involves conceiving, planning out and specifying the externally observable
characteristics of the website product. We have data design, architectural design and user
interface design in the design process. These are explained in the following section. The goal of
design process is to provide a blue print for implementation, testing and maintenance activities.
The primary activity during data design is to select logical representations of data objects
identified during requirement analysis and software analysis. A data dictionary explicitly
represents the relationships among data objects and constraints on the elements of the data
structure. A data dictionary should be established and used to define both data and program
design.
Design process is in between the analysis and implementation process. The following design
diagrams (Data Flow Diagrams and E-R Diagrams) make it easy to understand and implement
The design process for website system has two levels.
1. System Design or Top Level Design.
2. Detailed Design or Logical Design.
System Design or Top Level Design:
In the system design the focus is on deciding which modules are needed for the system, the
specification of these modules and how these modules should be interconnected.
Detailed Design or Logical Design: In detailed design the interconnection of the modules or how
the specifications of the modules can be satisfied is decided. Some properties for a software
system design are
12

Verifiability.
Completeness.
Consistency.
Trace ability.
Simplicity/Understandability.

4.5. Database Design

In database environment many users share the data available that is authorizing users share data
access application with the database software managing the data an entity. A database and the
information as the interrelated data shared with the minimum redundancy to server many user
quickly and efficient. The general objectives are to make information access easy, quick and
flexible for the user. A database is the collection of the interrelated data. A database system
provides the enterprise with centralized control of its operation data. MYSQL is chosen for
developing the relevant database.

Database Tables
Hospital Table
Field

Type

hospital-Id

integer

Null
No

Foreign Key
No

References
-

hospitalnm

Varchar(50)

No

No

address

Varchar(300)

No

No

no.ofdoctor

integer

No

No

description

Varchar(300)

No

No

Field

Type

doctor-Id

integer

Null
No

Foreign Key
No

References
-

doctorName

Varchar(50)

No

No

password

Varchar(50)

No

No

Doctor Table

13

Patient Table
Field

Null

Type

References

Foreign Key

P-id

integer

No

No

email

Varchar(50)

No

No

patientName

Varchar(50)

No

No

password

Varchar(50)

No

No

gender

Varchar(10)

yes

No

phoneNumber

Integer

No

No

bloodType

Varchar(10)

No

No

Appointment Table
Field
appointmentId

Null

Type
integer

References

Foreign Key

No

No

doctorId

integer

No

yes

Doctor

patientId

integer

No

yes

Patient

Varchar(15)

No

No

period

Varchar(50)

No

No

title

text

No

No

status

14

date

integer

yes

No

Comment Table

Field
patientId

Null

Type
No

Yes

patient

integer

No

Yes

Doctor

integer

Yes

No

Varchar(15)

No

No

title

Varchar(50)

No

No

text

text

No

No

rating

integer

Yes

No

doctorId

integer

References

Foreign Key

rating

time

Prescription Table

Field

Null

Type

References

Foreign Key

prescriptionId

integer

No

No

doctorId

integer

No

Yes

Doctor

patientId

integer

No

Yes

patient

15

drugCount
date

integer

No

No

integer

No

No

5. Testing and Implementation

5.1. Testing Objectives
Test More and Test Frequent is organizations tagline for testing. A typical screen is tested at
four levels before it goes for production.
Level 1 is generally the work to be tested by other developers or other interns (this is typical first
level of testing where focus is not on requirement but end user testing) Ratio: 0% end user: 100%
Technical
Level 2 is level where a senior programmer comes into the testing cycle of the screen that was
unit tested by the developer in this phase the onus is to test software for technical requirements
specified.
Ratio: 80% Technical: 20% end user
Level 3 is where a tester will come into picture. The tester will test the software for both end user
as well as technical point of view.
The ratio here is: 50% Technical: 50% end user
Level 4 is where we make the code at Release-Ready. Here screen is tested to the core and each
and every standard must be followed and verified.
Ratio here is: 80% User Testing 20% Technical
This allows us to text a screen at four levels and at the end of four weeks when the screen goes to
production, it is generally bug free because more people have looked at this screen from different
viewpoints.

5.2. Testing Methodologies

Software testing is a critical element of the software quality assurance
and represents the ultimate review of specification, design and coding. Testing is the exposure of
the system to trial input to see whether it produces correct output.

Testing Phases: Software testing phases include the following:

16

Test activities are determined and test data selected. The test is conducted and test results are
compared with the expected results. There are various types of testing:

Unit Testing: Unit testing is essentially for the verification of the code produced during the
coding phase and the goal is test the internal logic of the module/program. Int the Generic code
project, the unit testing is done during coding phase of data entry forms whether the functions are
working properly or not. In this phase all the drivers are tested they are rightly connected or not.

Integration Testing: All the tested modules are combined into subsystems, which are then
tested. The goal is to see if the modules are properly integrated, and the emphasis being on the
testing interfaces between the modules. The generic code integration testing is done mainly on
table creation module and insertion module.

System Testing: It is mainly used if the software meets its requirements. The reference
document for this process is the requirement document.

Acceptance Testing: It is performed with realistic data of the client to demonstrate that the
software is working satisfactorily.

Testing Methods: Testing is a process of executing a program to find out errors. If testing is
conducted successfully, it will uncover all the errors in the software. Any testing can be done
basing on two ways:

White Box Testing: It is a test case design method that uses the control structures of the
procedural design to derive the test cases. Using this testing a software engineer can derive the
following test cases: Exercise all the logical decisions on either true or false sides. Execute all
loops at their boundaries and within their operational boundaries. Exercise the internal data
structures to assure their validity.

Black Box Testing: It is a test case design method used on the functional requirements of the
software. It will help a software engineer to derive sets of input conditions that will exercise all
the functional requirements of the program.
Black box Testing attempts to find errors in the following categories:

Incorrect or missing functions

Interface errors
Errors in data structures
Performance errors
Initialization and termination errors

By Black box testing we derive a set of test cases that satisfy the following criteria:

17

Test cases that reduce by a count that is greater than one, the number of additional test
cases that must be designed to achieve reasonable testing.
Test cases that tell us something about the presence or absence of classes of errors rather
than errors associated only with a specific test at hand.

5.3. Validation Check

User must take care that username and password must be properly entered for restore.

6. Conclusion & Discussion

6.1. Limitation Of Project
Tracing depends upon Google Maps API's.

This project is depends on web services.

A user must have fundamental knowledge as to how to use the
application.

6.2. Future Enhancements

The application can be further enhanced and several other functionalities can be added. The
application can be made for other platforms like windows, apple, and blackberry. The present
system is only applicable to android devices.
We can enhance the application by creating directory of doctors at
country, state or district level. The feature to update the details of the doctors at a later stage can
also be implemented. The system can also be enhanced by using voice recognition feature of the
Android.

6.3. Experience Gained (Technical & other)

This project is very helpful to increase our technical knowledge.

7. Bibliography & References

7.1. Reference Books
[1] paper 1- Domain Specific Search Of Nearest Hospital And Health care Management System
by Rashmi A.Nimbalkar, R.A. Fadnavis.06-08 march 2014.
[2] paper 2- Implementation of Near Field Communication Based Health care Management
System Abhishek Gune, AnirudhaBhat, Abhijith Pradeep. 22-25 September 2013.
[3]Paper3- EHospital Management &Hospital Information Systems Changing Trends.
Premkumar Balaraman, Kalpana Kosalram. May 2013.
18

[4] Paper 4- Privacy-Preserving Patient-Centric Clinical Decision Support System on Nave

Bayesian Classification by Ximeng Liu, Student Member, IEEE, Rongxing Lu, Member, IEEE,
Jianfeng Ma, Member, IEEE, Le Chen.
[5] Paper 5- Big Data, Big Knowledge, Big Data for Personalized Healthcare Marco Viceconti,
Peter Hunter, and Rod Hose. May14.
[6] paper 6- Design and Implementation of a Web-Service-Based Public-Oriented Personalized
Health Care Platform by PengWei Wang, ZhiJun Ding, ChangJun Jiang, and MengChu Zhou.
[7] - Li-Linchen, An Emergency Medical Service Support System For Patients In Rural Areas An Example From Taiwan Proceedings of the 2012 International Conference on Machine
Learning and Cybernetics, Xian, 15-17 July, 2012.
[8 ] M. Armbrust, A. Fox, R. Griffith, A. D. Joseph, R. Katz, A. Konwinski, G. Lee, D. Patterson,
A. Rabkin, I. Stoica, and M. Zaharia, Above the clouds: A Berkeley view of cloud computing,
EECS Department, Univ. California, Berkeley, CA,Tech. Rep. UCB/EECS-2009-28, Feb. 2009.
[9] DREAMITECH TEXTBOOKS- Web Technology and Application Development by KOGENT
Dr. Hiren Joshi.
[10] Michael L. Popovich, Joseph M. Henderson, John Stinn, Information Technology in the
Age of Emergency Public Health Response.

7.2. Other Documentation & resources

Web sites

www.java.sun.com
www.google.co.in
www.en.wikipedia.org
www.androidhive.info.
www.w3school.com
www.developers.android.com.

19