The Blood Testing Application is a comprehensive platform designed to manage the entire lifecycle of blood testing processes. It facilitates interactions between various stakeholders, including patients, technicians, lab personnel, and regulatory bodies.
- Appointment Scheduling: Users can book blood test appointments.
- Sample Collection Management: Technicians can update sample collection status.
- Laboratory Testing: Lab technicians can perform tests and update results.
- Result Approval: CDC can review and approve test results.
- Inventory Management: Track and manage testing equipment and supplies.
- Reporting: Generate system-wide performance and data reports.
- Programming Language: Java
- User Interface: Java Swing
- Database: db4o (object-oriented database)
- Email Integration: JavaMail API
- Design Pattern: Model-View-Controller (MVC)
- Authentication: Role-based access control
- Data Persistence: Object-oriented database (db4o)
- User Interface: Desktop application using Java Swing
- User registers and schedules an appointment
- Sample technician collects the sample and updates status
- Lab technician performs the test and records results
- CDC approves the results
- User can view their test results
- Role-based authentication
- Secure password storage
- Data encryption for sensitive information
- The application is designed to handle multiple enterprises and organizations
- Efficient data retrieval using object-oriented database
- Integration with external laboratory systems
- Mobile application for users
- Advanced analytics and reporting features
- A running swing application that addresses the challenges outlined aboveat an eco-system scale. A typical implementation must include the participation of at least 4 enterprises, 4-8 organizations, and 4-6 roles.
- A presentation that outlines details specific to the design and implementation of your solution. This must include, the definition of the problem you solved, stakeholder and their contributions,use-cases, design, and implementation techniques followed. You must explain why each enterprise is essential to delivering the total value as outlined in your problem statement.
- A robust role-based authentication module with strong user name and password capabilities.
- A reporting module with summarized view of the data in your system. This could include performance data that is important at the system or network level.
- A configuration module with test cases that will populate your model and show the correctness of your solution. You might want to integrate with a Faker module from faker.com for random data generation.
- add the jar files in (home)Libraries folder to the (blood-work)libraries within the bloodwork project for db4o and javax/mail
- clean and build the project again
-Qwerty1 / Qwerty@123
- creates an appointment with platform for a blood test (chooses from four types of blood test)
- Tracks the status on their test and view past tests as well
-Qwerty2 / Qwerty@123
- Can see all registered users and appointment details with associated personnel
- Can delete / enable user
-Qwerty3 / Qwerty@123
- Collects sample from user and updates user testing status
- clears the sample to be forwarded to lab
- Can place orders for equipments
- Updates workqueue
-Qwerty4 / Qwerty@123
- Carries out test relevant and updates the status
- Can view past status
- Can place orders for equipments
- Updates workqueue
-Qwerty6 / Qwerty@123
- Releases slots for new appointments
- Manages existing appointments
- Updates workqueue
-Qwerty5 / Qwerty@123
- Manages employee from testing enterprise
-Qwerty8 / Qwerty@123
- Approves the associated testing result
- Updates workqueue
-Qwerty10 / Qwerty@123
- Handles incoming orders from employees and fulfills them]
- Handles refilling inventory
-Qwerty7 / Qwerty@123
- Has overview over appointment statuses and details
- Has overview over employees as well