Hospital Database Management System
Abstract-My project Hospital Database Management
system includes registration of patients, storing their
disease details into the system. It will also contain
doctor’s information and will digitalize the whole billing
system. It has the facility to give a unique id for every
patient and stores the details of every patient and staff
automatically. It includes a search facility to know the
current status of each room. User can search
availability of a doctor and the details of a patient using
the id. And the whole process conducted by
Administrator.
Keywords- Hospital, Administrator, Patients, Doctor,
Diseases, Staff, Treatments, Test, Lab reports, Schema.
1. BACKGROUND
A Hospital Database Management System (HDMS) is a
computer or web based system that facilities managing the
functioning of a hospital or any medical set up. This system
will help in making the whole functioning paperless.
The hospital database includes all the necessary patient
data. The disease history, test results, prescribed
treatment can be accessed by doctors without much delay
in order to make an accurate diagnosis and monitor the
patient's health. It enables lower risks of mistakes.
A hospital is a place where Patients come up for general
diseases. Hospitals Provide facilities like:
• Consultation by Doctors on Diseases.
• Diagnosis for diseases.
• Providing treatment facility.
• Facility for admitting Patients (providing beds,
nursing, medicines etc.)
• Immunization for Patients/Children.
Various operational works that are done in a Hospital are:
• Recording information about the Patients that
come.
• Generating bills.
• Recording information related to diagnosis given
to Patients.
• Keeping record of the Immunization provided to
Children/Patients.
• 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:
• Information about Patients is done by just writing
the Patients name, age, and gender. Whenever the
Patient comes up his information is stored freshly.
• Bills are generated by recording price for each
facility provided to Patient on a separate sheet and
at last they all are summed up.
• Diagnosis information to patients is generally
recorded on the document, which contains Patients
information. It is destroyed after some time period
to decrease the paper load in the office.
• Immunization records of the children are
maintained in pre-formatted sheets, which are kept
in a file.
• Information about various diseases is not kept as
any document. Doctors themselves do this job by
remembering various medicines
All this work is done manually by the receptionist and
other operational staff and lot of papers are needed to
be handled and taken care of. Doctors have to
remember various medicines available for diagnosis
and sometimes miss better alternatives as they can’t
remember them at that time.
2. IDEAS
The hospital database includes all the necessary patient
data. The disease history, lab reports, prescribed
treatment can be accessed by doctors without much delay
in order to make an accurate diagnosis and monitor the
patient's health. It enables lower risks of mistakes.
 The project maintains two levels of users:
• Administrator.
• User Level-Data Entry Operator.
 Now, I discuss the main facilities in this project are:
• Maintaining records of indoor/outdoor patients.
• Maintaining patient’s test and examinations details.
• Providing different test facilities to a Doctor for
doctor for diagnosis of a patients.
• Maintaining patient’s prescription, medicine and
diet advice details.
• Providing billing details for indoor/outdoor
patients.
• Results of tests, prescription, precautions and diet
advice will be automatically updated in the
database.
• In this project collection of data in form different
pathology labs.
• Related test reports, patient’s details report, billing
reports can be generated as per user requirements.
 • User or administrator can search a patient’s record  ER Diagram of Hospital Database Management System
by his id.
• Hospital Database Management System Design:
The Hospital database management system design is a
database design use for managing hospital functions
and events. It enables the admin to register a patient
for the hospital, stores their disease details into the
database. Any of the staff members, doctor & admin is
able to add, view, edit, update or delete data.
 Purpose of Hospital Database Management System:
The purpose of the Hospital Management
System database Design is to make a secure and easy
way of storing information of the patient, doctors,
inpatient, outpatient, Rooms, and Bill payment.
 Features of the Hospital Database Management
System: There are seven (8) common features of
Hospital Management System Database Design such
as
Managing Administrator, Doctors, laboratory,
Inpatient, Outpatient, Rooms, and Hospital Bills
information.
• Administrator
This table of ER Diagram Hospital Management System
will be used for storing and managing the administrator
information. Administrator manage & maintain the whole
system.
• Manage Doctor
This table will be used for storing and managing the
Doctor information and login account.
• Manage Laboratory The proposed ER diagram for Hospital DBMS with
This table will be used for storing and managing the relationship shows the entity of the proposed Hospital
Laboratory transaction. Management system database, which is presented by
• Manage Inpatient tables; the tables are made to meet the required
This table will be used for storing and managing specification of the system and provide much more specific
the inpatient information and diagnosis. details of each entity within the system.
• Manage Outpatient Data Tables:
This table will be used for storing and managing 1. Administrator Table:
the inpatient information and diagnosis. Fields Data Type Relationships
• Manage Room
a_id int(5) Primary Key
This table will be used for storing and managing
a_name Varchar(20) Not Null
the room information and assigning of patient in
every room. gender Varchar(10) Not Null
• Manage Bills
The billing table will be used for managing the 2. Doctor Table:
statement of accounts per patient and for the
Fields Data Type Relationships
collection of bills.
• Manage Staff Doctor_id int(5) Primary Key
This table will be used for storing and managing Doctor_name Varchar(15) Not Null
the Staff information. Dept Varchar(15) Not Null
a_id Int(5) Foreign Key
3. Staff Table: 8. Bill Table:
Fields Data Type Relationships
Fields Data Type Relationships
s_name Varchar(15) Not Null
s_id Int(5) Primary Key bill_no int(50) Primary Key

NID Int(12) Not Null Patient_id int(5) Foreign Key

salary Int(5) Not Null patient_type Varchar(10) Allow Null
a_id Int(5) Foreign Key doctor_charge int Not Null
medicine_charge int Not Null
4. Lab table: room_charge int Not Null
Fields Data Type Relationships operation_charge int Allow Null
lab_no int(5) Primary Key number_of_days int Allow Null
Patient_id int(5) Not Null nursing_charge int Allow Null
weight int Not Null advance int Allow Null
Doctor_id int(5) Foreign Key health_card Varchar(50) Allow Null
date Date/Time[6] Not Null lab_charge int Allow Null
category Varchar(15) Not Null bill int Not Null

patient_type Varchar(15) Not Null

amount Int(10) Not Null Snapshot:
• Hospital DBMS Tables list in SQL
5. Inpatient Table: Database Server
Fields Data Type Relationships
Patient_id int(5) Primary Key
name Varchar(20) Not Null
gender Varchar(10) Not Null
address Varchar(20) Not Null
room_no int(5) Not Null
date_of_admit Date/Time[ 6] Not Null
date_of_discharge Date/Time[6 ] Not Null
advance Int(10) Not Null
lab_no int(5) Foreign Key • Hospital DBMS SQL Server Database Schema
Doctor_id Int(5) Foreign Key Diagram

disease Varchar(20) Not Null

6. Outpatient Table:
Fields Data Type Relationships
Patient_id int(5) Primary Key
date Date/Time Not Null
lab_no int(5) Foreign Key

7. Room Table:

Fields Data Type Relationships

room_no Int(5) Primary Key
Insert data into all Tables:
room_type Varchar(10) Not Null Now, we can use insert statement for Insert (add) data or
status Varchar(10) Not Null record into tables.
Patient_id Int(5) Foreign Key • For Administrator table:
The statement below enters 2 records or rows into
patient table:
 Table: Table:

• For bill Table:

The statement below enters 2 records or rows into
• For doctor table: bill table:
The statement below enters 2 records or rows into
doctor table:
Table:

• For staff Table:

Table: The statement below enters 2 records or rows into
staff table:

Table:
• For lab Table:
The statement below enters 2 records or rows into
lab table:

Note: We will store this kind of record or information by

Table: using above process.

 Search a patient’s record by his id:

To see patient’s record, we will use select
• For inpatient table: statement.
The statement below enters 2 records or rows into I would like to see how much bill, doctor
inpatient table: charge, medicine charge, room charge, operation
charge, nursing charge are came and how much
advance given the first patient's

Table:

• For outpatient table:

The statement below enters 2 records or rows into
outpatient table:

3. Conclusion
The project Hospital Data Management System (MDBS)
Table: is for computerizing the working in a hospital. It takes care
of all the requirements of an average hospital and is
capable to provide easy and effective storage of
information related to patients that come up to the hospital.
It generates test reports, provide medicines prescribed to
• For room table: patient and doctor. It also provides billing facility on the
The statement below enters 2 records or rows into basis of patient’s status whether it is an indoor or outdoor
room table: patient. The system also provide the facility of backup as
per the requirement.
create database HMS1
use HMS1
CREATE TABLE department(
[department_id] [int] NOT NULL PRIMARY KEY,
[dep_name] [varchar](max) NOT NULL,
[dep_head] [varchar](max) NOT NULL,
);
CREATE TABLE employee(
[employee_id] [int] NOT NULL PRIMARY KEY,
[employee_name] [varchar](max) NOT NULL,
[DoB] [date] NOT NULL,
[joinning_date] [date] NOT NULL,
[emp_type] [varchar](max) NOT NULL,
[email] [varchar](max) NOT NULL,
[address] [varchar](max) NOT NULL,
[salary] [int] NOT NULL,
[date_of_leaveing] [date] NOT NULL,
[department_id] [int] NOT NULL foreign key
references [department]);
CREATE TABLE Medicine(
[medicine_id] [int] NOT NULL PRIMARY KEY,
[medicine_name] [varchar](max) NOT NULL,
[quantity] [int] NOT NULL,
[date] [date] NOT NULL,
[medicine_cost] [nchar](10) NOT NULL,
CREATE TABLE patient(
[patient_id] [int] NOT NULL PRIMARY KEY,
[patient_name] [varchar](max) NOT NULL,
[phone_no] [varchar](max) NOT NULL,
[blood_group] [varchar](max) NOT NULL,
[email] [varchar](max) NOT NULL,
[gender] [varchar](max) NOT NULL,
[address] [varchar](max) NOT NULL,
[disease] [varchar](max) NOT NULL,
[arrival_date] [date] NOT NULL,
[discharge_date] [date] NOT NULL,
);
create table Bill
( [payment_id] [int] NOT NULL PRIMARY KEY,
[date] [date] NOT NULL,
[room_cost] [int] NOT NULL,
[othercharge] [int] NULL,
[mcost] [int] NOT NULL,
[Total] [int] NOT NULL,
[patient_id] [int] NOT NULL foreign key references
[patient]);
CREATE TABLE doctor(
[doctor_id] [int] NOT NULL PRIMARY KEY,
[qualification] [varchar](max) NOT NULL,
[patient_id] [int] NOT NULL foreign key references
[patient],
[employee_id] [int] NOT NULL foreign key
references [employee]);
CREATE TABLE nurse(
[nurse_id] [int] NOT NULL PRIMARY KEY,
[patient_id] [int] NOT NULL foreign key references
[patient],
[employee_id] [int] NOT NULL foreign key
references [employee]);
CREATE TABLE reletive(
[reletive_id] [int] NOT NULL PRIMARY KEY,
[reletive_name] [varchar](max) NOT NULL,
[reletive_contact] [varchar](max) NOT NULL,
[relation] [varchar](max) NOT NULL,
[patient_id] [int] NOT NULL foreign key references
[patient]);
CREATE TABLE room(
[room_id] [int] NOT NULL PRIMARY KEY,
[room_type] [varchar](max) NOT NULL,
[patient_id] [int] NOT NULL foreign key references
[patient],
[room_cost] [int] NOT NULL);
CREATE TABLE Test([test_id] [int] NOT NULL
PRIMARY KEY, [test_name] [varchar](max) NOT
NULL, [test_cost] [int] NOT NULL, [date] [date]
NOT NULL, [patient_id] [int] NOT NULL foreign
key references [patient]);

Conclusions

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.