hospitalmanagementsystem-220914162441-4dac2fe7

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 25

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

1
KarmaveerKakasahebWagh Education Society’s
K. K. Wagh Arts Commerce, Science,
&ComputerScienceCollege Saraswati Nagar Nashik-422003

CERTIFICATE
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

2
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 support and 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.

3
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

Problem Definition
4
 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.)

5
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 throughout the hospital management infrastructure.
Often information(on forms) is incomplete
or does not follow management standards forms are often lost in transit between
lost. Multiple copies of the same information exist in the hospital and may lead to
inconsistences in data in various data stores.

Proposed System

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 room schedules,
and patient invoices. These services are to be provided in an efficient, cost
effective manner with the goal of reducing the time and resources currently
required for such tasks.

6
Requirement Analysis
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.

Scope of the System


7
This system product is 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
Feasibility Study
8
–––

Technical Feasibility

 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 proposed equipments have the technical capacity to hold the data
required to use the new system?
 Will The proposed system provide adequate response to 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?

Operational Feasibility

9
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.
Economical Feasibility

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 cost in creating the system is evaluated against the
ultimate benefit derived from the new systems. Financial benefits must equal or
exceed the costs. The system is economically feasible. It does not require any
additional hardware or software.

System requirements

Hardware and Software requirement

 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

10
ER Diagram
H_addr
#H_id H_name

Hospital

Has
#user_id
Password

user_name
User
P_name P_id
D_name
#R_id
Maintain
Doctor Registration
Record

#D_id
qualification
P_name

Patient Done

#P_id 11
Rm_no F_name
Is a
#F_id
DFD

Level 0 DFD

Modified Patient Details

Patient Information Diagnosis Information

Admin 0.0
Hospital Patient Info Patient
Management
Employee/Doctor
System

Patient’s Diagnosis Bill Information


List of Patient Details

Level 1 DFD
Patient’s Information Patient’s Information
1.0
Patient’s Diagnosis Patient’s Diagnosis
Manage Patient
Bill Information

Facilities Information

2.0
12
Patient’s Diagnosis Assign Room/
Facility
Level 2 DFD

Patient Information 1.1 Patient Information


Patient Diagnosis Patient Diagnosis
Manage
Patient
Bill Information
Patient
Database
Facilities Information

Patient Diagnosis 1.2

Patient Information Assign Room/


Bill Information Facilities Employee/Doctor

Patient Diagnosis
Employee Information
Patient Assigned Facilities Assigned Department

Assigned Medicine Patient Diagnosis


Employee
Medicine Database
Database 1.4
1.3
Manage Employee Information
Assign
Assigned Medicine Doctors
Medicine
Department

Assigned Department
13
Medicine Information
DATA DICTIONARY

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

Registration table:
Field Type Constrains
R_id int Primary key
P_id Int Foreign key
14
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

Discharge:
Field Type Constrains
Dschrg_id Int Primary key
Dschrg_date Date Not null

Doctor Table
Field Type Constrains
D_id Int Primary key
D_name Char (30) Not null
qualification Char (30) Not null

Room table:
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
15
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

Output Screen

Users Login screen

Welcome screen
16
Room screen

17
Patient screen

Doctor screen

Bills screen

18
Service Screen

19
Admit Patients Screen

Discharge Patients Screen

20
21
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 database designing 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

22
Future Enhancement

The system has wide scope in 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 doctor etc.

 Different medicals also also connect with this.

23
Bibliography

WEB REFERENCES

1. www.google.com
2. www.youtube.com
3. www.slideshare.com (Reference)

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 - 9
Functional requirements,
Performance requirements,
Security requirements etc
III System Design
1 Class Diagram 12

24
2 Use Case, Activity Diagram, Sequence Diagram, 13
Deployment Diagram
3 User Interfaces 14
IV Implementation details

1
Software / Hardware Specifications
V Outputs and Reports Testing
1 Screenshot and Report

25

You might also like