Blood Bank
Content
Blood Bank Management System ( BBMS)
*INTRODUCTION Blood Bank is a humanitarian organization for meeting the demand for blood in various emergency conditions from traumas to major operations and diseases that necessitate regular insertion of blood. That is why it is one of the major components of a hospital, concerned with various related activities including donor registration, physical examination, blood grouping, blood infectious tests, component separation, blood requisition and cross match. To replace the existing manual process of collecting, storing and managing data for this system with a complete and automated Management Information System, Blood Bank Management Information System (BBMIS) has been introduced. The BBMIS provides ready information about blood reserve/stock, daily crossmatched details, total daily blood requisitions and information regarding blood and donor.
USE CASE DIAGRAM FOR the Blood Bank Management System
Use Case name : Process Receive Blood Area: Medicine Actors: System Operator Stake-Holders & Interest: System Operator, Donor, Institution, Humanitarian Organization, hospitals etc Level: Blue Description : Steps performed(Main path) Information for steps 1. Donor arrives to donate blood. 2. Operator starts a new blood donation. 3. Operator enters donor id. 4. Operator enters donor’s instantaneous physical information for eligibility testing. 5. Operator asks a worker to take blood from donor. 6. System generates an id for the new bag 7. Worker takes blood in a bag. 8. Donor leaves after being entertained. 9. Operator logs out. Preconditions: Operator is identified and authorized. Success Guarantee (Post-conditions): Blood input along with donor’s information is saved. Risk: medium Extension (Alternative Flow): *a. At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery 1. System signals error, records the error and enters a clean state. 2. Operator starts a new blood input. 3a. Invalid ID: System signals error & rejects entry 3b. Donor is new:
1. Operator enters personal information about the new donor. 2. Donor wants to be member. 2a.Donor wants to be normal donor. 3. System presents a new id. 4a. System outputs that donor isn’t eligible for physical problems: 1. Donor is rejected to donate blood.
Use Case name : Process Deliver Blood to Members Area: Medicine Actors: System Operator Stake-Holders & Interest: System Operator, Client, Institutions. Level: Blue Description : Steps performed (Main path) Information for steps 1. Client arrives for taking blood.. 2. Operator verifies his papers and demand of blood. 3. Operator starts a new delivery. 4. Operator enters ID. 5. Operator uses use case (Uc5): Process Deliver Blood free. 6. Operator repeats step5. 7. System operator takes taka 50 from Client. 8. Operator updates balance. Preconditions: Operator is identified & authorized. Success Guarantee (Post-conditions): Blood input along with donor’s information is saved. Extension (Alternative Flow): *a At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery. 1. System signals error to operator, records the error and enters a clean state. 2. Operator starts a new blood deliver. 1a. Invalid Request: Rejects the request. 2a.Demanded blood bags are not available: Operator logs his demanded information if Client wants. 4a. Invalid Member Id: System rejects the entry, operator retries with correct Id. 7-8a. Financial inability for payment: Operator takes the amount which client can pay & updates balance with the given amount.
Use Case name : Process Deliver Blood Free. Area: Medicine Description : Steps performed (Main path) Information for steps 1. Operator starts a new free delivery for client. 2. Operator delivers a bag of required group to the client. 3. Operator enters necessary delivery information. Success Guarantee (Post-conditions): Blood delivery with associated information is saved. Extension (Alternative Flow): *a At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery 1. System signals error, records the error and enters a clean state. 2. Operator starts a new blood deliver.
*INTRODUCTION Blood Bank is a humanitarian organization for meeting the demand for blood in various emergency conditions from traumas to major operations and diseases that necessitate regular insertion of blood. That is why it is one of the major components of a hospital, concerned with various related activities including donor registration, physical examination, blood grouping, blood infectious tests, component separation, blood requisition and cross match. To replace the existing manual process of collecting, storing and managing data for this system with a complete and automated Management Information System, Blood Bank Management Information System (BBMIS) has been introduced. The BBMIS provides ready information about blood reserve/stock, daily crossmatched details, total daily blood requisitions and information regarding blood and donor.
USE CASE DIAGRAM FOR the Blood Bank Management System
Use Case name : Process Receive Blood Area: Medicine Actors: System Operator Stake-Holders & Interest: System Operator, Donor, Institution, Humanitarian Organization, hospitals etc Level: Blue Description : Steps performed(Main path) Information for steps 1. Donor arrives to donate blood. 2. Operator starts a new blood donation. 3. Operator enters donor id. 4. Operator enters donor’s instantaneous physical information for eligibility testing. 5. Operator asks a worker to take blood from donor. 6. System generates an id for the new bag 7. Worker takes blood in a bag. 8. Donor leaves after being entertained. 9. Operator logs out. Preconditions: Operator is identified and authorized. Success Guarantee (Post-conditions): Blood input along with donor’s information is saved. Risk: medium Extension (Alternative Flow): *a. At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery 1. System signals error, records the error and enters a clean state. 2. Operator starts a new blood input. 3a. Invalid ID: System signals error & rejects entry 3b. Donor is new:
1. Operator enters personal information about the new donor. 2. Donor wants to be member. 2a.Donor wants to be normal donor. 3. System presents a new id. 4a. System outputs that donor isn’t eligible for physical problems: 1. Donor is rejected to donate blood.
Use Case name : Process Deliver Blood to Members Area: Medicine Actors: System Operator Stake-Holders & Interest: System Operator, Client, Institutions. Level: Blue Description : Steps performed (Main path) Information for steps 1. Client arrives for taking blood.. 2. Operator verifies his papers and demand of blood. 3. Operator starts a new delivery. 4. Operator enters ID. 5. Operator uses use case (Uc5): Process Deliver Blood free. 6. Operator repeats step5. 7. System operator takes taka 50 from Client. 8. Operator updates balance. Preconditions: Operator is identified & authorized. Success Guarantee (Post-conditions): Blood input along with donor’s information is saved. Extension (Alternative Flow): *a At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery. 1. System signals error to operator, records the error and enters a clean state. 2. Operator starts a new blood deliver. 1a. Invalid Request: Rejects the request. 2a.Demanded blood bags are not available: Operator logs his demanded information if Client wants. 4a. Invalid Member Id: System rejects the entry, operator retries with correct Id. 7-8a. Financial inability for payment: Operator takes the amount which client can pay & updates balance with the given amount.
Use Case name : Process Deliver Blood Free. Area: Medicine Description : Steps performed (Main path) Information for steps 1. Operator starts a new free delivery for client. 2. Operator delivers a bag of required group to the client. 3. Operator enters necessary delivery information. Success Guarantee (Post-conditions): Blood delivery with associated information is saved. Extension (Alternative Flow): *a At any time system fails: To support recovery ensure all transactions can be recovered. 1. Operator restarts system, logs in & requests recovery of prior state. 2. System reconstructs prior state. 2a. System detects anomalies preventing recovery 1. System signals error, records the error and enters a clean state. 2. Operator starts a new blood deliver.
