open platforms for healthcare applications
DESCRIPTION
Today's Electronic Health Record (EHR) offerings inhibit the ability to develop the next generation of clinical applications for providers to provide the best possible care and patients to become more engaged. Such offerings are designed as monolithic silos of storage and end-user experience that use proprietary methods for accessing key functionality. While large health care providers typically have physical control over their data, they lack in having functional control. This barrier makes it virtually impossible for data to be easily accessed by other applications without very costly and time-consuming migration strategies. As a result, the pace of innovation is greatly stymied by closed systems that appear to be all-too-prevalent in the healthcare industry. This session presents a strategy of vendor-neutral, public, open Application Programming Interfaces (APIs) and advocates for their use in developing open platforms for healthcare applications.TRANSCRIPT
![Page 1: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/1.jpg)
HIMSS MN Presents:
Open Platforms for Healthcare Applications
Thursday, August 21, 2014
![Page 2: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/2.jpg)
Thank you to all our Annual Sponsors!
![Page 3: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/3.jpg)
Elite Level Sponsors
![Page 4: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/4.jpg)
Premiere Level Sponsors
![Page 5: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/5.jpg)
Partner Level Sponsors
Tanson Logo Here?
![Page 6: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/6.jpg)
Dates and topics TBDPlease take HIMSS MN survey to guide your chapter on topic selection!
Opportunity to win $100 Amazon gift card.
HIMSS MN 2014-2015 Event CalendarMonth FormatAugust 21st Webinar – Open Platforms for Healthcare ApplicationsSeptember WebinarOctober Expert PanelNovember Midwest Fall Technology Conference (Chicago)December WebinarJanuary Advocacy EventFebruary WebinarMarch Networking EventApril HIMSS National Chapter Reception (Chicago)May 14th Annual Spring ConferenceJune 3rd Annual Charity Golf TournamentJune Twin Cities Summer SocialJuly SE Minnesota Summer SocialAugust Webinar
![Page 7: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/7.jpg)
Today’s Speakers
Keith ToussaintExecutive Director
Collaborative DevelopmentMayo Clinic
Ken BobisAdministrator
Chief Technology OfficeMayo Clinic
![Page 8: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/8.jpg)
Open Platforms for Health Care Applications
An Open Interface Approach
Presented to HIMSS MNAugust 21, 2014Keith M. ToussaintKen G. Bobis, PhD
![Page 9: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/9.jpg)
Agenda
Definitions The problem Solution vision Business value An example Further research
![Page 10: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/10.jpg)
Definitions
Health Care Organization (HCO) EMR Application Interface / API / Messaging Standard Ecosystem Open Interface
![Page 11: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/11.jpg)
EMR Application
Application that is integral to the delivery of patient care, but not found in the institution’s core Electronic Medical Record
◦ Document Viewer, EMR Viewer, Pt. Itinerary, smartplatforms.org
![Page 12: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/12.jpg)
Interface / API / Messaging Standard Interface
◦ A point where two systems, subjects, organizations, etc., meet and interact Tape data transfer; interface engine
API◦ Application Program (API) or Web Services (WS) Interface
A callable program interface ValidatePatientNumber, ValidateDate
Messaging Standard◦ Rules by which an interface is maintained◦ An agreed upon message format
HL7, FHIR
![Page 13: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/13.jpg)
Ecosystem
(biological) A biological community of interacting organisms and their physical environment◦Rain Forest, Prairie, Coral Reef
(software) A set of businesses functioning as a unit and interacting with a shared market for software and services, together with relationships among them◦Wintel, iOS, Android, Java
![Page 14: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/14.jpg)
Biological Ecosystem
![Page 15: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/15.jpg)
Software Ecosystem
http://subprint.com/blog/it%27s-the-ecosystem,-stupid
![Page 16: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/16.jpg)
Open Source Software Ecosystem
![Page 17: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/17.jpg)
Open Interface
open (small ‘o’)◦May be used by others◦Control retained by the author◦Traditional view of “open”
Open (big ‘O’)◦Author-independent◦Emerging view of “Open”
Open Interface <> Open Source
![Page 18: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/18.jpg)
The Problem Practice functionality needs are huge
◦ More than a single provider organization can satisfy◦ Years to implement workflows in existing products◦ New capabilities removed from “The Gemba”
Closed architectures◦ No access to data sources and business logic
Product lock-in◦ Product B may be more conducive but … switching
costs are prohibitively high
![Page 19: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/19.jpg)
Current State
Data Storage and Computing Infrastructure
Core Clinical Informatics Functionality
User Interface
EH
R X
Monolith
Y
Viewer 1
Tool 1
Viewer 2
Tool 2
Legend:
Vendor provided, HCO Managed HCO provided and managed
![Page 20: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/20.jpg)
Solution Vision Embrace Open APIs
◦ Author-neutral interfaces ◦ Reduce product lock-in
Layered architecture◦ Separating application, platform and storage functionality
New Value Network◦ New problems require new solutions◦ New business models with new value network
participants Common infrastructure
◦ Available to all – but not required
![Page 21: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/21.jpg)
Future State
Data Storage and Computing Infrastructure
Core Clinical Informatics Functionality
User Interface
EH
R
PoC Tool 1
Vendor 1
LegendVendor provided and
managedHCO provided and managed
Vendor 2
HCO 1 Vendor 3
PoC Tool 2 PoC Tool 3
Open interfaces
Open interfaces
![Page 22: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/22.jpg)
Business Value
![Page 23: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/23.jpg)
Strategic value to HCOs
Leverage common core capabilities Minimize capital expenditures Enable rich collaboration Focus on differentiating technology Reduce vendor “lock-in”
![Page 24: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/24.jpg)
Financial value to HCOs
Common platform to meet MU Establish common application frameworks Improved Innovation on reporting and
analytics Cost savings through shared physical
infrastructure
![Page 25: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/25.jpg)
Operational value to HCOs
Enabling Pay-as-you-go tools Minimal up-front costs Same quality tools for all
![Page 26: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/26.jpg)
Value to Newcomers
Enable new value network of application innovation◦Shared core functionality◦New capabilities on existing ‘stack’◦Enabling consistent tools across the spectrum
of care Reduce innovation friction
![Page 27: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/27.jpg)
Existing Efforts
![Page 28: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/28.jpg)
Industry Examples
FHIR HealthKit CommonWell Alliance Smart Platforms.org Continua Health Alliance OpenEHR OpenMRS
![Page 29: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/29.jpg)
HL7 Fast Health Interoperability Resources Fast and easy to implement Implementation libraries Free for use Interoperability out-of-the-box Path from HL7 Version 2 and CDA Web standards compatible Support for ReSTful architectures Human-readable message formats
About FHIR
http://www.hl7.org/implement/standards/fhir/summary.html
![Page 30: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/30.jpg)
Is it big “O” open? Yes!◦ Non-proprietary standards◦ Enables local extension of the standard◦ Well-defined process for evolving the standard
What is missing?◦ Definition of layered architecture◦ Clear description of “separation of concerns”◦ Example of such an architecture:
A Robust Health Data Infrastructure prepared by JASON for ONC: http://healthit.gov/sites/default/files/ptp13-700hhs_white.pdf
FHIR considered
![Page 31: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/31.jpg)
JASON interoperability architecture
Data Storage and Computing Infrastructure
Core Clinical Informatics Functionality
User Interface
![Page 32: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/32.jpg)
Previous Forays from Tech
Microsoft HealthVault Google Health Optum Health Cloud
![Page 33: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/33.jpg)
Further Research
Cloud-based deployment architectureCatalog of required of servicesFlesh out business valueOperational policies & procedures for
member HCOsProtocols for EMR & Ecosystem
interactionsCommon local & public architecture
requirements
![Page 34: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/34.jpg)
Wrap up / Summary
Current State is sub-optimal Loosely-coupled architecture Open APIs
◦Understanding the difference between small ‘o’ and big ‘O’
Now possible to make a shift Can be driven by providers Opinions invited on how to proceed
![Page 35: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/35.jpg)
Today’s Speakers
Keith ToussaintExecutive Director
Collaborative DevelopmentMayo Clinic
Ken BobisAdministrator
Chief Technology OfficeMayo Clinic
![Page 36: Open Platforms for Healthcare Applications](https://reader034.vdocuments.us/reader034/viewer/2022042815/55842354d8b42a785e8b467a/html5/thumbnails/36.jpg)
Open Platforms for Health Care Applications
An Open Interface Approach
Presented to HIMSS MNAugust 21, 2014Keith M. ToussaintKen G. Bobis ,PhD