In this report, the author proposes a system to detect two heart diseases called tachycardia and bradycardia, which are caused by heart rate abnormalities. The signal information, which is processed by the microcontroller, is sent to the mobile phone. A created app sends an alert to patients' emergency contacts when tachycardia or bradycardia conditions have been detected by the sensor.
I would like to express my appreciation and gratitude to the FYP I and II coordinators of the Department of Electrical and Electronics for their assistance throughout the period of completion of my graduation project. The body condition of each individual is one of the determinants of heart rate. Tachycardia and bradycardia are conditions in which a person's heart rate is higher and lower than the normal heart rate, respectively.
This can lead to a lack of enough oxygen to the organs and heart and to serious illnesses such as cardiac arrest and stroke. A person's heart rate is detected when a person's blood volume is in sync with the heart rate.
Problem Statement
Problem identification
Objectives
Scope of study
Feasibility of the project
The prototype building of this project will be started by the end of the first semester. The first six weeks of the Final Year Design Project II (FYP II) will be dedicated to complete the development of mobile apps, whereas the next six weeks are planned to conduct the experiment to evaluate the effectiveness of the designed prototype.
LITERATURE REVIEW
Limitation of the existing system
The collected data should be sent to the doctors to analyze the data and diagnose the problem. The existing system requires action from the patient to call the relatives, which the patients sometimes cannot.
Bluetooth Protocol
The synchronous and asynchronous of a Bluetooth device will be part of the transport protocol. Audio in the protocol function will take care of the host controller interface (HCI) transport. The fluff of the air interface within the Bluetooth devices will be configured by the link manager.
In addition, the lower and upper layers of the transport protocol will be connected with the Logical Link Control and Adaptation Protocol (L2CAP). When pairing for Bluetooth devices, the baseband acts as a Bluetooth connection controller. The Bluetooth air interface connection will be used to work on the previous and different application in the Middleware protocol.
From the host, the user would control the input and output data using the Human Interface Device (HID) protocol function. Bluetooth device setup will be done using the RFComm Telephony Control Protocol (TCP), a serial port emulation protocol that allows more than one protocol and. Applications that use Bluetooth connectivity, such as printers, headsets, dial-up and fax, will fall into this group of applications.
METHODOLOGY
- Project work
- Gant chart of FYP l
- Gantt chart for FYP ll Submission of Interim
- Tools required Hardware
- System Design
A real-time assessment concept for elderly people who remain at home during the state of tachycardia and bradycardia, unable to communicate with their relatives, and unable to communicate their condition to their relatives. Based on the communication design concept as shown in Figure 8, the user FIGURE 3.2 System flow of the project. The data is transferred via Bluetooth as the sensor worn by the user and the mobile phone worn by him are close, so Bluetooth is the best option.
The application is programmed using android studio and java eclipse to receive data from the heart rate monitor every 1 second. When the data is transferred to the device in real time, the user's heart rate data is displayed in the smartphone accordingly. Besides that, it is programmed to perform intelligent sampling whereby it will trigger the user about tachycardia and bradycardia condition and also send an alert to the user's relatives.
RESULTS AND DISCUSSION
System design
The Bluebee Bluetooth module as used in this project to search and connect to the device. A socket with Bluebee is created by the app as soon as the Bluebee tries to connect to the application. The pulse data is then sent to the mobile phone once the device is connected to the microcontroller.
The connection manager in the phone will be responsible for sending the command to the microcontroller. The initialization to receive message and send command will be handled by the connection manager. When the 'send' command is sent, the size of the command will be notified to the Arduino by the connection manager.
Once Arduino receives the size, the serial communication will be used to send the command to the Arduino. This data will then be managed by the connection manager based on the size of the message as well as the correct message. In the phone, a mobile application was developed to receive the incoming pulse data and analyze it with the threshold set.
With the analysis, the mobile application was able to identify whether the user was experiencing Tachycardia or Bradycardia. If so, then the app will automatically send and alert the user's family members with this, the delay in getting doctors advice and treatment for heart beat abnormalities can be avoided. This section focuses on the system specifications used as part of the project to achieve the objective.
From the Table 4.1, the heart rate monitor device can detect the heart rate ranging from 0 BPM to 200 BPM. The nominal heart rate of a person over the age of 15 when they are at rest is from 60 BPM to 100 BPM. The heart rate data from the heart rate sensor is transmitted via Bluetooth to the Android phone at a range of 2.4 GHz to 2.835 GHz.
Minimum Typical Maximum Unit
Bluebee Bluetooth module
This will allow the microcontroller to record a PPG signal that will be used to detect the individual's heart rate per minute. Simple coding will be done to transfer the data to the computer as bluebee download testing. Once this Bluebee verification is complete, it will be implemented into the Arduino and Pulse sensor circuitry.
The data sent from the heart rate sensor will be received by the mobile application and an alert will be sent to the user's emergency contact if tachycardia or bradycardia conditions are detected. Data received from the microcontroller will be displayed in the app as shown in Figure 4.5. It will then analyze and notify the user's relatives if there are abnormalities in the heart rate.
The transfer of pulse rate data from the microcontroller to the application begins when the user wears the pulse sensor, as shown in Figure 4.7. Figure 4.8 shows the flowchart of the Bluetooth connection from the microcontroller circuit to the mobile application. When the heart rate monitor is paired with the smartphone, the app will show the Bluetooth connection status whether it is connected or not.
The packet data from the heart rate monitor is received by the smartphone. This section discusses the route of data transmission from the heart rate monitor to the smartphone application, which is H-Das. A hexadecimal value has been assigned to the pulse data to be monitored.
When you get the string data from the device, it is stringed into a text field that will be displayed on the application screen. The text brings up the heart rate data, which will display the number of heartbeats per minute. When any of these conditions are detected, a warning SMS will be sent to the user's emergency contact.
Data Validation
Power Consumption
CONCLUSION AND RECOMMENDATION
Conclusion
Future Recommendation
Cyber Physical System Approach for Heart Attack Detection and Control Using Wireless Monitoring and Actuation System. Proceedings of 2015 IEEE 9th International Conference on Intelligent Systems and Control (ISCO), Coimbatore, 9-10 Jan 2015, pp 1-6. Proceedings 2010, 32nd Annual International Conference of the IEEE Engineering in Medicine and Biology, Argentina, 31 August – 4 September 2010.
Live Demo: A Mobile ECG Healthcare Platform,” Proceedings of the 2012 IEEE Biomedical Circuits and Systems (BioCAS) Conference, 2012, p. Proceedings of the IEEE Engineering in Medicine and Biology Society Annual International Conference, San Diego, CA, 28 August–September 2012, p.
![FIGURE 2.4 Design of Middleware [18]](https://thumb-ap.123doks.com/thumbv2/azpdforg/10259841.0/22.892.188.826.221.591/figure-2-4-design-of-middleware-18.webp)
