Project

# Title Team Members TA Documents Sponsor
23 Device for remote health management of quarantined patients
Arnav Ahluwalia
Ishaan Datta
Rohit Kumar
William Zhang design_document1.pdf
design_document2.pdf
design_document3.pdf
final_paper1.pdf
presentation1.pdf
proposal1.pdf
Problem Statement

During the pandemic, monitoring the health of home quarantined patients at scale enables provision of timely medical support. Enabling medical authorities to remotely monitor the health of COVID-19 patients would lessen the load on hospitals and help divert medical resources well in time to people who need it the most. This is particularly relevant for places where the outbreak has progressed to an extent that not enough beds/medical facilities are available to cater to every patient and triaging is being carried out- i.e. medical personnel must tend to higher-risk/seriously ill patients. This is particularly true for developing countries (places where the medical infrastructure isn’t expansive enough to cover all patients).

Solution Overview
In this project we propose to build a low-cost remote health monitoring system that measures parameters like Heartbeat, Blood pressure, Blood pulse oximeter and ECG and makes the data available to medical personnel remotely. We propose to use the Atmega microcontroller, along with sensors and a WiFi module at the device end with a cloud-based platform for analysis of the data. Doctors could use a website to access and monitor the quarantined patient’s health.

Solution Components:

• Subsystem 1:
o Sensors for measuring patient health data: We propose to use Heartbeat, BP, Blood pulse oximeter and Temperature measurement sensors.
o Atmega Microcontroller for capturing health sensor inputs: The microcontroller would form the heart of the system that captures sensor data and does suitable protocol conversions as needed to send the data periodically to the backend application.

• Subsystem 2:
o Internet connectivity interface: We would use a WiFi interface module for providing internet connectivity to the device.

• Subsystem 3:
o We will implement an application with a cloud-based Backend which would carry out user provisioning (for patients as well as health professionals), storing, capturing and the display of patient data via a website- this application would essentially store the patient data, permit analytics on patient data and display it on a website for monitoring by a medical doctor. The platform should also have an email-based alerting mechanism that gets triggered by tunable health parameters obtained from the device, allowing it to indicate if/as soon as a patient needs medical attention.
o Self-service web portal on the cloud to register patients and link their personal details with the unique device ID present with them.
o Web portal on the cloud for authorized medical personnel to view patient data. The portal would have sufficient security controls – authenticated access and encrypted data storage to keep patient data secure.

• Security of data: We have two options for security of health data in transit - encryption and anonymization.
o Encryption modules do exist in the Atmega microcontroller. One option is to pre-provision the same public key in all devices and have the corresponding single private key securely stored in the cloud. On the device, the public key can be used for encrypting all outbound data.
o A simpler approach would be to anonymize the outbound data such that it does not contain any personal details (like names, addresses, phone number etc.). During device provisioning stage, the patient/ assistant would need to enter personal details on a provisioning (secure) website and link the device unique number with it (the unique number can be printed on the side of each device). Thereafter, all outbound data has just this number along with sensor metrics - no personal details would be sent. At the cloud end, the data would be stored encrypted once it is linked with personal details.

Criteria for success:

• Patient data captured by the device, streamed over the Internet to the cloud-based application and visible on a website to authorized personnel.
• Accurate monitoring of patient vitals and triggering of the alerting system based on predefined parameters.

Low Cost Distributed Battery Management System

Logan Rosenmayer, Daksh Saraf

Low Cost Distributed Battery Management System

Featured Project

Web Board Link: https://courses.engr.illinois.edu/ece445/pace/view-topic.asp?id=27207

Block Diagram: https://imgur.com/GIzjG8R

Members: Logan Rosenmayer (Rosenma2), Anthony Chemaly(chemaly2)

The goal of this project is to design a low cost BMS (Battery Management System) system that is flexible and modular. The BMS must ensure safe operation of lithium ion batteries by protecting the batteries from: Over temperature, overcharge, overdischarge, and overcurrent all at the cell level. Additionally, the should provide cell balancing to maintain overall pack capacity. Last a BMS should be track SOC(state of charge) and SOH (state of health) of the overall pack.

To meet these goals, we plan to integrate a MCU into each module that will handle measurements and report to the module below it. This allows for reconfiguration of battery’s, module replacements. Currently major companies that offer stackable BMSs don’t offer single cell modularity, require software adjustments and require sense wires to be ran back to the centralized IC. Our proposed solution will be able to remain in the same price range as other centralized solutions by utilizing mass produced general purpose microcontrollers and opto-isolators. This project carries a mix of hardware and software challenges. The software side will consist of communication protocol design, interrupt/sleep cycles, and power management. Hardware will consist of communication level shifting, MCU selection, battery voltage and current monitoring circuits, DC/DC converter all with low power draws and cost. (uAs and ~$2.50 without mounting)