Hi Fitbit team,*I apologize for the longer message, and thank you in advance for your considerations and time.*I'm a student doing my second last year of studies at the University of Ottawa. After several occurrences where my friend was hospitalized for her severe heart conditions, I realized that we had waited an average of *-* hours in the waiting room each time. It was one specific instance in the waiting room where her heart rate spiked instantaneously and there was no staff nearby to attend to her, that I had realized a gap in today’s hospital & clinic waiting room infrastructure. With this, I got together with a few friends and hacked together an application that collected specific data such as heart rate from a Fitbit, in order to help in integrating smart infrastructure in clinic and hospital waiting rooms. *The collection of this data, is averaged and is used in maintaining a running-average of an individual's heart rate as well as other variables. The purpose behind this, is we plan on integrating it into a system, where individuals are able to opt-in to wearing a Fitbit while waiting in an emergency room at a clinic or hospital. Each Fitbit would be linked to a patient, using a barcode on the Fitbit band that would link to their file, and then the data would then be sent to a dashboard where specific information that is pertinent to the specific triage nurse would be displayed. *The issue with pulling the data is that the fitbit API only allows for a specific number of pulls per minute (rate limit). With the idea of this system I would like to integrate being: to be able to access the heart rate alongside other variables of a patient, and update it on this dashboard as frequently as possible, frequent and limitless pulling of API data is critical. *After pulling the data, such as heart rate, and having it displayed on a dashboard at the triage nurse’s station, our system’s backend builds moving averages in order to be able to display alerts if there is any off data (compared to previous data) being pulled by the Fitbit, while on the patient. *Realizing the level of a difference the Fitbit alongside my program could make on the clinic-level and hospital-level, has made me relentlessly work on it for months. The project itself, has been of interest to several members at IBM (working with Watson) as well as doctors that are interested in having the system implemented in their clinics. *In order to be able to use fitbit for my project, I’m wondering if you guys are able to raise the api rate limit so that I can monitor data more frequently. I’d also would like to ask you guys if you’d allow my fitbit personal app access to more than just * account’s (developer’s account) intraday data. I’d like to authorize *-* bands*accounts additional for a small pilot but I’ll need to be able to access a couple of user’s intraday data using * api key*token. Otherwise, I’ll have to make a personal app for every band’s account, complicating my backend quite a bit.*I strongly believe a product like this would help in not only minimizing emergency room mishaps but also in bettering the overall quality of care hospitals and clinics are able to offer. Many of the deaths and injuries that occur in emergency waiting rooms in hospitals as well as waiting rooms in clinics are due to staff inattention. This can be directly cut-down via wearables, like Fitbit, integrated with a system to manage the data collected. * *Thank you for your time,*Suzana Vukovic
GetHuman1036131 did not yet indicate what Fitbit should do to make this right.
I have an issue with Fitbit too
How GetHuman1036131 fixed the problem
We are waiting for GetHuman1036131 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Find similar issues & fixes
Follow other customers in the midst of the same issue or find a prior solution.