What you propose is complex but doable. For the pacemaker simulator, note that you should not try to control the pacemaker (too complex and too much liability) but should treat it as a "read only" source of information. (Though it's not entirely clear why you need a connection to the pacemaker at all.) Most modern units have an ability to communicate with an outside sensor (to read out "incidents", etc), though likely this ability is turned off most of the time to conserve battery life -- a significant issue.
The EMR sensor is something that you'd have to buy or invent. I'm no expert with EMR and don't know how complex such a device might be. It could be that developing a compact unit that is sensitive in the right bands (and won't be upset by ordinary cellphones and the like) will be difficult. And of course you have to connect the sensor to the phone somehow -- this has been done through the microphone input or through the removable "memory chip" interface in some cases. I don't know if there are any phones out there with more general I/O abilities. There's also the issue of battery life on the phone, since this would be a constant-running application. That could probably be easily fixed, though, with a "piggyback" battery. Finally, the sensitivity of pacemakers to EMR has been greatly reduced over the years, to where now it's not nearly the issue it was 20-30 years ago. So there's some question as to the market for your device. But it sounds like an idea worth pursuing a little further, at least. You'll learn a lot regardless of the outcome. On Jul 23, 9:34 pm, AAJ <sethuraman.ak...@gmail.com> wrote: > hey all, > We are graduate student, currently working on our masters project on > an android platform for a healthcare domain. Since there are not many > pacemaker reated applications on an android phone, we decided to work > on the same. Our project scenario is something like this- > > Pacemaker patients are not suppose to get exposed to EMR affected > areas. The pacemaker will immediately stop functioning if exposed to > EMR. So our application will be alerting the patients based on the > intensity of the EMR . So here, we will be using- > 1. A pacemaker simulator which will periodically check the heartbeat > and if the heart does not function properly, the pacemaker will > regulate it. > 2. The handset has an in-built sensor, which can sense the intensity > of the EMR. > 3. Also using Google maps we can pin the nearby locations which has > high intensity EMR. > > Now, some of the things that we have to do- > 1. Implement the pacemaker simulator, since we are not able to access > the source code for the already available ones. > 2. Implement the EMR sensor , to sense the EMR intensity. > 3. Alert the patient as soon as he/she enters the danger zone. > 4. Also show all the nearby EMR affected areas. > > Our questions are- > 1. Is the project feasible ?? As a masters project can we go ahead and > start working on this. > 2. How do we find out all the EMr affected areas nearby ? Which means > how do we connect Google maps API with the sensor program ?? > > It would be great if you could help us out with these questions. We > are really looking forward to working on an Android platform . > > Thanks > AAJ. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
