Good point, and even if this data is only used by the consumer, when home health devices start measuring things like blood pressure & glucose levels, they begin to cross that line where there must be treated as medical devices. A diabetic may make decisions that have medical consequences based on such a reading. It's unrealistic to believe that such data would not influence the user's behavior just because the device is called a "home health device" rather than an FDA-approved medical device.
I think it is still going to take a little time for them to figure out what wearables are going to be utilized. Fitness is an easy market. These are people who are already measuring easily measurable things (like heartrate, calories, steps, etc). Fitness people are also passionate about what they are doing and have created a decent market (look at nike!).
Give them some time, they'll expand beyond simple bio metrics.
I'm not sure health and fitness tracking is a very big and broad market...I don't care how many steps I take, what my heart rate is or calories consumed...but if anyone could create a cool consumer wearable service it would seem to be Apple...so where are they?
Actually, when I first read articles that detailed Apple's meetings with FDA, I remember I was really happy about it.
It's because I know almost all the m-Health device vendors are avoiding to seek FDA approval (because it takes too long) and opt for labeling their product "home health care device" rather than "medical device."
As I said, I totally understand why they need to do that. But if any m-Health devices eventually need to talk to a doctor's office (by sending the collected data) and the doctor accepting it (without doubting its accuracy), m-Health device needs to be approved by FDA.
Otherwise, where does the data you collect on your little portable device is going to go? Will that be ever useful to anyone? Well, it's good for your own satisfaction, but seriously, will it ever become useful?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.