E-Healthcare Faculty- MD MASUM

BILLAH

Management System External- RAIHAN

UDDIN AHMED

Submitted By
Name ID
Islam, Rashedul 18-36155-1
Ayshi, Aishwarya debnath 18-36042-1
Sohan, MD. Tanzil Alam 18-36915-1
Rahat, Abdul Jabbar 17-34515-2
Abstract

Telemedicine and online have become pivotal parts of the healthcare

industry. Having access to medical advice, information, appointments
and emergency services at a moment reach has helped improve the
healthcare experience though software services and technology.
However, due to the lack of a mature market, coupled with
fragmentation of services, the current state of the Medicare application
and service market remains quite underdeveloped. In an attempt to
implement a unified approach to Medicare services and create a service
that is adaptable to the Bangladeshi market, our project proposes a
unified Medicare application.
The project proposes a unified application with blood bank,
appointments and emergency services integration available through the
web to users with user-friendly interface and widely available. The aim
of the project is to create a SaaS based application that addresses these
issues within the Bangladeshi market while making the lives of patients
better.
What is E-healthcare Management
System?
E Healthcare Management System is a web based application that allows
people to access medical services online from anywhere. Network
technology and communications are now prominent developments in
information technology and have a large impact on health care. It has
mainly administration, doctor, patient and medical service provider
modules. Patients can easily consult a doctor at home through chat and
they can book an ambulance and they will get the benefit of the blood
bank. It is a complete solution for people who need emergency
treatment.
Objective of this project

This solution is created to meet the different types of problem faced by

the mass people when they are unable to visit the doctor or hospital.
There are so many cases where the patients are in such a place that he
is unable to consult with a doctor. Sometimes the patients died only for
not attended to a doctor at proper time. This application will be a cure
for such type of difficulties. Whenever a person is unable to visit the
doctor/hospital due to pandemic, illness, shortness of time, vehicle
inaccessibleness or in need of ambulance, blood donor, he would have
the solution of his sufferings through this technology. Here’s to meet the
variations, every kind of specialists will be available.
Patients can select his specialist as his wish, can talk with him virtually,
who must not be a robot doctor. If anyone stuck in a recess that he can’t
have access any vehicle, he can get an ambulance just by a click. If
anyone need to emergency blood, he can also able to have the blood
without any hassles as this application also have the “Blood Bank”
features. In a word this application is a complete solution for today ‘s
virtual health services.
Requirement Elicitation
Four Basic Users

 Admin
 Doctor
 Patient
 Medical Service Provider
ADMIN

 Can add/delete/update
 Verifying doctor's registration
 Can search for specific memebers
 Have full access to the system
Doctor

 Have to register
 Can view/update/delete their information
 Can email prescription to Patient
 Can see patients Information
Patient

 Can book session with doctors

 Receiving prescription through email
 Can search for blood donors from blood
group
 Can view medical service providers
information
Medical Service
Provider
 Confirming blood donation request
 Confirming ambulance hiring request
 Can edit/delete ambulance
advertisements
 Software Requirements:
• Windows 7 or above

Operating • JRE 1.8

• MySQL Server
Environmen Hardware Requirements:
t • Core i3 Processor
• 4GB Ram
• 25 GB HDD in machine and
500GB HDD in server machine
 Encrypted and wirelessly networked

Need Password to access Database

Design and
Recommended to use less RAM and
Implementation processing power
Constraint
ID and Password should be Unique

Only the admin has full access

 Valid user id and password are
required
Assumptions Server must be up and
and operating

dependenci To access any record, users

must first log in to the system
es
Records can only be deleted
by the Admins
REQUIREMENTS SPECIFICATIONS &
FEATURES
BUSINESS REQUIREMENTS

1. A short video clip called “How to Use E-Health Care System” should appear on the front page of
the system.
2. System design should be understandable.
3. Search functionality should show the result faster.
4. Patient should be able to easily search for desired Doctor, specific Ambulance, specific Blood
group.
5. User should be able to give complaint if they face any problems.
6. All complaint should look over within 24 hours.
7. Overall user friendliness of this system should be high.
SYSTEM FEATURES
 We have four users in this system , 1. Admin 2. Doctor 3. Patient 4. Medical Service
Provider.
 We divided all features into different modules. For Example:
Front Page Module (M1)

Function Description Database

M1F1 Users will be shown a front page that includes a navbar directing to N/A
login, Registration, doctor’s subscription, blog, about us.

M1F2 User can view blogs. Select ‘blog_name’, ‘blog_details’, ‘doctor_id’

form ‘blogs’ table.
 
Login Module(M2)
 
Function Description Database
M2F1 There will be a login page with 2 input fields n/a
one will take the users email address and
another will take input of the user’s password.
There will also be a login button which will be
used to submit form data for successful login to
the system using a post request.

M2F2 A backend form validation will occur which n/a

will validate the user’s credentials
submitted if they are secure to pass to the
database for validation.
Validations includes:
 Valid email syntax
 Email length < 50characters
 Null email and password field validation.
 Password length min. 8 characters and
max. 20characters.
Password contains alphanumeric
characters. If any invalid input is given then
error message should be shown to the view
page accordingly.
 SYSTEM FEATURES
M2F3 After passing the validation steps the user Search from database table ‘’users’’ and
must be searched by the email address in column “email” and return “password”,
the database and get the users email, “user_name”, “user_type” fields.
username and password. Then the  
password must be checked with the user  
submitted password if it matches with the  
database password for validation. If it  
matches then necessary credentials such
as user type, user name should be saved in
session of cookie storage and redirected to
the home page of the user using get
request. Upon not finding the user form
database or password mismatch an error
message must be shown to the view. Users
will be redirected to their designated view
according to their user type.
 
 SYSTEM FEATURES

Logout Module (M3)

Function Description Database

M3F1 User logged into the system can N/A

press a log out button which will
redirect them to a logout URL by
making a get request that clears
the previous session or cookie
credentials of the user which logs
him out of the system and takes
him to the login view page
Medical Service Provider Module (M7)

Function Description Database

M7F1 (Medical Service
Provider’s Dashboard (MSP))
After a successful registration and login to the system MSP will redirect  
to the MSP dashboard. In the MSP dashboard there is a navigation bar in
the top of the dashboard. This dashboard will contain some links such
as home, about us, contact, a dropdown button called “more” which
will contain some links such as profile, settings, logout. And in the
navigation bar there will be a button called “Post Add for Ambulance
Service”.

M7F2(Medical Service Provider After hitting “Profile” link(button) form navigation bar the MSP will be Select the whole row from table
‘s (MSP)Profile info) redirect to MSP profile page (route: /dashboard/msps_profile_info). In “m_s_p_s” where “email” = “email” and
this page every necessary information will be shown about MSP
“password”=”password”
him/herself (register info, blood donation status).

M7F3 (Medical Service After hitting “settings” link(button) from navigation bar the MSP will be Example Database query is given below:
Provider’s (MSP) settings page) redirect to the settings page where he/she can update their UPDATE users
information such as ‘name’, ‘username’, ‘email’, ‘selectdate’, ‘phone
SET “full_name”= “full_name WHERE
no’, ‘nid no’, ‘password’, ‘confirm password’, ‘select gender’, ‘blood
type’, ‘upload your photo with the help of some individual form for “email”= “email”;
each field. Example Route are given below:
 
Route::post('/dashboard/full_name',
'SettingsController_edit_full_name')->name('change_full_name');
 

 
 
 
 
M7F4 (Medical Service Provider’s
(MSP) Advertisement From)
M7F5 (Medical Service
Provider’s (MSP) show all
posted advertisement and
details)
And also, there will be a Button called “Save Change” for save every
change. The MSP will set himself eligible for blood donation form this
settings page with the help of two radio button called 1. Enable 2.
Disable. MSP can also delete his/her account form this page with the
help of a form by providing a valid password.
After hitting “Post Add For Ambulance” link(button) from navigation Use insert query to store information to
bar the MSP will be redirect to the Advertisement form named “Add database. (Eloquent ORM : $advertisement
Post for Ambulance Service” with field “select inner air system”,
->save(); )
“select Ambulance type”, “upload a ambulance photo ”,
“rate(per_kilometer)”, “phone”, “Ambulance Feature ”. Every field is
required and in the backend every input must be go through validation
such as photo must be (jpg, png,jpeg) type. Rate field input must be
numeric.
In order to show all the posted advertisement there will be a “All # Select All form Advertisement table.
Posted Advertisement page”. Where all posted Advertisement will be  
shown in a particular format depends on CSS/bootstrap (front end # Delete from Advertisement table where
development). At the top of the “All Posted Advertisement Page” there add_id = add_id
must be a “Search” feature to find a particular advertisement easily.
Each advertisement view must contain “Details” link(button) in order
to redirect to details page in order to show all information with
availability about that ambulance. MSP can also delete advertisement
from this page with the help of “Delete Button” attached with
advertisement view. In this details page there must be a rent option
(button). After clicking “Rent Now” button the MSP will redirect to
Payment option such as “cash on”, “credit card” e.t.c option will be
shown which is called payment system. For rent a ambulance the MSP
must be go through payment system.
M7F6(Medical Service In order to show all the ambulance, rent record there Select “rented_from” ,“rented_by” ,
Provider’s (MSP) show all must be a “record view page” where all rent information record creation date form
ambulance rend record page such as “rented from”, “rented by”, rent date and time Ambulance_rent_record table.
and details) will show in that page.

M7F7 (Medical Service To edit advertisement information there will be a UPDATE users
Provider’s (MSP) edit “edit_Add_form” with previous information. And also, a SET “phone_no”= “phone_no”, column2 = value2,
advertisement page) button called “save_change” to save every change to the ...
database. WHERE “add_id”= “add_id”;

M7F8(Complain Form(page)) To send a complaint about any inconvenient to Admin there Use Eloquent ORM save function for insert
will be a complaint form with “complain_by”, query
“complaint_name”, “complaint_details” field. Every field is
required. User must fill up this form and submit with the
“submit” button.
BUSINESS REQUIREMENTS

SYSTEM SECURITY

1. Need to install SSL Certificates.

2. Input Field should be Sanitize/formatted appropriately.
3. Client side and server side both validations must be needed.
4. Automated website malware scanner should be used.
5. Vulnerability scanner must be needed.
6. Need to implement A web application firewall (WAF).
BUSINESS REQUIREMENTS

System Performance
1. System should operate and response faster.
2. System must have the capability of balancing the load.

Safety Requirements
System server should be in a safer place to protect from natural disasters, animal and human
made damages.
 BUSINESS REQUIREMENTS

Safety Requirements
System server should be in a safer place to protect from natural disasters, animal and human made damages.

Availability
Our target is to achieve more than 90% availability for this system. System should have 98% uptime. System should
not fail or undergoing a repair action when it needs to be used.

Usability
Our goal is, the system will be user friendly and faster to do the task of end user. The usability of the system will be
determined after the whole testing process.
We need to collect the user’s experience, opinion and requirements to determine the usability properly.
E-HEALTH CARE SYSTEM DATA MANAGEMENT

 Data Accuracy
 Data Consistency
 Data Security
 Data Backup & Recovery
SOFTWARE DESIGN SPECIFICATIONS &
DIAGRAMS 
Use Case Diagram
Er Diagram
User Interface Design (Front Page)
Login Page
Register Page
User Dashboard
Profile Page
Settings Page
Settings Page
Settings Page
Settings Page
Post Advertisement Page
Section 5- Requirements
validation
Formal Review (inspection Process)

In our project a formal review will be done as a high priority

process. In order to successfully complete this process. Project
manager will assign a team of 5 members. Each member has
their individual role to complete their process.
Process Of Formal Review

Planning Kick-off Preparation

Follow-up Rework Review Meeting

Planning

 In planning phase the author has to submit a request to the for an initial review.
Moderator is the leader of inspection process for this project. The moderator is
responsible for the review schedule such as date, time, location and invitation.
Moderator ensures that the document is ready for a review. The moderator also
selects how many pages to review from the documentation. Moderator decide
that who will play what role in our review meeting. Moderator identify the exit
criteria for the review. Moderator schedule the later stages of the review.
Kick-off

 An initial meeting called kick-off which ensures that every one of the inspection
team is at the same level regarding the document to be reviewed. A short
introduction about objectives of review and documents is given in this meeting.
Any relationship between the document under review and other document is
explained. Distribution of the documents under review, source documents and
related documents is also done.
Preparation

In the preparation phase our participant works individually on the documents to

identify defects, doubts and comments according to their understanding about
documents. One member of the team has to record all the issues like spelling
mistakes and annotate them in document. In this phase we should not try to
exceed the checking rate of documents.
Review Meeting

Review meeting consists of three phases- logging, discussion, and decision phase.

Logging Phase: Every defect is logged in logging phase. Defects identified by individuals are logged
page by page, reviewer by reviewer by the author.

Discussion Phase: Discussion about the defects and issues start in this phase. Participants bring forward
their comments and reasoning about the issues in this phase.

Decision Phase: In this phase the decision on the documents under discussion is made based on the exit
criteria. If the document does not meet the criteria then re-reviews are done.
 
Rework
 In rework phase the author improves the reviewed document based on the
comments in review meeting. Our author analyzes the defect and decide
that what needs to be changed. The changes made by our author are re-
reviewed in this phase.
Follow-up

All the changes made by our author in rework phase are re-reviewed in follow-
up phase. Our moderator also distributes the updated document to all the
participants and collects feedback from them.
Software project management plan

Software project management is referred to as the couple of tasks

related to managing the project as planning, considering the scope of
the software product, scheduling of tasks and events, estimating the
cost in various terms and resource management. Project management
activities need knowledge, skills, tools, resources and proper
management ability. This area consumes different types of
responsibilities such as planning, control and implementation. The
project should be integrated with the feasibility studies.
Project Estimation

In this project Constructive Cost Model will be used for calculation estimation. So,
 #Coefficient: 3.0
# Project complexity P: 1.12
# SLOC dependent coefficient T: 0.35
# Source line of code (guessed) SLOC: 12000
Effort Estimation Formulas:
Effort = PM = Coefficient * (SLOC/1000) ^P
Development Time = DM = 2.50 * (PM) ^T
Required number of people = ST = PM/DM
Using these formulas, we get,
Effort = PM = 3.0 * (12000/1000) ^1.12 = 48.5 person-days needed for the project (labor working
hours)
Development Time = DM = 2.50 * (48.5) ^0.35 = 9.77 Weeks (week-days)
Required number of people = ST = 48.5/9.77 = 4.96
Cost:
Labor cost: 4.96 * 50000 = 248000/= Taka (Approximately)
Service cost: 20000=20000/=
268000/= taka (Approximately)
Project Scheduling (Tasks)

Project Manager: Developer/Quality Tester:

1. Project Analysis 1. System Development
2. Define user requirements 2. Web Pages
3. Analyzing websites requirements 3. Databases
4. Cost & functionality analysis
4. Components test
Project Manager/Developer:
Developer:
1. Design
1. System Integration
2. Define standards
3. Design website’s structure 2. Link Pages
4. User Interface 3. Link Databases
5. Prototyping
 Project Scheduling (Tasks)

Quality Tester:

1. System Test & Trial

2. User Interface
3. Page links
4. Database access

5. Exception handling

6. Connect to the internet

Risk assessment

There are significant risks related to e-health projects. Followings are noticeable of them,

 System failure to give the expected output

 Deadline missing
 Unsatisfied customer’s review
 Completion Delay
 Insufficient numbers of Transport (Ambulance)
 Insufficient Blood Bank service
 Technical discontinuity
 Slowly updating information
 Lack of the experience of the programmer
 Project Cancelled
Conclusion

Considering the above discussions we can reach the decision that a-

healthcare management system is a cutting edge technology to ensure
health care services to all classes of people. E-health care management
system comes out exploring the Information Technology and Health
services binding together. The specialized expert doctors, ambulance
service, all time needed blood -all these life-saving equipment is
managed in this single system. No one has to panic if the situation
requires an emergency doctor at the time of pandemic or from
inaccessibleness or the financial or physical crisis resist anyone from
check out the doctor’s chamber
A virtual, hassle free doctor’s chamber lies through this application. To
ensure the telemedicine service for all, this application is proposed and
created with the permission of experts. Therefore, a user -friendly UI is
built keeping in mind that senior people and the children may easily call
the emergency services. In spite of some risks assessment the proposed
system will meet its purpose by the proper implementation and further
developments of this project will be looking forward to more challenges.