Hospital Management System

CHAPTER 1

INTRODUCTION

1. 1. Abstract

The main aim of the project is to provide good user friendly to maintain the complete
Hospital Information and to automate the patient registration and all other activities and track all
the transaction and post it to the respective register.

Title of the Project:

The title of the project is “Hospital Management System”. It is application software

with Microsoft Access database and Visual Basic 6.0

This software comprises the following

• New patient registration.
• New doctor’s appointment.
• Inpatient and Outpatient registration.

Whenever a new patient visits the hospital al his details are recorded, like address, age
sex, suffering from and all the details are sent to the concerned doctor for further treatment.

New appointment of doctors and al other staff are provided so that when ever new
appointment are taken their details are recorded in a separate register and similarly when a staff
quits the job his details are also maintained.

Depending on the seriousness of the patient he/she may be taken as inpatient or out patient.
The doctor will decide that and if outpatient they may be given further date for review. If
inpatient his details are collected and a bed is allotted and at the time of discharge he has to clear
all his bills.

1.2 Objectives:

The objective of HMS is as follows:

1. Provide a good GUI based Application Software to maintain the details of

patient and staff.
2. Maintain the Inpatient and Outpatient details.

3. Maintenance the bills of and other details of inpatient.

4. To provide suitable security to the database.

{1}
Hospital Management System

CHAPTER 2

SYSTEM STUDY

2.1 Introduction
System Analysis is an important activity that takes place when we are building new
system information or charging existing ones. Analysis is used to gain an understanding of an
existing system and what is required of it. At the conclusion of the analysis, there is a system
description and a set requirement for the new system. If there is no existing system, the analysis
defines only the requirement.

System models are used to gain the ambiguities often found in the system. Modeling
techniques used in the system analysis avoids ambiguity by using precise modeling constructs
and process description. They also assist to define precisely the requirement of the new system.
Software tools that help analyst in their work now often support system analysis.

This phase is a detail appraisal of the existing system. This appraisal includes finding out
how the system works and what it does. It also includes finding out in more detail what the
system’s problem are and what the user requires from the new or changed system. After this
phase, analysts should be familiar with both the detailed operation of the system and what is
required of the new system. Analysts must spend considerable time examining components.

One of the most important factors in system analysis is to develop a good understanding
of the system and its problems. A good understanding of the system enbable designers to
identify the correct problems and suggest realistic solutions for them. It also helps them to
develop solutions that satisfy all users and thus makes the new system acceptable in an
organization. System users are the first information source investigated by analysts. From users
it is possible to find out the existing system activities and to develop the user objectives and
requirements. A system analysts must spend a lot of time taking to users and finding out how
they use the system, any problems they find with the system and what they expect from it.

2.2 Existing system

According to the study made on the existing system, which is a manually operated, the
following points have been notified.

The details of the staff’s/patient’s of details as to be entered manually, which is time

consuming and complex one and wastage resources, in terms of human effort, storage
space and so on.

The details of the staff’s/patient’s specification will be entered in different ledgers and
the details of the design will be stored in other
Registers, which is every difficult in accessing of the information.
If one person is using the register then the other should wait until the register id free.

{2}
Hospital Management System

2.3 Limitation of existing manual system

Time consuming .
Maintenance of existing manual system is very much complex in terms of
The human efforts, efficiency and resources it requires.
Extra storage space is required for storing the registers.
Difficulty in accessing the information.
Quick and correct information is not available in time.
Security for the information or the records.
Information between the subsystems is poor.

2.4 Proposed System

The proposed system will have features of the existing system and overcome the
above mentioned limitations. The proposed system will try to meet below-motioned objectives,
in turn will try to satisfy the user of the system.

The HMS is proposed to have the following modules:

The Staff’s management.

The Patient’s information.

2.5 Hardware and Software Requirement:

Hardware:-
Machine : Pentium 200 MHz and above.
Primary : 32 MB and above.
Secondary Memory : 2.1 GB and above.

Software:-
Platform : GUI (Windows-98 and above)
Back-end : Microsoft Access
Front-end Tool : Visual Basic 6.0

{3}
Hospital Management System

2.6 System Objectives

 Deliver an efficient Computerized System:
The existing system is the manual system, which is a cumbersome work. The new
system makes use of the keyed access facilities, security and reliability of the
RDBMS in delivering an efficient improved computerized system.

 Provides a user friendly user interface:

This system is completely user friendly, the sys tem includes help a about project
and screen along with appropriate messages.

 Avoid data inconsistency and maintain integrity:

The system ensures data integrity and avoids inconsistency along with the
database and data by providing built in validations before posting the data into the
database.

 Enhance the security features:

The system is built upon well-secured database unauthorized access and
manipulation is strictly prohibited by incorporating password authorization
wherever is needed.

 Avoid major deviations from existing system:

This is because any change in the existing system will need the change in the
earlier working practice that may require extreme attention or may lead to an
inefficient use of the designed system.

 Good MIS to the management:

GSMS becomes a good management information system to the management and
useful reports are generated for specific information depending on management
needs.

2.7 Functional Requirement

 Creation of Staff’s/Patient’s.
 Creation of Staff list.
 Rising Bill.
 Printing Staff and Patient List.
 Printing Discharge List.
 Printing all details List.

{4}
 Hospital Management System

CHAPTER 3

FESIBILITY ANALYSIS
3.1 Introduction
Every project is feasible if there is unlimited resources and infinite time. But In real
sense the development of a computer-based system is more likely with a limited resource and
time. It is necessary to evaluate the feasibility of a project at the earliest.

So as to avoid any dangerous consequences in the process of product development. So

the detail study was carried out to check the workability t6uy of the proposed system.
.
Feasibility study is an evolution of the system proposed regarding its workability impact
in the organization ability to meet user needs, and effective use of resources. Thus when a new
application is proposed, it normally goes through a feasibility study before it is approved for
development

Feasibility and risk analysis is related in many ways. If project risk is great, the
feasibility of producing quality software is reduced. During feasibility analysis for this project,
the following five primary areas of interest were considered very carefully.

3.2 Technical Feasibility

he consideration that is normally associated with technical feasibility includes resource
availability of the organization where the project is to be developed and implemented, by taking
these into consideration before developing, the resource availability at this organization was
observed. Thus, this project is considered technically, feasible for the development.

3.3 Economical Feasibility

Economic feasibility is generally the “Bottom Line” consideration for most system.
Economic justification includes an broad range of concerns that include cost benefit analysis.
Cost benefit analysis delineates costs for project development and weighs them against the
tangible benefits of a system.

This software is economically feasible for the development of the organization, because
of the benefits that the system is providing in terms of security and user-friendly interfaces.

3.4 Social feasibility

The interest and support shown by the organization during system study was satisfactory.

{5}
Hospital Management System

3.5 NORMALIZATION:

First normal form:

A relation is said to be in first normal form, if the value in the domain of each attribute of
the relation is atomic. That is only one value is associated each attribute. The table is in first
normal form, since there are no reputed groups.

Second normal form:

A relation is said to be in second normal form, if it is in the first normal form and if all
non-prime attributes are full functionally dependent on the primary key of the relation. The
relations are checked for full functional dependency.

Third normal form:

In this step all the tables are checked for dependency. Since there is no transitive
dependency, the tables are automatically in third normal form. The databse for GSMS has been
normalized upto third normal form.

{6}
Hospital Management System

CHAPTER 4

SYSTEM DESIGN

4.1 Introduction
Design, which follows system study, proposes the new system that meets the
requirements. This phase produces a design for the new system. Designers must select the
equipment needed to implement the system. Design is the hardest phase to describe. It is very
different form analysis. There is no such thing as a correct design. A good design is very
dependent in the particularly system and what is a good design for one system may be bad for
another. Design considerable creativity to make necessary changes and additions and come up
with a new system that is acceptable to users easy to implement.

Design is a problem solving process that investigates ways of meeting the objectives. Its
goal is to create a new system that meets a set of objectives and these objectives are the driving
forces behind the design process.

Design is the only way in which we can accurately translate a customer’s requirements
into finished software product or system. Without design risk of building an unstable system
exists-one that will fail when small changes are made, one that may be difficult to test. System
design usually proceeds in two steps, broad designs & detailed design.

During Broad design, major new functions are proposed and changes to the existing
functions are defined. Important inputs and outputs are also defined at this point and
performance requirements are also specified. Board design outlines, which part of the system is
to automated and which will remain manual.

During detailed design, the database and the program modules are designed detailed
documented. The interfaces between the system users and the computers are also defined. These
interfaces define exactly how user will be expected to use the system. It should be noted that
detailed design tends to be more structured than broad designs and is easier to describe.

4.2 Design Technique

Normally Structured System Analysis and Design technique are used for design. These
include.
HIPO Charts
Data modeling (ERD)
Process modeling (DFD)

4.3 HIPO Chart

HIPO (hierarchy and input/output charts) are one of the earliest methods devised to
describe systems by their functions. The idea of the HIPO technique is functional hierarchical
decomposition. We start with a high-level function decompose it into more detailed components.

{7}
Hospital Management System

Process Model (DFD)

DFD depicts flow of data from and to different processes and the transforms that are
applied as data moves from input to output. It is the starting point if the design phase that
functionally decomposes the requirement specification down to the lowest level of details.
DFD can be two types:
Physical DFD
Logical DFD

Logical DFD shows the flow of data over the processes. Leveled DFD set is a
hierarchical way of organizing the system. It has a context level diagram identifying the major
inputs, outputs and processes in the system, then each process is refined and DFD is drawn for
the process. Physical DFD shows flow of data over physical media.

Here are the Physical Data Flow Diagrams of “GSMS”.

Data flow diagrams are made up of four basic elements:

• External Entities
An external entity represents any entity that supplies or receives information from
the system, but is not a part of the system.
The symbol representing the external entities is a rectangle as shown below.

External entity

• Data Flow:
Data in a system move in a specific direction that is from origin to destination.
The data flow is a “packet” of data indicating the movement of data within the system.
They are shown as:

Data Flow

• Processes:
The emphasis in any DFD is placed on processing. Processes transform
inputs into outputs. They are work or actions that are performed by people, machines, or
computers on incoming data flows to produce outgoing data flow. Processes are depicted
as:
• Data Store:
Data stores could be thought of the ‘Memory’ of the system. Data stores are
temporary holders of data. Data flow diagrams do not specify the type physical storage
i.e. tape, disk etc. It is depicted as:

Data Store

{8}
Hospital Management System

DFD

Staff New Staff Admit Out Patient

Hospital
Management
System

In Patient

Give Disease
Details
Cases Discharge
Pay Bill

Context data flow diagram

{9}
Hospital Management System

Out Patient
Check Doctor
Registratio Inspection
n

Report

Registration File

Physical data flow diagram

{10}
Hospital Management System

4.5 SYSTEM FLOW DIAGRAMS

FLOW CHARTS
Flowcharts are also a method of communicating complex relationships. They are
extensively used to describe information flow and processing throughout the analysis and
development of computer-based information system.
Each procedure defined in a flowchart specifies all the logical steps and sequence in
involved in it. They help to divide the problem into smaller segments and are widely used in
evaluations of the process logic’s since they do bring to light new area of problem that are
needed for the study.
Uses of flowcharts:
Flowcharts help the analyst to describe and communicate complex sets of data in there
principal ways. They are:
1. Analyses existing systems
2. Synthesize New systems
3. Communicate with others

Types of Flowcharts
According to their usage, the flowcharts are classified into:
1. System Flowchart
2. Program Flowchart

System flowcharts are used in describing the overall work flow of the system. In a
system flow chart normally the origin of data, manual operations, I/O devices, storage
media’, data transmission procedures and I/O operations are explained.
The Programming flow charts describe the sequence of each step exactly involved
in a procedure. Three main program flowcharting techniques are in use to represent
processes and events. Each method has its own set of symbols to signify the steps
involved in procedure or program.

{11}
Hospital Management System

The advantages of flowchart are:

1. They enable facts to be set out early with sufficient details according to the level.
2. They Provide means for comparison and analysis.
3. They act as a good referencing tool.

Process  Connection 

Alternate Process  Stored data 

Direct Access Storage  Decision 

Manual Operation  Merge 

Manual Input  Preparation 

{12}
Hospital Management System

Flow Chart: System Flow

Patient Registration

Doctor Appointment

Room Allotment

Billings

Patient Discharge

{13}
Hospital Management System

Start

Patient Registration

If
Seriou Out Patient
s

In Patient

Allocate Room

Treatment

Discharge

{14}
Hospital Management System

4.6 Entity Relationship Diagram (ERD)

ERD is graphical nation for modeling of data. ERD highlights relationship

between the data store on the DFD
ERD uses three major abstractions to describe the data

a) Entities, which are distinct in the organization, It is conceptual

Representation of an object.

b) Relationships which are meaningful interactions between the Objects.

c) Attributes which are properties of entities and relationships

Three types of relationship exists among entities

a) A One-to-One (1:1) relationship describes an entity that may Have two
or more entities related to it.

b) A One-to-May (1:M) relationship describes an entity that may Have to

or more entities related to it.

c) A Many-to-Many (M:M) relationship describes an entity that may

have many relationships in both directions.

4.7 Input Design:

After the design of required tables i.e. database design comes the screen (forms) design.
The screens are designed to input data into the tables and also for user query purpose. These
screens allow the user to interact with the database through user interface modules.
This is done as per the specification given by the Client and also keeps in mind the input
requirement of the system.
They specify-
What data to input
• How data has to be arranged and coded.
• Dialogs to guide user in providing input to the database.
• Methods to perform input validation and steps to follow when
error occurs.
The screens are designed as per the colour codes given by the client, and the various
control buttons are also made iconic which helps the user to use the software more easily.

{15}
Hospital Management System

4.8 Output Design:

Output generally refers to the results and information that is generated by the system. For
the end-user, output is the basic need for developing the system and the basis on which the
usefulness of the system/software will be evaluated. The output may be in one of the following
forms-
A report
A document
A message

In output design too, this has done as per the specification give by the client and also
keeping in min the output requirement. It also includes the relevant reports like individual Sales
person reports, Data wise reports, Invoice reports Quotation reports and Consignor Commission
reports are also generated. The other forms of output are in the forms of messages for the user
which guides him to use the package comfortably, the other types of message is in the forms of
message box, which is trigger when the user makes any mistake, error or when and confirmation
is necessary for further processing.

4.9 Database Tables

Table: Staff
Field Name Data Type Length Constraints Description
S_code Text 10 Primary Key Staff Code
Name Text 20 Not Null Staff Name
Sex Text 5 Not Null Sex
Age Number Integer Not Null Age
Address Memo Memo Not Null Address
Qualification Text 20 Not Null Qualification
Des Text 20 Not Null Designation
Exp Text 20 Not Null Experience
Doj Date/Time Date/Time Not Null Date of Join
Ph_no Number Integer Not Null Phone No
Spl Text 20 Not Null Specialization

Table: Cases Sheet

Field Name Data Type Length Constraints Description
C_no Text 10 Primary Key Case No
P_code Text 10 Foreign Key Patient Code
S_code Text 10 Foreign Key Doctor Code
Dis Details Text 20 Not Null Disease Details
Date Date/Time Date/Time Not Null Date
Time Text 20 Not Null Time

{16}
Hospital Management System

Table: Patient Registration

Field Name Data Type Length Constraints Description
P_code Text 10 Primary Key Patient Code
Name Text 20 Not Null Patient Name
Sex Text 5 Not Null Sex
Age Number Integer Not Null Age
Address Memo Memo Not Null Address
Status Text 20 Not Null Marital Status
Occupation Text 20 Not Null Occupation
Dist Text 20 Not Null District Name
Pin_no Number Long Integer Not Null Pin Code
Ph_no Number Long Integer Not Null Phone No
Date Date/Time Date/Time Not Null Date
Time Date/Time Date/Time Not Null Time

Table: In Patient
Field Name Data Type Length Constraints Description
Ip_code Text 10 Primary Key In Patient Code
P_code Text 10 Foreign Key Patient Code
A_date Date/Time Date/Time Not Null Admit Date
R_no Number Integer Not Null Room No
B_no Number Integer Not Null Bed No
Dis_details Text 20 Not Null Disease Details
Med_pres Text 20 Not Null Medicine Details

Table: Discharge
Field Name Data Type Length Constraints Description
D_no Text 10 Primary Key Discharge No
P_code Text 10 Foreign Key Patient Code
Bill_Paid Text 20 Not Null Patient Name
Amount Number Integer Not Null Bill Amount
Date Date/Time Date/Time Not Null Discharge Date
R_date Date/Time Date/Time Not Null Review Date

{17}
Hospital Management System

CHAPTER 5

CODING AND TESTING

5.1 CODING
After designing each module application programs were written for menus, process and
reports.

Here we have adopted the TOP-DOWN approach of coding, each application modules
was written by considering needs of the user and the storage sectors of the database. The job of
the application program is to provide the interface between the tables (Database) and the screen
(forms) and facilitates the user with different validation checks for data entry.

5.2 TESTING
5.2.1 Introduction
Testing is the major quality control measured employed during software development. Its
basic function is to detect errors in the software. Testing not only to uncover the errors
introduced during coding, but also errors introduced during the previous phases. The goal of
testing is to uncover requirement design or coding errors in the programs, consequently different
levels of testing are employed.

5.2.2 Type of Testing

Unit Testing:
This is the starting point of testing; GSMS system is tested simultaneously with the
coding phase. The purpose is to exercise the different parts of the module code to detect coding
errors.

Integration Testing:
During the integration of all the levels (modules) the integration testing is performed. The
goal of this testing is to detect design errors. While focusing on testing the interconnection
between the levels or (modules).

System Testing:
System testing performed against the system requirement to see if all the requirements
are met and the GSMS system performs as specified by the requirements.

Acceptance Testing:
This is done in front of the clients on the real data of the client, the GSMS system was
found to be working perfectly as it was designed.

Validation Testing:
Validation testing is and as the part of the software requirements analysis, and validated
against the software already been designed. This test provides the final assurance of against the
software, meets all the functional, behavior performance requirements, and the errors, which are
uncovered during the testing.

{18}
Hospital Management System

Deviation or errors discovered at this step in this project is corrected prior to completion
of the project with the help of user by negotiating to establish a method for resolving
deficiencies. Thus, the proposed system under consideration has been tested by using validation
testing and found to be working satisfactorily.

Output Testing:
The output generated or displayed by the system under consideration is tested by asking
the user about the format required by them. Here the output format is considered in two ways.
One is on the screen is found to correct as the format was designed in the system design phase
according to the specified requirements. Some minor changes proposed by the user are done
immediately. Hence, output testing did not result in any correction in the system.

{19}
Hospital Management System

Private Sub cmd_Cancel_Click()

End
End Sub

Private Sub cmd_OK_Click()

If UCase(txt_User_Name) = "APTECH" And UCase(txt_Password) = "UPP" Then
Hospital.Show
Else
MsgBox "Yser can not be allowed", vbCritical, "Login"
End If
End Sub

Private Sub cmdAdd_Click()

If Adodc1.Recordset.EOF Then
Adodc1.Recordset.AddNew
txt_s_code = "P1"
Else
Adodc1.Recordset.MoveLast
Adodc1.Recordset.AddNew
txt_P_Code = "P" & Adodc1.Recordset.RecordCount
End If
Button (False)

End Sub

Private Sub cmdCancel_Click()

If MsgBox("Are you sure?", vbQuestion + vbYesNo) = vbYes Then
Adodc1.Recordset.CancelUpdate
Button (True)
End If
End Sub

Private Sub cmdClose_Click()

If MsgBox("Are you sure?", vbQuestion + vbYesNo) = vbYes Then
Unload Me
End If
End Sub

Private Sub cmdEdit_Click()

Button (False)
End Sub

Private Sub cmdFirst_Click()

On Error Resume Next
Adodc1.Recordset.MoveFirst
End Sub

{20}
Hospital Management System

Private Sub cmdLast_Click()

On Error Resume Next
Adodc1.Recordset.MoveLast
End Sub

Private Sub cmdNext_Click()

On Error Resume Next
Adodc1.Recordset.MoveNext
End Sub

Private Sub cmdPrevious_Click()

On Error Resume Next
Adodc1.Recordset.MovePrevious
End Sub

Private Sub Form_Activate()

Hospital.StatusBar1.Panels(2).Text = Me.Caption
End Sub

Private Sub cmdSave_Click()

On Error Resume Next
If txt_name = "" Then
MsgBox "You must enter the Name", vbCritical
txt_name.SetFocus
Exit Sub
End If
If MsgBox("Do you want to save this record?", vbQuestion + vbYesNo) = vbYes Then
Adodc1.Recordset("p_code") = txt_P_Code
Adodc1.Recordset.Update
Button (True)
End If
End Sub

Private Sub Form_Deactivate()

Me.Hide
End Sub

Private Sub Form_Load()

On Error Resume Next
Button (True)
End Sub

Private Sub Clear()

On Error Resume Next

{21}
Hospital Management System

txt_P_Code = ""
txt_date = ""
txt_time = ""
txt_name = ""
txt_age = ""
txt_sex = ""
txt_occupation = ""
txt_status = ""
txt_address = ""
txt_pincode = ""
txt_email = ""
txt_district = ""
txt_phone = ""
End Sub

Public Function Button(bval As Boolean)

cmdAdd.Visible = bval
cmdSave.Visible = Not bval
cmdEdit.Visible = bval
cmdCancel.Visible = Not bval
cmdClose.Visible = bval
cmdFirst.Visible = bval
cmdPrevious.Visible = bval
cmdNext.Visible = bval
cmdLast.Visible = bval

'txt_P_Code.Locked = bval
txt_date.Enabled = Not bval
txt_time.Enabled = Not bval
txt_name.Locked = bval
txt_age.Enabled = Not bval
txt_sex.Locked = bval
txt_occupation.Locked = bval
txt_status.Locked = bval
txt_address.Locked = bval
txt_pincode.Enabled = Not bval
txt_email.Locked = bval
txt_district.Locked = bval
txt_phone.Enabled = Not bval
End Function

{22}
Hospital Management System

CHAPTER 6
Introduction to MS-Access 98 and Visual Basic 6.0

6.1 Ms-Access 98:

Microsoft Access 98 is used as the back end for this project. Microsoft Access 98 offers
many new and improved feature to help you create powerful database applications. Microsoft
access is used as the back end with Visual Basic as front end will have added advantage because
both are Microsoft products. Microsoft Access does not load software components that are not
required for all databases. Such as Visual Basic for Applications and data Access Objects. Until
they are needed. This shortens the time it takes database to load and improves overall
performance.

Microsoft Access does not load modules, including form modules, until the Visual Basic
in a module is executed. This improves overall performance. You can optimize bulk update
queries for ODBC data sources by sending the query to the server where all the appropriate
records are processed at once instead of one record at a time.

You can set a reference from a Visual Basic project in one Microsoft Access database to
a project in another Microsoft Access database, a library database. Once you have set reference,
you can run Visual Basic procedures in the referenced project.

6.2 Visual Basic:

Visual Basic has been the tool choice for database programmers everywhere. Visual
Basic is one of the popular visual programming tools that bring smile back on the programming
face. A Visual programming environment provides all features that are required to develop a
graphical interface as ready-to-use components. The visual programming environments display a
list available components.

The new features of Visual Basic 6.0 are Active X technology, data access controls, the
development environment, client/server development, or the language itself. We can begin an
application, creating its features, fine tuning it, or getting it ready for distribution and can be
parted to any system.

It provides language reference updates such as objects, properties, function methods,

class modules, and Collection Class module, events, statements, Constants and error meassages.

Microsoft Visual Basic version 6.0 is the popular programming language. With its new
features, Visual Basic is and even stronger contender in the enterprise application development
area that ever before. Visual Basic play a key role in data access strategy of large and small
organization alike. Almost all Visual Basic Application involves connection relational database
management system (RDBMS).

You can develop robust stand-alone application, games and utilities in less time than it
takes in other languages. You can also use ActiveX Technology to create Internet enabled
applications that are limited only by your imagination. When used in conjunction with the

{23}
Hospital Management System

Windows API, you are armed with a serious programming tool for which you can do almost
anything in the you project development efforts.

6.3 Crystal Report Designer

The Crystal Report Designer is the user interface for creating and manipulating database
report. A gallery of report expert gives users and easy “Point and Click” approach to crating
reports. Reports can be further customized within the design window or while viewing the report
data within the preview window. The Crystal Report Designer is sophisticated in its ability to
provide a powerful report design capabilities such as sub reports, overlapping section and
conditional formatting through an simple and intuitive user interface.

6.4 Crystal Report Engine

The Crystal Report Engine is the core of Seagate. Crystal Reports and its elements.
Which stands out above all other query and reporting products. The multi-pass engine the bulk of
the report processing work, including sorting grouping, totaling and formatting. In addition to
being used within the crystal report Designer, the Crystal Report Engine is callable by the most
popular window application development environments.

{24}
Hospital Management System

CHAPTER 7

Conclusion

“Hospital Management System” is a user friendly, menu driven and easily maintainable.
Many control details are stored in separate tables. These names can be altered without altering
the programs. Thus data independence is achieved. Since table are normalized. Redundancy and
anomalies are reduced.

Manual system used to take hours together to search a particular record, but his
computerized system will take a few seconds to do the above said operations.

This system is easy to handle and provides timely reports and faster access to the
information. This system has been tested with sample as well as lives data converting all possible
options and its performance is commendable.

{25}
Hospital Management System

APPENDIX-A[FORMS AND REPORTS]

Main Form

Patient Information Form

{26}
Hospital Management System

Inpatient Information Form

Staff Information Form

{27}
Hospital Management System

Patient Information Report

Staff Information Report

{28}
Hospital Management System

Cases Sheet Report

{29}
Hospital Management System

APPENDIX-B [TIME CHART]

Activities No. of Days Effective Hours Percentage

Learning 2.5 200 14.3%
System Analysis 30 240 17.15%
System Design 25 200 14.3%
Database Design 15 120 8.6%
Screen Design 10 80 5.7%
Coding 15 120 8.6%
Testing 30 240 17.05%
Documentation 25 50 14.3%
Total 152.5 1250

Learning

System
Analysis
System design

Database
Design
Screen Design

Coding

Testing

Documentation

{30}
Hospital Management System

APPENDIX-C [BIBLILOGRAPHY]

• Software Engineering  Roger.S. Pressmen.

• Analysis and design of information System  James.A.Senn.

• Database System Concept  Henry.F.Korth.

• Microsoft Access  Steven Holzne

• Visual Basic 6.0 Database  Eric WinMiller.

• Visual Basic 6.0  SSI Material

{31}