This is Telemedicine SRS.

2. Software Requirement
Specification on
Telemedicine App
Jubair Ahmed Junjun
B.Sc in Computer Science& Engineering(CSE)

3. Index
◦ 1. Introduction
◦ 1.1 Purpose
◦ 1.2 Scope
◦ 1.3 Definition, acronyms, abbreviations
◦ 1.4 References
◦ 1.5 Overview
◦ 2. Overall Description
◦ 2.1 Product Perspective
◦ 2.1.1 User interface (UI)
◦ 2.1.2 Software requirement
◦ 2.2 Product Function
◦ 2.3 User Characteristics
◦ 2.4 Constrains
◦ 2.5 Assumptions and dependencies
◦ 2.6 Apportioning of Requirements
◦ 3. Functional requirements
◦ 4. Non-Functional
◦ 5.Conculation

4. 1. Introduction: Access, equity, quality, and cost-effectivenessare key issues facing health care
in both developed and less economically developed countries. Modern information and communication
technologies (ICTs), such as computers, the Internet, and cell phones, are revolutionizing how
individuals communicatewith each other, seek and exchange information, and enrichingtheir lives.
These technologies have great potential to help address contemporaryglobal health problems.
1.1 Purpose: The purpose of this report, Telemedicine App is synonymous and used
interchangeably.Four elements are germane to telemedicine:
1. Its purpose is to provide clinical support.
2. It is intended to overcomegeographical barriers, connectingusers who are not in the same physical
location.
3. It involves the use of various types of ICT.
4. Its goal is to improve health outcomes.
1.2 Scope: The introduction and popularization of the Internet has further accelerated the pace of
ICT advancements,therebyexpanding the scope of telemedicineto encompass Web-based applications
(e.g. e-mail, teleconsultations and conferences via the Internet) and multimedia approaches (e.g. digital
imagery and video). These advancements have led to the creation of a rich tapestry of telemedicine
applications that the world is coming to use.

5. •1.3 Definition, acronyms, abbreviations:
•1. Physician Licensing
•In theory, telemedicine would allow cross-state consultations that would allow specialists to help more patients.
However, physicians face several telemedicine and telehealth challenges if they wish to practice in another state, including
regulations that vary state-by-state. In some cases, practitioners may need a full medical license in both the state they live
in and the state where the patient resides. In other situations, physicians may have to pay an exorbitant fee to practice
across state lines. Additionally, even after obtaining the necessary clearances to practice medicine across state lines,
physicians may be asked to adhere to state medical practice rules that are diverse and even sometimes conflicting. The
arduous nature of these laws defeats the quick convenience of telemedicine.
•Potential Solution:
•One reasonable move that could help solve the problem would be to create a national telemedicine license. However,
with differing opinions between states’ lawmakers, universal medical licensure is still a distant fantasy. Currently, there are
telemedicine-specific licenses available
in Tennessee, Texas, Oregon, Oklahoma, Ohio, New Mexico, Minnesota, Montana and Alabama, and Nevada offers a
special purpose telemedicine license. The American Telemedicine Association has a petition out for removing barriers
to medical licensure. And in good news, many states have adopted language consistent with the Interstate Medical
Licensure Compact, which seeks to reduce the obstacles of cross-state telemedicine adoption.

6. •2. Credentialing
•The telemedicinecredentialing process can get very complicated. For example, in hospitals that work from a
hub and spoke model, physician specialists at every hospital in the system must have telemedicine credentials at
all the other hospitals. Not only is the volume of paperwork needed for credentialing time-consuming,
but the administrative processing costs are through the roof. The time and money invested in approving
physician credentials for telemedicine could be used to train hospital staff and onboard patients instead.
•Potential Solution:
•Streamlining the credentialing process with a common set of requirements would allow physicians to apply
for credentials at many hospitals in one fell swoop, in the same vein as the college Common Application that is
used at U.S. universities. One initiative by the CMS and Joint Commissions supports credentialing by proxy. This
allows for a network or system’s hub hospital to apply for credentialing, by proxy, to the
spoke hospitals. This process would eliminatethe overwhelming numbers of applications, and allow physicians to
begin practicing more quickly. Although the long primary verification process is not addressed by credentialing by
proxy, it definitely is a step in the right direction.

7. a. SRS : Software RequirementSpecification [2]
b. Web application: An application which runs in a global server and accessible by everyone allowed to access.
c. API: Application programming interface.
d. Laravel: Backend PHP language framework developed.
e. Database: Where all data will be stored.
f. JS: JavaScript language.
g. Visual Studio: To develop the project, this is an IDE.
h. SQL Server Management: This is for doing database design and operation.
1.4 References:
1. https://www.quora.com/What-are-the-advantages-and-disadvantages-of-hospital-management-software
2. https://www.docsity.com/en/software-requirements-specification-for-hospital-information-management-
system/874363/
3. https://laravel.com/
4. https://www.myhospitalwebsite.com/en/Features/MedicalFeatures
5.https://www.designingbuildings.co.uk/wiki/How_to_Develop_the_Most_Constrained_Hospital_Sites_to_Reduce_
Waiting_Times_and_Improve_Patient_Care
6. https://www.quora.com/What-are-the-functional-requirements-for-hospital-management-system
7. https://www.webopedia.com/TERM/W/website-optimization.html

8. • 1.5 Overview:
• User Roles :-Hereyou can find user customization that provides certain privileges and grant access to
the system features and functionality. There are three user levels within the telemedicineapplication
platform: Patient, Doctor, and Admin. Let’s take a look below:
• Patientsare users with basic permissions who can request online consultation with a doctor.
• Doctors are users who can view patient’s profiles - medical records, lab results, view and schedule
appointments, etc.
• Admin has the highest administrative responsibilities and security level.
The rest of the SRS documents contains overall descriptions of the project, identifying the functional
and non-functionalrequirements. The SRS is organized in various steps.
Step 1: Purpose, Scope, Some Definition of specific words,references.
Step 2: Product perspective, Functions, User characteristics, Constraints, Assumptions
and dependences, Apportioning of requirements.
Step 3: Functional requirements of the system.
Step 4: Non-functional requirements of the system.

9. 2. Overall Description:
Here we will be discussing about the interaction of system with all other facts and environments.Product
perspective, user functionality, constrains, assumption and some other requirements will bediscused.
2.1 ProductPerspective: This “Telemedicine App” is a web based application intended to serve patients. It is a
hospital based website by which a patient can take pre serial of a doctor, upload test results, can talk by video
conferencing, takeprescriptions online and so on. Along with those, it also digitalize the regular hospital manual
processes.
2.1.1 User interface (UI): A nice looking user friendly design will be provided for ease of access to all therequired
functionality. DifferentUI will be there for different target user. It will help them to comfortably use the system.
2.1.2 Software requirement:
For developer:
. TextEditor( Main framework Laravel, front end HTML, CSS, Bootstrap,
JavaScript,React)
-SQL Server Managementfor MySQL
-Google Chrome / Mozilla Firefox to RUN the project
For user:
-nternet Browser (To access the website)
- Official Host / Server
2.2 ProductFunction: The targeted user of this website are given some main features to fulfill their purposes.

10. Telemedicine App Features for Patients
➢ Registration
➢ Profile management
➢ Search & filters
➢ Video conferencing
➢ Text chat
➢ Calendar
➢ Payment details
Telemedicine App Features for Physicians
➢ Physician profile
➢ Calendar management
➢ Viewing EHRs
➢ Communication
•Register: All user should register to login to this site. Doctors registration will be verified by
Administrator.
•Login: After registration user should login to use the site.

11. 2.3 User Characteristics: The system considers three types of users in it. It must be technical guy to handle the
website. He / She supposed to handle logins for other users.
Doctor must have some common user ability of web as well as patient. As patient supposed to use this
site, they also have some basic idea of using internet to navigate through a website.
2.4 Constrains:
An active internet connection is required to use the website. Without internet the website can be
availablethrough local server but will not be available for patients. Also computer, mobile and an email
id is must to login to this site.
2.5 Assumptions and dependencies:
The website is dependent on active internetconnection. If internet is off some very important feature willbe
hampered. Maintenance of this site is done by admin . Any fault done by handlingdatabase by the admin can be
catastrophic. This is assumed that all the expected user have mobile orcomputer with internetconnection. Also
email id is very import for login as it is used for notificationsystem.
2.6 Apportioning of Requirements: We were planning some extra feature like e-doctor which will servepatients via
online doctor

12. 3. Functional requirements :
Patient: The main section of our project is patient section. Here we will discuss about patients
actions in the web application.
Registration: Patientmust register first to login and have other option. One must provide
below information on registration.
➢ Name
➢ Login Password
➢ Personal phone number
➢ Emergency phone number
➢ Blood group (optional)
➢ Address (optional)
➢ Valid email id
Login: Patientcan login with email id/phone number and password given when
registered. After login user will have other options.
Profile Management : patient have to set his profile .
Search &filters :It will help patients find the right doctors.
Take appointment: After login patient can take appointment of doctor depend on
availability. Patient will get an email notification before a day of appointment.

13. Video conference & text-bot :Then patient can connect with doctor via video call or text-
bot.
Take next visit date and time: Doctor will give next appointment date and time if
necessary. An email notification will be send before one day of that day.
Doctor: Doctor interacts with patient directly via video call or textbot.
Other actions of doctor given below:
Registration: Doctor will be registered by A login email id,
password will be given to doctor for login.
Login for doctor: With provided credentials doctor will login to his dashboard. He can see number
of patients who has an appointment that day and their information.
show in website.
Blood bank: Blood group and availability will be shown here.

14. 4. Non-Functional requirements:
➢ No restriction to registered users
➢ Encrypted patient data storage
➢ Secure website with https
➢ Secure mail server
➢ Firewall security for database
➢ Scalability
➢ SMS notification can be added
➢ Data storage can be increases
➢ Available for any devicewith internet access
➢ Optimization
➢ Less timefor loading
➢ Fast and accurate mail service
➢ SEO facts
➢ User Friendly UI
➢ Responsive user interface
➢ Nice looking design
➢ Valid contact information
➢ Regular maintenance and update

15. 5.Conculation
Telemedicineapp development is definitely not an easy project as it sounds, but the returns can be
rewarding. The market trends show that the need for telemedicine apps is huge in the global market.