This is my College Project Documentation on Hospital Management System. Which includes mainly Problem Definition, Existing System, Proposed System, Requirement Analysis, Scope of the System, Feasibility Study, Hardware & Software Requirement, ER Diagram, DFD Diagram, Data Dictionary for Project, Sample Output Screenshots, Conclusion
1. 1
Hospital Management System
SUBMITED BY
1. Nikhil Ishwar Patil
GUIDED BY :- Mrs. Chavhan Pallavi
Department Of Computer Science.
K.K.Wagh Arts, Commerce, Science and Computer Science College.
Nashik 422003
Academic Year2020-2021
2. 2
KarmaveerKakasahebWagh Education Society’s
K. K. Wagh Arts Commerce, Science,
&ComputerScienceCollege SaraswatiNagarNashik-422003
C E R T I F I C A T E
This is to certify that Mr./Miss Nikhil Ishwar Patil .
Has satisfactorily completed his/her/their project on
Hospital Management System fulfilment in S.Y.BBA (CA) Department
for the academic year 2020- 2021.
Prof. Chavhan Pallavi. Prof BAVA V.H.
(Project Guide ) H.O.D. of BBA(CA)
Internal Examiner External Examiner
3. 3
ACKNOWLEDGEMENT
We own our sincere gratitude to all those people who have given us their
constant support and encouragement without which our project report would not
have reached this stage.
We would like to express our thanks to Prof.Chavhan Pallavi For her /his
advice and encouragement. She/he has been pillar of strength right through
the project till the preparation of this report and helped by boosting moral, so we
could surmount the difficulties that came across during completion of this
project.
We would like to express our gratitude to Dr.A.P.Rajput,
Principal, K.K.Wagh Arts, commerce, science and Computer Science College.
And Prof. Bava V.H. Head of BBA(CA) department for the supportand the
infrastructure they have provide, so that we could successfully complete the
project on time.
Last but not the list we would like to express our sincere thanks to all staff
members and our friends for their help and cooperation in all phases of
the project.
4. 4
INDEX
Sr.No Title Page NO.
1. Problem Definition. 5
2. Existing System. 6
3. Proposed System. 6
4. Requirement Analysis 7
5. Scope of the system 8
6. Feasibility study 9
7. H/w and s/w requirement. 11
8. ERD. 12
9. DFD 13
10. Data Dictionary. 15
11. Sample I/O Screen. 17
12. Conclusion 22
13. Future Enhancement 23
14. Bibliography 24
5. 5
Problem Definition
Problems with Conventional system
Difficult to retrieve the information(user has to go through various registers to find
single information)
The information generated by various transactions takes time and efforts to be stored
at right place.
Various changes to information like patient details or immunization details of child
are difficult to make as paper work is involved
Preparation of accurate and prompt reports(This becomes a difficult task as
information is difficult to collect from various registers.)
6. 6
The hospital management system is designed for any hospital to replace their
existing manual, paper-based system the new system is to control the following
information: patient information, room info, staff and operating roomschedules,
and patient invoices. These services areto be provided in an efficient, cost
effective manner with the goal of reducing the time and resources currently
required for such tasks.
Proposed System
Existing System
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 throughoutthe hospital management infrastructure.
Often information(on forms) is incomplete
or does not follow management standards forms areoften lost in transitbetween
lost. Multiple copies of the same information exist in the hospital and may lead to
inconsistences in data in various data stores.
7. 7
I have designed the given proposed system to automate the process of
day to day activities of Hospital like Room activities, Admission of New Patient,
Discharge of Patient, assign a Doctor, and finally compute the bill etc., facilities to
the multiple users etc.
The complete set of rules & procedures related to Hospital’s day to day activities
and generating report is called “HOSPITAL MANAGEMENT SYSTEM”. My
project gives a brief idea regarding automated Hospital activities.
The following steps that give the detailed information of the need of proposed
system are:
Performance: During past several decades, the hospital management system is
supposed to maintain manual handling of all the hospital daily activities. The manual
handling of the record is time consuming and highly prone to error. To improve the
performance of the hospital management system, the computerized hospital
management system is to be undertaken. The computerized hospital project is fully
computerized and user friendly even that any of the hospital’s members can see the
patient’s report and the doctor’s report.
Requirement Analysis
8. 8
This system productis the Hospital Management System. The system will be used in
any hospital or clinic. Clinic to get the information from the patients and then storing
that data for future usages. The current system in use is a paper-based system. It is too
slow and cannot provide updated lists of patients within reasonable timeframe. In
hospital management system its data is more important. In this system we can arrange
the data and store in properformat for long time.
This program is developed to make easy the routine work.
Easy to find data or information.
Save lot of manpower and time.
System covers large number of people and try minimize data redundancy.
In this system process ofsummary report is main part, using the
computerized system.
This process is becomesimple and small; you can immediately get the report
for the query.
This system provides interaction user friendliness and also less paper work
Scope of the System
9. 9
–––
The technical issue usually raised during the feasibility stage of the
investigation includes the following:
Does the necessary technology exist to do what is suggested?
Do the proposedequipments have the technical capacity to hold the data
required to use the new system?
Will The proposed systemprovide adequate responseto inquiries,
regardless of the number or location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and
Data security?
TechnicalFeasibility
Feasibility Study
Preliminary investigation examines project feasibility, the likelihood
the system will be useful to the organization. The main objective of the feasibility
study is to test the Technical, Operational and Economical feasibility for adding new
modules and debugging old running systems. All systems are feasible if they are given
unlimited resources and infinite time. There are aspects in the feasibility study portion
of the preliminary investigation:
I. Technical Feasibility
II. Operation Feasibility
III. Economical Feasibility
10. 10
A system can be developed technically and that will be used if
installed must still be a good investment for the organization. In the economical
feasibility, the development costin creating the system is evaluated against the
ultimate benefit derived from the new systems. Financial benefits must equal or
exceed the costs. Thesystem is economically feasible. It does not require any
additional hardware or software.
EconomicalFeasibility
Proposed projects are beneficial only if they can be turned out into
information systems, which will meet the organization’s operations.
requirements. Operational feasibility aspects of the project are to be.
taken as an important part of the project implementation.
Some of the important issues raised are to test the operational feasibility of a project
includes the following: -
Is there sufficient supportfor the management from the users?
Will the system be used and work properly if it is being developed and
implemented?
Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordancewith the above-mentioned issues.
Beforehand, the management issues and user requirements have been taken into
consideration. So, there is no question of resistance from the users that can
undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.
OperationalFeasibility
11. 11
System requirements
Processor: Intel(R) Core i5-8265U CPU @ 1.60GHz 1.80GHz
Operating system: Windows 10 enterprise
Installed memory (RAM): 8.00 GB
Hard disk: 1TB
Keyboard: 101 keys
Mouse: Optical mouse
Hardware and Software requirement
13. 13
Level 1 DFD
Diagnosis Information
Modified Patient Details
Patient Information
Bill Information
List of Patient Details
Patient’s Diagnosis
0.0
Hospital
Management
System
Employee/Doctor
Admin
Patient
Patient Info
Level 0 DFD
Assigned Doctors
List of Patients
Medicine Info
Facilities Information
Medicine Information
Assigned Facilities
Patient’s Diagnosis
Patient’s Diagnosis
Bill Information
Patient’s Diagnosis
Patient’s Information
1.0
Manage Patient
2.0
Assign Room/
Facility
3.0
Assign Medicine
4.0
Manage Employee/
Doctor
Patient Employee/Doctor
Patient’s Information
Employee Info
Patient’s Diagnosis
DFD
14. 14
Level 2 DFD
Assigned Facilities
1.1
Manage
Patient
1.2
Assign Room/
Facilities
1.4
Manage
Doctors
Department
1.3
Assign
Medicine
Patient
Employee/Doctor
Assigned Department
Patient Information
Assigned Medicine
Patient Information
Patient Diagnosis
Bill Information
Patient Diagnosis
Bill Information
Patient Diagnosis
Assigned Medicine
Facilities Information
Patient Diagnosis
Patient Information
Employee Information
Employee Information
Assigned Department
Medicine Information
Patient Diagnosis
Employee
Database
Patient
Database
Medicine
Database
15. 15
Hospital Table:
Field Type Constrains
H_id Int Primary key
H_name Char(30) Not null
H_addr Char(30) Not null
Users table :
Field Type Constrains
user_id Int Primary key
user_name Char (30) Not Null
Password Char (30) Not Null
Registrationtable:
Field Type Constrains
R_id int Primary key
P_id Int Foreign key
P_name Char(30) Not null
Patient table:
Field Type Constrains
P_id Int Primary key
Rm_no Int Foreign key
P_name Char(30) Not null
Admit:
Field Type Constrains
Admt_id Int Primary key
Admt_date Date Not Null
DATA DICTIONARY
16. 16
Discharge:
Field Type Constrains
Dschrg_id Int Primary key
Dschrg_date Date Not null
DoctorTable
Field Type Constrains
D_id Int Primary key
D_name Char (30) Not null
qualification Char (30) Not null
Roomtable:
Field Type Constrains
Rm_no Int Primary key
Rm_type Char(30) Not null
P_id Int Foreign key
Rm_no Int Primary key
Facility table:
Field Type Constrains
F_id Int Primary key
F_name Char(30) Not null
P_id Int Foreign key
Bill table:
Field Type Constrains
B_id Int Primary key
Dschrg_id Int Foreign key
B_amt Int Not null
22. 22
Conclusion
This project has been a rewarding experience in more than one way. The entire
project work has enlightened us in the following areas.
a) We have gained an insight into the working of the HOSPITAL. This
represents a typical real world situation.
b) Our understanding of database design has been strengthened this is because
in order to generate the final reports of databasedesigning has to be properly
followed.
c) Scheduling a project and adhering to that schedule creates a strong sense of
time management.
d) Sense of teamwork has developed and confidence of handling real life
project has increased to a great extent.
e) Initially, there were problem with the validation but with discussions, we
were to implement validations
23. 23
The system has wide scopein the future. All the limitation mentioned above could
be fulfilled which will make it complete commercial system.
In future it can be enhanced with some more features like:
Notifications of user , patient and doctoretc.
Different medicals also also connect with this.
Future Enhancement
24. 24
Sr. No Documentation Content Page No
I Introduction
1 Motivation 4
2 Problem Statement 5
3 Purpose / Objective and Goals 5
4 Literature Survey 6
II System analysis
1 Existing Systems 7
2 Scope and Limitations of Existing Systems 7
3 Project Perspective, Features, Stakeholders 8
4 Requirement Analysis -
Functional requirements,
Performance requirements,
Security requirements etc
9
WEB REFERENCES
1. www.google.com
2. www.youtube.com
3. www.slideshare.com (Reference)
Bibliography
25. 25
III System Design
1 Class Diagram 12
2 Use Case, Activity Diagram, Sequence Diagram,
Deployment Diagram
13
3 User Interfaces 14
IV Implementation details
1
Software / Hardware Specifications
V Outputs and Reports Testing
1 Screenshot and Report