Introduction
- Problem Statement and Motivation
- Project Scope
- Project Objective
- Impact, significance and contribution
- Background information
- Report Organization
So this system has eliminated all manual processes and all documents will be digitized. TB is also one of the top ten causes of death and the leading cause of a single infectious disease (Anon, 2018). According to the World Health Organization (WHO), about one third of the world's population had a latent tuberculosis infection.
The TB Skin Test is performed by injecting a small volume of tuberculin (fluid) into the inner surface of the forearm. Most of the labs keep the result in manual paper file, also a lot of storage is required to store these documents. Finally, the conclusion of the whole project and the future work of the system are described in Chapter 7.
Literature Review 2.1 Review on similar system
Image Computer Laboratory Information Management System (iLIMS) The case study is on the Image Computer Laboratory Information
Before the patient report can be printed, the report must first be authorized via second-level authorization. In this module, the selected test report is ready to be printed, which is shown for final authorization. The user can select more than one test and the user can also preview the selected test result before going to the final authorization.
The system provided a complete user defined report format, the user can set the report printing order and have multiple report formats based on the test.
Tuberculosis Information Management System (TBIMS)
The system had built in the quality control functions to improve the quality of data such as the timeliness and accuracy of the data. Therefore, the user must request permission from the supervisor to edit the data that has been entered to avoid accidental edits to the data shown in Figure 2.1.2.1. TBIMS and IDRS are interconnected to facilitate the process of real-time data exchange.
TB cases in China must report cases to IDRS within 24 hours. Once cases are updated in IDRS, staff at TB health facilities can alert the interface linking IDRS and TBIMS.
Features Hotspot Map
System Design 3.1 System Design
The skin/blood test module is used by the nurse who answered the skin test and the blood test. The nurse can search the relevant patient record with IC number or passport number. The nurse will therefore carry out the skin test/blood test and record the test carried out.
After the result is known, the nurse will insert the test data and the test result. With a skin test, the nurse records the test data, such as the diameter of the induration, the injection performed in the left/right arm and the test result. For the blood test, the nurse records the important test data, such as the type of blood test and the test result.
Test Module
System Flow Diagram
- General Flow Diagram (non-system flow chart)
- System Flow Diagram (Maintenance Module)
- System Flow Diagram (Reception Module)
- System Flow Diagram (Skin/Blood Test Module)
- System Flow Diagram (Chest X-Ray Test Module)
- System Flow Diagram (Smear/Culture/ DST Test Module)
- System Flow Diagram (Treatment/Analysis and Reporting Module)
The general flow chart (as below) describes the procedures for people going through the TB testing process.
Entity Relationship Diagram (ERD)
Data Dictionary
Design Specification 4.1 Methodology involved
- Project Phase 1. Planning Phase
- Analysis Phase
- Design Phase
- Implementation Phase
- System Prototype
- System
- Tools for Developer
- User Requirements
- User requirements
- Implementation Issue and Challenges
- Timeline
A prototype model starts with a best understanding of the requirement and the requirements of the system must be defined in detail. An interview session will be held to know the requirements of the system and also to know the user's needs and wants. In this phase, examine and study the information to determine who will use the system, what can use the system, when and where the system operates.
In this phase, a preliminary design or rapid design is created for the system, which will give the user an idea of the system. The Entity Relationship Diagram (ERD) will be designed to build the database structure for the system and create a description table to allow users to have a "current view" of the system's interface design. The prototype will give the user a "current view" of the system and the user can provide feedback to the developer.
The final system is assembled when all feedback and reviews from the user have been collected, the final system is usually created based on the latest or final prototype model. HTML5 and CSS3 as a front-end language for structuring system elements and at the same time styling all elements to make the system more user-friendly. The processor and RAM of the PC/Laptop must be in standard performance as multiple programs such as XMAPP and Visual Studio Code can be open at the same time.
The PC/Laptop can also test the basic function of the system and troubleshoot the system. 4 GB of RAM and an Intel Core i3 (minimum) device ensure system performance. Another difficulty in implementation will be the collection of requirements, as some data or information is difficult to obtain in a journal or online article and takes a long time to discover.
It is important to have an accurate timeline to track the progress of the project and to know the end date of the task to be completed, the timeline also shows the duration of each task.
System Implementation 5.1 Setup and Configuration
- Download XAMPP Apache Server
- Install XAMPP Apache Server
- Login Module
- Administrator Module
- Receptionist Module
- Skin/Blood Test Module
- Chest X-Ray Test Module
- Lab Scientist Module
- Collection Sample Sputum Test
- Smear & Culture Test
- DST Test
- Doctor Module
After the radiologist clicks the "Submit" button, a window will be prompted as shown in Figure 5.6.9 below. After the lab researcher clicks the “Submit” button, a window will be prompted as shown in Figure 5.7.1.7 below. After the lab researcher clicks the “Submit” button, a window will be prompted as shown in Figure 5.7.2.7 below.
After the lab scientist clicks the Submit button, a window will appear as shown in Figure 5.7.3.7 below.
System Testing 6.1 Login Module Testing
- Maintenance Module Testing
- Manage User Account Function Testing
- Reception Module Testing Table Table 6-4-1 Reception Module Testing Table
- Common Function in Dashboard - Function Testing Table 6-5-1 Common Function in Dashboard - Function Testing Table
- Common Function in History Report - Function Testing
- Skin/Blood Test Module Testing
- Chest X-Ray Test Module Testing
- Lab Scientist - Sputum Sample Module Testing
- Lab Scientist - DST Test Module Testing
- Doctor Module Testing
Discussion and Conclusion
- Project Overview
- System Strengths and Limitations
- Future Work
- Conclusion
The TB Diagnosis Laboratory Information System (Skin/Blood Test Module) at the same time provides automatic results derived from the input parameter in previously which potentially reduces the possibilities of wrong data insertion incident. Apart from the analysis mentioned in chapter 3.1, one of the feature functionalists called 'TB Diagnosed Pin Maps', this feature function will graphically represent all the TB diagnosed patients using 'Google Maps' to locate patients. Users using this feature function can have information of all the TB diagnosed patient's current location and further perform some surveillance prevention actions based on this location's address (Pin shows in the map).
Furthermore, the design of the TB Diagnostic Laboratory Information System is based on end-user requirements, the user may come up with new requirements due to the continuous development of new drugs or new treatment. Thus, the TB data analysis section is still under development, there are still shortcomings that can be improved. Mykad Card Scanner can be applied to support system efficiency. Since the Malaysian Identity Card is the method for the patient to register, the Mykad scanner will be useful for registration.
The current proposed TB system provided the fundamental concepts and development of the TB information system. The functionalists of the maintenance module can be increased as the current system only supports basic insert, delete (deactivate user), update (modify/activate user). Although the current system provides some of the functionality that presents the TB data graphically using the bar graph, line graph, table and Google Maps to the user.
However, data analysis is not an easy path, it required a lot of study and patient to discover additional useful tools or tools that can be united with TB Diagnosis Laboratory Information System to analyze and present this useful data to the relevant user. The lack of early detection and prevention of the TB disease promotes the TB cases that have occurred worldwide and is becoming a serious global health problem. At the end of this project, this proposed system can help to reduce the annual risk of TB and the implemented feature will help to solve the problem of TB diagnostic laboratory.
I hope that the TB Diagnostic Laboratory Information System is expected to act as a useful tool for the TB medical domain to help solve the TB disease problem.
Plagiarism Check
FINAL YEAR PROJECT WEEKLY REPORT
- WORK DONE
- WORK TO BE DONE
- PROBLEMS ENCOUNTERED
- SELF EVALUATION OF THE PROGRESS
- SELF EVALUATION OF THE PROGRESS I think the progress of the project overall is good
I think the progress in this system is quite slow because we still have a lot of work to do. We had made some changes to our system based on Miss Saw's suggestions and feedback. We need to change the skin test and blood test module, if the result is negative, at the admission table it will automatically use adm_result = negative otherwise it will pass the patient's data for the following test.
Progress is slower than a few weeks before. We need to spend more time catching up to complete the final year project before the deadline. We had met Miss Saw, we just had to keep the x-ray normal as image format. Therefore, if the sputum sample cannot be used, it will collect it together with the patient to perform the next test.
Progress is slower than a few weeks ago, I have to spend more time catching up to finish my final year project before the deadline. Meet with Miss Yap to report on the progress of our system and complete the doctor's module. So meet with Miss Saw for the data analysis part to understand what information needs further processing. We have already met with Ms. Saw and understood what we need to do for analysis.
Miss Yap has given us some feedback about our system, we need to make some changes in our system, such as display the result at the bottom and move the result definition to the right side. Thus, we must also complete the doctor module which is the last module in our system. Complete the coding for the analysis section in the doctor module and complete the full report.
Fix the bugs in the system and try to complete the report within this week.
UNIVERSITI TUNKU ABDUL RAHMAN FACULTY OF INFORMATION & COMMUNICATION
TECHNOLOGY (KAMPAR CAMPUS)
