Documente Academic
Documente Profesional
Documente Cultură
SYSTEM
A PROJECT OF DATABASE
PREPARED BY:
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.
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
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
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
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.
PATIENT_TYPE
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
Composite Key:
NORMALIZATION:
“The process of decomposition relations with anomalies to produce
Smaller, well-structured relations.”
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.
PATIENT
P_ID P_NAME P_AGE P_GENDER P_DISEASE
LAB REPORT
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: