DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

KKR & KSR INSTITUTE OF TECHNOLOGY AND SCIENCES

(Accredited by NBA|| Accredited with ‘A’ Grade by NAAC|| Approved by
A.I.C.T.E New Delhi || Affiliated to JNTUK, Kakinada)
Vinjanampadu (Vil), Vatticherukuru (Md), Guntur (DT), A.P-522017.

A PROJECT REPORT
On
“Patient health monitoring system”

Project guide: Team members:

Dr Bhanu Prakash, MTech., PhD., PDF (Malaysia) 17JR1A05C4-Ravali
Professor 17JR1A05E1-Devika
Department of CSE 17JR1A05C1- Haritha
KITS 17JR1A05C8- Harika
Guntur.
 INTRODUCTION

1.1 Introduction of project

Quick transportation frameworks and fast travel frameworks are nerves of financial
advancements for any country. Blunder and activity clog brings about long holding up times, loss
of fuel and money.[1] It is in this manner most extreme important to have a quick, temperate and
effective movement control framework for national improvement. The monitoring and control
of city traffic is becoming a major complication in many countries. With the ever
increasing number of vehicles on the road, the Traffic Monitoring Authority has to find new
methods of overcoming such a problem. One approach to enhance movement stream and
wellbeing of the present transportation framework is to apply robotization and keen control
techniques. As the quantity of street clients continually increments, and assets gave by current
frameworks are restricted, clever control of movement will turn into a vital issue later on.
Activity clog may come about because of substantial movement at an intersection. To
abstain from congestion there are such a significant number of activity administration strategies
accessible. Be that as it may, no method is flawless independent from anyone else as the ongoing
circumstances are by and large ceaselessly changing and the framework needs to adjust to
change in the consistently evolving conditions. We have made an attempt to provide some traffic
administration strategy which is self-changing in nature, so as to fit into continuously changing
real time traffic scenarios. We are detecting fire on the any of the lane, if fire is detected, in
control room the concern person will get notification in speech format using TTS which
present at PC side.

Need: Due to traffic issues in and around metro cities in India, people face a
tremendous hardship during regular commuting resulting in wastage of time, money and
energy. (This project is based on Traffic management system where the real time traffic
situations are handled to avoid delays at traffic junctions for the smooth functioning of traffic.
[3])Thus we felt a need that traffic should be handled during real time situations so as to avoid
the hardships of people traveling around, also this would help vehicles in emergency to
a certain extent.
Basic concept: Propose a system for controlling the traffic light by image processing. The system
will detect camera will be installed along the traffic light. It will capture image sequences. The
picture grouping will then be examined utilizing computerized picture handling for vehicle
discovery, and as indicated by activity conditions out and about movement light can be
controlled The framework depends on the AT89S52 miniaturized scale controller
technology.[2] The code for this undertaking will be coded in Python and the recreated
with Proteus programming.

1.2 Existing System

This system was first developed using sensors, but since sensors have a complicated
hardware and implementation , the project was developed using OpenCV and Matlab, which
made the project comparatively easy to implement and understand, also there were changes
in the hardware such as the microcontroller used was Rasberry Pi. The techniques used
were blob detection, blob analysis, vehicle counting, colour thresholding and background
subtraction. Various algorithms used were Haar Cascade, blob detection .The previous project
was implemented using video processing.

Problems of Existing System

 In existing solution the manual service provided by traffic police man.

 Manual system was operated with time based led traffic lights.

1.3 Proposed System

This system uses OpenCV as a software, and uses the concept of Image Processing. The
language that will be used is python. As observed in the previous implementation, since
Raspberry Pi is complicated and is difficult to work with ,we are using 8051
microcontroller so that it becomes easy to convert digital language into a binary one
.The techniques implemented are blob detection and colour thresholding . The algorithm
used here is viola jones algorithm. Additional feature that will be implemented is, our
system will be able to detect fire and will take the required actions, also we are
implementing this project using the python language. Speaking about the feasibility,
since we are using OpenCV as the software,the entire cost of the project is minimised.
1.4 Benefits of Proposed System
 It is useful during heavy traffic.
 Manual monitoring will be reduced at some extent.
 Police men effort will be reduced.
 Fatal risk of a patient will be reduced.
 Accuracy of time delay will reduced .

1.5 Literature Review

1.) Smart Traffic Control Using Open cv

Abstract—
We know that, the population of cities and vehicles on the road is increasing rapidly. On
account of this, controlling the roads have seamless traffic movement is major issue.
Today’s traffic management system has no emphasis on live traffic scenario, which leads
to inefficient systems. The traffic timers now installed show the present time making it an
open loop system. If incorporated a closed loop system, it will be possible to forecast the exact
time to regulate traffic light timers. If timers are made intelligent to predict exact time then the
system will be more efficient as it will greatly reduce the time wasted on unwanted green
signals . This project has been implemented by using OpenCV software and aims to
have SMART way for signal management which will ultimately be a cost effective solution.
The system includes a camera placed facing a lane that will capture images of the road
on which we want to control traffic. These images are efficiently processed to know the
traffic density. According to the processed data from OpenCV , a 8051 micro controller will send
command to the traffic LED timer to show particular time on the signal to manage traffic.
Keywords : Open CV, Image Processing, density based traffic control, Adaptive traffic
control system, fire detection

Conclusion:
In this paper, a method for estimating the traffic using OpenCV is presented. This is done by
using the camera images captured from the road lanes. Each image is processed separately
and the number of cars has been counted. This system guarantees that the average waiting
time of the vehicle in front of traffic signal will be lesser than present traffic control systems,
also the techniques and algorithms used in this project promises to be more effective as
compared to the previous system. The advantages of this new method include such benefits as
use of OpenCV over sensors, low cost, easy setup and relatively good accuracy and
speed. Because this method has been implemented using OpenCV software, production
costs are low while achieving high speed and accuracy .The implementation of this
system is not possible in rural areas since there are less number of vehicles present due to
which there are no traffic issues encountered.
References: V.Padmanabhan, M.Sornalatha,” Smart Saline Monitoring”, International Journal
of Scientific & Engineering Research, Volume 5, Issue 5, May-2014.
 SYSTEM ANALYSIS

2.1 Requirements Analysis

Requirements analysis, also called requirements engineering, is the process of determining user
expectations for a new or modified product. These features called requirements must be
quantifiable, relevant and detailed. In software engineering, such requirements are often called
functional specifications requirements analysis is an important aspect of project management.

Requirements analysis involves frequent communication with system users to determine specific
feature expectations, resolution of conflict or ambiguity in requirements as demanded by the
various users or groups, avoidance of feature creep and documentation of all aspects of the
project development process from start to finish.

Requirements analysis is a team effort that demands a combination of hardware, software and
human factors engineering expertise as well as skills in dealing with people.

2.1.1 Functional requirement Analysis

 The functional specification is a useful document which describes functions, appearance,

purpose and requested outputs of the software. It allows you to structure all the
information regarding an application.

2.1.2. User requirement

• Admin should provide exact time delay for each side signals to operate with density wise

• Most probably, the admin and the operators should be able to respond to the alert vehicles
In the particular direction of the high density side .

• We need to give a detailed awareness to police men and operators to maintain the
product should be used.

2.1.3. Non-functional requirements

• RELIABILITY: Our product has ability to perform its intended functions and operations
in a systems environment without any failure.
 • PERFORMANCE: Our application is effective, it will monitor and maintain a particular
time delay for each direction with the help of count of vehicles.

• SECURITY: All the traffic signals surveillance data is secured safely in a application
database.

2.1.4. System requirements

 An android or ios mobile

 Browser to access the application.
 Active internet is required to access the application.

2.2. Modules description

We have divided our project into 5 modules. They are:

• Pc with MATLAB software

• Digital image processing technics

• Arduino family based microcontroller board

• LED Indication

• Traffic controlling system

2.2.1.Level detection module :

• This module is used to check the level of the saline bottle.

• Water level indicator is very useful to indicate the liquid level in a saline bottle.

• A constant monitoring of the saline level in the bottle is required.

• So, for that purpose here we are using water level indicator.

2.2.2 Pulse detection module:

 • Pulse Sensor is a well-designed plug-and-play heart-rate sensor for Arduino.

• It can be used by students, artists, athletes, makers, and game & mobile developers who
want to easily incorporate live heart- rate data into their projects.

• The sensor clips onto a fingertip or earlobe and plugs right into Arduino.

• It also includes an open-source monitoring app that graphs your pulse in real time.

2.2.3. GSM Module:

• It is a hardware device that uses GSM mobile telephone technology to provide a data link
to a remote network.

• This GSM modem can accept any GSM network operator SIM card and act just like a
mobile phone with its own unique phone number.

• GSM Modem can be used to develop embedded applications like SMS control, data
transfer, remote control and logging.

• In our project, the GSM is used to send the alert messages to nurses, doctors, etc.,

2.2.4. LED Indication:(Light Emitting Diode)

• It is used as indicating, warning, accidental signals and other signals of circuits in the
areas of electric power.

2.2.5. Flow stopper module:

• Flow meters can be used to measure quantity of water passing through liquid pipes. .

• Flow meters have special circuits with actuators through which we can control the water
flow.

• Major constraints of flow meters are accuracy, precision and resolution.

• With out accuracy, precision and greater resolution flow meters are of no use.

• Flow meters works on the principle of hall effect.

• Based on the statistical data of the saline bottle level count , if there is no response from
doctors then the flow stopper sensor is used.
 • If the saline bottle level is below the limit mark then the sensor will stop the flow of
saline.

2.3. Feasibility study

A feasibility study is a study usually done by engineers that establishes whether conditions are
right to implement a particular project. Feasibility studies can be done for many purposes, and
are sometimes done in IT in order to look at feasibility for new hardware and software setups
sometimes a feasibility study is done as part of a systems development lifecycle, in order to drive
precision for the implementation of technologies. Engineers might look at a five-point model
called TELOS this includes the following components:

 Technical
 Operational
 Behavioural
 Process model used
 Hardware requirements and Software requirements
 System requirement specification

2.3.1. Technical feasibility

 It requires less training for the people for the usage of our system.
 It is user friendly.
 The concept of graphical and pictorial representation makes it more interactive.

2.3.2. Operational feasibility

 Output of the project can be used by android and ios user and it will be more communal

2.3.3. Behavioural feasibility

 It performs the intended functionalities and operations.

2.4. Process model used

The methodology used to implement our product follows a waterfall model for software
processes. The waterfall model is a sequential (non-iterative) design process, used in software
development processes, in which progress is seen as flowing steadily downwards (like a
waterfall) through the phases of conception, initiation, analysis, design, construction, testing,
production/implementation and maintenance.

2.5. Hardware requirements and Software requirements

Software requirements:

• Arduino UNO platform using embedded C.

• Windows 10, window 8.1 update, or windows 8 or windows 7.

Hardware requirements:

• Arduino board

• Flow stopper Sensor

• Water Level Indicator

• Pulse sensor

• GSM Module

2.6. Software requirement specification

 An SRS is basically an organization and understanding of a client and system

requirements and dependencies at a particular point in time.
 The SRS document itself states in precise and explicit language those functions and
capabilities a software system must provide, as well as states any required constraints by
which the system must abide.
 DESIGN PHASE

3.1. Design concepts

The set of fundamental software design concepts are as follows:

A .Abstraction

 Environment at the highest level abstraction

 The lower level of abstraction provides a more detail description of the solution
 A sequence of instruction that contain a specific and limited function refers in a
procedural abstraction

b. Architecture

 The complete structure of the software is known as software architecture

 Structure provides conceptual integrity for a system
 The architecture is the structure of program modules
 The aim of the software design is to obtain an architectural framework of a system

c. Patterns

 A design pattern describes a design structure that solves a particular design problem in a
specified context.

d. Modularity

 A software is separately divided into name and addressable components, they are called
as modules which makes design easy.
 Modularity is the single attribute of a software that permits a program to be managed
easily.

e. Information hiding

 Modules must be specified and designed so that the information like algorithm and data
presented in a module is not accessible for other modules which do not require that
information.
f. Functional independence

 The functional independence is the concept of separation and related to the concept of
modularity, abstraction and information hiding
 The functional independence is accessed using two criteria ie, Cohesion and coupling

g. Cohesion

 Cohesion is an extension of the information hiding concept

 A cohesive module performs a single task and it requires a small interaction with the
other components in other parts of the program

h. Coupling

 Coupling is an indication of interconnection between modules in a structure of software

Design concepts for our project:

 Modularity: Our application is divided into 5 modules alert message module, flow
stopper module, level detection module, pulse detection module, LED indication.

 Cohesion: The sensors will performs some task and it requires a small interaction with
the other components in other parts of the product

3.2. Design constraints

These are limitations on a design, these include imposed limitations that you don’t control and
limitations that are self-imposed as a way to improve a design The following are common types
of design constraint

9 Types of Design Constraint

 Commercial Constraints :Basic commercial constraints such as time and budget

 Requirements :Functional requirements such as specifications of features for a website
  Non-Functional Requirements :Requirements that specify intangible elements of a design
For example ,a non-functional requirement that a building be accessible
 Compliance: Compliance to applicable laws, regulations and standards
 Sensory Design: Beyond visual design, constraints may apply to taste, touch, sound and
smell For example, a brand identity that calls for products to smell fruity
 Usability :Usability principles, frameworks and standards For example, the principle of
least astonishment
 Style: A style guide or multiple style guides related to an organization, brand, product,
service, environment or project For example, a product development team may follow a
style guide for a brand family that constrains the colors and layout of package designs
 Principles :The design principles of an organization, team or individual For example, a
designer who uses form follows function to constrain designs
 Integration: A design that needs to work with other things such as products, services
,systems, processes, controls, partners and information

Design constraints for our project

Design constraints for our project:

 Commercial constraint: Maximum time to develop this system is 4 months and the
budget is medium

 Non-functional requirements: Non-functional requirements such as reliability,

performance, speed and accuracy

 Integration constraint: Based on the information gathered we present the statistical data
by grouping all the sensor results in a specific economic line.

3.3. Conceptual design

Conceptual design is the very first phase of design, in which drawings or solid models are the
dominant tools and products. The conceptual design phase provides a description of the proposed
system in terms of a set of integrated ideas and concepts about what it should do, how it should
behave, and what it should look like, which will be understandable by users in the manner
intended. Visualizing your product is an important aspect of verifying the complete design intent.
The primary outputs are the conceptual design(s), design specifications, project schedule, cost
estimate, design review, and required Proposal Report Competitive products are additional
sources of information for conceptual design.

Conceptual Design Diagrams

1.Use Case Diagram: A use case illustrates a unit of functionality provided by the system.The
main purpose of the use-case diagram is to help development teams visualize the functional
requirements of a system, including the relationship of "actors" (human beings)to essential
processes, as well as the relationships among different use cases

• Hospital staff has access to the database where the details of patients will reside.

• Other subscribers means guardians who are concerned with patient will also get
messages.

• Patient is associated with saline bottle, portable readymade wearable sensors and stopper
to stop fluid flow.
 3.3.1 : Use Case Diagram
 LED indication module indicates pulse readings inorder to allow saline flow in the body.

2. Class Diagram: The class diagram shows how the different entities relate to each other; in
other words, it shows the static structures of the system. A class diagram can be used to display
logical classes, which are typically the kinds of things the business people in an organization talk
about -- rock bands, CDs, radio play; or loans, home mortgages, car loans, and interest rates.
Class diagrams can also be used to show implementation classes, which are the things that
programmers typically deal with.

3.3.2 : Class Diagram

• The system has mainly 5 classes patient class, Smart bottle class, alert messaging class,
Subscriber class, flow stopper class.

• Patient class has attributes patient name, guardian phone number

• Smart bottle class has attributes saline level, sensor levels and different methods to
perform some tasks like collecting sensor results, messaging and startandstop fluid flow.

• Alert messaging module has attributes of subscribers details

3. Sequence diagram: Sequence diagrams show a detailed flow for a specific use case or even
just part of a specific use case. They are almost self- explanatory, they show the calls between
the different objects in their sequence and can show, at a detailed level, different calls to different
objects A sequence diagram has two dimensions: The vertical dimension shows the sequence of
messages/calls in the time order that they occur; the horizontal dimension shows the object
instances to which the messages are sent

3.3.3 : Sequence Diagram

• The above sequence diagram has different objects like patient , smart bottle, LED
indicator, alert messaging module and subscriber.

• After patient got connected to smart bottle, smart saline bottle collects sensor results and
based on those results it sends messages to alert messaging module to send alerts to
subscribers and stops fluid flow if needed.

4.Activity diagram: Activity diagrams show the procedural flow of control between two or more
class objects while processing an activity. Activity diagrams can be used to model higher-level
business process at the business unit level, or to model low-level internal class actions. In my
experience, activity diagrams are best used to model higher-level processes, such as how the
company is currently doing business, or how it would like to do business in future.
3.3.4 : Activity Diagram

• From the above activity diagram, the flow follows a patient get connected to the smart
bottle.

• Then portable cover of sensors integrated with smart bottle interprets results of sensors
of level and pulse. If pulse readings are not normal then, it should be indicated by using
LED indicator

• Alert message module send alerts to subscribers if needed and stops the fluid if needed.

5. Collaboration diagram: A communication diagram offers the same information as a sequence

diagram, but while a sequence diagram emphasizes the time and order of events, a
communication diagram emphasizes the messages exchanged between objects in an application
Sequence diagrams can fall short of offering the "big picture”. This is where communication
diagrams come in and offer that broader perspective within a process. You can draw your own
communication diagram using our free UML software. Communication diagrams offer benefits
similar to sequence diagrams, but they will offer a better understanding of how components
communicate and interact with each other rather than solely emphasizing the sequence of events
They can be a useful reference for businesses, organizations, and engineers who need to visualize
and understand the physical communications within a program.

3.3.5 Collaboration Diagram

 Rectangles represent objects that make up the application

 Lines between class instances represent the relationships between different parts of the
application
 Arrows represent the messages that are sent between objects
 Numbering lets you know in what order the messages are sent and how many messages
are required to finish a process

6. Component diagram: A component diagram provides a physical view of the system Its
purpose is to show the dependencies that the software has on the other software components (eg,
software libraries) in the system The diagram can be shown at a very high level, with just the
large-grain components, or it can be shown at the component package level Component diagram
is a special kind of diagram in UML The purpose is also different from all other diagrams
discussed so far It does not describe the functionality of the system but it describes the
components used to make those functionalities Thus from that point of view, component
diagrams are used to visualize the physical components in a system These components are
libraries, packages, files, etc Component diagrams can also be described as a static
implementation view of a system Static implementation represents the organization of the
components at a particular moment A single component diagram cannot represent the entire
system but a collection of diagrams is used to represent the whole

The purpose of the component diagram can be summarized as :

 Visualize the components of a system

 Construct executable by using forward and reverse engineering
 Describe the organization and relationships of the components

3.3.6 : Component Diagram

 Majorly, the entire design is divided into 5 components smart bottle, stopper, gsm
module, subscriber, LED indicator.
 Led indicator will represent the pulse level results.
 In smart bottle component, all sensors are integrated into this.
 Subscriber component specifies the details of persons to whom messages and alerts
should be sent.
 Alert messaging component sends messages to receiver.
7. Deployment diagram: The deployment diagram shows how a system will be physically
deployed in the hardware environment Its purpose is to show where the different components of
the system will physically run and how they will communicate with each other Since the diagram
models the physical runtime, a system's production staff will make considerable use of this
diagram The notation in a deployment diagram includes the notation elements used in a
component diagram, with a couple of additions, including the concept of a node A node
represents either a physical machine or a virtual machine node (eg, a mainframe node) To model
a node, simply draw a three-dimensional cube with the name of the node at the top of the cube
Use the naming convention used in sequence diagrams: [instance name]: [instance type] (eg :
Application Server")

3.3.7 : Deployment Diagram

• After collecting results from iot environment alert messaging i.e., messaging component
sends messages to mobiles of subscribers.

• Continuously, sensor should sense results from sensors of pulse, level sensor

3.4.Logical design
A logical design is a conceptual, abstract design. You do not deal with the physical
implementation details yet; you deal only with defining the types of information that you need.
The process of logical design involves arranging data into a series of logical relationships called
entities and attributes. An entity represents a chunk of information. In relational databases, an
entity often maps to a table. An attribute is a component of an entity and helps define the
uniqueness of the entity. In relational databases, an attribute maps to a column .You can create
the logical design using a pen and paper, or you can use a design tool such as Oracle Warehouse
Builder or Oracle Designer While entity relationship diagramming has traditionally been
associated with highly normalized models such as online transaction processing(OLTP)
applications, the techniques still useful in dimensional modelling.

Logical Design Diagrams

DFD: A data flow diagram (DFD) maps out the flow of information for any process or system. It
uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data
inputs, outputs, storage points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig
progressively deeper into how the data is handled. They can be used to analyze an existing
system or model a new one

a. Level-0 DFD:

a.Level-0 Data Flow Diagram

b. Level-1 DFD:

b.Level-1 Data Flow Diagram

c.Level-2DFD:

c.Level-2 Data Flow Diagram

 In the data flow diagram is as shown in the figure,the user will be able to access the
application, while the applications data will be stored into and retrieved from the database
 and all the data about user details as well as the business updation details will be
monitored by the administrator.

3.5. Architectural design

Requirements of the software should be transformed into an architecture that describes the
software's top-level structure and identifies its components This is accomplished through
architectural design (also called system design), which acts as a preliminary 'blueprint' from
which software can be developed IEEE defines architectural design as 'the process of defining a
collection of hardware and software components and their interfaces to establish the framework
for the development of a computer system' This framework is established by examining the
software requirements document and designing a model for providing implementation details
These details are used to specify the components of the system along with their inputs, outputs,
functions, and the interaction between them An architectural design performs the following
functions:

1. It defines an abstraction level at which the designers can specify the functional and
performance behaviour of the system

2. It acts as a guideline for enhancing the system (whenever required) by describing those
features of the system that can be modified easily without affecting the system integrity

3. It evaluates all top-level designs

4. It develops and documents top-level design for the external and internal interfaces

5. It develops preliminary versions of user documentation

6. It defines and documents preliminary test requirements and the schedule for software
integration

7. The sources of architectural design are listed below

8. Information regarding the application domain for the software to be developed

9. Using data-flow diagrams

10. Availability of architectural patterns and architectural styles

Architectural design is of crucial importance in software engineering during which the essential
requirements like reliability, cost, and performance are dealt with This task is cumbersome as the
software engineering paradigm is shifting from monolithic, stand-alone, built-from-scratch
systems to componentized, evolvable, standards-based, and product line-oriented systems Also, a
key challenge for designers is to know precisely how to proceed from requirements to
architectural design To avoid these problems, designers adopt strategies such as reusability,
componentization, platform-based, standards-based, and so on. Though the architectural design
is the responsibility of developers, some other people like user representatives, systems
engineers, hardware engineers, and operations personnel are also involved. All these
stakeholders must also be consulted while reviewing the architectural design in order to
minimize the risks and errors.

3.5.1 :Block Diagram/ Architectural Diagram

 Here in the above figure, the architectural view of the entire application is shown.
 We are developing the product called smart bottle for health care.
 All the screens are displayed according to the modules specified.
  Motor is connected to the saline bottle which is used to control the flow of saline and gsm
module is connected to the saline using a resistor inorder to send alert messages to
subscribers.
 Arduino uno is also connected via a resistor inorder to record sensor results to control
flow of saline when needed.
 Pulse sensor is also integrated to recording pulse results and they are indicated using LED
indicators

3.6. Algorithm design

An algorithm is a series of instructions, often referred to as a “process,” which is to be followed

when solving a particular problem While technically not restricted by definition, the word is
almost invariably associated with computers, since computer-processed algorithms can tackle
much larger problems than a human, much more quickly Since modern computing uses
algorithms much more frequently than at any other point in human history, a field has grown up
around their design, analysis, and refinement The field of algorithm design requires a strong
mathematical background, with computer science degrees being particularly sought-after
qualifications It offers a growing number of highly compensated career options, as the need for
more algorithms continues to increase

The steps involved in the application are as follows:

Step 1: Start

Step 2: Deploy the IOT environment to the Readymade portable sensors.

Step 3: Attach to the saline bottle

Step 4: Associate subscribers details with alert Messaging.

Step 5: Change the emptied bottle with filled one if it reaches certain limit of fluid.

Step 6: stops the fluid flow if change of bottle if not done at certain time or if normal pulse level
not detected.

Step 7: stop
3.7. Module design specification

Module design which is also called "low level design" has to consider the programming language
which shall be used for implementation This will determine the kind of interfaces you can use
and a number of other subjects Some crucial principles for a successful design are the following:

 Object Orientation: Object orientation is nowadays usually associated with certain design
methods like UML and programming languages like C++ or Java However, the principles
of object orientation were developed long before these methods and programming
languages were invented
 Encapsulation and Information Hiding: The principle of encapsulation goes hand in hand
with "information hiding" and is part of the idea of object orientation The principle is that
only the data which are part of the interface of an object are visible to the outside world
Preferably these data are only available via function calls, rather than being presented as
global variables.

We have divided our project into 5 modules. They are:

• Level detection module

• Pulse detection module

• LED indicator

• Alert message module

• Flow stopper module

3.7.1.Level detection module :

• This module is used to check the level of the saline bottle.

3.7.2 Pulse detection module:

 • This module is used to identify the patient’s pulse readings whether they are normal or
exceeded..

3.7.3 LED indicator:

• This is used to indicate the level of pulse using LED lights

3.7.4. Alert message module:

 When the level of saline bottle is below the limit mark, then GSM will send message to
doctor
 CODING
4.1 Sample code

Flow Stopper Module

Flow meters can be used to measure quantity of water passing through liquid
pipes. Flow meters have special circuits with actuators through which we can control the
water flow. Major constraints of flow meters are accuracy, precision and resolution.
Without accuracy, precision and greater resolution flow meters are of no use. Flow
meters works on the principle of Hall Effect.

Code:

void salineNflowsensors()
{
salinestate = digitalRead(salinepin);
if (salinestate == LOW)
{
digitalWrite(flowmotorpin, HIGH);
Serial.println("motor on saline flow
continues");
}
else
{
digitalWrite(flowmotorpin, LOW);
Serial.println("motor off siline low");
gsmsendmessage("Hello 1st person , Saline is
Over , Please Takecare" , phonenoone);

delay(10000);
 gsmsendmessage("Hello 2nd person ,Saline is
Over , Please Takecare" , phonenotwo);
delay(10000);
havesaline = false;
digitalWrite(flowmotorpin, LOW);}
}
GSM Module
The acronym GSM stands for Global System for Mobile Communications. This GSM modem
can accept any GSM network operator SIM card and act just like a mobile phone with its own
unique phone number. GSM Modem can be used to develop embedded applications like SMS
control, data transfer, remote control and logging. In our project, the GSM is used to send the
alert messages to nurses, doctors, etc.,

Code
void gsmsendmessage(String mymessage , String phno){
Serial.print("AT+CMGF=1\r");
delay(200);
Serial.println("AT + CMGS = \"+91"+phno+"\"");
delay(200);
Serial.println(mymessage);
delay(200);
Serial.println((char)26);
}
Pulse Detection Module
 Pulse Sensor is a well-designed plug-and-play heart-rate sensor for Arduino. It can be used by
students, artists, athletes, makers, and game & mobile developers who want to easily
incorporate live heart- rate data into their projects. The sensor clips onto a fingertip or earlobe
and plugs right into Arduino. It also includes an open-source monitoring app that graphs your
pulse in real time.

Code
void pulsesensor()
{
Pulsereadings = analogRead(Pulsepin);
Serial.println("reading........");
Serial.println(Pulsereadings);
if (Pulsereadings>450 && Pulsereadings<570)
{
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("no pulse found");
}
else
{
Serial.println("pulse found");
if(Pulsereadings>600 )
{
digitalWrite(led1,HIGH);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("led1");
}
else if(Pulsereadings>571 && Pulsereadings <599)
{
digitalWrite(led1,LOW);
digitalWrite(led2,HIGH);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("led2");
}
else if(Pulsereadings>350 && Pulsereadings <449)
 {
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,HIGH);
digitalWrite(led4,LOW);
Serial.println("led3");
}
else if(Pulsereadings <349)
{
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,HIGH);
Serial.println("led4");
}

Final Code:
const int salinepin = 9;
const int flowmotorpin = 8;
const int Pulsepin = A0;
int Pulsereadings = 0;

int led1 = 7;
int led2 = 6;
int led3 = 5;
int led4 = 4;

String phonenoone = "7981826414"; //10 digits

String phonenotwo = "8297937523"; //10 digits

int salinestate = 2;
bool havesaline = true;

void setup()
{
Serial.begin(9600);
pinMode(flowmotorpin, OUTPUT);
pinMode(salinepin, INPUT);
pinMode(led1, OUTPUT);
pinMode(led2, OUTPUT);
pinMode(led3, OUTPUT);
pinMode(led4, OUTPUT);

void loop()
{

if(havesaline)
{
salineNflowsensors();
}
pulsesensor();
}

void pulsesensor()
{
Pulsereadings = analogRead(Pulsepin);
Serial.println("reading........");
Serial.println(Pulsereadings);
if (Pulsereadings>450 && Pulsereadings<570)
{
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("no pulse found");
}
else
{

Serial.println("pulse found");

if(Pulsereadings>600 )
{
digitalWrite(led1,HIGH);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("led1");
}
else if(Pulsereadings>571 && Pulsereadings <599)
{
digitalWrite(led1,LOW);
digitalWrite(led2,HIGH);
digitalWrite(led3,LOW);
digitalWrite(led4,LOW);
Serial.println("led2");
}
else if(Pulsereadings>350 && Pulsereadings <449)
{
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,HIGH);
digitalWrite(led4,LOW);
Serial.println("led3");
}
else if(Pulsereadings <349)
{
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
digitalWrite(led3,LOW);
digitalWrite(led4,HIGH);
Serial.println("led4");
 }
}
}
void gsmsendmessage(String mymessage , String phno){
Serial.print("AT+CMGF=1\r");
delay(200);
Serial.println("AT + CMGS = \"+91"+phno+"\"");
delay(200);
Serial.println(mymessage);
delay(200);
Serial.println((char)26);
}

void salineNflowsensors()
{
salinestate = digitalRead(salinepin);
if (salinestate == LOW)
{
digitalWrite(flowmotorpin, HIGH);
Serial.println("motor on saline flow continues ");
}
else
{
digitalWrite(flowmotorpin, LOW);
Serial.println("motor off siline low");
gsmsendmessage("Hello 1st person , Saline is Over ,
Please Takecare" , phonenoone);

delay(10000);
gsmsendmessage("Hello 2nd person ,Saline is Over ,
Please Takecare" , phonenotwo);
delay(10000);
havesaline = false;
digitalWrite(flowmotorpin, LOW);

}
}
/*
void sendsms()
{
Serial.print("AT+CMGF=1\r");
delay(200);
Serial.println("AT + CMGS = \"+917989108434\"");
delay(200);
//Serial.println("Hii VIJAY");
delay(200);
Serial.println((char)26);
}*/
4.2. Output Screens:
1. When the saline level decreases, 1st nurse will receive message.
2. When the 1st nurse was not responded in time then, the
message is received by 2nd nurse.
3. When the patient pulse rate is below the normal condition,
and then LED1 blink.
4. As the patient pulse rate is below the normal condition, then
the nurse or guardian will receive message.
5. When the patient pulse rate is in normal
condition, and then LED2 blink.
6. When the patient pulse rate is above the
normal condition, and then LED3 blink.
.
7. As the patient pulse rate is above the normal
condition, then the nurse or guardian will receive
message.
4.3 SCREEN REPORTS:
1. When the saline level decreases, 1st nurse will receive message: As the limit of the saline
decreases then the information should be passed to nurses or guardians. Here when the saline
decreases initially then 1st nurse will receive message. If the 1st person is responded, then he or
she must come and remove the saline.

2. When the 1st nurse was not responded in time then, the message is received by 2nd nurse:
When the 1st nurse was not responded in particular time then the GSM will send message to the
2nd nurse statistically. If the 2nd person is responded, then he or she must come and remove the
saline.
Even if the 2nd person was not responded then it automatically stops the flow of the saline
through the flow sensor.

3. When the patient pulse rate is below the normal condition, and then LED1 blink:
Monitoring of pulse rate is very essential so, when the patient pulse rate is below the normal
condition then LED1 blink.

4. As the patient pulse rate is below the normal condition, then the nurse or guardian will
receive message:
When the patient pulse rate is below the normal condition then it’s better to inform to guardians
or nurses. So, at this condition the nurse or guardian will receive message. If the Nurse was
responded then he or she will come and check the health condition of patient.

5. When the patient pulse rate is in normal condition, and then LED2 blink :
When the patient pulse rate is in normal condition, then it just shows the better health
condition of patient. so, when LED2 blink then it indicates the patients health is in normal
condition.

6. When the patient pulse rate is above the normal condition, and then LED3 blink:
When the patient pulse rate is below the normal condition then this information must be passed
to guardians or nurses. So, at this condition the nurse or guardian will receive message. If the
Nurse was responded then he or she will come and check the health condition of patient.

7. As the patient pulse rate is above the normal condition, then the nurse or guardian will
receive message:
When the patient pulse rate is above the normal condition then it’s better to inform to guardians
or nurses. So, at this condition the nurse or guardian will receive message. If the Nurse was
responded then he or she will come and check the health condition of patient.