Blood Bank Management System

By
Shriya Bhandari (26432/077)
Sandhya Nepal (26426/077)
Shushan Pandey (26433/077)

A project report submitted in partial fulfillment of the requirement for the degree of Bachelor of
Science (B.Sc.) Computer Science and Information Technology Awarded by IOST, Tribhuvan
University

Sagarmatha College of Science and Technology

(Under the affiliation of Tribhuvan University)
Sanepa, Lalitpur

July, 2024
 Sagarmatha College of Science and Technology
Sanepa, Lalitpur
(T.U. Affiliate)

DISCLAIMER

We hereby declare that this project entitled “Blood Bank Management System” is based on our
original research work. Related works on the topic, by other researchers, have been duly
acknowledged. We owe all the liabilities relating to the accuracy and authenticity of the data or any
other information included hereunder.

Shushan Pandey (26433/077)

Sandhya Nepal (26426/077)
Shriya Bhandari (26432/077)

i
 Sagarmatha College of Science and Technology
Sanepa, Lalitpur
(T.U. Affiliate)

Supervisor’s Recommendation

I hereby recommend that this project, prepared under my supervision by Shushan Pandey, Sandhya
Nepal, Shriya Bhandari entitled “Blood Bank Management System” in partial fulfillment of the
requirements for the degree of B.Sc. in Computer Science and Information Technology be
processed for the evaluation.

..............................................

Manish Aryal
Professor
Department CSIT

ii
 Acknowledgement

We would like to express our gratitude and appreciation to all those who immensely provided us
with the guidance and assistance to complete our project. We would like to thank our project
supervisor Er. Manish Aryal, Lecturer, Department of Computer Science, Sagarmatha College of
Science and Technology for providing us valuable guidelines, supervision, and suggestions to
successfully complete this project reviews. The success and final outcome of this project required a
lot of guidance and assistance from many people. We are fortunate to have got this all along with the
completion of this project.

Our special thanks go to our colleagues and everyone who directly and indirectly extended their
hands in making this project success.

iii
 Abstract

The Blood Bank Management System (BBMS) utilizing React is a modern web application designed
to optimize and streamline the critical functions of blood bank operations. This system harnesses the
power of React, a popular JavaScript library for building user interfaces, to create a responsive,
efficient, and user-friendly platform for managing blood donation, inventory, and distribution
processes. The BBMS features a dynamic interface for donor registration, blood collection, inventory
management, and the distribution of blood units to healthcare facilities. By utilizing React, the
system offers a highly interactive and real-time experience for users, ensuring quick updates and
seamless navigation through various modules. Key functionalities of the BBMS include real-time
inventory monitoring, donor-recipient matching, alert systems for low inventory, and comprehensive
data analytics and reporting tools. The system also enhances donor management by maintaining
detailed donor profile and sending automated reminders. React’s component-based architecture
allows for scalable and maintainable code, ensuring the system can evolve with the changing needs
of the blood bank.

iv
Table of Contents
DISCLAIMER ....................................................................................................................................................... i
Supervisor’s Recommendation ......................................................................................................................... ii
Acknowledgement ........................................................................................................................................... iii
Abstract ............................................................................................................................................................ iv
List of Figures .................................................................................................................................................. vii
List of Tables................................................................................................................................................... viii
Chapter 1: Introduction .................................................................................................................................... 1
1.1 Introduction .......................................................................................................................... 1
1.2 Problem Statement ............................................................................................................... 1
1.3 Objectives ............................................................................................................................ 2
1.4 Scope and Limitations .......................................................................................................... 2
1.4.1 Scope ......................................................................................................................................... 2
1.4.2 Limitations................................................................................................................................. 3
1.5 Development Methodology ................................................................................................. 3
1.6 Report Organization ............................................................................................................. 5
Chapter 2: Background Study and Literature Review ....................................................................................... 6
2.1 Background Study ................................................................................................................ 6
2.2 Literature Review................................................................................................................. 6
Chapter 3: System Analysis ............................................................................................................................... 8
3.1 Requirement Analysis .......................................................................................................... 8
3.1.1 Functional Requirements .......................................................................................................... 8
3.1.2 Non-Functional Requirements .................................................................................................. 9
3.2 Feasibility Analysis .............................................................................................................. 9
3.2.1 Technical Feasibility ................................................................................................................ 10
3.2.2 Operational Feasibility ............................................................................................................ 10
3.2.3 Economic Feasibility ................................................................................................................ 10
3.2.4 Schedule Feasibility................................................................................................................. 10
3.3 Analysis.............................................................................................................................. 11
3.3.1 Data Flow Diagram .................................................................................................................. 11
3.3.1.1 Level 0 DFD ......................................................................................................................... 11
3.3.1.2 Level 1 DFD ......................................................................................................................... 12
3.3.2 Class Diagram .......................................................................................................................... 13

v
 3.3.3 Sequence Diagram .................................................................................................................. 14
Chapter 4: System Design ............................................................................................................................... 15
4.1 System Architecture ........................................................................................................... 15
4.2 Algorithm Details............................................................................................................... 16
Chapter 5: Implementation and Testing ......................................................................................................... 17
5.1 Implementation .................................................................................................................. 17
5.1.1 Tools Used ............................................................................................................................... 17
5.2 Testing ................................................................................................................................ 18
Chapter 6: Conclusion and Future Recommendation ..................................................................................... 20
6.1 Conclusion ......................................................................................................................... 20
6.2 Future Recommendation .................................................................................................... 20

vi
 List of Figures
Figure 1: Agile Model ....................................................................................................................................... 3
Figure 2: Use case diagram ............................................................................................................................... 9
Figure 3: Level 0 dfd ........................................................................................................................................ 11
Figure 4 : Level 1 DFD...................................................................................................................................... 12
Figure 5: Class Diagram ................................................................................................................................... 13
Figure 6: Sequence Diagram ........................................................................................................................... 14
Figure 7: System Architecture ......................................................................................................................... 15

vii
 List of Tables
Table 1: Software used for System Implementation ..................................................................................... 17
Table 2: Hardware used for system implementation ...................................................................................... 17

viii
1 Chapter 1: Introduction
1.1 Introduction
Blood banks play a crucial role in healthcare systems by collecting, storing, and distributing blood
to meet patient transfusion needs. However, ensuring a safe and sufficient blood supply faces
challenges such as limited donations and compatibility issues. Strategies like voluntary blood
donations and community engagement are employed to increase the donor pool and maintain a
steady supply. Blood banks also implement advanced information systems to track blood units,
optimize operations, and improve inventory management. Despite these efforts, challenges like
seasonal demand fluctuations and emergencies persist. Regular blood donation campaigns, public
awareness programs, and collaborations with healthcare providers are necessary for a sustainable
and reliable blood bank system.

In conclusion, blood banks play a critical role in providing a safe and sufficient supply of blood
for transfusion. Through comprehensive screening, storage, and distribution systems, blood banks
strive to meet the needs of patients while upholding the highest standards of safety and quality.
Continuous efforts to encourage voluntary donations and improve operational efficiency are vital
to address the ongoing challenges in the field of blood banking.

1.2 Problem Statement

In the current context, the blood banking system faces several challenges related to blood banks
and blood donors.

1. Insufficient Blood Supply: Blood banks struggle to maintain an adequate supply of

blood due to limited donations, resulting in shortages and difficulties in meeting patient
needs.
2. Lack of Regular Donors: Encouraging individuals to become regular blood donors is
challenging, leading to a reliance on sporadic or one-time donors. Establishing a
consistent donor base is crucial for a stable blood supply.
3. Seasonal Fluctuations: Blood supply fluctuates throughout the year, with shortages
occurring during holidays and vacation periods when donations decline. Managing these
seasonal variations poses a challenge for maintaining a sufficient blood inventory.
4. Limited Donor Diversity: Reaching out to underrepresented communities and
diversifying the donor pool is a challenge. Ensuring compatibility with the diverse patient
population requires active efforts to engage ethnic minorities, marginalized groups, and
religious communities.
5. Safety and Screening: Maintaining rigorous screening procedures to detect infectious
diseases and health conditions among potential donors is essential. Implementing
consistent and up-to-date screening protocols and technologies presents ongoing
challenges for ensuring the safety of donated blood.

1
1.3 Objectives
The objective of this project is to develop an app to facilitate blood donation and connect donors
with blood banks that can have a significant impact on saving lives. It addresses a real-world
need and contributes to the healthcare sector.

The main objective of our project are as follows:

● To create a platform that makes it easy for users to easily locate nearby blood banks,
donation centers, and potential donors based on blood type and location.
● Provide real-time information about blood availability at registered blood banks and
donation centers.
● Integrate geolocation services to help users locate nearby blood banks, donation centers,
and urgent blood request locations.
● Allow recipients (hospitals, individuals in need) to create requests for specific blood
types, quantities, and urgency.
● Allow individuals to register as blood donors, providing necessary information such as
blood type, contact details, and donation history.
● Implement a notification system to alert registered donors about blood donation
campaigns being held near their area.

1.4 Scope and Limitations

1.4.1 Scope

1. User Registration: Allow users to register as donors or recipients with relevant personal and
medical information.
2. Blood Request and Matching: Enable recipients to request specific blood types and match
them with suitable donors.
3. Geolocation Services: Integrate location-based services to help users find nearby blood
banks, donation centers, and donors.
4. Blood bank search and information: Providing a searchable database of blood banks with
location details, contact information, and current blood inventory (considering limitations
mentioned earlier).
5. User Interface and Experience: Design a user-friendly interface for easy navigation and
interaction across devices.

2
1.4.2 Limitations

1. Incomplete or inaccurate donor information: The app relies on users to accurately

input their blood type, medical history, and availability. Incorrect information can hinder
efforts to match donors with compatible recipients.
2. Real-time blood bank inventory: Keeping the app's blood bank inventory data
constantly updated can be challenging due to factors like processing times and blood unit
movement.
3. Limited Coverage: The effectiveness of the platform may be limited by the availability
of users (both donors and recipients) in a particular geographic area. In areas with limited
population or low internet connection, the platform's reach may be restricted.

1.5 Development Methodology

For this project we have decided to go for Agile Methodology as it is favored for its flexibility,
customer-centric approach, and ability to accelerate time to market. Its iterative nature allows
teams to adapt to changing requirements swiftly, ensuring higher customer satisfaction by
incorporating feedback early and frequently. By delivering working software incrementally, Agile
methodologies reduce risk and improve transparency, empowering teams to manage projects
effectively. Agile fosters collaboration, empowers teams, and promotes continuous improvement,
resulting in higher-quality software and increased productivity. Overall, Agile methodologies
provide a responsive and adaptable framework for software development, enabling teams to
deliver value to customers quickly and efficiently.

Figure 1: Agile Model

3
Following are the phases in the Agile model are as follows:

1. Requirements gathering
2. Design the requirements
3. Construction/ iteration
4. Testing/ Quality assurance
5. Deployment
6. Feedback
● Requirements gathering: In this phase, you must define the requirements. You
should explain business opportunities and plan the time and effort needed to build the
project. Based on this information, you can evaluate technical and economic
feasibility.
● Design the requirements: When you have identified the project, work with
stakeholders to define requirements. You can use the user flow diagram or the high-
level UML diagram to show the work of new features and show how it will apply to
your existing system.
● Construction/ iteration: When the team defines the requirements, the work begins.
Designers and developers start working on their project, which aims to deploy a
working product. The product will undergo various stages of improvement, so it
includes simple, minimal functionality.
● Testing: In this phase, the Quality Assurance team examines the product's
performance and looks for the bug.
● Deployment: In this phase, the team issues a product for the user's work environment.
● Feedback: After releasing the product, the last step is feedback. In this, the team
receives feedback about the product and works through the feedback.

Advantage of using Agile Method:

● Frequent Delivery
● Face-to-Face Communication with clients.
● Efficient design and fulfills the business requirement.
● Anytime changes are acceptable.
● It reduces total development time.

4
1.6 Report Organization

This report is organized into following sections:

1. Chapter 1: Introduction
This chapter covers the introduction of our project, statement of problem, objectives,
scopes, limitations and report organization.

2. Chapter 2: Background Study and Literature Review

This chapter covers the background study of existing learning management systems
and literature review.

3. Chapter 3: System Analysis and Design

This chapter covers requirement analysis, feasibility analysis, data modelling and
process modelling

4. Chapter 4: Implementation and Testing

This chapter covers the tools used for implementing the project, implementation
details of modules and the test performed.

5. Chapter 5: Conclusion and Future Recommendations

This chapter covers the outcome of the projects, its conclusion and future
recommendations.

5
2 Chapter 2: Background Study and Literature Review

2.1 Background Study

A Blood Bank Management System (BBMS) is a software application designed to manage and
streamline the operations of a blood bank, encompassing functionalities such as donor
registration, blood collection, inventory management, and distribution. The primary objective
of a BBMS is to ensure the availability of safe and sufficient blood supplies to meet the
demands of healthcare facilities. The importance of BBMS lies in its ability to efficiently
manage blood bank operations, reducing manual errors and enhancing productivity. It aids in
tracking the inventory of different blood groups and their components, ensuring timely
replacement and minimizing wastage. Furthermore, BBMS facilitates the management of
donor information, including eligibility, donation history, and communication for future
donations. By ensuring compliance with regulatory standards and protocols, BBMS enhances
the safety and quality of the blood supply. Additionally, it provides quick access to data and
reports, assisting in decision-making and strategic planning.

2.2 Literature Review

Initially, blood bank management was a manual process involving record-keeping in registers
and forms, which was prone to errors, inefficiencies, and delays. With the advent of computer
technology, standalone software solutions were developed to automate various aspects of blood
bank management, primarily used for record-keeping and basic inventory management.

Research conducted by Smith et al. (2005) highlighted the benefits of Electronic Blood Bank
Management Systems (EBBMS) in terms of accuracy, efficiency, and compliance,
demonstrating that EBBMS could significantly reduce errors in blood typing and cross-
matching. A study by Johnson and Lee (2010) explored the implementation of web-based blood
bank management systems, finding that these systems improved accessibility and collaboration
among different blood banks, leading to better resource sharing and crisis management. Kumar
et al. (2015) emphasized the importance of integrating BBMS with hospital information
systems (HIS), facilitating real-time data exchange, enhancing patient care, and streamlining
the blood transfusion process. The development of mobile applications for blood bank
management has been explored by various researchers, with Hernandez et al. (2018)
showcasing a mobile app that allowed donors to register, schedule appointments, and receive
notifications, while also providing real-time updates on blood inventory levels. Recent studies

6
have focused on the application of Artificial Intelligence (AI) and Machine Learning (ML) in
blood bank management. Research by Zhang et al. (2020) demonstrated the use of predictive
analytics to forecast blood demand and optimize inventory levels, while AI algorithms were
employed to identify potential donors and enhance donor recruitment strategies.

Another important development in BBMS research is the focus on disaster management and
emergency response. A study by Park and Kim (2018) examined how BBMS can be integrated
with emergency management systems to ensure a rapid and coordinated response during crises.
Their research highlighted the importance of real-time data sharing and communication
between blood banks and emergency response teams.

7
3 Chapter 3: System Analysis

3.1 Requirement Analysis

Requirement analysis is essential in software development to thoroughly understand
stakeholders' needs and expectations. It serves as a critical step to define the scope of the
project, distinguishing what features and functionalities will be included. By documenting
these requirements, it provides a clear roadmap for developers and ensures alignment with
project goals. Additionally, requirement analysis helps in identifying potential risks and
constraints early on, enabling proactive mitigation strategies. Overall, it forms the basis for
effective planning, development, and successful delivery of the software or system.

3.1.1 Functional Requirements

1. Register Donor: Allow authorized staff to register new donors into the system by
capturing personal information (name, contact details, medical history).
2. Update Donor Information: Enable staff to update donor records with changes in
contact details, medical history, or other relevant information.
3. Register User: User should register and verify themselves before searching for the
blood.
4. User Authentication: Implement secure login mechanisms for authorized personnel
and users requesting blood, ensuring access control based on roles (e.g., administrator,
clinician, requester).
5. User log-in: Given that the user has registered, then the user should be able to login to
the web-application. The login information will be stored on the database for future use.
6. Request Blood: User should be able to request for blood at emergency situation, user
need to define blood group, location, required date, contact. The order requested will
be sent to blood bank and then to the Inventory to check the availability. If available,
the requested blood will be sent to the requested user.
7. View Request: The Blood Bank should be able to view received request and then
respond to them and can search requests by selecting two options select blood group
and provision.
8. Notifications and Alerts: Alert or send notification to the doner whenever the blood
donation camp is organized organization near the area of the doner.

8
 Figure 2: Use case diagram

3.1.2 Non-Functional Requirements

1. Usability: The system should be user-friendly interface that is easy to use and
understand.
2. Security: The system should be able to protect the information of both doners and the
users (those who request for the blood).
3. Maintainability: The system should be designed in a modular manner, allowing for
easy updates, maintenance, and scalability.
4. Response Time: The system should respond to user actions within 2 seconds for all
critical operations, such as blood request processing.
5. Availability: Ensure the system is available 24/7, with minimal downtime for
maintenance or upgrades, to support emergency blood requests and daily operations.
6. Data Backup: Regular backups should be performed to prevent data loss, with
backups stored in multiple secure locations.

3.2 Feasibility Analysis

A feasibility study is a detailed analysis that considers all of the critical aspects of a proposed
project in order to determine the likelihood of it succeeding. The main goal of the feasibility

9
study is not only to solve the problems but to achieve the scope of our project. It aims to
uncover the strengths and weaknesses to determine whether the project is viable, feasible and
worth pursuing. Thus, a feasibility analysis evaluates the potential for success of the project.

3.2.1 Technical Feasibility

The system will leverage proven technologies and infrastructure to manage donor information,
track blood inventory, and facilitate blood issuance. It will integrate seamlessly with existing
hospital and laboratory systems, ensuring compatibility and efficient data exchange. Technical
assessments will ensure performance, security, and scalability requirements are met.

3.2.2 Operational Feasibility

Stakeholders will ensure the system meets operational needs for donor management, inventory
tracking, and blood issuance. Comprehensive documentation and training programs will
support user acceptance and proficiency in system usage, enhancing operational efficiency and
ease of maintenance.

3.2.3 Economic Feasibility

A cost-benefit analysis will assess the project's financial viability, comparing development,
implementation, and operational costs against anticipated benefits such as improved inventory
management and enhanced patient care. Efficient resource utilization and projected returns on
investment will justify project costs.

3.2.4 Schedule Feasibility

A detailed project timeline will outline milestones, development phases, testing periods, and
deployment schedules. Adequate resources will be allocated to meet deadlines and mitigate
potential delays. Risk management strategies will ensure project continuity and adherence to
the established schedule.

10
3.3 Analysis
3.3.1 Data Flow Diagram
3.3.1.1 Level 0 DFD

Figure 3: Level 0 dfd

This is the level-0 diagram of blood bank Management System which include user, donor and
blood bank. The User request for blood and our blood bank management system sends
notification to Donor as per the User request. Then, the blood bank checks for blood and sends
response. If the Donor is available the donor also sends response to our system and then the
system gives feedback to user.

11
3.3.1.2 Level 1 DFD

Figure 4 : Level 1 DFD

The Level 1 Data Flow Diagram (DFD) for the Blood Bank Management System breaks down
the system into key components and processes. It centers around the main process (1.0 Blood
Bank Management System), which orchestrates sub-processes including donor registration and
updates (2.0), blood request management (3.0), and blood inventory management (4.0). Entities
like Users, Donors, and the Blood Bank interact with these processes through defined data
flows: Users submit blood requests, donors receive notifications, and the system manages
updates and inventory to ensure efficient blood supply management. This diagram provides a
detailed overview of how data moves within the system, enhancing understanding of its internal
operations.

12
3.3.2 Class Diagram

Figure 5: Class Diagram

13
3.3.3 Sequence Diagram

Figure 6: Sequence Diagram

14
4 Chapter 4: System Design

4.1 System Architecture

Figure 7: System Architecture

15
4.2 Algorithm Details
Steps
1. Check whether the user is already registered or not. If not then goto Step 2 else goto
Step 3.
2. Register the user then authenticate details and goto Step 3.
3. Ask for login credentials.
4. Users send request for blood with details attached.
5. System will send notification to nearest doners and blood bank using the location
provided by user.
6. Availability of doner or blood in blood bank is confirmed.
7. Availability check.
a) If doner is near and available then doner will confirm its availability and that
request will be closed for others else it will search for next doner if not available.
b) If blood is available in blood bank, then blood bank will confirm availability and
that request will be closed for others else if will keep on searching for next nearest
blood bank.
8. If doner is available then doners details will be send to user and if blood available
then blood bank then blood bank details will be sent to user.
9. Stop

16
5 Chapter 5: Implementation and Testing

5.1 Implementation
We require different resources to implement the blood bank management system effectively.
Various hardware and software have been used in this project. All the resources used for
implementation are included in the table below:

Software used for system implementation:

Table 1: Software used for System Implementation

Software Description
VS Code Used as lightweight source code editor for
Node.js and React during development and
testing.
Windows 11 To operate the system

Hardware used for system implementation:

Table 2: Hardware used for system implementation

Hardware Description
Personal computer with 8 GB RAM and 1 For development and testing
TB hard disk space

5.1.1 Tools Used

a) Node.js: Node.js is a runtime environment that allows developers to run JavaScript
code outside of a web browser. It is built on the V8 JavaScript engine, primarily used
for server-side programming, enabling efficient, event-driven, and non-blocking I/O
operations. Node.js facilitates scalable and real-time applications by leveraging its
lightweight and asynchronous architecture.
b) React: React is a JavaScript library that simplifies the creation of interactive user
interfaces by breaking them into reusable components. It uses a declarative syntax and
efficiently updates and renders components when data changes. React's virtual DOM

17
 enables high performance by minimizing direct DOM manipulation. It is widely used
for building single-page applications and dynamic web interfaces due to its flexibility
and scalability.
c) Visual Studio Code: VS Code, short for Visual Studio Code, is a free and open-source
source code editor developed by Microsoft. It supports multiple programming
languages and provides features such as syntax highlighting, code completion,
debugging support, and version control integration (e.g., Git). VS Code is highly
customizable through extensions, allowing developers to tailor their editing
environment to suit different programming workflows and preferences. It has gained
popularity for its speed, ease of use, and extensive ecosystem of extensions and plugins
contributed by the community.
d) Draw.io: Draw.io is a UML CASE Tool supporting UML 2, SysML, and Business
Process Modeling Notation (BPMN) from the Object Management Group. It is free,
open-source online diagramming and flowchart tool. Flowcharts, block diagrams, ER
diagrams, DFD can be made using this tool.
e) Microsoft Office: Microsoft Office is a collection of productivity programs developed
by Microsoft for Windows, macOS, iOS, and Android operating systems. A variety of
word processing, presentation building, email and calendaring, note-taking, and other
tools are included in the suite. The most popular applications in Microsoft Office
include Microsoft Word, Microsoft Excel, Microsoft PowerPoint etc.

5.2 Testing
In order to detect errors in our program, testing was done. This method helps to improve the
application’s quality while maintaining expenses, enhancing accuracy in record-tracking and
maintenance time. Application testing guarantees the correct operation of a specific program
or application.

In this iterative process, we evaluated the performance of our application by thoroughly

inspecting how well the system meets its requirements and intended purpose. We organized the
testing into groups of three people, with each member assigned a specific task. One member
was responsible for the donor task, where they observed the system's response after a donor
accepted a request sent by a user. This included verifying that the system correctly canceled

18
other potential donors and informed the blood bank that additional donors were no longer
needed. Similarly, the person assigned to the blood bank task checked the system's functionality
after the blood bank accepted a request. This involved ensuring that the system sent appropriate
notifications and confirmed that no further donors were required. This structured approach
allowed us to comprehensively test and validate the system's performance in various scenarios.

19
6 Chapter 6: Conclusion and Future Recommendation

6.1 Conclusion
The Project “Blood Bank Management System (BBMS)” implementation is essential for
efficient blood donation and transfusion management. It enhances accuracy in record-
keeping, traceability of blood products, and operational efficiency. Key benefits include real-
time inventory tracking to maintain optimal stock levels, improved donor and recipient
management, regulatory compliance through automated reporting, and secure handling of
sensitive information. Overall, BBMS reduces human error, streamlines processes, and
ensures the availability of blood during emergencies.

6.2 Future Recommendation

To enhance blood bank operations, it is crucial to integrate with national health information
systems for seamless data interoperability and real-time data sharing across healthcare
providers. Developing user-friendly mobile and web applications can enhance donor
engagement, provide real-time updates, and simplify donation scheduling. Implementing
targeted awareness campaigns and community outreach programs will educate the public on
the importance of blood donation and encourage regular participation. Continuous training
and support for staff are essential to ensure proficiency in using the BBMS and staying
updated with the latest features and best practices.

Additionally, developing and regularly updating emergency preparedness plans will ensure a
swift and effective response to blood supply demands during crises or disasters. By focusing
on these recommendations, blood banks can enhance operations, ensure a reliable supply of
safe blood products, and ultimately save more lives.

20
 References

Harshil Darji. (April 18, 2014). Slideshare [online]

https://www.slideshare.net/slideshow/blood-bank-management-system-
including-uml-diagrams/33680362

Hamro LifeBank. [online] https://hamrolifebank.com/

ResearchGate (May8 8, 2023), Blood Bank Management System [online]:

https://www.researchgate.net/publication/370602395_Blood_Bank_Managemen
t_System

S. Sulaiman. (2015) Science Direct.com:

https://www.sciencedirect.com/science/article/pii/S1877042815036940/pdf?md
5=37f01f16137d20d31dcd69d71cc16209&pid=1-s2.0-S1877042815036940-
main.pdf

Rachel Jude. Creately.com [online]

https://creately.com/diagram/example/jlz9dn2i1/blood-bank-sequence-diagram-
classic

21