Project Hospital Management System

Submitted by:
Zain Javed : 2023-uam-1903
Annas Abbas: 2023-uam-1889
Abdul Wahab: 2023-uam-1908
M. Najam Ul Hassan: 2023-uam-1901
Introduction
Hospital Management System
Hospitals play a vital role in our lives by offering the greatest medical care to those
with a variety of illnesses, whether brought on by stress, emotional trauma, a
change in the weather, or other causes. Hospital staff members who are essential
to the proper operation of the facility must maintain detailed records of their daily
activities and interactions with patients, physicians, nurses, ward boys, and other
staff members.
However, it is exceedingly time-consuming and prone to error to keep track of all
the actions and their records on paper. Not to mention that it takes a lot of time
and is highly inefficient given the ongoing rise in both the population and hospital
visits. Keeping track of all these documents is extremely unpredictable, ineffective,
and prone to mistakes.
Problem Statement for Hospital Management System
The broken and manual processes used by hospital management today create
inefficiencies and make it difficult to provide high-quality patient care. Unorganised
communication lines, outdated technology, and paper-based record-keeping all
lead to mistakes, omissions, and delays in obtaining vital patient data.
Furthermore, the absence of integrated solutions makes it more difficult to analyze
data for resource optimisation and well-informed decision-making.

A comprehensive hospital management system (HMS) that centralises and

automates critical functions is desperately needed in this situation to address these
issues. In addition to streamlining administrative duties and facilitating smooth
patient management, the system should enhance provider communication and
offer strong analytics tools for ongoing performance evaluation and enhancement.
Proposed Solution for Hospital Management System
Our suggested Hospital Management System (HMS) provides a simplified approach
to improve patient care and hospital operations. Our intuitive software assists in
effective workflow management by integrating billing, analytics, appointment
scheduling, and patient management. Decision-making accuracy and speed are
increased by automated procedures, electronic health record (EHR) administration,
and real-time data access. The technology protects data security and guarantees
adherence to healthcare rules. Our Health Care Management System (HMS)
enables healthcare providers to achieve better patient outcomes, optimise
resource utilisation, and deliver high-quality care by centralising functions and
offering powerful features.
 Objective of the Project
The objective of the Hospital Management System (HMS) project is to design and
implement an efficient and user-friendly system that automates the various tasks
associated with managing a hospital.
1. To computerise every detail related to hospital and patient information.
2. Arranging patient appointments with physicians in a way that is convenient for
both parties.
3. Appropriately scheduling emergency room visits and specialised medical
appointments to ensure that hospital resources are completely and effectively
utilised.
4. The medical store's stock level should decrease if it provides patients with
medications, and vice versa.
5. It ought to be capable of managing patient test findings from the hospital's
pathology lab.
6. Every time a transaction is completed, the inventory ought to be updated
automatically.
7. Patients' information should be current, and their records should be preserved
in the system for future reference.
Scope of the Project
The scope of the project "hospital management system" typically includes various
aspects related to the efficient functioning of a hospital. This may involve managing
patient records, appointments, staff schedules, inventory, billing, and other
administrative tasks. Additionally, it might encompass features like electronic
health records (EHR), laboratory and pharmacy management, and integration with
medical devices. The scope can vary depending on the specific requirements of the
hospital and the functionalities desired in the management system.
The scope of the project of Hospital Management System typically covers the
following aspects:
Functional Requirement
1. Patient Management
 Register patients
 Maintain patient records including personal information, medical history,
and treatment details
 Schedule appointments and manage patient queues
2. Staff Management
 Register staff members including doctors, nurses, administrative staff,
etc.
 Manage staff schedules and assignments
 Track staff attendance and performance
3. Inventory Management
 Maintain inventory of medical supplies, equipment, and medications
 Track usage and order supplies when needed
 Manage stock levels to avoid shortages or excess inventory
4. Billing and Accounting
 Generate bills for services rendered to patients
 Manage insurance claims and payments
 Track financial transactions and generate reports
5. Appointment Management
 Schedule and manage patient appointments with doctors and other
healthcare providers
 Send reminders to patients about upcoming appointments
6. Medical Records Management
 Create and maintain electronic health records (EHR) for patients
 Ensure the security and privacy of patient information
 Allow authorized personnel to access and update medical records as needed
Non-Functional Requirement
1. Usability:
 Ensure the system is user-friendly and easy to navigate for both staff and
patients
 Provide clear instructions and guidance for using different features of the
system
2. Reliability:
 Ensure the system is reliable and available whenever needed, with minimal
downtime
 Implement backup and recovery mechanisms to prevent data loss in case of
system failures
3. Performance:
 Ensure fast response times for accessing patient records and performing
other tasks
 Optimize system performance to handle a large number of concurrent users
and transactions
4. Security:
  Implement robust authentication and authorization mechanisms to prevent
unauthorized access to patient records and sensitive information
 Encrypt data transmission to protect patient privacy
 Regularly update and patch the system to address security vulnerabilities
5. Scalability:
 Design the system to scale easily as the hospital grows and the number of
patients and staff increases
 Ensure the system can handle additional workload without significant
performance degradation
6. Interoperability:
 Ensure the system can integrate with other healthcare systems and external
services such as laboratories, pharmacies, and insurance providers
 Implement standard protocols and interfaces to facilitate data exchange and
communication between different systems.

Main Actor
1. Patient
Stores information about patients such as patient ID, name, contact details, and
address.
2. Doctor
Contains details about doctors including doctor ID, name, specialty, contact
information, and department.
3. Appointment
Represents appointments made by patients with doctors. It includes attributes
like appointment ID, appointment date and time, patient ID, doctor ID, and any
additional notes.
4. Staff
Stores information about hospital staff members such as staff ID, name,
position, and contact details.
5. Department
Contains details about different departments in the hospital. Each department
has a department ID and name.

Use Case Diagram of Hospital Management System

Use case diagram
It referred as a Behaviour model or diagram. It simply describes and displays the
relation or interaction between the users or customers and providers of application
service or the system. It describes different actions that a system performs in
collaboration to achieve something with one or more users of the system. Use case
diagram is used a lot nowadays to manage the system.
Here is a Use Case Diagram for Hospital Management System:

Activity Diagram of Hospital Management System

This activity diagram outlines the main activities and interactions within the
Hospital Management System, including booking appointments, patient check-in,
accessing medical records, billing, inventory management, staff management, and
report generation. Each activity represents a specific task or function performed by
users or the system.
1. User Interaction:
1. Book Appointment
2. Check in
3. View Medical Records
4. Pay Bills
5. Manage Inventory
6. Manage Staff
7. Generate Reports
8. Log Out
2. Book Appointment
1. User selects Book Appointment.
2. System displays available doctors and time slots.
3. User selects a doctor and preferred time.
4. System confirms the appointment booking.
3. Check in
1. Patient arrives at the hospital.
2. Receptionist greets the patient and verifies their appointment.
3. Receptionist checks the patient in and assigns a queue number.
4. View Medical Records
1. User selects View Medical Records.
2. System prompts user to enter patient ID or name.
3. System retrieves and displays the patient's medical history.
5. Pay Bills
1. User selects Pay Bills.
2. System displays a list of outstanding bills for the user.
3. User selects the bill(s) to pay and enters payment details.
 4. System processes the payment and updates the billing records.
6. Manage Inventory
1. Authorized staff member selects Manage Inventory.
2. System displays options to add, update, or remove items from inventory.
3. Staff member performs the desired inventory management tasks.
4. System updates the inventory database accordingly.
7. Manage Staff
1. Authorized administrator selects Manage Staff.
2. System displays options to add, update, or remove staff members.
3. Administrator performs the desired staff management tasks.
4. System updates the staff database accordingly.
8. Generate Reports
1. Authorized user selects Generate Reports.
2. System provides options to generate various reports such as patient
statistics, financial summaries, etc.
3. User selects the type of report to generate.
4. System generates the report and displays it to the user.

An architecture diagram for a Hospital Management System (HMS)

illustrates the structure and components of the system and their interactions. It
typically includes layers such as user interface, application logic, database, and
external integrations.

Hospital Management System Architecture Diagram

1. Layers and Components

1.1. User Interface Layer (Frontend)

- Purpose: Interaction with users (patients, doctors, staff).
- Technologies: HTML/CSS, JavaScript frameworks (React, Angular, etc.),
mobile apps.
- Components:
- Patient Portal: Appointment booking, test results, payment.
 - Staff Portal: Schedules, patient records, administrative tasks.
- Doctor Dashboard: Prescriptions, medical records, test results.

A swim lane diagram is a type of

process flow diagram that organizes processes into lanes to visually distinguish
tasks, roles, or responsibilities of different entities involved in a system. In the
context of a Hospital Management System, it can represent the flow of tasks
among different departments or roles such as patients, receptionists, doctors, and
the administration.

Swim lane Diagram for Hospital Management System

Key Swim lanes (Roles/Entities)

1. Patient: Represents the patient interacting with the system.
2. Receptionist: Handles appointments, registrations, and inquiries.
3. Doctor: Manages diagnoses, prescriptions, and treatments.
4. Pharmacy: Dispenses medicines based on prescriptions.
5. Lab/Diagnostic Center: Conducts tests and provides reports.
6. Administration: Oversees hospital operations and billing.

Example Process Flow

1. Patient
- Requests an appointment online or at the hospital.
- Provides personal and medical history during registration.
- Visits the doctor at the scheduled time.

2. Receptionist
- Schedules the appointment and registers the patient.
- Collects fees and issues receipts.
- Directs the patient to the respective doctor or department.

3. Doctor
- Examines the patient and prescribes tests or medications.
- Refers the patient to the lab or specialist if needed.
- Updates medical records and advises follow-up care.

4. Lab/Diagnostic Center
- Conducts medical tests (e.g., blood tests, X-rays).
- Shares reports with the doctor for diagnosis.

5. Pharmacy
- Dispenses prescribed medicines to the patient.
- Updates inventory and generates bills.
6. Administration
- Ensures system data security and backups.
- Manages billing, insurance claims, and reporting.
- Monitors staff performance and hospital efficiency.

Diagram Representation
Each swim lane represents one of the above roles. The diagram uses arrows to
depict the process flow, showing how tasks move across swim lanes.
For example
- Patient -> Receptionist (to book an appointment).
- Receptionist -> Doctor (to direct the patient).
- Doctor -> Lab/Diagnostic Center -> Doctor (to share test reports).
- Doctor -> Pharmacy (to fill prescriptions).

Benefits of the Swim lane Diagram

- Clarifies roles and responsibilities in the system.
- Highlights process bottlenecks and inefficiencies.
- Improves coordination between hospital departments.
- Serves as a blueprint for implementing or optimizing a Hospital Management
System.
Sequence Diagram of Hospital Management System

Creating a sequence diagram for a Hospital Management System involves depicting

the interactions between various components or actors within the system. Here's a
simplified version:

1. Patient Admission:
 Patient arrives at the hospital.
 Receptionist greets the patient.
 Receptionist collects patient information (name, contact details, reason for
visit, insurance details, etc.).
 Receptionist verifies patient's insurance coverage.
 Receptionist assigns a unique identifier (ID) to the patient.
2. Medical Assessment:
 Nurse or medical assistant escorts the patient to the examination room.
 Nurse takes vital signs and records patient history.
 Nurse updates patient's medical record in the system.
3. Consultation with Doctor:
 Doctor reviews patient's medical history and current condition.
 Doctor performs physical examination and orders further tests if necessary.
 Doctor discusses diagnosis and treatment plan with the patient.
4. Treatment and Procedures:
 Nurse administers medications or treatments as prescribed by the doctor.
 Nurse schedules any necessary procedures (e.g., X-rays, scans, surgeries).
5. Patient Discharge:
 Doctor determines when the patient is ready for discharge.
  Nurse provides discharge instructions and medications.
 Receptionist handles billing and insurance claims.
 Patient leaves the hospital.
This sequence diagram illustrates the flow of interactions between various
components involved in the patient admission process, including receptionists,
nurses, doctors, and patients. Each step represents a specific action or task
performed as part of the admission process within the Hospital Management
System.

Data Flow Diagram of Hospital Management System

A Data Flow Diagram (DFD) for a Hospital Management System (HMS) illustrates
the flow of data within the system and between external entities. Here's a
simplified DFD for an HMS
In this DFD:
1. External Entities: These represent entities outside the system that interact
with it, such as patients, doctors, and administrators.
2. Processes: Processes represent functions or operations performed within the
Hospital Management System, such as Patient Records, Appointment Scheduler,
Patient Billing, Doctor Records, and Medical Records.
3. Data Flows: Arrows represent the flow of data between external entities,
processes, and the database. For example, patient information flows from the
Patient Records process to the Database, and medical records flow from the
Medical Records process to the Database.
4. Data Stores: These represent repositories where data is stored, such as the
Hospital Management Database. Patient information, appointment details,
doctor records, and medical records are stored in the database.
This DFD provides a high-level overview of how data flows within the Hospital
Management System, showing the interactions between external entities,
processes, and the database.
Class Diagram of Hospital Management System:
Class Diagram for Hospital Management System simply describes structure of Hospital
Management System class, attributes, methods or operations, relationship among objects .

For a Hospital Management System (HMS), the class diagram and its characteristics would
typically include:
1. Classes: Representing entities such as Patient, Doctor, Nurse, Administrator,
Appointment, Medical Record, Department, and Billing.
2. Attributes: Each class would have attributes representing its properties. For example, the
Patient class might have attributes like patient ID, name, and gender, date Of Birth, and
contact Details.
3. Operations (Methods): These would define the behaviors associated with each class. For
instance, the Appointment class might have methods like schedule Appointment (), cancel
Appointment (), and reschedule Appointment ().
4. Associations: Relationships between classes would be depicted to show how they are
connected. For instance, an association between Patient and Doctor classes would show
that a patient can be associated with one or more doctors.
5. Multiplicity: Multiplicity would specify how many instances of one class are associated
with instances of another class. For example, a Doctor can have multiple patients,
indicating a one-to-many relationship.
6. Inheritance (Generalization): If there are common attributes or methods shared between
classes, inheritance can be used to depict this relationship. For example, Doctor and Nurse
classes might inherit from a common super class called Healthcare Professional.
7. Composition and Aggregation: These relationships would show how one class contains or
is composed of another class. For example, a Hospital class may have a composition
relationship with the Department class, indicating that a hospital consists of multiple
departments.
8. Dependency: This would show when one class relies on another class, usually
through method parameters or return types. For example, the Billing class may
have a dependency on the Patient class to retrieve patient information for
billing purposes.

An architecture diagram for a Hospital Management System (HMS) illustrates the

structure and components of the system and their interactions. It typically includes
layers such as user interface, application logic, database, and external integrations.

---

Hospital Management System Architecture Diagram*

1. Layers and Components

1. User Interface Layer (Frontend)

Purpose: Interaction with users (patients, doctors, staff).
Technologies: HTML/CSS, JavaScript frameworks (React, Angular, etc.), mobile
apps.
Components:
- Patient Portal: Appointment booking, test results, payment.
- Staff Portal: Schedules, patient records, administrative tasks.
- Doctor Dashboard: Prescriptions, medical records, test results.

2. Application Layer (Backend)

-Purpose: Business logic and workflow handling.
- Technologies: Node.js, Java, Python, .NET, PHP.
Components
- Appointment Management: Schedules and booking.
- Electronic Health Records (EHR): Stores patient medical history.
- Billing and Payments: Handles invoices and transactions.
- Lab Module: Integrates with diagnostics for tests and reports.
- Pharmacy Module: Tracks prescriptions and inventory.

1.3. Database Layer

Purpose: Data storage and retrieval.
Technologies: MySQL, PostgreSQL, MongoDB, Oracle.
Components:
Patient Records: Personal and medical details.
Staff Records: Doctor, nurse, and admin data.
Appointments: Schedules and availability.
Billing: Transactions, insurance details.
Inventory: Pharmacy and equipment data.

1.4. Integration Layer (APIs & External Services)*

Purpose: Connects with third-party systems.
Components
- Payment Gateways: For billing transactions.
- Insurance Systems: Verifies claims and policies.
- Diagnostic Labs: Fetches test reports.
- SMS/Email Services: Sends notifications and alerts.

1.5. Security Layer

- Purpose: Ensures data protection and access control.
- Technologies: SSL/TLS, OAuth, JWT.
Features
- Role-Based Access Control (RBAC): Limits access to sensitive data.
- Data Encryption: Protects patient records.
- Audit Logs: Tracks user activity.

---

Workflow
- A patient interacts with the frontend to book an appointment.
- The application layer processes the request and schedules it in the database.
- During a consultation, the doctor accesses patient records via the application
layer.
- If tests are required, the lab module stores and retrieves test reports.
- The billing module generates invoices, which the patient pays using an integrated
payment gateway.