Blood Bank Management System - Assumption University

6m ago
46 Views
7 Downloads
3.35 MB
43 Pages
Last View : 1d ago
Last Download : 1d ago
Upload by : Sabrina Baez
Share:
Transcription

!ASSUMPTION UNIVERSITYVincent Mary School of Science and TechnologyDepartment of Information TechnologyIT 4299 Senior ProjectBlood Bank Management SystemProject Advisor:Project Committee :Asst. Prof. Dr. Darun KesraratA. Tapanan YeophantongDr. Jittima WongwuttiwatSubmitted by:Phyu Phyu Khaing 5718331Wasin Rattanaroengchai 5737458Sossarun Tupcullai 5645116Semester 2/20161

Blood Bank Management SystemDepartment of Information TechnologySenior ProjectProject Title:Blood Bank Management SystemBy:Phyu Phyu Khaing 5718331Wasin Rattanaroengchai 5737458Sossarun Tupcullai 5645116Project Advisor:Asst. Prof. Dr. Darun KesraratAcademic Year:2/2016The Senior Project committees of the Department of Information Technology, Vincent MarySchool of Science and Technology, Assumption University had approved this Senior Project. TheSenior Project submitted in partial fulfillment of the requirements for the degree of Bachelor ofScience in Information Technology.Approval Committees:(Asst. Prof. Dr. Darun Kesrarat)Project Advisor(Dr. Jittima Wongwuttiwat)Committee Member(A. Tapanan Yeophantong)Committee Member2

AcknowledgementMost importantly, our group sincerely thankful to our advisor Asst. Prof. Dr. DarunKesrarat for giving us proper guidance to complete our senior project. Without hissupport we wouldn't be able to complete. We are also thankful to our committeesmembers A. Tapanan Yeophantong and Dr. Jittima Wongwuttiwat who also gave usproper guidance for completing our project. Finally, we would like to give ourspecial thanks to Assumption University of Thailand for giving us enoughknowledge and skills that made us to innovatively and successfully research andcompile this project.3

Table of ContentsPage1.Introduction1-22.Statement of Problem3-43.User Requirements5-64.Objectives5.Scope of the Project6.Cost and Benefits Analysis7.Methodology8.Project Management9.Analysis of Existing System10. Logical Design of the Proposed System10.1 Data Flow Diagram (DFD)10.7 Entity Relationship Diagram (ERD)78-91011-121314-1617-3117-222310.8 Data Dictionary24-2810.9 Interface design29-3611. Reference374

List of TablesTablesPageTable 10.1 Gantt Chart For Project Management13Table 10.2: Data Dictionary - User24Table 10.3: Data Dictionary - Donor24-25Table 10.4: Data Dictionary - Blood Donation25-26Table 10.5: Data Dictionary - Inventory26-27Table 10.6: Data Dictionary - RequestTable 10.7: Data Dictionary - WithdrawTable 10.8: Data Dictionary - Hospital2727-28285

List of FiguresFigurePage10.1 Context Diagram of Blood Bank Management System1710.2 Level 0 of Blood Bank Management System1810.3 Level 1 of Blood Bank Management System1910.4 Level 4 of Blood Bank Management System2010.5 Level 9 of Blood Bank Management System2110.6 Level 10 of Blood Bank Management System22Figure 10.7: Entity Relationship Diagram of Blood Bank ManagementSystem23Figure 10.9: Donor’s Log-in Page29Figure 10.10: Home Page29Figure 10.11: View Personal Profile Page30Figure 10.12: View Donation History Page30Figure 10.13: Administrator’s Log-in Page31Figure 10.14: Home Page31Figure 10.15: Manage Donor Page32Figure 10.16: Create New Donor Page32Figure 10.17: Manage Blood Donation Page33Figure 10.18: Create New Donations and Stock Page33Figure 10.19: Request Approval Page34Figure 10.20: Create New Request Page34Figure 10.21: Blood Bag Withdrawal Page35Figure 10.22: Manage Expired Blood Bag Page35Figure 10.23: Hospital Contact Information Page36Figure 10.24: Report Page361

1. IntroductionA blood donation is a process whereby a person voluntarily has blood drawn to beused for future transfusions when in need at hospitals for treatment procedures thatrequire them. Donation may be of whole blood (blood drawn directly from thebody) or of specific components of the blood; such as red blood cells, white bloodcells, plasma, and platelets. Blood banks often participate in the process ofcollecting blood and other procedures such as managing stocks, approving bloodrequests and updating donation information.The inspiration of this project is to improve blood banks in Thailand and todevelop a blood bank information system which focuses on making an onlinesystem that is accessible for both donors and administrators. Donors can directlyreceive information regarding their previous blood donations, including their bloodresults and donation history, in order to easily schedule their next donations. Theycan also update the personal information through the system, without having tocontact the blood bank registry.The system is also developed for the administrators, who are the main authority inthe system. Administrators can add, modify, delete, and query any donation1

information if necessary. The administrator is also responsible for responding tothe hospital’s blood requests and checking the stocks in the blood bank’s inventory.2

2. Statement of the ProblemThe following problem arises when using a typical blood bank’s existing system: Personal profile accessibility ( P1 )The donor’s information can only be updated by the administrators of the bloodbank. A donor can update their information by calling, faxing, e-mailing, but not bythemselves. This is a waste of time just for updating a piece of information and itmay be troublesome for some donors. Lost or damaged card ( P2 )A typical membership card can easily get damaged if it is exposed to the sunlightor weather and this causes to ruin the card’s barcode which is significantlyimportant for retrieving records. If the card gets lost or stolen, the donor has tomake a replacement card to keep their membership at the blood bank. Donation record accessibility ( P3 )The donor ID card is the only tangible evidence that contains the donor’s recentdonation records, if the card gets lost, donors may find it difficult to schedule theirnext appointment since they are not able to see the last time they had donatedblood.3

Blood result notifications ( P4 )After the process of blood donation, the donor will receive a card that onlycontains their name and blood type. They will not be notified of their blood resultunless they request that information from the blood bank. Blood stock management ( P5 )Blood banks are required to maintain account of blood bags in the inventory. Thisincreases with each blood donation recorded in our system, and decreases as theyare checked out upon hospital requests. Our system will need to keep theinformation up-to-date to ensure correctness of the inventory. Mailing by postal system ( P6 )Blood banks will only mail donors when the donated blood is disqualified,however, this mail is sent through the postal system to the donor’s given address. Ifthe donor’s address is recorded incorrectly, the mail will be sent to the wrongaddress and the donor will never be notified that their blood is rejected and giventhe reason for that.4

3. User RequirementsThere are two internal users involved in this system. The user requirements areconsidered as follows:Donor1. To be able to view their donation records, including where and when they madedonations, and the blood results for each, to learn of their donated blood qualityand schedule their next donations. (Solving P3, P6)2. To be able to view and update their personal information, including name,contact address, and phone number, to keep their donor’s information record upto-date with the blood bank. (Solving P1)3. To be notified of the blood results of their previous donation by e-mail, to knowthe success of their donation. (Solving P4)Administrator1. To be able to create, update, delete, and query donor’s records in order tomanage donor information.2. To be able to create, update, delete, and retrieve donation records to manageinformation about donations made.3. To be able to deposit donated blood into inventory when donations are made.5

4. To be able to withdraw blood from the inventory and keep a record of bloodstocks to always keep count of the blood bags. (Solving P5)5. To be able to create, update, delete, and retrieve request records from hospitalsto manage hospital requests for blood.6. To be able to create, update, delete, and query hospital’s records in order tomanage hospital information.7. To be able to send e-mails to donors for their user account and blood resultsthrough the system. (Solving P6)8. To be able to send e-mail responding to hospitals for their blood requeststhrough the system. (Solving P6)6

4. ObjectivesThe goal of the project is to develop a web application for blood banks to manageinformation about their donors and blood stock. The main objectives of thiswebsite development can be defined as follows:1. To develop a system that provides functions to support donors to view andmanage their information conveniently.2. To maintain records of blood donors, blood donation information and bloodstocks in a centralized database system.3. To inform donors of their blood result after their donation.4. To support searching, matching and requesting for blood convenient foradministrators.5. To provide a function to send an e-mail directly to the donor for their useraccount and the hospital, the availability of the blood bag.7

5. Scope of the ProjectThe system functions and features of our system will include the following: RegistrationThis function allows the donor and administrator to register as a user to interactwith the system. The system requires the user to login before viewing and editingany information. View and edit information onlineDonors are allowed to view their blood donation records online by their givenaccount. They can also edit their personal information through the system. Data is input by the AdministratorsThe donor’s information and donation records can be sent from the hospital to theadministrator by calling or e-mail. The administrator is responsible for keying thereceived data into the system. Recording donation recordsThe system is able to record data of whole blood which is sent from the hospital.8

Manage blood inventoryThe system uses a First-In-First-Out stock management, where the blood stock thatis checked-in to the system first will be the first one given to the hospital whenrequested. When the blood stock is expired, the administrator is responsible forremoving the stock from the inventory and updating the system. Blood requestsThe hospital can request blood via e-mail and by calling to the blood bank. Notify by E-mailThe donor’s account and generated password will be sent via e-mail, following bytheir blood result of the previous donation sent in a separated e-mail. Hospitals canalso receive e-mail responding to their requested blood whether it is available inour stock or not. Summary reportThe system is able to generate a report to summarize all records including blooddonation, blood requests and blood stock for the administrator.9

6. Cost and Benefit AnalysisCost AnalysisGoDaddy - Web Hosting (Economy) 1 website 100 GB storage Unmetered bandwidth 1 free domain 3,108/yearBenefits Analysis1. Users do not have to contact the hospital to know the results of their blooddonation. They can view their results through the website by logging-in withtheir username and password.2. The reports and information are kept in electronic form and can be easilymaintained by the administrators, and donors may access their donation recordswhenever they want to.3. The reports of donations are kept in electronic files so that they may last longerand have less chance of being lost or damaged.4. Administrators of the system can easily manage blood stock and bloodwithdrawals that have been requested by the hospitals.10

7. Methodology1. Project Identification and SelectionIn this project, we aimed to develop an online blood bank system which will focusmainly on managing the donor’s blood information. Anyone who is interested inblood donation can donate the blood at the hospital or blood donation centers.2. Project Initiation and PlanningTo begin the project, we have gather user requirement of this system and preparethe scope and objective. The results from this phase are scope and limitation,objectives, cost and benefits, feature of the proposed system and user interfacedesign.3. Analyzing System needsWe have studied and identified problems of existing system, then we develop dataflow diagram for the existing system. We also develop data flow diagram (DFD)and entity relation diagram (E-R diagram) for the proposed system.4. Designing the Proposed SystemBased on the analysis phase, we converted E-R diagram into relational databasemodel and created data dictionary and DFD and user interface are designed in thisprocess.11

5. Development of the Proposed SystemIn this phase, we are going to convert the design of proposed system to computersoftware, which includes computer programming using phpMyAdmin as asoftware tool written in PHP, which is intended to handle the administration ofMySQL, and translating the design specifications into the computer code.6. Testing the Proposed SystemThis step is the process of testing whether the programming code will workcorrectly with the conditions in our system or not. In this phase, we will fix bugs inorder to produce a system with maximum performance.7. Implementing the Proposed SystemWe wish to launch this system on the internet, so that donors are able to view theirblood donation records online and administrators can create, update, delete, andquery records conveniently.12

13Table 10.1 Gantt Chart For Project Management8. Project Management

9. Analysis of the Existing SystemThere are two types of process in the existing system: the blood donation processby donors, and the blood request process by hospitals. In both processes, anadministrator is in charge of managing the blood inventory in the blood bank.Blood Donation Process by DonorsWhen a new donor comes to donate blood, they are required to fill out theirpersonal information during the registration process before making a donation [1].After the donation, the donor is given a donor identification card with their name,blood type and a barcode to be used as a reference for future donations [2]. Thebarcode is used to retrieve the donor’s record containing their personalinformation, medical history and donation information, including blood results [3].Only blood bank administrators have the authority to access the donor’s records,since the system is only available for their use within the organization. This makesit difficult for donors to make changes to their personal information within thesystem. That is, for donors to update their personal information, such as theirphone number, mailing address, or e-mail, they cannot update the information bythemselves, but have to contact the blood bank center to update their information.14

At the back the card is a table that contains number of donations, date, location,and the blood collector’s signature. Existing donors can submit their donor IDcards to retrieve their personal information and donation records and start theblood donation process, and they will be given a new card after they have donatedblood for a total of eight times. Having a donor ID card may be a tangible reminderto people that they are helping lives as a blood donor; however, possessing aphysical card comes with drawbacks such as loss or damage. To ensure donors canstill identify themselves with the system, other credentials, such as username andpassword, can be used as a safeguard if their donor ID card is lost or damaged.If the donated blood is disqualified, the donor will be notified through postal mailthat their blood component is reactive to viruses [4], meaning that there is apositive result of the blood being infected, and the organization will also inform thedonor to perform another blood test at the blood bank to confirm the result ofblood. If the blood is qualified, the administrator then will deposit the blood intothe inventory for future requests.Blood Request Process by HospitalsHospitals can request for blood by calling in or e-mailing the blood bank the typeof blood and the quantity that is in need. The administrator is responsible in15

checking the availability of the blood type according to the request. If therequested blood type is available, the administrator will withdraw the blood fromthe inventory and transfer it to the hospital. However, if the requested blood isunavailable, the administrator will send an e-mail to inform the hospital.16

10. Logical Design of the Proposed System10.1 Data Flow Diagram - Context DiagramFigure 10.1: Context diagram of Blood Bank Management System17

10.2 Data Flow Diagram - Level 0Figure 10.2: Level 0 of Blood Bank Management System18

10.3 Data Flow Diagram - Level 1Figure 10.3: Level 1 of Blood Bank Management System19

10.4 Data Flow Diagram - Level 4Figure 10.4: Level 4 of Blood Bank Management System20

10.5 Data Flow Diagram - Level 9Figure 10.5: Level 9 of Blood Bank Management System21

10.6 Data Flow Diagram - Level 10Figure 10.6: Level 10 of Blood Bank Management System22

10.7 Entity Relationship DiagramFigure 10.7: Entity Relationship Diagram of Blood Bank Management23

10.8 Data DictionaryUser : Contains general information of a e key to identifyeach user1876534279usernameVarchar(10)username for log in tosystemjohn0802auth keyVarchar(32)key to rememberusername d hashVarchar(60)generate hash forpassword 2y 13 oBCpassword reset tokenVarchar(43)token for user to resetpasswordS f7X10B83mpMaLBYz7H TNv7qTa6j 1497180423emailVarchar(30)email address that useruse for register [email protected](2)status use to identifywhether user is beingactived10 active20 deactivecreated atDatedate of new usernameis created01/03/2017updated atDatedate of user updateusername or password23/12/2017roleSmallint(2)role to distinguish usertype10 donor20 adminTable 10.2: Data Dictionary – UserDonor: Contains general information of a DonorColumnTypeDescriptionExampled id(PK)Int(11)unique key to identifydonor124

identification noVarchar(13)identification number1101800344496d nameVarchar(50)name and surname ofdonorAlexander Washingtond ageDatedonor’s date of birth02/10/1997d addrVarchar(70)address of donor424 trapha bkk 12000d genderVarchar(6)gender of donorMale, Femaled phoneInt(10)contact number ofdonor093999999blood typeText(3)blood type of donorABemail statusInt(1)status of donor's bloodtest1 sent0 pendingtype rhVarchar(10)identify special type ofbloodRh Positive, RhNegativeTable 10.3: Data Dictionary – DonorBlood Donation: Contains blood donation information of each donorColumnTypeDescriptionExampleb id(PK)Int(10)Unique key to identifyeach donation12434567890d id(FK)Int(11)auto-incrementationnumber1h id(FK)Int(10)Unique key to identifyhospital3257865235stock id(FK)Int(10)Unique key to identifyeach blood bag128blood qtyInt(2)a unit of blood donateper time1 (units)blood statusVarChar(20)record whether blood isqualifiedqualified, disqualifieddonate dateDatedonation date17/04/2017result dateDateblood result date23/04/2017blood typeVarchar(3)blood type of donorABsysphilisTinyint(1)identify transfusiondisease1 yes0 no25

hepatitis B virusTinyint(1)identify transfusiondisease1 yes0 nohuman immunodeficiency virusTinyint(1)identify transfusiondisease1 yes0 nohepatitis C virusTinyint(1)identify transfusiondisease1 yes0 not cruziTinyint(1)identify transfusiondisease1 yes0 nomalariaTinyint(1)identify transfusiondisease1 yes0 nohuman T lymphotropic virus Tinyint(1)identify transfusiondisease1 yes0 nowest mile virusTinyint(1)identify transfusiondisease1 yes0 nocytomegalovirusTinyint(1)identify transfusiondisease1 yes0 nohepatitis E virusTinyint(1)identify transfusiondisease1 yes0 noemail statu

List of Figures 1 Figure Page 10.1 Context Diagram of Blood Bank Management System 17 10.2 Level 0 of Blood Bank Management System 18 10.3 Level 1 of Blood Bank Management System 19 10.4 Level 4 of Blood Bank Management System 20 10.5 Level 9 of Blood Bank Management System 21 10.6 Level 10 of Blood Bank Management System 22