Minor Project on Hospital

Management System

Submitted by

Rishikesh Kumar(OA996086708)
Kartik Devji Gami(OA996086486)
Kunal Kumawat(OA996086487)
Karan Kumar(OA996086485)
Ram Bhatt (OA996086705)

Under the supervision and guidance of

DR. Rishi Kumar Sharma

In the partial fulfilment of Bachelor of technology

Submitted to the
DR. Rishi Kumar Sharma

Project Dhanvantari
 Content
1. Acknowledgment
2. Certificate
3. Abstract
4. Definition
i) Entities
ii) Attributes
iii) Keys
a) Primary Key
b) Candidate Key
c) Super Key
d) Foreign Key
e) Alternative Key
f) Composite Key
g) Artificial key

5. Introduction to HMS
6. Problems of HMS
7. Need of HMS
8. List of Entities and Attributes.

9. Diagram
i) Architecture diagram
ii) Use case diagram
iii) ER-diagram
iv) Data model diagram

10.Modules
i) Admin
ii) Doctor
iii) Patient
iv) Staff

11.Data Dictionary and Schema

12. Tables
13. Abbreviation
14.Cardinality and Optionality
15.Conclusion

Project Dhanvantari
 ACKNOWLEDGEMENT

Apart from the efforts of team, the success of any project depends largely on the
encouragement and guidelines of many others. We take this opportunity to express
our gratitude to the people who have been instrumental in the successful
completion of this project. The completion of any inter-disciplinary project
depends upon cooperation, co-ordination and combined efforts of several sources
of knowledge. We are eternally grateful to our teacher DR. Rishi Kumar Sharma
for his even willingness to give us valuable advice and direction under which we
executed this project. His constant guidance and willingness to share his vast
knowledge made us understand this project and its manifestations in great depths
and helped us to complete the assigned tasks.

Rishikesh Kumar(OA996086708)
Kartik Devji Gami(OA996086486)
Kunal Kumawat(OA996086487)
Karan Kumar(OA996086485)
Ram Bhatt(OA996086705)

Project Dhanvantari
 Certificate
This is to certify that computer science engineering project
report entitled “Hospital management system” is the work
carried out by Ram Bhatt, Rishikesh Kumar, Kartik Devji Gami,
Kunal Kumawat , Karan Kumar student of b.tech CSE (Section-
2) Third Semester, Quantum school of the technology, Quantum
University under the supervision of DR. Rishi Kumar Sharma,
Quantum University.

DR. Rishi Kumar Sharma

(Project Mentor)

…………………………..
Signature

Project Dhanvantari
 Abstract

Hospital Management System is an organized computerized system designed and

programmed to deal with day-to-day operations and management of the hospital
activities. The purpose of the project “Hospital Management System” is to
computerize the front office management of hospital to develop software which is
user friendly simple, fast and cost-effective. The main function of the system is
approving the appointment placed by the patients and store their details, doctor
details, and retrieve these details as and when required, also to manipulate these
details meaningfully. Hospital Management System follows a authentication
based system in which only the registered user can access the system. The system
is built so to protect the user data and information.

Project Dhanvantari
# Some Definitions:-

1. Entities:- Entities are distinct and identifiable objects, concepts, or

elements with independent existence. In databases, entities represent real-
world objects, each with associated attributes, often organized in tables.

2. Attributes:- An attribute is a characteristic or property that describes a

feature of an entity in a database. In data modeling, attributes are the
fields or columns that store specific information about the entities.

3. Key:- A key is a field or set of fields in a database that uniquely identifies

a record in a table. Keys are crucial for ensuring data integrity and
facilitating efficient data retrieval in relational database systems.

# Types of keys:-
1. Primary key:- A primary key is a unique identifier for each record in a
database table. It ensures the integrity of the data by ensuring that each
record can be distinctly identified.

2. Candidate Key:- A candidate key is a set of attributes in a database

table that can uniquely identify each record. Unlike a primary key, a
candidate key is a candidate for becoming the primary key.

3. Super Key:- A super key is a set of one or more attributes that, taken
together, can uniquely identify a record in a database table. It can include
more attributes than necessary for uniquely identifying records and may
contain candidate keys.

4. Foreign Key:- A foreign key is a field in a database table that is used to

establish a link between two tables. It typically refers to the primary key
of another table, creating a relationship between the two tables.

5. Alternative key:- An alternative key in a relational database is a

candidate key that is not chosen as the primary key, providing an
additional unique identifier for a table's records. It ensures data integrity
and supports efficient data retrieval.

6. Composite key:- A composite key in a relational database consists of

multiple columns used together to uniquely identify a record within a
table. Unlike a single-column primary key, a composite key involves
a combination of two or more columns.

7. Artificial key :- An artificial key in a database is a surrogate key

introduced solely for the purpose of uniquely identifying records, often
using an auto-incremented or generated value. It is not inherently tied to
the data and helps simplify database management.

Project Dhanvantari
 Introduction to HMS

The project Hospital Management system includes appointment booking,

registration of patients, doctor, and storing their details into the system. The
software has the facility to give a unique id for every patient and stores the details
of every patient and the staff automatically. The project can be entered using a
username and password. Where User can search various services available, Book
appointment, view doctor details and Doctor can view their appointments and
patient detail using their id. It is accessible either by an admin or staff. Only they
can add data into the database. The data can be retrieved easily. The interface is
very user-friendly. Hospital Management System is Powerful, Flexible and easy to
use and is designed and developed to deliver real conceivable benefits to
hospitals, clinics tec.

Project Dhanvantari
Problems Facing due to the lack of hospital Management
system
A hospital management system can lead to several problems and challenges in
healthcare organizations.
Here are some of the common issues:

1. Inefficient Workflow:
Without a management system, tasks such as patient registration, appointment
scheduling, and billing may be manual and time-consuming. This can lead to
inefficiencies in workflow and increase the likelihood of errors.

2. Data Inaccuracy:
Manual record-keeping is prone to errors, and the chances of inaccurate patient
data, prescription details, and medical histories are higher. This can compromise
patient safety and quality of care.

3. Difficulty in Accessing Patient Information:

Retrieving patient records and medical histories becomes challenging when relying
on paper-based systems. This can hinder healthcare providers' ability to make
informed decisions quickly, especially in emergency situations.

4. Limited Communication and Collaboration:

Lack of an integrated system can result in poor communication among
different departments within a hospital. This may lead to delays in patient
care and treatment, as well as miscommunication regarding appointments
and procedures.

5. Security Risks:
Paper records are more susceptible to loss, damage, or unauthorized access.
A digital hospital management system with proper security measures helps
in safeguarding patient information and ensures compliance with privacy
regulations.

6. Billing and Financial Challenges:

Manual billing processes can be error-prone and time-consuming. A management
system streamlines the billing process, reducing the chances of mistakes and
ensuring timely and accurate financial transactions.

Project Dhanvantari
# Need of the Hospital Management System

A Hospital Management System (HMS) is a comprehensive software solution that

facilitates the efficient management of various aspects of a hospital or healthcare
facility. The need for a Hospital Management System arises from the complexities
and challenges associated with managing healthcare institutions.
Here are some key reasons for the need of an HMS:

1. Streamlining Administrative Tasks:

Patient Registration: HMS helps in easy and accurate patient registration,
maintaining their records, and retrieving information when needed.

Appointment Scheduling: It streamlines the process of scheduling and

managing appointments for patients, doctors, and other resources.

2. Efficient Billing and Financial Management:

Billing and Invoicing: HMS automates the billing process, ensuring accurate
and timely invoicing for services provided.

Insurance Management: It helps in managing patient insurance information,

claims, and settlements, reducing the chances of errors.

3. Patient Management:
Electronic Health Records (EHR): HMS maintains electronic health
records, ensuring easy access to patient data, medical history, and treatment plans.

Prescription and Medication Management: It assists in managing

prescriptions, tracking medication administration, and reducing the likelihood of
errors.

4. Inventory Management:
Medicine and Equipment Inventory: HMS helps in managing and
monitoring the inventory of medicines and medical equipment, preventing
shortages or excesses.

Project Dhanvantari
5. Appointment and Resource Optimization:
Doctor and Staff Scheduling: It optimizes the scheduling of doctors and
staff, ensuring efficient utilization of resources.

Facility Management: HMS helps in managing the overall infrastructure of

the hospital, including rooms, equipment, and other resources.

6. Data Security and Compliance:

Data Security: With sensitive patient information at stake, HMS ensures data
security and compliance with healthcare regulations.

Regulatory Compliance: It helps in adhering to healthcare regulations and

standards, avoiding legal issues.

# List of Entities and Attributes:-

Entities Attributes

Doctor Doctor_Id (Primary Key)

Doctor_Name
Experience
Shift
Gender
Contact Details
Specialization
Staff Staff_Id (Primary
Key) Name
Position
Salary
Contact Details
Patient Patient_Id (Priamry Key)
Patient_Name
Gender
Contact Details
Medical History

Project Dhanvantari
Department Department_Id
Department_Name

Billing Bill_Id
Patient_Id
Total_Cost
Appointment Appointment_Id
Patient_id
Doctor_Id
Date
Time
Status
Ward/Room Ward Name
Room_Id
Bed Number
Capacity

Project Dhanvantari
# Diagram

i) ARCHITECTURE DIAGRAM
An architectural diagram is a diagram of a system that is used to abstract
the overall outline of the software system and the relationships,
constraints, and boundaries between components. It is an important tool
as it provides an overall view of the physical deployment of the software
system and its evolution roadmap.

Staff
User

Result Result Result

Login/Register Hospital Management Booking
System Approval/Cancel

Admin Doctor Details

Data

Fig:- Architectural Diagram

Project Dhanvantari
 ii) Use Case Diagram

A use case diagram in the Unified Modelling Language (UML) is a type

of behavioural diagram defined by and created from a use-case analysis.
Its purpose is to present a graphical overview of the functionality
provided by a system in terms of actors, their goals (represented as use
cases), and any dependencies between those use cases.

Signup

Login

Add Doctor

Admin Add Staff Patient

Approve Appointment

Make Appointment

Payment/Bill

View Patient Details

View Doctor Details

Send Feedback

View Feedback

Staff Doctor
Logout

Fig:- Use Case Diagram

Project Dhanvantari
iii) ER- Diagram

Project Dhanvantari
iv) Data Model Diagram

a) Logical Model

b) Relational Model

Project Dhanvantari
#) Modules
 In this system we have four modules they are
given below:-

a) Admin
b) Patient
c) Doctor
d) Staff

a) Admin:-
Admin has the full access to the system which means he is able to manage
any activity with regard to the system. He is the highest privileged user who
can access to the system.

# Key function of the admin are given below:-

i. Add doctor:- The Admin have authority to add the new doctor and
remove the doctor.

ii. Add Staff:- The Admin have authority to add the new staff and
remove the existing staff.

b) Patient:-
Patients can choose the best preferred appointments from the options
provided and can also change the appointment schedule or cancel it. After
appt. is confirmed by the respective doctor they can pay their consultant fee
online. Patients have access to only their records.

#) Key function of the patient are given below:-

i. Make appointment
ii. Cancel appointment
iii. Update details
iv. Payment

c) Doctor:-
Doctors can view the patient details and add prescription to the patient.
Doctors have access to only records of those patients whom they are treating.

#) Key function of the doctor are given below:-

i. View patient details

ii. Add Prescription.

Project Dhanvantari
 d) Staff:-
Staff can view the patient appointment list and provide the confirmation or
make changes in the appointment list if required.

#) key function of the staff are the given below:-

i. Approve appointment
ii. Cancel appointment
iii. Modification the appointment

#) Data Dictionary and Schema

1. Admin

Attribute Name Data type Constraints Description

Log In ID INT Not Null (PK) Unique id for each login process

User id Int Not Null (FK) User id of the person

Password Varchar(50) Not Null Password for the verification and security

2. Staff

Attribute Data type Constraints Description

Staff ID Int Not NULL (PK) Unique for the each staff

User name Varchar(255) Not NULL Name of the staff

Address Varchar(255) Not Null Address of the staff

Position Varchar(255) Not Null Position of the staff

Contact number Int Not Null Contact number of the staff

password Varchar(50) Not Null Password for the verification and security

Project Dhanvantari
 3. Patient
Attribute Data type Constraints Description

P ID Int Not NULL (PK) Unique for the each patient

User name Varchar(255) Not NULL Name of the patient

Address Varchar(255) Not Null Address of the patient

Medical history Char Not Null Medical history of the patient

Contact number Int Not Null Contact number of the patient

password Varchar(50) Not Null Password for the verification and security

4. Doctor

Attribute Data type Constraints Description

D ID Int Not NULL ( PK) Unique for the each doctor

User name Varchar(255) Not NULL Name of the doctor

Address Varchar(255) Not Null Address of the doctor

Specialist Varchar(255) Not Null Specialization of the doctor

Contact number Int Not Null Contact number of the doctor

password Varchar(50) Not Null Password for the verification and security

5. Department

Attribute Data type Constraint Description

Dep id Int Not Null (PK) Unique for each department

D id Int Not Null (FK) Id of the doctor

Dep name Varchar Not Null Name of the department

Project Dhanvantari
 6. Appointment

Attribute Data type Constraints Description

APP ID Int Not NULL (PK) Unique for the each patient

User name Varchar(255) Not NULL Name of the patient

Address Varchar(255) Not Null Address of the patient

Appointment date and time int Not Null Appointment date and time of the patient

Contact number Int Not Null Contact number of the patient

7. Payment

Attribute Data type Constraints Description

Bill ID Int Not NULL (PK) Unique for the each bill generated

P id Int Not Null (FK) Patient id

User name Varchar(255) Not NULL Name of the patient

Address Varchar(255) Not Null Address of the patient

Total cost int Not Null Total amount of money to pay

Contact number Int Not NUll Contact number of the patient

8. Prescription

Attribute Data type Constraints Description

D ID Int Not Null Doctor Id

P ID Int Not Null (FK) Patient Id

Medicine Varchar Not Null Name of medicine

Advice Char Not Null Advice given to patient
Remark Varchar Not Null Remarks

Project Dhanvantari
#) Some of the data stored in the database is given below:-

i. Table to add the doctor

Doctor Doctor Specialist Address Contact No Status

Id Name
10001 Dr. Govind Internal medicine Daijee 9812705820 Approve Reject

10002 Dr. Narayan General Surgery Baitadi 6397552081 Approve Reject

10003 Dr. Vasudev Family medicine Nepal 9810601495 Approve Reject

10004 Dr. Gopal Radiology Kanchanpur 9867700810 Approve Reject

ii. Table for the doctor list

Doctor Id Doctor Name Specialist Address Contact No

10001 Dr. Govind Internal medicine Daijee 9812705820

10002 Dr. Narayan General Surgery Baitadi 6397552081

10004 Dr. Gopal Radiology Kanchanpur 9867700810

iii. Table for the staff list

Staff Id Staff Name Address Contact No Position

20001 Shiv Mahendranagar 9840742823 Receptionist

20002 Mahadev Bhamka 9863470771 Ward boy

20003 Bholenath Jhalari 9868581081 Pharmacist

20004 Kali Rameshor 9804684143 Nurse

Project Dhanvantari
 iv. Table for the appointment list of the patient

App ID Name Appointment Date Appointment Time Description Doctor Name

30001 Shyam 2022/10/28 5:02 Heart Checkup DR. Govind

30002 Hari 2022/12/17 12:37 Brain Checkup DR. Vasudev

30003 Geeta 2023/02/28 4:20 Mouth Checkup DR. Gopal

30004 Bhumi 2023/03/18 1:42 Body checkup DR. Narayan

v) Table for the admitted patient

P Id Patient Name Gender Age Contact No Address Admission Date

40001 Madhav Male 43 9810601494 Dwarka 2022/10/28

40002 Devi Female 23 9867700809 Bihar 2022/12/17

40003 Keshav Male 64 9812705819 Gokul 2023/02/28

40004 Parth Male 25 6397552080 Banbas 2023/03/18

#) Abbreviation

Short form Full form

HMS Hospital Management System

D Id Doctor ID

P Id Patient ID

S Id Staff ID

App Id Appointment ID

D Name Doctor Name

P Name Patient Name

S Name Staff Name

App Date Appointment Date

App Time Appointment Time

PK Primary Key

FK Foreign Key

Project Dhanvantari
#) Relationship among Entities.
(Cardinality & Optionality)
i. Cardinality:
Cardinality in DBMS is to represent relationship between two tables and
represent how many times an entity appear in relation to other.
1. One-To-One:
Each instance relates to one instance of other entity
2. One-To-Many:
Each instance relates to many instances of other entity.
3. Many-To-One:
Multiple instances of one entity relates to one instance of other
entity.
4. Many-To-Many:
Multiple instances of one entity relates to multiple of other.

ii. Optionality:
Optionality defines if the relation between two entities is mandatory
or optional.
1. Mandatory
Each instance must be related to another one
2. Optional:
Every instance in one entity doesn’t need one in other entity.

Project Dhanvantari
#) Conclusion
 To summarize, the Hospital Management System serves as a thorough
solution that has effectively tackled the complex challenges in healthcare
administration. Through careful design and strong functionality, the system
has proven its ability to optimize and streamline various aspects of hospital
operations. The smooth integration of modules, such as managing patient
information, scheduling appointments, handling billing, greatly improved
operational efficiency.

Real-time access to patient data, analytics, and reporting features has

empowered healthcare providers and administrators with valuable insights,
enabling them to make more informed decisions. Furthermore, the system's
focus on user-friendly interfaces ensures that healthcare professionals can
easily navigate and utilize its features, ultimately resulting in enhanced
patient care. The automated processes, including appointment scheduling
and billing have minimized manual errors and simplified workflows,
leading to a more reliable and error-free healthcare environment. As we
contemplate the impact of the Hospital Management System, it becomes
clear that it not only addresses immediate operational needs but also
establishes the groundwork for a more responsive and adaptable healthcare
system.

Essentially, the successful implementation of the Hospital Management

System signifies a significant milestone in the ongoing evolution of
healthcare administration, showcasing a dedication to excellence, efficiency,
and, most importantly, the well-being of patients.

Hence, Hospital Management System is one of the basic need of the patient
and doctor in this modern era to perform their tasks efficiently.

Project Dhanvantari