Patient health monitoring is emerging as a prominent application of the

embedded sensor networks. Providing health facilities at a low cost has always
been a great challenge for health service provider in smarter ways of providing
healthcare to sufferers of age related diseases. In addition, emphasis has to be
paid on providing health monitoring in out-of-hospital conditions for elderly
people and patients who require regular supervision particularly in remote areas.
This dissertation presents a ubiquitous monitoring system for the continuous
monitoring of patients under their natural physiological states or elderly persons
with chronic diseases. Especially our system is designed for homecare or the
monitoring of the elderly who live in country side or small rest home without
enough support from caregivers or doctors, instead of patient monitoring in big
hospital environment.
2E-Health Sensor Platform V2.0 for Arduino and Raspberry Pi [Biometric / Medical
Applications]

E-health sensor platform v2.0 for arduino

The e-Health Sensor Shield V2.0 allows Arduino and Raspberry Pi users to perform
biometric and medical applications where body monitoring is needed by using 10 different
sensors: pulse, oxygen in blood (SPO2), airflow (breathing), body temperature,
electrocardiogram (ECG), glucometer, galvanic skin response (GSR - sweating), blood
pressure (sphygmomanometer), patient position (accelerometer) and muscle/eletromyography
sensor (EMG).
This information can be used to monitor in real time the state of a patient or to get sensitive
data in order to be subsequently analysed for medical diagnosis. Biometric information
gathered can be wirelessly sent using any of the 6 connectivity options available: Wi-Fi, 3G,
GPRS, Bluetooth, 802.15.4 and ZigBee depending on the application.

If real time image diagnosis is needed a camera can be attached to the 3G module in order to
send photos and videos of the patient to a medical diagnosis center.
Data can be sent to the Cloud in order to perform permanent storage or visualized in real time
by sending the data directly to a laptop or Smartphone. iPhone and Android applications have
been designed in order to easily see the patient's information.
Wi-Fi Module for Arduino and Raspberry Pi "Roving RN-XVee"

Wi-Fi module for arduino

Wireless E-health Monitoring at Remote Area System Model
In WEMARA system model have client side and server side.
Case 1. When patients are moving and in the range of wireless access point in that case
patient consider as a client side and PDA (computer/laptop) consider a server side. Here
client side collect the e-health data and send it to the server directly using its IP address and
port number throw access point wirelessly. Server side receive the data directly from the
client side throw access point using wirelessly and display the data in the computer display.

Architecture 1 for case 1

Case 2. When patient are moving and not in the range of wireless access point in that case we
consider patient as a server side and PDA (computer/laptop) as client side. Here server side
first connect with the access point which in the range of the server side. Server side collect
the patient e-health data and send it to local client which is in the range throw wirelessly.
Client side display the e-health data.
Architecture 2 for case 2

We develop WEMARA system client server using java TCP sockets API that supports
Transmission Control Protocol (TCP).

The server creates a ServerSocket object, specifying the port number it listens on.

The server invokes the accept () method on this object. This method makes the server

waiting until a request comes from a client.

The client creates a socket object, specifying the servers name/IP address and port

number to connect to.

The constructor of the socket class attempts to establish a connection to the server
socket having specified socket address (IP address and port number). If the connection
is established, it returns a socket object that represents the client end of the logical

connection created. The client uses this socket object to communicate with the server.
The accept() method on the ServerSocket object also returns a socket object that
represents server end of the channel that is connected to the clients socket. The server
uses this socket object to communicate with the client.

Clean Data Received At Server Side

3.6 Client Model

1. Setup () Set the baud rate 9600.

2. Loop () we enters in command mode
2.1 Sets DHCP and TCP protocol

set ip dhcp 1
set ip protocol 3
set wlan ssid AP name
set wlan channel 0

2.2 Configures the way to join the network Access point

set wlan join 1

join AP

2.3 Set the ip address of the server side

set i h IP address

2.4 set remote port no of the server

2.5 set local port number of the client
2.6 Connection open and attempts to establish a connection to the specified server and port
number
2.7 save
2.8 reboot

3.7 Server Model

Its a java handler using TCP
1. Create a serversocket object, specifying a port number.
2. Invokes the accept method on this object. This method makes the server waiting for
incoming connection request.

3. The accept method on the serversocket object also return a socket that represents the
server side end of the logical connection.
4. Get InputSrteam type object.
5. Read data using InputStream.

6. Algorithm for client side

7. Step 1: setup ()
8. Set baud rate of communication channel as 9600 so that the sender and receiver
becomes
9. Synchronized.
10. Step 2: loop ()
11. Step 2.1. Enter in command mode. There are two modes in the WiFly module, namely
data mode and command mode. In data mode, the module is ready to either accept
incoming connections or initiate outgoing connections. To configure the parameters
and/or to view the current configuration, the module must be put into command mode
(also called configuration mode). At any given time, the module will either be in
command mode or in data mode. Upon power up, the device will be in data mode. To
enter command mode, exactly the escape
12. Sequence (set to three characters, $$$ by default) must be sent. The device will
respond with CMD indicating it is in command mode.
13. Step 2.2. Set DHCP and TCP protocol.
14. Step 2.3. Set the IP protocol for TCP client only.
15. Step 2.4. Set the wlan ssid to associate with.
16. Step 2.5. Set the wlan channel. If 0 is set, then scan is performed, using the ssid, for
all the
17. Channels set in the channel mask.
18. Step 2.6. Configures the way to join the network AP.
19. Step 2.7. Set the host IP address, remote IP address and local IP address.
20. Step 2.8. TCP mode: sets the auto connect timer. This command causes the module
periodically connect to the stored remote host.
21. Step 2.9. Save the configurations in config file.
22. Step 2.10. Reboot so that the settings take effect
23. Step 2.11. Read the message from the sensor connected to the communication board
and send it to access point wirelessly.