PERFORMA OF PROJECT PROPOSAL

SCHOOL OF COMPUTER AND INFORMATION SCIENCES

IGNOU, MAIDAN GARHI, NEW DELHI – 110 068

Enrolment No. : ………………………………..

Study Centre: …………………………………..
Regional Centre: ………..... RCCode: ………..
E-mail: ………………………………………….
Telephone No.: …………………………………

1. Name and Address of the student

…………………………………………………………………………
…………………………………………………………………………

2. Title of the Project …………………………………………………….

3. Name and Address of the Counsellor

…………………………………………………………………………
…………………………………………………………………………

4. Educational Qualification of the Counsellor

Ph.D* M.Tech* B.E*/B.Tech.* MCA M.Sc.*

5. Working / Teaching experience of the Counsellor**…………………

6. Software used in the project…………………………………………..

Signature of the Student Signature of the counselor

Date: ………………….. Date: …………………

Suggestions for improving the project:

 Performa for Approval of Project Proposal.
 Bio-data of the project guide with sign/date.
 Synopsis of the project proposal (15-20 pages) covering the following aspects:

1. Title of the project

2. Introduction and objective of the project

3. Project category

4. Hardware Software Requirement Specification

4.1 Hardware Requirement Specification
4.2. Software Requirement Specification

5. Requirement and Analysis

5.1 Problem Definition
5.2 Requirement Specifications
5.3 Project Planning and Scheduling

6. Scope of the project.

7. Analysis
7.1 DFDs
7.2 ER Diagrams/ Class Diagrams

8. Complete Structure
8.1 Module Description
8.2 Data Structure
8.3 Process Logic of each module
8.4 List of reports likely to be generated

9. Implementation of security mechanisms at various levels

10. Future Scope and future enhancement of the project.

11. Bibliography
 1. Title of the Project

Title: Hospital Management System

2. Introduction and Objective of the project

 Introduction

Computer is very useful now in daily life. It’s growing more and more. It is never ends. It
is useful to all businesses. It had done our work easy. By Usage of computer we can
easily communicate to others. We can store many data to it. Internet is a very useful by
with we can easily communicate others. Our important work like bill submitting , salary
checking , account status, Reservation for traveling and many more work easily do at
home using internet.

 Objective Of Project

The main objective of this project is to make work easily to store data in hospital. It is
Hospital Management System. This is made for Sevashram Hospital, Bharuch. It is made
as per requirement of this hospital. It is government hospital which is very cheep in rent.
Here ESIS word is also included. All doctors are available with their schedule. This is a
website project so it can may useful to other branch also in future.

Here, we can easily create different types of reports. In hospital maintain register which
are also develop here easily. Person can easily check data about patient’s details. We can
easily know how many beds are available on following date. We can know easily
materials details. User can also make bill in different manner if patient is outdoor or
indoor type. Here all staff details also available.

3. Project Category

Type: Commercial Project.

Website Designing.

4. Hardware Software Requirement Specification

4.1 Hardware Requirement Specification

 PROCESSOR : Intel® Pentium® 4 CPU 2.40GHZ

 RAM : 768 MB

 FLOPPY DRIVE : 3.5" format remove able media

  MOTHERBOARD :

 MONITOR : Intel(R) 82845G/GL/GE/PE/GV Graphics

o Controller [Display adapter]
o LGE 700B [Monitor]

 MOUSE : PS/2 Compatible Scroll Mouse

 KEYBOARD : Standard 101/102-Key or Microsoft Natural PS/2

o Keyboard.

 HARD DISK : 80 Gigabytes Hard Drive Capacity

 DISK DRIVE : HL-DT-ST DVD-RAM GSA-H55N

4.2 Software Requirement Specification

 OPERATING SYSTEM : Windows XP Professional Service

 RDBMS: Microsoft SQL Server 8.0

 DEVELOPMENT TOOLS: Microsoft Visual Basic .Net 2008

 APPLICATION SOFTWARE: Microsoft Office 2002

 REPORT WRITER: Crystal Report 9

5. Requirement and Analysis

5.1 Problem Definition

Hospital Management System is software which covers latest technology and process
which are useful in hospital day to day. It is a website designing. So user can use it from
any place if he has ride to login in it. It is client server application. It uses Microsoft
technologies as Front End and Back End as (SQL server)

In this software we have to cover day to day important works. This is very useful. Daily
there are many data use to store in registers. It is very hard to collect them and save all.
If any patient takes revisit, then it is very hard to find its old details. So now this all work
is done very easily with this software. We can easily check how many bed/rooms are
empty for particular date. We can easily Fill Indent Form, Order Form. In this we can
easily check day to day material stock details. We can easily check staff details and also
give fees receipts easily without any more calculation.
 5.2 Requirement Specification

This system is done for Sevashram Hospital, Bharuch. There are many
requirements which are given by the user and we will do our best try to cover
them.

1. User wants to save details of any patient who visit the hospital. Here patient
personal details and case details are saved in database. If patient takes revisit
then his/her have no need to register new time. His/her details should be valid
up to 6th month after register date. Then he/she should have registered new
details.

2. In hospital death and breath are take place in any cases. If there is a new born
child he/she have to register about it. So here we have included Breath
register. Same as in any cases patient should be death. It is important to
register his/her name. So here Death details register also available.

3. Here ESIS’s patients are also treated. So some important reports are required
to be generated.

4. Patient may be outdoor or indoor. His category wise bill should be generated.

5. Different types of material are required by different department. Then they

should have to feel INDENT form. After order is take place.

6. Material In-Out entry must be possible. We can check stock details of

particular material. We have to generate report group wise material.

7. We can easily check bed details. We have to check it day wise. How many
beds are full or empty.

8. Staff details must be stored. Report should be generated department wise staff
details.

9. Staff personal details and work details are also included here.

10. We can see at a moment report generate.

5.3 Project Planning and Scheduling

 Project Planning
Planning is very important in every aspect of development work. Software project plan
indicated scope of the project, milestones and deliverables, project estimates, resource
allocation, risk management, scheduling techniques and quality control and standard.
Software project plan can be viewed as the following:

a. Effort: It includes the total number of manpower per months. As this project is
completely computerized hence less number of manpower will be used to successfully
run this project. At least 2-3 persons will be enough to maintain this project.
b. Hardware cost: It includes 2 INTEL P4 Standalone Computers. Cost around 30,000.
c. Travel expenses: As the persons assigned for this project are local peoples. It is
website designing. So it is available at Internet. No cost as travel expenses.
d. Training Cost: It is not so hard to work this system. But developer can be give
trainings about it.
e. Project size: The size of the project is estimated to be within 1500-1600 lines of code.
f. Project duration: It will take complete 5 months for completion. After that it will
take another 2-3 weeks for implementation and testing. Another 1-2 weeks is kept in
hand for any inconvenience.

 Scheduling

Scheduling o a project can be correlated to prioritizing various jobs with respect to their
cost, time and duration. Scheduling can be done with resource constraint or time
constraint in mind.

1. Work can be done like this:

Hospital
Management
System

Requirement
Design Coding Testing
Analysis

Patient Bed management

Maintenance management
Problem Definition planning and
scheduling Unit testing
Material
Data Design
management
Requirement
s/w and h/w
specification
requirement Other Modules
Modular design Integration testing

System testing
 2. Gantt chart Months

TASKS 1 2 3 5 6
4
1
1. System
Requirement

2. .System analysis

3. System Design

4. Coding

5. Implementation

6. Testing

3. Pert chart

Interviewing For requirement Analysis of Processes in

Hospital System Analysis Requirement
Documentation
1 8 days 2 8 days 3 15 days
4 10 days

System Testing System Implementation System Coding System Design

9 30 days 7 15 days 6 60 days 5 30 days

6. Scope of the project

 This project is very useful in for any hospital management. It should be done for
Sevashram Hospital, Bharuch. But we include common modules in this system.
Which all are useful and common to each hospital.

Future we can also expand this system by adding new modules like Lab management,
Finance management and many more.

7. Analysis

7.1 DFDS

Data flow diagrams (also called data flow graphs) are commonly used during problem
analysis. DFD’s are very useful in understanding a system and can be effectively used
during analysis.

It is the most important tools of system designing which enables software engineer to
develop models of the information domain and functional domain at the same time. It
serves two purposes:-

a. Provides an indication of how data are transformed as they move through the system.
b. Depicts the function and sub functions that transforms the data flow.

DFD SYMBOLS:

In the DFD, there are four symbols

 A square defines a source (originator) or destination of system data.

 An arrow identifies data flow. It is the pipeline through which the information
flows.
 A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
 An open rectangle is a data store, data at rest or a temporary repository of data.

Process that transforms data flow.

Source or Destination of data.

Data flow
 Data Store

7.2 ER Diagram/ Class Diagram

8. Complete Structure

8.1 Module Description

We have devised the following modules according to the requirements of a

Hospital and they integrate the various departments into a comprehensive system.

The Various Modules are

1. Patient Management.
2. Material Management.
3. Bed Management.
4. Fees Management.
5. Staff Management.
6. User Management.

1. Patient Management

Here we have to register patient details. All patient have an id which is auto generated. Case no.
Patients are likes ESIS and General type.

 If Patient will admit for any treatment in hospital then he/she is knows as Indoor patient.
He/she have a patient Id likes IPDNO. All details of his/her is belong this id. Which is auto
generated.
 If Patient will not admit in hospital then he/she is knows as Outdoor patient. He/she have a
Patient Id likes OPDNO. All details of his/her is belong this id. At all visit he knows as this
id which is auto generated.
 Various features are included in patient management

2. Material management
Here details of materials are maintained. Each material has its id. Stock of material is maintained.
In each department different types of material is useful. Issue new stock. Maintain stock.
Purchase new stock.

3. Bed management

We can easily see that how many beds are full and empty at given date. Receptionist can easily
check in which ward which bed is available at particular time. We can also easily count income
form bed management.

4. Fees Management

 OPD patients with complete details of Patient Information, Services provided like
Consultation, Medicines, and Procedures etc. along with Payment details.

 IPD patients with details of Patient Information, Services provided on daily basis like Room
rent, Operation, Delivery, Oxygen & Other Gases, Consultation, Nursing Charges, ,
Medicines, Procedures etc.

5. Staff management

This module describes details of staff members. Form we can take all data about any staff
members. We can retrieve contact details and also work details from that.

6. User management

This module is very useful. Here each user has different access rides. User has User name and
Password. By this user can access their module.

8.2 Data Structure

 Patient Management

1. Patient Master

Field Name Field Type Details

Pid Bigint Pk
Name Varchar(50)
Sex Char(10)
Age Bigint
Address Varchar(50)
Caste Varchar(50)
Religion Varchar(50)
Occupation Varchar(50)
Residence Varchar(50)
PatientType Varchar(50)

2. Patient Entry

Field Name Field Type Details

Id Bigint
Pid Bigint Fk form patient Master
Date Date time
IONO Varchar(50)
PatientType Char(10) FK from patient Master
Diagnosis Char(10)
Depid Bigint FK from Department Master
Status Char(10) If I as indoor O as outdoor

3. Treatment

Field Name Field Type Details

Tid Bigint PK
Pid Bigint FK from patient Master
IONO Varchar(50) FK form Patient entry
Name Varchar(50)
Dr Name Varchar(50) FK from Doctor Master
Ward Varchar(50)
Date Date time

4. Treatment Details

Field Name Field Type Details

Tdid Bigint PK
Tid Bigint FK from Treatment
IONO Varchar(50) FK from Patient Master
Date Date time
Time Date time
Clinical Note Varchar(50)
Treatment Varchar(50)

5. Birth Details

Field Name Field Type Details

Bid PK
Pid FK form patient Master
Sr.No Bigint
Date Of Register Date time
Birth Date Date time
Sex Char(10)
Name Varchar(50)
Place(born) Varchar(50)
Address Varchar(50)
Father name Varchar(50)
FT_Education Varchar(50)
FT_Occuption Varchar(50)
FT_Nationality Varchar(50)
FT_Region Varchar(50)
Mother name Varchar(50)
MT_Education Varchar(50)
MT_Occuption Varchar(50)
MT_Nationality Varchar(50)
MT_Region Varchar(50)
Mother’s Age Numeric(9) At the time of child born
Born No Numeric(9)
Treatment Type Varchar(50)
Sign Of Relative Varchar(50)
Sign Of Officer Varchar(50)
Remarks Varchar(50)

6. Death details

Field Name Field Type Details

Did Bigint PK
Pid Bigint FK from Patient Master
Sr.No Numeric(9)
Date Of Register Date time
Death Date Date time
Name Varchar(50)
Relative Name Varchar(50)
Place(Death) Varchar(50)
Age Numeric(9)
Sex Char(10)
Married Char(10)
Occupation Varchar(50)
Nationality Varchar(50)
Region Varchar(50)
Address Varchar(50)
Reason Varchar(50)
Physical Certificate Char(10) Yes/no
Physical Treatment Varchar(50)
Name of Relative Varchar(50) Who have to register
Sign Of Relative Char(10)
Sign of Officer Char(10)
Remarks Varchar(50)

 Material Management

1. Material Master

Field Name Field Type Details

Mid Bigint PK
Icode Varchar(50)
Itemname Varchar(50)
Gid Bigint FK from Group Master

2. Material InOut

Field Name Field Type Details

Minid Bigint PK
Trantype Char(10) I Inward new stock
O Outward old stock
PSid Bigint FK from Patient Master
FK from Supplier Master
Icode Varchar(50) FK from Material Master
Quantity Bigint
Stock Start Bigint
Usage Bigint
Stock End Bigint

3. Supplier master

Field Name Field Type Details

Sid Bigint PK
Name Bigint

4. Order Entry

Field Name Field Type Details

Oid Bigint PK
Date Date time
Order No Bigint

5. Order Details

Field Name Field Type Details

ODID Bigint PK
Order No Bigint Fk From Order
Sr.No Bigint
Particular Varchar(50)
Quantity Bigint

6. Indent Entry

Field Name Field Type Details

IID Bigint PK
No Bigint
Department Varchar(50)
Date Date time

7. Indent Details

Field Name Field Type Details

Inid Bigint PK
No Bigint FK from Indent Master
Sr.No Numeric(9)
Particular Varchar(50)
Quantity Numeric(9)

 Bed/Room Management

1. Room Master

Field Name Field Type Details

Rid Bigint PK
Room type Varchar(50)
Price Money(8)

2. Bed Details

Field Name Field Type Details

Bdid Bigint PK
Rid Bigint FK from room master
Price Money(8)
Bdesc Varchar(50)
Date Date time
Pid Bigint FK from patient master
Status Varchar(50)

 Fees Management

1. Bill Master

Field Name Field Type Details

Bilid Bigint PK
Sr.No Bigint
Case No Bigint
Name Varchar(50)
Amount Money(8)

2. Bill Details

Field Name Field Type Details

Bilid Bigint FK from Bill Master
Sr.No Numeric(9)
Case No Numeric(9)
Particular Varchar(50)
Amount Money(8)

3. Fees Details

Field Name Field Type Details

Bilid Bigint FK from Bill Master
Sr.No Numeric(9)
Case No Numeric(9)
Particular Varchar(50)
Amount Money(8)

 Staff Management

1. Staff Details

Field Name Field Type Details

Sid Numeric(9) PK
Name Varchar(50)
Address Varchar(50)
Phone no Varchar(50)
Education Varchar(50)
Department Varchar(50)
Date Of Joining Date time
Time Varchar(50)
Status Varchar(50)

2. Department Master

Field Name Field Type Details

Did Bigint PK
Department No Numeric(9)
Department Name Varchar(50)

 User Management

1. User Master

Field Name Field Type Details

User id Varchar(50) PK
Username Varchar(50)
Password Varchar(50)

2. Module Master

Field Name Field Type Details

Module Id Varchar(50) PK
Module Name Varchar(50)

3. UserMod_ride

Field Name Field Type Details

User id Varchar(50) PK
Module id Varchar(50)
Access type Varchar(50)

4. Group Master

Field Name Field Type Details

Group id Varchar(50) PK
Group name Varchar(50)

8.3 Process Logic of each module

1. Patient management

 First of all details of new patient must be entered in patient master form. Then
data is flow up to patient entry form.
 Here patient have two different categories Likes Indoor and Outdoor.
 If he/she is Outdoor patient then he went to particular department takes treatment
and Outdoor patient bill should be generated.
 If he/she is Indoor patient then he occupies Room/Bed. Hospital gives him
material too. He takes treatment day to day. Nursing chart should be generated
here upon the basis of treatment give to the patient.
 If Indoor patient takes treatment and result be death. Then death details should be
register in to death register. If any patient give born to child then breath details
should be register in breath register.
 Lastly Indoor patient Bill should be generated.

2. Material management

 First of all, all department feel Indent form for required new things.
 Then Order form takes place for this item.
 When supplier supplies this item to hospital its record feels in material
inward. Here stock should be increased.
 When Material given to any patient its record feels in material outward. Here
stock should be decreased.

3. Bed/room management
  Indoor patient should take rooms to admit in hospital. Each hospital have limited
number of beds. So they have to need takes details of bed.
 They can know how many beds are reserved at any time. Which beds are
available in hospital at a time?

4. Fees management

 All charges are foals in this module.

 All details of patient entry fetch here. He has to charges above its usage material
and takes treatment in hospital.

5. Staff management

 All detail of staff member store here. It should be personal details as well as
working details.
 Department details also feel in this module.
 Staff report should be generated category wise or department wise.

6. User management

 Users have to takes ride to access any module or system.

 He/she has his own username and password.

 There is a table group master also generated. In this table we have to declare some
group name with id. It is very useful. By this we can takes report GroupWise.

8.4 List of reports likely to be generated

Reports

 ESIS monthly indoor patient no Count department wise.

 Indoor patient treated Register.
 Outdoor patient treated Register.
 ESIS Outdoor patient treated Register.
 ESIS indoor patient treated Register.
 Outdoor patient report department wise.
 Nursing Chart.
 Indoor paper history sheet.
 Born Register.
 Death Register.
 ESIS treated patient’s details reports monthly.
 Order Book
 Indent for material
 Kitchen register
  Perceptions stock details
 Sprit Register
 Injection register
 Tablets registers
 ESIS word bed Report
 Outdoor Patient Slip.
 Indoor Patient Slip
 Monthly income Report
 Staff details department wise
 Staff details Group wise.

9. Implementation of security mechanisms at various levels

7. Hospital management System checks if user is valid or not who have login in it.
8. User has to give rides to access particular modules.
9. If there is any error generated at any stage. It will give simply error message to
user. The design of error messages is an important part of the user interface design.
As user is bound to commit some errors or other while designing a system the system
should be designed to be helpful by providing the user with information regarding the
error he/she has committed.

10.Future Scope and future enhancement of the project.

10. This Project has very good scope for adding new features. We can add new
modules which are useful in Hospital Management System. Like Lab
management, Finance management, Reception management.

11. Here project type is website Development. So it is useful at any place via Internet.
All online users who have rides to use this project can be use it form any place.

12. Next this project can be useful to another branch also by Internet.

11. Bibliography

13. SQL FOR PROFESSION By Jain

 14. VISUAL BASIC.NET Black Book By Evangeleous Petereous

15. ASP.Net Professional By Wrox Publications

16. MSDN 2008 By Microsoft

Welcome screen

User Login

Menu

Master IPD OPD Other Reports

Master
 Patient Master
 Material Master
 Bed/Room Master
 Fees Master
 Staff Master
 Department Master
 Group Master
 Supplier Master
IPD
 Patient Entry
 Treatment Details
 Bed Transaction
 Material Given
 Born details
 Death details
 Bill

OPD
 Patient Entry
 Treatment details
 Bill details

Others
 Indent
 Order
 Material inward
Reports
 ESIS monthly indoor patient no Count department wise.
 Indoor patient treated Register.
 Outdoor patient treated Register.
 ESIS Outdoor patient treated Register.
 ESIS indoor patient treated Register.
 Outdoor patient report department wise.
 Nursing Chart.
 Indoor paper history sheet.
 Born Register.
 Death Register.
 ESIS treated patient’s details reports monthly.
 Order Book
 Indent for material
 Kitchen register
 Perceptions stock details
 Sprit Register
 Injection register
 Tablets registers
 ESIS word bed Report
 Outdoor Patient Slip.
 Indoor Patient Slip
 Monthly income Report
 Staff details department wise
 Staff details Group wise.