HOSPITAL MANAGEMENT SYSTEM
Aditya Mishra, Snehil Aryan, Trinabh Chokhani, Vedant Mehrotra
Keywords: Hospital management system, data
structures, HTML, PHP
Abstract
1.Introduction
1.1 Basic Introduction
The project Hospital Management system
includes registration of patients, storing
their details into the system, and also
computerized billing in the pharmacy, and
labs. The software has the facility to give
a unique id for every patient and stores the
details of every patient and the staff
automatically. It includes a search facility
to know the current status of each room.
User can search availability of a doctor
and the details of a patient using the id.
The Hospital Management System can be
entered using a username and password. It
is accessible either by an administrator or
receptionist. Only they can add data into
the database. The data can be retrieved
easily. The interface is very user-
friendly.The data are well protected for
personal use and makes the data
processing very fast.
Hospital Management System is
powerful, flexible, and easy to use and is
designed and developed to deliver real
conceivable benefits to hospitals.
Hospital Management System is designed
for multispecialty hospitals, to cover a
wide range of hospital administration and
management processes. It is an
integrated end-to-end Hospital
Management System that provides
relevant information across the hospital to
support effective decision making for
patient care, hospital administration and
critical financial accounting, in a seamless
flow.
Hospital Management System is a
software product suite designed to
improve the quality and management of
hospital management in the areas of
clinical process
1.3 Modules
analysis and activity-based costing. Hospital ∙
Management System enables you to ∙
develop your organization and improve its ∙
effectiveness and quality of work.
Managing the key processes efficiently is 2.
critical to the success of the hospital helps
you manage your processes 2.1
Hos
for
1.2 Problem Introduction the
crit
(a)Lack of immediate retrievals: - info
The information is very difficult to retrieve num
spre
and to find particular information like- E.g. man
- To find out about the patient’s history, the infr
inco
user has to go through various registers. man
This results in inconvenience and wastage stan
of time. betw
(b)Lack of immediate information com
storage: - that
The information generated by various cop
transactions takes time and efforts to be hos
data
stored at right place. stor
(c)Lack of prompt updating: -
Various changes to information like patient 2.2
details or immunization details of child are The
difficult to make as paper work is involved. Three key considerations involved in the
(d)Error prone manual calculation: - designed
feasibility
for any
analysis
hospital
are:to replace their
Manual calculations are error prone and existing
3.3.1 manual
Economic paper based system. The
Feasibility
new system is to control the information
take a lot of time this may result in incorrect of This study is carried out to check the
patients. Doctor’s
economic impactdetails, common
will have on the system
information. For example, calculation of will have on the organization. The amount
diseases
patient’s bill based on various treatments. andoftheir fundcauses
that the
andcompany
symptoms.can These
pour into the
(e)Preparation of accurate and prompt services research
are and
to bedevelopment
provided in ofanthe system is
efficient,
reports: - costlimited.
effective The
manner,expenditures
with the goalmust
of be
justified.
This becomes a difficult task as information reducing Thusand
the time theresources
developed system as
currently
well for
is difficult to collect from various register. required within
such the
tasks.budget and this was
∙Appointment achieved because most of the technologies
∙Ambulance used are freely available. Only the
∙Addition of Doctor’s name customized products have to be
∙Diseases purchased.
3.3 Feasibility study
3.3.2 Technical Feasibility
The feasibility of the project is analyzed in
this phase and business proposal is put This study is carried out to check the
forth with a very general plan for the technical feasibility, that is, the technical
project and some cost estimates. During requirements of the system. Any system
system analysis developed must not have a high demand
on the 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.

3.3.3 Operational Feasibility

The aspect of study is to check the level of

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.
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.

3. Design
Before we started writing the code for the
program, we needed to have a clear idea of
how to work through the problem set. So
for that purpose, we decided to draw some
diagrams.

functionality provided by a system in

Fig1: Use Case diagram
A use case diagram in the is a type of
behavioral diagram defined by and created
from a use-case analysis. Its purpose is to
present a graphical overview of the
terms of actors, their goals (represented as
use cases), and any dependencies between
those use cases.
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.
Fig2: Collaboration Diagram
desktop Client
Printer

Hospital Local Server

Database Server

Fig3: Deployment 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.

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-
shapedthan 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
bull’s eye.
5.1.2 Integration Testing
Fig4: State Diagram
4. System Implementation
problem will take huge space, it has not
been included in this report.
5. 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.
5.1 Types of Testing 5.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 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
fter the completion of an individual unit
Implementation is the stage of the
project before integration. This is a
structural when the theoretical design is
turned out testing, that relies on
knowledge of its into a working system.
Thus it can be construction and is
invasive. Unit tests considered to be the
most critical stage in perform basic tests at
component level and achieving a
successful new system and in test a
specific business process,
application, giving the user, confidence
that the new and/or system configuration.
Unit tests system will work and be
effective. The ensure that each unique
path of a business implementation stage
involves careful process performs
accurately to the planning, investigation
of the existing documented specifications
and contains
system and its constraints on clearly
defined inputs and expected results.
implementation, designing of methods to
achieve changeover and evaluation of
changeover methods. As the code of the
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.
Before functional testing is complete,
additional tests are identified and the
effective value of current tests is
a determined.
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.
5.1.3Functional test
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, allotment for the admitted patients and the
and successive processes must be stock details of medicines in the
considered for testing. pharmacy. Providing such features enable
Features to be tested the users to include more comments into
the system
∙Verify that the entries are of the correct
format Acknowledgements
∙No duplicate entries should be allowed It is indeed with a great pleasure and
∙All links should take the user to the correct immense sense of gratitude that we
acknowledge the help DR Himanshu
page. Chaudhary for giving us the opportunity
to make this project.
Test Results:
∙All the test cases mentioned above passed References
successfully. No defects encountered. www.w3school.com
www.tutorialpoint.com
6.Conclusions
The Hospital Management System is a
great improvement over the manual
system using case fields and paper. The
computerization of the system has sped 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
ADVANTAGES:
∙It is fast, efficient and reliable
∙Avoids data redundancy and
inconsistency
∙Web-based
∙Number of personnel required is
considerably less
∙Provides more security and integrity to
data
Future Enhancements:
The proposed system is Hospital
Management System. We can enhance
this system by including more facilities
like billing system, inpatient room