HMSystem Anand Joshi - Anand Dipakkumar Joshi 's
HMSystem Anand Joshi - Anand Dipakkumar Joshi 's
HMSystem Anand Joshi - Anand Dipakkumar Joshi 's
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>HMSystem</strong><br />
<strong>Anand</strong> <strong>Joshi</strong><br />
Idea<br />
<strong>HMSystem</strong> is abbreviation of Health Monitoring System. <strong>HMSystem</strong> is a web and mobile based<br />
system that consists of body sensors such as SPO2, mounted on the patient<strong>'s</strong> body to record<br />
their health activities in regular intervals and display it to the medical personnel via the<br />
website. So the health professionals can keep a regular eye on the patient<strong>'s</strong> health. Also, when<br />
the health of the patient goes critical it then alarm system so that necessary precautions<br />
measures can be taken timely by the doctors. For example, at the very critical stage of patient<strong>'s</strong><br />
health, it can automatically generate the call to the ambulance. Also this system implements<br />
the concept of health prediction. This concept predicts the health of person in near future by<br />
taking into consideration the past health data as well as the present data. These data are<br />
projected on the graph showing Time Vs Health. The linear curve is marked which helps the<br />
doctors to estimate the level.<br />
This complete project is divided into several modules:<br />
1. Hardware Interfacing Module<br />
2. Communication Module<br />
3. Data Storage and Management Module<br />
4. Emergency Handling Module<br />
5. Health Prediction Module<br />
Hardware Interfacing Module<br />
The sensors – SPO2, Blood Pressure, etc sensors are attached to the patients or the aged<br />
persons. These sensors take readings and send the output to low power wireless modules say<br />
eg SunSpots. These sensors give the reading to the base station which is either a laptop or a<br />
mobile device. The data are recorded on the SDCard situated on the base station. This approach<br />
helps to maintain the client version of the data. This data is encrypted with the RSA so that only<br />
the patient’s doctor can decrypt and receive the information. Also the data is compressed to<br />
reduce the size, helps to store more data in less space and also it helps to reduce network<br />
traffic when transmitting the data to doctor’s machine.<br />
Fig: SPO2 Sensor
Fig: Blood Pressure Sensor<br />
Fig: SunSpot Sensors<br />
Body Sensors Take Reading<br />
Send Data to Transmitting<br />
Sensors<br />
Data is saved on SDCard<br />
after processing on base<br />
Station<br />
Low Power Transmitting<br />
Sensors transmit data to<br />
Receiving Sensors on Base<br />
Station<br />
•Either PC, PDA or a mobile device<br />
Data ready for transmittion<br />
to Communication Module<br />
Fig: Process flow in Hardware Interfacing Module
Communication Module<br />
Tracking Server Database<br />
Tracking Server<br />
Doctor’s Server<br />
Doctor’s Server Database<br />
Patient’s Base Point<br />
Doctor’s Machine<br />
The Communication module has a bit complicated structure. The figure above shows the basic<br />
connections between the different components of this module. We describe the connections as<br />
under:<br />
1. The Patient’s Base point can be any instrument connected to wireless internet<br />
connection. The Patient’s Base point is a machine or a smart phone or a simple base
station. Here the sensors are interfaced directly or indirectly to the Patient’s Base Point.<br />
The Patient’s Base Point has the dynamic ip address and hence in order to establish the<br />
communication with doctor’s machine, it needs to establish the connection with it.<br />
2. Doctor is usually having the static ip address to which patient can connect. (Dynamic ip<br />
are also possible but for first approach we took the simpler case)<br />
3. To get the ip address of the doctor’s machine, it contacts the Tracking server by making<br />
proper authentications. Once it logs inside the system, it gets the doctor’s connection<br />
information.<br />
4. This forms the client – server architecture between the tracking machine and patient’s<br />
base point. Now once the patient’s base point receives the details, it forms peer-peer<br />
connection with the doctor’s machine for the transfer of the medical data.<br />
5. These transfers are of two kinds. For the first case patient’s module regularly transmit<br />
information (daily if condition is normal and hourly if condition is critical). Second case is<br />
when doctor wants to pull the data from the patient’s machine. For this case, he can’t<br />
contact the Patient’s module directly because patient carries a dynamic ip address. So to<br />
solve that Doctor’s server sets the call bit in tracking server which is captured by the<br />
Patient’s module and when it receives that bit, it transmits the data to the Doctor’s<br />
server.<br />
Data Storage and Management Module<br />
The Data Storage and Management module works on<br />
1. Patient’s Base Point: The patient’s module is constantly receiving the data and is stored<br />
on the SDcard. This is for the patient backup information. This data is encrypted by the<br />
Private Key of the patient and then encrypted by the Public Key of the doctor. This<br />
facility ensures proper protection of data and then the data is compressed to store on<br />
the SDCard. This data is sent by the patient’s module on the periodic basis.<br />
2. Doctor’s Server: The periodic and on demand data coming from the patient’s end are<br />
temporary stored and policies are employed on that to retrieve the most effective<br />
reading and only that particular reading is stored. From daily large number of readings<br />
only one reading is sampled out which effectively represents all data. Like that there are<br />
daily, monthly and yearly data store. The older data of two years back is converted to<br />
reports and mailed or sent back to the patient.<br />
3. Tracking Server: Tracking servers main purpose is to keep track of the Doctor’s server<br />
and thus help to form the communication link between the patient and doctor. The<br />
tracking server maintains the databases that have information of doctor’s ip address<br />
and it has patients associated to a given doctor. It also stores the access bit information<br />
that helps the patient module to know whether the doctor needs the data on demand<br />
or not.
Emergency Handling Module<br />
The Patient’s base module received data continuously. If this data is crossing certain thresholds<br />
limits than it alerts the emergency services both at doctor end and automated calls to<br />
ambulance and emergency services are done.<br />
Health Prediction Module<br />
The Health Prediction Module uses the concepts of machine learning and data mining to make<br />
predictions that what can be the health of the patient in near future considering the past<br />
records. Here the doctor’s server has the software that computes the supposed future value of<br />
the medical reading while considering the past trends of the health. If the future predicted<br />
value turns to be greater than the threshold value, than the doctors are alerted well in advance<br />
and the doctors can take necessary precautions to prevent the health going in such critical<br />
conditions in near future.