E N D
1. SMArtSubstitutable Medical Apps Reusable Technologies SHARP Area 3
2. Or:Creating the App Store for Health SHARP Area 3
4. March 1, 2009
6. Use case 1 Med-tastic is a well-funded NewCo which has developed an elegant medication list application that has physician and consumer facing functionality
To work, Med-tastic needs
Prescribing history
Dispensed medication history
Allergies
Problem list diagnoses
7. Use case 2
8. Domestic Abuse
9. Use case 2 (cont) The application would require
Comprehensive diagnostic data from primary site of care for each patient (to work well)
Comprehensive diagnostic data from all sites of care (to work very well)
10. MedTastic may be able to develop apps adapted to several APIs (Cerner’s Mpages etc)
Academic group cannot.
THEREFORE, focus is on an API that enables a single apps store for
Cerner Install
Hospital with homegrown system
Physician practice
Open source EMR
11. “We cannot overstate how important PHRs are to the efficient functioning of a low-cost, high quality health-care system . . . . We think that the INDIVO system, or something like it is a good place to start.”
--Clayton Christensen
Harvard Business School
13. Ecosystem
14. EHR as an “iPhone-like” Platform There is a common application programming interface that enables
Software developers to build SUSTITUTABLE applications
Push innovation to the edges
Nimbly evolve functionality
Avoid vendor lock
Shrink switching costs
Enable disruption
15. Create Disruption in the EMR Space Two key elements of our approach
Demonstrate substitutability as a core concept in building HIT
Capacitate third party innovation
16. Executive Committee Zak Kohane
PI, CoDirector
Ken Mandl
CoDirector, Chair Exec Committee
Rachel Ramoni
Executive Director
Ben Adida
CHIP, SMArt lead architect, Indivo
Elmer Bernstam
UT, I2B2
Shannon Manzi
Pharmacist
Mike McCoy
Regenstreif, Careweb, Networked data
Shawn Murphy
Partners, I2B2
Griffin Weber
HMS IT, I2B2
21. SMArt APIs based on REST*Representational State Transfer (REST) The fundamental API for the Web
Each resource (object) has a unique ID (URI). For example:
https://inpc/patients/1234567/meds/active (pt’s active med list)
Four fundamental operators can be applied:
GET - return a representation of the referenced resource
POST - Create the resource
PUT - Update a resource
DELETE - Remove a resource
HTTP enables content negotiation, e.g. HTML, XML, RSS/Atom
Powerful semantics that leverages web scalability and performance
22. 3 Open Source Systems to build on I2b2 Analytic Platform (NLM Funded)
Indivo PCHR Platform (NLM and CDC Funded)
CareWeb EMR
23. Indivo
24. I2B2
25. CareWeb: An EMR viewer into INPCWeb-based, modular UI Components
26. TimeLine August 2010: Present Prototypes to early adopters
December 2010: Release SMArt API specs
April 2011: Apps developed