Heart Savers Mid-Semester Demo Chris Hoffman Ryan Kellogg Mike Zizza February 28, 2007 http://www.ece.cmu.edu/~ece549/spring07/team5/ Project Concept Now – Doctor's office or hospital - short visit – Holter monitor - continuous home monitoring Asymptomatic – Don’t know when having a problem Later – Wearable ECG monitor that fits into daily life Using 3 electrodes instead of 12 – Detect arrhythmia (irregular, faster, or slower) – Patients of all types System architecture Status Update Accomplished – Acquired parts – Made parts talk – Set up development environment – Prototyping acquisition circuitry Risks mitigated – Moved toward accurate data acquisition – Worked out communication between Gumstix and Robostix through I2C Assumptions – Circuit will work – Communication with phone isn’t tough – Algorithms can be constructed to adequately process signal Eye Candy Demo Scenario Console Robostix Gumstix (Filtered) signal from body Data/communication over I2C Data/comunication over Bluetooth Next steps Complete acquisition/filtering circuitry (with optoisolation) Work out communication with phone Measure latency to determine time available for processing signal Do basic processing of signal – ex: heart rate detection More advanced processing – ex: arrhythmia detection Develop phone GUI Software architecture What we’ve learned Verify your hardware ships with power supply Opto-isolation required between electrode and circuit Making acquisition circuit trickier than originally thought Triple-check drivers work for all operating systems used Learned about Gumstix, Robostix, i2c, hardware virtualization, cross-compiling How to transfer files over serial Tentative Schedule Date Milestone March 5 •Finish circuit for 1 lead •Risk: Unexpected circuit behavior •Communication with phone works March 19 •Build/test complete 3-lead circuit •Acquire 3-lead signal and display on phone •Understand latency contraints April 2 •Perform basic decomposition of ECG signal April 16 •Implement simpler processing tasks (Heart rate detection) •Risk: Maybe not so simple April 30 •Implement advanced processing •Risk: Latency issues •Finished phone GUI and test system