2012 User's Conference SMART-Indivo Integration
Upcoming SlideShare
Loading in...5
×
 

2012 User's Conference SMART-Indivo Integration

on

  • 980 views

2012 Indivo X User's Conference talk on the deep SMART (www.smartplatforms.org) integration included in the Indivo version 2.0 release.

2012 Indivo X User's Conference talk on the deep SMART (www.smartplatforms.org) integration included in the Indivo version 2.0 release.

By Daniel Haas, Indivo X Lead Architect

Statistics

Views

Total Views
980
Views on SlideShare
632
Embed Views
348

Actions

Likes
0
Downloads
27
Comments
0

1 Embed 348

http://indivohealth.org 348

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The work we’ve done. Data models ‘require effort’, ‘bulk of the work’, in other containers
  • Held to a higher standard: blue sky: advantages for developers

2012 User's Conference SMART-Indivo Integration 2012 User's Conference SMART-Indivo Integration Presentation Transcript

  • Intelligent Health Lab Indivo and SMART:enabling standardized, substitutable, patient-facing apps Daniel Haas Harvard Medical School Children’s Hospital Informatics Program 18 June, 2012
  • Intelligent Health Lab What is SMART?“SMART provides a unified mechanism for diverse applications to interact with medical-record data.”
  • Intelligent Health Lab What is SMART? Apps APIContainers
  • Intelligent Health Lab What is SMART? Apps APIContainers
  • Intelligent Health Lab Isn’t that Indivo? Apps APIContainers
  • Intelligent Health Lab Nope.Unlike SMART, Indivo (pre-v2.0) supported:• A different API• Different data-models• A different authentication scheme• Patient-facing apps only• Extra functionality: Sharing Writing Data Auditing Etc.
  • Intelligent Health Lab But they are similar…• Reading Medical Data:  Problems, Meds, Lab results, Vital Signs, etc.• Authentication:OAuth-inspired• Philosophy: substitutability
  • Intelligent Health Lab So let’s take advantage of that! Apps Indivo App API Indivo-specific data models/APIsContainers
  • Intelligent Health Lab Goals• Enable existing (and future) SMART apps to run against Indivo• Shift Indivo apps towards adopting SMART standards• Enable hybrid SMART/Indivo apps that offer additional functionality when run against Indivo
  • Intelligent Health Lab Architecture: Before Indivo API Clinician- Clinician- Facing Admin Indivo- Facing API Apps Specific Apps Other Apps Sharing API Indivo Data Models Data Write APIClinician- Indivo Clinician- Facing Pure Facing Data Read Apps API Indivo SMART Apps Core Data Apps Models
  • Intelligent Health Lab Architecture: After Indivo API Clinician- Clinician- Facing Admin Indivo- Facing API Apps Specific Apps Other Apps Sharing API Indivo Data Models Data Write APIClinician- Indivo Clinician- Facing Pure Facing SMART API Apps SMART SMART Apps Data Apps Models
  • Intelligent Health Lab Technical ImplicationsSMART Containers supply Apps with UI integration Authenticated API Access DataData models are critical to enable app developersKeeping developer experience in mindData need to be predictable, (relatively) simple
  • Intelligent Health Lab Technical Implications: Data• Data Fidelity in Indivo• Coding Systems• Non-SMART data  What happened to ‘pluggable document processing?’
  • Intelligent Health Lab Technical Implications: SMART app Developers• Your apps will now run on Indivo!• If your apps are patient-facing (or might be appropriate for patient eyes), you can add Indivo-specific calls to write data, share data, and more.• Good coding practice: make sure to fail gracefully if Indivo calls aren’t available
  • Intelligent Health Lab Technical Implications: Indivo app Developers• Start learning SMART! APIs data models• Code your data  Data in Indivo must be consistent with SMART standards• When you build new Indivo apps, they will run on other SMART containers But only if you fail gracefully when Indivo-specific APIs aren’t available (Hint: Can you tell that I think this is important?)
  • Intelligent Health Lab Future Directions: The SMART-Indivo Portal• Mapping data from local EHR formats to other ontologies requires effort.  Goal: If you’ve done it for any SMART container, you shouldn’t have to do it for Indivo as well.• Obtaining data has been a primary obstacle for personal health platforms  Goal: If you have a SMART container exposing good medical data, Indivo should be able to run apps against that data.• For instance: 60+ academic medical centers with i2b2 could all provide Indivo, running apps, simply by setting up the SMART-Indivo Portal.
  • Intelligent Health Lab Future Directions: The SMART-Indivo Portal Indivo API SMART APIClinician SMART- Clinician Clinician Indivo Clinician -Facing Clinician Indivo -Facing Patient- -Facing SMART Connector -Facing Apps -Facing Apps Facing Apps Container App Apps Apps Apps Local EHR
  • Intelligent Health Lab Summary • By deeply integrating Indivo with SMART technologies, we have enabled Indivo to:  consume apps written for other SMART platforms  adhere to SMART standards for data models and data quality  support hybrid apps that add patient-facing components which are not yet ratified as part of the SMART model Apps Indivo App API Indivo-specific data models/APIsContainers