TABLE OF CONTENTS

I declare that this report entitled "HOSPITAL AGREEMENT SYSTEM" is my own work, except as cited in the references. This project is about developing a mobile based hospital appointment system for patients using Flutter SDK.

LIST OF TABLES

LIST OF ABBREVIATIONS

INTRODUCTION INTRODUCTION

• Patient registration and appointment scheduling is time consuming Although some variant of appointment scheduling and management system is being
• Long waiting time
• Patient no-shows

This project is important for patients as it will drastically reduce their waiting time in the hospital and increase patient satisfaction. Indirect wait time is the difference between the appointment request time and the actual patient appointment time, while direct wait time is the difference between the patient appointment time and the service receipt time.

INTRODUCTION

• Objectives
• Sub-Objectives

Adding a current patient queue so that the patient can see the patient queue for the same day appointment, which prevents the patient from showing up for an appointment with many people and reduces long outpatient waiting times. Implementing QR code so the patient can check in directly on the appointment date, reducing the need for manual queuing and check-in.

INTRODUCTION 1.3 Project Scope

• QR code check-in
• Patient queue
• Appointment reminder feature
• Chat Feature

This prevents them from making an appointment with the wrong specialist, which means they can reschedule an appointment. Plus, they don't have to do their own research on their symptoms, which can be difficult for them.

INTRODUCTION 1.4 Contribution

• Report Organization

In Chapter 3, it consists of the system design and includes UML diagrams such as use case diagram and activity diagram. Finally, Chapter 7 deals with the closing of the project, and it includes the project review, discussion and future recommendation.

LITERATURE REVIEW LITERATURE REVIEW

• Traditional Appointment Scheduling

Description Patient must make an appointment in advance or a few months before the actual date. Patient is required to fill and submit appointment forms or place identification card or appointment card in boxes and wait their turn.

Table 2.1 Summary of traditional appointment scheduling

LITERATURE REVIEW 2.2. Online Appointment System

In 2009, all public tertiary hospitals in China started using web-based appointment system (WAS) to replace the traditional registration method that had tedious waiting times and caused great stress on clinic staff [ 14 ]. In addition, [2] proposed a web-based appointment system to reduce long patient waiting time and workload for hospital staff.

Figure 2.2.2 Flowchart of outpatient registration method

LITERATURE REVIEW

The proposed work allows the patient to search for a doctor based on their location, hospital and specification of the doctors. One of the proposed features is using location services to look up nearby hospitals so you don't have to go far for a doctor's consultation, saving you time and money.

Figure 2.2.4 Flowchart for web application

LITERATURE REVIEW 2.3 Mobile-based Appointment System

The system also still requires patients to manually log in for hospital or clinic staff to search and access patients' date and medical records, which can cause delay in the appointment consultation. Moreover, the appointment scheduling procedure is based on the priority level of the patient and the system will check the appointment schedule of medical staff and suggest the most suitable appointment time based on fuzzy preferences.

Figure 2.3.4 Context Diagram of Medical Appointment Application

LITERATURE REVIEW 2.4 Summarized Table of Comparison

SYSTEM DESIGN

• System Framework

SYSTEM DESIGN 3.2 Use Case Diagram

• Use Case Explanation Register Account

Basic flow The use case describes the process where the patient and administrator register as users of the system. Patient will register an account via mobile application, hospital administrator will register account via web application.

Table 3.3 Register Account explanation

SYSTEM DESIGN Update User Profile

Once the patient confirms the choice to update, the system will update the data in the database and display the updated appointment list. Alternative flows patient deselects for deletion, the system will display the current appointment list.

Table 3.8 Update appointment explanation

SYSTEM DESIGN Set Appointment Reminders

Alternate Flow Medical receptionists enter invalid data, the system displays an error and asks to re-enter the data.

Table 3.13 Manage patient records explanation

SYSTEM DESIGN Set Up Follow-up Appointment

• Activity Diagram Register Account

SYSTEM DESIGN Sign In into system

SYSTEM DESIGN Cancel Appointment

SYSTEM DESIGN Manage Patient Records

SYSTEM DESIGN Manage Patient Appointment

SYSTEM METHODOLOGY/APPROACH 4.1 Design Specifications

• Methodologies and General Work Procedures

SYSTEM METHODOLOGY/APPROACH Requirement Analysis

Every functionality and module of the project is tested to make sure they work smoothly. The hospital appointment system will also need to be tested to prevent patients from having a slow and difficult application, which can reduce the user experience. In addition, since today's mobile devices come in different formats, the application needs to be tested on multiple formats so that it can work as planned.

However, these two phases may not be completed for the duration of the project as the application may not be placed on the Google Play Store or Apple App Store unless required.

SYSTEM METHODOLOGY/APPROACH 4.1.2 Tools to use

• Mobile Phone

It will be used to develop the front-end for both the mobile application and the web application user interface. It will be used for this project to develop, test and debug the mobile application for user or patients. It will be used to develop, test and debug the web application for hospital administrators.

It will be used to authenticate users and store data for both the mobile and web applications.

SYSTEM METHODOLOGY/APPROACH 4.1.3 User Requirements

PROPOSED METHOD/APPROACH 4.2 Timeline

PROPOSED METHOD/APPROACH

SYSTEM IMPLEMENTATION

• User Interface (Mobile Application) .1 Sign in and Registration
• Homepage
• Make Appointment

If the patient's credentials are correct, the patient will be redirected to the home page; if it is wrong, an error message will be displayed. In addition, the patient can select "View All" of the categories to see the list of categories provided as shown in Figure 5.1.5. After selecting an appointment type, it will redirect the patient to each scheduled appointment page as shown in Figure 5.1.7 or to the same day appointment page as shown in Figure 5.1.8.

After pressing the Book Appointment button, a success page will be displayed as shown in Figure 5.1.9 indicating that the appointment is booked and a confirmation email will be sent to the patient.

Figure 5.1.3 Application homepage

SYSTEM IMPLEMENTATION 5.1.4 Manage appointments

After selecting a date, the patient can press the Continue button to move the appointment to the new date. However, if the specific doctor for that date is not available, the patient will receive an email from admin to move to another convenient date.

Figure 5.1.12 Reschedule appointment

SYSTEM IMPLEMENTATION 5.1.5 Appointment Details

• Set appointment reminder

After selecting the set reminder option, the patient will be redirected to the set reminder page. After pressing done, the patient will be redirected to the reminder list page containing all appointment reminders.

Figure 5.1.14 Set appointment reminder

SYSTEM IMPLEMENTATION 5.1.7 Manage reminders

• User profile
• Appointment history

The Logout button is also at the bottom of the menu drawer to make logging out easy. The patient may be able to update their credentials here by selecting one of the fields and pressing done after verifying the credentials. After selecting the appointment, the details of the appointment, including any comments, will be displayed for the patient to see.

Figure 5.1.20 Edit profile page

SYSTEM IMPLEMENTATION 5.1.10 Chat Enquiries

• Admin Interface (Web Application) .1 Admin sign in

The administrator can login to the web application by entering a valid email and password that will be provided by the database administrator, who will also fill in their credentials. This is to prevent administrators from creating an account with fake or offensive email or credentials. Entered credentials will be validated by Firebase Authentication, an error message will be displayed if incorrect credentials are entered.

This is because the doctor and the medical receptionist both have different privileges and access to different functions.

Figure 5.2.1 Admin login

SYSTEM IMPLEMENTATION 5.2.2 Homepage

Each admin role will have different privileges, as medical receptionist will have access to the patient menu and can chat queries, while doctor will have the privilege to have the doctors and appointments menu.

SYSTEM IMPLEMENTATION 5.2.3 Profile page

SYSTEM IMPLEMENTATION 5.2.4 Add Appointments

• Doctors List

It is displayed after the doctor selects the "All doctors" option in the Doctors menu. This list is intended as a reference when doctors want to book follow-up appointments for their patients with other specialist doctors.

Figure 5.2.7 Doctors List

SYSTEM IMPLEMENTATION 5.2.6 Appointment List

SYSTEM IMPLEMENTATION 5.2.7 Add Patients

• Patients List
• Chat Inquiries
• Coding Explanation (User Mobile Application)
• Create Account
• Sign In
• Homepage
• Make Appointment

After selecting a particular patient, you will be taken to the patient details page as shown in Figure 5.2.13. If you then press one of the lists, you will be redirected to the patient chat page as shown in Figure 5.2.15. In addition, the code in Figure 5.3.6 is used to retrieve the patient's ordering data and is stored in the snapshots.

The function will first store the required data in a card, then it will add the reminder data to Firestore and update the doctor's unavailable date with the functions shown in Figure 5.3.10.

Figure 5.2.12 Patient List

SYSTEM IMPLEMENTATION 5.3.5 Manage Appointment

If the patient selects the update option, an update dialog will appear after passing a few arguments, such as appointment time and patient ID. After selecting the new updated date, the patient can select the Continue button to continue rescheduling the appointment as shown in Figure 5.3.13. The code in Figure 5.3.14 will be called to update the data in Cloud Firestore.

Then, a snack bar containing the pop-up message will be displayed to notify the patient of a successful appointment rescheduling.

Figure 5.3.13 Update appointment (1)

SYSTEM IMPLEMENTATION Cancel appointment

• Appointment Details

The image above shows the code for retrieving patient appointment data from Cloud Firestore and is retrieved from the "Appointments" collection. The system will save the obtained data in a DocumentSnapshot, which will be used to display the data. Next, the meeting data is combined into a string that will be used as the data for the generated QR code, as shown in Figure 5.2.18.

The QR code will then be displayed as shown in Figure 5.2.19 by setting the data for the QR, the size of the QR image along with the background color for the generated QR code.

SYSTEM IMPLEMENTATION 5.3.7 Appointment Reminders

SYSTEM IMPLEMENTATION Delete appointment reminder

• User Profile Edit profile
• Coding Explanation (Admin Web App)
• Sign in
• Add Appointments

The patient can select one of their profile details to request the keyboard as shown in Figure 5.2.24. After entering a new value, it will update the controller with the specific details as shown in Figure 5.2.25. Then the system will use the data stored in the QuerySnapshots to display the deal history details on the Deal History page.

The appointment details are stored in a map and then added to the "Agreement" collection using the add() method.

Figure 5.3.24 Edit profile (1)

SYSTEM IMPLEMENTATION 5.4.3 Appointment List

• Chat Enquiries

On the patient ordering page, the system will call the code as shown in Figure 5.2.6 in the initState() method. As a result, the patient's appointment information is stored in the map using add() to add the map to the list. After that, the data stored in the map is then displayed in the data table.

Then on the patient appointment details page, the appointment details such as patient name and ID, appointment date and time are passed as arguments and displayed.

Figure 5.4.6 Retrieve Patient Appointment Data

SYSTEM TESTING 6.1 Unit Testing

• User and Admin Authentication Test

SYSTEM TESTING

• User Appointment Module Test

SYSTEM TESTING 6.1.3 User Reminder Module

• User Profile Module Test

SYSTEM TESTING 6.1.5 Admin Module (Doctor)

• Admin Module (Medical Receptionist) Test

Action: Enter the doctor list page. The system should display the list of doctors with brief details. Action: Enter the patient list page. The system should display the doctor's patient list. Action: Enter the patient details page. The system should display the details of specific patients.

Action: Go to the chat request list page. The system should display a list of chat request ID numbers.

Table 6.5 Admin medical receptionist module test case

CONCLUSION AND RECOMMENDATION CONCLUSION AND RECOMMENDATION

• Future Recommendation

In addition, a feedback and rating system can be added to further strengthen the credibility of the hospital appointment system. Sait, “Application of smart technologies for mobile patient appointment system,” International Journal of Advanced Trends in Computer Science and Engineering, vol. Sankaranarayanan, "Application of Intelligent Agents in Hospital Appointment Scheduling System," International Journal of Computer Theory and Engineering, vol.

Roomi, “5 Advantages and Disadvantages of a Client Server Network | Disadvantages and advantages of a client-server network,” www.hitechwhizz.com, Nov.

FINAL YEAR PROJECT WEEKLY REPORT

• WORK DONE
• WORK TO BE DONE
• PROBLEMS ENCOUNTERED No problem encountered
• SELF EVALUATION OF THE PROGRESS Slow progress
• PROBLEMS ENCOUNTERED No problem encountred
• SELF EVALUATION OF THE PROGRESS I am still on track
• PROBLEMS ENCOUNTERED
• SELF EVALUATION OF THE PROGRESS
• SELF EVALUATION OF THE PROGRESS I am on track and plan to proceed to report writing
• SELF EVALUATION OF THE PROGRESS Planning to complete everything before due date

I have completed the draft design of the admin webapp interface and have moved on to finalizing the webapp user interface. SELF-ASSESSMENT OF PROGRESS I am on track and planning to move on to report writing. Note: Supervisor/candidate(s) are required to provide a soft copy of the full set of the originality report to the faculty/department.

Based on the above results, I hereby declare that I am satisfied with the originality of the end-of-year project report submitted by my student(s) as stated above.

UNIVERSITI TUNKU ABDUL RAHMAN