ONLINE BLOOD BANK SYSTEM

by

VAISHALI
Enrolment No: 084975988

Under Guidance
of

Submitted to the School of Computer and Information Sciences,

IGNOU
in partial fulfilment of the requirements
for the award of the degree
Master of Computer Applications (MCA)
2015

Indira Gandhi National Open University

Maidan Garhi
New Delhi – 110068.

1
ONLINE BLOOD BANK SYSTEM

Under Supervision of :

Submitted By:

Name : Vaishali

Programme : MCA

Enrolment No. : 084975988

Study Center Code : 0759

2
 ONLINE BLOOD BANK SYSTEM

TABLE
TABLEOF
OFCONTENTS
CONTENTS
Contents Page No.

1. Title of the project. 4

2. Introduction and objectives of the Project. 4

3. Advantage 6

4. Project Category 8

5. Tools/Platform, Hardware and Software requirement specifications. 9

6. Data Modeling 11

7. ER-Diagram 15

8. Data Flow Diagram Context Level DFD 16

9. Module Description 24

10. Report Generation 28

11. Security and Validation Checks. 29

12. Scope of future application 30

13. Conclusion 31

14. Bibliography. 31

3
 1. TITLE OF THE PROJECT

ONLINE BLOOD BANK SYSTEM

2. INTRODUCTION AND OBJECTIVES OF THE PROJECT

Introduction

This is a Project work undertaken in context of partial fulfillment of the MCA.

I have tried my best to make the complicated process of the Blood banks as simple as
possible using Structured & Modular technique & Menu oriented interface. I have tried to
design the software in such a way that user may not have any difficulty in using this
package & further expansion is possible without much effort. Even though I cannot claim
that this work to be entirely exhaustive, the main purpose of my exercise is perform each
user’s activity in computerized way rather than manually which is time consuming.

People will no longer get caught in hospital red tape to procure blood. Detailed
information about the blood stock position, blood group, blood components and the
procedure of getting blood is now available on the Internet. It is Web Based Blood Bank
Management System.

• Provides the stock of blood for various groups in the various blood banks.
• Provides online registration to people who are willing to donate blood.
• Gives the details of blood donation camps.
• GroupWise listing of various blood groups.
• Citizens get information about the next coming blood donation camp via post or email
after registration.
• Online submission of registration forms.
• All the process of submission of registration form is quite simple.
• Department can collect information regarding various blood groups.
• People can get registration by sitting at home.
• Before any blood donation camp the registered citizens gets all the details regarding the
camp.

4
I am confident that this software package can be readily used by non-programming
personal avoiding human handled chance of error.

Objectives of the project

I am confident that this software package can be readily used by non-programming

personal avoiding human handled chance of error. This project is used by two types of
users
i. Online Users.
ii. Administrator.
Online users can enquire about the blood donation if he/she wants to donate or receive
blood. Doctors, Nodal Hospitals can also register through this site.
Administrator can maintain daily updates in the requests of the users, doctors, hospitals
etc. Administrator is must be an authorized user. He can further change the password.
There is the facility for password recovery, logout etc. The main objectives of the project
are:

 The objective of blood bank is to collect and distribute blood

 Collect detailed description of the donors who are interested in blood donation.

 Nodal hospitals registrations.

 Rules, terms and conditions for Blood donation.

5
3. ADVANTAGE

I have designed the given proposed system in ASP.NET to automate the process of Rotary
Blood Banks

The complete set of rules & procedures related to a blood bank generating report is called
“Online Blood Bank System”. My project gives a brief idea regarding automated Blood
Bank activities.

The following steps that give the detailed information of the need of proposed system are:

Performance: During past several decades, the company records are supposed to be
manually handled for all the activities. The manual handling of the record is time
consuming and highly prone to error. To improve the performance of the blood bank, the
computerized system is to be undertaken. The computerized project is fully computerized
and user friendly even that any of the members can see the report and status of the blood
bank.

Efficiency: The basic need of the project is efficiency. The project should be efficient so
that whenever a new customer record is added, or record is modified or deleted, the record
is updated automatically.

Control: The complete control of the project is under the hands of authorized person who
has the password to access this project and illegal access is not supposed to deal with. All
the control is under the administrator and the other members have the rights to just see the
records not to change any transaction or entry.

Security: Security is the main criteria for the proposed system. Since illegal access may
corrupt the database. So security has to be given in this project.

6
Key Features Are:
 System Connectivity

 No data duplication

 No Paper Work Required

 Time Efficient

 Cost Efficient

 Automatic data validation

 User friendly environment

 Data security and reliability

 Fast data insertion & retrieval

 Easy performance check

 Maintaining records of customers

 Crystal Report generation

7
4. PROJECT CATEGORY

Business Application (RDBMS) Expert Systems:

This Project is coupled with material on how to use the various tool, sub sets available in
ASP.NET AND SQL SERVER.

The need of today’s software development is competence in a GUI based front-end tool,
which can connect to Relational Database engines. This gives the programmer the
opportunity to develop client server based commercial applications.

These applications give users the power and ease of a GUI with the multi user capabilities
of Novell, UNIX or WinNT based RDBMS engines such as SQL SERVER.

8
5. TOOLS / PLATFORM, HARDWARE AND SOFTWARE
REQUIREMENT SPECIFICATION

HARDWARE:

Processor : Pentium 2.4 GHz or above

Memory : 256 MB RAM or above

Cache Memory : 128 KB or above

Hard Disk : 3 GB or above [at least 3 MB free space required]

Floppy Disk Drive : 3.5”

[At least one drive labeled a: required]

SOFTWARE:

Operating System : Windows XP (Professional).

Font-End Tool : ASP.NET, C#, Xml

Back-End : SQL SERVER 2000

9
.NET FRAMEWORK

Advantages of the .NET Framework

 Some advantages of the .NET Framework are:

o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment

Security

 Evidence-based security (authentication)

 Based on user identity and code identity
 Configurable policies
 Imperative and declarative interfaces

SQL SERVER

Microsoft SQL Server is an application used to create computer databases for the
Microsoft Windows family of server operating systems. It provides an environment used
to generate databases that can be accessed from workstations, the web, or other media
such as a personal digital assistant (PDA). Microsoft SQL Server is probably the most
accessible and the most documented enterprise database environment right now. This also
means that you can learn it a little quicker than most other database environments on the
market.

10
6. DATA MODELING

Introduction to data dictionary:

Data dictionaries are an integral component of structured analysis, since data flow
diagrams by themselves do not fully describe the subject of the investigation . The
data flow diagrams provide the additional details about the project/system.

Data Dictionary (Definition):

A data dictionary is a catalog- a repository- of the elements in a system. These elements

center on the data and the way they are structured to meet user requirements and
organization needs. A data dictionary consists of a list of all the elements composing the
data flowing through a system. The major elements are data flows, data stores, and
processes. The data dictionary stores details and descriptions of these elements.

Login Table

Field Type constraint

Username Char(30) Not Null
Password Char(30) Not Null
Email Char(30) Not Null
Security question Char(30) Not Null
Answer Char(30) Not Null

Admin Table

Field Type constraint

Username Char(30) Not Null
Password Char(30) Not Null

Feedback table

11
Field Type constraint
Name Char(30) Not Null
Phone Number Not Null
Email Char(50) Not Null
Contact Char(200) Not Null

Donator’s Table

Field Type constraint

Donator Id Char (30) Not Null
Name Char (30) Not Null
Address Char (30) Not Null
City Char (30) Not Null
State Char (30) Not Null
Email Char (50) Not Null
Phone Number Not Null
Blood Group Char (30) Not Null
Physical Status Char (30) Not Null
Diabetic Bit Not Null
Blood Pressure Bit Not Null
Weight Number Not Null
Remark Number Not Null

Receiver’s table

Field Type constraint

Receiver Id Char (30) Not Null
Name Char (30) Not Null
Address Char (30) Not Null
City Char (30) Not Null
State Char (30) Not Null
Email Char (50) Not Null
Phone Number Not Null
Blood Group Char (30) Not Null
Physical Status Char (30) Not Null
Diabetic Bit Not Null
Blood Pressure Bit Not Null
Weight Number Not Null
Remark Number Not Null
No_of_bottles_req Number Not Null
Doctor_name Char(30) Not Null
Hospital Char (50) Not Null
Disease Char (50) Not Null

Hospital table

Field Type constraint

Hospital Name Char (50) Not Null

12
Address Char (60) Not Null
City Char (50) Not Null
State Char (30) Not Null
Blood_group_req Char (30) Not Null
Qty_req Char (50) Not Null
Qty_avail Number Not Null
Details Char (150) Not Null
Conatct Person Char (15) Not Null

Indians_blood Bank: Details of the blood bank in India

Field Type constraint

Bank_id Char (30) Not Null
Name Char (30) Not Null
Address Char (30) Not Null
City Char (30) Not Null
State Char (30) Not Null
Contact_person Char (30) Not Null
Email Char(50) Not Null
Phone Number Not Null
Details Char(150) Not Null

Blood_bank_stock: Stock of the Blood groups available in Rotary Blood Bank.

Field Type constraint
Bank_group Char (30) Not Null
Qty_available Char (30) Not Null
Qty_required Char (30) Not Null

Camps table: Store details of the temporary camps arranged by Rotary society
Field Type constraint
Camp_no Char (30) Not Null
Timings Char (30) Not Null
Date, day Char (30) Not Null
Place Char (30) Not null
Phone Number Not Null
Contact Person Char (50) Not Null

13
7. ER-DIAGRAM

14
8. DATA FLOW DIAGRAMS

Context level DFD

Update Availabilities
Use Respond Admin
Services Of Blood

Camps
Details

ONLINE
Check BLOOD
Request BANK Add
Services Hospitals
View SYSTEM
Add/ Edit
Blood Bank Blood Banks Details

Receive
Request as Donor Request
Blood donator
Receive
Patients Request

Accept
Doctors Details

15
 Ist LEVEL DFD

User Process
Request

DI Receiver details

Book Details

Update 1.2 Provide

stock Availability

2 Provide
Request Receive Camp
For Donation Donor Details
Request
Form

D2 Donors D3 camp

User name 4 Verify

Admin User D4 Admin Login
Login
Password

Invalid use
Enter Username
After Login

Add 5
doctor Add 6
s Blood D5 Blood Bank
Bank

16
 II nd LEVEL DFD for Receiver

Blood Request

Receiver/ Patient

1.1 Receivers
the Blood
request

Assign Doctor

ONLINE
1.2 check the
BLOOD BANK availability
for blood
SYSTEM bank

Receivers
1.3 Issue
Blood
with
details

Blood Bank

17
 II nd LEVEL DFD for DONOR

Donates Blood

DONOR /
PATIENT
2.1 Receiver
the Donor
Request
form

2.4
Issue
donor
Card
Assign Doctor

ONLINE
2.2 Doctor
BLOOD BANK Executive
the Donor
SYSTEM request

Doctor Donor
2.3
Update
Blood
bank

Blood bank

18
 II nd LEVEL DFD for Camp

Arranges Blood 3.1

ADMIN Bank Receive
the
Request

3.2
Assign
ONLINE Duty to the
BLOOD BANK Doctor
SYSTEM

3.3
Check the Doctor
Donor
Blood
DONOR Details

Issue Card
3.4
If Report is
Ok receive the
blood & issue Donor
donor card

Update

Blood Bank

19
 IInd LEVEL DFD for doctor registration

Apply
5:1
Accepts
Doctor
Doctor data

Informs

ONLINE
BLOOD BANK
SYSTEM

Update

Print
screen
Doctor

20
 DFD FOR ADMIN LOGIN

1.1 1.2
Admin
Validate user
Username
Accept the & allow
Password
Upload / Access
Download
request

Verify User

Information
ONLINE
BLOOD BANK
SYSTEM

User

Screen / Print

21
 IInd LEVEL DFD FOR NODAL HOSPITAL REGISTRATION

Request
3.1 Accept
the
Registration
request

Hospital

3.2 update
the Doctors
& Facility
Update lists

ONLINE
BLOOD BANK
SYSTEM

Screen | Print Nodal Hospital

22
9. MODULES DESCRIPTION
Different modules that makeup these systems are briefly described below:

Module 1: Password Module

In this module, User enters a password and the software checks its validity. If the
password is valid then option is given to change the password, otherwise “Invalid
User/Password” message is displayed.

Module 2: Creating new Entity (Users, Donators, Receivers, Patients, and Hospitals
etc.)
In this module, whenever a new entity is required to be added the corresponding forms are
opened and the database is manipulated to check whether the data is already existing or
not. If it already exists, then it prompts that “Entry already existing” and if not than the
data is entered with the various validation checks.

Module 3: Modifying/Updating Existing Entities

In this module, whenever an existing entity is required to be modified the corresponding
forms are opened and the database is manipulated and the data is fetched. Now the user
can made the required changes and then accordingly, he updates the data. Again, the
checks are followed in case there is any invalid entry. For example if some purchase order
has already been raised but not dispatched than it can be modified accordingly if there is
any change in the order from the customer side.

Module 4: Searching
The Search page will have controls for selecting different possible values for all of the
fields, as described above. This will search for all the donators, receivers, doctors, patients
in the database which match the given criteria.

Module 5: Donators

This module is related to donators. Database is maintained for the donators. Some persons
only enquire about it but some are really interested in donations. It is important to know
about their physical or health status

23
Module 6: Receivers
This module is related to receivers. Database is maintained for the receivers.

Module 7: Nodal Hospitals

This module is related to nodal hospitals, registration of Nodal Hospitals.

Module 8: Benefits

 Increased productivity and operational savings

 Value added services to Donors
 Donor records available on emergency blood requirements
 Blood Component Preparation made easier
 Blood Bag orders and tracking are made easier
 Blood Cross Matching now simpler and quicker
 Blood issue records updates now faster
 Blood Bags Inventory alerts
 Assist users in planning for Blood Camps

Module 9: Queries:
In this module user can query about the donations, receiving bloods, blood problems etc.

Module 10: Terms and Conditions: This module is related to the terms and conditions
for the donation, transplantation etc.

Module 11: Administration screen:

The Blood Bank system will be able to differentiate between administration and normal
users. Logging in with administrator user will provide access to administrations functions
which will be: Creating Users getting the details of patients, donators, doctors etc. and
then responding them.

24
Module 12 : Validation of Data Entered by the User & Error Handling
In this module, the validity of data entered by the user during the various business
processes is checked through various validation checks. For example, there should not be
any characters entered in the numeric fields, likewise if there is any error occurs than it
should handle that particular error and give the required messages.

Module 13: Report Generation

In this module reports are generated for the following entities:
a) Users Reports
b) Donators Details
c) Receivers Details
d) Blood Bank Details
e) Search Donators -city ,blood group wise
f) Nodal Hospitals Registered.

Module 14: Feedbacks

In this module, Feedback details are given by the users and checked by the administrator
of the site.

Process Logic for Each Module:

Process Logic of Module is a tool that may be useful in planning and evaluating projects.
Our logic model contains four components with Inputs-Outputs-Outcomes being central to
the built in response to the model:

 Situation: The context and need that gives rise to a project or initiative; logic
modules are built in response to an existing situation.

 Inputs: The resources, contributions, and investments that are made in response to
the situation. Inputs lead to Outputs.
 Outputs: The activities, products, methods, and services that reach people and
users. Outputs lead to outcomes.
 Outcomes: The results and benefits for individuals, groups, agencies, communities
and/or systems.

Project Details

25
 What It Does:-
 Provides the stock of blood for various groups in the various blood banks.
 Provides online registration to people who are willing to donate blood.
 Gives the details of blood donation camps.

Beneficiary of project:-
 Citizen
 Department

Output (Major one):-

 GroupWise listing of various blood groups.
 Citizens gets information about the next coming blood donation camp via post
or email after Registration

How it has benefited citizens:-

 Online submission of registration forms.

How it has improved the efficiency:-

 All the process of submission of registration form is quite simple.
 Department can collect information regarding various blood groups.

Impact:-
• People can get registration by sitting at home.
• Before any blood donation camp the registered citizens gets all the details
regarding the camp.

10. REPORT GENERATION

26
From above modules different reports are generated. 'Crystal Reports' is a popular third
party package that is included with ASP.NET which allows us to create reports for our
application. Reporting is an important module for an administrator. Administrator can
generate the reports to get details about:

 Users Reports : Gives users details.

 Donators Details: Gives donators details.
 Patients Details: Gives patients details.
 Blood collection Details: Gives the details about the total stock in the blood bank
according to different blood groups.
 Nodal Hospitals Registered.
 Feedback Details
 Admin Details

27
11. SECURITY AND VALIDATION CHECKS

In this project we have used different validation checks. While entering the date into the
form it will check for the name of the client is properly filled & it should not be null.

Whenever we enter the data for the new customers will automatically check the details
from the customers table.

Almost for all fields we have used the validations, for example if name of the fields
requires the text type of data then it will check for the string and if the data is numeric then
it will check if the number entered is proper numeric or not.

ASP.NET Provides Security

 Evidence-based security (authentication)

 Based on user identity and code identity
 Configurable policies
 Imperative and declarative interfaces

28
12. SCOPE OF FUTURE APPLICATION

This project can be used in the Blood banks. Rotary Blood Bank System is a Complete
Blood Bank Management Solution that covers all the activities of a blood bank. User can
have details from Donor Registrations either from Camps or Voluntary Blood Donations,
Blood Screening, Blood Cross matching, Blood Component Preparation, Blood issues,
Blood Receipts Blood Stock Updates etc.

Utmost care and back-up procedures must be established to ensure 100% successful
implementation of the Online Blood Bank System.

In case of system failure, the organization should be in a position to process the

transaction with another organization or if the worst comes to the worst, it should be in a
position to complete it manually.

Benefits of the web project

 Increased productivity and operational savings

 Value added services to Donors
 Donor records available on emergency blood requirements
 Blood Component Preparation made easier
 Blood Bag orders and tracking are made easier
 Blood Cross Matching now simpler and quicker
 Blood issue records updates now faster
 Blood Bags Inventory alerts
 Assist users in planning for Blood Camps
 Cater to emergency services now well equipped
 Record keeping now better for statutory needs
 Financial transaction updates

29
13. CONCLUSION

This project is designed to meet the requirements of the Blood banks. It has been
developed in ASP.NET, keeping in mind the specifications of the system.

For designing the system we have used simple data flow diagrams.

Overall the project teaches us the essential skills like:

 Using system analysis and design techniques like data flow diagram in designing the
system.
 Understanding the database handling and query processing using SQL Server.

14. BIBLIOGRAPHY

1. Senn James A: Analysis and Design of Information Systems, McGraw Hill,

International Ed, 1989.
2. O'Brien Jamea A: Management Information Systems, Galgotia Publications Pvt Ltd,
New Delhi, 1998.
3. Laudon & Laudon: Management Information Systems, Organisation and Technology,
PHI, New Delhi, 1998.
4. Wetherebe James: Systems Analysis and Design, Galgotia Publications Pvt Ltd, New
Delhi, 1990

Websites

www.indianblooddonors.com
www.bloodgivers.com
www.jeevan.org
www.blooddonations.org
www.aabb.org
www.redcross.org

30