S15: Patient Buddy System (PBS)
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Patient Buddy System
Abstract
A system to enable the doctor or caregivers to remotely detect the physiologic measurements of multiple patients and receive alerts if patients’ conditions get critical or if the patient seeks emergency help. The system measures heartbeat, body temperature, position (sleeping or standing) and activity of the day (step count) continuously and sends an alert to the doctor automatically when the critical conditions are reached. The doctor or caregiver can monitor these measurements and alerts in their mobile app.
Objectives & Introduction
- Monitor physiologic measurements of the patients: heartbeat, temperature, movement and patient position
- Allows the doctor to monitor physiologic data for up to three patients.
- Send the physiologic data to the doctor upon request,
- Determine if the patient’s physiological conditions are critical.
- Automatically alert the doctor of the patient’s conditions if critical conditions are reached.
- Allow the doctor to send a text to the patient inform them about the next steps.
- Communication between the boards.
Team Members & Responsibilities
- Avinash Closepet Suresh
- Girish Bangalore Ramesh
- Thiruparan Balachandran
- Nimmi Bhatt
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 4/14/2015 | Order materials, ElectricImp exploration, Patient Position | Completed ordering materials |
| 2 | 4/21/2015 | Develop position details about the subject's orientation via the accelerometer, test different algorithm methods and store the data in Flash. | Completed getting the position details and developing a basic algorithm; Attempts to modify the algorithm are in progress. |
| 3 | 4/28/2015 | End to End Communication: Getting the data from the sensor and displaying it on the app's page. | Completed sending data via electric imp and reading it on the server on other side. |
| 4 | 5/05/2015 | Add other sensors to the system (temperature and heart rate) and work on doctor to patient communication and implement some emergency feature. | Completed integrating the heart rate sensor. The ADC collects the raw heart rate and runs the data through a heart rate algorithm. The algorithm will measure critical levels. |
| 5 | 5/12/2015 | Improve app and work on data analysis on the app's side to make the data look meaningful and interesting. | Completed heart rate algorithm and implemented DSP to get a cleaner heart rate. Completed processing accelerometer data to determine the footsteps and orientation. |
| 6 | 5/19/2015 | Improve and implement the android app and test the entire system from end to end. | Planned |
| 7 | 5/22/2015 | Demo! | Planned |
Parts List & Cost
- Pulse sensor = 24.95$
- ElectricImp(x2)= 29.95$
- Temperature Sensor = 5.95$
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation. File:PBS SystemOverview.PNG
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
- Pulse sensor: Sends analog data to the ADC
- Heart sensor: Uses I2C
- Temperature sensor: Uses I2C
- Flash: SPI used to save data to the flash memory
- IoT: Electric Imp used to send the data to the server
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
- Algorithms Implemented for Data Processing:
- Heart Rate Algorithm: Determine the bpm (beats per minute) by plotting pulse wave and taking the peaks. The signal was ran through a median filter and the peaks were smoothed out.
- Step count Algorithm: Determine the number of steps taken by the subject by plotting the magnitude of the accelerometer data (x,y and z) against time and taking the peaks.
- Orientation Algorithm: Determine the orientation of the subject.
- Determine the critical values: Based on literature research, have a certain set of predefined constants that determine if the patients reach the critical levels. If the patients reach the critical levels, the doctor automatically gets an alert message.
- Electric Imp: The electric imp sends data to the server.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
- Analyzing sensor data:
- Issue 1: We had difficulty interpreting data. When we first collected data, we noticed some numbers change, but we didn't know how to make sense of the data. To fix this issue, we plotted the data in Matlab and ran it through some filters (such as LPF to remove noise from motion artifact) and then extracted the values from the processed data to see if they gave meaningful results. Once the data looked meaningful, we implemented those algorithms in C.
- Issue 2: IoT Device: We faced connectivity issues with using Electric Imp. The electric imp would not always work reliable on different Wifi locations.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
