LIBERATING OUR DATAReducing the Burden of T1D through Access to Data and Interoperability

Howard Look, CEO

Diabetes Mind D-Data ExChangeNovember 20, 2014

Type 1 Diabetesis a highly burdensome disease

Reductionin Burden

Timenow

Time

Cure

now

Reductionin Burden

Time

Cure

Closed Loop

now

Reductionin Burden

Time

Cure

Closed Loop

Things we can do NOW

now

Reductionin Burden

Time

Cure

Closed Loop

Things we can do NOW

now

#WeAreNotWaiting

Reductionin Burden

So what can we do NOW?

Access to Data

Interoperability:Data

Devices

Increase choice.

Reduce the burden.

A thought experiment: Digital Cameras

Canon

Olympus

Kodak

JPEG

Access View

A thought experiment: Digital Cameras

Access View?!

Canon

Olympus

Kodak

Canon

Olympus

Kodak

Canon

Olympus

Kodak

Canon

Olympus

Kodak

A thought experiment: Digital Cameras

Your choice

Your choice

Access View

How do you access the data?

How do you view the data?

Your choice

Your choice

Access View

c X

No access to data meansYOU HAVE NO CHOICE.

Participants who upload their datamore than once per week:

Pump: 3%BGM: 2%CGM: 6%

Participants who NEVER upload data:

Pump: 60%BGM: 76%CGM: 52%

Source: T1D Exchange

No choice INCREASES the burden of managing type 1 diabetes.

No access to data meansYOU HAVE NO CHOICE.

T1D is my disease.And that is my data.

T1D is my disease.And that is my data.

And I should get to choose:

• What tools I want to use to see my data.

• Who else gets to see my data.• What other devices I want to

use to manage my T1D.

So what can you do NOW?

Release data access protocols for

EXISTING devices.

Expose RESTful APIs for cloud services.

Adopt standards like IEEE 11073.

Access to Data

Interoperability:Data

Devices

Access + Interoperability = Ecosystem

A Diabetes Application Ecosystem

T1D + Fitness Data Apps that make dosing easier

Research Appsand Interfaces

Apps for Remote Monitoring

Apps for Pregnant Moms with T1D

Apps for Teens

Apps for Clinical Decision Support

Apps for Kids

A Diabetes Application Ecosystem

App App

App App

App

App App

App

App

App

App

App

App

App

AppApp

Does the patient own their own health data?

Can patients donate and/or repurpose their data?

Does your cloud service have machine accessible (RESTful) APIs?

Does your device have available, documented protocols?

Do you support standards like IEEE 11073?

Are your data format/protocols complete and unambiguous?

Device Makers: Abbott Animas Asante Bayer

Dexcom Insulet

Lifescan Medtronic

Roche Tandem

Cloud Service Providers: Dexcom Diasend Glooko Livongo

Medtronic Telcare Tandem Tidepool

8 of 10 device makers: Yes!

8 of 8 diabetes cloud service providers: Yes!

Does the patient own their own health data?

Can patients donate and/or repurpose their data?

Old: “Any data submitted through [the service] shall be the property of [the service], and you hereby waive all right, title and interest to the submitted data.”

New: “As the submitter of Submitted Data you always have the right to, free of charge, access information regarding your Personal Data.”

Does your cloud service provide machine accessible APIs?

(e.g. REST APIs and Oauth)

3 providers: APIs under development, not yet released.

1 provider: REST API + Oauth in use!

2 providers: CSV download only.

6 of 10 device makers: Yes!

Does your device have available, documented protocols?

A Diabetes Application Ecosystem

App App

App App

App

App App

App

App

App

App

App

App

App

AppApp

Auto-immune attack on pancreas

Not a choice:

Burden of managing T1D

Access to data.Interoperability

of devices.

A choice:

REDUCE the burden of

managing T1D