I've been working on ways to describe smaller parts of some of my projects.
One project is to end the upload problem.
The basic idea is to create a small "adapter" kind of device that makes diabetes devices available for near-real-time, "cloud" management, similar to meraki.com, but for any and all diabetes devices.
I'd love to know if framing it this way as "ending the upload problem" makes sense to people, and what you think.
I heard a story recently of a teenager T1 who went out shopping with her friends. She set a lower temp rate to accomodate for the activity, but then the battery ran out while she out and about and very very busy. She took care of the battery, but the reboot canceled her temporary rates causing a low. With near-real-time "cloud" management, not only can you forget about manually uploading to your spreadsheets or doctor, but one could also eliminate this kind of problem by syncing rates across reboots.
One of the eventual goals is new schedulers, that present a mashup of Facebook + Google calendar, along with fitness data to manage diabetes, but step 0 is to get the diabetes data in the firs place. Use your calendar to schedule temporary rates for the gym... my gym schedule is already on my calendar for example; why not simply confirm and tell the pump to do the right thing?
End the pointless manual labor.
Estimated cost for something like this, DIY-style, is ~$140 for the equipment, then $5/mo for ongoing cell service from ting.com. Most parts can be ordered from amazon.com. A future version could be miniaturized with custom pouches for each device.
There are two ways to update glucosurfer.
One is to include an endpoint known the dataurl URI. https://github.com/bewest/insulaudit-ssh-tools/blob/master/perform_... The script will upload a tab separated file, one timestamp and glucose reading per line.
The second way is to use github's webhooks to notify your website when insulaudit updates your git phr. github will send your website a series of messages you can use to sniff out anything that may have changed in the user's "medical record."
I'm flexible on formats, eventually it would be wise to have a suite of plain text formats, csv tsv, etc, that translate nicely to Indivo RDF or similar. https://gist.github.com/bewest/4965993#comment-832679
http://medevice-users.github.io/diabetes/ - I've created a users group to discuss technical specifics for any medical device related to diabetes. It is not a support group, but rather a users group to advance the state of the art in diabetic technology, and a place to advocate for better access to our data.