4 TH Documentation

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE
1 INTRODUCTION
1.1 PROBLEM STATEMENT
The problems faced in the field of medical and health care such as the aging of
the population, the increase of chronic patients, the rising medical expenses, and the
needs to improve the quality of medical services are common around the world today.
In order to solve them, information technology (IT) must be deployed to this field. In
recent years, medical information systems play an increasingly important role in
supporting doctors and nurses, enhancing the quality of medical services, reducing the
medical expenses, and improving the care of chronic patients. Therefore, medical
informatization has drawn more and more attention in various countries.
1.2 EXISTING SYSTEM

The existing system mainly focuses on informatization for hospitals or medical
institutions within the organizations. However, few efforts are directly oriented to the
patients, their families, and other general users. With the rapid development of
information and communication technologies and the change of medical and health
care service models, creating various public-oriented health care service systems has
become a trend. The agencys goal is to realize EMR, online service for choosing
medical institutions and making appointment, electronic prescriptions, health network
infrastructure, PACS, and so on. It aims to help patients obtain better, faster, and safer
medical care by using IT. To achieve this goal and to build a network infrastructure of
health information,
1.2.1 Drawback in existing system
It has difficulties in meeting the diverse and personalized needs
of users and in adapting to the dynamically changing complex
application environments. Consequently, they fail to realize the
personalized customization and active recommendation of health
care services for users.
ASTI CSEDEPT
1.3 PROPOSED SYSTEM

In this paper, we have presented a health care platform PHISP. It supports
personal health information management, personal health risk assessment and
guidance, dynamic personal health monitoring and real-time early warning, active
recommendation of personalized medical treatment, active seasonal disease warning,
and other health care services for individuals. Moreover, for some specific diseases,
PHISP provides remote medical and care services. With the help of information and
communication technologies, especially the service oriented technologies, we have
designed and implemented the health care platform based on SOA and Web service
technologies, which makes our developed system have higher reusability, flexibility,
and extensibility.
1.3.1 Advantages of proposed system
The important means to achieve it is to realize the sharing of
patients information among general practitioners and hospitals in
real time.
1.4 SCOPE OF THE PROJECT

There is a strong demand for medical and health care service systems for the
public under the new computing model. They can provide remote health consultation,
remote real-time monitoring, remote diagnosis, personal health record (PHR), networkbased health care education, and other personalized services for the public through
personalized medical information management and services configuration and
integration. Thus, they can help us realize the integration of health care prevention,
medical services, and health management.
1.5 OBJECTIVE
We aim the use of information technology and management systems for the
betterment of health care is more and more important and popular. And In this paper,
we present PHISP It can support numerous health care tasks, provide individuals with
ASTI CSEDEPT
many intelligent and personalized services, and support basic remote health care and
guardianship.
2 PROJECT DESCRIPTION
2.1 USER INTERFACE DESIGN
This is the first module of our project. User Interface Design plays an important
role for the user to move login window to user window. This module has created for the
purpose of how many users are interacting with our website. In this login page we have
to enter login user name and password. It will check username and password is match
or not (valid username and valid password). If we enter any invalid username or
password we cant enter into login window to user window it will shows error message.
So we are preventing some unauthorized user entering into the login window to user
window. It will provide a good security for our project. So server contain user name
and password server also check the authentication of the user. It well improves the
security and preventing from unauthorized user enters into the admin login.
Patient Registration
Patient Login
Interaction
Data Base
Patient Window
Fig 2.1 Userinterfacedesign
ASTI CSEDEPT
Error Page
2.2 IMPLEMENT HEALTH CARE SERVICE SYSTEM

This is the second module of our project in this with the advent of web
applications, it includes a series of subsystems, such as personal health information
management system, personal health risk assessment and guidance system, seasonal
disease early warning system, decision making libraries for various diseases, remote
nursing, and medical systems for such patients as cardiovascular, cerebral apoplexy,
and diabetic ones. Health monitoring involves the collection of data about vital
physiological parameters from different parts of the body and making decisions based
on it. It is a new kind of solutions for universal health care, disease surveillance, and
prevention, and is also an important part of the Internet of things. Its aim is to provide
platform that integrates hardware, software, and wireless communication technology
and provides necessary conditions for the future development of universal medical and
health care systems.
Patient Health Records
Patient Health Status

Cloud Data Base
Patient Window
Patient Diet and Environmental Information
Patient physiological information
Fig 2.2 health care service system

ASTI CSEDEPT
2.3 SERVICES ENCAPSULATED

In the platform, a majority of functional modules are packaged in the form of
services. Here, we describe some of them briefly as follows. Environmental
information acquisition service , Subjective feelings acquisition service, Coronary heart
disease oriented data analysis and diagnosis service, Cerebral-apoplexy-oriented data
analysis and diagnosis service
and diabetes oriented data analysis and diagnosis
service, Personal health risk assessment service ,Based on the preliminary diagnostic
results and the EMR information of a patient, this service can assess the status of the
patients health risk. Personal health guidance service. According to the preliminary
diagnostic results and EMR information of a patient, it can provide the patient with
preventive measures, things to be cared and other health guidance. Personal health realtime warning service, It can warn the user about the signs of certain disease. All round
intervention service.
ASTI CSEDEPT
Cloud Data Base
Patient Window
Encapsulation Of Services For Patients
Service 1
Service2
Service n
Fig 2.3 services encapsulated
ASTI CSEDEPT
2.4 MEDICAL INFORMATION RETRIEVAL

When more number of Users will interact with our website. Then they want the
best information among the medicines what they are providing. So to give the better
medicines to the users who are visiting our websites for their medical information they
can choose the best medicine based on the previous user feedback. This information
may help some of the most highly customized by the admin who are always takes care
about our website growth and they will provide the updated information and
replaceable by the admin people.
Cloud Data Base

Patient Window
Encapsulation Of Services For Patients

Admin Login
Fig 2.4 medical information retrieval
ASTI CSEDEPT
2.5 USER FEEDBACK UNIT

This is the last module of our project in this we know about that the previous
users valuable suggestion and information about the medicines what they are used
according to their requirement for their health. To retrieve medical information, a
requester asks some medical information with the query browser. The request will be
forwarded to the processing segment and based on their requirement our website may
provide best results. The requester looks for the providers of the requested segment and
returns a set of the latest updated data to the requester. The processor returns a number
of medicines which is available based on the users requirement. Also, it chooses the
latest users feed back in order to increase the probability that for further times for our
web sites.
Cloud Data Base

Patient Window
User Feed Back Unit

Admin Login
Fig 2.5 feedback
ASTI CSEDEPT
3 LITERATURE SURVEY
3.1 DEFINITIONS
3.1.1 Effective web service composition in diverse and large-scale service networks
Description
Web services are considered to be a potential silver bullet for the envisioned
Service Oriented Architecture, in which loosely coupled software components are
published, located, and executed as integral parts of distributed applications. The main
research focus of Web services is to achieve the interoperability between distributed
and heterogeneous applications. Therefore, flexible composition of Web services to
fulfill the given challenging requirements is one of the most important objectives in this
research field. However, until now, service composition has been largely an error-prone
and tedious process. Furthermore, as the number of available Web services increases,
finding the right Web services to satisfy the given goal becomes intractable. In this
paper, toward these issues, we propose an AI planning-based framework that enables
the automatic composition of Web services, and explore the following issues. First, we
formulate the Web service composition problem in terms of AI planning and network
optimization problems to investigate its complexity in detail. Second, we analyze
publicly available Web service sets using network analysis techniques. Third, we
develop a novel Web service benchmark tool called WS Ben. Fourth, we develop a
novel AI planning-based heuristic Web service composition algorithm named WSPR.
Finally, we conduct extensive experiments to verify WSPR against state-of-the-art AI
planners. It is our hope that both WSPR and WS Ben will provide useful insights for
researchers to develop Web service discovery and composition algorithms, and
software.
Author : Seog-Chan Oh, Dongwon Lee, and Soundar R.T. Kumara
Year
: 2008
ASTI CSEDEPT
3.1.2 Semi-automatic composition of web services using semantic descriptions

Description
As web services become more prevalent, tools will be needed to help users and,
alter and integrate these services. Composing existing services to obtain new
functionality will prove to be essential for both business-to-business and business-toconsumer applications. We have developed a prototype that guides a user in the
dynamic composition of web services. Our semi-automatic process includes presenting
matching services to the user at each step of a composition, altering the possibilities by
using semantic descriptions of the services. The generated composition is then directly
executable through the WSDL grounding of the services. We tested our system by
generating semantic descriptions for some of the common services available on the web
such as translator, dictionary and map services. We also applied our approach to a
prototype sensor network environment where each sensor provides its data as a
network service.
Author
Year
: Evren Sirin1, James Hendler2, and Bijan Parsia

: 2006
ASTI CSEDEPT
10
3.1.3 htn planning for web service composition using shop2.

Description
Automated composition of Web Services can be achieved by using AI planning
techniques. Hierarchical Task Network (HTN) planning is especially well-suited for
this task. In this paper, we describe how HTN planning system SHOP2 can be used
with OWL-S Web Service descriptions. We provide a sound and complete algorithm to
translate OWL-S service descriptions to a SHOP2 domain. We prove the correctness of
the algorithm by showing the correspondence to the situation calculus semantics of
OWL-S. We implemented a system that plans over sets of OWL-S descriptions using
SHOP2 and then executes the resulting plans over the Web. The system is also capable
of executing information-providing Web Services during the planning process. We
discuss the challenges and difficulties of using planning in the information-rich and
human-oriented context of Web Services.
Author : Evren Sirin, Bijan Parsia, Dan Wu, James Hendler, Dana Nau.
Year
: 2006.
ASTI CSEDEPT
11
3.1.4 Service-oriented computing and cloud computing

Description
Today, many organizations strive to cope with rapid market changes, such as
evolving customer requirements and new business processes. One of the latest
challenges is how to work with service-oriented computing (SOC) in a cloud
computing environment. Here, we consider how to combine these two paradigms in
mutually beneficial ways. Competitiveness requires that companies continually modify
their IT systems by adding new features or deleting old ones in a relatively short period
of time. Traditional software lifecycle models havent explicitly addressed this
requirement for continuous integration of new capabilities.1 SOC aims to use services
as basic blocks to construct rapid, low cost yet secure and reliable applications. It
reduces the need to develop new software components each time a new business
process arises. A service is different from a traditional Software artifact in that its
autonomous, self-described, reusable, and highly portable. Services range from doing
simple arithmetic calculations to executing complicated programs in distributed
environments. By using standard description languages, such as the Web Service
Description Language (WSDL), a service can expose its interface to the outside world
for service discovery and, either by SOAP or Representational State Transfer (REST)
protocols, be invoked separately or as a composition of multiple services. The
advantages of this new computing paradigm are visible: companies and organizations
can develop massively distributed software systems by assembling basic services
dynamically.3 These services may come from different service providers and use
markup language techniques, such as XML, to exchange program information and data.
Author
: Yi Wei and M. Brian Blake
Year
: 2005
ASTI CSEDEPT
12
3.1.5 Qos-aware web service configuration

Description
With the development of enterprise-wide and cross-enterprise application
integration and interoperation towards web service, web service providers try to not
only fulfill the functional requirements of web service users, but also satisfy their nonfunctional conditions in order to survive in the competitive market. A hot research topic
is how to configure web services to meet their demand when the diversity of user
requirements, distinction of service components performance, and limitation of
resources are considered. This paper builds a web service configuration net based on
Petri nets in order to exhibit web service configuration in a formal way. Then, an
optimal algorithm is presented to help choose the best configuration with the highest
quality of service (QoS) to meet users non-functional requirements. Finally, the
simulation results and related analysis prove the soundness and correctness of our
model and algorithm.
Author : PengCheng Xiong, YuShun Fan, and MengChu Zhou
Year
: 2006
ASTI CSEDEPT
13
3.1.6 An efficient syntactic web service composition algorithm based on the

planning graph model
Description
In this paper, we have studied a common Web service composition problem, the
syntactic matching problem, where the output parameters of a Web service can be used
as the input parameters of another Web service. Many automatic Web service
composition algorithms based on AI planning techniques have been proposed.
However, most of them do not scale well when the number of Web services increases,
or may miss finding a solution even if one exists. The planning graph, another AI
planning technique, provides a unique search space. We have found that when we
model the Web service composition problem as a planning graph, it actually provides a
trivial solution to the problem. Instead of following the usual way to find a solution by
a backward search, we put our efforts into removing the redundant Web services
contained in the planning graph. Our approach can find a solution in polynomial time,
but with possible redundant Web services. We have tested our algorithms on the data set
used in ICEBE05 and compared our results with existing methods.
Author : Xianrong Zheng, Yuhong Yan
Year
ASTI CSEDEPT
: 2004
14
3.1.7 Recent advances in wireless sensor networks for health monitoring.

Description
Current technological advances in sensors, power efficient integrated circuits,
and wireless transferring have allowed the development of miniature, lightweight, lowcost, and smart physiological sensor nodes. These sensor nodes have capacity of
sensing, controlling, processing, and communication one or more vital signs.
Furthermore, they can be used in wireless personal area networks (WPANs) or wireless
body sensor networks (WBSNs) for health monitoring. Many studies were performed
and/or are under way in order to develop flexible, reliable, secure, real-time, and
power-efficient WBSNs suitable for healthcare applications. This paper reviews the
applications of wireless sensor networks in the healthcare area and discusses the related
issues and challenges. It reviews some applications of WSNs developed or currently
being developed for health monitoring.
Author : Jin Soo CHOI and MengChu ZHOU
Year
: 2005.
ASTI CSEDEPT
15
3.2 PROBLEMS ASSOCIATED

SOA aims to allow users to string together fairly large chunks of functionality to
form ad hoc applications that are built almost entirely from existing software services.
The larger the chunks, the fewer the interface points required implementing any given
set of functionality; however, very large chunks of functionality may not prove
sufficiently granular for easy reuse. Each interface brings with it some amount of
processing overhead, so there is a performance consideration in choosing the
granularity of services.
The great promise of SOA suggests that the marginal cost of creating the nth
application is low, as all of the software required already exists to satisfy the
requirements of other applications. Ideally, one requires only orchestration to produce a
new application. For this to operate, no interactions must exist between the chunks
specified or within the chunks themselves.
Instead, humans specify the interaction of services (all of them unassociated
peers) in a relatively ad hoc way with the intent driven by newly emergent
requirements. Thus the need for services as much larger units of functionality than
traditional functions or classes, lest the sheer complexity of thousands of such granular
objects overwhelm the application designer
3.3 TECHNIQUE AND ALGORITHM USED

3.3.1 Phisp (public-oriented health care information service platform).
ASTI CSEDEPT
16
In this paper, we present a platform called Public-oriented Health care

Information Service Platform (PHISP) under the new computing model, which can
support numerous health care tasks and provide individuals with many intelligent and
personalized health care services.
In particular, for such diseases as cerebral apoplexy, coronary heart disease, and
diabetes, some decision-making libraries and remote medical and care systems are
established, respectively. To overcome the shortcomings of the existing medical
information systems that are based on simple application architectures and to take full
advantages of the newly emerging service-oriented technologies, we design the
platform based on the modern SOA and adopt Web services and related composition
technologies as the means of implementation.
We describe its architecture and main components in detail and discuss some
important issues about the platform. In the platform, most of the functional modules are
packaged in the form of services, some of which are described briefly. Then, three
types of user/domain preferences are presented, and a simple programming language
style expression is proposed to express them.
For these preferences that are not considered in the previous work on automatic
service composition, we present new solutions to introduce branch structures into the
process models of composite services accordingly. Moreover, a new strategy for
identifying possible parallel cases in service composition is also presented.
3.3.2ALGORITHM
ASTI CSEDEPT
17
ASTI CSEDEPT
18
ASTI CSEDEPT
19
3.4 APPLICATIONS
Health care management
The term managed care or managed health care is used in the United States to
describe a variety of techniques intended to reduce the cost of providing health benefits
and improve the quality of care ("managed care techniques") for organizations that use
those techniques or provide them as services to other organizations ("managed care
organization" or "MCO"), or to describe systems of financing and delivering health
care to enrollees organized around managed care techniques and concepts ("managed
care delivery systems"). According to the United States National Library of Medicine,
the term "managed care" encompasses programs.
ASTI CSEDEPT
20
4 SOFTWARE REQUIREMENT SPECIFICATIONS

4.1 OVERALL DESCRIPTIONS
The software requirements document is the specification of the system. It
should include both a definition and a specification of requirements. It is a set of what
the system should do rather than how it should do it. The software requirements
provide a basis for creating the software requirements specification. It is useful in
estimating cost, planning team activities, performing tasks and tracking the teams and
tracking the teams progress throughout the development activity.
The hardware requirements may serve as the basis for a contract for the
implementation of the system and should therefore be a complete and consistent
specification of the whole system. They are used by software engineers as the starting
point for the system design. It shows what the system does and not how it should be
implemented.
4.1.1 Software Requirements
FRONT END
BACK END
OPERATING SYSTEM
IDE
J2EE (JSP, SERVLET), STRUTS

MS SQL 2005
:
WINDOWS 07
NET BEANS
4.1.2 Hardware Requirements
PROCESSOR
PENTIUM IV, INTEL CORE 2
DUO.
RAM
MONITOR
HARD DISK
:
:
:
512 MB DD RAM
15 COLOR
40 GB
ASTI CSEDEPT
21
4.2 OPERATIONAL ENVIRONMENT

Java Framework
Java is a programming language originally developed by James Gosling at
Microsystems and released in 1995 as a core component of Sun Microsystems' Java
platform. The language derives much of its syntax from C and C++ but has a simpler
object model and fewer low-level facilities. Java applications are typically compiled to
byte code that can run on any Java Virtual Machine (JVM) regardless of computer
architecture. Java is general-purpose, concurrent, class-based, and object-oriented, and
is specifically designed to have as few implementation dependencies as possible. It is
intended to let application developers "write once, run anywhere".
Java is considered by many as one of the most influential programming
languages of the 20th century, and is widely used from application software to web
applications. The java framework is a new platform independent that simplifies
application development internet. Java technology's versatility, efficiency, platform
portability, and security make it the ideal technology for network computing. From
laptops to datacenters, game consoles to scientific supercomputers, cell phones to the
Internet, Java is everywhere!
Objectives of Java
To see places of Java in Action in our daily life, explore java.com.
Why Software Developers Choose Java
Java has been tested, refined, extended, and proven by a dedicated community. And
numbering more than 6.5 million developers, it's the largest and most active on the
planet. With its versatility, efficiency, and portability, Java has become invaluable to
developers by enabling them to:
ASTI CSEDEPT
22
Write software on one platform and run it on virtually any other platform
Create programs to run within a Web browser and Web services
Develop server-side applications for online forums, stores, polls, HTML forms
processing, and more
Combine applications or services using the Java language to create highly

customized applications or services
Write powerful and efficient applications for mobile phones, remote processors,
low-cost consumer products, and practically any other device with a digital
heartbeat
Some Ways Software Developers Learn Java

Today, many colleges and universities offer courses in programming for the
Java platform. In addition, developers can also enhance their Java programming skills
by reading Sun's java.sun.com Web site, subscribing to Java technology-focused
newsletters, using the Java Tutorial and the New to Java Programming Center, and
signing up for Web, virtual, or instructor-led courses.
Object-oriented
To be an Object Oriented language, any language must follow at least the four
characteristics.
1. Inheritance : It is the process of creating the new classes and using the behavior of
the existing classes by extending them just to reuse the existing code and adding
addition a features as needed.
2. Encapsulation: It is the mechanism of combining the information and providing the
abstraction.
3. Polymorphism: As the name suggest one name multiple form, Polymorphism is the
way of providing the different functionality by the functions having the same name
based on the signatures of the methods.
ASTI CSEDEPT
23
4. Dynamic binding: Sometimes we don't have the knowledge of objects about their
specific types while writing our code. It is the way of providing the maximum
functionality to a program about the specific type at runtime.
JAVA SERVER PAGES
Java Server Pages or JSP for short is Sun's solution for developing dynamic web
sites. JSP provide excellent server side scripting support for creating database driven
web applications. JSP enable the developers to directly insert java code into jsp file,
this makes the development process very simple and its maintenance also becomes very
easy.
JSP pages are efficient, it loads into the web servers memory on receiving the
request very first time and the subsequent calls are served within a very short period of
time. In todays Environment most web sites servers dynamic pages based on user
request. Database is very convenient way to store the data of users and other things.
JDBC provide excellent database connectivity in heterogeneous database environment.
Using JSP and JDBC its very cease to develop database driven web application.
Java is known for its characteristic of "write once, run anywhere." JSP pages
are plat Java Server Pages Java Server Pages (JSP) technology is the Java platform
technology for delivering dynamic content to web clients in a portable, secure and welldefined way. The Java Server Pages specification extends the Java Servlet API to
provide web application developers with a robust framework for creating dynamic web
content on the server using HTML, and XML templates, and Java code, which is
secure, fast, and independent of server platforms.
JSP has been built on top of the Servlet API and utilizes Servlet semantics. JSP
has become the preferred request handler and response mechanism. Although JSP
technology is going to be a powerful successor to basic Servlet, they have an
evolutionary relationship and can be used in a cooperative and complementary manner.
Servlet are powerful and sometimes they are a bit cumbersome when it comes to
generating complex HTML. Most Servlet contain a little code that handles application
logic and a lot more code that handles output formatting. This can make it difficult to
separate and reuse portions of the code when a different output format is needed. For
ASTI CSEDEPT
24
these reasons, web application developers turn towards JSP as their preferred Servlet
environment.
Evolution of Web Applications

Over the last few years, web server applications have evolved from static to
dynamic applications. This evolution became necessary due to some deficiencies in
earlier web site design. For example, to put more of business processes on the web,
whether in business-to-consumer (B2C) or business-to-business (B2B) markets,
conventional web site design technologies are not enough. The main issues, every
developer faces when developing web applications, are:
Scalability - a successful site will have more users and as the number of users is
increasing fastly, the web applications have to scale correspondingly.
Integration of data and business logic - the web is just another way to conduct
business, and so it should be able to use the same middle-tier and data-access code.
Manageability - web sites just keep getting bigger and we need some viable
mechanism to manage the ever-increasing content and its interaction with business
systems.
Personalization - adding a personal touch to the web page becomes an essential
factor to keep our customer coming back again. Knowing their preferences, allowing
them to configure the information they view, remembering their past transactions or
frequent search keywords are all important in providing feedback and interaction from
what is otherwise a fairly one-sided conversation.
Apart from these general needs for a business-oriented web site, the necessity for new
technologies to create robust, dynamic and compact server-side web applications has
been realized.
ASTI CSEDEPT
25
The main characteristics of today's dynamic web server applications are as follows:
1. Serve HTML and XML, and stream data to the web client
2. Separate presentation, logic and data
3. Interface to databases, other Java applications, and CORBA, directory and mail
services
4. Make use of application server middleware to provide transactional support.
5. Track client sessions.
Benefits of JSP
One of the main reasons why the Java Server Pages technology has evolved into
what it is today and it is still evolving is the overwhelming technical need to simplify
application design by separating dynamic content from static template display data.
Another benefit of utilizing JSP is that it allows to more cleanly separating the roles of
web application/HTML designer from a software developer. The JSP technology is
blessed with a number of exciting benefits, which are chronicled as follows:
The JSP technology is platform independent, in its dynamic web pages, its web
servers, and its underlying server components. That is, JSP pages perform perfectly
without any hassle on any platform, run on any web server, and web-enabled
application server. The JSP pages can be accessed from any web server.
The JSP technology emphasizes the use of reusable components. These
components can be combined or manipulated towards developing more purposeful
components and page design. This definitely reduces development time apart from the
At development time, JSPs are very different from Servlet, however, they are
precompiled into Servlet at run time and executed by a JSP engine which is installed on
a Web-enabled application server such as BEA Web Logic and IBM Web Sphere.
ASTI CSEDEPT
26
Servlet
Earlier in client- server computing, each application had its own client program
and it worked as a user interface and need to be installed on each user's personal
computer. Most web applications use HTML/XHTML that is mostly supported by all
the browsers and web pages are displayed to the client as static documents.
A web page can merely displays static content and it also lets the user navigate
through the content, but a web application provides a more interactive experience.
Any computer running Servlet or JSP needs to have a container. A container is
nothing but a piece of software responsible for loading, executing and unloading the
Servlet and JSP. While Servlet can be used to extend the functionality of any Javaenabled server.
They are mostly used to extend web servers, and are efficient replacement for
CGI scripts. CGI was one of the earliest and most prominent server side dynamic
content solutions, so before going forward it is very important to know the difference
between CGI and the Servlet.
Java Servlet
Java Servlet is a generic server extension that means a java class can be loaded
dynamically to expand the functionality of a server. Servlet are used with web servers
and run inside a Java Virtual Machine (JVM) on the server so these are safe and
portable.
Unlike applets they do not require support for java in the web browser. Unlike
CGI, Servlet don't use multiple processes to handle separate request. Servlet can be
handled by separate threads within the same process. Servlet are also portable and
platform independent.
A web server is the combination of computer and the program installed on it.
Web server interacts with the client through a web browser. It delivers the web pages to
the client and to an application by using the web browser and he HTTP protocols
respectively.
ASTI CSEDEPT
27
The define the web server as the package of large number of programs installed
on a computer connected to Internet or intranet for downloading the requested files
using File Transfer Protocol, serving e-mail and building and publishing web pages. A
web server works on a client server model.
JSP and Servlet are gaining rapid acceptance as means to provide dynamic
content on the Internet. With full access to the Java platform, running from the server in
a secure manner, the application possibilities are almost limitless. When JSPs are used
with Enterprise JavaBeans technology, e-commerce and database resources can be
further enhanced to meet an enterprise's needs for web applications providing secure
transactions in an open platform.
J2EE technology as a whole makes it easy to develop, deploy and use web
server applications instead of mingling with other technologies such as CGI and ASP.
There are many tools for facilitating quick web software development and to easily
convert existing server-side technologies to JSP and Servlet.
4.3 FUNCTIONAL REQUIREMENTS

A functional requirement defines a function of a software-system or its
component. A function is described as a set of inputs, the behavior, and outputs. The
proposed system is achieved by suppression-based and generalization-based kanonymous and confidential databases. The protocols rely on well-known
cryptographic assumptions, and we provide theoretical analyses to proof their
soundness and experimental results to illustrate their efficiency.
ASTI CSEDEPT
28
4.4 NON FUNCTIONAL REQUIREMENTS

Non-functional requirements are the ones that act to constrain the solution.
Nonfunctional requirements are sometimes known as constraints or quality
requirements. Non-functional requirements can be further classified according to
whether they are performance requirements, maintainability requirements, safety
requirements, reliability requirements, or one of many other types of requirements.
4.5 COMMUNICATION INTERFACES

Most systems must operate with other systems must be specified as part of the
requirements. Procedural interfaces access services through calling procedure api. The
data structures are to be passed from one sub system to another sub system they can be
described graphical data models. Representation of data will be in bitwise specification.
ASTI CSEDEPT
29
5 SYSTEM DESIGN
Design Engineering deals with the various UML [Unified Modeling language]
diagrams for the implementation of project. Design is a meaningful engineering
representation of a thing that is to be built. Software design is a process through which
the requirements are translated into representation of the software. Design is the place
where quality is rendered in software engineering. Design is the means to accurately
translate customer requirements into finished product.
5.1 ARCHITECTURE DIAGRAM

The systems architect establishes the basic structure of the system, defining the
essential core design features and elements that provide the framework for all that
follows, and are the hardest to change later. The systems architect provides the
architects view of the users' vision for what the system needs to be and do, and the
paths along which it must be able to evolve, and strives to maintain the integrity of that
vision as it evolves during detailed design and implementation.
ASTI CSEDEPT
30
Fig 5.1 system architecture
ASTI CSEDEPT
31
5.2 USE CASE DIAGRAMS

A use case diagram is a type of behavioral diagram created from a Use-case
analysis. The purpose of use case is to present overview of the functionality provided
by the system in terms of actors, their goals and any dependencies between those use
cases. In the below diagram eleven use cases are depicted.
login
Hospital Information
Admin
Pharmacy Information
user
Medical Information
Feed Back
Fig 5.2 Use case diagram
ASTI CSEDEPT
32
5.3 ACTIVITY DIAGRAM

Activity diagram are a loosely defined diagram to show workflows of stepwise
activities and actions, with support for choice, iteration and concurrency. UML, activity
diagrams can be used to describe the business and operational step-by-step workflows
of components in a system. UML activity diagrams could potentially model the internal
logic of a complex operation. In many ways UML activity diagrams are the objectoriented equivalent of flow charts and data flow diagrams(DFDs)from structural
development.
user login
hospital
information
pharmacy
information
medical
reports
some other
information
access
feed back
Fig 5.3 Activity diagram
ASTI CSEDEPT
33
5.4 DATAFLOW DIAGRAM

Data flow diagrams can be used to provide a clear representation of any
business function. The technique starts with an overall picture of the business and
continues by analyzing each of the functional areas of interest.
Level-0:
Patient login
Data Base
Error Page
Patient Window
Level-1:
Patient window
Cloud Data
Encapsulating Services
Feedback Unit
Fig 5.4 dataflow diagram
5.5 SEQUENCE DIAGRAM
ASTI CSEDEPT
34
A sequence diagram in UML is a kind of interaction diagram that shows how

processes operate with one another and in what order. It is a construct of a message
sequence chart. Sequence diagrams are sometimes called Event-trace diagrams, event
scenarios, and timing diagrams. These diagrams must tells about each and actions
performed by the particular users. Their shows the operation performed systems.
login
hospital
information
login valid
pharmacy
information
user access
show different information

user1
feedback1
user2
feedback2
user3
Fig 5.5 sequence diagram
5.6 COLLABORATION DIAGRAM
ASTI CSEDEPT
feed back
35
feedback3
A collaboration diagram show the objects and relationships involved in an

interaction, and the sequence of messages exchanged among the objects during the
interaction. The collaboration diagram can be a decomposition of a class, class diagram
, or part of a class diagram. it can be the decomposition of a use case, use case
diagram, or part of a use case diagram. The collaboration diagram shows messages
being sent between classes and object (instances). A diagram is created for each system
operation that relates to the current development cycle (iteration).
login
hospital
information
2: login valid
1: show different information
3: user1
5: user2
7: user3
user
access
pharmacy
information
4: feedback1
6: feedback2
8: feedback3
feed
back
Fig 5.6 collaboration diagram
5.7 CLASS DIAGRAM

ASTI CSEDEPT
36
A class diagram in the UML is a type of static structure diagram that describes
the structure of a system by showing the systems classes, their attributes, and the
relationships between the classes. Private visibility hides information from anything
outside the class partition. Public visibility allows all other classes to view the marked
information. Protected visibility allows child classes to access information they
inherited from a parent class.
Medical_Informati
on
new medicines
old medicines
expiry date
login
username
password
insert()
update()
delete()
login()
validate()
registration
username
password
phone number
emailid
validate()
insert()
choose()
Hospital_Informati
on
address
websites
phone numbers
show()
update()
FeedBack
excellent
good
average
bad
insert()
modify()
Fig 5.7 class diagram
5.8 OBJECT DIAGRAM
ASTI CSEDEPT
37
Object diagram is a graphical representation of the static view which shows a

collection of objects and their relationships.
Medical_Informati
on
login
new medicines
old medicines
expiry date
username
password
insert()
update()
delete()
login()
validate()
registration
username
password
phone number
emailid
validate()
insert()
choose()
Hospital_Informati
on
address
websites
phone numbers
show()
update()
Fig5.8 object diagram
5.9 E-R DIAGRAM

ASTI CSEDEPT
38
FeedBack
excellent
good
average
bad
insert()
modify()
name
account
Patient
admin
id
address
mailid
Doctor
name
admin
specialist
name
Hospital
specialization
EMR
Cloud Data
Patient Information
admin
Fig5.9 E-R Diagram
6 CODING
ASTI CSEDEPT
39
LOGIN:
<!DOCTYPE html>

<html>
<head>
<meta charset="UTF-8">
<title>Services - Medical Hospital Website Template</title>
<link rel="stylesheet" href="css/style.css" type="text/css">
</head>
<body>
<div class="background">
<div class="page">
<a href="index.html" id="logo">phisiotherapy Hospital</a>
<div class="sidebar">
<ul>
<li>
<a href="index.jsp">Home</a>
</li>
<li>
<a href="login.jsp">Login</a>
</li>
<li>
<a href="programs.jsp">Programs</a>
ASTI CSEDEPT
40
</li>
<li class="selected">
<a href="services.jsp">Services</a>
</li>
<li>
<a href="blog.jsp">Blog</a>
</li>
<li>
<a href="contact.jsp">Contact</a>
</li>
</ul>
<div class="first">
<div>
<a href="user.jsp"><h2>User Login</h2></a>
<a href="admin.jsp"><h2>Admin Login</h2></a>
</div>
</div>
<div>
<div>
<img src="images/doctors-and-nurse.jpg" alt="">
</div>
</div>
</div>
ASTI CSEDEPT
41
<div class="body">
<div class="services">
<div>
<div>
<div>
<h4>These are the services sufficiently provided</h4>
<img src="images/services2.jpg" alt="">
<p align="justify">
</p>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
© Copyright 2013. All rights reserved
</p>
</div>
</div>
</div>
</body>
</html>
ASTI CSEDEPT
42
Register page:
<form
name="frm"
action="Register"
method="post"
validateForm()">
<table>
<tr>
<td>Name:</td>
<td><input type="text" name="rname"></td>
</tr>
<tr>
<td>User Name:</td>
<td><input type="text" name="runame"></td>
</tr>
<tr>
<td>Password:</td>
<td><input type="password" name="rpassword"></td>
</tr>
<tr>
<td>Confirm Password:</td>
<td><input type="password" name="rcpassword"></td>
</tr>
<tr>
<td>Gender:</td>
<td>
ASTI CSEDEPT
43
onsubmit="return
<input
type="radio"
name="gender">Male
type="radio"name="gender">Female</td>
</tr>
<tr>
<td>Date Of Birth:</td>
<td><select name="date">
<%
for (int i = 1; i <= 31; i++) {
%>
<option value="<%=i%>"><%=i%></option>
<%
}
%>
</select> <select name="month">
<option value="na">Month</option>
<option value="1">January</option>
<option value="2">February</option>
<option value="3">March</option>
<option value="4">April</option>
<option value="5">May</option>
<option value="6">June</option>
<option value="7">July</option>
<option value="8">August</option>
<option value="9">September</option>
ASTI CSEDEPT
44
<input
<option value="10">October</option>
<option value="11">November</option>
<option value="12">December</option>
</select> <select name="year">
<%
for (int i = 1950; i <= 2013; i++) {
%>
<option value="<%=i%>"><%=i%></option>
<%
}
%>
</select></td>
</tr>
<tr>
<td>Mobile:</td>
<td>
<input type="text" name="rmobile"></td>
</tr>
<tr>
<td>Email:</td>
ASTI CSEDEPT
45
<td>
<input type="text" name="remail"></td>
</tr>
<tr>
<td colspan="1">
<input type="submit" value="submit"></td>
<td><input type="reset" value="reset"></td>
</tr>
</table>
</form>
Implementation of Health Care Services:
function solution()
{
alert(" enter the correct detai");
var s=document.getElementById("problem").value;
alert(s);
var a;
var x="solutions.jsp?val="+s;
if (window.XMLHttpRequest)
{// If the browser if IE7+FirefoxChromeOperaSafari
a=new XMLHttpRequest();
}
else
{//If browser is IE6, IE5
a=new ActiveXObject("Microsoft.XMLHTTP");
}
a.onreadystatechange=function()
{
if (a.readyState==4 && a.status==200)
{
document.getElementById("information").innerHTML=a.responseText;
}
ASTI CSEDEPT
46
}
a.open("POST",x,true);
a.send();
}
Encapsulated Services:
<!DOCTYPE html>

<html>
<head>
</head>
<body>
<div class="page">
<ul>
<li>
</li>
<li>
</li>
<li>
</li>
</li>
<li>
</li>
<li>
</li>
</ul>
<div class="first">
<div>
<img src="images/man.jpg" alt="">
</div>
</div>
<div>
<div>
ASTI CSEDEPT
47

</div>
</div>
</div>
<div class="body">
<div>
<div>
<div>
<h4>These are the services sufficiently provided</h4>
<img src="images/services2.jpg" alt="">
<p align="justify">
</p>
</div>
</div>
</div>
</div>
</div>
<p>
</p>
</div>
</div>
</div>
</body>
</html>
Medical information retrieval
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<%@ page import="user.AdminOperations" %>
<
%@pageimport="dbpack.DBClass,java.sql.Connection,java.sql.ResultSet,java.sql.State
ment" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
ASTI CSEDEPT
48
HTML
4.01
Transitional//EN"
</head>
<% %>
<body bgcolor="Gray">
<div class="page">
<ul>
<li>
</li>
<li>
</li>
<li>
</li>
</li>
<li>
</li>
<li>
</li>
</ul>
<div class="first">
<div>
</div>
</div>
<div>
<div>
</div>
</div>
</div>
<div class="body">
<div>
<img src="images/services2.jpg" alt=""><br /><br />
<font color="Blue" size="25">
ASTI CSEDEPT
49
<center><h5><marquee direction="left">Admin Monitoring

Records</marquee></h5></center><br /></font>
<form action="AdminDeleteOperations" method="post">
<table align="center" border="0" bgcolor="DARKKHAKI">
<div id="titleBar">
<ul>
<li><h2 class="sIFR">Monitoring Process</h2></li>
</ul>
</div>
<table border="5" border style="padding: px;" with="20%" cellpadding="3"
cellspacing="2" bgcolor="DARKKHAKI">
<tr>
<th colspan="8"><br />
<h4>ADMIN RECORD DETAILS</h4></th>
</tr>
<tr>
<th>****</th>
<th>Problem</th>
<th>Tablet</th>
<th>Description</th>
<th>Tablet</th>
<th>Tablet</th>
</tr>
<%
ASTI CSEDEPT
50
Connection con=DBClass.con();
Statement st =con.createStatement();
ResultSet rs = st.executeQuery("select * from problemswithmedicines");
while (rs.next())
{
String s1 = rs.getString(1).trim();
%>
<tr align="left">
<td><input type="checkbox" name="ch" value="<%=s1%>"/></td>
<td><%=s1%></td>
<td><%=s2%></td>
<td><%=s3%></td>
<td><%=s4%></td>
<td><%=s5%></td>
<td><%=s6%></td>
<td><%=s7%></td>
</tr>
<%
}
%>
ASTI CSEDEPT
51
</table></table><br /><br />


<input type="submit" name="delete" value="DELETE">
</form>
<a href="addrecords.jsp"><input type="submit" name="add" value="ADD"></a>
</div>
</div>
</div>
</div>
</div>
<p>
</p>
</div>
</div>
</div>
</body>
</html>
package user;
import java.io.IOException;
import java.util.ArrayList;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
* Servlet implementation class AdminOperations
*/
ASTI CSEDEPT
52
public class AdminOperations extends HttpServlet {

private static final long serialVersionUID = 1L;
/**
* @see HttpServlet#HttpServlet()
*/
public AdminOperations() {
super();
// TODO Auto-generated constructor stub
}
/**
* @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse
response)
*/
protected
void
doGet(HttpServletRequest
request,
HttpServletResponse
response) throws ServletException, IOException

{
// TODO Auto-generated method stub
}
/**
* @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse
response)
*/
protected void
doPost(HttpServletRequest
request,
HttpServletResponse
response) throws ServletException, IOException

{
if (request.getParameter("view") != null)
{
// Invoke FirstServlet's job here.
/*response.sendRedirect("selectrecords1.jsp");*/
ServletContext context= getServletContext();
RequestDispatcher rd= context.getRequestDispatcher("/selectrecords1.jsp");
rd.forward(request, response);
}
else if (request.getParameter("delete") != null) {
// Invoke SecondServlet's job here.
}
}
}
User Feed Back Unit
ASTI CSEDEPT
53

<%@ page import="user.FeedBack" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
<html>
<head>
<title>Programs - Medical Hospital Website Template</title>
</head>
<body>
<div class="page">
<ul>
<li>
</li>
<li>
</li>
</li>
<li>
</li>
<li>
</li>
<li>
</li>
</ul>
<div class="first">
<div>
</div>
</div>
<div>
<div>
</div>
</div>
</div>
<div class="body">
ASTI CSEDEPT
54
<div class="programs">
<div>
<div>
<div class="featured">
<img src="images/sharing.jpg" alt="">
<p>
</p>
</div>
<div>
<h4 align="left" style="color: blue;">Give Your FeedBack</h4>
</div>
<div>
<form action="FeedBack" method="post">
<table style="background-color: gray;">
<tr>
<td align="center">Name</td><td>:</td><td><input type="text"
name="fname"/></td><br /><br />
</tr>
<tr>
<td>Description</td><td>:</td><td><textarea name="fdescription" rows="3"
cols="15" style=" "></textarea></td><br />
</tr>
<tr>
<td align="center">Mailid</td><td>:</td><td><input type="text"
name="fmailid"/></td>
</table><br />
<tr > <input type="submit" value="submit"></tr>
</form>
</div>
</div>
</div>
</div>
</div>
<p>
</p>
</div>
</div>
</div>
</body>
</html>
<%@ page import="user.FeedBack,java.sql.*" %>
ASTI CSEDEPT
55
<%@ page import="dbpack.*"%>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
<html>
<head>
<title>Programs - Medical Hospital Website Template</title>
</head>
<body>
<div class="page">
<ul>
<li>
</li>
<li>
</li>
</li>
<li>
</li>
<li>
</li>
<li>
</li>
</ul>
<div class="first">
<div>
</div>
</div>
<div>
<div>
</div>
</div>
</div>
<div class="body">
<div class="programs">
<div>
<div>
<div class="featured">
ASTI CSEDEPT
56
<img src="images/sharing.jpg" alt="">

<p>
</p>
</div>
<div>
<h4 align="left" style="color: blue;">Give Your FeedBack</h4>
</div>
<div>
<table>
<tr>
<td>User name</td>
<td>Description</td>
<td>Mail id</td>
</tr>
<%Connection con=DBClass.con();
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select * from feedback");
while(rs.next())
{%>
<tr>
<td><%=rs.getString(1)%></td>
</tr>
<% }%</table>
</div>
</div>
</div>
</div>
</div>
<p>
</p>
</div>
</div></div></body></html>
DataBase
package dbpack;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.ArrayList;
import org.apache.catalina.connector.Request;
public class DBClass {
public static Connection con()
{
Connection dbcon = null;
try{
ASTI CSEDEPT
57
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
dbcon=DriverManager.getConnection("Jdbc:Odbc:HealthCare");
/* st=dbcon.createStatement();*/
}
catch(Exception e)
{e.printStackTrace();}
return dbcon;
}
public static int
register(ArrayList al) throws ClassNotFoundException,
SQLException
{
ResultSet rs;
String rname=al.get(0).toString();
String runame=al.get(1).toString();
String rpwd=al.get(2).toString();
String rcpwd=al.get(3).toString();
String rgender=al.get(4).toString();
String rage=al.get(5).toString();
String rmobile=al.get(6).toString();
String remail=al.get(7).toString();
String ruserid=al.get(8).toString();
int i=0;
try
{
rs=con().createStatement().
executeQuery("select
uname
from
registration
where
uname='"+runame+"'");
if(rs.next())
{System.out.println("avoid duplicates");}
else{
PreparedStatement ps=con().prepareStatement("insert into registration
values(?,?,?,?,?,?,?,?,?)");
ps.setString(1, rname);
ps.setString(2, runame);
ps.setString(3, rpwd);
ps.setString(4, rcpwd);
ps.setString(5, rgender);
ps.setString(6, rage);
ps.setString(7, rmobile);
ps.setString(8, remail);
ps.setString(9, ruserid);
i=ps.executeUpdate();
}
}catch(Exception e)
{
ASTI CSEDEPT
58
e.printStackTrace();
}
return i;
}
public static int authentic(ArrayList al)
{
int count=0;
String runame=al.get(0).toString();
String rpwd=al.get(1).toString();
try{
Statement st=con().createStatement();
ResultSet rs=st.executeQuery("select * from registration
where uname='"+runame+"' and password='"+rpwd+"'");
while(rs.next())
{
count++;
}
}
catch(Exception e)
{
}
return count;
}
public static int insert(ArrayList al) throws ClassNotFoundException,
SQLException
{
int i=0;
String problem=al.get(0).toString();
String tab1=al.get(1).toString();
String des1=al.get(2).toString();
try
{
PreparedStatement
ps=con().prepareStatement("insert
problemswithmedicines values (?,?,?,?,?,?,?)");
ps.setString(1, problem);
ps.setString(2, tab1);
ps.setString(3, des1);
ASTI CSEDEPT
59
into
}
catch(SQLException e)
{e.printStackTrace();}
return i;
}
/*public static int delete(ArrayList al)
{
int i=0;
for(int j=0; j<al.size();j++)
{
String s=al.get(0).toString().trim();
try {
i=st.executeUpdate("delete from problemswithmedicines
where problem='"+s+"'");
} catch (SQLException e) {
// TODO Auto-generated catch block
}
}
return i;
}
*/
public static int delete(ArrayList al)
{
boolean b = false;
int j=0;
try
{
Statement st = con().createStatement();
for (int i = 0; i < al.size(); i++)
{
String d = al.get(i).toString().trim();
j=st.executeUpdate("delete
from
problemswithmedicines
problem='"+d+"'");
}
} catch (Exception e) {
// TODO: handle exception
}
ASTI CSEDEPT
60
where
return j;
}public static int feedback(ArrayList al)
{
int i=0;
String name=al.get(0).toString().trim();
String description=al.get(1).toString().trim();
String mailid=al.get(2).toString().trim();
try
{
PreparedStatement
ps=con().prepareStatement("insert
into
feedback
values(?,?,?)");
ps.setString(1, name);
ps.setString(2, description);
ps.setString(3, mailid);
} catch (SQLException e)
{
// TODO Auto-generated catch block
}return i;
}
/*public static String fileSearch(String filename)
{
String res="file not found";
try{
ResultSet
rs=st.executeQuery("select
filename='"+filename+");
while(rs.next())
{
} }catch(Exception e)
{
ASTI CSEDEPT
61
from
cloud_data
where
}
return res;
}*/}
Pharmacy details
<?xml version="1.0" encoding="ISO-8859-1" ?>
<%@page import="java.util.Iterator"%>
%@page import="java.util.ArrayList"%
%@page import="com.dbpack.DBClass"%
<%@
page language="java" contentType="text/html;
charset=ISO-8859-1"
<!DOCTYPE html>
<html lang="en">
<head>
<title>SERVICES | MEDICAL CENTER
NAME - Free Website Template from Web-Flash-Template.com</title>
<meta name="description" content="Place your description here" />
<meta name="keywords" content="put, your, keyword, here" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="author" content="Web-Flash-Template.com - We deliver
best flash website templates" />
<link rel="stylesheet" href="css/reset.css" type="text/css" media="all">
<link rel="stylesheet" href="css/layout.css" type="text/css" media="all">
<link rel="stylesheet" href="css/style.css" type="text/css" media="all">
</head>
<body id="page6">
<div class="wrap">
<div class="header">
<div class="container">
<h1 id="for_all"><a href="index.html">Medical Center</a></h1>
<div class="nav">
<ul>
<liclass="m1"><a
href="index.html"><span><b>Home</b></span></a></li>
ASTI CSEDEPT
62
<liclass="m2"><a
href="articles.html"><span><b>Articles</b></span></a></li>
<li class="m3">
<a href="about_us.html"><span><b>About us</b></span></a>
</li>
<li class="m4">
<a
href="services.html"
class="active"><span><b>Service</b></span></a></li>
<li class="m5 last">
<a href="contacts-us.html"><span><b>Contacts</b></span></a></li>
</ul>
</div></div></div>
<div class="container">

<div class="aside">
<div class="inside">
<h2>Latest News</h2>
<ul class="news">
<li><a href="#">June
30,
2010</a><strong>Sed
ut
perspiciatis
unde</strong>Omnis iste natus luptatem accusantium doloremque laudantium

totamrem.</li>
<li><a href="#">June
14,
2010</a><strong>Neque
porro
quisquam
est</strong>Consequuntur magni dolores eos qughi ratione voluptatem

sequi.</li>

</ul>
</div>
</div>

<div class="section" id="content">
<h2>Site Map</h2>
<p>At vero eos et accusamus et iusto odio dignissimos ducimus qui
blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas
molestias excepturi sint occaecati cupiditate non provident, similique sunt in
culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. </p>

<h2>THE FOLLOWING ARE THE PHARMACY DETAILS FOR THE
PATIENT</h2>
<%String patientid=(String)session.getAttribute("patientid");
System.out.println("patient id is \t"+patientid);
DBClass db=new DBClass();
String diseaseName=db.getDiseaseName(patientid);
System.out.println("disease name is \t"+diseaseName);
ArrayList list=DBClass.retrieveMedicines(diseaseName.trim());
System.out.println("the list values is"+list);
System.out.println("the list values is"+list.get(0).toString().trim());
Iterator iterator=list.iterator();
while(iterator.hasNext())
{
String disease=iterator.next().toString().trim();
String tablet1=iterator.next().toString().trim();
String reaction1=iterator.next().toString().trim();
%>
ASTI CSEDEPT
64
<table border="1" style="border-color: red;color: white ; background-color: black; " >

<tr><td><b>DISEASE NAME</b></td><td>:<%=disease%></td></tr>
<tr>
<td><b>PRESCRIPTION</b></td>
<td>:<%=tablet1%></td>
</tr>
<tr><td><b>DESCRIPTION</b></td>
<td>:<%=reaction1%></td>
</tr>
<tr>
</tr>
<tr>
<td><b>DESCRIPTION</b></td>
</tr>
<tr>
</tr>
<tr>
<td><b>DESCRIPTION</b></td>
</tr>
</table>
<%} %>
</div>
<div class="clear"></div></div></div>

<div class="footer"><div class="container">
<div class="cont-bot"></div><div class="social">
<div id="face">
<a
href="http://www.facebook.com/group.php?
gid=129632973725217&v=wall">
<img src="images/facebook.png" alt="" /></a></div>
ASTI CSEDEPT
65
<div id="twitter">
<a href="http://twitter.com/#!/wflashtemplate/"><img src="images/twitter.png"
alt="" /></a></div>
<div id="youtube">
<a href="http://www.youtube.com/user/WebFlashTemplateCom">
<img src="images/youtube.png" alt="" /></a>
</div>
</div>
<div class="inside"> Copyright © 2013. All right reserved. Image
from BigStockPhoto.com © Kurhan<br>
<a href="http://www.web-flash-template.com/" class="visit" title="Best
website
templates.">Website template</a> designed by web-flash-template.com </div>
</div>
</div>
</body>
</html>
7 TESTING
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to
check the functionality of components, sub assemblies, assemblies and/or a finished
product it is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
ASTI CSEDEPT
66
unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement. The process verifies that the application meets the
requirements specified in the system requirements document and is bug free.
7.1 TYPES OF TESTS

7.1.1 Unit Testing
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program input produces valid outputs.
All decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge
of its construction and is invasive. Unit tests perform basic tests at component level and
test a specific business process, application, and/or system configuration. Unit tests
ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.
7.1.2 Functional Testing

Functional tests provide systematic demonstrations that functions tested are
available as specified by the business and technical requirements, system
documentation, and user manuals.Functional testing is centered on the following items:
Valid Input
: identified classes of valid input must be accepted.
Invalid Input
: identified classes of invalid input must be rejected.
Functions
: identified functions must be exercised.
Output
: identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
7.1.3 System Testing

System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test. System
testing is based on process descriptions and flows, emphasizing pre-driven process
links and integration points.
ASTI CSEDEPT
67
7.1.4 Performance Testing

The Performance test ensures that the output be produced within the time limits,
and the time taken by the system for compiling, giving response to the users and
request being send to the system for to retrieve the results.
7.1.5 Integration Testing
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by
interface defects. The task of the integration test is to check that components or
software applications, e.g. components in a software system or one step up software
applications at the company level interact without error.
7.1.6 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires
significant participation by the end user. It also ensures that the system meets the
functional requirements.
Acceptance testing for Data Synchronization:
The Acknowledgements will be received by the Sender Node after the Packets
are received by the Destination Node
The Route add operation is done only when there is a Route request in need
The Status of Nodes information is done automatically in the Cache Updating
process
7.1.7 Build the Test Plan

Any project can be divided into units that can be further performed for detailed
processing. Then a testing strategy for each of this unit is carried out. Unit testing helps
to identity the possible bugs in the individual component, so the component that has
bugs can be identified and can be rectified from errors.
7.2 TEST RESULTS

ASTI CSEDEPT
68
7.2.1 White box testing

White box testing is a testing in which the software tester has knowledge of the
inner workings, structure and language of the software or at least its purpose. it is used
to test areas that cannot be reached from a black box level.
7.2.2 Black box testing
Black box testing is testing the software without any knowledge of

the inner workings, structure or language of the module being tested.
Block box tests must be written from a definitive source document, such as
specification or requirement document. it is a testing in which the software
under test is treated, as a block box we cannot see into it.
8 OUTPUT SCREENS
Snapshot is nothing but every moment of the application while running. It gives
the clear elaborated of application. It will be useful for the new user to understand for
the future steps.
HOMEPAGE
ASTI CSEDEPT
69
LOGIN
ASTI CSEDEPT
70
USERLOGIN
ASTI CSEDEPT
71
USERREGISTRATION
ASTI CSEDEPT
72
KEYGENERATION
ASTI CSEDEPT
73
PATIENTLOGIN
ASTI CSEDEPT
74
PATIENTTREATMENT
ASTI CSEDEPT
75
ENCAPSULATEDSERVICES
ASTI CSEDEPT
76
FEEDBACK
ASTI CSEDEPT
77
USERFEEDBACK
ASTI CSEDEPT
78
ADMINLOGIN
ASTI CSEDEPT
79
ADMINMONITORINGRECORD
ASTI CSEDEPT
80
FILLTHERECORDS
ASTI CSEDEPT
81
CLOUDADMINLOGIN
ASTI CSEDEPT
82
GLOBALLYREGISTEREDUSERID
ASTI CSEDEPT
83
PATIENTDETAILES
ASTI CSEDEPT
84
DOCTORREGISTRATION
ASTI CSEDEPT
85
DOCTORKEY
ASTI CSEDEPT
86
DOCTORLOGIN
ASTI CSEDEPT
87
PATIENTALLOTED
ASTI CSEDEPT
88
PHARMACYDETAILES
ASTI CSEDEPT
89
9 CONCLUSION
ASTI CSEDEPT
90
In the field of medical treatment and health care, existing work, including
projects, researches, software
products, and standards,
mainly focuses
on
informatization for hospitals or medical institutions within the organizations. However,

few efforts are directly oriented to the patients, their families, and other general users.
With the rapid development of information and communication technologies and the
change of medical and health care service models, creating various public-oriented
health care service systems has become a trend. In this paper, we have presented a
health care platform PHISP. It supports personal health information management,
personal health risk assessment and guidance, dynamic personal health monitoring and
real-time early warning, active recommendation of personalized medical treatment,
active seasonal disease warning, and other health care services for individuals.
10 FUTURE SCOPE
ASTI CSEDEPT
91
The medical and health care platform that we have implemented is only a
research and demonstration system. For its large-scale commercial applications, much
more work is needed. Further improvement and optimization of the proposed
composition methods supporting branch and parallel structures is another future
research, including learning from the work on automatic program synthesis and the
technique of multi agent planning and optimization. However, few efforts are directly
oriented to the patients, their families, and other general users. With the rapid
development of information and communication technologies and the change of
medical and health care service models, creating various public-oriented health care
service systems has become a trend.
11 REFERENCES
ASTI CSEDEPT
92
[1] D. Ardagna and B. Pernici, Adaptive service composition in flexible processes,

IEEE Trans. Softw. Eng., vol. 33, no. 6, pp. 369384, Jun. 2007.
[2] 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.
[3] R. Balzer, A 15 year perspective on automatic programming, IEEE Trans. Softw.
Eng., vol. SE-11, no. 11, pp. 12571268, Nov. 1985.
[4] D. Basin, Y. Deville, P. Flener, A. Hamfelt, and J. F. Nilsson, Synthesis of
programs in computational logic, in Program Development in Computational Logic,
vol. 3049, LNCS, M. Bruynooghe and K.-K. Lau, Eds. New York: Springer-Verlag,
2004, pp. 3065.
[5] D. Berardi, D. Calvanese, G. De Giacomo, M. Lenzerini, and M. Mecella,
Automatic composition of e-services that export their behavior, in Proc. ICSOC,
2003, pp. 4358.
Synthesis of underspecified composite e-services based on automated reasoning, in
Proc. ICSOC, 2004, pp. 105114.
Automatic service composition based on behavioral descriptions, Int. J. Coop. Inf.
Syst., vol. 14, no. 4, pp. 333376, 2005.
[8] R. Buyya, C. S. Yeo, S. Venugopal, J. Broberg, and I. Brandic, Cloud computing
and emerging IT platforms: Vision, hype, and reality for delivering computing as the
5th utility, Future Gener. Comput. Syst., vol. 25, no. 6, pp. 599616, Jun. 2009.
[9] G. Canfora, A. R. Fasolino, G. Frattolillo, and P. Tramontana, Migrating interactive
legacy system to Web services, in Proc. CSMR, 2006, pp. 2436.
ASTI CSEDEPT
93
[10] G. Canfora, A. R. Fasolino, G. Frattolillo, and P. Tramontana, A wrapping

approach for migrating legacy system interactive functionalities to service oriented
architectures, J. Syst. Softw., vol. 81, no. 4, pp. 463480, Apr. 2008.
[11] S. Cherukuri, K. K. Venkatasubramanian, and S. K. S. Gupta, Biosec: A biometric
based approach for securing communication in wireless networks of biosensors
implanted in the human body, in Proc. ICPPW, Oct. 2003, pp. 432439.
[12] F. Curbera, R. Khalaf, N. Mukhi, S. Tai, and S. Weerawarana, The next step in
Web services, Commun. ACM, vol. 46, no. 10, pp. 2934, Oct. 2003.
ASTI CSEDEPT
94

4 TH Documentation

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

4 TH Documentation

Загружено:

Авторское право:

Доступные форматы

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

1.2 EXISTING SYSTEM

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

1.3 PROPOSED SYSTEM

1.4 SCOPE OF THE PROJECT

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

Fig 2.1 Userinterfacedesign

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

2.2 IMPLEMENT HEALTH CARE SERVICE SYSTEM

Patient Health Records

Patient Health Status

Patient Diet and Environmental Information

Patient physiological information

Fig 2.2 health care service system

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

2.3 SERVICES ENCAPSULATED

and diabetes oriented data analysis and diagnosis

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

Patient Health Records

Patient Health Status

Cloud Data Base

Patient physiological information

Encapsulation Of Services For Patients

Fig 2.3 services encapsulated

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

2.4 MEDICAL INFORMATION RETRIEVAL

Patient Health Records

Cloud Data Base

Patient Health Status

Patient Diet and Environmental Information

Patient physiological information

Encapsulation Of Services For Patients

Fig 2.4 medical information retrieval

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

2.5 USER FEEDBACK UNIT

Patient Health Records

Cloud Data Base

Patient Health Status

Patient Diet and Environmental Information

Patient physiological information

User Feed Back Unit

Fig 2.5 feedback

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.2 Semi-automatic composition of web services using semantic descriptions

: Evren Sirin1, James Hendler2, and Bijan Parsia

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.3 htn planning for web service composition using shop2.

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.4 Service-oriented computing and cloud computing

: Yi Wei and M. Brian Blake

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.5 Qos-aware web service configuration

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.6 An efficient syntactic web service composition algorithm based on the

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.1.7 Recent advances in wireless sensor networks for health monitoring.

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

3.2 PROBLEMS ASSOCIATED

3.3 TECHNIQUE AND ALGORITHM USED

WEB SERVICE BASED PUBLIC ORIENTED PERSONALIZED HEALTH CARE

In this paper, we present a platform called Public-oriented Health care