On First Steps and Directions

[Ira Laefsky]

Hi everybody--I'm out of hospital and eager to build on our progress.   In particular we seem to agree that the initial use case should be a combination of the Quantified Self enthusiast who wishes to gather all of their health and fitness data in one place for analysis and sharing progress with other enthusiasts, in combination with the use case of a health or physiology researcher who seeks input from analog and digital appliances and self-built instruments (GSR, HRV (or pulse)) and to gather that data for subsequent analysis.  I think (do you all concur?) that we should start with a device which attaches to a few self-built analog instruments
such as GSR and at least one digital appliance like Fitbit or Neurosky.  A big open question on my part is how (and how generally) should we approach the input and translation of the data format of digital health and  fitness appliances should we just do enough data format translation to input a particular instrument data point coming in from USB or wireless port(s) or do we need (even initially a more general approach) which
can translate among several differing digital health appliance protocols? Should the input data from our initial digital input(s) and analog self-built instrument(s) be sent to the cloud via a ethernet or a wifi router?

I'm looking for a somewhat general approach to our first steps and prototyping which goes in the direction of hopes for the health/fitness/physiology data aggregator and Internet of Things appliance.

[MRE]

Hmmn my vote:
Keep it simple. A few home vuilt sensors and common log format which is easy to work with. PC/mobile device apps can then manipulate, visualize, further translate or upload.

If we then add commercial devices, it may onlt need to be a software translation solution (a plugin) on the host, or an arduino sketch.

[Charalampos Doukas]

Hi all,

Ira welcome back, I totally agree with keeping it simple, at least in the beginning. May I suggest we start a google sheet listing devices (like Fitbit, Zeo, etc.) and links to APIs if available, as well as open source libraries provided by the community?

Ch.

> --
> You received this message because you are subscribed to the Google Groups "Physiosense" group.
> To unsubscribe from this group, send email to physiosense...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Ira Laefsky]

An Important source of Open Source Drivers for Devices such as Fitbit, et is http://www.openyou.org/ 

[Ira Laefsky]

An Important source of Open Source Drivers for Devices such as Fitbit, et is http://www.openyou.org/

On Tue, Nov 13, 2012 at 6:18 AM, Charalampos Doukas <ch.d...@gmail.com> wrote: