B.RATHOD
20132014
HOSPITAL
MANAGEMENT SYSTEM
ACKNOWLEDGEMENT
PROJECT MEMBER:
Pramod B. Rathod.
INDEX
Sr. No
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
2.1
2.2
2.3
2.4
2.5
2.6
2.7
TOPIC
PRELIMINARY INVESTIGATION
ORGANIZATIONAL OVERVIEW
OBJECTIVES
CURRENT SYSTEM
LIMITATION OF CURRENT SYSTEM
PROPOSED SYSTEM AND ITS ADVANTAGES
FEASEBILITY STUDY
STAKEHODER
PROCESS MODEL
ACTIVITY SHEETS
GANTT CHART
SYSTEM ANALYSIS
EVENT TABLE CONTENTS
USE CASE DIAGRAM
E-R DIAGRAM
ACTIVITY DIAGRAM
CLASS DIAGRAM
SYSTEM SEQUENCE DIAGRAM
SEQUENCE DIAGRAM
SYSTEM DESIGN
CONVERTING ERD TO CLASS DIAGRAM
DATA DICTIONARY
COMPONENT DIAGRAM
PACKAGE DIAGRAM
DEPLOYMENT DIAGRAM
MENU TREE
CRUD TABLE
SYSTEM CODING
VALIDATION
TEST CASE, TEST DATA, TEST RESULT
SCREEN LAYOUT
MAINTANANCE AND EVALUATION
FUTURE ENHANCEMENT
REFERENCES AND BIBLIOGRAPHY
PRELIMINA
RY
INVESTIGAT
ION
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4.1
4.2
4.3
5.1
5.2
ORGANIZATIONAL
OVERVIEW
LIFE CARE HOSPITALS is multi-specialty, tertiary care
hospital extending quality health care service to people in
and around Madurai for the past 12 years.
The hospital was founded by Dr.S.Rajendran who is a
leading Laser and Laparoscopic surgeon.
The hospital is located at Dhanappa Mudali Street which is
very near to Madurai Meenakshi Amman Temple.
OBJECTIVE
The objective of the hospital management system is
consistent growth of the Hospital, through continual
improvement in the processes.
To provide quick, reliable, quality and error free service by
making use of high end technology to ease the management
of the patients.
To help administration in efficient management of the
organization very smoothly by achieving high competency.
CURRENT SYSTEM
A Hospital is a place where Patients come up for general
diseases.
Hospitals provide facilities like:
o Consultation by Doctors on Diseases.
o Diagnosis for diseases.
o Providing treatment facility.
o Facility for admitting Patients (providing beds, nursing,
medicines)
o Immunization for Patients/Children.
Various operational works that are done in a Hospital are:o Recording information about the Patients that come.
o Generating bills.
o Recording information related to diagnosis given to
Patients.
o Keeping record of the Immunization provided to
children/patients.
o 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:o Information about Patients is done by just writing the
Patients name, age and gender.
10
LIMITATION OF CURRENT
SYSTEM
Problems with conventional system
1. Lack of immediate retrievals: -The information is very
difficult to retrieve and to find particular information like- E.g.
- To find out about the patients history, the user has to go
through various registers.
This results in inconvenience and wastage of time.
11
12
13
ADVANTAGES OF PURPOSED
SYSTEM
o Planned approach towards working: - The working in the
organization will be well planned and organized. The data will
be stored properly in data stores, which will help in retrieval of
information as well as its storage.
o Accuracy: - The level of accuracy in the proposed system will
be higher. All operation would be done correctly and it ensures
that whatever information is coming from the center is
accurate.
o Reliability: - The reliability of the proposed system will be
high due to the above stated reasons. The reason for the
increased reliability of the system is that now there would be
proper storage of information.
o No Redundancy: - In the proposed system utmost care would
be that no information is repeated anywhere, in storage or
otherwise. This would assure economic use of storage space
and consistency in the data stored.
o Immediate retrieval of information: - The main objective of
proposed system is to provide for a quick and efficient retrieval
of information. Any type of information would be available
whenever the user requires.
o Immediate storage of information: - In manual system
there are many problems to store the largest amount of
information.
14
15
FEASEBILITY STUDY
The Project Feasibility is concerned with expected benefits.
An important outcome of the preliminary investigation is the
destination that the proposed system is feasible.
There are two aspects in the feasibility study portion of
the preliminary investigation.
Economic Feasibility
Operational Feasibility
Technical Feasibility
ECONOMIC FEASIBILITY:
It is considered mainly of two tests:
a) Anticipated Value of benefit is greater than cost of
development
b) Does the organization have adequate cash flow to fund
the project?
17
OPERATIONAL FEASIBILITY:
18
Technical Feasibility:
It is based on computer hardware and network software.
Additional peripheral devices are required and funds are
available in industry.
The Software used for the development of proposed system
is:
19
STAKEHOLDERS
Stakeholders are anyone who has an interest in the project.
Project stakeholders are individuals and organizations that
are actively involved in the project, or whose interests may
be affected as a result of project execution or project
completion. They may also exert influence over the projects
objectives and outcomes. The project management team
must identify the stakeholders, determine their requirements
and expectation, and, to the extent possible, manage their
influence in relation to the requirements to ensure a
successful project.
The people involved in the project development are:
DEVELOPER:
Here in this project the Developer is PRAMOD B. RATHOD
PROJECT LEADER:
Here in this project the project leader are Professors:
Prof.Vaishali Kadam & Prof.Smita Dalvi who guides me in my
project.
20
ADMIN:
21
PROCESS MODEL
22
ACTIVITY SHEET
23
SR
No
Activity
Planned
Start Date
Sig
n
Actual
End Date Start Date
End Date
Preliminar
y
20/11/201 29/11/20
Investigati 3
13
on
20/11/201
3
5/12/201
3
System
Analysis
30/11/201 20/12/20
3
13
30/11/201
3
30/12/20
13
System
Design
21/12/201 10/01/20
3
14
21/12/201
3
20/01/20
14
System
Code
11/01/201 12/02/20
4
14
20/01/201
4
22/02/20
14
System
Testing
13/02/201 11/03/20
4
14
13/02/201
4
22/03/20
14
Project
12/03/201 28/03/20
Terminatio
4
14
n
12/03/201
4
08/04/20
14
24
GANTT
CHART
Generally the further part of this documentation is a
NOTE:
25
26
SYSTEM
ANALYSIS
27
EVENT TABLE
CONTENT
28
Activity
Response
Destinati
on
Verifying
details
Requesting
to retrieve
password
Changing
Password
Adding
Doctor
Deleting
Doctor
Adding
Receptionist
Login
Confirmed
Admin
Password Sent
Admin
Password
Changed
Database
Doctor added
Database
Event
Trigger
Source
Admin Logs In
Login
Admin
Admin Forget
Password
Forgot
Password
Admin
Admin change
Password
Admin adds
doctor
Admin deletes
doctor
Admin adds
receptionist
Admin
deletes
receptionist
Change
Password
Admin
New doctor
Admin
Delete doctor
Admin
New
receptionist
Admin
deletes
receptionist
Admin
Deleting
Receptionist
Receptionist
deleted
Database
Admin view
details
Doctor or
Receptionist
details
Admin
Verifying
Details
Details
Checked
Admin
Admin view
Patients details
Patients
details
Admin
Details
Checked
Admin
Admin check
wards
Wards details
Admin
Details
Checked
Admin
Admin add
medicine stock
Admin update
Medicine Stock
Admin delete
medicine
Admin add new
treatments
facility
Admin update
treatment
facility
29
Adding new
medicine
stock
Updating
medicine
stock
Delete
Medicine
Add
treatment
Update
treatment
Studying
patient case
history
Checking
wards
availability
Doctor
deleted
Receptionist
added
Database
Database
Admin
Adding
medicine
Medicine
Added
Database
Admin
Updating
medicine
Medicine
Updated
Database
Admin
Deleting
Medicine
Medicine
Deleted
Database
Admin
Adding
treatment
Treatment
added
Database
Admin
Updating
treatment
facility
Treatment
updated
Database
Admin delete
treatment
Admin adds
staff
Admin deletes
staff
Delete
treatment
Admin
Deleting
treatment
Treatment
deleted
Database
Add staff
Admin
Adding staff
Staff Added
Database
Delete Staff
Admin
Deleting staff
Staff Deleted
Database
30
Patient report
Trigger
Source
Activity
Response
Login
Receptioni
st
Verifying
details
Login
Confirmed
Destinatio
n
Receptioni
st
Change
Password
Receptioni
st
Changing
Password
Password
Changed
Receptioni
st
New
patients
Receptioni
st
Adding new
patient
Patient added
Database
Receptioni
st
Updating
patients
health
Patient
updated
Database
Receptioni
st
Reporting
patient
details
Report handed
Patient
Patients
Paying bill
Collecting
payment
Receptioni
st
Update
patient
current
status
Generate
patient
report
Payment of
Hospital
charges
Receptionist
enter payment
details
Enter
payment
Receptioni
st
Adding
payment
Payment
added
Database
Receptionist
allocate
appointment
Allocation of
appointment
Receptioni
st
Adding
appointment
Appointment
confirmed
Database
Send
confirmation
Cancelation
of
appointment
sent to
patient
Receptioni
st
Sending
confirmation
Confirmation
sent
Patient
Receptioni
st
Sending
cancelation
information
Cancelation
information
sent
Patient
Inform patient
for appointment
Cancel
appointment
31
Trigger
Source
Activity
Response
Destinatio
n
Doctor logs in
Login
Doctor
Verifying
details
Login
Confirmed
Doctor
Doctor change
Password
Change
Password
Doctor
Password
Changed
Doctor
Doctor update
profile
Update
profile
Doctor
Changing
Password
Updating
his/her
profile
Profile
updated
Database
Patient
updated
Database
Patient
deleted
Database
Review added
Database
Update patients
Doctor delete
patient
Add disease
review
Update disease
review
Delete disease
review
Doctor view
patients reports
32
Update
patient
current
status
Delete
patient
Add review
Update
review
Delete
review
Checking
Doctor
Doctor
Doctor
Doctor
Doctor
Updating
patients
health
Deleting
patients
Adding
review
Updating
review
Deleting
review
Review
updated
Review
Deleted
Database
Database
USE CASE
DIAGRAM
33
Admin Login
SYSTEM
Change
Password
Admin
Retrieve Forgotten
Password
Adds/Deletes/Views doctor
Adds/Deletes/Views receptionist
check wards
Admin
Adds/Updates/Deletes/ Views
medicine stock
Adds/Updates/Deletes/ Views
treatment facility
Adds/Updates/Deletes/ Views
staff details
Adds/Update/Views Patients
Reception
Adds/Updates appointment
Cancel appointment
36
Update profile
Update/Delete patients
SYSTEM
Add/Update/Delete disease
review
Doctor
view patients reports
37
E-R DIAGRAM
38
ACTIVITY DIAGRAM
39
40
41
42
43
CLASS DIAGRAM
44
45
SEQUENCE DIAGRAM
46
47
48
SYSTEM SEQUENCE
DIAGRAM
49
SYSTEM
ADMIN
Authenticate Admin
Admin authenticated
Change password
Update Password
Add, deletes, view doctor details
Add/ View/ Delete Doctor
Adds, deletes, view receptionist details
Add/ View/ Delete receptionist
View Patient details
View Patient details
Check, View ward details
Checks ward details
Adds, Update, Delete medicine details
Adds/ Update/ Delete medicine details
Adds, Update, Delete Treatment details
Adds/ Update/Delete treatment details
50
SYSTEM
RECEPTIONIST
Receptionist authentication
Receptionist authenticated
Change password
Update Password
Add, updates, view patients details
Add/ Updates/ Delete patients
Adds, deletes, view receptionist details
Add/ View/ Delete receptionist
Generate Patients report details
View/Generate Patient report details
Add, Check, View payment details
Add/Checks/View payment details
Adds, Update, Delete appointment
Adds/ Update/ Delete appointment details
Inform patient appointment details
Inform patient details
SYSTEM
DOCTOR
Doctor authentication
Doctor authenticated
Change password
Update Password
Updates, view, delete patients
Updates/View/ Delete patients
Adds, deletes, view profile details
Add/ View/ Delete profile
Add, Updates, deletes disease review
Add/Update/delete disease review
View patients reports details
Views patient reports
52
53
SYSTEM
DESIGN
CONVERTING ERD TO
CLASS DIAGRAM
54
Handles
-username
Database
-password
-HMS
Admin
Patient
-username
-ID
-password
-Add
-Name
-Sex
-Age
-ContactNo
DateAddimitted
DateDischarge
d
55
Handles
Patient
-ID
-ID
-Add
-Name
-Sex
-Age
-ContactNo
DateAddimitted
DateDischarge
d
Handles
Patient
-ID
-Add
-Name
-Sex
-Age
-ContactNo
DateAddimitted
DateDischarge
d
56
Handles
Patient
-ID
-Price
-Add
-Description
-Name
-Sex
-Age
-ContactNo
DateAddimitted
DateDischarge
d
Handles
Patient
-ID
-Add
-Name
-Sex
-Age
-ContactNo
DateAddimitted
DateDischarge
d
57
Employee
Doctor
-ID
-Visiting
-Qualification
-Permanent
-Name
-Traniee
Handles
-Sex
-Salary
-ContactNo
-Experience
Employee And Nurse
Employee
Nurse
-ID
-ID
-Qualification
-Permanent
-Name
-Traniee
Handles
-Sex
-Salary
-ContactNo
-Experience
58
Employee
Receptionist
-ID
-ID
-Qualification
-PartTime
-Name
-FullTime
Handles
-Sex
-Salary
-ContactNo
-Experience
Records And Receptionist
Records
Receptionist
-Appointment
-ID
PatientInformat
ion
-RecordNo
-PartTime
Handles
59
-FullTime
DATA DICTIONARY
60
COMPONENT DIAGRAM
61
62
PACKAGE DIAGRAM
63
VIEW LAYER
Admin
Login
Patient
Details
Employee
Detail
Treatment
Details
Medicine
Details
Equipment
Details
Room
Details
Record
Details
DOMAIN LAYER
Admin
Class
Patient
Class
Employee
Class
Treatment
Class
Medicine
Class
Equipment
Class
Room
Class
Record
Class
64
dbo.Admin
dbo.
Patient
dbo.Emplo
yee
dbo.
Treatment
dbo.
Medicine
dbo.
Equipment
dbo. Room
dbo.
Record
CRUD TABLE
65
Table Process
Doctor
Recepti
onist
Patient
Medicin
e
Treatm
ent
Admin Main
Form
Record
s
R,U
Patient Main
Form
Patient Add
Form
Patient
Modify Form
Patient
Remove Form
Records Main
Form
Records Add
Form
Records
Modify Form
Records
Remove Form
Medicine
Main Form
Medicine Add
Form
Medicine
Modify Form
Medicine
Remove Form
Treatment
Main Form
Treatment
Add Form
Treatment
Modify Form
Treatment
Remove Form
66
Admin
DEPLOYMENT DIAGRAM
67
68
SYSTEM
CODING
69
MENU TREE
70
Admin
Login
Employee
Doctor
Nurse
Receptionist
Patient
Treatment
Medicine
Equipment
Room
71
VALIDATIONS
o Validation for empty ID field:
If the ID field is empty then display a message box
ID Field Empty.
o Validation for empty Password field:
If the Password field is empty then display a
message box Password Field Empty.
o Validation for mandatory field:
If the mandatory field is empty then display a
message box Field marked mandatory cannot be
blank.
o Validation for doctor code field:
If the code entered is already present in Doctor
table then display a message box Code already
exists.
o Validation for patients code field:
If the code entered is already present in patients
table then display a message box Code already
exists.
o Validation for Staff code field:
If the code entered is already present in Staff table
then display a message box Code already exists.
72
73
TEST CASES
TEST DATA
TEST
RESULT
74
Expected
Result
Admin and
password
Will allow to
enter into main
form
Test Case
Test Data
State
Login Form
Valid
User name
must correct
Valid
doctorID
and password
Will allow to
enter into main
form
User name
must correct
Valid
receptionistID
and password
Will allow to
enter into main
form
Ward number,
patient name
Properly
filled
Some correct
values
Patient
name,sex,mobil
e number,age
Data
should be
according
datatype
Values
inserted
should be
correct
Will allocate
the ward to
patient name
Doctor
information
Form
Receptionist
information
Form
Ward Form
Patient Form
75
Test Input
Value
Form Name
Patient will be
added
SCREEN
LAYOUTS
76
77
MAINTENAN
CE
AND
BIBLIOGRA
PHY
78