Looked into the R package called RHRV (http://rhrv.r-forge.r-project.org/index.html)
Decided to use Python for the task.

Feed Back For EKG Team

Real World

This is really an interesting problem that I feel has some amazing and under realized implications. Obviously heart health is a huge concern in the US but access to affordable health-care is a consistent problem especially in areas that are either poor or rural (worst case both). The goal of making EKG technology more ubiquitous will allow for proactive medicine which has an amazing impact of both quality of life but also cost savings (i.e. a win-win).

Considering the fact that this technology has the potential for wide impact the "target" group is quite wide, ranging from doctors interested in working with hard to reach populations to individuals interested in maintaining their health.

With this in mind, depending on your goal (i.e. developing a consumer product vs. a health-care product), I feel it would be good to consider what aspects you can tweak in order to achieve the maximum desired outcome.

An example being:

You are trying to make a consumer product. It would be good to focus on how to get the user "hooked" on the product to ensure that the data is as complete as possible, therefor having the best chance for preventative medicine. There is obviously a huge drop off in usage once the initial "OH COOL!" factor has worn off, so thinking about ways to keep the user engaged will be important (maybe gamification, maybe dataviz is really important, etc.)

Data

Frankly I think you have a better idea than I do what kind of related data is important so I'm not going to touch that. The biggest thing I would think about is security around the BLE you plan to implement. Obviously health-care data is highly sensitive so privacy and security really should not be an after thought.

Approach

I think it is great that you are building an iOS application, this helps with the security problem I was identifying (as opposed to sending it to the phone, then up to the cloud, around in the cloud, etc.). The one caution I would say is to take a look around and see what people have developed for dataviz in iOS. Building from scratch is great for learning if you have time but you can also waste a lot of time building something that already exists (or is close enough for you to take and then modify). Really it boils down to your intent, are you trying to learn everything about iOS development or are you trying to 'just get it done'. (And for the record I think both are totally fair)

Project Management

I think you have a realistic plan for the end of class, in terms of have a working prototype and it also helps that you want to work on this even after the class concludes. I think the working iOS application is a reach, but it would be awesome if you got it done!!

Hey guys I'm just testing this out.

From what I remember, the time interval is off in between samples. This makes it seem like the heart is beating much faster (tachycardic) than it actually is.

1. I'll speak to Javier about this.

2. I also bought an AliveCor Mobile ECG Case (http://store.alivecor.com/products/3rd-generation-alivecor-heart-monitor-with-case-for-iphone-6) so we can compare the data from our EKG with theirs.