BLOOD DONATION SYSTEM

BLOOD DONATION MANAGMENT SYSTEM

CONTENTS
TITLE
PAGE
1. INTRODUCTION……………….……………..
……………………….…………….…………….…….2
2. OBJECTIVES……………………….………..
………………………………………………………..
…..3
3. IDENTUFING PROBLEMS……………………….
………..……………………………………….4
4. ENTITY TYPES AND R/SHIPS…………………..….
……….………………….………………5
5. ATTRIBUTES AND CONSTRAINTS………………..
…………….……………………………6
6. PRIMARY AND FOREIGN KEYS…….
…………………………………….……………….…..7
7. ER diagram……………………….………..
………………………………………………………..
…..8
8. NORMALIZATION……………………….………..
…………………………………………………….9
9. NORMALIZED TABLE……………………….………..
………………………………………………10
10. SUMMARY……………………….………..
………………………………………………………..
………13

Page | 1
BLOOD DONATION SYSTEM

1. INTRODUCTION
In our previous part of this project we tried to see the background information, the
objective, the drawbacks, system definition and requirement collection and analysis for our
blood bank management system. In this one, we will see the process of constructing an ER
model.

Since in the process of designing our ER model we discover a lot of new things that we
didn’t discover in our first project, we started this document with our modified user view
and modified requirement collection and analysis part. Then we will list our entity types
along with their descriptions and attributes. We will also see the relationship type that we
have between this entity types. Then we will classify our attributes in to primary, candidate
and alternate keys. We will also try to list the attribute domains. Next we will try to see if
any generalization or specialization method I used. At last the last part of our ER model will
be attached.

Page | 2
BLOOD DONATION SYSTEM

2. OBEJECTIVES
2.1 GENERAL OBEJECTIVE
The main purpose of this system is to keep an organize records management of blood
inventory. It would be a great help in the properly monitoring of blood available in the blood
bank and for easy processing of blood request.

2.2 SPECIFIC OBJECTIVES

This project got so many objectives specifically. Like
 If there is blood shortage or any other constraints give the blood to the more severe
case by looking at the status of the patients.
 It has a security layer that allows only authorized employees of the Blood bank to
access and update the records through a login using a secret password.
 Quality checking of blood at various levels is introduced. It is required for the safety
of the patients.
 Minimizes human error.
 Help blood bank supervisors to service inquiries and various blood recipients,
whether they are individual patrons or hospitals, with higher efficacy and attenuate
wastage.
 Tries to effectively bridge the gap between blood banks, donors and recipients by
creating effective databases and applications for all the three.
 To develop a system that provides functions to support donors to view and manage
their information conveniently.
 To maintain records of blood donors, blood donation information and blood stocks
in a centralized database system.
 To inform donors of their blood result after their donation.
 To support searching, matching and requesting for blood convenient for
administrators.
 To provide a function to send an e-mail directly to the donor for their user account
and the hospital, the availability of the blood bag
 The system uses a First-In-First-Out stock management, where the blood stock that
is checked-in to the system first will be the first one given to the hospital when
requested. When the blood stock is expired, the system can inform us.
 The system can generate a report to summarize all records including blood donation,
blood requests and blood stock for the administrator
 Reduces time consuming activities

Page | 3
BLOOD DONATION SYSTEM

3. IDENTIFING PROBLEMS
There are so many drawbacks on the existing system and because of this drawbacks the
users of blood donation system demand for a better system to emerge or take place. What
are the reasons or causes for this new system? The answer is easy, it is because of this
problems:
 Patients facing difficulty in tracing their donors
 Managers facing difficulty in managing blood bank accounts
 Addressing the efficiency of doing transactions in Hospitals
 The existing system is time consuming
 No inquiry for directly contacting Blood bank
 User view of Blood bank information is not location dependent.
 Donors can't easily donate their blood near Blood bank Location
 Patient can’t easily request for blood near Blood bank location
 There is no online system that connects donors to patients
 The donation is recorded in paper, less secured and it can easily get lost
 Summary report that contains all records including blood donation, blood request
and blood stock for the administrator is hardly accessible or even exists

4. ENTITY TYPES AND R/SHIPS

Entity types and their description:
1. Blood bank: this entity represents the whole organization. It is concerned with serving
donors, accepting blood from them and then storing it in their inventory. Then checking for
any shortage in any type of blood, enhancing some festivals or activities for donors to get
initiated or to get more donors.
2. Hospital: this entity also represents an organization. But their role is quite different. This
entity is the one which requests blood from blood banks. It then gives it to nurses for them
to give it to the right patient. The one who fills the request might be the nurse’s themselves.
This entity also checks if there is any shortage of any type of blood in their inventory.
3. Donor: this entity is a person. This is the one that donates blood to blood banks. It is
necessary for this entity to access the database because it needs to see if there any blood
donation activities nearby or to know where to go and to fill in information about
themselves.
4. Nurses: this entity is also a person. But in this case we are talking about to categories of
nurses; one for the nurse that works in the blood bank (to take blood from donors) and one
in the hospital (to give blood to patients). So there is some sort of generalization in our
enhanced modeling concept, which we will discuss in the last topic.

Page | 4
BLOOD DONATION SYSTEM

Relationships between our entities:

1. Between donor and blood bank: the relationship between this two is many to many
because a donor can donate at more than one blood bank and a blood bank can accept
blood from many donors.

2. Between blood bank and hospital: the relationship between this two is many to many
because blood bank can supply to many hospitals and a hospital can accept blood from more
than one blood bank too.

3. Between hospital and nurse: here there would be more than 2 relationships, because as I
said, there are two kinds of nurses. One that connects with the blood bank and one that
connects with the hospital. The former is one to many because blood bank can hire so many
nurses but a nurse works at one and only one blood bank organization (assuming that she
works full time). The latter is also one to many because can a hospital can hire so many
nurses but a nurse works at one and only one hospital (assuming that she works full time
again).

5. ATTRIBUTES AND CONSTRAINTS

Attributes:
1. Blood bank
 Blood bank id
 Blood bank name
 Blood bank address
 Blood bank contact number
 Blood bank email
 Hospital name(the one the blood bank is supplying for)
2. Hospital

Page | 5
BLOOD DONATION SYSTEM

 Hospital name
 Hospital type
 Hospital address
 Hospital contact number
 Hospital email
 Nurse ID
3. Donors
 Donor ID
 Donor’s full name
 Donor’s medical information
 Donor’s gender
 Donor’s address
 Donor’s contact number
 Donor’s DOB
 Donor’s age
 Donor’s health status
 Blood bank ID
 Donor’s blood type
 Donor’s weight
 Donor’s pulse rate
 Donor’s blood pressure

4. Nurse
 Nurse ID
 Nurse’s full name
 Nurse’s gender
 Nurse’s qualification
 Nurse’s address
 Nurse’s contact information
 Nurse’s DOB
 Nurse’s age
 Patient Id
 Donor ID

Attribute constraints:
 Age (nurse, donor): 0-9/age>100
 Gender (nurse, donor, and patient): ‘F’ or ‘M’
 Blood type (donor): ‘A’ or ’B’ or ’O’ or ’AB’
 Health status(donor): ‘healthy’ or ’not healthy’

6. CANDIDATE AND PRIMARY KEYS

Page | 6
BLOOD DONATION SYSTEM

Keys
1. Candidate keys (a specific type of field in a relational database that can identify each unique
record independently of any other data)
 Blood bank:
 blood bank Id
 blood bank name
 blood bank contact number
 hospital
 hospital name, hospital address
 hospital name, hospital contact information
 donor
 donor ID
 donor’s full name, donors contact information
 donor’s full name, donors address
 Nurse
 Nurse ID
 Nurse’s full name, nurse’s contact information
 Nurse’s full name, nurse’s address
2. Primary keys (a field in a table which uniquely identifies each row/record in a database
table)
 Blood bank:
 blood bank Id
 hospital
 hospital name, hospital contact information
 donor
 donor ID
 Nurse
 Nurse ID

Page | 7