Hospital Management System

By
Rishit Gajjar (10BIT031)
Mehul Ranavasiya (10BIT047)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINERING

Ahmedabad 382481
November 2013

Hospital Management System

Minor Project

Submitted in partial fulfillment of the requirements

For the degree of
Bachelors of Technology in Information Technology

By
Rishit Gajjar (10BIT031)
Mehul Ranavasiya (10BIT047)

Guided By
Mr. Sapan Mankad
[DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING]

DEPARTMENT OF COMPUTER SCICEN AND ENGINEERING

Ahmedabad 382481
November 2013

CERTIFICATE
This is to certify that the Minor Project entitled Hospital Management System
submitted by Rishit Gajjar(10bit031),Mehul Ranavasiya (10bit047), towards the
partial fulfillment of the requirements for the degree of Bachelors of Technology
in Information Technology of Nirma University of Science and Technology,
Ahmedabad is the record of work carried out by them under my supervision and
guidance. In my opinion, the submitted work has reached a level required for
being accepted for examination. The results embodied in this minor project, to
the best of my knowledge, havent been submitted to any other university or
institution for award of any degree or diploma.

Prof Sapan Mankad

Guide,
Assistant Professor
Department of Computer Engineering,
Institute of Technology,
Nirma University,
Ahmedabad

Dr. Sanjay Garg

Professor and Head,
CSE Department,
Institute of Technology,
Nirma University,
Ahmedabad

ACKNOWLEDGEMENT
I would like thank to all those who are involved in this endeavor for their kind
cooperation for its successful completion. At the outset, I wish to express my
sincere gratitude to all those people who have helped me to complete this project
in an efficient manner.
I offer my special thanks to my Project guide Prof. SAPAN MANKAD, Assistant
Professor,

Department

of

Computer

Science

&

Engineering,

Institute

of

Technology, Nirma University, Ahmedabad without whose help and support

throughout this project would not have been this success.
I am thankful to Dr. K KOTECHA, Director and Institute of Technology,
Ahmedabad for his kind support in all respect during my study. I would like to
thank Dr. SANJAY GARG, Head, Department of Computer Engineering, Institute
of Technology, Nirma University, who gave opportunity to do this project at an
extreme organization. Most of all and more than ever, I would like to thanks my
family members for their warmness, support, encouragement, kindness and
patience. I am really thankful to all my friends who always advised and
motivated me throughout the course.

RISHIT GAJJAR
Roll No.10BIT031
MEHUL RANAVASIYA
Roll No.10BIT047

ABSTRACT
Many Hospitals currently use a manual system for the management and
maintenance of critical information. The current system requires numerous paper
forms,

with

data

stores

spread

throughout

the

hospital

management

infrastructure. Often information (on forms) 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.
A significant part of the operation of any hospital involves the acquisition,
management and timely retrieval of great volumes of information. This
information typically involves; patient personal information and medical history,
staff information, room and ward scheduling, staff scheduling, operating theater
scheduling and various facilities waiting lists. All of this information must be
managed in an efficient and cost wise fashion so that an institution's resources
may be effectively utilized HMS will automate the management of the hospital
making it more efficient and error free. It aims at standardizing data,
consolidating data ensuring data integrity and reducing inconsistencies.

CONTENTS
Certificate

Acknowledgement

Abstract

Contents

List of figures

List of tables

Chapter 1

Chapter 2

Introduction

1.1

General

Design

10

2.1

Overview

10

2.2

UML Diagram

10

2.3

2.2.1 Introduction

11

2.2.2 Use case Diagram

12

2.2.3 Sequence Diagram

13

2.2.4 Activity Diagram

14

Project Module
2.3.1 List of Modules

15

2.3.2

16

Module Description

2.3.3 Screen Shots

Chapter 3

Chapter 4

18

Database

25

3.1

25

Data Dictionary

Conclusion

29

4.1

Conclusions

29

4.2

Future Enhancements

30

Bibliography

31

LIST OF FIGURES

Figure No.
Figure 2.1
Figure 2.2
Figure 2.3
Figure 2.4
Figure 2.5
Figure 2.6
Figure 2.7
Figure 2.8
Figure 2.9
Figure 2.10

Caption
Use case Diagram
Sequence Diagram
Activity Diagram
Home Page
Admin Page
Registration page
Operation Theater
Medical Test
Pharmacy Page
Discharge Page

Page No.
12
13
14
18
19
20
21
22
23
24

LIST OF TABLES

Table No.
Table 3.1
Table 3.2
Table 3.3
Table 3.4
Table
Table
Table
Table
Table
Table

3.5
3.6
3.7
3.8
3.9
3.10

Table 3.11

Caption
Doctor Registration
Employee
Registration
Inpatient
Registration
Out Patient
Registration
Patient Information
Surgery Information
Blood test
Urine test
Operation
Pharmacy
Information
Discharge Summary

Page No.
25
25
26
26
27
27
27
28
28
28
28

INTRODUCTION

1.1 GENERAL
Documenting the assembly, maintenance, use, and troubleshooting of a
system as complex as a voting system is a difficult task. A single system
might combine proprietary hardware, custom operating systems and
software, commodity personal computers, and pen and paper. Describing
these highly varied components is one function of voting system
documentation .But it is not only voting system technology that is
heterogeneous; so are voting systems users, and the environments in
which the systems are used. Election officials, poll workers, and voters
often need guidance from documents in order to administer or use a
voting system. In addition, voting system certificationthe process by
which a system is approved for use in state demands evidence that a
voting system complies with one or more sets of standards or guidelines.
Documentation provides the details that certification bodies need to
evaluate the System. Taken as a whole, voting system documentation
must explain the system in several ways to meet the needs of these
multiple audiences.
As the modern organizations are automated and computers are working as
per the instructions, it becomes essential for the coordination of human
beings, commodity and computers in a modern organization.
Many big cities where the life is busy needs the transaction of the goods
within few minutes of time. So, this online information recorded by the
distributor helps him to complete this task within the time.
The administrators and all the others can communicate with the system
through this project, thus facilitating effective

implementation and

monitoring of various activities of the voting Software.

DESIGN

2.1 Overview
Design is the first step in the development phase for any techniques
and principles for the purpose of defining a device, a process or system in
sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified
the software design involves three technical activities - design, coding,
implementation and testing that are required to build and verify the
software.
The design activities are of main importance in this phase, because
in this activity, decisions ultimately affecting the success of the software
implementation and its ease of maintenance are made. These decisions
have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customers requirements
into finished software or a system.
Design is the place where quality is fostered in development.
Software design is a process through which requirements are translated
into a representation of software. Software design is conducted in two
steps. Preliminary design is concerned with the transformation of
requirements into data.

10

2.2 UML Diagrams

2.2.1 Introduction
Actor:
A coherent set of roles that users of use cases play when interacting with
the use `cases.

Use case:
A description of sequence of actions, including variants, that a system performs
that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for

specifying, visualizing and documenting the system. This is the step while
developing any product after analysis. The goal from this is to produce a model
of the entities involved in the project which later need to be built. The
representation of the entities that are to be used in the product being developed
need to be designed.
There are various kinds of methods in software design:
They are as follows:

Use case Diagram

Sequence Diagram

Activity Diagram

11

2.2.2 USECASE DIAGRAM

A Use case is a

description of set of sequence

of actions

Graphically it is rendered as an ellipse with solid line including only its

name. Use case diagram is a

behavioral diagram that shows a set of

use cases and actors and their relationship. It is an association between

the use cases and actors. An actor represents a real-world object.

Registration

Reception

Discharge Summary
Patient

Doctor

Laboratory

Pharmacy

Fig. 2.1 Use case Diagram

12

2.2.3 SEQUENCE DIAGRAM

Sequence

diagram

and

collaboration

diagram

are

called

INTERACTION DIAGRAMS. An interaction diagram shows an interaction,

consisting of set of objects and their relationship including the messages
that may be dispatched among them.
A sequence diagram is an introduction that empathizes the time
ordering of messages. Graphically a sequence diagram is a table that
shows objects arranged along the X-axis and messages ordered in
increasing time along the Y-axis

Reception

Resgistration

Doctor

Patient

Laboratory

Pharmacy

Discharge
Summary

login

View appointments

Register

Send request

done any surgeries

Go to Laboratory
Take madicine

send discharge summary

Discharge patient

Fig. 2.2 Sequence Diagram

13

2.2.4 ACTIVITY DIAGRAM

start

Doctor

Patient

Registration
Pharmacy

Reception

Discharge
summary

Laboratory

End

Fig. 2.2 Activity Diagram

14

2.3

PROJECT MODULES
List of Modules:

Reception
Administration
Pharmacy
Laboratory
Registration
Discharge Summary

15

2.3.2 MODULE DESCRIPTION

Name of the module-1: Reception

Description: The reception module handles various enquiries about the
patient's admission and discharge details, bed census, and the patient's
movements within the hospital. The system can also handle fixed-cost
package deals for patients as well as Doctor Consultation and Scheduling,
Doctor Consultancy Fees and Time Allocation
Sub modules:

Doctor visit schedule

Doctor Appointment Scheduling

Enquiry of Patient

Find History of Patient Enquired.

Name of the module-2: Administration

Description: This module handles all the master entry details for the
hospital requirement such as consultation detail, doctor specialization,
consultancy fee, and service charges.
Employee
Sub modules:

Employee Detail Recording.

Doctor Type .

Doctor Master

Referral Doctor

Name of the module-3: Pharmacy

Description: This module deals with all medical items. This module helps
in maintaining Item Master, Receipt of Drugs/consumables, issue,
handling of material return, generating retail bills, stock maintenance. It
also helps in fulfilling the requirements of both IPD and OPD Pharmacy.

16

Name of the module-4: Laboratory.

Description: This module enables the maintenance of investigation
requests by the patient and generation of test results for the various
available services, such as clinical pathology, X-ray and ultrasound tests.
Requests can be made from various points, including wards, billing,
sample collection and the laboratory receiving point. The laboratory
module is integrated with the in-patient/ outpatient registration, wards
and billing modules.
Name of the module-5: Registration.
Description: This module helps in registering information about patients
and handling both IPD and OPD patients query. A unique ID is generated
for each patient after registration. This helps in implementing customer
relationship management and also maintains medical history of the
patient.
Name of the module-6:Discharge Summary.
Description: The module helps in generating patients discharge
summary, which includes patients health at the time of discharge,
medical history, various diagnosis and drug prescriptions, history of
present illness and course in hospital.

17

2.3.3 SCREEN SHOTS

Figure 2.4 Home Page

18

Figure 2.5 Admin Page

19

Figure 2.6 Registration page

20

Figure 2.7 Operation Theater

21

Figure 2.8 Medical Test

22

Figure 2.9 Pharmacy Page

23

Figure 2.10 Discharge Page

24

DATA DICTIONARY

3.1 DATABASE TABLES:

Table 3.1 Doctor Registration

Name
Name
Loginid
password
Department
Specialization
Phonenumber
Address
Email

NULL /
NOTNULL
Null
Null
Null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar (20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Bigint
Varchar(20)
Varchar(20)

Table 3.2 Employee Registration

Name
Name
Loginid
password
Department
Phonenumber
Address
Email

NULL /
NOTNULL
Null
Null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar (20)
Varchar(20)
Varchar(20)
Varchar(20)
Bigint
Varchar(20)
Varchar(20)

25

Table 3.3 Inpatient Registration

Name
Patientname
Patientid
Gender
Age
Phoneres
Phonemob
Maritual
Occupation
Admid
Admdate
Admtime
Status
Symptoms
Department
Wardno
Bedno
Doctor

NULL /
NOTNULL
Null
Not Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null

TYPE
Varchar (20)
Varchar(20)
Varchar(20)
Int
Bigint
Bigint
Varchar(20)
Varchar(20)
Int
Datetime
Datetime
Varchar(20)
Varchar(20)
Varchar(20)
Int
Int
Varchar(20)

KEY

Primary

Table 3.4 Out Patient Registration

Name
Patientname
Patientid
Gender
Age
Address
Assigndoctor
Phoneres
Phonemob
Opdate
Department

NULL /
NOTNULL
Null
Not Null
Null
Null
Null
Null
Null
Null
Null
Null

TYPE
Varchar (20)
Varchar(20)
Varchar(20)
Int
Varchar(20)
Varchar(20)
Bigint
Bigint
Datetime
Varchar(20)

KEY

Primary

26

Table 3.5 Patient Information

Name
pid
Patientname
Age
Department
Doctor

NULL /
NOTNULL
Not null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Int
Varchar(20)
Varchar(20)

Foreign

Table 3.6 Surgery Information

Name
pid
Patientname
Age
Department
Doctor
Surgerydate

NULL /
NOTNULL
Not null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Int
Varchar(20)
Varchar(20)
Datetime

Foreign

Table 3.7 Blood test

Name
Patienttype
Patientid
Patientname
Mediclatestype
Bloodgroup
Haemoglobin
Bloodsugar
Sacid
Description

NULL /
NOTNULL
Null
Null
Null
Null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)

27

Table 3.8 Urine test

Name
Patienttype
Patientid
Patientname
Mediclatestype
Color
Clarity
Odor
Specificgravity
Glucose
Description

NULL /
NOTNULL
Null
Null
Null
Null
Null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)

Table 3.9 Operation

Name
Patienttype
Patientid
Patientname
Refdoctor
Operationtype
Operatonresult

NULL /
NOTNULL
Null
Null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Datetime

Table 3.10 Pharmacy Information

Name
Patienttype
Patientid
Department
Patientname
Medicine

NULL /
NOTNULL
Null
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)
Varchar(20)

Table 3.11 Discharge Summary

Name
Patientid
Patientname
Joiondate
Dischargedate

NULL /
NOTNULL
Null
Null
Null
Null

TYPE

KEY

Varchar(20)
Varchar(20)
Datetime
Datetime

28

CONCLUSION
The package was designed in such a way that future modifications can be
done easily. The following conclusion can be deduced from the
development of the project.
Automation of the entire system improves the efficiency
It provides a friendly graphical user interface which proves to
be better when compared to the existing system.
It gives appropriate access to the authorized users depending
on their permissions.
It effectively overcomes the delay in communications.
Updating of information becomes so easier.
System security, data security and reliability are the striking
features.
The System has adequate scope for modification in future if it
is necessary.

29

FUTURE ENHANCEMENTS
This application avoids the manual work and the problems concern with it.
It is an easy way to obtain the information regarding the various travel
services that are present in our System.
Well I and my team member have worked hard in order to present an
improved website better than the existing ones regarding the information
about the various activities. Still, we found out that the project can be
done in a better way. Primarily, In this system patient login and then go
to reception. By using this patient will send request for consulting the
doctor. Reception will set the date for doctor appointments. After that
doctor see his appointments and see the patients, surgeries also done.
The next enhancement is, we will develop online services. That
mean, if patient have any problems he can send his problem to the doctor
through internet from his home then doctor will send reply to him. In this
patients have some login name and password.

30

BIBLIOGRAPHY
1. MICROSOFT .NET WITH C#,Microsoft .net series
2. ASP .NET 2.0 PROFESSIONAL,Wrox Publishers
3. ASP .NET WITH C# 2005, Apress Publications
4. C# COOK BOOK, O reilly Publications
5. PROGRAMMING MICROSOFT ASP .NET 2.0 APPLICATION, Wrox Professional
Guide
6. BEGINNING ASP .NET 2.0 E-COMMERCE IN C# 2005, Novice to Professional.
WEBSITES:
1. www.google.com
2. www.microsoft.com

31