Skip to content

Instantly share code, notes, and snippets.

@mddub

mddub/medtronic-nightscout-uploading-options.md

Created November 6, 2015 00:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mddub/3b5ce8ea97a70be0fe58 to your computer and use it in GitHub Desktop.
Save mddub/3b5ce8ea97a70be0fe58 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
medtronic-nightscout-uploading-options.md

Options to upload data from a Medtronic pump to Nightscout

First pass; others, please correct or fill in gaps.

  • MiniMed Connect
    • Default behavior (using the Medtronic iOS app paired with a Connect)
      • Real-time: we can scrape the data the Connect sends to Medtronic's servers using minimed-connect-to-nightscout. It's not much -- just BG data, active insulin, reservoir, etc. See this sample
      • Historical: once a day, the Medtronic app asks the Connect to poll the pump for history, then uploads that into CareLink. SPECULATIVE: you could run mmcsv regularly to translate and upload that data to Nightscout. You'd have pump data alongside CGM data delayed by ~24 hours.
    • Custom behavior (using an open source iOS app paired with a Connect)
      • Real-time: SPECULATIVE: @bewest has captured a conversation between a Connect and a pump, suggesting it makes the same history requests as a CareLink stick. We could develop an app to impersonate the Medtronic iOS app and request that data more frequently.
  • CareLink stick + OpenAPS
    • Real-time
  • RileyLink + OpenAPS
    • Real-time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment