Blood Bank Management System is a Web application which stores the information of all users with their Blood Group,Contact numbers,email id and it includes features like To whom they can donate the Blood ,No. of times they have donated the Blood , Do they charge anything for donating Blood and is there any Food requirements for them after donating Blood etc.
Each nurse who is managing incoming donors will need a password to ensure that only authorized staff can see and change data. That password should change daily, too, and each password should only allow access to THAT DAY’s data. A Manger password should allow access to all of the data, too.
Each donor should be allowed to see, but not change, his/her record, so he/she will will need unique password access to his/her own data, and must not be able to see anyone else’s data. Each donor will need a clear Demographics record, that includes address, phone, email, and some identification such as driver’s license number, state, and expiration date. (In other words, when making a donation, there needs to be a way to confirm the correct person has presented him/herself.
The person’s blood type can be part of the Demographics, and it should be limited to the valid blood types that exist A, B, O, positive and negative, etc. If the person has food/drink allergies for post-donation nourishment, it can be noted here, too.
A donation record should be created, too, for each donation event. Date, time, location, nurse/person doing the initial screening, claimed weight (and measured weight, if doubt if the person can safely give blood), measured blood pressure, temperature, the anemia test that is done with a droplet of blood, and answers to several common screening questions, such as: contact with anyone with HIV/AIDS, TB, hepatitis, or any other infectious diseases, any recent fevers or other illnesses, and use of injected drugs.
The donation record should include a place for Serial Number of the collection bags and test tubes used for the donation. Also, the nurse who does the actual donation collection should be noted, and the approximate length of time the person stayed and rested after donating the blood.
The donation record should have a place to indicate if and when the person’s blood was rejected, which sometimes happens if the above questions raise alarm or if random testing reveals an infectious disease or other problem.
A case number should be recorded if the blood was rejected for future follow-up. Ideally, too, the patient data should be kept in an encrypted folder, to make hacking and tampering difficult or impossible.
Software retirements of Blood Bank Management System Web Application are HTML,CSS,Java Scrip,Java,JSP,my SQL,PHP etc.,
Blood Bank Management System Python Web Application:
Survey of Existing Models:
During a literature survey, we collected some information about the blood bank management system located in city and rural areas, some hospitals have their own blood bank unit with each and all technical facilities. The BD process starts with the arrival of the donor at the blood center. Donors can be divided into returning donors, who donate on an almost regular basis, and walk-in donors, who are entering the system occasionally or for the first time. In any case, donations can be made after a defined rest period from the previous one, which is defined by law. When a donor centers in the system for the first time, he/she is requested to provide personal (e.g., name, address, age, job, gender) and medical/health (e.g., diagnosis, lab results, treatments) data, which are digitally collected. Digital registration provides good traceability of the transfusion cycle, from collection to blood distribution and transfusion.
Observation of Literature Survey:
The conduction of blood in rural areas is poor. The inventory management is not up to the mark. An effective, well-organized screening program and a good quality system are required for provisioning safe blood bags to patients and meeting the transfusion requirements. Several management problems are, both at a planning level (e.g., blood collection center location or staff dimensioning) and at an operational level (e.g., appointment scheduling).
Overview of Proposed Work:
Introduction:
The project provides search facilities based on various factors such as blood bank, donor, blood group, and bloodstock. It tracks all the information of blood bank, donor, blood group, and bloodstock. It is easy to understand by the user and operator. Framework for the proposed system: The project has a backend database that is managed in SQL Plus and a front-end UI in Python. The application is installed on Windows.
Module involved in your project:
Donor Module, Blood details module