A PROJECT REPORT FOR DEPICTION OF

HOSPITAL MANAGEMENT
SYSTEM

SUBMITTED BY:

KANIKA SHRIDHAR
SANIA MAHAJAN
KUNAL GUPTA

1
 INTRODUCTION

The " HOSPITAL MANAGEMENT " system forms a basic

entity of the management of a Hospital. Hence, it is very
important for the system to be reliable, user friendly, and
should be properly functional for a long time without
cropping up of any errors.

To start with the system study we visited Bhagat Hospital in

Janak Puri. There we took the help of Dr. C.M. Bhagat. He
showed us the project which he is using in his daily life for
management of his hospital. This project gave me the idea of
the different fields that ought to be in a Hospital
Management System such as patient registration, his/her
advance payment, the records, the details etc.. and also that
how a software system can make the work easy both for the
hospital staff and the patient. Moreover, the evaluation
helped me to arrive at the conclusion that the automated
software are far more superior to the manual ones.

The database structure was then taken into account based on

the input and output data. The ERD's (Entity Relationship
Diagram) and the DFD's (Data Flow Diagrams) and various
flowcharts are also drawn showing the flow of information
and data.

2
 CERTIFICATE

This is to certify that the project entitled “HOSPITAL

MANAGEMENT” submitted by Kanika Shridhar , Sania
Mahajan and Kunal Gupta has been carried out under our
supervision. The project is submitted in fulfillment of the
requirement for the 4th semester of Computer Sc. (H).

Teacher-in-charge

3
 ACKNOWLEDGEMENT

On the successful completion of our project entitled

“HOSPITAL MANAGEMENT”, we would like to express
our sincere gratitude to everyone who helped us throughout
in the making of this report.

We are sincerely thankful to Ms. Bhawna, the Project

Incharge, for being the constant source of help, knowledge
and encouragement.

We express our sincere gratitude to Ms. Deepali for her co-

operation and are thankful to Ms. Anita and Mr. Negi for
their help in gathering the software tools required for the
project.

Kanika Shridhar

Sania Mahajan

Kunal Gupta

4
 CONTENTS

1. SYSTEM REQUIREMENT

2. REQUIREMENT SPECIFICATION

3. FLOWCHARTS

4. ANALYSIS MODELING

5. TEST PLAN

6. FUTURE ENHANCEMENTS

7. BIBLIOGRAPHY

8. SUGGESTIONS

5
 SYSTEM
REQUIREMENT

1. FUNCTIONAL REQUIREMENTS
2. NON- FUNCTIONAL REQUIREMENTS

SYSTEM REQUIREMENT

1. FUNCTIONAL REQUIREMENTS

The software is to atomize the Hospital Management:

 The user is the non-remedial staff such as receptionist.

6
 The system should provide the facility for storing the
information in the database and hence perform
modification as required.

 The system should have a user-friendly interface so that

the user can adapt to the new system easily.

 The database should be reliable and developed such that if

at some time later stage the software has to be upgraded,
the database is not affected.

2. NON – FUNCTIONAL REQUIREMENTS

 EFFICIENCY: The software should not make wasteful use

of the system resources such as memory and processor
cycles. The response time should be kept minimum.

 PORTABILITY: The software should be portable and not

hardware dependent.

 DELIVERY OF THE SYSTEM: The project should be

completed within a period of one month.

7
REQUIREMENT
SPECIFICATION

8
 REQUIREMENT SPECIFICATION

 HOSPITAL MANAGEMENT

1. REGISTRATION: Register the patient. Provide the

facility for adding new patient details and modify the record
or print the record if necessary.

2. FACILITIES: Services provided by the hospital to the

patient.
 Doctors Codification: The details of the doctor
dealing with the patient.
 Beds Codification: Information about the room
type, bed type and charges.

3. MEDICAL RECORDS:
 Diagnosis: The disease which the patient is suffering
from is diagnosed.
 Treatment: It deals with the treatment done by the
doctor for a particular patient.

9
4. RECORD:
 Admission – Discharge record
 Charges / Bills :
• Visiting fees
• Diagnosis charges
• Treatment charges
• Miscellaneous charges

FLOWCHARTS
1. PATIENT REGISTRATION
2. BEDS CODIFICATION
3. DOCTORS CODIFICATION
4. DIAGNOSIS AND TREATMENT
5. MISCELLANEOUS CHARGES

10
11
PATIENT REGISTRATION

START

REGISTER THE
PATIENT

ENTER PATIENT
DETAIL

ENTER ROOM NO

NO
IS
ROOM
EMPTY
E

YES

ASSIGN DOCTOR

STOP

12
 BEDS CODIFICATION

START

ENTER
CODE

MODIFY
THE INSERT ROOM TYPE, PRINT THE
RECORD BED TYPE AND RECORD
CHARGES

SEARCH
THE
GENERATE THE BILL RECORD

STOP

13
 DOCTORS CODIFICATION

START

ENTER
CODE

MODIFY INSERT DOCTOR’S

DETAILS AND VISIT PRINT THE
THE RECORD
RECORD CHARGES TYPE, BED
TYPE AND CHARGES

SEARCH
THE
GENERATE THE BILL RECORD

STOP

14
 DIAGNOSIS AND TREATMENT

START

ENTER
CODE

MODIFY INSERT
TREATMENT PRINT THE
THE RECORD
RECORD DETAILS AND
CHARGES HARGES

SEARCH
THE
GENERATE THE BILL RECORD

STOP

15
 MISCELLANEOUS CHARGES

START

ENTER
CODE

MODIFY INSERT
MISCELLANEOUS PRINT THE
THE RECORD
RECORD ITEMS AND THEIR
CHARGES HARGES

SEARCH
THE
GENERATE THE BILL RECORD

STOP

16
ANALYSIS
MODELING
1. ERD
2. DFD
3. DATA DICTIONARY

17
 ENTITY
RELATIONSHIP
DIAGRAM

18
 Bill
Reciept Date
no. Amount
A.C. &
Canteen
Heater
All Final Bill
Charge
s

Facilities
available Patient Patient
Name ID

Diagnosis,
Avail Patient Treatmen
facilities t

Registere Doctor
d

Room
No. Doctor Doctor
ID name
Room

Room
type

Entity Relationship Diagram (ERD)

19
DATA FLOW
DIAGRAM

20
 Patient Healthy
Person

discharged
Gets
admitted HOSPITAL
MANAGEMENT

LEVEL - 0 Data Flow Diagram (DFD)

21
 PATIENT

Gets DISCHARGED
admitted

REGISTER BILL

PAID

TREATMENT

LEVEL – 1 Data Flow Diagram (DFD)

22
 Total Bill
Paid Discharged

Patient
Bills Diagnosis
Generated &
Treatment

Allot
room if rooms
empty Codification
Diagnosis
&
Treatment
Patient
Registration

Assign Doctors
Doctor Codification

LEVEL - 2 Data Flow Diagram (DFD)

23
 DATA
DICTIONARY

24
TABLE 1 :
NAME : patientreg
PURPOSE : It stores the details of the patient.

STRUCTURE :

FIELD NAME DATA TYPE DESCRIPTION

pc Number Patient code

pn Text Patient name
age Number Patient Age
sex Text Patient sex
bg Text Patient blood group
addp Text Patient address
phno. Number Patient phone no.
doa Text Date of admission
toa Text Time of admission
rn Number Room no.
bn Number Bed no.
reln Text Relative name
addr Text Relative address
dc Number Doctor code
dn Text Doctor name
refby Text Referred by

25
TABLE 2:

NAME : diagnosis and treatment

PURPOSE : It stores the investigations , diagnosis and surgery charges
related to particular patient .

STRUCTURE:
FIELD NAME DATA TYPE DESCRIPTION

Pc Number Patient code

Inv Text Investigation

Surch Number Surgery charges

Theach Number Theatre charges

Delich Number Delivery charges

Pedch Number Pediatrician charges

TABLE 3:

26
NAME : doctor codification
PURPOSE : It stores the details of the doctor dealing with a particular
patient .

STRUCTURE:

FIELD NAME DATA TYPE DESCRIPTION

Pc Number Patient code

Spec Text Doctor specialization

Phno Number Doctor phone no

Vch Number Visit charges

Vdt Text Visit date

Vech Number Emergency visit charges

27
TABLE 4 :

NAME : miscellaneous charges.

PURPOSE : It stores the miscellaneous items and their charges.

STRUCTURE:
FIELD NAME DATA TYPE DESCRIPTION

Pc Number Patient code

Acch Number AC charges

Rhch Number Room heater charges

Interch Number Intercom charge

Cantch Number Canteen charges

28
TEST PLAN

29
 TEST PLAN

Why we need testing in any project?

As without get tested a project by a third party one cannot
determine the various errors that may be there in the project or
may come in future , that gradually becomes defects while
implementing the project. So, to make an efficient project it
should be properly tested.

UNIT TESTING is one of the white-box oriented testing. Unit

testing focuses verification efforts on the smallest unit of
software design- the software component and module. As in
this project various modules are:
Patient registration module, doctors codification module ,
generating charges modules , providing facilities module and
so on .So, various modules are independently tested here to
ensure that information properly flow into and out of the
various modules

INTEGRATION TESTING
Integration testing is a technique to uncover errors associated
with interfacing. The objective is to take unit testing
components and build a program structure. Here interfaces can
be between patient and doctor , between patient and facilities
between patient and charges, between patient and rooms and so
on. Therefore these interfaces are properly tested.

SYSTEM TESTING
Software in incorporated with other system elements(such as
people, information , hardware) thus a series of system
integration and validation tests are conducted. It is actually a
series of different test whose primary purpose is to fully
exercise the computer based system.

30
 FUTURE
ENHANCEMENTS

31
 FUTURE ENCHANCEMENTS

At a later point of time we plan to enhance our software. The

following points would be given emphasis on :

1) The facility of Blood-bank would be provided. Various

plans to organize blood donation camps would also be
implemented.

2) The facility of payments of bills by credit cards also be

provided.

3) The facilities such as speech therapy , physiotherapy ,

acupressure would also be provided.

32
 BIBLIOGRAPHY

1. SOFTWARE ENGINEERING
A Practitioner’s Approach
- By ROGER S. PRESSMAN
2. SOFTWARE ENGINEERING
- By PANKAJ JALOTE

3. AN APPROACH TO SOFTWARE ENGINEERING

- By K.K.KHANNA

33
SUGGESTIONS

34