TRADE PROJECT

TITTLE: ELDORET REGIONAL BLOOD BANK MANAGEMENT

SYSTEM

OL’LESSOS TECHNICAL TRAINING INSTITUTE

P.O BOX 210, LESSOS

PRESENTED BY: RAHAB CHEPTOO

INDEX NO: 510010160

CENTER CODE: 541001

PAPER NO: 308

COURSE CODE: 2920

COURSE NAME: DIPLOMA IN INFORMATION AND COMMUNICATION

TECHNOLOGY

DEPARTMENT: ICT DEPARTMENT.

PRESENTED TO: THE KENYA NATIONAL EXAMINATION COUNCIL IN

PARTIAL FULLFILLMENT FOR THE AWARD OF DIPLOMA

IN INFORMATION AND COMMUNICATION TECHNOLOGY.

SUPERVISOR: MR. ABRAHAM LAGAT

SERIES: NOVEMBER 2024

DECLARATION
I declare that this Project is based on my original production, research and findings and has not been
published or submitted for any other award in this institution or elsewhere. Where information is not
my option, I have endeavored to dully attribute.

NAME:

Signature: ……………………………………….

Date: …………………………………………….

SUPERVISOR:

Signature: ……………………………………….

Date: …………………………………………….

i
DEDICATION
I dedicate this piece of my work to my family, relatives, teachers, community and my fellow students
for their patients and moral support.

ii
iii
ACKNOWLEDGEMENT
First and foremost, I take this opportunity to convey my appreciation to God for maintaining
conducive environment for me to come with this project. A special compliment to my supervisor,
who worked tirelessly with me, providing meaningful criticism and thoughtful comments that greatly
contributed to the completion of this project, despite the challenging moments during research. I also
thank teachers for their support and patient in ensuring this project was successful. Not forgetting the
full support of my fellow ICT students who offered their guiding to the success of this project. Last
but not least, am indebted to my family members my siblings for their encouragement and support
during my study. Almighty God blesses you all.

iv
ABSTRACT

Blood transfusion safety is a relevant and significant public health issue in the country. Since most
blood banks are still in paper-based system, various disadvantages are experienced by various
stakeholders, which endanger the lives of patients and deter the healthcare system. As such, the
research aimed to design, develop, and implement an online Blood Bank Management System.

The purpose of the project entitled as “ELDORET REGIONAL BLOOD BANK MANAGEMENT
SYSTEM” is to computerize the management of Hospital Blood Transfusion Center to develop
software which is user friendly simple, fast, and cost – effective. It deals with the collection of
patient’s information and details, etc. Traditionally, it was done manually. The main function of the
system is register and store donors’ details and doctor details and retrieve these details as and when
required, and also to manipulate these details meaningfully system input contains patient details,
donors’ details, while system output is to get these details on to the screen. Also, processes involving
recording about blood donors, blood bag collection, storage, and inventory will be systematized and
organized, hence, improving the healthcare management for blood banks.

v
 TABLE OF CONTENTS
DECLARATION.................................................................................................................................i

DEDICATION....................................................................................................................................ii

ACKNOWLEDGEMENT.................................................................................................................iii

ABSTRACT.......................................................................................................................................iv

CHAPTER ONE.................................................................................................................................................1

1.0 Introduction..........................................................................................................................................1

1.1 Background study.................................................................................................................................1

1.2 Problem Statement................................................................................................................................2

Speed of retrieving data......................................................................................................................2

Information insecurity........................................................................................................................2

Data errors and redundancy................................................................................................................2

Mismanagement of records.................................................................................................................2

1.3 Objectives of the Study.........................................................................................................................3

1.4 Scope of the Study................................................................................................................................3

1.4.1 Assumptions and Hypothesis.............................................................................................................3

1.5 limitations of the study.........................................................................................................................4

1.6 Justification of the system.....................................................................................................................4

1.7 RESEARCH QUESTIONS..................................................................................................................5

1.8 ORGANIZATION OF THE REPORT.................................................................................................5

1.9 Definition of terms................................................................................................................................5

CHAPTER TWO................................................................................................................................................7

Literature Review.......................................................................................................................................7

2.0 INTRODUCTION................................................................................................................................7

2.1 Literature Review.................................................................................................................................7

2.2 HARDWARE REQUIREMENTS........................................................................................................8

MINIMUM HARDWARE REQUIREMENTS FOR PRESENT PROJECT:.............................................8

2.3 SOFTWARE REQUIREMENTS:........................................................................................................8

vi
 SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:..................................................................9

2.4 Conclusion............................................................................................................................................9

CHAPTER THREE..........................................................................................................................................10

Methodology.............................................................................................................................................10

3.0 Introduction........................................................................................................................................10

3.1 EXISTING SYSTEM.........................................................................................................................10

3.2 PROPOSED SYSTEM.......................................................................................................................10

3.3 FEASIBILITY STUDY......................................................................................................................11

3.3.1 Economic Feasibility......................................................................................................................11

3.3.2 Technical Feasibility.......................................................................................................................11

3.3.3 Operational Feasibility.....................................................................................................................12

3.4 CONCLUSION..................................................................................................................................12

CHAPTER FOUR............................................................................................................................................13

IMPLEMENTATION AND DOCUMENTATION OF THE SYSTEM...................................................13

4.0 System design.....................................................................................................................................13

Database...........................................................................................................................................14

4.1 DESIGN OF PROPOSED SYSTEM..................................................................................................14

4.2 IMPLEMENTATION.........................................................................................................................15

4.3 PROGRAM DOCUMENTATION.....................................................................................................15

DOCUMENTATION OF THE SYSTEM................................................................................................15

4.4 OPERATING THE SYSTEM............................................................................................................15

4.5 MAINTAINING THE SYSTEM........................................................................................................15

CHAPTER FIVE..............................................................................................................................................16

5.0 System Analysis and requirements....................................................................................................16

5.1 Results Of the New Proposed System.................................................................................................16

5.2 Analysis..............................................................................................................................................17

System Error Handling.............................................................................................................................17

vii
 5.3 System Test:.......................................................................................................................................17

Features to be tested..................................................................................................................................17

Integration Testing....................................................................................................................................18

5.4 File and system maintenance..............................................................................................................18

CHAPTER SIX................................................................................................................................................20

SUMMARY, CONCLUSIONS & RECOMMENDATIONS...................................................................20

6.0 Summary.............................................................................................................................................20

6.1 Conclusion..........................................................................................................................................20

6.2 Recommendations...............................................................................................................................20

6.3 References..........................................................................................................................................21

viii
CHAPTER ONE
1.0 Introduction
Blood transfusion safety remains an important public health concern in Kenya. The availability of
blood products of all blood types and the provision of its safety ensure public trust of its excellent
healthcare system. However, lack of availability of these blood products and provision of unsafe
blood products still impacts morbidity and mortality. Through the use of Blood Bank Management
System, blood transfusion safety is expected to be enhanced or improved. Risks on improper blood
donors’ documentation, and misplaced records can be minimized or totally avoided. Also, processes
involving blood bag collection, storage, and inventory will be systematized and organized, hence,
improving the healthcare management.

1.1 Background study

For hospitals, a blood bank known as blood collection center, also is an area in which collected blood
bags are stored and preserved for future use in blood transfusion services. Blood transfusion is a
medical operation where a patient requires blood or blood products as a life saving measure.

Most blood banks are still running manual system in its processes. As such, there is a lack of
efficiency because it is still paper-based in collecting information about donors, inventories of blood
bags, and blood transfusion services. The lack of proper documentation may endanger patients’
health due to the possibility of having contaminate blood bags. All this work is done manually by the
receptionist and other operational staff and lot of papers are needed to be handled and taken care of.

The Blood Bank currently uses the following methods;

-manual registration of blood donors

-allocation of blood takes time

-recording donor details manually

Page 1
1.2 Problem Statement

Despite advances in technology, nowadays, most blood bank systems are

running in manual system. As such, there is a prevalent problem in the
availability of needed blood types.

The current system undergoes different problems. The proposed software is intended to address the
following problems in the Blood Bank;

-speed of retrieving data.

-information insecurity

- data redundancy and errors

-mismanagement of donor records

Speed of retrieving data

It normally takes a long time for one to receive blood transfusion. This is because the organization
takes long to acquire the information of the applicant in physical files one by one which is tiresome
and takes a lot of time.

Information insecurity
- Data is normally stored in books which are not well kept this gives a chance to malicious people to
access the information. In case of a fire or theft the information will be lost thus endangering the
blood bank’s operations.

Data errors and redundancy

Data can be interfered or altered by the books of accounts and those of those of applicants of blood
transfusion in that the figures entered maybe interchanged making an error.

Mismanagement of records
-Its makes it hard to trace records lost by the organization since it is not clear records are altered
since one person is managing the blood donor records of the blood bank in a written record which
can be altered hence mismanagement of records.

Page 2
1.3 Objectives of the Study

1. Enhance data security: - The proposed system will be secure and accurate because there will be a
creation of a database that is going to store all information, there is going to have access control
methods whereby each user will have access to the database according to his rights and each user
will have a unique password that he/she will use to access the system.

2. Enhance customer satisfaction - Patients and Donors will be served fast, accurate and will not
wait for long this will make them trust more in the blood bank hence bringing a good relationship
between them and the blood bank thus enhancing good relation.

3. Data accuracy: - The proposed blood bank system will enable the system users easily input data
into the system fast and accurate this will be facilitated with the validation feature of the system
hence enabling them work efficiently thus saving time.

4. Quick system operations: - The proposed system will enhance the speed of carrying out all
activities this is because computers processing capabilities are fast as to compared to human beings.

1.4 Scope of the Study

Registration of members

Blood group allocation

Blood transfusion application

Tracing the records

Blood bank management plans

1.4.1 Assumptions and Hypothesis

The researchers assume the following assumptions:

Internet connectivity is needed for the online blood management system. Internet speed may affect
the perception of the systems users with regards to the system effectiveness and efficiency.

Blood transfusion should be performed by medical or professional doctors only. The over-all safety
depends on the success of the medical operation.

Page 3
The researchers identify the following hypotheses:

There is a significant difference in the level of blood transfusion safety between manual-based and
online blood bank systems.

There is an increased level of blood transfusion safety in using online blood bank management
systems while there is an increased risk when using manual-based one.

1.5 limitations of the study

Resistance: - It isn’t easy to get the information from the individuals this is because they have a
doubt that the system was going to deny some of jobs due to reduction of manpower.

Costly: - A lot of money was spent in transport that is from home to the offices of the company, also
had to buy books and other stationery to facilitate the study.

Time consuming: - It is time consuming to conduct the study especially when gathering the
information about the system it took me a lot of time to convince the staff of a blood bank to give the
correct information.

1.6 Justification of the system

Easy and cheap to maintain- once the system has been fully implemented it will need minimal
maintenance which will be cheap as compared to the current manual system.

Accuracy of work- Because of the data entered is going to be accurate and correct.

Data security- Information will be secured as compared to the current system since there is personal
user passwords to access the system.

Fast Speed- The system will run in great speed especially in accessing patients and donor data and
information also processing calculations hence enabling fast operations.

Page 4
1.7 RESEARCH QUESTIONS

1) Define blood transfusions

2) Recording information about the donors that come.
3) Generating reports.
4) Recording information related to diagnosis given to patients.
5) Keeping record of the blood types.

Keeping information about various blood types and donors available to give blood.

1.8 ORGANIZATION OF THE REPORT

This work is organized in such a way that the reader can easily understand it.

Chapter one discusses the general introduction and overview of the whole project. It is based on the
introduction, the definition of the problem, the purpose of the study, the aim and objectives of the
study.

Chapter two is concerned with the literature review. It reviews past work done to the project,
historical background to the study and discussed on related aspect of the project topics related.

Chapter three discusses about the description and analysis of the existing system. Also gives the
description of the existing system and its problems and the description of the proposed system and
possible advantages it will provide that will solve the problems encountered in the existing manual
system.

Chapter four talks about the design of the new system. It covers description of the output design,
input design, database design and procedure design. The implementation method used, the
programming language used and system requirement for running the system.

Chapter five is about the implementation of the new system that has been designed and its
documentation. Also presents the conclusion, recommendation and references.

1.9 Definition of terms

Page 5
Blood bags: are designed for the collection, processing and storage of whole blood and blood
components They help in providing aseptic conditions for the separation of blood components. It acts
as a closed system reducing the chances of contamination.

Blood bank: is a place where blood bags that are collected from blood donation events is stored in
one place. Which refers to a division of a hospital laboratory where the storage of blood product
occurs and where proper testing is performed to reduce the risk of transfusion related events.

Donor: is someone who gives a part of their body or some of their blood to be used by doctors to
help a person who is ill and needs a transfusion.

Transfusion: transfusion is done as a lifesaving maneuver to replace blood cells or blood products
lost through severe bleeding. Transfusion of one's own blood (autologous transfusion) is the safest
method, but it requires advanced planning, and not all patients are eligible.

Page 6
CHAPTER TWO

Literature Review

2.0 INTRODUCTION

This work does not look in the direction of an offline system that will save the technicality demands
and cost requirements of an online system. It deals with the collection of patient’s information,
blood details, etc. Traditionally, it was done manually. The main function of the system is register
and store donor details and doctor details and retrieve these details as and when required, and also to
manipulate these details meaningfully system input contains patient details, donation details, while
system output is to get these details on to the screen.

Instant use of the system is a fast and effective way to make sure all Doctors and staff working at the
blood bank have the proper identification and their information is stored well. Other systems require
time for processing and printing.

2.1 Literature Review

The system allows an authorized blood bank administrator to sign in with a password to manage
easily the records of donors and patients who need blood. The system provides many features
including the central database, quick access to the system content through the login, includes the
search code to find donors on a given basis, and the ease of adding and updating donor data. The
main aim of the system was to complete the process of the blood bank. This system was designed to
suit all types of blood banks. Once successful in the implementation of the application, it can be
applied and rolled out in several blood banks. This application contains User Login Screen, Blood
Management, Menu Form, Blood Stock, Donor Management, Donor Registration, Blood
Reservation, Donor Blood Test, Recipient Management and Blood Reservation. In similar manner,
the researchers planned in their application to have hospital administrator, doctors, and blood bank
receptionists as users.

Page 7
Based on this study, since entering the details about the blood donors and related records were done
manually, thus, tracking of blood donation activities was difficult and complicated, and even led to
erroneous information.

In the study it is found out that it is important for every hospital to use an information system to
manage data in blood bank. Also, it observed that the manual system has disadvantages for the user
and the hospital. One of the disadvantages identified was the blood bank staff should enter the donor
details in each time he/she donates blood in which led to duplicate data of the donor and also the data
may be lost or missing after period of time.

2.2 HARDWARE REQUIREMENTS

The most common set of requirements defined by any operating system or software application is the
physical computer resources, also known as hardware. A hardware requirements list is often
accompanied by a hardware compatibility list, especially in case of operating systems. Lists tested,
compatibility and sometimes incompatible hardware devices for a particular operating system or
application. The following sub-sections discuss the various aspects of hardware requirements.

MINIMUM HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

PROCESSOR : Intel dual Core ,i3

RAM : 2 GB

HARD DISK : 250 GB

2.3 SOFTWARE REQUIREMENTS:

Software Requirements deal with defining software resource requirements and pre-requisites that
need to be installed on a computer to provide optimal functioning of an application. These

Page 8
requirements or pre-requisites are generally not included in the software installation package and
need to be installed separately before the software is installed.

SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

OPERATING SYSTEM : Windows 7/ XP/ 8/ 10

FRONT END : HTML, CSS, Java Script.

SERVER SIDE SCRIPT : PHP

DATABASE : MySQL

2.4 Conclusion

The purpose of these literature reviews was to collect information on how an information system
helped the management of blood banks. Based on the reviews, it was found out that web-based blood
bank systems provide convenience, efficiency and security to the system users and hospitals
compared to the manual systems. It was found out that manual systems have many disadvantages
that disappoint and dissatisfy users. Indeed, online blood bank management system applications
make work easy, and ensures fast retrieval of data when needed.

Page 9
CHAPTER THREE

Methodology

3.0 Introduction
The researchers used both descriptive research and experimental research design methods. The study
was descriptive because it describes the nature of situation as it exists at the time of the study. Also,
it was a systematic and scientific approach to research in which the researchers manipulate one or
more variables, and control and measure any change in other variables. It involves collection of data
in order to test hypotheses or to answer questions concerning current status of the subject of the
study. The study was also experimental because it has an assumption of a cause-and-effect
relationship, and the researchers introduce blood bank management system as intervention that
caused the change.

During the study I used different research methods to acquire information. These methods are;

- Interview

- Questionnaire

- Observation

3.1 EXISTING SYSTEM

Blood Banks currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper forms, with data stores spread throughout
the blood bank management infrastructure. Often information is incomplete or does not follow
management standards. Forms are often lost in transit between departments requiring a
comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the
same information exist in the blood bank and may lead to inconsistencies in data in various data
stores.

3.2 PROPOSED SYSTEM

Page 10
The Blood Bank Management System is designed for any blood bank to replace their existing
manual paper-based system. The new system is to control the information of patients and donors.
Room availability, staff and donation room schedules and patient invoices. These services are to be
provided in an efficient, cost-effective manner, with the goal of reducing the time and resources
currently required for such tasks.

3.3 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth with a very
general plan for the project and some cost estimates. During system analysis the feasibility study of
the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to
the blood bank. For feasibility analysis, some understanding of the major requirements for the system
is essential.

Three key considerations involved in the feasibility analysis are:

3.3.1 Economic Feasibility

This study is carried out to check the economic impact will have on the system will have on the
blood bank. The amount of fund that the blood bank can pour into the research and development of
the system is limited. The expenditures must be justified. Thus the developed system as well within
the budget and this was achieved because most of the technologies used are freely available. Only
the customized products have to be purchased.

3.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is, the technical requirements of the
system. Any system developed must not have a high demand on the available technical resources.
This will lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes for the implementing this system.

Page 11
3.3.3 Operational Feasibility
The aspect of study is to check the level of acceptance of the system by the user. This includes the
process of training the user to use the blood bank system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the users
solely depends on the methods that are employed to educate the user about the system and to make
him familiar with it. His level of confidence must be raised so that he is also able to make some
constructive criticism, which is welcomed, as he is the final user of the system.

3.4 CONCLUSION

This chapter gives and insight into how data was collected despite the various problems outlined
above, adequate information was gathered to facilitate the understanding of how information is
managed at the blood bank. The methods used are not mutually exclusive, a combination of term was
used to elicit more data at the same time. In this study, the researchers used questionnaire to collect
information and to obtain the perception of the various stakeholders on how they perceive the
manual-based system and the online system. The questionnaire was administered to hospital
administrators, doctors, and blood bank receptionists.

Page 12
 CHAPTER FOUR

IMPLEMENTATION AND DOCUMENTATION OF THE SYSTEM

4.0 System design

The Blood bank management system has a database to store the data entered and extracted from
various sources, procedures to access the database and an interactive user interface to allow users
effectively communicate with the system and input their own insight.

The system is flexible and adoptable its able to respond to the change of environment and the needs
of its users.

The system has the following major components:

1. Client application

2. Server application

3. Database.

Client Side

HTML elements form the building blocks of all websites. HTML allows images and objects to be
embedded and can be used to create interactive forms. It provides a means to create structured
documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes
and other items. It can embed scripts written in languages such as JavaScript which affect the
behavior of HTML web pages.

Below are sample screenshots of the developed system:

Page 13
 ELDORET ELDORET
ELDORET ELDORET
ELDORET ELDORET

Samples from other hospitals

Test information

ELDORET ELDORET ELDORET

ELDORET

Sent requests page

Server Side (backend)

With PHP you are not limited to output HTML. You can output images, PDF files, and even Flash
movies. You can also output any text, such as XHTML and XML. JavaScript is the scripting
language of the Web. All modern HTML pages are using JavaScript. A scripting language is a
lightweight programming language. JavaScript code can be inserted into any HTML page, and it can
be executed by all types of web browsers. JavaScript is easy to learn.

Page 14
Dashboard

Home page

Page 15
Database
-The database contains basic information used to access loan applications some of this information
includes;

LOCALIZATION:
 The server can provide error messages to clients in many languages.
 All data is saved in the chosen character set.
CLIENTS AND TOOLS:

MySQL includes several client and utility programs. These include both command-line programs
such as MySQL dump and MySQL, and graphical programs such as MySQL Workbench.

Provides the user with an interface between him /her and the database, this facilitates interaction
between the user and the database. the front end has been developed visual basic.net framework.

4.1 DESIGN OF PROPOSED SYSTEM

The blood bank management system is developed using PHP and MySQL for the back-end database.

Page 16
4.2 IMPLEMENTATION
This is the process of putting the system fully into function. The system basically runs on p.c
computers.

The change over system used was the parallel system whereby the new system is run parallel with
the old system until the users are able to comfortably use the new system that’s when the old system
will be completely shut down.

4.3 PROGRAM DOCUMENTATION

DOCUMENTATION OF THE SYSTEM

This is the detailed description of the proposed system. It’s important because it helps to design and
implement a system that would allow generating of patient information to be performed on the
system.

4.4 OPERATING THE SYSTEM

Step 1: Boot your computer and click on start button on the task bar

Step 2: Launch the Browser

Step 3: Open the Localhost server (Xampp)

Step 4: Run the software on localhost.

4.5 MAINTAINING THE SYSTEM

It is the process of identifying the product, component or a system subsequent to delivery or

installation that correct the faults, improve the system’s performance or other product attributes or
adapt product to a changed operational environment. It is the process of adjusting the system files
after delivery and while in use. This is a continuous process of refining and improving a system’s
functionality that sometimes goes back to the start of the System Design Life Cycle in an iterative
manner.

It is designed to support extensibility and maintainability.

Page 17
Page 18
CHAPTER FIVE

5.0 System Analysis and requirements

System analysis and requirement is the study of a system, its current and future required objectives
and procedures in order to form a basic for the system and the design. Since we are entering details
of the patients electronically in the” Blood Bank Management System”, data will be secured. Using
this application, we can retrieve patient’s history with a single click. Thus, processing information
will be faster. It guarantees accurate maintenance of blood donations details. It easily reduces the
book keeping task and thus reduces the human effort and increases accuracy speed.

5.1 Results Of the New Proposed System

i. The system provides good documentation about the blood donor and its blood donation activities

ii. The system can search fast the list of possible blood donors through its donors’ files.

iii. The system can clearly monitor the availability of blood bags or products of all blood types.

iv. The system has the ability to track to whom the blood bag/product has been given using the
patient record

v. The system allows user to know easily the period of expiration of blood bags/products.

vi. The system has the ability to generate medical reports or statistics easily.

vii. The system offers an organized and systematized filing or record system.

viii. The system provides easy to use, efficient, effective system to the users.

ix. The system allows user to know easily if the person donate blood for the last 3 months.

Page 19
5.2 Analysis

The question of ability of providing good documentation about the donor and blood donation
activities was rated the lowest which implied that in most manual systems, most files or records have
the tendencies of being either misplaced or lost. Though respondents rated the ability of the system
to generate reports the highest criterion in the manual system, still the result showed that respondents
felt that report generation in manual-system is time-consuming, and laborious. The results showed
that the respondents did not agree nor disagree on the ability of the manual-based system on its
efficiency and effectiveness.

agreed that the online system can provide good documentation about donor and its donor activities,
monitoring of blood bags availability, tracking of issued blood bags, identification of expired blood
bags, report generation, system efficiency and effectiveness, organized and systematized record
system, to name a few. Respondents rated the ability of online system to know period of expiration
of blood bags as the highest criterion while the ability of online system to offers systematized and
organized filing or record system was rated the lowest criterion.

System Error Handling

During coding, some error handlers were included which helped to locate the errors which were
present or occurring in the system. In this system the error handle used is “ON ERROR RESUME
NEXT”, which looks for errors step by step and if in a line there is no error, it goes to the next line
and start looking for errors until it reaches the last line. This is done in all the forms used, during
coding.

5.3 System Test:

System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the
configuration-oriented system integration test. System testing is based on process descriptions and
flows, emphasizing pre-driven process links and integration points.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed

Page 20
  All links should take the user to the correct page.

Integration Testing
Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects.

The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.

5.4 File and system maintenance

It is the process of identifying the product, component or a system subsequent to delivery or

installation that correct the faults, improve the system’s performance or other product attributes or
adapt product to a changed operational environment. It is the process of adjusting the system files
after delivery and while in use. This is a continuous process of refining and improving a system’s
functionality that sometimes goes back to the start of the System Design Life Cycle in an iterative
manner. Changes which may be involved include:

A] Simple changes to correct the coding errors

B] More extensive changes to correct design errors

C} Significant enhancement to correct design errors or accommodate new requirements

Types of software for system maintenance

Adaptive maintenance - It concerned with changes that aim at introducing new things to the
system. These changes emerge throughout the system as a result in changes in the teaching process.

Perfective maintenance- Attempts to make the system perform more effectively. Changes may
include alteration of user interface and integration of new sub routines into the system.

Preventive maintenance- it involves anticipation of errors that uses may perform on the system
after it has been put to use.

Page 21
Corrective maintenance- problems always surface after a system has been in use for a short time.
Some part of the system may not function as expected, or a report may be wrong in some way,
incorrect sequence of data and wrong headings which may call for correction.

Page 22
CHAPTER SIX

SUMMARY, CONCLUSIONS & RECOMMENDATIONS

6.0 Summary

The research conducted applied to examine and evaluate on how the blood bank management system
can enhance blood transfusion safety. The researchers aimed to design and implement this system.
The research used both descriptive and experimental design methods. The research floated and
administered questionnaires to hospital administrators, doctors, and blood bank receptionists from
the various hospitals. Further, based on the gathered data, means, standard deviations, and values
were computed. Based on the findings and results, conclusions and recommendations were made.

6.1 Conclusion

Based on results, this study concluded that blood bank management system is much better than the
manual system. The findings showed that respondents prefer to use the blood bank management
system rather than the manual system because it offers many advantages and benefits that lead to its
effectiveness, and efficiency. Because of the increased confidence on the users on the system, it can
be concluded that the blood bank management system enhances blood transfusion safety because it
provides better ways of handling the various processes in blood bank.

6.2 Recommendations

In view of the findings, the research recommends that implementation of blood bank management
system. Further, the research recommends that further studies on how blood bank management
system enhances blood transfusion safety can be undertaken to strengthen this study’s findings. This
requires actual implementation of the system and evaluates how the users respond after
implementation. This study recommends that it should be roll out across blood banks. Likewise, to
ensure that there will be better user engagement, user manuals and proper user training should be
given. Lastly, this study recommends that the system can be expanded by allowing donors to register

Page 23
online and be a system user, and these donors will be informed about the planned blood donation
activities through the online system.

6.3 References

1. Voluntary blood donations rising in Oman. (2024). Retrieved from

https://timesofoman.com/article/43536

2. Teena, C.A, Sankar, K. and Kannan, S. (2024). A Study on Blood Bank Management.

Retrieved from https://www.idosi.org/mejsr/mejsr19(8)14/21.pdf

3. Kumar, R., Singh, S. and Ragavi, V.A. (2024).). Blood Bank Management System. Retrieved

from http://ijariie.com/AdminUploadPdf/Blood_Bank_Management_System_ijariie6874.pdf

4. Liyana, F. (2024). Blood Bank Management System Using Rule-Based Method. Retrieved
from http://greenskill.net/suhailan/fyp/report/038077.pdf

Page 24
APPENDIX

SOURCE CODE

LOGIN

<!DOCTYPE html>

<html>

<?php $title="Bloodbank | Login"; ?>

<?php require 'head.php'; ?>

<body>

<?php require 'header.php'; ?>

<div class="container cont">

<?php require 'message.php'; ?>

<div class="row justify-content-center">

<div class="col-lg-4 col-md-5 col-sm-6 col-xs-7 mb-5">

<div class="card rounded">

<ul class="nav nav-tabs justify-content-center bg-light" style="padding: 20px;">

<li class="nav-item">

<a class="nav-link active" data-toggle="tab" href="#hospitals">Hospitals</a>

</li>

<li class="nav-item">

<a class="nav-link" data-toggle="tab" href="#receivers">Receiver's</a>

</li>

</ul>

<div class="tab-content">

<div class="tab-pane container active" id="hospitals">

<form action="file/hospitalLogin.php" method="post">

<label class="text-muted font-weight-bold" class="text-muted font-weight-bold">Hospital Email</label>

Page 25
 <input type="email" name="hemail" placeholder="Hospital Email" class="form-control mb-4">

<label class="text-muted font-weight-bold" class="text-muted font-weight-bold">Hospital Password</label>

<input type="password" name="hpassword" placeholder="Hospital Password" class="form-control mb-4">

<input type="submit" name="hlogin" value="Login" class="btn btn-primary btn-block mb-4">

</form>

</div>

<div class="tab-pane container fade" id="receivers">

<form action="file/receiverLogin.php" method="post">

<label class="text-muted font-weight-bold" class="text-muted font-weight-bold">Receiver Email</label>

<input type="email" name="remail" placeholder="Receiver Email" class="form-control mb-4">

<label class="text-muted font-weight-bold" class="text-muted font-weight-bold">Receiver Password</label>

<input type="password" name="rpassword" placeholder="Receiver Password" class="form-control mb-4">

<input type="submit" name="rlogin" value="Login" class="btn btn-primary btn-block mb-4">

</form>

</div>

</div>

<a href="register.php" class="text-center mb-4" title="Click here">Don't have account?</a>

</div>

</div>

</div>

</div>

<?php require 'footer.php' ?>

</body>

</html>

<?php } ?>

Page 26
REGISTER

<!DOCTYPE html>

<html>

<?php $title="Bloodbank | Register"; ?>

<?php require 'head.php'; ?>

<body>

<?php include 'header.php'; ?>

<div class="container cont">

<?php require 'message.php'; ?>

<div class="row justify-content-center">

<div class="col-lg-4 col-md-5 col-sm-6 col-xs-7 mb-5">

<div class="card rounded">

<ul class="nav nav-tabs justify-content-center bg-light" style="padding: 20px">

<li class="nav-item">

<a class="nav-link active" data-toggle="tab" href="#hospitals">Hospitals</a>

</li>

<li class="nav-item">

<a class="nav-link" data-toggle="tab" href="#receivers">Receivers</a>

</li>

</ul>

<div class="tab-content">

<div class="tab-pane container active" id="hospitals">

<form action="file/hospitalReg.php" method="post" enctype="multipart/form-data">

<input type="text" name="hname" placeholder="Hospital Name" class="form-control mb-3" required>

<input type="text" name="hcity" placeholder="Hospital City" class="form-control mb-3" required>

<input type="tel" name="hphone" placeholder="Hospital Phone Number" class="form-control mb-3" required

pattern="[0,6-9]{1}[0-9]{9,11}" title="Password must have start from 0,6,7,8 or 9 and must have 10 to 12 digit">

Page 27
 <input type="email" name="hemail" placeholder="Hospital Email" class="form-control mb-3" required>

<input type="password" name="hpassword" placeholder="Hospital Password" class="form-control mb-3"

required minlength="6">

<input type="submit" name="hregister" value="Register" class="btn btn-primary btn-block mb-4">

</form>

</div>

<div class="tab-pane container fade" id="receivers">

<form action="file/receiverReg.php" method="post" enctype="multipart/form-data">

<input type="text" name="rname" placeholder="Receiver Name" class="form-control mb-3" required>

<select name="rbg" class="form-control mb-3" required>

<option disabled="" selected="">Blood Group</option>

<option value="A+">A+</option>

<option value="A-">A-</option>

<option value="B+">B+</option>

<option value="B-">B-</option>

<option value="AB+">AB+</option>

<option value="AB-">AB-</option>

<option value="O+">O+</option>

<option value="O-">O-</option>

</select>

<input type="text" name="rcity" placeholder="Receiver City" class="form-control mb-3" required>

<input type="tel" name="rphone" placeholder="Receiver Phone Number" class="form-control mb-3" required

pattern="[0,6-9]{1}[0-9]{9,11}" title="Password must have start from 0,6,7,8 or 9 and must have 10 to 12 digit">

<input type="email" name="remail" placeholder="Receiver Email" class="form-control mb-3" required>

<input type="password" name="rpassword" placeholder="Receiver Password" class="form-control mb-3"

required minlength="6">

<input type="submit" name="rregister" value="Register" class="btn btn-primary btn-block mb-4">

</form>

</div>

Page 28
 </div>

<a href="login.php" class="text-center mb-4" title="Click here">Already have account?</a>

</div>

</div>

</div>

</div>

<?php require 'footer.php' ?>

</body>

</html>

<?php } ?>

Blood info

<!DOCTYPE html>

<html>

<?php $title="Bloodbank | Add blood samples"; ?>

<?php require 'head.php'; ?>

<body>

<?php require 'header.php'; ?>

<div class="container cont">

<?php require 'message.php'; ?>

<div class="row justify-content-center">

<div class="col-lg-4 col-md-5 col-sm-6 col-xs-7 mb-5">

<div class="card">

<div class="card-header title">Add blood group available in your hospital</div>

<div class="card-body">

<form action="file/infoAdd.php" method="post">

<a data-toggle="collapse" href="#collapseExample" role="button" aria-expanded="false" aria-

controls="collapseExample" title="click to see">Term & conditions. </a><br>

<div class="collapse" id="collapseExample">

Page 29
 If you have a blood sample tested by your doctor’s, nurse, or trained phlebotomist, at a pathology collection
center, clinic or hospital. Blood samples are most commonly taken from the inside of the elbow where the veins are
usually closer to the surface. If before the needle is inserted, the area had been cleaned with an antiseptic cloth and
blood sample is transferred into tubes containing the correct preservatives then add your blood group available in
your hospital to your blood bank. <br><br>

</div>

<input type="checkbox" name="condition" value="agree" required> Agree<br><br>

<select class="form-control" name="bg" required="">

<option disabled selected>Blood Group</option>

<option>A-</option>

<option>A+</option>

<option>B-</option>

<option>B+</option>

<option>AB-</option>

<option>AB+</option>

<option>O-</option>

<option>O+</option>

</select><br>

<input type="submit" name="add" value="Add" class="btn btn-primary btn-block"><br>

<a href="index.php" class="float-right" title="click here">Cancel</a>

</form>

</div>

</div>

</div>

<?php if(isset($_SESSION['hid'])){

$hid=$_SESSION['hid'];

$sql = "select * from bloodinfo where hid='$hid'";

$result = mysqli_query($conn, $sql);

?>

<div class="col-lg-4 col-md-5 col-sm-6 col-xs-7 mb-5">

<table class="table table-striped table-responsive">

<th colspan="4" class="title">Blood Bank</th>

Page 30
 <tr>

<th>#</th>

<th>Blood Samples</th>

<th>Action</th>

</tr>

<div>

<?php

if ($result) {

$row =mysqli_num_rows( $result);

if ($row) { //echo "<b> Total ".$row." </b>";

}else echo '<b style="color:white;background-color:red;padding:7px;border-radius: 15px 50px;">Nothing

to show.</b>';

?>

</div>

<?php while($row = mysqli_fetch_array($result)) { ?>

<tr>

<td><?php echo ++$counter; ?></td>

<td><?php echo $row['bg'];?></td>

<td><a href="file/delete.php?bid=<?php echo $row['bid'];?>" class="btn btn-danger">Delete</a></td>

</tr>

<?php } ?>

</table>

</div>

</div>

</div>

<?php require 'footer.php' ?>

</body>

<?php } ?>

Page 31
BLOOD REQUEST

<!DOCTYPE html>

<html>

<?php $title="Bloodbank | Blood Requests"; ?>

<?php require 'head.php'; ?>

<body>

<?php require 'header.php'; ?>

<div class="container cont">

<?php require 'message.php'; ?>

<table class="table table-responsive table-striped rounded mb-5">

<tr><th colspan="9" class="title">Blood requests</th></tr>

<tr>

<th>#</th>

<th>Name</th>

<th>Email</th>

<th>City</th>

<th>Phone</th>

<th>Blood Group</th>

<th>Status</th>

<th colspan="2">Action</th>

</tr>

<div>

<?php

if ($result) {

$row =mysqli_num_rows( $result);

if ($row) { //echo "<b> Total ".$row." </b>";

}else echo '<b style="color:white;background-color:red;padding:7px;border-radius: 15px 50px;">No one

has requested yet. </b>';

?>

Page 32
 </div>

<?php while($row = mysqli_fetch_array($result)) { ?>

<tr>

<td><?php echo ++$counter;?></td>

<td><?php echo $row['rname'];?></td>

<td><?php echo $row['remail'];?></td>

<td><?php echo $row['rcity'];?></td>

<td><?php echo $row['rphone'];?></td>

<td><?php echo $row['bg'];?></td>

<td><?php echo 'You have '.$row['status'];?></td>

<td><?php if($row['status'] == 'Accepted'){ ?> <a href="" class="btn btn-success

disabled">Accepted</a> <?php }

else{ ?>

<a href="file/accept.php?reqid=<?php echo $row['reqid'];?>" class="btn btn-

success">Accept</a>

<?php } ?>

</td>

<td><?php if($row['status'] == 'Rejected'){ ?> <a href="" class="btn btn-danger

disabled">Rejected</a> <?php }

else{ ?>

<a href="file/reject.php?reqid=<?php echo $row['reqid'];?>" class="btn btn-

danger">Reject</a>

<?php } ?>

</td>

</tr>

<?php } ?>

</table></div>

<?php require 'footer.php'; ?>

</body>

</html>

<?php } ?>

Page 33