Tidepool Uploader

These notes were updated on Tuesday, December 30, 2014.

This is a Chrome App that acts as an uploader client for Tidepool. It is intended to allow you to plug devices into the USB port and automatically load the data stored on it up to the Tidepool cloud.

WARNING! THIS SOURCE CODE IS UNDER ACTIVE DEVELOPMENT AND IS KNOWN TO BE INCOMPLETE AND WITH ERRORS. IT IS ACTIVELY CHANGING. THIS CODE SHOULD NOT BE USED FOR COMMERCIAL MEDICAL SYSTEMS OR FOR ANY PURPOSE OTHER THAN ONGOING DEVELOPMENT AND IMPROVEMENT OF THIS CODE.

About:

A Chrome App

Has a manifest that asks for appropriate permissions on installation (perhaps someday the permissions request will be dynamic based on your devices)

Can talk to the Tidepool Platform

You log in as an individual user
Will log you in to your account on the Tidepool platform.
If you can upload to other users' accounts, presents a dropdown so you can select which user you want to upload to.

Has code to manage various USB devices and data accounts

In production:
- Carelink account
- Dexcom G4 CGM
Under development:
- Asante Snap insulin pump
- Insulet Omnipod insulin pump
- Abbott Precision Xtra blood glucose meter
- OneTouch Mini blood glucose meter
Coming soon:
- Tandem t:slim

Can manage serial communications

Knows how to talk to serial devices using the Chrome serial API and has a useful amount of intelligence about how to communicate in packets and the like. It turns out that serial protocols from several manufacturers are relatively similar if you squint a bit.
Has some utilities for building and disassembling byte-oriented packets of data and calculating CRCs.
Has some functionality to walk serial ports and try to find devices, but this is a Certified Hard Problem and for now, at least, this code has been disabled.

Can handle selection and upload of a data file from a block mode device

This code is not in production
It can detect insertion of a block mode device, but you must press "Choose File" to bring up the file selection dialog (this is a security measure imposed by Chrome).
So far, the Insulet OmniPod is the only block mode device supported.

Is starting to know how to talk to a Dexcom G4

It has the ability to get firmware data, manufacturing data, and to query pages of EGV data
It can interpret that data well enough to post it to Tidepool as CGM records
Has a collection of tools for managing Dexcom communications
Has not been completely validated

Has code to talk to an Asante SNAP pump

We hope that this now works reliably if there is no other serial device using the same cable. We still need to resolve that issue.

Can read a data file from an Insulet Omnipod pump

This is to a first-order approximation (it doesn't do everything yet, but it handles scheduled basals, boluses, settings, and smbg readings).

Has a start at downloading a data file from CareLink and uploading it to Tidepool

This is work in progress (based on server-side work we've already done). More soon.

How to set it up

Clone this repository.
Run npm install
Set the config for the environment you want to target (see Config section below)
Run npm start (will bundle files, and watch for changes)
Open Chrome. Go to chrome://extensions and turn on Developer mode (checkbox on the top line).
Click "Load Unpacked Extension".
Choose the directory you checked out above and click OK.
To run it, you can choose "Launch" from the chrome://extensions page. You can also run it from the Chrome App Launcher, which Chrome may install for you whether you want it or not.
If you're developing, you may find that the only way it runs properly is to hit "Reload" after each change to the source. You will definitely need to reload any time you change the manifest.

How to use it

Run the app
Log in
Plug your devices in

Dexcom

Press the "Upload" button; all the connected devices should upload in an arbitrary sequence.

Carelink

Enter username/password

Insulet

Plug in the device and start the app (in either order)
Log in
Press the "Choose File" button
Navigate to the device (which on the pump I have shows up as "NO NAME")
Select the most recent .ibf file on the device (there should be only one)
Press "Open"

Note that Blip doesn't like it much if you don't have at least 24 hours worth of data, although it will work with only CGM data.

Config

Configuration values (for example the URL of the Tidepool Platform) are set via environment variables. If you need to add a config value, modify the .config.js file. If you need to read a config value inside the app, use var config = require('./lib/config'). To set config values (do this before building the app), you can use Shell scripts that export environment variables, for example:

$ source config/local.sh
$ npm start

Mock mode

You can run the app in "mock mode": it will use fake data and fake HTTP & device APIs. This is handy for development when focusing on UI design, for example.

To run in mock mode use:

$ source config/mock.sh
$ npm start

The code for the fake APIs and data is located in the mock/ directory. It is only bundled when working in mock mode (see webpack.config.js). In other words, it is not included in the released version of the app.

Running in the browser

IMPORTANT: This only works in "mock mode".

For certain development tasks, like CSS or JavaScript that doesn't use any of the Chrome App APIs, it might be useful to run the app in the browser (refreshing the browser is slightly faster than reloading a Chrome App). You can do this with:

$ source config/mock.sh
$ npm run web

In a separate terminal start a server on http://localhost:8080 with:

$ npm run server

Publishing

Bump version number and tag with mversion minor -m (npm install -g mversion if you haven't already)
Build dist.zip file with npm run build MAKE SURE YOU'VE SOURCED THE CORRECT CONFIG BEFORE YOU RUN THE BUILD SCRIPT!!!

mgranberry/chrome-uploader