Hello 2016!

By David Haddad on January 8, 2016 - Sign up for free updates here

Happy new year everyone! I want to personally thank you for being so supportive this last year in making mobile health data more accessible. We’ve accomplished so much together in 2015 and we’re looking forward to what the new year brings.

But before we reflect on the last year, I want to call out a few important events in January that I think you might like:

  • I’ll be presenting at three Meetups in NYC next week on January 12, 13, and 14th.
  • Come say “hello” to our software engineer, Jasper, at UCSF’s Informatics & Digital Health Conference on January 14th. He’ll be at our booth.
  • If you haven’t already registered for our first training on how to integrate mobile health data, you should. We’re limiting the event to only 25 people, so get your ticket while tickets are available. It’s going to be an incredible experience if you want to build your integration chops.

Now that we’ve gotten that out of the way, let’s talk about 2015.

Data Science

We’ve been writing new schemas for provenance and GPS as part of our work with MD2K.org, hosted our first-ever Clinical Measure Group (CLIME) for medication prescriptions, serialized Apple’s HealthKit to our JSON schema with Granola, and published over 80+ schemas in our new library. This all helps to standardize digital health data so it can make sense in a clinical environment.

Open Source Platform

We’ve built some great tools to make the lives of developers easier so that they want to acquire, store, process and visualize mobile health data. Here are some of the highlights:

  1. Shimmer – a free and open alternative to many of the more proprietary data aggregators
  2. Granola – a healthful way to serialize Apple’s HealthKit data
  3. Pulse – away to map HL7 / EHR data into JSON schemas
  4. Visualization Library – for various measures like blood pressure, weight, heart and physical activity
  5. Storage – a place to store your Open mHealth formatted data that comes with a simple and clean RESTful API
  6. Data generator – a programmatic way to see how your application responds to mobile health data.

Anyone can take any one of the components from above and use it in isolation or as part of a comprehensive solution to make mobile health data more meaningful. We hear about people using these tools, but would love to hear more of your uses in the comments. Don’t be shy!

Community

We expanded our Meetups from NYC to San Francisco, Chicago and London and are now up to over 700 members. We also hosted our first ever Summit in San Francisco and are looking forward to this year’s summit as well. We also spoke at events like the QS Pain Symposium, VITL, White House PMI conference, Connected Health Symposium, Diabetes Mine, and way more!

Special Projects

We launched our marquee demo app, Linq, at Stanford’s Preventive Cardiology, released an iOS app that syncs your HealthKit data to Dropbox as JSON files, and are now embarking on making a ResearchKit analog for Android called ResearchStack.

Funding

We also just launched a services line to help organizations use mobile health data (as well as Open mHealth technology) and we continue to seek corporate sponsorship from organizations who care about building an open standard for mobile health data (shout out to Catalyze for believing in our mission).

What does 2016 look like?

This next year is about going to be focused on you–the community.

We will be using CLIMEs to strengthen our data science work. At the same time, we hope to build and engage the community through more blogging and Meetups, as well as feature improvements on the open source platform.

Stay tuned for more announcements and updates. It’s going to be a great year for mobile health.

If there’s something you think we should do this upcoming year, please feel free to leave a comment below.

Leave a Reply

Your email address will not be published. Required fields are marked *


five × = 35