|
|
|
|
|
by atria
3993 days ago
|
|
Disclaimer: I'm writing software for a company that offers FDA approved pace-makers, defibrillators, and implantable heart monitors. These comments are my own. No where on your site do you reference FDA approval and I see that you are not in the U.S., so take my comments with a grain of salt. Bio-metric authentication using cardiac wave forms? I'm not sure that is a good way to go, but it sure sounds good. What happens when the user takes medications that changes the waveform (ie., they start new blood pressure medicine or cardiac meds, or intermittently take those meds)? What if the user has PVCs when trying to authenticate? What about diabetics with high glucose levels? The only time I've seen a legitimate use for using ECG in a consumer/commercial application is detecting a pulse when a user is attempting validate a finger print. I worked with a guy who had to implement something for ATMs being shipped to Africa. They required the user to authenticate with a finger print scanner in order to withdraw money. It wasn't long before people were loosing their fingers. As far as monitoring for cardiac anomalies, they don't happen all the time. Your device only appears to work when you hands are touching it. It often takes days or weeks for them to occur, requiring continuous monitoring for days, weeks, and sometimes months. |
|
What we do offer is the possibility of more frequent ECG monitoring, beyond the 10 second ECG exam that most people do only once or twice per year. For example, driving is a stressful environment, where a major cardiac event is more likely to occur. In a car with our technology, we would be able to detect when that event happens, thus preventing a crash by automatically stopping the car, and calling emergency services.
Regarding signal variability due to medication and other pathologies, that's something we have to account for, with robust feature extraction methods that are invariant to these changes, or adapt to them.