PULSE OXIMETER, WEB APPLICATION, AND CLOUD DATABASE DESIGN FOR REAL-TIME REMOTE PATIENT MONITORING

• Main Author: Reyhan Soebroto, Andhika
• Format: Final Project
• Language: Indonesia
• Online Access: https://digilib.itb.ac.id/gdl/view/73882
• Institution: Institut Teknologi Bandung

According to WHO (2020), cardiovascular and respiratory diseases are the top two causes of death worldwide. Similar observations can be found in Indonesia, with the prevalence of heart disease increasing by 1% from 2013 to 2018, and the prevalence of chronic obstructive pulmonary disease reaching 9.2 million people in 2013. In managing patients with these two diseases in the ICU, healthcare professionals rely on monitoring the patients' physiological conditions as one of the fundamental processes. However, existing monitoring devices still have limitations, particularly in terms of remote monitoring capabilities. Therefore, the author developed a patient monitor to provide doctors with the ability to continuously monitor patients' vital signs remotely through a web application. In developing the product, the author created a biometric sensor in the form of a pulse oximeter to measure oxygen saturation, and developed a web application and cloud database as the foundation for remote monitoring capabilities. The pulse oximeter was implemented using the MAX30100 sensor. The sensor readings were processed by a microprocessor and displayed on a monitor device, as well as sent to the cloud database. The cloud database was implemented using InfluxDB Cloud, which received data from the patient monitor and provided access to the data for the web application. The web application was implemented using React as the main framework and JavaScript as the programming language. Overall, the thesis met the specified requirements, although some functionalities did not meet the desired targets or were not ideal. The pulse oximeter could not accurately read conditions when oxygen saturation was below 70%. Real-time data communication between the entire system could not be implemented, resulting in a latency of 52 seconds.