“Vaccine Wallet” is a fully computerized vaccination details system to replace the vaccination card system in Sri Lanka. “Vaccine Wallet” has a simple user interface for registration and usage of the system. This enhanced online vaccination system will completely bring down the forgetting of vaccination details and time period.** “Vaccine Wallet”** also check the availability of vaccines from the hospitals and allows the user to find a location for the vaccination process.
This project contain with,
- Flutter App - For public users (Click to go to the repo)📱
- Dashboard - For hospital staff (This repo) 💻
- Flutter - Flutter is used to design the frontend of the “Vaccine Wallet” mobile app (iOS and Android).
- JS | HTML | CSS - These are used to design the Frontend of the “Vaccine Wallet” admin web interface.
- Firebase - Firebase is used to build up the database of the “Vaccine Wallet”.
The aim of this project is to research, design, activate and evaluate a digital vaccine description application for digitizing the vaccine system to make it easier to obtain information on vaccination locations, times, dates, and vaccines obtained.
The general overview of the enhanced vaccination system is represented through this diagram which is being analyzed or modeled. This diagram is easily understood as it is designed to get a basic idea of the enhanced vaccination system at-a-glance view. High-level entities and process flow of enhanced vaccination system are:
- Managing all users
- Managing all admins
- Managing all vaccine details
- Managing all notifications
- Managing stocks
The first level data flow diagram of the enhanced vaccination system is visualized in figure where the system is divided into subsystems. The first level data flow diagram is a more detailed version of the zerolevel data flow diagram of the enhanced vaccination system. Functionalities of the vaccination system are represented here by in or out data flows.
Figure above illustrates the 2nd level data flow diagram of the enhanced vaccination system. This diagram is a deeper version of the 1st level data flow diagram of the vaccination system which contains further details on vaccines, users, admins, and so on.
Above figure illustrates the ER diagram for the Enhanced Vaccination System depicting various entities, attributes, and their relationships. This diagram will be useful when designing the database of the Enhanced Vaccination System.
Below figure illustrates the Class diagram for the enhanced vaccination system where the structure of the system is depicted with classes, attributes, methods, and the relationships among objects. Classes of the enhanced vaccination system:
- System Database
- Account
- Vaccine
- Children
- Date
- Admin Account
- User Account
The "Vaccine Wallet" digitalizes the current vaccine card system. This automated system was created as a mobile application for users and a web portal for administrators. The simple user interface of “Vaccine Wallet” system makes it easy to register, examine vaccination records, and find the nearest vaccination center.
The diagram shows two main activities.
Registered users can view their vaccine records and their children vaccine records.
when user get vaccinated admin can update the system. as well as they can view users’ vaccine records. (Medical staff)
- Login to system - Admins can login using their user id and password.
- Manage Users - Admin can add or remove users.
- Manage Admins - Existing admins can add new admins.
- View Vaccine details - Admins can view users’ vaccine details (hospital staff).
- Login to system - Users can login using their National ID and password.
- Signup - Users can sign up with their preregistered national ID.
- View Vaccine details - Users can view their and their children vaccination history and next vaccination details.
Vaccine Wallet system has one centralized database for the user registration, store vaccine details and store vaccination centers.
This diagram displays the entities, attributes, and relationships of the Vaccine wallet system. The entities and attributes of the EER diagram are as follows:
- User – Age, date of birth, mobile number, NIC number and name divided as first name and last name, is a composite attribute of the user. NIC number is the primary key of the user.
- Children – Children ID (Birth certificate number), date of birth and name as first name and last name, is a composite attribute of the children. Child ID is the primary key of the children.
- Admin – Admin ID is the primary key of the here. Admin role, admin id, mobile number, and name as first name and last name is a composite attribute of the of the admin.
- Vaccine – Number of vaccines, vaccine name and vaccine id are the attributes of vaccine. Vaccine id is the primary key here.
The relationships between the entities of the EER diagram are as follows:
- One user has many children.
- Many users manage many admins.
- One admin updates many vaccines (one specific admin dedicated for the manage vaccine).
- Many users get many vaccines.
- Many children get many vaccines
Normalization is the process of organizing data in a database. This includes creating tables and establishing relationships between those tables according to rules designed both to protect the data and to make the database more flexible by eliminating redundancy and inconsistent dependency. In the NoSQL database, there are no rules of normalization to consider and follow. The reason for it is NoSQL databases don’t relationally store data. we are using Firebase store data that use NoSQL. So, there is no need to normalize our database