EMERGENCY ALERT SYSTEM

A PROJECT REPORT

Submitted by

DIKSHA DIVASALIWALA
200410107009

ROMA KATARIA
200410107022

SALONI SHAJAN
210410107501

In fulfillment for the award of the degree of

BACHELOR OF ENGINEERING

in
Computer Engineering

Sardar Vallabhbhai Patel Institute Of Technology, Vasad

Gujarat Technological University, Ahmedabad

[ April 2024 ]
 Sardar Vallabhbhai Patel Institute Of Technology
Vasad

CERTIFICATE
This is to certify that the project report submitted along with the project entitled

Emergency Alert System has been carried out by Diksha Divasaliwala [200410107009],

Roma Kataria [200410107022] and Saloni Shajan [210410107501] under my guidance

in fulfillment for the degree of Bachelor of Engineering in Computer, 8th Semester of

Gujarat Technological University, Ahmedabad during the academic year 2023-24.

Prof. Nisha Velani Dr.Neha Soni

Internal Guide Head of the Department
CE-Department CE-Department
 Sardar Vallabhbhai Patel Institute Of Technology
Vasad

DECLARATION
We hereby declare that the Project report submitted along with the Project entitled

Emergency Alert System submitted in fulfillment for the degree of Bachelor of

Engineering in Computer Engineering to Gujarat Technological University, Ahmedabad, is

a bonafide record of original project work carried out by us at Sardar Vallabhbhai Patel

Institute Of Technology, Vasad under the supervision of Prof. Nisha Velani and that no

part of this report has been directly copied from any students’ reports or taken from any

other source, without providing due reference.

Name of the Students Sign of Students :

Diksha Divasaliwala

Roma Kataria

Saloni Shajan
 ACKNOWLEDGEMENT
We extend our heartfelt gratitude to all those who have contributed to the successful
completion of our project, "Emergency Alert System," which marks a significant
milestone in our academic journey.
We would like to express our deepest appreciation to our Project Guide, Prof. Nisha Velani,
for her invaluable guidance, unwavering support, and insightful feedback throughout the
duration of this project. Her expertise, encouragement, and dedication have been
instrumental in shaping our ideas and refining our approach.
We are also indebted to the faculty members of Sardar Vallabhbhai Patel Institute of
Technology for providing us with an enriching learning environment and for their
continuous encouragement and support.
Furthermore, we extend our gratitude to our peers, whose collaborative efforts and
constructive feedback have greatly contributed to the success of this project.
Last but not least, we would like to acknowledge the support of our friends and family
members for their patience, understanding, and encouragement during the challenging
phases of this project.
Thank you all for being a part of this journey and for your unwavering support.

i
 ABSTRACT

Healthcare has become increasingly vital in recent years, prompting the

development of innovative solutions such as IoT-based health monitoring
systems. Leveraging the Internet of Things (IoT) technology, these systems
offer real-time monitoring of patient health parameters, even from remote
locations. This report presents a health monitoring system capable of
continuously tracking vital signs such as heartbeat and temperature. Through
a Wi-Fi module-based communication system, patient data is seamlessly
transmitted to a server for storage and analysis. Authorized personnel can
access this data via our website platform, enabling remote diagnosis and
proactive intervention by healthcare professionals. By providing timely
information on patient health status, this IoT-based monitoring system
enhances healthcare delivery, enabling prompt medical intervention and
potentially saving lives in critical situations. Additionally, the system
incorporates an SOS feature using GPS, allowing patients to send distress
signals in emergencies. By providing timely information and emergency
assistance, this IoT-based monitoring system enhances healthcare delivery,
potentially saving lives in critical situations. This project is designed using
Arduino uno and esp8266 microcontroller development board, LM35
industrial grade temperature sensor, Neo 6m GPS module and GSM Module .

ii
 List of Figures

Fig 1.1 Gantt Chart- Month: January-February................................................................7

Fig 1.2 Gantt Chart- Month: March..................................................................................7

Fig 1.3 Gantt Chart- Month: April....................................................................................7

Fig 2.1 Activity Diagram..................................................................................................13

Fig 2.2 Use case Diagram.................................................................................................13

Fig 3.1 DFD Level – 0......................................................................................................18

Fig 3.2 DFD Level – 1......................................................................................................18

Fig 3.3 System Block Diagram.........................................................................................19

Fig 4.1 Arduino Uno …………………………………………………………….….…..22

Fig 4.2 NodeMCU ESP8266 …………………………………………………….……..22

Fig. 4.3 LM35…………………………………………………………………….…......23

Fig. 4.4 Pulse Sensor………………………………………………………………........23

Fig. 4.5 NEO GM GPS Module…………………………………………………….......23

Fig. 4.6 SIM800L GSM Module………………………………………………………..23

Fig. 4.7 Database: “meditrack1”………………………………………………………..24

Fig. 4.8 Website: Pre-Login Homepage ………………………………………………..25

Fig. 4.9 Website: Patient Login page …………………………………………………...26

Fig. 4.10 Website: Patient Signup page ………………………………………………...26

Fig. 4.11 Website: Patient Post-Login Homepage ……………………………………...27

Fig. 4.12 Website: Patient Medical History Update form …………………………........27

Fig. 4.13 Entering Contact No. for verifying submitted Medical History……………...28

Fig. 4.14 Verifying Medical History ……………..……………………………………..28

Fig. 4.15 View Medical History using Contact No.……………..…….………………...28

iii
Fig. 4.16 Viewing Medical History……………………… ……………………………..29

Fig. 4.17 Website: Appointment Scheduling page…………………………………….…29

Fig. 4.18 Website: Patient Health Data Monitoring Page ………………………….……30

Fig. 4.19 Temperature Data Monitoring Page …………………………………………..30

Fig. 4.20 Pulse sensor Data Monitoring Page …………………………………………...31

Fig. 4.21 Website: Doctor Signup Page ………………………………………………....31

Fig. 4.22 Website: Doctor Login Page ……………………… ………………………..32

Fig. 4.23 Website: Doctor Post-Login Home Page……………………………………....32

Fig. 4.24 Website: Patient history monitoring for doctor …………………………….…33

Fig. 4.25 Website : Searching For a particular patient history ……….......………….….33

Fig. 4.26 SOS : Live Location Tracking …………………………………………….….34

Fig. 4.27 Hardware : Circuit Diagram …………………………………………….……34

iv
 List of Tables

Table 3.1 Database : Patient_signup table .....................................................................16

Table 3.2 Database : Doctor_signup table......................................................................17

Table 3.3 Database : Appointment table.........................................................................17

Table 3.4 Database : History table..................................................................................17

Table 3.5 Database : Medical Records table...................................................................17

Table 5.1 Login Test Case ……………………………..................................................37

Table 5.2 Error Handling Test Cases for Viewing Medical History ...............................38

Table 5.3 Medical history update test case .....................................................................38

v
 Abbreviations

NodeMCU Node MicroController Unit

GPS Global Positioning System

GSM Global System for Mobile Communications

IDE Integrated Development Environment

SQL Structured Query Language

HTML Hyper Text Markup Language

CSS Cascading Style Sheets

PHP Hypertext Preprocessor

TC Test Case

ID Identification

vi
 Table of Contents

Acknowledgment.............................................................................................................i
Abstract…........................................................................................................................ii
List of Figures .................................................................................................................iii
List of Tables ...................................................................................................................v
List of Abbreviations .......................................................................................................vi
Table of Contents .............................................................................................................vii
Chapter 1 Introduction to Project …...…………………………...………….….……..1
1.1 Project summary……………………………………………………..…………....2
1.2 Purpose…………………………………..………………………………………..2
1.3 Objective…………………………………..……………………………………...2
1.4 Scope……………………………..……………………………………………….3
1.4.1 Functionality Highlights:...............................................................................3
1.4.2 Limitations and constraints............................................................................3
1.5 Technology and Literature review………………………………….……………..3
1.5.1 HTML……....................................................................................................3
1.5.2 Javascript(Bootstrap).....................................................................................4
1.5.3 PHP……………............................................................................................4
1.5.4 MySql……………........................................................................................4
1.6 Project planning…………………………………………………………...……...5
1.6.1 Project Development Approach and Justification………….........................5
1.6.2 Project Effort, time and Cost Estimation......................................................5
1.6.3 Roles and Responsibilities............................................................................6
1.6.4 Group Dependencies.....................................................................................6
1.7 Project scheduling………………………………………………….…………....6
Chapter 2 System Analysis ……………………………………………………………8
2.1 Study of Current System…………………............................................................9
2.2 Problem and Weaknesses of Current System………………………………….....9
2.3 Requirements of New System…………………....................................................9
2.4 System feasibility ……..…………………............................................................9
2.5 Features of New/Proposed System…………........................................................11

vii
 2.6 Main modules…………..……………..................................................................12
2.7 Selection of Hardware and Software……….........................................................12
2.8 Activity/Process in new System ……………………...........................................13
Chapter 3 System Design ……………….……..…………………………….………..14
3.1 System Design & Methodology ………………………………..……………….15
3.2 Database Design..………………..………………………………………………16
3.3 System Architecture………………..…………………………………………....18
3.3.1 Data Flow Diagram……………………..…………………………….……18
3.3.2 Block Diagram(Hardware)……….….…..…………………………………19
Chapter 4 Implementation…………………………………………………………....20
4.1 Implementation environment……………………………………………………21
4.1.1 Hardware Platform………………………………………………………...21
4.1.2 Software Environment: …………………………………………………...21
4.1.3 Development Tools and Libraries: …………………………..……………21
4.1.4 Development Environment Setup: …..……………………………………22
4.2 Technology / Modules Specifications………….………………………………..22
4.2.1 Microcontrollers ………………………………………………………..…22
4.2.2 Sensors ……………………………………………………………………23
4.2.3 Software Technologies ……………………………………………………24
4.3 Results / Outcomes ……………....…………………………..…….……………24
4.3.1 Implementation: Database…………………………………………………24
4.3.2 Implementation: Website…………………………………………………..25
4.3.3 Implementation: Hardware………………………………………………...34
Chapter 5 Testing …………..……………………………………….…………………35
5.1 Testing plan /Strategy ………………………………………………….………..36
5.2 Test results and analysis……………………………………………………........36
5.2.1 Test Case 1: Login Validation ………………………………….…………37
5.2.2 Test Case 2: Error Handling for viewing Medical History ..……………...38
5.2.3 Test Case 3: Updating Medical History………………………….………..38
Chapter 6 Conclusion …………………………………………………………..….....39
6.1 Overall analysis of Project viabilities……………………………...……………40
6.2 Dates of continuous evaluation…………………………………………….…....40

viii
 6.3 Problem Encountered And Possible Solutions…………………………………..41
6.3.1 Problems Encountered …………………………………………………….41
6.3.2 Possible Solutions …………………………………………………………41
6.4 Summary of Project work…………………………………………….……….....42
6.5 Limitation and future enhancement………………………………………..….....42
References …...................................................................................................................44

ix
Team ID : 444215 INTRODUCTION TO PROJECT

CHAPTER 1
INTRODUCTION TO PROJECT

Gujarat Technological University 1 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

1.1 PROJECT SUMMARY:

The increasing number of fatalities due to a lack of timely medical intervention underscores
the critical need for continuous patient monitoring systems. Many lives are lost because
doctors cannot continuously monitor their patients. To address this pressing issue, our
project focuses on the development and implementation of an IoT-based health monitoring
and Emergency Alert system.

This system utilizes wearable sensors to track vital signs like heartbeat and temperature,
transmitting data via Wi-Fi to a centralized server. Authorized personnel can access this
data through a dedicated website, enabling remote patient monitoring and timely
intervention. Additionally, an SOS feature using GPS allows patients to send distress
signals in emergencies, enhancing the system's capability to provide immediate assistance
and potentially saving lives.

1.2 PURPOSE :
The purpose of our project is to develop an IoT-based health monitoring system to address
the crucial need for continuous patient monitoring. This system aims to provide real-time
tracking of vital signs, such as heartbeat and temperature, from any location, ensuring
prompt medical intervention in critical situations and ultimately saving lives.

1.3 OBJECTIVE :

Our project aims to develop an IoT-based health monitoring system with the following
objectives:

• Continuous Patient Monitoring: Implement a system capable of continuously

tracking patients' vital signs, such as heartbeat and temperature, in real-time.

• Remote Accessibility: Enable authorized personnel, including doctors, to access

the collected data remotely through a dedicated website platform.

• Prompt Medical Intervention: Provide timely alerts to medical personnel in case

of any variations in the patient's condition, ensuring prompt medical intervention.

• Emergency Assistance: Incorporate an SOS feature using GPS technology,

allowing patients to send distress signals in emergencies, enhancing the system's
capability to provide immediate assistance.

Gujarat Technological University 2 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

• Data Analysis and Storage: Develop a centralized server for the storage and
analysis of collected data, facilitating informed decision-making and long-term
patient management.

1.4 SCOPE :

1.4.1 Functionality Highlights:

• Continuous monitoring of vital signs.

• Real-time data transmission and remote monitoring.

• Emergency alerts for critical conditions.
• Integration with GPS and GSM for location tracking and communication.
• Data analysis and visualization for medical professionals.
1.4.2 Limitations and Constraints :

• Diagnose or treat medical conditions.

• Make autonomous decisions regarding patient care.

• Guarantee absolute accuracy due to potential sensor errors.
• Provide emergency response without human intervention.

• Ensure compatibility with all medical devices.

1.5 TECHNOLOGY AND LITERATURE REVIEW :

In our project, the front-end development utilizes HTML, CSS, JavaScript (Bootstrap), and
PHP, while the back-end database management system is MySQL.We adhere to the iterative
model for project development, following the Software Development Life Cycle (SDLC)
scenario for comprehensive project management.

1.5.1 HTML

• HTML, or Hyper Text Markup Language, serves as the standard markup language
for creating web pages.

• It describes the structure of a web page through a series of elements, which instruct
the browser on content display.

Gujarat Technological University 3 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

1.5.2 JavaScript (Bootstrap)

• JavaScript, along with the Bootstrap framework, enhances the interactivity and
responsiveness of our web pages.

• Bootstrap is a front-end framework that simplifies the process of designing

responsive and mobile-first websites.

• JavaScript, combined with Bootstrap, facilitates dynamic content manipulation,

form validation, and user interface enhancements.

• Utilizing Bootstrap components such as modals, carousels, and dropdowns

enhances the user experience and improves overall website functionality.

1.5.3 PHP

• PHP, a server-side scripting language, is utilized for server-side processing and

database interactions in our project.

• PHP seamlessly integrates with HTML, allowing dynamic content generation and
database connectivity.

• With PHP, we can perform tasks such as form handling, data validation, and user
authentication, enhancing the functionality of our web application.

• Additionally, PHP enables seamless interaction with MySQL databases, facilitating

efficient data retrieval, storage, and manipulation.

1.5.4 MySQL

• MySQL is an open-source relational database management system (RDBMS)

employing Structured Query Language (SQL) for data manipulation.

• It seamlessly integrates with popular server-side scripting languages like PHP,

facilitating robust database management in various web development scenarios.

• It is a multithreaded, multi-user, SQL (Structured Query Language) relational

database server (RDBMS).
• Data can be stored, updated and deleted using languages such as PHP. The data can
be retrieved from the database to allow the generation of dynamic Webpages.

Gujarat Technological University 4 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

1.6 PROJECT PLANNING:

Project planning for the development and implementation of the Health Monitoring and
Emergency Alert System involves several crucial steps to ensure its successful execution
and delivery.

1.6.1 Project Development Approach and Justification

In this project, the following activities were undertaken:

• Researching and identifying cost-effective and accurate sensors for continuous

patient monitoring.

• Selecting microcontroller boards, NodeMCU, and Arduino Uno, for seamless

integration with the chosen sensors.

• Procuring hardware components and initiating individual setup and calibration of

each sensor.

• Establishing a ThingSpeak channel for cloud-based storage of patient data, ensuring

accessibility and monitoring capabilities.

• Commencing the development of the web interface, including basic design and
layout using HTML, CSS, JavaScript (Bootstrap), and PHP for database
connectivity.

• Integrating the collected data from sensors with the web interface to provide real-
time monitoring.

Justification:

• The utilization of NodeMCU and Arduino Uno microcontroller boards was essential
for their compatibility and ease of integration with the selected sensors.

• HTML, CSS, JavaScript (Bootstrap), and PHP were chosen for website
development due to their versatility and compatibility, enabling the creation of a
dynamic and user-friendly interface for monitoring patient data.

• ThingSpeak was selected for cloud-based storage due to its ease of use and
compatibility with the project requirements, facilitating seamless data access and
monitoring from anywhere.

Gujarat Technological University 5 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

1.6.2 Project Effort, Time, and Cost Estimation

• Setting up the entire hardware and software system: An estimated timeframe of 4-5
weeks is allocated to ensure meticulous attention to compatibility, proper
configuration, and comprehensive testing.
• Modifying database structures and integrating with the system: This task is
anticipated to take approximately 1-2 weeks, considering potential challenges such
as data migration and ensuring seamless functionality.
• Challenges may arise during system setup and integration due to intricate hardware
and software dependencies, potentially impacting the overall project timeline.
• It is important to note that the cost primarily encompasses expenses related to
hardware sensors and boards. However, unforeseen circumstances, such as
malfunctioning sensors, may lead to additional expenditures.

1.6.3 Roles and Responsibilities

• Research and Procurement of Hardware and Sensors

• System Integration and Calibration
• Development of Web Interface and Database Connectivity
• Monitoring the data transmitted from sensors to the cloud
• Testing and Quality Assurance

1.6.4 Group Dependencies

Collaboration in live projects necessitates efficient task allocation among team members,
encompassing responsibilities such as hardware setup, sensor calibration, software
development, and database management.

Specific duties include addressing sensor issues, ensuring compatibility across hardware,
cloud, and database systems, as well as verifying the accuracy and functionality of the
"MediTrack" website. Additionally, the team is tasked with resolving any data duplication
and accuracy concerns, while ensuring the seamless operation of all website pages.

1.7 PROJECT SCHEDULING :

Project scheduling, an essential aspect of software project management, serves as the

culmination of meticulous planning activities. Combined with estimation methods and risk
analysis, scheduling establishes a roadmap for effective project management.

Gujarat Technological University 6 SVIT

Team ID : 444215 INTRODUCTION TO PROJECT

Commencing with process composition, project characteristics are utilized to adapt an

appropriate task set for the work to be undertaken. The task network is then employed to
compute critical project paths, generate a timeline chart, and provide essential project
information.

• Gantt chart :

Fig 1.1 Month-January & February

Fig 1.2 Month-March

Fig 1.3 Month-April

Gujarat Technological University 7 SVIT

Team ID : 444215 SYSTEM ANALYSIS

CHAPTER 2
SYSTEM ANAYLSIS

Gujarat Technological University 8 SVIT

Team ID : 444215 SYSTEM ANALYSIS

2.1 STUDY OF CURRENT SYSTEM :

Current healthcare monitoring systems suffer from limitations such as limited accessibility,
lack of real-time monitoring, and insufficient emergency response features. These
drawbacks underscore the need for a more advanced and comprehensive solution.
Additionally, current systems are often not user-friendly and may be difficult for individuals
unfamiliar with technology, such as the elderly, to understand and utilize effectively.

2.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM :

• Lack of real-time monitoring for temperature and pulse.

• Inability to track user location in real-time.

• Limited scalability to accommodate additional sensors or devices.

• Limited accessibility to health data for healthcare providers and caregivers.

2.3 REQUIREMENTS OF NEW SYSTEM :

The inadequacies of existing systems highlight the pressing need for a more efficient and
effective healthcare monitoring solution. The new system aims to address these limitations
by leveraging IoT technology to offer enhanced monitoring and emergency response
capabilities. Current systems often lack comprehensive real-time monitoring and
emergency response features, necessitating the development of a more advanced solution.
The integration of GPS technology in the new system ensures accurate location tracking in
emergencies, facilitating timely assistance.

Additionally, the system enables remote access for healthcare professionals to view and
analyse patient data, enhancing collaboration and enabling prompt intervention, even from
a distance. Therefore, the new system, leveraging IoT technology and GPS availability,
aims to bridge the gaps in existing healthcare monitoring systems and provide
comprehensive, timely, and remote services.

2.4 SYSTEM FEASIBILITY :

A feasibility study considers various constraints within which the system should be
implemented and operated. In this stage the resource needed for implementation such as
computing equipment, manpower and costs are estimated. The estimated are compared with
available resources and a cost benefit analysis of the system is made. The main objectives

Gujarat Technological University 9 SVIT

Team ID : 444215 SYSTEM ANALYSIS

of the feasibility study are to determine whether the project would be feasible in terms of
the following categories:

• Technical feasibility
• Economic feasibility
• Operational feasibility
• Schedule feasibility

Technical Feasibility:

Evaluation: Assessing technical feasibility involves determining whether our system can be
implemented using available technology.

Integrating IoT temperature sensors, pulse sensors, and GPS tracking is technically feasible,
utilizing available hardware and wireless communication protocols for seamless integration
and data transmission.

Considerations: Evaluating the compatibility of hardware and software components, the

feasibility of integrating IoT and GPS technologies with IoT-based cloud platforms and our
website, and the availability of necessary expertise for system development and
maintenance.

Outcome: A positive technical feasibility assessment indicates that the system can be
successfully implemented using existing technology and resources.

Economic Feasibility:

Economic feasibility examines whether the proposed system is financially viable and cost-
effective. For declaring that the system is economically feasible, the benefits from the
project should exceed or at least to the equal to the cost of development.

The considerations involve estimating the initial investment required for hardware,
software, development, and implementation costs, as well as ongoing operational expenses.

A favourable economic feasibility assessment demonstrates that the benefits derived from
the system outweigh the costs incurred, resulting in a positive return on investment.

Gujarat Technological University 10 SVIT

Team ID : 444215 SYSTEM ANALYSIS

Operational Feasibility:

Operational feasibility assesses whether the proposed system aligns with organizational
goals and can be effectively integrated into existing workflows and processes.

Considerations include evaluating the impact of the system on day-to-day operations, the
ability of users to adapt to new technology, and the availability of necessary resources and
support. We provide constant monitoring along with emergency SOS alerts from patients.
Caretakers can monitor the patients' vitals from the website itself, providing constant care.

Operational feasibility ensures that the proposed system can be seamlessly incorporated
into existing operations, enhancing efficiency and effectiveness.

Schedule Feasibility:

Schedule feasibility examines whether the proposed system can be developed and
implemented within the specified timeframe.

The considerations involve estimating the time required for system development, testing,
deployment, and user training, as well as identifying potential risks and mitigating
strategies.

A positive schedule feasibility assessment ensures that the project can be completed within
the agreed-upon timeline, meeting stakeholder expectations and project objectives.

2.5 FEATURES OF NEW SYSTEM / PROPOSED SYSTEM:

1. Continuous Vital Sign Monitoring.

2. Emergency SOS Alert: Patients can trigger emergency SOS alerts directly from the
monitoring device in case of a medical emergency, notifying caregivers or medical
professionals.

3. Remote Monitoring: Caregivers can remotely access patient data and vitals through
a secure website, enabling constant monitoring and timely intervention if necessary.

4. User-friendly Interface: Intuitive user interface for both patients and caregivers,
facilitating easy navigation and understanding of vital sign data.

Gujarat Technological University 11 SVIT

Team ID : 444215 SYSTEM ANALYSIS

5. Scalability: The system will be scalable to accommodate additional users and

devices, allowing for future expansion and integration with other healthcare
systems.

2.6 MAIN MODULES :

• Patient/Member Signup & Login

• Doctor Signup & Login

• Pre-Login Home Page
• Member Landing Page after Successful Login

• Medical Professional Landing Page after Successful Login

• Appointment Management Page
• Medical History Page

• Health Data Monitoring Page for both Members and Medical Professionals

2.7 SELECTION OF HARDWARE AND SOFTWARE :

Hardware:
• LM35 industrial grade temperature sensor
• Pulse sensor
• Neo6m GPS module
• SIM800L GSM module
• ESP8266 Wi-Fi embedded microcontroller for communication
• Arduino Uno
Software:
• Website development using JavaScript, HTML, CSS for user interface and
interaction
• SQL Database Management System for storing patient data
• PHP for website and database connection
• Thingspeak cloud platform for data output.

Gujarat Technological University 12 SVIT

Team ID : 444215 SYSTEM ANALYSIS

2.8 ACTIVITY / PROCESS IN NEW SYSTEM :

Fig 2.1 Activity Diagram

Use Case Diagram :

Fig 2.2 Use Case Diagram

Gujarat Technological University 13 SVIT

Team ID : 444215 SYSTEM DESIGN

CHAPTER 3
SYSTEM DESIGN

Gujarat Technological University 14 SVIT

Team ID : 444215 SYSTEM DESIGN

3.1 SYSTEM DESIGN & METHODOLOGY:

The design and methodology of our project, the "Emergency Alert System," were
meticulously crafted to ensure seamless operation, reliability, and effectiveness in
healthcare monitoring and emergency response. The following outlines the key components
of our system design and the methodology employed during the development process:

Hardware Selection and Integration:

• We began by researching and selecting appropriate hardware components to fulfill

the system requirements. This included sensors for vital sign monitoring,
microcontrollers for data processing and communication, and additional modules
for GPS and GSM functionalities.

• Integration of these hardware components was carefully planned to ensure

compatibility and optimal performance. Prototyping and testing were conducted
iteratively to validate hardware functionality and compatibility.

Software Architecture and Development:

• Our software architecture comprised firmware development for microcontrollers,

backend programming for data management and processing, and frontend
development for user interface design.

• The firmware development involved writing code to interface with sensors, process
sensor data, establish communication with external devices such as GPS and GSM
modules, and transmit data to the cloud platform.

• Backend programming focused on creating databases to store patient data securely,

implementing algorithms for data analysis and emergency alert generation, and
establishing communication protocols for data exchange between hardware
components and the cloud server.

• Frontend development included designing a user-friendly interface for both patients

and medical professionals. Features such as real-time data visualization, alert
notifications, and interactive controls were implemented to enhance user
experience.

Gujarat Technological University 15 SVIT

Team ID : 444215 SYSTEM DESIGN

Cloud Integration and Data Management:

• We utilized cloud platforms such as ThingSpeak for storing and processing sensor
data in real-time. Integration with these platforms involved setting up data channels,
establishing secure communication protocols, and implementing data visualization
tools for remote monitoring.
• Data management strategies were implemented to ensure data integrity, security,
and accessibility. This included regular backups, encryption of sensitive
information, and access control mechanisms to protect patient privacy.

Testing and Validation:

• We tested our project a lot to make sure it worked the way it was supposed to. We
tested each part on its own, then put it all together and tested it again.

• We also got feedback from other people to see if they found any problems or had
any suggestions for improvements.

Methodology:

• Our development methodology followed an iterative approach, allowing for

flexibility and adaptability to changing requirements.

• We adopted agile principles, conducting regular meetings and reviews to track

progress and address any challenges encountered during the development process.

3.2 DATABASE DESIGN :

TABLES :

1. Member/Patient Signup:
Field Type
Full_name Varchar(100)
age Int (11)
Email Varchar (100)
password Varchar (255)
phn BigInt (10)
gender Varchar (20)

Table 3.1 Patient_signup

Gujarat Technological University 16 SVIT

Team ID : 444215 SYSTEM DESIGN

2. Doctor Signup table :

Field Type
dname Varchar (60)
email Varchar (80)
Uname Varchar (40)
Pass Varchar (30)
Phn BigInt (10)
Age Int (10)
Sex Varchar (20)
Specialist Varchar (80)
Table 3.2 Doctor_signup

3. Appointment table:

Field Type
fname Varchar (60)
lname Varchar (60)
Email Varchar (60)
phn BigInt (10)
Table 3.3 Appointment

4. Medical History table:

Field Type
Id Int(11)
contact_no Varchar(10)
name Varchar (100)
Current_medications text
Health_conditions text
surgeries text
height float
weight float
Blood_type Varchar (10)
Date Timestamp
Table 3.4 history

4. Medical Records table:

Field Type
Record_id int(11)
Contact_no Varchar(20)
File_path Varchar (255)
Table 3.5 medical_records

Gujarat Technological University 17 SVIT

Team ID : 444215 SYSTEM DESIGN

3.3 SYSTEM ARCHITECTURE:

3.3.1 Data Flow Diagram :

Fig 3.1 DFD Level – 0

Fig 3.2 DFD Level -1

Gujarat Technological University 18 SVIT

Team ID : 444215 SYSTEM DESIGN

3.3.2 Block Diagram (Hardware) :

Fig 3.3 System Block Diagram

Gujarat Technological University 19 SVIT

Team ID : 444215 IMPLEMENTATION

CHAPTER 4
IMPLEMENTATION

Gujarat Technological University 20 SVIT

Team ID : 444215 IMPLEMENTATION

4.1 IMPLEMENTATION PLATFORM / ENVIRONMENT:

4.1.1 Hardware Platform:

• Microcontrollers: We employed Arduino Uno and NodeMCU as the core

microcontroller boards for data processing and communication tasks.

• Sensors: Key sensors integrated into the system include the LM35 industrial grade
temperature sensor and the Pulse sensor for monitoring vital signs.

• Additional Modules: We incorporated the Neo6m GPS module and the Sim800l
GSM module for location tracking and emergency communication features.

• Other Components: Supporting components such as resistors, capacitors, antenna,

LEDs and connectors were also utilized to complete the hardware setup.

4.1.2 Software Environment:

• Arduino IDE: We utilized the Arduino Integrated Development Environment (IDE)

for writing and uploading firmware code to the Arduino Uno microcontroller.

• Web Development: Frontend development for the "MediTrack" website was carried
out using HTML, CSS, JavaScript, and PHP for server-side scripting.

• Database Management: MySQL was employed as the database management system

for storing patient data securely.

• Cloud Integration: ThingSpeak platform was utilized for real-time data storage and
processing in the cloud.

4.1.3 Development Tools and Libraries:

• Arduino Libraries: Standard Arduino libraries for sensor interfacing,

communication protocols (e.g., Serial communication), and GPS/GSM
functionalities were utilized.

• Bootstrap Framework: The Bootstrap framework was employed for frontend

development to ensure responsive and visually appealing website design.

• ThingSpeak API: We leveraged the ThingSpeak API to establish communication

between the hardware components and the cloud platform, enabling seamless data
transmission and retrieval.

Gujarat Technological University 21 SVIT

Team ID : 444215 IMPLEMENTATION

4.1.4 Development Environment Setup:

• Installation and Configuration: We installed the necessary software tools, including

Arduino IDE and web development tools, and configured them according to project
requirements.

• Hardware Setup: Hardware components were assembled and connected according

to the system architecture design, ensuring proper wiring and connectivity.

• Testing and Debugging: Initial testing and debugging were conducted to verify
hardware functionality and software integration, addressing any issues encountered
during the setup process.

4.2 TECHNOLOGY / MODULES SPECIFICATIONS :

In this section, we provide detailed specifications of the technologies and modules used in
the development of our project, the "Emergency Alert System."
4.2.1 Microcontrollers:
1. Arduino Uno:
• Microcontroller: ATmega328P
• Operating Voltage: 5V
• Digital I/O Pins: 14 (of which 6 provide PWM output)
• Analog Input Pins: 6
• Flash Memory: 32 KB (of which 0.5 KB used by bootloader)

2. NodeMCU:
• Microcontroller: ESP8266
• Operating Voltage: 3.3V
• Digital I/O Pins: 11
• Analog Input Pins: 1
• Flash Memory: 4 MB

Fig 4.1 Arduino Uno Fig 4.2 NodeMcu ESP8266

Gujarat Technological University 22 SVIT

Team ID : 444215 IMPLEMENTATION

4.2.2 Sensors:
1. LM35 Industrial Grade Temperature Sensor:
• Temperature Range: -55°C to +150°C
• Output Voltage: 10 mV/°C
• Accuracy: ±0.5°C

2. Pulse Sensor:
• Operating Voltage: 3.3V - 5V
• Output: Analog Pulse
• Detection Method: Photoplethysmography (PPG)
• Compatibility: Arduino and NodeMCU

Fig. 4.3 LM35 Fig. 4.4 Pulse Sensor

3. Neo6m GPS Module:

• Satellite System: GPS/QZSS, GLONASS
• Receiver Channels: 50
• Tracking Sensitivity: -161 dBm
• Update Rate: 1 Hz

4. Sim800l GSM Module:

• Operating Voltage: 3.4V - 4.4V
• Quad-Band GSM/GPRS Module
• Integrated TCP/IP Stack
• SMS and Call Functionality

Fig. 4.5 NEO GM GPS Module Fig. 4.6 SIM800L GSM Module

Gujarat Technological University 23 SVIT

Team ID : 444215 IMPLEMENTATION

4.2.3 Software Technologies:

1. Programming Languages:
• C/C++: Firmware development for microcontrollers
• HTML, CSS, JavaScript: Frontend development for web interface
• PHP: Backend scripting for server-side functionality

2. Development Tools:
• Arduino IDE: Integrated Development Environment for microcontroller
programming
• Sublime Text, Visual Studio Code: Text editors for web development

3. Database Management System:

• MySQL: Relational database for storing patient data securely
4. Cloud Platform:
• ThingSpeak: Cloud platform for real-time data storage and processing
4.2.4 Arduino Libraries:
• ESP8266WiFi: Enables NodeMCU connectivity to Wi-Fi networks for internet
access & data transmission.
• ThingSpeak: Facilitates communication with ThingSpeak cloud platform for
data logging.
• TinyGPS++: Parses GPS data streams for accurate location information.

4.3 RESULTS / OUTCOMES :

4.3.1 Implementation: Database

Fig. 4.7 Database: “meditrack1”

Gujarat Technological University 24 SVIT

Team ID : 444215 IMPLEMENTATION

4.3.2 Implementation: Website

Fig. 4.8 Website: Pre-Login Homepage

Gujarat Technological University 25 SVIT

Team ID : 444215 IMPLEMENTATION

• Member / Patient Side :

Fig. 4.9 Website: Patient Login page

Fig. 4.10 Website: Patient Signup page

Gujarat Technological University 26 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.11 Website: Patient Post-Login Homepage

Fig. 4.12 Website: Patient Medical History Update form

Gujarat Technological University 27 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.13 Entering Contact No. for verifying submitted Medical History

Fig. 4.14 Verifying Medical History

(On clicking Update details one can go back to update their medical history details. This
won’t create a new row in the database table .It will update the already existing row.)

Fig. 4.15 Viewing Medical History

Fig. 4.15 View Medical History using Contact No.

Gujarat Technological University 28 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.16 Viewing Medical History

Fig. 4.17 Website: Appointment Scheduling page

Gujarat Technological University 29 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.18 Website: Patient Health Data Monitoring Page

• Health Data Monitoring through Thingspeak :

Fig. 4.19 Temperature Data Monitoring Page

Gujarat Technological University 30 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.20 Pulse sensor Data Monitoring Page

• Medical Professional Side :

Fig. 4.21 Website : Doctor Signup Page

Gujarat Technological University 31 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.22 Website : Doctor Login Page

Fig. 4.23 Website : Doctor Post-Login Home Page

Gujarat Technological University 32 SVIT

Team ID : 444215 IMPLEMENTATION

Fig. 4.24 Website : Patient history monitoring for doctor

Fig. 4.25 Website : Searching For a particular patient history

Gujarat Technological University 33 SVIT

Team ID : 444215 IMPLEMENTATION

• SOS SMS:

Fig. 4.26 SOS : Live Location Tracking

4.3.3 Implementation: Hardware

Fig. 4.27 Hardware : Circuit Diagram

Gujarat Technological University 34 SVIT

Team ID : 444215 TESTING

CHAPTER 5
TESTING

Gujarat Technological University 35 SVIT

Team ID : 444215 TESTING

5.1 TESTING PLAN / STRATEGY :

We outline our approach to testing the "Emergency Alert System" to ensure its
functionality, reliability, and performance.

1. Unit Testing: To test individual components of the system, such as sensor data collection,
data transmission and database interactions.

2. Integration Testing: To verify the interaction and compatibility of our system components
when integrated together.

3. Regression Testing: To ensure that system changes or updates do not introduce new
defects or impact existing functionalities-run previously executed test cases after system
modifications to validate that existing features still work as expected.

5.2 TEST RESULTS AND ANALYSIS :

After conducting the testing activities outlined in the testing plan, the following key
findings and analyses are observed:

• Unit Testing: All individual components have been thoroughly tested, and no major
issues were identified. Minor bugs and discrepancies were addressed during the
testing phase.

• Integration Testing: The integration of system components proceeded smoothly,

with data flowing seamlessly between sensors, platforms, and databases. No
significant compatibility issues were encountered.

• Regression Testing: Regression tests confirmed that system changes and updates
did not introduce new defects or impact existing functionalities. Any issues
identified during regression testing were promptly addressed and resolved.

5.2.1 Test Case 1: Login Validation

This test case verifies the functionality of the login validation process within the
"MediTrack" system. It ensures that users attempting to access the system are authenticated
correctly, and invalid login credentials are appropriately handled.

Gujarat Technological University 36 SVIT

Team ID : 444215 TESTING

Test ID Test Condition Expected Output Actual Output Remarks

TC1 Verify that the login Required fields Required fields Positive
screen contains available. available.
elements such as
Contact no,
Password,Login
button,SignUp
button.
TC2 Verify the alert Alert message of Got alert of Field Positive
message when click field Required. required.
on Log-In button
without filling the
details.
TC3 Verify that the user Home page must Redirected to Positive
will be able to log in be shown. Home page.
their account with the
correct credentials.
TC4 Verify the error Alert message of Got alert of Field Positive
message should field Required. required.
display after just
entering an contact
no and leaving the
password field blank.
TC5 Verify the error Alert message of Got alert of Field Positive
message should field Required. required.
display after entering
an incorrect contact
no and password
combination.
TC6 Verify User User should be Verify that the Positive
Navigation After able to navigate user can
Logging In through the seamlessly
application navigate through
without the browser after
encountering any logging in,
navigation issues accessing
or errors. various pages
and features.

Table 5.1 Login Test Case

Gujarat Technological University 37 SVIT

Team ID : 444215 TESTING

5.2.2 Test Case 2: Error Handling for viewing Medical History

This series of test cases evaluates the system's response when users attempt to access
medical history information.

Test ID Test Condition Expected Output Actual Output Remarks

TC1 Enter an Error message Error message Positive
incorrect displayed: "Invalid displayed:
contact no Contact no. Please "Invalid Contact
during the try again." No. Please try
viewing process again."
and attempt to
access the
corresponding
data.
TC2 Attempt to view Error message Error message Positive
medical history displayed: "Invalid displayed:
with a blank or Contact No.” "Invalid Contact
empty contact No.”
field.
TC3 Enter a valid Medical history Medical history Positive
Contact No.and details for the details for the
attempt to view specified contact specified contact
the no. are displayed. no. are
corresponding displayed.
medical history.
Table 5.2 Error Handling Test Cases for viewing Medical History

5.2.3 Test Case 3: Updating Medical History

This test case examines the system's behaviour when updating a patient's medical history.
It ensures that modifications to medical records are properly managed, with a focus on
preventing duplicate entries and maintaining data accuracy.

Test ID Test Condition Expected Output Actual Output Remarks

TC1 Attempt to Error message Error message Positive
update medical displayed: "Please displayed:
history with fill in all fields." "Please fill in all
empty fields fields."
and verify error
handling.
TC2 Update medical Existing medical Existing medical Positive
history for the history record is history record is
same patient modified, not modified, not
and verify that a duplicated. duplicated.
new row is not
created.
Table 5.3 Medical history update test case

Gujarat Technological University 38 SVIT

Team ID : 444215 CONCLUSION

CHAPTER 6
CONCLUSION

Gujarat Technological University 39 SVIT

Team ID : 444215 CONCLUSION

6.1 OVERALL ANALYSIS OF PROJECT VIABILITIES :

The project on developing an Emergency Alert System demonstrates strong potential for
addressing critical gaps in healthcare monitoring and emergency response. Here's a
breakdown of its viability:

1. Market Demand: There is a growing demand for innovative healthcare solutions

that provide real-time monitoring and emergency assistance. The project directly
addresses this demand by offering continuous monitoring of vital signs and prompt
alerts in critical situations.

2. Technological Feasibility: The use of established technologies ensures technical

feasibility and scalability.

3. User-Friendliness: With a focus on creating a user-friendly interface and

integrating features accessible to both patients and medical professionals, the
project aims to overcome the usability challenges commonly encountered in current
healthcare monitoring systems. This aspect is particularly crucial for ensuring
acceptance among elderly users and individuals with limited technological
proficiency.

4. Competitive Advantage: By leveraging technologies like cloud computing and

IoT, the project offers features such as real-time data transmission and remote
monitoring, setting it apart from traditional healthcare monitoring systems.
Additionally, the integration of GPS and GSM modules enhances its emergency
response capabilities, providing a competitive edge in the market.

5. Cost-Effectiveness: The selection of cost-effective hardware components and

open-source software tools, along with the utilization of cloud platforms like
Thingspeak, contributes to the project's cost-effectiveness. This approach ensures
affordability without compromising on functionality and performance.

6.2 DATES OF CONTINUOUS EVALUATION :

• 1st evaluation : 03/02/24

• 2nd evaluation : 17/02/24
• 3rd evaluation : 02/03/24
• 4th evaluation : 16/03/24

Gujarat Technological University 40 SVIT

Team ID : 444215 CONCLUSION

• 5th evaluation : 30/03/24

• 6th evaluation : 06/04/24
• 7th evaluation : 13/04/24
• 8th evaluation : 20/04/24

6.3 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTIONS:

6.3.1 Problems Encountered:

The sensor readings were not being successfully transmitted to the cloud, disrupting the
real-time monitoring system. Additionally, the limited availability of analog pins on the
NodeMCU posed a challenge, as both the pulse and temperature sensors required it.
Furthermore, the GPS sensor took an extended period to establish a connection with
satellites, resulting in significant delays in obtaining location data.

6.3.2 Possible Solutions:

1. Code Modification: We addressed the issue by revising the code to ensure proper
integration and transmission of sensor readings to the cloud platform, thereby
resolving the data transfer failure.

2. Serial Connection with Arduino: To overcome the shortage of analog pins on the
NodeMCU, we implemented a serial connection with an Arduino board. This
allowed the temperature sensor to utilize the analog pins of the Arduino board,
effectively resolving the pin shortage issue.

3. Alternative Solution: Analog Multiplexer Module: Alternatively, we can

consider increasing the number of analog pins for the NodeMCU using a 16-
Channel Analog Multiplexer Module. This would provide additional analog input
channels, allowing for simultaneous use of multiple sensors without pin limitations.

4. Upgrade GPS Module: To address the delay in satellite connection, we can explore
the option of upgrading to a more efficient GPS module with improved satellite
acquisition capabilities. A high-sensitivity GPS module may significantly reduce
the waiting time and enhance the accuracy of location data retrieval, ensuring
prompt and reliable location tracking.

Gujarat Technological University 41 SVIT

Team ID : 444215 CONCLUSION

6.4 SUMMARY OF PROJECT WORK :

Our project focused on the development and implementation of an a comprehensive Health

Monitoring & Emergency Alert System aimed at addressing critical gaps in healthcare
monitoring and emergency response. The system's primary objective was to continuously
monitor vital signs, such as heartbeat and body temperature, and provide real-time alerts to
medical professionals and concerned people in case of critical conditions through SOS
feature.

The "MediTrack" website served as a central hub for users to access health data and
emergency alerts. Features included user authentication, patient/member signup and login,
medical professional signup and login, appointment scheduling, medical history tracking,
and real-time health data monitoring.

Through the website, professionals could monitor patients' vital signs and access their
medical histories. This feature enhanced patient care and allowed for proactive
intervention.

6.5 LIMITATION AND FUTURE ENHANCEMENT :

Limitation: Currently, the system relies on microcontrollers and sensors , which may limit
its portability and accessibility for users. While effective, the current setup may not be ideal
for users who require constant monitoring on the go.

Future Enhancement:

1. Miniaturization and Wearable Device: Future iterations of the system could focus
on miniaturizing the entire circuit and developing a wearable device. By
incorporating compact components and wireless connectivity technologies, such as
Bluetooth or LTE, the system could be transformed into a wearable device that users
can comfortably wear anywhere, ensuring continuous monitoring without
hindrance.

2. Website Refinement: Further refinement of the "MediTrack" website's user

interface and functionality is recommended to improve usability and accessibility.
Enhancements could include streamlining navigation, optimizing page loading
times, and implementing responsive design principles to ensure compatibility
across various devices and screen sizes.

Gujarat Technological University 42 SVIT

Team ID : 444215 CONCLUSION

3. Integration of Advanced Features: Integration of advanced features, such as

machine learning algorithms, holds promise for enhancing the system's capabilities.
By analyzing historical health data and patterns, machine learning algorithms could
enable the system to predict and detect early signs of medical emergencies, allowing
for proactive intervention and improved patient outcomes.

By addressing these limitations and implementing future enhancements, the "MediTrack"

system can evolve into a more versatile, user-friendly, and effective healthcare monitoring
solution, ultimately contributing to better patient care and outcomes.

Gujarat Technological University 43 SVIT

Team ID : 444215 CONCLUSION

REFERENCES
• Research Papers referred:
[1] Akhil Chandran Miniyadan , Nithya G P (2021). IOT BASED SMART
EMERGENCY ALERTING SYSTEM. International Journal of Computer
Engineering and Scientific Research, 8(3), 56-60.
https://troindia.in/journal/ijcesr/vol8iss3/56-60.pdf

[2] Sabukunze, I. D., Setyohadi, D. B., & Sulistyoningsih, S. (2021). Designing

An Iot Based Smart Monitoring and Emergency Alert System for Covid19
Patients , IEEE Xplore. https://ieeexplore.ieee.org/document/9418078

• Arduino IDE: https://www.arduino.cc/

• Thingspeak : https://www.mathworks.com/help/thingspeak/getting-started-with-
thingspeak.html
• Serial communication : https://www.hackster.io/RoboticaDIY/send-data-from-
arduino-to-nodemcu-and-nodemcu-to-arduino-17d47a

Gujarat Technological University 44 SVIT