HOSPITAL MANAGEMENT
SYSTEM
A PROJECT OF DATABASE
PREPARED BY:
ZAINAB AYAZ AND MISBAH IRSHAD
ROLL NO: 5666 , 5676
HOSPITAL MANAGEMENT SYSTEM
INTRODUCTION
PLANNING:
“A project plan, according to the project management body of
knowledge is a formal approved document used to guide both
project execution and project control.”
Background: Hospitals are the essential part of our lives,
providing best medical facilities to people suffering from various
ailments, which may be due to change in climatic conditions,
increased workload, emotional trauma stress etc. It is necessary
for the hospitals to keep the track of its day to day activities &
records of its patients, doctors, and nurses that keep the hospital
running smoothly and successfully.
But keeping the track of all the activities and the records on paper
is very cumbersome and error prone. It also is very inefficient and
a time consuming process. Observing the continuous increase in
population and a number of people visiting the hospital.
Recording and maintain all these records is highly reliable,
inefficient and error-prone. It is also not economically and
technically feasible to maintain these records on paper.
Thus keeping the working of the manual system as the basis of
our project. We have developed an automated version of the
manual system, named as “HOSPITAL MANAGEMENT
SYSTEM”.
Goal Of Project:
The main aim of our project is to provide a paperless hospital up to
90%. It also aims at providing low-cost reliable automation of the
existing systems. The system also provides excellent security of data at
every level of user system interaction and also provides robust and
reliable storage and backup facilities. The main aim of this HMS is to
maintain data and provide facility to access it easily.
SCOPE:
The proposed database product is the HOSPITAL MANAGEMENT
SYSTEM. The system will be used in any hospital, clinic, or pathology
labs to get the information from the patients and then storing that
data for future usage.
The current system in use is a paper based system. It is too slow and
cannot provide updated lists of patients with in a reasonable time –
frame. The intentions of the system are to reduce overtime pay and
increase the number of patients that can be treated accurately.
ANALYSIS:
“The Analysis Phase is also the part of the project where you identify
the overall direction that the project will take through the creation of
the project strategy documents. Gathering requirements is the main
attraction of the Analysis Phase.”
REQUIREMENT ANALYSIS:
In system engineering and software engineering, requirements analysis
encompasses those tasks that go into determining the needs or
conditions to meet for a new or altered product or project, taking
account of the possibly conflicting requirements of the various
stakeholders, analyzing, documenting, validating and managing
software or system requirements.
DISADVANTAGES OF MANUAL SYSTEM:
A manual system is a bookkeeping system where records are
maintained by hand, without using a computer system. Instead,
transactions are written in journals, from which the information is
manually rolled up into a set of financial statements.
There are some disadvantages in keeping records in the manual system
which are given below:
It is difficult to manage
Limited data sharing
Lengthy development time
Duplication of data may be possible
Data inconsistency
Insecurity of data
DATA BASE:
A database-management system (DBMS) is a computer-software
application that interacts with end-users, other applications, and
the database itself to capture and analyze data.
Database has replaced the manual system due to its efficient
performance its advantages are as under:
ADVANTAGES OF DATABASE APPROACH:
Remove data redundancy
Improved data consistency
Improved data sharing
Increased productivity of application development
Enforcement of standards
Improved data quality
Induced program maintenance
PROJECT OVERVIEW:
The Hospital Management System is designed for any hospital to
replace their manual, paper based system. The new system is to
control the following information;
Patient information
Room availability
Staff information
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.
SYSTEM SPECIFICATION:
HARDWARE REQUIREMANTS:
Core i3 (Processor)
4 GB Ram
512 KB Cache Memory
Hard disk 400 GB
Microsoft Compatible 101 or more Key Board
SOFTWARE REQUIREMENT:
Operating System: Windows 7
Front End: C#
Back End: Microsoft SQL Server
Documentation Tools: Microsoft Word 2010
SYSTEM DESIGN:
ERD :
The Entity-Relationship Model (ERD) is a way of graphically representing
the logical relationships of entities in order to create a database
ENTITY:
An entity is a thing, person, place, unit, object or any item about
which the data should be captured and stored in the form of
properties, workflow and tables .FOR EXAMPLE PATIENT and DOCTOR
Etc. It is represented by a rectangle.
ENTITY
ATTRIBUTES:
An attribute describes the facts, details or characteristics of an
entity. FOR EXAMPLE PATIENT_NAME, DOC_NAME etc. .It is
represented by oval.
Attribute
RELATIONSHIP:
A relationship, in the context of database, is a situation that exists
between two relational database tables when one table has a
foreign that references the primary key of the other table.
Relationship allow relational database to split and store data in
different tables, while linking disparate data items. It is
represented in diamond shape symbol.
Relationshi
p
ERD-MODEL
P-ID
D-ID
P-WT
P-GENDER D-
NAME
PATIENTS CONS DOCTOR
-ULTS
C
P_NA H
AGE EC
ME DEPT SALARY
KS
P-DISEASE
AMOUNT
PAYS LAB_NO
LAB REPORT
ADVANCE CATEGORY
OPRTN_CHRG
DATE
S
N-O-
D BILL
MED_CHRGE
S
P_TYPE
BILL_NO
P_ID
TOTAL_BIL ROOMCHRG
L S
ENTITIES AND ATTRIBUTES OF HOSPITAL MANAGEMENT
SYSTEM:
DOCTOR:
Doc_ID
Doc_NAME
Doc-PHONENO
DOC_SPECIALIZATION
Doc_DEPT
Doc_phone#
PATIENTS:
PATIENT_ID
PATIENT_NAME
PATIENT_AGE
P_GENDER
P_DISEASE
LAB REPORT:
LAB_NO
PATIENT_ID
DOCTOR_ID
AMOUNT
CATEGORY
DATE
ROOM:
ROOM_NO
ROOM_TYPE
STATUS
BILL:
BILL_NO
PATIENT_ID
PATIENT_TYPE
LAB_CHARGES
MEDICINES_CHARGES
ADVANCE
OPERATION_CHARGES
ROOM_CHARGES
NO_OF_DAYS
ENHANCED ERD MODEL:
“ A model that has resulted from extending the original ER Model
with new modeling constructs.” D-
SALARY D-ID
P-GENDER NAME
DEPT
PATIENTS CONSULTS DOCTOR
CHE
CKS
P- AGE
NAME P-WT
P-ID PERMANENT HOUSE_JOB
P-DISEASE AMOUN
T
MED_CHRGE LAB REPORT
LAB_NO
S
ADVANCE
OPRTN_CHRG
CATEGORY DATE
S
BILL ISSUE DECI
N-O- D
PATIENT_TYPE
DES
D
TO
P_TYPE
BILL_NO
P_ID
IN_PATIENT OUT_PATIENT
TOTAL_BIL ROOMCHRG
L S D_O_C DATE_ADMIT
SUBTYPE AND SUPERTYPE:
A supertype is a generic entity type that has a relationship with one or
more subtypes. A subgrouping of the entities in an entity type that is
meaningful to the organization and that shares common attributes or
relationships distinct from other subgroupings.
The Subtype and Supertype Entities of HOSPITAL MANAGEMENT
SYSTEM are
PATIENT
DOCTOR
PATIENT_ID
DOC_ID
PATIENT_NAME
DOC_NAME
PATIENT_AGE
DOC_SPECIALIZATION
P_GENDER
DOC_TYPE
P_DISEASE
PATIENT_TYPE
PERMANEN HOUSE JOB
AT
INPATIENT OUTPATIENT
LOGICAL DATABASE DESIGN AND RELATIONAL MODEL:
RELATIONAL DATA MODEL:
“The relational data model represents data in the form of tables.”
BASIC DEFINITIONS:
Data structure:
“Data are organized in the form of tables, with rows and columns.”
Data manipulation:
“Powerful operations (using the SQL language) are used to
Manipulate data stored in the relations.”
Data integrity:
“The model includes mechanisms to specify business rules that
maintain the integrity of data when they are manipulated.”
DOCTOR
DOC_ID Doc_name Doc_no Doc_dept Doc_Specialization
D1 Zainab Ayaz 45678 Kidney_care Urology
D2 Marosha Khan 56789 Child_Specialist Padriatic
RELATIONAL DATA STRUCTURE:
“A named two-dimensional table of data.”
PATIENT (P_ID, P_name, P_age, P_gender, P_disease, Doc_ID)
PRIMARY KEY:
“An attribute or a combination of attributes that uniquely identifies each row
in a relation.”
PATIENT (P_ID, P_name, P_age, P_gender, P_disease, Doc_ID)
Composite Key:
“A Primary Key that consists of more than one another.”
PATIENT (P_ID, P_name, P_age, P_gender, P_disease, Doc_ID)
DOCTOR (Doc_ID, Doc_name, Doc_no, Doc_dept, Doc_Specialization)
NORMALIZATION:
“The process of decomposition relations with anomalies to produce
Smaller, well-structured relations.”
MAIN GOAL OF NORMALIZATION:
Minimize data redundancy, thereby avoiding anomalies and
conserving storage space
Simplify the enforcement of referential integrity constraints
Make it easier to maintain data (insert, delete and update)
Provide a better design
NORMAL FORM:
A state of a relation that requires that certain rules regarding relationships
between attributes (or functional dependencies) are satisfied.
STEPS IN NORMALIZATION:
FIRST NORMAL FORM:
Any multi-valued attributes have been removed, so there is a single
value (possible null) at the intersection of each row and column of the table.
SECOND NORMAL FORM:
Any partial functional dependencies have been removed (i-e, non-key
attributes are identify by the whole primary key).
THIRD NORMAL FORM:
Any transitive dependencies have been removed (i-e, non-key
attributes are identify by the whole primary key).
BOYCE-CODD NORMAL FORM:
Any remaining anomalies that result from functional dependencies have
been removed (because there was more than one possible primary key
for the same non-key.
FOURTH NORMAL FORM:
Any multi-valued dependencies have been removed.
FIFTH NORMAL FORM:
Any remaining anomalies have been removed.
Normalized relation of our database as:
DOCTOR
DOC_ID DOC_NAME DOC_PNO DOC_SPECIALIZATION DOC_DEPT
PATIENT
P_ID P_NAME P_AGE P_GENDER P_DISEASE
LAB REPORT
LAB_NO P_ID DOC_ID AMOUNT CATEGORY DATE
BILL
BILL_NO P_ID P_TYPE LAB_CHARGES ADVANCE OPER_CHARGES ROM_Char days T_bill
PHYSICAL DESIGN OR IMPLENTATION OF OUR
DATABASE:
LOGIN PAGE:
MAIN FORM:
HOSPITAL:
DOCTOR:
PATIENT:
LAB:
ROOM:
