HOSPITAL MANAGEMENT SYSTEM

21CSC101T/OBJECT ORIENTED DESIGN AND

PROGRAMMING
PROJECT REPORT

Submitted by

BHAVANA.SR RA2311030020088
POOJYA SREE.V RA2311030020116
SHRUTI.K RA2311030020126

Under the guidance of

Ms. K. Srinarayani
(Assistant Professor, Department of Computer
Science and Engineering)

II SEMESTER/I YEAR

COMPUTER SCIENCE AND ENGINEERING

FACULTY OF ENGINEERING AND TECHNOLOGY

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

RAMAPURAM, CHENNAI
APRIL 2024

1
 SRM INSTITUTE OF SCIENCE AND TECHNOLOGY
(Deemed to be University U/S 3 of UGC Act, 1956)

BONAFIDE CERTIFICATE

Certified that this project report titled HOSPITAL MANAGEMENT

SYSTEM is the bonafide work of SR. Bhavana (RA2311030020088), V.
Poojya Sree (RA2310030020116), Shruti Karthikeyan
(RA2311030020126) who carried out the project work under my
supervision. This project work confirms to 21CSC101T /Object Oriented
Design and Programming, II Semester, I year, 2024.

SIGNATURE:

Ms. K. Srinarayani, M.E

Assistant Professor
Computer Science and Engineering,
SRM Institute of Science and Technology,
Ramapuram, Chennai.

2
 SRM INSTITUTE OF SCIENCE AND
TECHNOLOGY
RAMAPURAM, CHENNAI

DECLARATION

We hereby declare that the entire work contained in this project report titled
“HOSPITAL MANAGEMENT SYSTEM” has been carried out by SR.
Bhavana (RA2311030020088), V. Poojya Sree (RA2310030020116), Shruti
Karthikeyan (RA2311030020126) at SRM Institute of Science and
Technology, Ramapuram, Chennai, under the guidance of Ms. K.
SRINARAYANI, Assistant professor, Department of Computer Science and
Engineering.

Place: Chennai BHAVANA

Date: POOJYA SREE
SHRUTI

3
 INDEX

S.NO. CONTENTS PG.NO

1. Abstract 1

2. Introduction 2

3. Problem Statement 3

4. Objective 4

5. Scope of Project 5

6. Existing System 6

7. Proposed System 6

8. Models Description 6

9. UML Diagrams 7-16

10. Implementation, Coding and 17-23

Output Screenshot
11. Conclusion 24

4
 LIST OF FIGURES

Figure. No. Title Pg.No.

1.1 Class Diagram 8

1.2 Use Case Diagram 9

2.1 Sequence Diagram 10-11

2.2 Collaboration Diagram 12

3.1 State Chart Diagram 13

3.2 Activity Diagram 14

4.1 Package Diagram 15

4.2 Deployment Diagram 16

4.3 Component Diagram 17

5
 ABSTRACT

The Hospital Management System (HMS) is a comprehensive digital solution

designed to streamline the complex operations of healthcare facilities. This
system integrates various functional modules that assist in the daily management
of administrative, medical, legal, and financial aspects of a hospital's operation.
The core objective of the HMS is to enhance efficiency, reduce operational costs,
and improve the delivery of healthcare services. The system features modules for
patient management, including registration, scheduling, and patient tracking;
staff management, with rostering, payroll, and performance evaluation
capabilities; and inventory management for pharmaceuticals and medical
supplies. It also supports electronic medical records (EMR), facilitating easy
access to patient history, treatment plans, and medical documentation, thereby
enhancing the continuity and quality of care.

Additionally, the HMS includes financial management tools

that handle billing, accounting, and revenue cycle management, ensuring timely
and accurate financial operations. Advanced reporting functionalities offer
analytics on hospital performance, patient outcomes, and resource allocation,
aiding in strategic decision-making.

Implementing HMS results in improved communication between departments,

efficient resource management, and higher patient satisfaction. Ultimately, the
system supports healthcare facilities in achieving better healthcare outcomes by
optimizing both clinical and administrative processes, making it an indispensable
tool in modern healthcare management.

1
 I. INTRODUCTION

Healthcare systems globally face significant challenges in managing hospital

resources efficiently while ensuring timely and accurate patient care. The
introduction of technology into healthcare operations has proven instrumental in
addressing these challenges. This program represents a digital solution aimed at
optimizing hospital and patient data management processes. By automating
tasks such as recording hospital details, managing patient admissions, and
monitoring bed availability, it streamlines operations, reduces errors, and
enhances overall efficiency. With this program, hospitals can enhance their
ability to deliver quality care while patients benefit from improved access and
streamlined admissions processes.

The Hospital Management System (HMS) is a comprehensive system designed

to integrate all aspects of hospital operations, such as medical, administrative,
financial, and legal, into one platform. This integration helps in managing the
vast information and complex processes characteristic of hospitals efficiently
and accurately. Traditionally, hospitals have relied on fragmented systems or
manual methods that often lead to inefficiencies and errors. The advent of HMS
has revolutionized how hospital operations are managed, streamlining processes
and significantly enhancing service delivery and patient care.

2
 II. PROBLEM STATEMENT

Traditional methods of hospital and patient data management often rely on

manual record-keeping, which is labor-intensive and prone to errors. Hospitals
struggle to maintain up-to-date records of available beds, leading to
inefficiencies in-patient admissions and resource allocation. Patients, on the
other hand, may experience delays in accessing care due to the lack of real-time
information on bed availability. There is a pressing need for a systematic
approach to address these challenges and improve the overall quality of
healthcare services. The inefficiencies in the existing system led to suboptimal
resource utilization and can impact patient outcomes negatively.

Despite the critical nature of healthcare services, many hospitals continue to

struggle with outdated or inefficient management systems that compromise
patient care quality, increase waiting times, and escalate costs. Common
problems include inadequate scheduling systems, disjointed information flows,
slow response times, and high administrative overhead. These issues not only
affect the operational efficiency of healthcare institutions but also impact patient
satisfaction and safety. The need for an integrated system that addresses these
challenges is evident and urgent.

3
 III. OBJECTIVE

The primary objective of this project is to develop a comprehensive software

solution that revolutionizes hospital and patient data management. The software
aims to provide a user-friendly platform for hospitals to input and update their
information effortlessly. Likewise, it offers patients a convenient way to register
with their preferred hospitals. Real-time monitoring of bed availability ensures
that hospitals can efficiently manage patient admissions, reducing wait times
and optimizing resource utilization. Overall, the objective is to enhance the
efficiency, accuracy, and accessibility of healthcare services through
technological innovation. By achieving this objective, the program aims to
contribute to improved patient outcomes and a more effective healthcare
system.

• Automate hospital operations to reduce manual labor and decrease the

probability of human error.
• Enhance the efficiency of hospital services by streamlining patient
admissions, discharges, and transfers.
• Improve patient data management through centralized and secure
electronic records.
• Facilitate better communication channels within different hospital
departments.
• Support timely and more informed decision-making through integrated
analytics tools.

4
 IV. SCOPE OF THE PROJECT

The scope of this project encompasses various aspects of hospital and patient
data management. It includes the development of modules for hospital
registration, patient registration, data display, and bed management.
Additionally, the project involves implementing features for administrators to
oversee and manage the system effectively. While the initial focus may be on a
limited number of hospitals and patients, the scalability of the software allows
for future expansion to accommodate a larger network of healthcare facilities
and users. The project's scope extends beyond mere digitization to actively
improving processes and enhancing the overall quality of healthcare delivery.

1. Patient Management: Registration, tracking patient history,

appointments, and patient care management.
2. Inventory Management: Managing medical and non-medical inventory,
including pharmaceuticals and hospital equipment.
3. Staff Management: Employee scheduling, payroll, and human resources
management.
4. Financial Management: Handling billing, insurance claims, and
accounting operations.
5. Reporting and Compliance: Generating customizable reports for
administrative and compliance purposes.
6. Security and Privacy: Ensuring the integrity and confidentiality of
patient and hospital data in compliance with regulatory standards.

This project will initially be implemented in the outpatient department of the

hospital and will gradually be expanded to cover other departments after the
evaluation phase.

5
 V. EXISTING SYSTEM

In the existing system, hospital and patient data management often relies on
manual processes, paper-based records, and fragmented information systems.
Hospitals maintain records using spreadsheets, paper files, or legacy software
systems, leading to data duplication, inaccuracies, and delays in accessing
information. Patient admissions and bed management may be done manually,
making it challenging to track bed availability in real-time and optimize
resource allocation efficiently. Overall, the existing system lacks integration,
real-time updates, and user-friendly interfaces, resulting in inefficiencies and
suboptimal patient care.

VI. PROPOSED SYSTEM

The proposed system introduces automation and integration into hospital and
patient data management. It offers a centralized platform where hospitals can
input and update their information seamlessly. Patients can register online,
choose their preferred hospitals, and access real-time information on bed
availability.

VII. MODULES DESCRIPTION

• Hospital Module: Allows hospitals to register, update, and manage their

information, including name, location, and available beds.
• Patient Module: Enables patients to register, select their preferred
hospitals, and access real-time information on bed availability.
• Data Display Module: Provides functionalities for administrators to view
hospital details, patient records, and bed availability in real-time.

6
 VIII. UML DIAGRAMS

CLASS DIAGRAM

Fig: -1.1

NOTATIONS: -
➢ Classes: Rectangular boxes represent classes. The class name is shown at
the top of the box.
➢ Attributes: Attributes are listed below the class name and prefixed with
a visibility modifier (+ for public, - for private, # for protected).
➢ Operations: Operations (or methods) are listed below the attributes and
prefixed with a visibility modifier. They can also include parameters and
a return type.
➢ Relationships: Lines are used to show relationships between classes.

7
 USE CASE DIAGRAM

Fig: -1.2

NOTATIONS: -
➢ Actors: Actors are represented by stick figures or small human icons.
They represent users of the system ,external systems that interact with it.
➢ Relationships: Lines are used to show relationships between actors and
use cases. There are three main types of relationships:
o Association: A solid line indicates a basic interaction between an
actor and a use case.
o Include: A dashed line with the label "include" indicates that one
use case includes the functionality of another use case.
o Extend: A dashed line with the label "extend" indicates that one
use case extends the functionality of another use case under
specific conditions

8
SEQUENCE DIAGRAM

Fig: -2.1

9
10
 COLLABORATION DIAGRAM

Fig: -2.2
NOTATIONS: -
Classes:
➢ Patient Management: This class manages patients and has methods like
add Patient (), update Patient (), and delete Patient ().
➢ Billing System: Calculates payments and processes them.
➢ Medical Record: Represents patient medical records.
➢ Payment: Deals with payment-related information.
Entities:
➢ Patient: Has attributes like name and record.
➢ Doctor: Attributes include name and specialization.
➢ Service: Attributes are description and cost.
Associations:
➢ Relationships between classes/entities are represented by lines connecting
them:
➢ Patient Management manages Patient.
➢ Billing System processes payments.
➢ Patient has a Medical Record.

11
 STATE CHART DIAGRAM

Fig: -3.1

NOTATIONS: -
Rectangles (representing processes or actions):
➢ “Create Issue”
➢ “Do the Work”
➢ “Code Review”
➢ “Test Issue”
Diamonds (decision points):
➢ “Issue Approved?”
➢ “Work Approved?”
➢ “Issue Completed?”
Oval shapes:
➢ “New Issue” (start of the process)
➢ “Close Issue” (conclusion of the process)

12
 ACTIVITY DIAGRAM

Fig: -3.2

NOTATIONS: -
➢ Activities: Activities are represented by rectangles within the swim
lanes. They represent specific actions or tasks performed by the role
associated with the swim lane.
➢ Flow Arrows: Solid lines with arrowheads connect activities, showing
the sequential order of the workflow.
➢ Decisions: Diamonds represent decision points in the workflow. One or
more outgoing arrows branch from a decision diamond

13
 PACKAGE DIAGRAM

Fig: -4.1
NOTATIONS:
➢ Package: Represented by a rectangle with a smaller tabbed folder icon at
the top. It is labeled with the name of the package.
➢ Dependency: Depicted with a dashed line and an open arrowhead
pointing towards the depended-upon package.
➢ Import: Shown with a dashed line and an open arrowhead, often
annotated with the «import» stereotype.
➢ Merge: Illustrated by a dashed line ending in a filled diamond at the
source package, with the «merge» stereotype.
➢ Public Elements: Denoted by a ‘+’ sign before the element’s name
(optional in package diagrams).

14
 DEPLOYMENT DIAGRAM

Fig: -4.2
NOTATIONS:
➢ Node: Represented by a 3D box-like shape, labeled with the node's name.
Nodes symbolize physical entities such as servers, computers, or devices
where software components are deployed.
➢ Artifact: Shown as a rectangle with a document-like. Artifacts represent
tangible elements like software components, binaries, libraries, or
configuration files that are deployed on nodes.
➢ Association: A solid line between nodes indicating a physical connection
or network path through which the nodes can communicate.
➢ Dependency: Depicted with a dashed line and an arrow indicating a
directional relationship where one node or artifact relies on another.
➢ Deployment: Illustrated by a solid line with a closed arrowhead pointing
from an artifact to a node. This shows that an artifact is deployed on a
specific node.
➢ Communication Path: Represented by a dashed line, possibly with
labels to describe protocols or technologies used (e.g., HTTP, TCP/IP),
indicating the path along which nodes communicate.
15
 COMPONENT DIAGRAM

Fig: -4.3
NOTATIONS:
➢ Component: Represented by a rectangle with two smaller rectangles
protruding from its left side, symbolizing the component's interface.
Components are modular parts of a system.
➢ Interface: Shown as a small circle or a half-circle attached to the
component. This represents a defined point of interaction through which
the component provides or consumes services (e.g., APIs).
➢ Aggregation: Represented by a solid line with an empty diamond at the
end that points to the whole, symbolizing a "whole-part" relationship
where components are made up of smaller components.
➢ Composition: This stronger form of the relationship suggests that the
lifetime of the contained components is bound to the lifetime of the
container component.
➢ Port: Shown as a small square on the boundary of the component. Ports
define the interaction points allowing the component to communicate
with its environment or other components.

16
 IX. IMPLEMENTATION & CODING

The implementation involves coding the software solution using C++

programming language, adhering to object-oriented principles. The program
utilizes classes for hospitals and patients, along with functions for data input,
display, and management. Implementation focuses on efficiency, reliability, and
scalability, ensuring that the software meets the requirements of hospitals,
patients, and administrators.

Source Code: -
#include <iostream>
#include <vector>
#include <string>
using namespace std;
class Person {
protected:
string name;
int age;
char gender;

public:
Person(string _name, int _age, char _gender) : name(_name), age(_age),
gender(_gender) {}
virtual ~Person() {}
};

class Doctor : public Person {

private:
string specialization;

17
 vector<string> patients;

public:
Doctor(string _name, int _age, char _gender, string _specialization)
: Person(_name, _age, _gender), specialization(_specialization) {}

void assignPatient(string patientName) {

patients.push_back(patientName);
}
};

class Patient : public Person {

public: // Making member variables public for simplicity in this example
string name;
int id;
string hospitalName;

Patient(string _name, int _id, string _hospitalName)

: Person(_name, 0, ' '), id(_id), hospitalName(_hospitalName) {}
};

class Appointment {
private:
string doctorName;
string patientName;
string date;
string time;

public:

18
 Appointment(string _doctorName, string _patientName, string _date, string
_time)
: doctorName(_doctorName), patientName(_patientName), date(_date),
time(_time) {}

string getDoctorName() const {

return doctorName;
}

string getPatientName() const {

return patientName;
}

string getDate() const {

return date;
}

string getTime() const {

return time;
}
};

class Hospital {
public: // Making member variables public for simplicity in this example
string name;
vector<Doctor> doctors;
vector<Patient> patients;
vector<Appointment> appointments;

19
 Hospital(string _name) : name(_name) {} // Constructor for Hospital
};

void printHospitalData(const vector<Hospital>& hospitals) {

cout << "Hospital Details:" << endl;
cout << "-----------------" << endl;
for (const Hospital& h : hospitals) {
cout << "Name: " << h.name << endl;
// Additional information like location and available beds can be added
here if needed
cout << "-----------------" << endl;
}
}

void printPatientData(const vector<Patient>& patients) {

cout << "Patient Records:" << endl;
cout << "-----------------" << endl;
for (const Patient& p : patients) {
cout << "Name: " << p.name << endl;
cout << "ID: " << p.id << endl;
cout << "Hospital: " << p.hospitalName << endl;
cout << "-----------------" << endl;
}
}

int main() {
Hospital hospital("General Hospital");

Doctor doctor1("Dr. Smith", 40, 'M', "Cardiology");

20
 Doctor doctor2("Dr. Johnson", 35, 'F', "Pediatrics");
hospital.doctors.push_back(doctor1);
hospital.doctors.push_back(doctor2);

Patient patient1("John Doe", 101, "Hospital A");

Patient patient2("Jane Doe", 102, "Hospital B");
hospital.patients.push_back(patient1);
hospital.patients.push_back(patient2);

hospital.appointments.push_back(Appointment("Dr. Smith", "John Doe",

"2024-04-21", "10:00 AM"));
hospital.appointments.push_back(Appointment("Dr. Johnson", "Jane Doe",
"2024-04-22", "11:00 AM"));

cout << "Appointments:" << endl;

for (const auto& appointment : hospital.appointments) {
cout << "Doctor: " << appointment.getDoctorName() << ", Patient: " <<
appointment.getPatientName()
<< ", Date: " << appointment.getDate() << ", Time: " <<
appointment.getTime() << endl;
}

// Sample hospital and patient data

vector<Hospital> hospitals = {
Hospital("Hospital A"),
Hospital("Hospital B")
// Add more hospitals...
};

21
 vector<Patient> patients = {
{"Patient X", 101, "Hospital A"},
{"Patient Y", 102, "Hospital B"}
// Add more patients...
};

// Display hospital data

printHospitalData(hospitals);

// Display patient data

printPatientData(patients);

return 0;
}

22
X. SCREENSHOTS OF OUTPUTS

23
 XI. CONCLUSION

In conclusion, the developed software solution represents a significant

advancement in hospital and patient data management. By addressing the

limitations of manual processes and legacy systems, the proposed system

streamlines operations, improves data accuracy, and enhances the overall

quality of healthcare services. The integration of automation, real-time updates,

and user-friendly interfaces offers benefits to hospitals, patients, and

administrators alike. With its scalability and adaptability, the system has the

potential to transform healthcare delivery, contributing to improved patient

outcomes and a more efficient healthcare system overall.

Implementing the Hospital Management System represents a significant step

towards enhancing healthcare delivery by improving operational efficiencies,

reducing costs, and improving patient care quality. The proposed system will

automate critical processes, ensuring that they are error-free, faster, and more

efficient, which is essential in a fast-paced healthcare environment. Ultimately,

the successful implementation of this HMS will lead not only to enhanced

operational performance but also to higher patient satisfaction and better

healthcare outcomes.

24