Hospital Management System: DEPT OF CSE, Dr. A.I.T, 2014-2015

HOSPITAL MANAGEMENT SYSTEM
CHAPTER1
INTRODUCTION
HOSPITAL MANAGEMENT SYSTEM is a computerized management system. This
management system has been developed to form whole management system including
Employees, Doctors, Nurses, Patients, Bills, and Complains etc. The proposed system will
keep a track of Employees, Doctors, Patients, Accounts and generation of report regarding
the present status.
Health of citizen is the wealth of Nation. By using the cutting edge technologies, Hospital
Management can be improved with efficient work flow and communication. Details of the
Patients, their previous visits etc. are totally not perceptible without a computer. Relevant
Informations are always stored in the computer and are available instantly in front of the
user.
The project Hospital Management System is aimed to develop to maintain the day-to-day
state of admission/discharge of Patients, List of Doctors, List of medicines, Bills etc.
There are following main objectives of the Hospital:
Keeping records of admission of patient.
Keeping patient-care as utmost priority. Scheduling the appointment of Patient with

Doctor to make it convenient for both.
Keeping the records of prescriptions provided by the doctor to the patients.
Keeping records of Medicine department in an arranged order so that the treatment of

Patient becomes quick and satisfactory.
Keeping details about the consultants, their Prescriptions and treatments, surgery
reports etc.
DEPT OF CSE, Dr. A.I.T, 2014-2015
Page 1
CHAPTER 2
LITERATURE SURVEY
Hospital Management System provides the benefits of streamlined operations, enhanced
administration & control, superior patient care, strict cost control and improved profitability.
Hospital Management System is powerful, flexible, and easy to use and is designed and
developed to deliver real conceivable benefits to Hospitals and hospitals. More importantly it
is backed by reliable and dependable support.
The Hospital Management System is designed for multispecialty Hospitals, to cover a wide
range of Hospital administration and management processes. It is an integrated end-to-end
Hospital Management System that provides relevant information across the Hospital to
support effective decision making for patient care, Hospital administration and critical
financial accounting, in a seamless flow.
A Hospital is a place where Patients come up for general diseases. Hospitals provide facilities
like:Consultation by Doctors on Diseases.
Diagnosis for diseases.
Providing treatment facility.
Facility for admitting Patients (providing beds, nursing etc.)
Various operational works that are done in a Hospital are:Recording information about the Patients that come.
Generating bills.
Recording information related to diagnosis given to Patients.
Keeping record of treatment.
Keeping information about various diseases and medicines available to cure them.
These are the various jobs that need to be done in a Hospital by the operational staff and
Doctors. All these works are done on papers. The work is done as follows: Information about Patients is done by just writing the Patients name, age and gender.
Whenever the Patient comes up his information is stored freshly.
Bills are generated by recording price for each facility provided to Patient on a separate
sheet and at last they all are summed up.
Diagnosis information to patients is generally recorded on the document, which contains
Patient information. It is destroyed after some time period to decrease the paper load in the
office.
Immunization records of children are maintained in pre-formatted sheets, which are kept in
a file.
Page 2
Information about various diseases is not kept as any document. Doctors themselves do this
job by remembering various medicines.
All this work is done manually by the receptionist and other operational staff and lot of
papers are needed to be handled and taken care of. Doctors have to remember various
medicines available for diagnosis and sometimes miss better alternatives as they cant
remember them at that time.
The limited time and resources have restricted us to incorporate, in this project, only main
activities that are performed in a Hospital Management System, but utmost care has been
taken to make the system efficient and user friendly. It has been designed to computerize the
following functions that are performed by the system:
On Line Appointments for the Patients which includes admission of New Patient
Discharge detail functions which includes discharge of patient and doctor assigning related to
patients disease
Statement of patient details which includes admitted patient, discharged patient and doctor details
Total number of Patients admitted in the Hospital
Doctors available in the Hospital
Routine health check-ups
Administrator Links which includes Login, addition of new doctors and sisters/ward boys
Page 3
CHAPTER 3
SYSTEM REQUIRMENT SPECIFICATION

3.1 HARDWARE REQUIREMENTS
RAM Capacity 512MB Or Above

Processor : Pentium IV Or Above
Hard Disk : 20GB Or Above
Monitor
: SVGA Color
Keyboard : 104 keys
3.2 SOFTWARE REQUIREMENTS
Operating System
Back End
Front End
: Windows XP/7/8
: MS ACCESS
: VISUAL STUDIO 2005/2008
3.3 NON FUNCTIONAL REQUIREMENTS

These are functionalities that are generally implied and are factored in as characteristics of a
good system. They are not part of the system requirements.
Should be reliable and efficient.
Easy to maintain
Ensure security of the stored information.
3.4 FUNCTIONAL REQUIREMENTS

Following are inherent functionalities that the system is expected to perform to achieve goals
for the development.
Data storage-the system provides data storage capabilities. This is enhanced by

database management system that is capable managing the storage requirements.
Retrieval of data-it should be easier to retrieve data from the database through
procedures designed to ensure efficiency.
Registration processing:-registration should be done promptly and without delay or
errors.
Searching-records should retrieve records on c click of a button without unnecessary
delays as requested by the user.
Page 4
CHAPTER 4
SYSTEM DESIGN
Design is the first step into the development phase for any engineered product or system.
Design is a creative process. A good design is the key to effective system. The term design
is defined as the process of applying various techniques and principles for the purpose of
defining a process or a system in sufficient detail to permit its physical realization. It may be
defined as a process of applying various techniques and principles for the purpose of defining
a device, a process or a system in sufficient detail to permit its physical realization. Software
design sits at the technical kernel of the software engineering process and is applied
regardless of the development paradigm that is used. The system design develops the
architectural detail required to build a system or product. As in the case of any systematic
approach, this software too has undergone the best possible design phase fine tuning all
efficiency, performance and accuracy levels. The design phase is a transition from a user
oriented document to a document to the programmers or database personnel. System design
goes through two phases of development: Logical and Physical Design.
4.1. INPUT DESIGN

The design of input focuses on controlling the amount of input required, controlling the
errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is
designed in such a way so that it provides security and ease of use with retaining the
privacy.
4.2. OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents the
information clearly. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and
direct source information to the user. Efficient and intelligent output design improves the
systems relationship to help user decision-making.
Designing computer output should proceed in an organized, well thought out manner; the
right output must be developed while ensuring that each output element is designed so
that people will find the system can use easily and effectively.
Page 5
4.3. DATABASE DESIGN

A database is an organized mechanism that has the capability of storing information
through which a user can retrieve stored information in an effective and efficient
manner. The data is the purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements are
gathered together and a database is designed which will meet these requirements as
clearly as possible. This step is called Information Level Design and it is taken
independent of any individual DBMS.
In the second step, this Information level design is transferred into a design for the
specific DBMS that will be used to implement the system in question. This step is
called Physical Level Design, concerned with the characteristics of the specific
DBMS that will be used. A database design runs parallel with the system design.
4.4. USECASE DIAGRAM

A Use case is adescriptionof set of sequenceof 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. The usecase diagram of
Hospital Management System is as shown:
Page 6
4.5. DATA FLOW DIAGRAMS

IAGRAMS:
The DFD takes an input-process
process-output
output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of the
software. Data objects represented by labeled arrows and transformation are represented by
circles also called as bubbles. DFD is presented in a hierarchical fashion i.e. the first data
flow model represents the system as a whole.The DFD enables the software engineer to
develop models of the information
information domain & functional domain at the same time. As the
DFD is refined into greater levels of details, the analyst performs an implicit functional
decomposition of the system. At the same time, the DFD refinement results in a
corresponding refinement of the
the data as it moves through the processes that embody the
applications. The DFD for
or Hospital Management System is as shown:

2015
Page 7
4.6. E-R Diagram:

The Entity-Relationship (ER) model is a way to unify the network and relational database
views. Simply stated the ER model is a conceptual data model that views the real world as
entities and relationships. A basic component of the model is the Entity-Relationship diagram
which is used to visually represent data objects. The ER diagram for Hospital Management
System is as shown:
Page 8
Page 9
CHAPTER 5
IMPLEMENTATION
Pseudo Code: The pseudo code below consists of a starting Login form and five sub-forms called
Routinecheckup, patient admit, patient discharge, ad doctor and add sister/wardboy.
5.1 Code for routine check-up form

Imports System.Data
Imports System.Data.OleDb
Imports System
Public Class frmClinicalCheckup
Inherits System.Windows.Forms.Form
Public save_flag As Boolean
#Region "Load event of frmClinicalCheckup"
Private Sub frmClinicalCheckup_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
Fill_Textbox_Clinic()
fill_listview()
If LV_PatiView.Items.Count = 0 Then
'MessageBox.Show("There is no record to show.", "Error", MessageBoxButtons.OK,
MessageBoxIcon.Error)
btnRegisterPatient.Enabled = True
btnAdmit.Enabled = False
btnCustomprint.Enabled = False
cbDoctor.Enabled = False
Rtxt_Remark.ReadOnly = True
Else
btnSaveRegistration.Enabled = False
btnCancelRegistration.Enabled = False
txtDisease.ReadOnly = False
CB_Bloodgp.Enabled = True
cbDoctor.Enabled = True
Rtxt_Remark.ReadOnly = False
End If
End Sub
#End Region
Page 10
5.2 Code for Admit Patient form

#Region "Load event of frmAdmitPatient"
Private Sub frmAdmitPatient_Load(ByVal sender As System.Object, ByVal e As
Fill_Textbox_Admit()
fill_listview()
If LV_PatiView.Items.Count = 0 Then
btnRegisterPatient.Enabled = True
btnEditRegistration.Enabled = False
'btnDeleteRegistration.Enabled = False
Else
btnCancelRegistration.Enabled = False
CB_BedCategory.Enabled = False
CB_Bedno.Enabled = False
End If
End Sub
#End Region
Page 11
5.3 Code for Discharge patient form

Private Sub frmDischarge_Load(ByVal sender As System.Object, ByVal e As
Fill_Textbox_Discharge()
fill_listview()
If LV_Discharge.Items.Count = 0 Then
btnDeleteRegistration.Enabled = False
'btnPrint.Enabled = False
btnCustomprint.Enabled = False
End If
End Sub
Private Sub btnCustomprint_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles btnCustomprint.Click
Dim objfrmcheckbox = New frmCheckBox(Me, "c:\hm.mdb", "discharge")
objfrmcheckbox.show()
End Sub
Page 12
CHAPTER 6
SYSTEM TESTING
Software Testing is the process of executing software in a controlled manner, in order to
answer the question - Does the software behave as specified?. Software testing is often
used in association with the terms verification and validation. Validation is the checking
or testing of items, includes software, for conformance and consistency with an associated
specification. Software testing is just one kind of verification, which also uses techniques
such as reviews, analysis, inspections, and walkthroughs. Validation is the process of
checking that what has been specified is what the user actually wanted.
Validation
:Are we doing the right job?
Verification:Are we doing the job right?

Software testing should not be confused with debugging. Debugging is the process of
analyzing and localizing bugs when software does not behave as expected. Although the
identification of some bugs will be obvious from playing with the software, a methodical
approach to software testing is a much more thorough means for identifying bugs.
Debugging is therefore an activity which supports testing, but cannot replace testing.
Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers
based system. Nothing is complete without testing, as it vital success of the system testing
objectives, there are several rules that can serve as testing objectives. They are
For correctness
For implementation efficiency
For computational complexity
6.1 TEST PLAN

A test plan implies a series of desired course of action to be followed in accomplishing
various testing methods. The Test Plan acts as a blue print for the action that is to be
followed. The software engineers create a computer program, its documentation and
related data structures. The software developers is always responsible for testing the
individual units of the programs, ensuring that each performs the function for which it
was designed. There is an independent test group (ITG) which is to remove the inherent
problems associated with letting the builder to test the thing that has been built. The
specific objectives of testing should be stated in measurable terms. So that the mean time
Page 13
to failure, the cost to find and fix the defects, remaining defect density or frequency of
occurrence and test work-hours per regression test all should be stated within the test
plan.
6.2 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software design the
software component or module. Using the component level design description as a guide,
important control paths are tested to uncover errors within the boundary of the module.
The relative complexity of tests and uncovered scope established for unit testing. The unit
testing is white-box oriented, and step can be conducted in parallel for multiple
components. The modular interface is tested to ensure that information properly flows
into and out of the program unit under test. The local data structure is examined to ensure
that data stored temporarily maintains its integrity during all steps in an algorithms
execution. Boundary conditions are tested to ensure that all statements in a module have
been executed at least once. Finally, all error handling paths are tested.
Tests of data flow across a module interface are required before any other test is initiated.
If data do not enter and exit properly, all other tests are moot. Selective testing of
execution paths is an essential task during the unit test. Good design dictates that error
conditions be anticipated and error handling paths set up to reroute or cleanly terminate
processing when an error does occur. Boundary testing is the last task of unit testing step.
Software often fails at its boundaries.
6.3 INTEGRATION TESTING

Integration testing is systematic technique for constructing the program structure while at
the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested components and build a program structure that has been
dictated by design. The entire program is tested as whole. Correction is difficult because
isolation of causes is complicated by vast expanse of entire program. Once these errors
are corrected, new ones appear and the process continues in a seemingly endless loop.
6.4VALIDATION TESTING OR SYSTEM TESTING

This is the final step in testing. In this the entire system was tested as a whole with all
forms, code, modules and class modules. This form of testing is popularly known as
Black Box testing or System testing.
Page 14
Black Box testing method focuses on the functional requirements of the software. That
is, Black Box testing enables the software engineer to derive sets of input conditions that
will fully exercise all functional requirements for a program.
6.5 OUTPUT TESTING OR USER ACCEPTANCE TESTING

The system considered is tested for user acceptance; here it should satisfy the firms need.
The software should keep in touch with perspective system; user at the time of developing
and making changes whenever required. This done with respect to the following points
Input Screen Designs,
Output Screen Designs,
Online message to guide the user and the like.
The above testing is done taking various kinds of test data. Preparation of test data plays a
vital role in the system testing. After preparing the test data, the system under study is
tested using that test data. While testing the system by which test data errors are again
uncovered and corrected by using above testing steps and corrections are also noted for
future use.
Page 15
CHAPTER 7
SNAPSHOTS
Admit Patient form
Page 16
Clinical checkup form
Page 17
Discharge Patient form
Page 18

Hospital Management System: DEPT OF CSE, Dr. A.I.T, 2014-2015

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Hospital Management System: DEPT OF CSE, Dr. A.I.T, 2014-2015

Diunggah oleh

Hak Cipta:

Format Tersedia

HOSPITAL MANAGEMENT SYSTEM

Keeping records of admission of patient.

Keeping patient-care as utmost priority. Scheduling the appointment of Patient with

Keeping the records of prescriptions provided by the doctor to the patients.

Keeping records of Medicine department in an arranged order so that the treatment of

DEPT OF CSE, Dr. A.I.T, 2014-2015