NITC TELEHEALTH APPLICATION

PROJECT REPORT

submitted
by

Abhijeet Kumar Singh (M190675CA)

In partial fulfillment for the award of the Degree of

MASTER OF COMPUTER APPLICATION

Under the guidance of

Ms. Anu Mary Chacko

Assistant Professor

(Dept. of Computer Science and Engineering, NIT Calicut)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

NATIONAL INSTITUTE OF TECHNOLOGY CALICUT

NIT CAMPUS PO, CALICUT

KERALA, INDIA 673601

MAY 2022
ACKNOWLEDGMENT

It gives me a great sense of pleasure to present the report of the Project Work
undertaken during MCA, Final Year. I owe special debt of gratitude to my Project
Owner and Guide Ms Anu Mary Chacko, Assistant Professor, Department of
Computer Science and Engineering, National Institute of Technology, Calicut for
her constant support and guidance throughout the course of my work. It is only her
cognizant efforts that my endeavors have seen the light of the day.

Abhijeet Kumar Singh

M190675CA
DECLARATION

I hereby declare that the project titled, NITC TeleHealth Application, is my own
work and that, to the best of my knowledge and belief, it contains no material
previously published or written by another person nor material which has been
accepted for the award of any other degree or diploma of the university or any
other institute of higher learning, except where due acknowledgement and
reference has been made in the text.

Place: NIT Calicut Name: Abhijeet Kumar Singh

Date: Reg. No.: M190675CA

________________
Signature
NATIONAL INSTITUTE OF TECHNOLOGY CALICUT
KERALA, INDIA - 673 601

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE

Certified that this is a bonafide report of the project work titled

NITC TELEHEALTH APPLICATION

done by

Abhijeet Kumar Singh

of Sixth Semester MCA, during the Winter Semester 2021-’22, in partial

fulfillment of the requirements for the award of the degree of Master of
Computer Applications of the National Institute of Technology Calicut.

Ms. Anu Mary Chacko

Department of CSE
May, 2022 Project Guide
ABSTRACT

The project entitled “NITC TeleHealth Application” is designed and developed in

Flutter which uses Dart programming language for its frontend and backend is
designed in MongoDB with APIs written in Nodejs. The purpose of the project is
to implement an online appointment booking system for nitc students, faculty and
staff members. Users can also cancel and reschedule their appointments.
Table Of Contents

1. INTRODUCTION 1
1.1 Problem Definition 1
1.2 Product Scope 1
1.3 Intended Audience 2
1.4 Definitions, Acronyms and Abbreviations 2

2. OVERVIEW 3
2.1 Product Overview 3
2.2 Product Functionality 3
2.2 Design and Implementation Constraints 4
2.4 Assumptions and Dependencies 4
3. REQUIREMENT SPECIFICATION 5
3.1 Use Cases of all Users

3.1.1 Use Case #1 Login(Admin, doctor, Patient) 5

3.1.2 Use Case #2 Add User (Admin, doctor, Patient) 6
3.1.3 Use Case #3 Remove User (Admin, doctor, Patient) 6
3.1.4 Use Case #4 Create Schedule for Doctors 7
3.1.5 Use Case #5 Print Medical Certificate 8
3.1.6 Use Case #6 Appointments canceled by doctor 9
3.1.7 Use Case #7 Accept Medical Leave Request 10
3.1.8 Use Case #8 Appointment History 10
3.1.9 Use Case #9 Book Appointment 11
3.1.10 Use Case #10 Cancel Appointment By User 12
3.1.11 Use Case #11 Medical Leave Request 13
3.1.12 Use Case #12 Forgot Password 14

4. METHODOLOGY AND DESIGN 15

4.1 Data Modeling Diagram 15
4.2 Use Case Diagram 16
4.3 Static Snapshot of System - Object Diagram 17
4.4 System Interaction through sequence diagram 18
4.4.1 Login Sequence 18
4.4.2 Book Appointment and cancel appointment 19
4.4.3 Request Medical Leave 20
4.5 Control and Data Flow through activity diagram 21
4.5.1 Login Activity 21
4.5.2 Book Appointment Activity 22
4.5.3 Cancel Appointment Activity 23
4.5.4 Request Medical Leave Activity 24
5. IMPLEMENTATION 25
5.1 Technology Stack 25
5.1.1 Frontend 25
5.1.2 Backend 25
6. RESULTS 26
6.1 Testing Phase 26

7. CONCLUSION 37
REFERENCES 38
List of Figures

3.1 Data Modeling Diagram 15

3.2 Use Case Diagram 16
3.3 Static Snapshot of System - Object Diagram 17
3.4.1 Login Sequence 18
3.4.2 Book Appointment and cancel appointment 19
3.4.3 Request Medical Leave 20
3.5.1 Login Activity 21
3.5.2 Book Appointment Activity 22
3.5.3 Cancel Appointment Activity 23
3.5.4 Request Medical Leave Activity 24
6.1.1 Test Case #1 Login(Admin, doctor, Patient) 26
6.1.2 Test Case #2 Add User (Admin, doctor, Patient) 27
6.1.3 Test Case #3 Remove User (Admin, doctor, Patient) 28
6.1.4 Test Case #4 Create Schedule for Doctors 29
6.1.5 Test Case #5 Print Medical Certificate 30
6.1.6 Test Case #6 Appointments canceled by doctor 31
6.1.7 Test Case #7 Accept Medical Leave Request 32
6.1.8 Test Case #8 Appointment History 33
6.1.9 Test Case #9 Book Appointment 34
6.1.10 Test Case #10 Cancel Appointment By User 35
6.1.12 Test Case #12 Forgot Password 36
NIT Calicut, MCA 2019

Chapter 1

INTRODUCTION

The aim of the project is to develop a telehealth application for the students, staff
and faculty of NITC while they use NITC health center. Current process is paper
based and automating the process will improve the user experience.

The process for booking appointments, rescheduling appointments, canceling the

appointments, and request for medical leave for the students of NITC.

1.1 Problem Definition

To build an online app to manage telehealth consultation by doctors in NITC health

center for NITC staff and students

1.2 Product Scope

The scope of this project is to create an online platform for NITC students to make
appointments to doctors for their health checkup. This application will allow its
users (NITC students, faculty and staff members) an easy way to book an
appointment, reschedule it, and allow students to request for medical leave. This
app will allow them to book an appointment with a doctor according to their issues
and each week specialist doctors will also be there for particular problems. All the
other activities of NITC and Health Center are out of scope.

1
NIT Calicut, MCA 2019

1.3 Intended Audience and Document Overview

This document is intended for all the designers, developers, coders, project manager,
testers and all the stakeholders who are directly or indirectly involved in this project. The
reader is assumed to have basic knowledge of mobile UI/UX, databases and user
accounting along with knowledge and understanding of Use-case diagrams. The project
manager will read this document and check whether all the specifications required by the
client are present in the Telehealth Application design.

1.4 Definitions, Acronyms and Abbreviations

​ DB : Database
​ NITC : National Institute of Technology, Calicut
​ IEEE : Institute of Electrical and Electronics Engineering
​ GUI : Graphical User Interface
​ HTTP : Hypertext Transfer Protocol
​ CSS : Cascading Style Sheet
​ ID : Identity
​ API : Application Program Interface
​ UI : User Interface
​ US : Use Case

2
NIT Calicut, MCA 2019

Chapter 2

OVERVIEW

2.1 Product Overview

In this era of the Internet, where everything is moving towards online platforms
and each facility is available in one click. "NITC Tele Health Application" will
help students, faculty and staff to book appointments with NITC health center
doctors, rescheduling appointments and records management for previously
booked appointments.
This Application has a flow like, There are three users of the application
Admin, Doctor and patients(students). First Admin will register Doctors and
students to the application and send their login credentials to them. A student login
to the application then it requests for appointment by selecting what type of
problem he/she is facing, then according to the doctor schedule for morning,
afternoon and evening timings, a list of available slots will be visible to the user.
Each slot is 15 mins. After selecting an available slot after clicking on the
“Confirm Book” button, to book the slot. The user is also able to see a list of all its
previous bookings and the doctor will also be able to see all the past appointments.
In case, when the doctor won’t be able to take the appointments then he can cancel
appointments of that slot and the user will get notified that their appointments are
canceled and they have to again book another slot. Users can also reschedule its
appointments by simply canceling the upcoming appointment and then book
another slot at some other time. The Application will also allow its users to take a
medical leave certificate, if his condition is serious and needs to be admitted in
hospital. By this way the application has automated processes that are related to
appointment booking, rescheduling and cancellation.

2.2 Product Functionality

There are various functionality of this product depending upon the role of user-

1. Admin Functionality
​ Login Page
​ Add Admin, Doctor, Patient(NITC students, faculty and staff)

3
NIT Calicut, MCA 2019

​ Remove Admin, Doctor, Patient

​ Create Schedule
​ Print medical leave certificate

2. Doctor Functionality
​ Cancel Appointment
​ Accept Medical Leave
​ Appointments History

3. User Functionality
​ Book Appointment
​ Cancel Appointment
​ Medical leave request
​ Forget Password

2.3 Design and Implementation Constraints

This application will be using Nodejs (JavaScript) as the backend language and
Flutter in frontend for UI/UX design.
Here, I am using GIT version control to properly and concurrently develop
the application and use all the helpful features of GIT like staging area, commit it,
push etc. This will help in continuous and smooth development for the project.
MongoDB is a fast and reliable database that supports dynamic queries on
documents using a document-based query language. It handles large volumes of
data at high speed with a scale-out architecture.
This application also needs a reliable server for hosting as the application is
used by many students and faculties at the same time.

2.4 Assumptions and Dependencies

We have made the following assumptions:

● The intended user and doctor of the application must be a part of NITC, that
is they should have a unique ID given by NITC.
● Admin will deal with the reports that will be given by the users if someone is
not behaving appropriately with them.
● Network and data availability.
● It requires proper internet connection to request an appointment

4
NIT Calicut, MCA 2019

Chapter 3

REQUIREMENTS SPECIFICATION

3.1 Use Cases of all Users

3.1.1 Use Case #1 Login( Admin, Doctor, Patient)

Author : Abhijeet Singh

Purpose : The purpose of this test case is to get access to the application. The
user will provide its credentials to get access.

Priority : High

Precondition : The user has to enter the credentials to get logged to the account.

Post Condition : This will give the user access to the software.

Actors​: Human (Admin, Doctor, Student).

Extends : Verification of user's entered credentials

Flow of Events
◦ Basic Flow: The user will enter his/her email id, password, and role
(Admin, doctor, Student) to the system. If the credentials are correct the
user will be logged in to his account.
​
◦ Alternate Flow: If the credentials are invalid then an error message is
displayed.

5
NIT Calicut, MCA 2019

3.1.2 Use Case #2 (Add User - Admin, doctor, Patient)

Author : Abhijeet Singh

Purpose : The purpose of this test case is to allow admin to register any new user
to the application.

Priority : High

Precondition : Admin should be logged in to the application, to register any new

user.

Postcondition : Admin will see a successfully registered message, after user data
is saved in the database.

Actor : Admin(Human)

Extends : None.

Flow of Events:

■ Basic flow: Admin first selects the type of user( admin, doctor,
patient ) then according to that he will write user data and then
submit it. If the user data is not present in the system then it gets
successfully saved and gives a message " User added successfully'' .

■ Alternate Flow : If the user data already existed into the database
then it will give an error message "User Exist".

3.1.3 Use Case #3 ( Remove User - Admin, doctor, Patient)

Author : Abhijeet Singh

Purpose : The system will allow the admin to remove any user from the
application.

6
NIT Calicut, MCA 2019

Priority : Low

Precondition : The user's data should be present in the application and admin
should be logged in.

Post Condition : User's data is successfully deleted from the application.

Actors​: Admin(Human).

Extends : None.

Flow of Events
○ Basic Flow: The admin will give the user's Email ID and and click on the
"Search User" button to fetch details of the user. Once admin verifies the
user selected is correct. then it will click on the "Remove User" button to
delete data.

○ Alternate Flow: If no such email id is present in the application database

then it will show an error message "No such user exists, check email id !..".

3.1.4 Use Case #4 ( Create Schedule for Doctor)

Author : Abhijeet Singh

Purpose : The system will allow the admin to create schedule of each doctor that
is registered to the application.

Priority : High

Precondition : The Admin should be logged in to the application and the doctor
should be registered to the application.

Post Condition : Message pops up with "Schedule is successfully saved for

Doctor".

Actors​: Admin(Human).

Extends : None.

7
NIT Calicut, MCA 2019

Flow of Events
● Basic Flow: The admin will write details of the doctor and his time
interval for morning, afternoon and evening schedules for each day. If data
is successfully saved without any error then a success message pops up.
“Successfully Saved Schedule”.
Once the schedule creation code is executed, for each time interval
(morning, afternoon and evening) of the day slots of 15 minutes is created
automatically and users will be able to book those slots for appointments.

● Alternate Flow: If schedule is not created by the admin, then slots are also
not created and no appointments will be visible to the user.

3.1.5 Use Case #5 ( Print Medical Certificate)

Author : Abhijeet Singh

Purpose : The system will allow the admin to print medical certificate for the
student who has a serious medical condition.

Priority : High

Precondition : The doctor's have accepted the medical leave request and he should
have receipt of bill that he paid in the accounts department.

Post Condition : After Successful verification of submitted document, the

students will get his medical certificate.

Actors​: Admin(Human).

Extends : None.

Flow of Events
○ Basic Flow: The admin will check if the doctor had accepted his medical
leave request in the system then he checks for bill paid receipt. If both are
correct, the admin will accept the request and update it in the app and he
will get his medical leave certificate.

8
NIT Calicut, MCA 2019

○ Alternate Flow: If the admin finds that any of the provided documents by
the student have faults then his request is canceled and he again needs to
apply for it again with correct documents.

3.1.6 Use Case #6 (Appointments canceled by doctor )

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to allow doctor to cancel its all
appointments that lie in a particular date and time slot.

Priority : Medium

Precondition : The doctor should be logged in to application and they should

have scheduled appointments on that date and time.

Postcondition : Appointment will be canceled in that time slot.

Actor : Doctor(Human)

Extends : Booked Appointments.

Flow of Events:

○ Basic flow:
■ The doctor logged in to the application and moved to the "List
Appointment" page.
■ They need to give a date to check the list of appointments on that
particular date.
■ After that it will select the slot which he wants to cancel and click on
the “Cancel Appointment” button to cancel the appointment.

○ Alternate Flow : To remove previous data, doctor can click on “Reset”

button to refresh the page

9
NIT Calicut, MCA 2019

3.1.7 Use Case #7 ( Accept Medical Leave Request )

Author : Abhijeet Singh

Purpose : The purpose of this page is to allow the doctor to approve or reject
users medical leave requests.

Priority : High

Precondition : The doctor and user should have an appointment.

Postcondition :User Medical leave request accepted.

Actor : Doctor(Human)

Extends : None.

Flow of Events:

○ Basic flow: The doctor fills user details and writes his medical condition in
the application and then clicks on submit to accept his leave request.

○ Alternate Flow : None

5.1.8 Use Case #8 ( Appointment History)

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to show appointment history to the

doctor.

Priority : Medium

Precondition : The doctor should be logged in to the application

Postcondition : The doctor will see the appointment history of the patients.

10
NIT Calicut, MCA 2019

Actor ; Doctor(Human)

Extends : None.

Flow of Events:

○ Basic flow: The doctor will login to the application and then move to the
List appointment page to check all the details of his appointments. They can
give the date to check the list of all appointments on that date.

○ Alternate Flow : If no appointments are there, the page will be blank for
that person,

3.1.9 Use Case #9 ( Book Appointment )

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to allow users(student) of this

application to book an appointment.

Priority : High

Precondition : The user should be registered to the application and logged in to it.

Postcondition : Appointment is booked successfully.

Actor : User(Human)

Extends : User Verification.

Flow of Events:

○ Basic flow:
■ The user first login to the application and then move to the book
appointment page.

11
NIT Calicut, MCA 2019

■ From the given options, according to their issue, they will select the
option.
■ Then the user will give the date and time of day of his choice for
appointment.
■ From the list of slots it will select one and click on “Register” button
to book an appointment.

○ Alternate Flow : If the selected slot is already booked then an error

message will be shown "Already booked".

3.1.10 Use Case #10 ( Cancel Appointment by user)

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to allow the user to cancel his
appointment.

Priority : Medium

Precondition : The user should be logged in to the application.

Postcondition : User will get notification if his request is accepted or not.

Actor : User(Human)

Extends : None.

Flow of Events:

○ Basic flow: The user first logs in to the application then moves to the
cancel appointments page. There, he will see his appointments. User will
select the appointment and click on cancel appointment to confirm his
cancellation.
○ Alternate Flow : None.

12
NIT Calicut, MCA 2019

3.1.11 Use Case #11 ( Medical Leave Request)

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to allow its user to request for
medical leave.

Priority : Medium

Precondition : The user should be logged in to the application.

Post condition : User will get Medical leave certificate from Admin in person.

Actor ; User(Human)

Extends : None.

Flow of Events:

○ Basic flow: The user will login to the application then go to “Book
Appointment ” page then select the Medical leave request card and then
book an appointment with the doctor.

○ Alternate Flow : None.

3.1.12 Use Case #12 ( Forgot Password)

Author : Abhijeet Singh

Purpose : The purpose of this functionality is to allow its user to request for
medical leave.

Priority : Medium

Precondition : The user should be logged in to the application.

13
NIT Calicut, MCA 2019

Post condition : Registered user will get a password reset on the link on his mail.

Actor ; User(Human)

Extends : None.

Flow of Events:

○ Basic flow: The user will directly move to Forgot password page and give
his registered mail in it then click on submit button. If he is registered then
he will get a successful message.
○ Alternate Flow : Error generated.

14
NIT Calicut, MCA 2019

Chapter 4

METHODOLOGY AND DESIGN

4.1 System model using Class Diagram(Data Modeling Diagram)

Class Diagram in the Unified Modeling Language is a type of static structure
diagram that describes the structure of a system by showing the system’s
classes, their attributes, operations (or methods) and the relationships among
classes.

15
NIT Calicut, MCA 2019

4.2 Responsibilities - Usecase Diagram

16
NIT Calicut, MCA 2019

4.3 Static snapshot of the system - Object Diagram

17
NIT Calicut, MCA 2019

4.4 System Interactions through Sequence Diagrams

Sequence diagrams are interaction diagrams that show the sequence of
messages exchanged by the set of objects performing a certain task. A
sequence diagram shows, as parallel vertical lines (lifeline), different
processes or objects that live simultaneously, and as horizontal arrows, the
messages exchanged between them, in the order in which they occur.

4.4.1 Login Sequence

● For the first time, users will start the application and they will be directed to
the login page automatically.
● User will write his registered email and password given to him by the admin.
● The application will search for that user having the same email address and
password and whether it belongs to the entered category or not.
● If it matches then the user will be redirected to the dashboard of the
application.
● Otherwise it will generate an error message “email or password is incorrect”.

18
NIT Calicut, MCA 2019

4.4.2 Book Appointment and Cancel Appointment Sequence

Book Appointment Sequence:
● First the user(student, faculty and staff) login to the application.
● The user will then select the category of his problem from the given list of
categories.
● Select Date, part of day(morning, afternoon or evening) then select the slot
available according to his convenience.
● Click on the Book Appointment button to confirm the appointment with the
doctor.

Cancel Booked Appointments Sequence:

● Click on Cancel Appointment option to view the list all his the booked
appointments,
● From the list of booked appointments select that appointment which you
want to cancel.
● Click on Confirm cancel appointment button to cancel appointment.

19
NIT Calicut, MCA 2019

4.4.3 Request medical Leave Sequence

● First the user will login to the application and book an appointment with the
doctor to request for medical leave.
● Doctor will check, then approve or reject it and update it to the application
through the “Accept medical leave” page.
● Then the user will pay the challan to the accounts department for medical
leave and then book an appointment with admin.
● Admin will verify the doctors approval from application and challan.
● If everything is fine then he accepts the request and prints the medical leave
certificate and gives it to the user.

20
NIT Calicut, MCA 2019

4.5 Control and Data Flows through Activity Diagrams

● ACTIVITY DIAGRAM is basically a flowchart to represent the flow from
one activity to another activity. The activity can be described as an operation
of the system. The basic purpose of activity diagrams is to capture the
dynamic behavior of the system. It is also called object-oriented flowchart.
● This UML diagram focuses on the execution and flow of the behavior of a
system instead of implementation. Activity diagrams consist of activities
that are made up of actions that apply to behavioral modeling technology.

4.5.1 Login Activity

21
NIT Calicut, MCA 2019

4.5.2 Book Appointment Activity

22
NIT Calicut, MCA 2019

4.5.3 Cancel Booked appointment Activity

23
NIT Calicut, MCA 2019

4.5.4 Request Medical Leave Activity

24
NIT Calicut, MCA 2019

Chapter 5

IMPLEMENTATION

5.1 Technology Stack

5.1.1 FrontEnd

● Programming Language: Dart Programming

● Development Environment: Flutter UI Toolkit

5.1.2 BackEnd
● BackEnd Runtime Environment: Node.js
● Database: MongoDB Atlas
● Backend deployed: Heroku Cloud Platform

25
NIT Calicut, MCA 2019

Chapter 6

RESULTS

6.1 Testing Phase

6.1.1 Test Case #1 Login( Admin, Doctor, Patient)

Flow of Events
◦ Basic Flow: The user will enter his/her email id, password, and
role (Admin, doctor, Student) to the system. If the credentials are
correct the user will be logged in to his account.
​
◦ Alternate Flow: If the credentials are invalid then an error
message is displayed.

Test- case:

User is registered email or password is wrong

26
NIT Calicut, MCA 2019

6.1.2 Test Case #2 (Add User - Admin, doctor, Patient)

Flow of Events:

■ Basic flow: Admin first selects the type of user( admin, doctor,
patient ) then according to that he will write user data and then
submit it. If the user data is not present in the system then it
gets successfully saved and gives a message " User added
successfully'' .

■ Alternate Flow : If the user data already existed into the

database then it will give an error message "User Exist".

Test Case:

User is Unique User already exists

6.1.3 Test Case #3 ( Remove User - Admin, doctor, Patient)

Flow of Events
○ Basic Flow: The admin will give the user's Email ID and and click on
the "Search User" button to fetch details of the user. Once admin
verifies the user selected is correct. then it will click on the "Remove
User" button to delete data.

27
NIT Calicut, MCA 2019

○ Alternate Flow: If no such email id is present in the application

database then it will show an error message "No such user exists,
check email id.".

Test Case:
User data exists user not registered

6.1.4 Test Case #4 ( Create Schedule for Doctor)

Flow of Events
● Basic Flow: The admin will write details of the doctor and his time
interval for morning, afternoon and evening schedules for each day. If
data is successfully saved without any error then a success message
pops up “Successfully Saved Schedule”.
Once the schedule creation code is executed, for each time
interval (morning, afternoon and evening) of the day slots of 15
minutes is created automatically and users will be able to book those
slots for appointments.

● Alternate Flow: If schedule is not created by the admin, then slots

are also not created and no appointments will be visible to the user.

28
NIT Calicut, MCA 2019

Test Case:

6.1.5 Test Case #5 ( Print Medical Certificate)

Flow of Events
○ Basic Flow: The admin will check if the doctor had accepted his
medical leave request in the system then he checks for bill paid
receipt. If both are correct, the admin will accept the request and
update it in the app and he will get his medical leave certificate.

○ Alternate Flow: If the admin finds that any of the provided

documents by the student have faults then his request is canceled and
he again needs to apply for it again with correct documents.

29
NIT Calicut, MCA 2019

Test Case:

6.1.6 Test Case #6 (Appointments canceled by doctor )

Flow of Events:

○ Basic flow:
■ The doctor logged in to the application and moved to the "List
Appointment" page.
■ They need to give a date to check the list of appointments on
that particular date.
■ After that it will select the slot which he wants to cancel and
click on the “Cancel Appointment” button to cancel the
appointment.

○ Alternate Flow : To remove previous data, doctor can click on

“Reset” button to refresh the page

30
NIT Calicut, MCA 2019

Test Case :

6.1.7 Test Case #7 ( Accept Medical Leave Request )

Flow of Events:

○ Basic flow: The doctor fills user details and writes his medical
condition in the application and then clicks on submit to accept his
leave request.

○ Alternate Flow : None

31
NIT Calicut, MCA 2019

Test Case:

6.1.8 Test Case #8 ( Appointment History)

Flow of Events:

○ Basic flow: The doctor will login to the application and then move to
the List appointment page to check all the details of his appointments.
They can give the date to check the list of all appointments on that
date.

○ Alternate Flow : If no appointments are there, the page will be blank

for that person,

32
NIT Calicut, MCA 2019

Test Case:

6.1.9 Test Case #9 ( Book Appointment )

Flow of Events:

○ Basic flow:
■ The user first login to the application and then move to the book
appointment page.
■ From the given options, according to their issue, they will
select the option.
■ Then the user will give the date and time of day of his choice
for appointment.
■ From the list of slots it will select one and click on “Register”
button to book an appointment.

○ Alternate Flow : If the selected slot is already booked then an error

message will be shown "Already booked".

33
NIT Calicut, MCA 2019

Test Case:

34
NIT Calicut, MCA 2019

6.1.10 Test Case #10 ( Cancel Appointment by user)

Flow of Events:

○ Basic flow: The user first logs in to the application then moves to the
cancel appointments page. There, he will see his appointments. User
will select the appointment and click on cancel appointment to
confirm his cancellation.

○ Alternate Flow : None.

Test Case:

35
NIT Calicut, MCA 2019

6.1.11 Test Case #11 ( Forgot Password)

Flow of Events:

○ Basic flow: The user will directly move to Forgot password page and
give his registered mail in it then click on submit button. If he is
registered then he will get a successful message.

○ Alternate Flow : Error generated.

Test Case:

36
NIT Calicut, MCA 2019

Chapter 7

CONCLUSION

The proposed mobile app “Nitc Telehealth Application” is completed with frontend
in flutter and backend api written in Node.js deployed in Heroku platform and
mongodb is used for database storage. The proposed app is efficient and has a
friendly user interface.

Key features of the application are as follows:

Admin:
● Create schedule for doctors
● Register new users to the application
● Remove users from application
● Print medical certificate

Doctor:
● Cancel an appointment
● Check list of all appointments

User:
● Book an appointment
● Cancel an appointment
● Request for medical leave

37
NIT Calicut, MCA 2019

References

1. https://www.researchgate.net/publication/275097517_DOCUMENTATION_
OF_ONLINE_BOOKING_SYSTEM, last accessed on 15/04/2022

2. https://medium.com/@alenatsytovich/booking-an-appointment-6714c40954
0, last accessed on 19/04/2022

3. https://opus.govst.edu/cgi/viewcontent.cgi?article=1158&context=capstones,
last accessed on 22/04/2022

4. https://m.docsapp.in/?gclid=CjwKCAiAsNKQBhAPEiwAB-I5zaTENqZMF
CvTmnonvQnFjmDCfUW-lzOdrprd9JY1QtGFGpV7RABWVhoCvXEQAv
D_BwE, last accessed on 24/04/2022, last accessed on 28/05/2022

5. https://www.researchgate.net/publication/312946008_Mr_Doc_A_Doctor_A
ppointment_Application_System, last accessed on 05/05/2022

6. https://ieeexplore.ieee.org/abstract/document/8899460, last accessed on

11/05/2022

7. Draw.io- Used for designing and creating diagram, https://www.draw.io/, last

accessed on 15/05/2022

38