HOSPITAL MANAGEMENT SYSTEM

1
 Index
1. Introduction
2. Objectives
3. System Requirements
4. Feasibility Study
5. Functional & Non-Functional Requirements
6. Software Requirement Specification
7. Entity-relationship Diagram
8. Data Flow Diagram
9. Use case Diagram
10. Data dictionary
11.User Interface
12.Ghantt Chart
13.Testing
14.Conclusion
15.Future Scope
16.References

2
 INTRODUCTION

The project of Hospital Management System includes the registration of patient

and the doctor. The management of the hospital concerned with the increasing
effort in keeping the record of patient and recording their activities. The hospital
also keeps the information of the employees. Management and information
system, which may keep the record of each patient, employee and medicine.
The hospital treats both indoor and outdoor patients. It has to maintain full
information of the indoor patients as well as outdoor patients for the purpose of
historical use. The software has the facility to give a unique id to every patient
and every doctor and store the detail of the patients and doctors in the system.
The user can search the availability of the doctor and detail of the patient by
using the particular id. The hospital management system can be entered using
the user name and the password. It is accessible either by administrator’s or
receptionist. Only they can add the data with the database. The data can be
retrieved easily. The interface is user friendly. Help human hospital has a group
of social and professional people as director and manager in its management,
who provide a personal as well as professional touch to the overall working of
the hospital. Proper guidelines and objectives are laid down for every process
and section of the hospital which result ensuring satisfaction of the patient.

3
 OBJECTIVES

The software is for the automation of hospital management.

It maintains two level of user-
1. Administrator level
2. User level
The Software includes-
Maintaining patient detail.
 Providing and maintain all kind of test for a patient.
 Billing and report generation.
 Maintenance record of indoor and outdoor patient.
 Result of test will be automatically updated in the database.
 User or administrator cab search patient’s record by his/her name or their
registration date.
 Information about the patient is done by just writing patient’s name and id
whenever the patient comes up the information in the store freshly.
 Information about the doctor is also done by writing the name of the doctor
and his/her id.

4
 SYSTEM REQUIREMENTS

Hardware Required:-
 Processor –Intel® Atom™ Processor N2600 (1M Cache, 5.6 GHz)
 RAM – 1 GB
 HDD -200 GB ( For installing)

Software Required :-
 Operating system window 7 Ultimate SPI
 Windows 7 or higher version installer
 Microsoft .Net Framework 4
 Microsoft SQL Server 2013

5
 FEASIBILITY STUDY

Feasibility Study Depending on the results of the initial investigation the survey
is now expanded to a more detailed feasibility study. “FEASIBILITY STUDY”
is a test of system proposal according to its workability, impact of the
organization, ability to meet needs and effective use of the resources. It focuses
on these major questions:
 What are the user’s demonstrable needs and how does a candidate system
meet them?
 What resources are available for given candidate system?
 What are the likely impacts of the candidate system on the organization?
 Whether it is worth to solve the problem?
 During feasibility analysis for this project, following primary areas of
interest are to be considered.
 Investigation and generating ideas about a new system does this.
Steps in feasibility analysis: Eight steps involved in the feasibility analysis are:
1) Form a project team and appoint a project leader.
2) Prepare system flowcharts.
3) Enumerate potential proposed system.
4) Define and identify characteristics of proposed system.
5) Determine and evaluate performance and cost effective of each proposed
system.
6) Weight system performance and cost data.
7) Select the best-proposed system.
8) Prepare and report final project directive to management.
Technical Feasibility
A study of resource availability that may affect the ability to achieve an
acceptable system. This evaluation determines whether the technology needed
for the proposed system is available or not.
1) Can the work for the project be done with current equipment existing
software technology & available personal?
2) Can the system be upgraded if developed?

6
3) If new technology is needed then what can be developed?
4) This is concerned with specifying equipment and software that will
successfully satisfy the user requirement.
The technical needs of the system may include:
Front-end and back-end selection
An important issue for the development of a project is the selection of suitable
front-end and back-end. When we decided to develop the project, we went
through an extensive study to determine the most suitable platform that suits the
needs of the organization as well as helps in development of the project. The
aspects of our study included the following factors.
Front-end selection:
1) It must have a graphical user interface that assists employees that are not
from IT background.
2) Scalability and extensibility.
3) Flexibility.
4) Robustness.
5) According to the organization requirement and the culture.
6) Must provide excellent reporting features with good printing support.
7) Platform independent.
8) Easy to debug and maintain.
9) Event driven programming facility.
10) Front end must support some popular back end like Ms Access. According
to the above stated features we selected VB6.0 as the front-end for developing
our project. Hospital Management System
Back-end Selection:
1) Multiple user support.
2) Efficient data handling.
3) Provide inherent features for security.
4) Efficient data retrieval and maintenance.
5) Stored procedures.

7
6) Popularity.
7) Operating System compatible.
8) Easy to install.
9) Various drivers must be available.
10) Easy to implant with the Front-end. According to above stated features we
selected Ms-Access as the backend. The technical feasibility is frequently the
most difficult area encountered at this stage. Itis essential that the process of
analysis and definition be conducted in parallel with an assessment to technical
feasibility. It centre on the existing computer system (hardware, software etc.)
and to what extent it can support the proposed system.
Economical Feasibility
Economic justification is generally the “Bottom Line” consideration for most
systems. Economic justification includes a broad range of concerns that
includes cost benefit analysis. In this we weight the cost and the benefits
associated with the candidate system and if it suits the basic purpose of the
organization i.e. profit making, the project is making to the analysis and design
phase. The financial and the economic questions during the preliminary
investigation are verified to estimate the following:
1) The cost to conduct a full system investigation.
2) The cost of hardware and software for the class of application being
considered.
3) The benefits in the form of reduced cost.
4) The proposed system will give the minute information, as a result the
performance is improved which in turn may be expected to provide increased
profits.
5) This feasibility checks whether the system can be developed with the
available funds. The Hospital Management System does not require enormous
amount of money to be developed. This can be done economically if planned
judicially, so it is economically feasible. The cost of project depends upon the
number of manhours required.
Operational Feasibility
It is mainly related to human organizations and political aspects. The points to
be considered are:

8
1) What changes will be brought with the system?
2) What organization structures are disturbed?
3) What new skills will be required? Do the existing staff members have these
skills? If not, can they be trained in due course of time?
4) The system is operationally feasible as it very easy for the End users to
operate it. It only needs basic information about Windows platform.
Schedule Feasibility
Time evaluation is the most important consideration in the development of
project. The time schedule required for the developed of this project is very
important since more development time effect machine time, cost and cause
delay in the development of other systems.
A reliable Hospital Management System can be developed in the considerable
amount of time.

9
 FUNCTIONAL REQUIREMENT

Registration
 Add patients- The hospital management system shall allow front-desk staff to
add new patient to the system.
 Assign Id- The hospital management shall allow front desk staff to give each
patient a id and add it to the patient’s record. This id shall be used by the patient
through out his/her stay in hospital.
Report Generation
 Patients information- The hospital management system shall generate report
on patient about the following information like patient’s name, patient’ phone
number and doctor name which was assigned.
Database
 Patient Mandatory Information- Each patient shall have the following
mandatory information like first name, last name, phone number , address, city,
patient number.
 Update patient information- It shall allow the user to update any of the patient
information as described in SRS 007.
Technical issue
 Database- The system shall the MySQL Database which is open source and
free.
 Operating System- Operating System window 7 ultimate SPI.

10
 NON-FUNCTIONAL REQUIREMENT
Performance
 Response time – This system shall give response in one second after checking
the patient information.
 User Interface – The user interface screen shall report within a 5 sec.
 Conformity – The system must conform to the Microsoft Accessibility.

11
 SOFTWARE REQUIREMENT SPECIFICATION

The SRS is produced at the culmination of the analysis task. The function and
performance allocated to software as part of the system engineering and
redefine by establishing a complete information description, a detail functional
description, a representation of system behaviour indication of performance
requirement and design constrains, appropriate validation criteria and the other
information related to the requirement.
The SRS is technical specification requirement of the Hospital Management
System. This specification describes what the proposed system should do
without describing how it will do it. It describes complete external behaviour of
proposed system.
Purpose- The main purpose of our system is to make hospital task easy and is to
develop software that replaces the manual hospital system into automated
hospital management system. This document serves as the unambiguous guide
for the developer of this software system.
Scope-This document only cover the requirement specification for the hospital
management system. This document does not provide any references in the
other component of the hospital management system.

12
ENTITY RELATIONSHIP DIAGRAM

13
 DATA FLOW DIAGRAMS

The data flow diagram is a graphical representation of the flow of the data
through an information system. Data flow diagram are used by system analysis
to design information processing system but also as a way to model whole
organisation. The main merit of DFD is that it can provide an overview of what
data a system would process, what information of data are done, which data are
stored and which data is used and where the result is flowed.

14
ZERO LEVEL DIAGRAM

15
1ST-LEVEL DIAGRAM

16
2ND LEVEL DIAGRAM

17
USE-CASE DIAGRAM

18
 DATA DICTIONARY
HOSPITAL

ATTRIBUTE DATA TYPE

Hosp_id Int not null

Hos_name Varchar(20)

HAddress Varchar(20)

HCity Varchar(20)

DOCTOR
DATA TYPE
ATTRIBUTE

Doc_id Int not null

DNAME Varchar(20)

Qualification Varchar(20)

Salary Number(20)

19
PATIENT

ATTRIBUTE DATA TYPE

Pat_id Int not null

PName Varchar(20)

PAddress Varchar(40)

Pdiagnosis Varchar(40)

MEDICAL RECORD

ATTRIBUTE DATA TYPE

Date_of_Examination Date

Record_id Int not null

Problem Varchar(100)

20
 USER INTERFACE
There are many factors that must be considered when designing the user
interface of a software because the user must be able to interact with the system
in away that the system will understand whatever the input given by the user.
Therefore, the quality of the interface and software in general must pass the us
ability testing standard. Some usability factors, such as fit for use, ease of
learning, task efficiency, ease to remember, subjective satisfaction and under
standability but all be put into consideration when designing the user interface. .
The application will have a user friendly and menu based interface,. Following
screens will be provided
 A Login Screen for entering user name, password , administrator will be
provided. Access to different screen will be based upon the role of the user.
 A form for search the details of patient.
 The form for creating a new patient record will contain text field where the
Patient id will be generated automatically and the rest of the detail will have to
be filled up.
 A form the creating a new doctor record will contain text field where the
Doctor id will be generated automatically and the rest of the details will have to
filled up.
 The form to produce a bill create fields such as Patient Id, Doctor’s charges
and the medicine charges.

21
GHANTT CHART

22
 TEST PROCEDURE

Test procedure helps in assuring software quality. The purpose of test procedure
is a quality assurance, verification and validation. Basically testing procedure is
an investigation conducted to provide information about quality of product or
services. It ensures that doctors can access their id any time and patient can
check or update his treatment detail any time. Testing is the process of
executing a program with the intention of finding errors. It is used to represent
the ultimate review of specification, design, coding. Different test conditions
should be thoroughly checked and the bugs detected should be fixed. Testing in
hospital management system are fallowed as –
1. Unit testing- Unit testing plays a crucial role in early phase of software
testing life cycle which helps in detection bugs; and once properly
planned and executed, it reduces cost of quality. However, if unit tests are
not written well, or they are executed incorrectly, bugs go through into
the production phase. This oversight can cost a company thousands, if not
hundreds of thousands of dollars depending on the scale of the project.
Unit testing needs a deep expertise of looking into code with various
perspectives such as Code coverage, Loop coverage, Branch coverage,
Condition coverage, and Fuzzing code to predict its expected failure,
predefined negative tests while developing code . This involves not just
insights into code, but a much-required methodological approach towards
testing the code for its afferent and efferent coupling.

Testing Goal -Dots squares unit testing service goal is to catch as many
bugs early in the development as possible. This is achieved by writing
accurate and quality unit tests, while at the same time providing detailed
documentation for the development process. This ensures that bugs and
inconsistencies we detect early in the development stage, can be re-
factored by the development team. We work intimately with your team to
thoroughly ensure all project goals are met on time and within budget.

Benefits of Unit Testing –

 Finding problems early -Unit tests find problems early in the
development cycle.

23
  Facilitate change -Allows the programmer to re-factor code during the
testing process and at a later date, while making sure the module still
works correctly.
 Simplify integration -By testing the parts of a program first and then
testing the sum of its parts, integration testing becomes much easier.
 Documentation -Developers looking to learn the result of a unit test can
look at the unit test documentation to gain a better understanding.
 Design-Each unit test can be seen as a design element specifying
classes, methods, and observable behaviours during the project life-cycle.

2. Integration testing - We normally do Integration after unit testing. Once

all the individual units are created and tested, we start combining those
“Unit Tested” modules and start doing the integrated testing. So the
meaning of Integration testing is quite straight forward.
Integrate/combine the unit tested module one by one and test the
behaviour as a combined unit.
Testing goal -The main function or goal of Integration testing is to test
the interfaces between the units/modules. The individual modules are first
tested in isolation. Once the modules are unit tested, they are integrated
one by one, till all the modules are integrated, to check the combinational
behaviour, and validate whether the requirements are implemented
correctly or not.

Here we should understand that, Integration testing does not happen at

the end of the cycle, rather it is conducted simultaneously with the
development. So, in most of the times all the modules are not actually
available to test and here is what the challenge comes to test something
which does not exist
There are fundamentally 2 approaches for doing Integration testing:
 Bottom up approach
 Top down approach.

Black box testing

Black Box testing is a software testing technique in which functionality
of the software under test (SUT) is tested without looking at the internal
code structure, implementation details and knowledge of internal paths of
the software. This type of testing is based entirely on the software
requirements and specifications.
Black box testing –
24
 Steps Here are the generic steps followed to carry out any type of Black
Box Testing.
 Initially requirements and specifications of the system are examined.
 Tester chooses valid inputs (positive test scenario) to check whether
SUT processes them correctly. Also, some invalid inputs (negative test
scenario) are chosen to verify that the SUT is able to detect them.
 Tester determines expected outputs for all those inputs.
 Software tester constructs test cases with the selected inputs.
 The test cases are executed.
 Software tester compares the actual outputs with the expected outputs.
 Defects if any are fixed and re-tested.
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent
ones –
 Functional testing - This black box testing type is related to functional
requirements of a system; it is done by software testers.
 Non-functional testing - This type of black box testing is not related to testing
of a specific functionality, but non-functional requirements such as
performance, scalability, usability.
 Regression testing - Regression testing is done after code fixes, upgrades or
any other system maintenance to check the new code has not affected the
existing code.

25
 CONCLUSION
The project Hospital management system is for computerizing the working in a
hospital. 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. It is great improvement over the manual
system has speed up the process. The hospital managing system thoroughly
checked and tested with the data and thus is found reliable. The software takes
care of all the requirement of an average hospital and is capable to provide easy
and efficient storage of information related to patients that comes up to the
hospital .It generates test reports; provide prescription details including various
tests, diet advice, and medicines prescribed to patient and doctor. It also
provides injection details and 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. The system is secure as a user can modify the
information only after the proper authentication. Chances of error are also
eliminated to large extent. Computerization and automation of the whole system
helps in easy and fast access to the required information. The system is highly
user friendly as appropriate message are provided to guide the user logged in.

26
 SCOPE OF FUTURE WORK
The hospital management system can enhance by including more facility like
pharmacy system for the stock details of medicine in pharmacy. Providing each
future enable the users to include more comment in the system. Although the
project is complete in itself but as there is always a future scope for
improvement; the same applies to this software. The provision for getting
appointment from the doctor through Internet, i.e., Online Appointment facility
can be added. The doctor could view the requests from several patients and
accordingly give the appointment if possible. Further, Mobile Application can
be implemented to allow the patients to view their previous visit details and get
appointment from doctors through mobiles. Posting of employees from one
hospital to another can also be managed. Further, doctors can be given the
provision to post their articles on the website of hospital. It generates test
reports; provide prescription details including various tests, diet advice, and
medicines prescribed to patient and doctor. It also provides injection details and
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.

27
 REFERENCES

 www.unacademy.com
 www.projects.com
 www.howstuffworks.com

28