an exploratory method.

It includes gathering the

information from the
Health care providers
and
patients who visit or
work in OPD selected by
Convenience Sampling.
2.4-2: Setting of the
Study:
The study was
conducted at Public and
Private
Hospitals of Pune.
Sample Size of 300 is
included
in this research, 150
from healthcare
providers and
150 from patients. The
respondents are eligible
and
selected by
Convenience Sampling.
The
respondents had shown
positive interest in filling
questionnaire through
face to face interview.
a.
Public Hospitals : Public
Hospitals are
multispecialty hospitals.
The main objective of
these hospitals is to
provide treatment to all
patients without any
discrimination either
rich
or poor. The various
services offered in the
hospitals are medicine,
surgery, ophthalmology,
ENT, dermatology;
pediatric etc. The data is
collected through
structured
Questionnaires.
Respondents in the
hospital are (75
Healthcare
providers and 75
patients. The total is
150)
b.
Private Hospitals :
Private hospitals are
also
multispecialty hospitals.
The main objective of
these hospitals is to
provide treatment to all
patients without any
discrimination in race,
color. The various
services offered in the
hospitals are medicine,
surgery, ophthalmology,
ENT, dermatology.
CHAPTER NO 3
Conceptual
Discussion
Internal influencers can
obviously also be at
play in terms of what
services are provided by
the hospital and how
they are provided.
These
can include for instance

The skills and
experience of staff

Internal business
strategies such as
competition and
subsidization

Soft factors such as
morale and culture

Equipment availability.
Figure 1 – The Hospital
Context
It can be
seen from Figure 1
(above) that I have
made a link between the
entities “Laws and
Policies” and “Funding”.
This is intended to
signify the fact that in
some
cases laws and policies
governing healthcare
and hospitals are
imposed by the same
entities
that also provided
funding to hospitals.
This is
not always the case
however.
Whilst some of the inter-
relationships between
these entities are
obviously more
complex
than this diagram
suggests, the reason for
outlining these entities
and influencers is
simply to set the scene
for the conceptual
model
to be presented later in
this chapter.
characteristics of
healthcare is diversity,
and
they also asserted that
implementing IS .
healthcare is therefore
complex. The diagram
above is
intended to act as a
base point from which to
explore
this diversity and
complexity.
Let's
examine an example of
these
entities and influencing
factors at work. So let's
consider a hospital
manager - let's say
somebody
managing the operating
theatres. This manager
may
only be allowed to have
certain surgeries
performed in
their operating theatres,
and this could be for
many
reasons to do with any
of the entities
mentioned
above. If the hospital is
privately funded, it may
be
because the board or
senior hospital
management have
made a strategic
decision to not be in the
business of,
for example, pediatric
surgery. If it’s publically
funded, it may be
because the state health
department
has a co-ordinated
strategy around
providing pediatric
surgery in a limited
range of specialist
locations, and
this hospital is not one
of those locations. It
may be
that they are not
permitted to undertake
pediatric
surgery in their
operating theatres
because there are
no anesthetists available
to work at the hospital
who
have suitable
qualifications to provide
anesthetics to
children, or there are no
ward areas in the
hospital
suitable equipped to
care for children and
their
parents after the
surgery. Just with this
isolated
example, it quickly
becomes clear how
multiple
internal or external (to
the hospital) entities can
exert
an influence on what
services a provided by a
hospital, and how they
are provided. This
example
will become more
significant as I explore
the relevant
literature later in the
thesis.
Now let us consider
therefore the overlay of
information and
information systems on
this base,
from the viewpoint of
the hospital manager, as
defined
previously. In order for
the manager to comply
with
the requirement above,
given that they are not
(and
cannot be expected to
be) present on site 24/7,
they
have information needs,
and whilst these needs
could
be met in multiple ways,
they must be met. The
primary information
needs this manager has
is to be
sure that there are no
operations occurring on
children
(let's say anyone 15
years or younger) in the
operating
theatres of the hospital.
This need could be met
by a
range of solutions with
varying levels of
sophistication and
effectiveness. At the
simple end of
the spectrum, the
manager could receive a
report
every morning when
they arrive at work that
details
all the ages of patients
operated on in the
preceding
24 hours. At the more
complex end of the
spectrum,
the hospital patient
administration system
(PAS) could
have a business rule in it
the alerts the manager
by
SMS whenever a patient
under 15 is admitted to
the
hospital. Influencing
factors as to which of
these 2, or
a myriad of other,
solutions comes to be
implemented
include
existing technical infra
and info-structures,
available funding, and
mandatory reporting
requirements - amongst
many others.
It is clear
from the literature just
examined in Chapter 2
that there is widely held
belief in the information
systems community
internationally, with
varying levels of
evidence
behind it, that the
construct of a biological
ecosystem is a valid lens
through which to
examine information
systems, their
interrelationships with
each other, and the
interrelationships with
the business context in
which they sit.
In essence the core
drivers of the conceptual
framework
are as outlined below:

Information systems,
development,
acquisition, and
investment decisions
can
be critically influenced
by factors external
to an organization

Any ways in which such
decisions can be
made on a more
informed basis has the
potential to improve
organizational
outcomes in this space

The TEM model of
Adomavicius et al
(Adomavicius et al.,
2005
) is at the core
of this work and
represents many of the
concepts evident in
other theoretical
ecosystems frameworks,
whilst including
the added dimension of
a way to track
system evolution

However, the model is
yet to be validated in a
range
of contexts.

In addition, there are
ways in which the
model can be expanded
both in depth and
breadth
In summary, the
conceptual framework I
am proposing is
as follows: (see Figure 3)

The Hospital
Management
Technology
Ecosystem (HOME)
model is an
identifiable entity with
o
At least one focal
technology able to be
identified
o
Several TR’s able to be
identified
o
Several TL’s able to be
identified
o
A range of TSF’s able to
be identified

The existence of this
HOME then acts a
validation of
the core TEM

The HOME also
demonstrates
characteristics that
allow the expansion
of the core TEM
This framework ought to
be able to act as lens
through which to
examine the various
forces
(both internal and
external to a hospital)
acting
on the hospital.
management function.
(again, recall Figure 1 –
The
Hospital Context) . In
addition it should go a
long way
to explaining the
diversity, and the
interaction of
diverse elements of the
system, as proposed by
Fichman et al (Fichman
et al., 2011
)
Figure 2 – HOME
Conceptual
Framework
The 2 previously
outlined question sets
are designed
to allow validation of the
conceptual framework,
and
hence to validate (or
otherwise) the HOME
construct
in both a theoretical and
a practical sense. More
specifically the HOME
model, if validated by
this
research, could then act
as a lens through which
planners, developers
and purchasers of
systems can
make more informed
strategic and
operational
decisions in relation to
HMIS’.
In addition, researchers
would also then have a
position from which to
expand and deepen the
research base around
HMIS’, and technology
ecosystems more
broadly. More
specifically, the
model would allow the
more generic assertions
and
theories in relation to IS
planning, IS success and
IS
evolution to be
examined in the
healthcare
management setting,
considering the detailed
HOME
model.
In order to define the
scope of this conceptual
framework more
precisely, let us examine
some
further details around
the ecosystems concept.
The
work by De Thomasite al
(De
Thomasite al., 2005
)
around a business
modelling language for
digital
business ecosystems
(DBEs) has some
synergies with
the previous work by
Hadzic and Chang
(Hadzic and Chang,
2010
). These authors note
the potential to relate
business contexts, the
use of technology in
those contexts, and the
kinds of models evident
in biological
ecosystems. Another
similarity is the concept
that our understanding
of digital business
ecosystems (DBEs) or
DES’ in light of these
biological analogies, can
allow better planning
of investment and
development decisions
around technology. To
quote the authors, "the
DBE project aims at
overcoming the
aforementioned
difficulties by creating a
new
way of conceiving co-
evolution among
organization and
technology that shifts
from:

a mechanistic way of
organising business
based on static view of
the market to a
new organicistic
approach based on
mathematics, physics
and biological
science models,

an approach to
technology development
unrelated to inter
organisational issues to
new paradigms in which
technology and
organisation are related
variables
enabling innovative
ways of collaborating
and competing".
In addition, and
as previously noted,
Adomavicius et al
produced a number of
papers beyond their
initial work of 2005,
(Adomavicius et al.,
2006,
Adomavicius et al.,
2007b,
Adomavicius et al.,
2007a,
CHAPTER NO 4
 REQUIREMENT
SPECIFICATION
4.1 INTRODUCTION:
To be used efficiently,
all computer software
needs certain
hardware components
or the other software
resources to be
present on a computer.
These pre-requisites are
known
as(computer) system
requirements and are
often used as a
guideline as opposed to
an absolute rule. Most
software
defines two sets of
system requirements:
minimum and
recommended. With
increasing demand for
higher
processing power and
resources in newer
versions of
software, system
requirements tend to
increase over time.
Industry analysts
suggest that this trend
plays a biggerpart
in driving upgrades to
existing computer
systems than
technological
advancements.
4.2 HARDWARE
REQUIREMENTS:
The most common set of
requirements defined by
any
operating system or
software application is
the physical
computer resources,
also known as hardware.
A hardware
requirements list is
often accompanied by a
hardware
compatibility list (HCL),
especially in case of
operating
systems. An HCL lists
tested, compatibility and
sometimes
incompatible hardware
devices for a particular
operating
system or application.
The following sub-
sections discuss
the various aspects of
hardware requirements.
HARDWARE
REQUIREMENTS FOR
PRESENT
PROJECT:
PROCESSOR :
Intel dual Core ,i3
RAM : 1 GB
HARD DISK :
80 GB
4.3 SOFTWARE
REQUIREMENTS:
Software Requirements
deal with defining
software
resource requirements
and pre-requisites that
need to be
installed on a computer
to provide optimal
functioning of
an application. These
requirements or pre-
requisites are
generally not included in
the software installation
package
and need to be installed
separately before the
software is
installed.
SOFTWARE
REQUIREMENTS FOR
PRESENT
PROJECT:
OPERATING SYSTEM :
Windows 7/ XP/8
FRONT
END :
Html,css,java script.
SERVER SIDE SCRIPT :
Php
DATABASE
: Mysql
CHAPTER NO 5
 DATA
ANALYSIS
5.1EXISTING SYSTEM:
Hospitals
currently use a manual
system for the
management and
maintainance of critical
information. The
current system requires
numerous paper forms,
with data
stores spread through
out the hospital
management
infrastructure. Often
information is
incomplete or does not
follow management
standards. Forms are
often lost in
transit between
departments requiring a
comprehensive
auditing process to
ensure that no vital
information is lost.
Multiple copies of the
same information exist
in the
hospital and may lead to
inconsistencies in data
in various
data stores.
5.2 PROPOSED SYSTEM:
The Hospital
Management System is
designed for
any hospital to replace
their existing manual
paper based
system. The new system
is to control the
information of
patients. Room
availability, staff and
operating room
schedules and patient
invoices. These services
are to be
provided in an efficient,
cost effective manner,
with the
goal of reducing the
time and resources
currently required
for such tasks .
5.3 FEASIBILITY STUDY
The feasibility of the
project is analysed in
this phase
and business proposal is
put forth with a very
general plan
for the project and some
cost estimates. During
system
analysis the feasibility
study of the proposed
system is to
be carried out. This is to
ensure that the
proposed system
is not a burden to the
company. For feasibility
analysis,
some understanding of
the major requirements
for the
system is essential.
Three key
considerations involved
in the feasibility
analysis are:
5.3.1 Economic
Feasibility
This study is
carried out to check the
economic
impact will have on the
system will have on the
organization. The
amount of fund that the
company can
pour into the research
and development of the
system is
limited. The
expenditures must be
justified. Thus the
developed system as
well within the budget
and this was
achieved because most
of the technologies used
are freely
available. Only the
customised products
have to be
purchased.
5.3.2 Technical
Feasibility
 This study is
carried out to check the
technical
feasibility, that is,the
technical requirements
of the
system. Any system
developed must not
have a high
demand on the available
available technical
resources.
This will lead to high
demands being placed
on the client.
The developed system
must have a modest
requirement, as
only minimal or null
changes for the
implementing this
system.
5.3.3 Operational
Feasibility
The aspect of
study is to check the
level of
acceptance of the
system by the user. This
includes the
process of training the
user to use the system
efficiently.
The user must not feel
threatened by the
system, instead
must accept it as a
necessity. The level of
acceptance by
the users solely depends
on the methods that are
employed to educate
the user about the
system and to
make him familiar with
it. His level of
confidence must
be raised so that he is
also able to make some
constructive criticism,
which is welcomed, as
he is the
final user of the system.
5.4 SOFTWARE
SPECIFICATION
HTML:
HTML or Hypertext
Markup Language is the
standard markup
language
used to create web
pages
.
HTML is written in the
form of HTML elements
consisting
of tags enclosed in
angle brackets
(like <html>). HTML
tags most commonly
come in pairs like <h1>
and </h1>,
although some tags
represent empty
elements and so are
unpaired, for example
<img>. The first tag in a
pair is
the start tag, and the
second tag is the end
tag (they are
also called opening tags
and closing tags).
Though not
always necessary, it is
best practice to append
a slash to
tags which are not
paired with a closing
tag.
The purpose of a web
browser
is to read HTML
documents
and compose them into
visible or audible web
pages. The
browser does not
display the HTML tags,
but uses the tags
to interpret the content
of the page. HTML
describes the
structure of a website
semantically
along with cues for
presentation, making it
a markup language
rather than
a programming
language
.
HTML elements form the
building blocks of all
websites
.
HTML allows images and
objects
 to be embedded and
can
be used to create
interactive forms
. It provides a means to
create structured
documents
by denoting
structural semantics
for text such as
headings, paragraphs,
lists, links
, quotes and other
items. It can
embed scripts
 written in languages
such
as JavaScript
which affect the
behavior of HTML web
pages.
CASCADING STYLE
SHEETS (CSS):
It is a style
sheet language
used for describing
the look and formatting
of a document written
in a markup
language
. While most often used
to style web
pages
and interfaces
written in HTML
and XHTML
, the
language can be applied
to any kind of XML
document,
including plain XML
, SVG
and XUL
. CSS is a cornerstone
specification of the web
and almost all web
pages use CSS
style sheets to describe
their presentation.
CSS is designed
primarily to enable the
separation
of document content
from document
presentation,
including elements such
as the layout
, colors
, and fonts
.
[1]

This separation can

improve content
accessibility
,
provide more flexibility
and control in the
specification of
presentation
characteristics, enable
multiple pages to share
formatting, and reduce
complexity and
repetition in the
structural content .
 CSS can also
allow the same markup
page to be
presented in different
styles for different
rendering
methods, such as on-
screen, in print, by voice
(when read
out by a speech-based
browser or screen
reader
) and
on Braille-based
, tactile devices. It can
also be used to
allow the web page to
display differently
depending on the
screen size or device on
which it is being viewed.
While
the author of a
document typically links
that document to
a CSS file, readers can
use a different style
sheet, perhaps
one on their own
computer, to override
the one the author
has specified. However
if the author or the
reader did not
link the document to a
specific style sheet the
default style
of the browser will be
applied.
MySQL:
MySQL is developed,
distributed, and
supported by Oracle
Corporation. MySQL is a
database system used
on
the web it runs on a
server. MySQL is ideal
for both small
and large applications. It
is very fast, reliable, and
easy to
use. It supports
standard SQL. MySQL
can be compiled on
a number of platforms.
The data in MySQL is
stored in tables. A table
is a
collection of related
data, and it consists of
columns and
rows. Databases are
useful when storing
information
categorically.
FEATURES OF MySQL:
Internals and portability:

Written in C and C++.

Tested with a broad
range of different
compilers.

Works on many different
platforms.

Tested with Purify (a
commercial memory
leakage
detector) as well as with
Val grind, a GPL tool.

Uses multi-layered
server design with
independent
modules.
Security:

A privilege and
password system that is
very flexible
and secure, and that
enables host-based
verification.

Password security by
encryption of all
password
traffic when you connect
to a server.
Scalability and Limits:

Support for large
databases. We use
MySQL Server
with databases that
contain 50 million
records. We also
know of users who use
MySQL Server with
200,000
tables and about
5,000,000,000 rows.

Support for up to 64
indexes per table (32
before
MySQL 4.1.2). Each
index may consist of 1
to 16
columns or parts of
columns. The maximum
index width
is 767 bytes for InnoDB
tables, or 1000 for
MyISAM;
before MySQL 4.1.2, the
limit is 500 bytes. An
index
may use a prefix of a
column
for CHAR
, VARCHAR
, BLOB
, or TEXT
column types.
CONNECTIVITY:
Clients can connect to
MySQL Server using
several
protocols:

Clients can connect
using TCP/IP sockets on
any
platform.

On Windows systems in
the NT family (NT, 2000,
XP, 2003, or Vista),
clients can connect
using named
pipes if the server is
started with the --
enable-
named-pipe
option. In MySQL 4.1
and higher,
Windows servers also
support shared-memory
connections if started
with the --shared-
memory
option. Clients can
connect through shared
memory by using the --
protocol=memory
option.

On UNIX systems,
clients can connect
using Unix
domain socket files.
LOCALIZATION:

The server can provide
error messages to
clients in
many languages.

All data is saved in the
chosen character set.
CLIENTS AND TOOLS :

MySQL includes several
client and utility
programs.
These include both
command-line programs
such as
mysqldump
and mysqladmin
, and graphical
programs such as
MySQL Workbench
.

MySQL Server has built-
in support for SQL
statements to check,
optimize, and repair
tables.
These statements are
available from the
command
line through the
mysqlcheck
client. MySQL also
includes myisamchk
, a very fast command-
line
utility for performing
these operations
on MyISAM tables.

MySQL programs can be
invoked with the --
help or -? option to
obtain online assistance.
WHY TO USE MySQL:
•
Leading open source
RDBMS
•
Ease of use – No frills
•
Fast
•
Robust
•
Security
•
Multiple OS support
•
Free
•
Technical support
•
Support large database–
up to 50 million rows,
file
size limit up to 8 Million
TB
JAVASCRIPT:
JavaScript is the
scripting language of
the Web. All
modern HTML pages are
using JavaScript. A
scripting
language is a
lightweight
programming
language.JavaScript
code can be inserted
into any HTML
page, and it can be
executed by all types of
web browsers.
JavaScript is easy to
learn.
WHY TO USE
JAVASCRIPT:
JavaScript is one of the 3
languages all web
developers
must learn:
1.
HTML to define the
content of web pages
2.
CSS to specify the
layout of web pages
3.
JavaScript to specify the
behavior of web pages
Example
x=
document.getElementBy
Id("demo"); //Find the
HTML
element with id="demo"
x.innerHTML = "Hello
JavaScript"; //Change
the
content of the HTML
element
document.getElementBy
Id() is one of the most
commonly
used HTML DOM
methods.
OTHER USES OF
JAVASCRIPT :

Delete HTML elements

Create new HTML
elements

Copy HTML elements

In HTML, JavaScript is a
sequence of statements
that
can be executed by the
web browser.
JAVASCRIPT
STATEMENTS :

JavaScript statements
are "commands" to the
browser.

The purpose of the
statements is to tell the
browser
what to do.

This JavaScript
statement tells the
browser to write
"Hello Dolly" inside an
HTML element with
id="demo":
Semicolon;

Semicolon separates
JavaScript statements.

Normally you add a
semicolon at the end of
each
executable statement.

Using semicolons also
makes it possible to
write many
statements on one line.
JAVASCRIPT CODE:

JavaScript code (or just
JavaScript) is a
sequence of
JavaScript statements.

Each statement is
executed by the browser
in the
sequence they are
written.

This example will
manipulate two HTML
elements:

Example

document.getElementBy
Id("demo").innerHTML="
Hell
o Dolly";
document.getElementBy
Id("myDIV").innerHTML=
"Ho
w are you?";
JAVASCRIPT
PROPERTIES:

Properties are the
values associated with a
JavaScript
object.

A JavaScript object is a
collection of unordered
properties.

Properties can usually
be changed, added, and
deleted,
but some are read only.
PHP:
WHAT IS PHP?

PHP is an acronym for
"PHP Hypertext
Preprocessor"

PHP is a widely-used,
open source scripting
language

PHP scripts are executed
on the server

PHP costs nothing, it is
free to download and
use
WHAT IS PHP FILE?

PHP files can contain
text, HTML, CSS,
JavaScript,
and PHP code

PHP code are executed
on the server, and the
result is
returned to the browser
as plain HTML

PHP files have extension
".php"
WHAT CAN PHP DO?

PHP can generate
dynamic page content

PHP can create, open,
read, write, delete, and
close
files on the server

PHP can collect form
data

PHP can send and
receive cookies

PHP can add, delete,
modify data in your
database

PHP can restrict users to
access some pages on
your
website

PHP can encrypt data
With PHP you are not
limited to output HTML.
You can
output images, PDF files,
and even Flash movies.
You can
also output any text,
such as XHTML and XML.
WHY PHP?

PHP runs on various
platforms (Windows,
Linux,
Unix, Mac OS X, etc.)

PHP is compatible with
almost all servers used
today
(Apache, IIS, etc.)

PHP supports a wide
range of databases

PHP is free. Download it
from the official PHP
resource: www.php.net
CHAPTER NO 6
DESIGN
6.1 SYSTEM DESIGN:
6.1.1INTRODUCTION TO
UML:
UML Design
 The
Unified Modeling
Language
(UML) is a standard
language for specifying,
visualizing, constructing,
and documenting the
software
system and its
components. It is a
graphical language ,
which provides a
vocabulary and set of
semantics and
rules. The UML focuses
on the conceptual and
physical
representation of the
system. It captures the
decisions
and understandings
about systems that must
be
constructed. It is used to
understand, design,
configure,
maintain, and control
information about the
systems.
The UML is a language
for:

Visualizing

Specifying

Constructing

Documenting
Visualizing
Through UML we see or
visualize
an existing system and
ultimately we visualize
how the
system is going to be
after implementation.
Unless we
think, we cannot
implement. UML helps to
visualize, how
the components of the
system communicate
and interact
with each other.
Specifying
Specifying means
building, models
that are precise,
unambiguous and
complete UML
addresses the
specification of all the
important analysis
design, implementation
decisions that must be
made in
developing and
deploying a software
system.
Constructing
 UML
models can be directly
connected to a variety
of programming
language through
mapping a model from
UML to a programming
language
like JAVA or C++ or VB.
Forward Engineering
and
Reverse Engineering is
possible through UML.
Documenting
 The
Deliverables of a project
apart
from coding are some
Artifacts, which are
critical in
controlling, measuring
and communicating
about a system
during its developing
requirements,
architecture, desire,
source code, project
plans, tests, prototypes
releasers,
etc...
6.2 UML Approach
UML Diagram
 A
diagram is the graphical
presentation of a set of
elements, most often
rendered as a
connected graph of
vertices and arcs . you
draw diagram to
visualize a system from
different perspective, so
a diagram
is a projection into a
system. For all but most
trivial
systems, a diagram
represents an elided
view of the
elements that make up
a system. The same
element may
appear in all diagrams,
only a few diagrams , or
in no
diagrams at all. In
theory, a diagram may
contain any
combination of things
and relationships. In
practice,
however, a small
number of common
combinations arise,
which are consistent
with the five most useful
views that
comprise the
architecture of a
software-intensive
system.
For this reason, the UML
includes nine such
diagrams:
1.
Class diagram
2.
Object diagram
3.
Use case diagram
4.
Sequence diagram
5.
Collaboration diagram
6.
State chart diagram
7.
Activity diagram
8.
Component diagram
9.
Deployment diagram
USE CASE DIAGRAM:
A usecase diagram in
the Unified Modeling
Language(UML) is atype
of behavioral diagram
defined by
and created from a use-
case analysis.its
purpose is to
present a graphical
overview of the
functionality provided
by a system in terms of
actors, their
goals(represented as
use cases),and any
dependencies between
those use cases.
Use case diagrams are
formally included in two
modeling
languages defined by
the OMG:theunfied
modeling
language(UML) and the
systems modeling
language(sysML)
Use case diagram of our
project:
doct o r
Re gis t ra t io n
R e ce pt io n
Got o doctor
Ta k e recept
pha rm acist
la bo ra t o ris t
Dis cha rge sum m ary
pa t ient
Class Diagram:
A Class is a category or
group of things that has
similar
attributes and common
behavior. A Rectangle is
the icon
that represents the class
it is divided into three
areas. The
upper most area
contains the name, the
middle; area
contains the attributes
and the lowest areas
show the
operations. Class
diagrams provides the
representation that
developers work from.
Class diagrams help on
the analysis
side, too.
Pe rso n
+name_string
+age_number
+date of birth_number
+address_string
+phone num_number
+gender_string
+date of join()
+date of discharge()
Ho spit a l
+name_string
+address_string
+phon_number
+available time()
+states()
+1+*
Pa t ie nt
+gender_string
+prescription_string
-allergies_string
+in_time()
+out_time()
St a ff
+joined: date
+qulification_string
+certification_string
+languages_string
+work dutes()
+hoil days()
Oper a t ions st aff
+names_string
+deprt_string
+join time()
A dm inistra tive staff
+name of emp_string
#details_string
-time period_number
+open_list()
+close_list()
Te chnica l staff
+name_string
+location_string
+join time()
Doc t or
+name_string
+addresss_string
+phone_number
+speciality_string
+joined_date()
+dute_time()
Nurse
+name_string
+address_string
+phone_number
+join_date()
surge n
+opr_type
+free_number
+block_string
+opr_time()
+week period()
Re c ep tio nis t
+patient_details
+problem_string
+age_string
+in_time()
+ot_time()
Te chnician
+name_string
+address_string
+counter_number
+opr_name()
+total_opr()
La bo ra t or is t
+name_string
+test_details
+time_number
+room-num()
+opr_time()
+*
+1

Sequence diagram:
A Sequence Diagram is
an interaction diagram
that
emphasis the time
ordering of messages; a
collaboration
diagram is an
interaction diagram that
emphasizes the
structural organization
of the objects that send
and receive
messages. Sequence
diagrams and
collaboration diagrams
are isomorphic, meaning
that you can take one
and
transform it into the
other.
Doctor Registration Reception Patient
Laboratory Pharmacy ischarge summary
1: login()
2: view appointment()
3: registration()
4: send request()
5: done any surgeries()
6: go to laboratory()
7: take medicins()
8: paitent ok()
9: send discharge summmary()
10 : discharge paitent()
Collaboration diagram:
A Collaboration Diagram
also called a
communication
diagram or interaction
diagram, is an
illustration of the
relationships and
interactions among
software objects. The
concept is more than a
decade old although it
has been
refined as modeling
paradigms have
evolved.
P1 : Patient R1 : Receptionist
D1 : Doctor N1 : Nurse
1:Takes Appointment
10:Takes Appointment from
doctor
4:confirms appointment
9:Ask for payment
7:Take medicins
5:Consult doctor
8:paitent ok
6:Assist doctor
3:Doctor available
2:takes Appointment from doctor
Deployement diagram:
A Deployment Diagram
shows the configuration
of run-
time processing nodes
and the components
that live on
them. Deployment
diagrams address the
static deployment
view of architecture.
They are related to
component
diagrams in that a node
typically encloses one or
more
components.
Hospit al Local Se rv e r
desk t op Client
Printer
Database Serv er
Statechart Diagrams:
The state diagram
shows the
states of an object and
represents activities as
arrows
connecting the states.
The Activity Diagram
highlights the
activities. Each activity
is represented by a
rounded
rectangle-narrower and
more oval-shaped than
the state
icon. An arrow
represents the transition
from the one
activity to the next. The
activity diagram has a
starting
point represented by
filled-in circle, and an
end point
represented by bulls
eye.
Enter Hospital
Takes Appointment
Undergo Diagnosis
Takes Treatment
undergo labtests and buy
medicines
gets cured
not cured

CHAPTER NO 7
SYSTEM
IMPLEMENTATION
7. IMPLEMENTATION:
7.1 Inroduction:
Implementation is the
stage of the project
when the
theoretical design is
turned out into a
working system.
Thus it can be
considered to be the
most critical stage in
achieving a successful
new system and in
giving the user,
confidence that the new
system will work and be
effective.
The implementation
stage involves careful
planning,
investigation of the
existing system and it’s
constraints on
implementation,
designing of methods to
achieve
changeover and
evaluation of
changeover methods.
7.2 Sample code:
Home.html:
<!DOCTYPE html>
<html>
<body>
<table width="1350"
height="640"
border="1" >
<tr>
<td colspan="2"
style="background-
color:#FFF5EE;">
<h1>HOSPITAL
MANAGEMENT
SYSTEM</h1>
<h3
align="center">ADMIN
PANEL</h3>
</td>
</tr>
<tr>
<td style="background-
color:#00FFFF;width:50
px;height:400px;">
<table align="center">
<tr><td><form
action="doctor.php"
align="center">
<input type="submit"
align="center" value="
doctor
">
</form></td>
</tr>
<tr>
<td><form
action="nurse.php"
align="center">
<input type="submit"
align="center" value="
nurse
">
</form></td>
</tr>
<tr>
<td><form
action="patient.php"
align="center">
<input type="submit"
align="center" value="
patient
">
</form></td>
</tr>
<tr>
<td><form
action="pharmacist.php
" align="center">
<input type="submit"
align="center" value="
pharamacist
">
</form></td>
</tr>
<tr>
<td><form
action="laboratorist.php
" align="center">
<input type="submit"
align="center" value="
laboratorist
">
</form></td><tr>
<td><form
action="accountant.php
" align="center">
<input type="submit"
align="center" value="
accountant
">
</form></td>
</tr>
</table>
</td>
<td style="background-
color:#eeeeee;height:20
0px;width:400px;height:
400px;"><
h3
align="center">Advanc
ed, powerfull, flexible
complete
management software
for hospital, clinic and
medical
institutes. Integrates
and facilitates all user
area of a
hospital:
</h3><h4>align="cent
er">Administrator</h4>
<h4
align="center">Doctor<
/h4>
<h4
align="center">Patient
</h4>
<h4
align="center">Nurse</
h4>
<h4
align="center">Pharma
cist</h4>
<h4
align="center">Laborat
orist</h4>
<h4
align="center">Account
ant</h4>
</td>
</tr>
<tr>
<td colspan="2"
style="background-
color:#9ACD32;text-
align:center;">
<table align="right">
<th>
<tr>
<form
action="appointment.ph
p" align="center">
<input type="submit"
align="center" value="
appointment ">
</form>
</tr>
<tr>
<form
action="payment.php"
align="center">
<input type="submit"
align="center" value="
payment
">
</form>
</tr>
<tr>
<form
action="bloodbank.php"
align="center">
<input type="submit"
align="center" value="
bloodbank
">
</form>
</tr>
<tr>
<form
action="medicine.php"
align="center">
<input type="submit"
align="center" value="
medicine
">
</form>
</tr>
<tr>
<form
action="operations.php"
align="center">
<input type="submit"
align="center" value="
operations
">
</form>
</tr>
<tr>
<form
action="birthreport.php"
align="center">
<input type="submit"
align="center" value="
birthreport
">
</form>
</tr>
<tr>
<form
action="deathreport.ph
p" align="center">
<input type="submit"
align="center" value="
deathreport
">
</form>
</tr>
<tr>
<form
action="bedallotment.p
hp" align="center">
<input type="submit"
align="center" value="
bedallotment ">
</form>
</tr>
</th>
</table>
</td>
</tr></table></
body></html>
Doctor.PHP
<!DOCTYPE html>
<html>
<body>
<table width="1350"
height="640"
border="1" >
<tr>
<td colspan="2"
style="background-
color:#FFF5EE;">
<h1>HOSPITAL
MANAGEMENT
SYSTEM</h1>
<h3
align="center">ADMIN
PANEL</h3>
</td>
</tr>
<tr>
<td style="background-
color:#00FFFF;width:50
px;height:400px;">
<table align="center">
<tr>
<td><form
action="nurse.php"
align="center">
<input type="submit"
align="center" value="
nurse
">
</form></td>
</tr>
<tr>
<td><form
action="patient.php"
align="center">
<input type="submit"
align="center" value="
patient
">
</form></td>
</tr>
<tr>
<td><form
action="pharmacist.php
" align="center">
<input type="submit"
align="center" value="
pharamacist
">
</form></td>
</tr>
<tr>
<td><form
action="laboratorist.php
" align="center">
<input type="submit"
align="center" value="
laboratorist
">
</form></td>
<tr>
<td><form
action="accountant.php
" align="center">
<input type="submit"
align="center" value="
accountant
">
</form></td>
</tr>
</table>
</td>
<td style="background-
color:#eeeeee;height:20
0px;width:400px;height:
400px;">
<?php
$host='localhost';
$username='root';
$password='';
$dbname='hospital';
$con=mysql_connect($h
ost,$username,
$password);
mysql_select_db($dbna
me);
$result =
mysql_query("SELECT *
FROM doctor");
echo "<h4
align='center'> doctors
list </h4>";
echo "<table border=1
align=center><tr><th>
s.no</th><th>name</
th><th>d_id</
th><th>qualification</
th><th>speciality</
th><th>age</th
></tr>";
while($row =
mysql_fetch_array($resu
lt))
{
echo "<tr>";
echo "<td>" .
$row['s_no'] . "</td>";
echo "<td>" .
$row['name'] . "</td>";
echo "<td>" .
$row['d_id'] . "</td>";
echo "<td>" .
$row['qualification'] .
"</td>";
echo "<td>" .
$row['speciality'] .
"</td>";
echo "<td>" .
$row['age'] . "</td>";
echo "</tr>";
}
echo "</table>";
mysql_close($con);
?>
<br><br>
<table align="right">
<th>
<tr>
<form
action="adddoctor.php"
align="center">
<input type="submit"
align="center" value="
add new
doctor ">
</form>
</tr>
<tr>
<form
action="deletedoctor.ph
p" align="center">
<input type="submit"
align="center" value="
delete
doctor ">
</form></tr>
<tr>
<form
action="viewcompleted
octor.php"
align="center">
<input type="submit"
align="center" value="
viewcomplete ">
</form>
</tr>
<tr>
<form
action="admin.html"
align="center">
<input type="submit"
align="center" value="
home ">
</form>
</tr></table>
</td>
</tr><tr>
<td colspan="2"
style="background-
color:#9ACD32;text-
align:center;">
<table align="right">
<th>
<tr><form
action="appointment.ph
p" align="center">
<input type="submit"
align="center" value="
appointment ">
</form>
</tr><tr><form
action="payment.php"
align="center">
<input type="submit"
align="center" value="
payment
">
</form>
</tr><tr><form
action="bloodbank.php"
align="center">
<input type="submit"
align="center" value="
bloodbank
">
</form>
</tr><tr>
<form
action="medicine.php"
align="center">
<input type="submit"
align="center" value="
medicine
">
</form>
</tr><tr><form
action="operations.php"
align="center">
<input type="submit"
align="center" value="
operations
">
</form>
</tr><tr>
<form
action="birthreport.php"
align="center">
<input type="submit"
align="center" value="
birthreport
">
</form>
</tr><tr><form
action="deathreport.ph
p" align="center">
<input type="submit"
align="center" value="
deathreport
">
</form>
</tr><tr><form
action="bedallotment.p
hp"
align="center">
<input type="submit"
align="center" value="
bedallotment ">
</form>
</tr></th> </table>
</td></tr></table>
</body>
</html>
Appointment.php
<!DOCTYPE html>
<html>
<body>
<table width="1350"
height="640"
border="1" ><tr>
<td colspan="2"
style="background-
color:#FFF5EE;">
<h1>HOSPITAL
MANAGEMENT
SYSTEM</h1>
<h3
align="center">DOCTO
R PANEL</h3>
</td>
</tr>
<tr>
<td style="background-
color:#00FFFF;width:50
px;height:400px;">
<table align="center">
<tr> <td><form
action="docappointmen
t.php"
align="center">
<input type="submit"
align="center" value="
Appointment ">
</form> </td></tr>
<tr> <td><form
action="docperscription.
php"
align="center">
<input type="submit"
align="center" value="
perscription ">
</form> </td> </tr>
<tr> <td> <form
action="docoperation.p
hp"
align="center">
<input type="submit"
align="center" value="
Operation
">
</form> </td></tr>
<tr> <td><form
action="docmedicines.p
hp.php"
align="center">
<input type="submit"
align="center" value="
Add
Medicines ">
</form></td></tr>
<tr> <td> <form
action="doctests.php"
align="center">
<input type="submit"
align="center" value="
Add Tests
">
</form></td>
</table>
</td>
<td style="background-
color:#eeeeee;height:20
0px;width:400px;height:
400px;">
<h2 align="center">
Appointments </h2>
<?php
$host='localhost';
$username='root';
$password='';
$dbname='hospital';
$con=mysql_connect($h
ost,$username,
$password);
mysql_select_db($dbna
me);
$result =
mysql_query("SELECT *
FROM appointment
WHERE d_id='$a'");
echo "<table border=1
align=center> <tr>
<th>s.no</th>
<th>pid</th>
<th>name</th>
<th>problem</th>
<th>date</th>
<th>time</th>
<th>status</th> <th>
update</th> </tr>";
while($row =
mysql_fetch_array($resu
lt))
{
echo "<tr>";
echo "<td>" .
$row['s_no'] . "</td>";
echo "<td>" .
$row['p_id'] . "</td>";
echo "<td>" .
$row['name'] . "</td>";
echo "<td>" .
$row['problem'] .
"</td>";
echo "<td>" .
$row['date_of_app'] .
"</td>";
echo "<td>" .
$row['time_of_app'] .
"</td>";
echo "<td>" .
$row['status'] . "</td>";
echo "<td>" ;?> <form
action="updateappoint
ment.php"
align="center"
method="POST">
<input type="hidden"
name="sno" value=" <?
php echo
$row['s_no']; ?> ">
<input type="hidden"
name="pid" value=' <?
php echo
$row['p_id']; ?> '>
<input type="submit"
align="center" value="
update
">
</form> <?php echo
"<td>";
echo "</tr>";
}
echo "</table>";
mysql_close($con);
?>
<br><br>
<table align="center">
<tr>
<td><form
action="allappointment.
php" align="center">
<input type="submit"
align="center" value="
all
Appointment ">
</form> </td>
<td><form
action="pendingappoint
ment.php"
align="center">
<input type="submit"
align="center" value="
pending
Appointment ">
</form> </td>
<td> <form
action="upcomingappoi
ntment.php"
align="center">
<input type="submit"
align="center" value="
upcoming
appointment ">
</form> </td>
<td><form
action="completedappoi
ntment.php"
align="center">
<input type="submit"
align="center" value="
completed
Appointment ">
</form></td></table>
</td></tr>
<tr>
<td colspan="2"
style="background-
color:#9ACD32;text-
align:center;">
<table align="center">
<tr> <td> Doctor name
</td> <td>
</td> <td> Doctor id
</td> <td> </td>
</tr> </table>
</td></tr>
</table></body></
html>
CHAPTER NO 8
TESTING
8.1 INTRODUCTION TO
SYSTEM 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
unacceptable manner.
There are various types
of test. Each test type
addresses a
specific testing
requirement.
TYPES OF TESTING:
Unit testing:
Unit
testing involves the
design of test
cases that validate that
the internal program
logic is
functioning properly,
and that program inputs
produce
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.
Integration testing:
Integration tests are
designed to test
integrated software
components to
determine if they
actually run as one
program. Testing is
event driven and
is more concerned with
the basic outcome of
screens or
fields. Integration tests
demonstrate that
although the
components were
individually satisfaction,
as shown by
successfully unit testing,
the combination of
components
is correct and
consistent. Integration
testing is specifically
aimed at exposing the
problems that arise from
the
combination of
components.
Functional test:
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.
Organization and
preparation of
functional tests is
focused on
requirements, key
functions,
or special test cases. In
addition, systematic
coverage
pertaining to identify
Business process flows;
data fields,
predefined processes,
and successive
processes must be
considered for testing.
Before functional testing
is
complete, additional
tests are identified and
the effective
value of current tests is
determined.
System Test:
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.
White Box Testing:
White Box Testing is a
testing in which in which
the
software tester has
knowledge of the inner
workings,
structure and language
of the software, or at
least its
purpose. It is purpose. It
is used to test areas that
cannot
be reached from a black
box level.
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. Black box tests,
as most other
kinds of tests, must be
written from a definitive
source
document, such as
specification or
requirements document,
such as specification or
requirements document.
It is a
testing in which the
software under test is
treated, as a
black box .you cannot
“see” into it. The test
provides
inputs and responds to
outputs without
considering how
the software works.
Unit Testing:
Unit testing is usually
conducted as part of a
combined
code and unit test phase
of the software lifecycle,
although
it is not uncommon for
coding and unit testing
to be
conducted as two
distinct phases.
Test strategy and
approach
Field testing will be
performed manually and
functional
tests will be written in
detail.
Test objectives

All field entries must
work properly.

Pages must be activated
from the identified link.

The entry screen,
messages and
responses must not be
delayed.
Features to be tested

Verify that the entries
are of the correct format

No duplicate entries
should be allowed

All links should take the
user to the correct page.
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.
Test Results:
All the test cases
mentioned above
passed successfully. No
defects encountered.
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.
Test Results: All
the test cases
mentioned above
passed successfully. No
defects encountered.
CHAPTER NO 9
SAMPLE SCREENSHOTS
LOGIN PAGE:

ADMIN PANEL:
ADDING NEW EMPLOYEE
DETAILS:
Doctor module:

Operation details:
Create operation
details:
Add employee details:
Bed allotment:
Patient registration
form:
Blood status:
Appointments:
CHAPTER NO 10
CONCLUSION AND
LIMITATIONS
The project Hospital
Management System
(HMS) is for
computerising the
working in
a hospital. lt is a great
improvement over
the manual system.
The computerisation
of the system has speed
up the process. In
the current system, the
front office
managing is very slow.
The hospital
managing system was
thoroughly checked
and tested with dummy
data and thus is
found to be very
reliable. The software
takes care of all the
requirements of an
average hospital and is
capable to provide
easy and effective
storage of information
related to patients that
come up to the
hospital.
lt generates test
reports and provides
the facility for searching
the details of the
patient. lt also provides
billing facility on
the basis of patient’s
status whether it is
an indoor or outdoor
patient. The system
also provides the facility
of backup as per
the requirement.
LIMITATIONS:
•
The size at the database
increases day-
by-day, increasing the
load on the
database back up
and data maintenance
activity.
•
Training Our sin ple
computer up
creations is necessary
Our the
•
users working on the
system.
CHAPTER NO:- 11
BIBLOGRAPHY
1. PHP MySQL Website
Programming: Problem -
Design – Solution
byChris
Lea, Mike Buzzard,
Dilip Thomas , Jessey
White-Cinis
2. Beginning PHP5,
Apache, and MySQL
Web
Development
(Programmer to
Programmer) by
Elizabeth Naramore
3. MySQL/PHP Database
Applications, 2nd Edition
by Brad Bulger
4. How to Do Everything
with PHP and
MySQL by Vikram
Vaswani
Web References
1.
www.google.com
2.
www.slideshare.com
3.
www.yahoo.com