Post Covid-19 Website

Final Year Project

Supervisor: < MR. FAISAL SHEHZAD>

Presented by:
F21BINFT1M04104 SIDRA SADOOR
F21BINFT1M05007 HAMZA KHALID

Department of Information Technology (DIT)

The Islamia University Of Bahawalpur

 Post Covid-19 Website

By

SIDRA SADOOR
HAMZA KHALID

Project submitted to Department

of Information Technology, The Islamia

University of Bahawalpur.

in partial fulfillment of the requirements for the degree of

BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOY (BSIT)

Supervisor Signature In- Charge Examination Signature

Chairman, Department of Information

Technology
Abstract

In recent years, the epidemic of COVID-19 virus has become more and more serious,
resulting in more and more people infected by the virus. In view of the transmission and
infection characteristics of novel coronavirus and the potential risks of urban epidemic
prevention and control, the COVID-19 epidemic prevention and control management
system is designed and implemented based on the spring cloud microservice architecture
to implement standardized and intelligent management of urban epidemic prevention
and control. The mobile terminal is used to collect the nucleic acid detection information,
vaccination information and key personnel information of urban residents according to
the region, and conduct statistical analysis on all kinds of information to form intelligent
visual data for dynamic display, so as to improve the level of epidemic prevention and
control management.

i
 TABLE OF CONTENTS
ABSTRACT....................................................................................................................................................................I
ACKNOWLEDGEMENT............................................................................................................................................II
LIST OF FIGURES.....................................................................................................................................................III
LIST OF TABLES.......................................................................................................................................................IV
CHAPTER 1. INTRODUCTION............................................................................................................................ 1
1.1 INTRODUCTION...........................................................................................................................................................................................1
1.2 Purpose of this Document.......................................................................................................................................................................1
1.3 Definitions, abbreviations and acronyms..............................................................................................................................................1
1.4 References...........................................................................................................................................................................................1
1.5 Overview....................................................................................................................................................................................................1

CHAPTER 2. Overall Description................................................................................................................... 2

2.1 Product Perspective.................................................................................................................................................................................2
2.2 Product functions......................................................................................................................................................................................2
2.3 User Characteristics.................................................................................................................................................................................2
2.4 General Constraints, Assumptions and Dependencies......................................................................................................................2
2.5 Apportioning of the requirements...........................................................................................................................................................2

CHAPTER 3. Specific Requirements............................................................................................................. 5

3.1 External Interface Requirements...........................................................................................................................................................5
3.2 Detailed Description of Functional Requirements...............................................................................................................................5
3.3 Performance requirements.....................................................................................................................................................................5
3.4 Logical database requirements..............................................................................................................................................................5
3.5 References................................................................................................................................................................................................5

CHAPTER 4. TEST SPECIFICATION AND RESULTS................................................................................................ 7

4.1 TEST CASE SPECIFICATION.........................................................................................................................................................................7
4.2 SUMMARY OF TEST RESULTS.....................................................................................................................................................................7
CHAPTER 5. CONCLUSION AND FUTURE WORK................................................................................................ 8
5.1 PROJECT SUMMARY....................................................................................................................................................................................8
5.2 PROBLEMS FACED AND LESSONS LEARNED...............................................................................................................................................8
5.3 FUTURE WORK............................................................................................................................................................................................8
REFERENCES........................................................................................................................................................ 9
APPENDIX A GLOSSARY.............................................................................................................................. 10
APPENDIX B DEPLOYMENT/INSTALLATION GUIDE......................................................................................10

ii
Revision History
Name Date Reason For Changes Version

iii
Chapter 1. Introduction
1.1 Introduction
In the first quarter of 2020, the world was faced with COVID-19 pandemic which was
truly a ‘black swan’ event – an event whose probabilistic occurrence is rare, but should
it occur, the event can have devastating consequences. Globally, stock markets
nosedived, factories were shut down, global trade and supply chains were severely
disrupted, airports were deserted, offices had stopped their operations and shops
remained closed to contain the pandemic outbreak.
On the December 31, 2019, first official case was reported in Wuhan China. Initially it
was confined to China until first official case was recorded in Thailand on January 13,
2021. The first case of COVID-19 in Pakistan was reported on 26th February 2020. By 1st
June 2020, 76,398 cases were reported with 1,621 deaths, i.e., CFR1 2.12%.
Daily maximum cases in Pakistan were reported on June 14, 2020, i.e., 6,825 cases. 213
cases were the lowest official number that were reported on August 30, 2020. Second
wave was started in the second week of October, reached 3,795 official case on
December 6; maximum in the second wave. Although the cases started increasing the
maximum number remained close to 1,000 cases till February 2021.
The ongoing third wave in Pakistan was officially recognized to have started in the
second week of March 2021. The number of cases (on March 18, 2021) are increasing at
8 percent infection rate and CFR is 1.2 percent. Total cases are more than 600 thousand
and are expected to increase due to increase in infection rate as well as outbreak of new
variant of virus.

1.2 Purpose of this Document

The purpose of this SRS document is to provide a detailed overview of our Post Covid website,
its parameters and goals. This document describes the project's target audience and its user
interface, hardware and software requirements. It defines how our client, team and audience see
the product and its functionality.

1.3 Scope of the Development Project

The goal is to design website for a Post Covid Tracking System. In emergency situations such as corona virus
pandemic, communication plays a significant role. For instance, people may need to communicate with others
to appeal for help. Or they may want to be informed about the situation. However, in such situations it is very
likely to spread fake news and provide fake information. This application will deal with this problem and it
will allow users to get the latest and correct information. As a result of this, people become more aware and
also can help others in this situation. The application will be able to set a GPS connection using the internet. A
similar kind of mobile tracing application has been developed in India, namely, Aarogya Setu. The App is
designed in such a way that it informs the user whenever they come in contact with an infected person through
Bluetooth and GPS location services. The data acquired from the application is not disclosed publicly and is
only used by the government for tracing, tracking, and management of Post COVID-19[1]. The global impact
of Post COVID-19 pandemic has led to a rapid development and utilization of mobile health applications.

1
 These are addressing the unmet needs of healthcare and public health system including contact
tracing, health information dissemination, symptom checking and providing tools for training
healthcare providers [3].

The website must be able to perform the following operations:

1. Consult Doctor: It must be able to provide online consultations with the
concerned doctors.
2. Ambulance Facility: It must be able to provide an online ambulance facility to
the needy user/patient in an emergency situation by using GPS location.
3. Hospital Facility: The software must be able to provide the information about
nearby hospitals by using the user's GPS location.
4. E-Prescription: The software must be able to provide an e-prescription facility
so that if a patient has mild symptoms, he/she can get online prescriptions from
doctor through the application and need not to rush to the hospital.
5. Call Helpline: Users can call helpline number to inform about themselves or
other persons to the government or to get information regarding any doubt
related to the disease.
6. Assessment Information: User can get his/her self-assessment information
online in case the user has disease or not.
7. Cases Information: User can get information about the number of cases in
his/her area by using GPS location.

Containment is a primary road-map to quickly halt an outbreak, which may become an epidemic and
then in the worst case, turn into a pandemic, which is exactly what happened in case of POST
COVID-19[4]. Initially we plan to implement these functionalities in the contaminated zone of
selected cities where there is a major risk of POST COVID 19. In future we plan to implement it in
all the cities across the country so that everyone will feel safe in this pandemic situation.

The scope of the system is not just limited to the users belonging to the risky zone of POST
COVID 19 but also for the users who are not in the risky zone as well, so that they can get regular
checkup and updates.

1.4 Definitions, abbreviations and acronyms

Definitions
Table 1 gives explanation of the most commonly used terms in this SRS
document.

Table 1: Definitions for most commonly used terms

S.No. Term Definition

1 POST COVID- POST COVID-19 is the infectious disease caused by the most
19 recently discovered corona virus. This new virus and disease
2

2 Pandemic
3 Contact Tracing
4 Containment
were unknown before the outbreak began in Wuhan, China, in
December 2019. The most common symptoms of POST
COVID-19 are fever, tiredness, and dry cough.
A pandemic is defined as “an epidemic occurring worldwide,
or over a very wide area, crossing international boundaries and
usually affecting a large number of people”.
Contact tracing is key to slowing the spread of POST COVID-
19 and
helps protect you, your family, and your community.
The action of keeping something harmful under control or
within limits.

Abbreviations
Table 2 gives the full form of most commonly used mnemonics in this SRS document.
Table 2: Full form for most commonly used mnemonics

Sr No. Mnemonic Full Form

1 COVID Corona Virus Disease

2 GPS Global Positioning System

1.5 Overview
The remaining sections of this document provide a general description, including
characteristics of the users of this project, the product's hardware, and the functional and data
requirements of the product. General description of the project is discussed in section 2 of this
document. Section 2 gives the functional requirements, data requirements and constraints and
assumptions made while designing the multi-utility system. It also gives the user viewpoint of
product use. Section 3 gives the specific requirements of the product. Section 3.0 also discusses
the external interface requirements and gives detailed description of functional requirements.

Pandemic Experience Informs Post-Pandemic Strategy

At Sharp Rees-Stealy (SRS), a 580-physician multispecialty medical group in San Diego affiliated

with Sharp HealthCare, the initial adjustments to the pandemic were especially challenging. SRS

outpatient facilities discontinued all non-essential in-person visits, yet still had to manage the

primary care and specialty needs of thousands of patients. This prompted the scaling up of

telehealth encounters from a few dozen in February 2020 to more than 2,000 a day in March 2020.

3
For patients seen in clinic for essential visits, screening processes were quickly developed at point

of entry to ensure patients and staff within the buildings remained safe. Any symptomatic patients

were seen by their treating physician in outdoor respiratory clinics or an isolated area with

appropriately protected staff. All patients are screened, provided a mask if they don’t have an

appropriate face covering, and are required to use hand sanitizer before entering the clinic.

SRS staff had to overcome enormous logistical challenges in order to achieve this transition

efficiently. Initial on-hold wait times for patients who phoned in for information and services in the

early days of the pandemic and related shutdowns was 27 minutes. That metric was slashed to

around 10 seconds within a matter of days. That feat was accomplished, in part, by moving the

members of the medical staff most personally vulnerable to Covid-19 infection away from actual

patient encounters into roles providing telemedicine visits, which expanded the capacity to provide

care on patient phone calls. We also set up a secure messaging system platform so patients could

quickly communicate with staff and receive a rapid response regarding appointment availability

and other information.

The transformation was further bolstered by SRS’s purchase of equipment to enable physicians to

perform telemedicine encounters at home, training those physicians remotely, and expanding from

one to three telemedicine platforms in order to offer every doctor the options that would maximize

their comfort working virtually. In terms of hardware, high-resolution web cameras, averaging

from $70 to $100 each, were the main requirements for home setup. In some cases, USB or

Bluetooth headsets were purchased to provide better audio quality during telemedicine visits. To

ensure the virtual encounters provided the same experience as an in-person visit, physicians were

encouraged to attend webside manner training sessions to teach best practices for video. A stipend

of $140 was provided for additional hardware purchases to anyone who attended these training

sessions. Software licenses for use of the telehealth platform had to be purchased for all the

physicians. Depending on the platform chosen, license cost can range from free (with limited

4
features) to approximately $50 per provider per month.

70% of its patients are treated on a capitated basis (which includes both Medicare and commercial

payers). These arrangements provided steady enough cash flow to make dramatic changes to how

patient encounters are modeled, without the pressure to rapidly recoup enormous amounts of lost

revenue.

Although SRS did take an initial financial hit from these expenditures and the drop in non-essential

procedures, it had the flexibility to make these broad changes due to its payer mix: 70% of its

patients are treated on a capitated basis (which includes both Medicare and commercial payers).

These arrangements provided steady enough cash flow to make dramatic changes to how patient

encounters are modeled, without the pressure to rapidly recoup enormous amounts of lost revenue.

Some procedural specialists did experience reduced workload due to the postponement of non-

essential care, but that rose again once services were resumed in June.

The adjustment to the demands of the pandemic has also prompted clinic leadership to think

carefully about how SRS will be operating in the months and years to come. The conclusion is that

the organization will treat patients in a radically different manner, with Covid-19 accelerating a

move toward virtual care that was previously expected to take a decade.

Impact on Remote Patient Encounters

In 2019, SRS set modest goals of having 3% of patient encounters conducted via a telemedicine

platform by 2021. That would rise to 10% by 2023. These estimates have been thrown out the

window due to the pandemic. At the worst of the Covid-19 crisis in late spring, 70% of SRS patient

visits were virtual (Figure 1).

Figure 1 .Even when Covid-19 vanishes from the landscape, we are now planning that between

15% to 30% of all patient encounters will be remote — triple the pre-Covid goal that had been set

5
for 2023. But it is possible that percentage will be lower (Table 1).

Table 1.

Scroll table to see more

Medical Care Category Week of 8-7-2020 Target for 2021

Family Medicine 59.5% 27.0%

Pediatric Internal Medicine 28.1% 27.0%

Internal Medicine 60.5% 30.0%

Pediatric Primary Care 15.9% 24.9%

Specialty Care 36.3% 36.4%

Surgical Specialties 10.2% 8.5%

Primary Care 52.2% 30.2%

All Patient Encounters 37.5% 26.3%

To determine 2021 virtual care targets, we carefully tracked the amount and percent of
in-person and virtual visits each week and compared that to our staffing levels, taking into
account backlogs for in-person visits. Initially, we’d hoped to set 2021 telemedicine visits
at about 30% of the overall total, but as physicians returned to the office and patients
became more comfortable with in-office care, that demand is increasing; so, despite
efforts to maximize the use of telemedicine, the 2021 average may be closer to 15%
telemedicine.
Source: The authors

In some departments, such as internal and family medicine, the virtual encounter rate approaches

60%, while specialty care is lower. Currently, about one-third of encounters involving medical

specialists are now virtual. However, telemedicine has been less widely embraced when it involves

more complicated procedures or pediatric patients. Only about 10% of surgical specialty encounters

are virtual, as are about 16% of pediatric visits.

6
Taking this case mix data into account, SRS is aiming for 50% to 60% of all primary care visits to be

virtual by 2021. We also plan for virtual visits at 30% of all specialty encounters except for surgical

consultations, for which we will aim for 10% to 20% of visits to be virtual. These targets are

supported by current encounter data.

7
8
 2. Chapter 2. Overall Description
2.1 Product Perspective

The product will run as a Web application. It requires internet connection and GPS
connection. It can run on all platforms such as Mac and Windows etc.
1. It must be able to check the user’s location correctly to provide accurate
data. Contact tracing is an essential tool for public health officials and local
communities to fight the spread of novel diseases, such as for the COVID-19
pandemic [2].
2. It must be able to provide quick information about ambulance, doctor and
nearby hospital facility.
The Web application must be able to provide user friendly GUI so that the user cannot face any issues while using the
web application.

9
 2.2 Product Function
The product should be able to perform the following functions:

 Cases
User can check number of active cases, recovered cases and deceased cases according to
Users can use this feature by providing the symptoms of the disease and can get help
regarding any problem.

his/her state or country.

 Call Helpline
Users can call helpline number to inform about themselves or other persons to the
government or to get information regarding any doubt related to the disease.

 Self-Assessment
Users can use this feature by providing the symptoms of the disease and can get help
regarding any problem.

 Locate Hospital
Users can get the location of nearby hospitals using GPS connectivity. Additionally, you can
also find nearby laboratories and pharmacies to seek help in the case of emergency.

 Consult Doctor
User can consult doctors online to get prescriptions from them based on their
symptoms.There will be doctors available 24/7 with whom users can discuss their problem.

 Ambulance Facility
This feature is essential for emergency issues arising in untimely situations. One- click
ambulance call can be of great help here. This feature let you request the emergency help
for yourself, friends or family. This feature notifies the trusted contacts and the hospital
along with the precise location.

2.3 User Characteristics

The goal is to design web apllication for a Post Covid Tracking System
Our goal is to develop website that should be easy to use for all types of users. Thus, while
designing the website one can assume that each user type has the following characteristics:
There are two types of users that interact with the system: users of the web application, and
administrators. Each of these two types of users has different use of the system so each of them
has their own requirements. The web application users can only use the application. This means
that the user has to be able to search for hospitals, choose a hospital from that search and then
navigate to it. In order for the users to get a relevant search result there are multiple criteria the
10
 users can specify and all results matches all of those. The administrators also interact with the
web portal. They are managing the overall system so there is no incorrect information within it.
The administrator can manage the information for each user.

2.4 General Constraints, Assumptions and Dependencies

The following list presents the constraints, assumptions, dependencies or guidelines that are imposed
upon implementation of the Post Covid Tracking System

 The product must have a user-friendly interface.

 A general knowledge of basic computer skills is required to use the website.

2.5 Apportioning of Requirements

The Covid Tracking System is to be implemented in the following phases:

i. Initial Phase: Here the Covid tracking system initially implemented on a

set of 1000 users. We will check the feasibility of the application and then
implement it on a larger scale.
ii. Wide user deployment: Following the successful completion of the
initial phase, we plan to deploy the same across the. In this phase the
application will be available for all the users and also with some security
features.
iii. Extension of Covid tracking system to other applications: In the future
we can have many more features in the application according to the
requirements of users and their feedbacks.

Here the same functionalities will be implemented in each phase; the only difference will be the
number of transactions being carried out and the scale of implementation.

11
 Chapter 3. Specific Requirements
3.1 External Interface Requirements

The following list presents the external interface requirements:

 The product requires very limited graphics usage. It will use graphics only to
display graphs.
 The product requires usage of animation. The hardware and operating system
require an android or IOS platform with internet connectivity.
 Sound is not an essential feature but it can be considered for future variants of the
system wherein the user can give voice commands.

3.2 Detailed Description of Functional Requirements

Table 3 shows a template that we’ll be using to describe functional requirements for
users.
Table 3: Functional Requirements for Login
This screen thus provides information specific to each user upon
Purpose the successful identification of the ID no. and the password with the
values stored in the central database server.

Input A user can enter his/her User ID and password.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can get many options such as
Output
consult doctor, helpline number, etc.

Table 4: Functional Requirements for Helpline

This screen thus provides information specific to each user about the
Purpose
helpline number to get any help or information regarding the disease.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

12
 Output consists of a screen where user can get different helpline numbers
Output
according to his/her state.

Table 5: Functional Requirements for Self Assessment

This screen thus provides information specific to each user for his/her self-
Purpose assessment if he/she has any symptom related to the disease.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can get a questionnaire of different

Output
symptoms and click on of the options and can check his/her health status.

Table 6: Functional Requirements for Cases

This screen thus provides information specific to each user regarding the
Purpose number of cases in the state and total case across the country.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

13
 Output consists of a screen where user can check the number of active
Output cases, deceased cases, recovered cases across the country or a particular
state and also can visualize the graphs according to the data.

Table 7: Functional Requirements for E-Prescription

This screen thus provides information specific to each user if he/she wants to
Purpose
get online prescription in case of mild symptoms.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can register himself for prescription
Output
from the doctor and he can see the doctors name and his specialization.
Table 8: Functional Requirements for Locate Hospital

This screen thus provides information specific to each user regarding nearby
Purpose
hospitals in case the condition gets serious.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can see a list of hospitals nearest to
Output
his/her place so they can rush to the hospital in very less time.

Table 9: Functional Requirements for Consult Doctor

This screen thus provides information specific to each user regarding

Purpose
different doctors who will be available for online prescription.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

14
 The menu responds to selections by displaying a page containing the
Processing
pre-defined text requested information.

Output consists of a screen where user can get a list of doctors and their
Output specialization so that user can easily choose which doctor he/she has to
consult.

Table 10: Functional Requirements for Ambulance Facility

This screen thus provides information specific to each user if he/she needs
Purpose ambulance facility to reach nearby hospital.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can get the information of the
Output
available ambulance at that particular time and can ask the service.

15
 Table 11: Functional Requirements for Transaction Facility

This screen thus provides information specific to each user if he/she needs to
Purpose
perform a transaction to pay fees for online prescription.

Input The user must enter his/her User ID and password and after that he/she can
access this feature.

The menu responds to selections by displaying a page containing the

Processing
pre-defined text requested information.

Output consists of a screen where user can get different modes of

Output transaction such as UPI, credit/debit card etc. along with the doctor
name and his ID.

Performance Requirements
 System
The application will run on all Android devices and IOS. It will be around 1GB in size. The
application will respond to the size of the screen and/or window the application is running in.

 Response Time
The application should take less than 4 seconds when running on an Android phone and
less than 8 second when on an emulator or tablet. The application will run fine until the
user begins to multi-task between 3 or more processes.

 Workload
The application must support approximately 10,000 users at the time of launch.

 Scalability
The application will be able to scale globally.

16
 3.3 Logical Database Requirements

Figure 2 shows the E-R diagram for the entire

Figure 2: E-R Diagram for the Covid Tracking System

Quality Attributes
 Security
Users can authenticate by logging in using their user id and password.

 Reliability
Most functionality will require network connectivity. System components that require
authentication and network connectivity will function as long as the systems are available.

 Maintainability
The development team will follow best practices for clean code and software modularity
in order to make the application as maintainable as possible.

 Portability
Users will be able to access this application anytime on their mobile device even with low
internet connection.

 Extensibility
The application will be highly extensible in terms of adding course and calendar details or
views. However, the application in general has low extensibility.
17
  Reusability
An application instance shall be able to be reusable.

 Application Affinity/Compatibility
The application shall be compatible with Android and IOS.

3.4 Other Requirements

There are no other requirements.
3.5 References

3.5.1.1.1 The 2019-nCoV Outbreak Joint Field Epidemiology Investigation Team and Li, Q. (2020)
An Outbreak of NCIP (2019-nCoV) Infection in China-Wuhan, Hubei Province, 2019-
2020. China CDC Weekly, 2, 79-80.
3.5.1.1.2 Tang, B., Bragazzi, N.L., Li, Q., Tang, S., Xiao, Y. and Wu, J. (2020) An Updated Estimation
of the Risk of Transmission of the Novel Coronavirus (2019-nCov). Infectious Disease
Modelling, 5, 248-255
3.5.1.1.3 Wu, Z. and McGoogan, J.M. (2020) Characteristics of and Important Lessons From the
Coronavirus Disease 2019 (COVID-19) Outbreak in China: Summary of a Report of
72 314 Cases From the Chinese Center for Disease Control and Prevention. The Journal
of the American Medical Association.
3.5.1.1.4 Ding, R., Long, J., Yuan, M., Y Jin, & Duan, G. (2021).CRISPR / CAS system: potential
technologies for the prevention and control of covid-19 and emerging infectious
diseases. Frontier of cell and infection Microbiology, 11, 639108.
3.5.1.1.5 Rainisch, G, Undurraga, E. A., & Chowell, G. (2020). A dynamic modeling tool for
estimating healthcare demand from the covid19 epidemic and evaluating population-
wide interventions. International Journal of Infectious Diseases, 96.

18