62
INTEROPERABILI TY

Healthcare Interoperability

Embed Size (px)

Citation preview

Page 1: Healthcare Interoperability

INTEROPERABILITY

Page 2: Healthcare Interoperability

ABOUT ME Jarod Ferguson CEO of Royal Jay, Chief Architect of Kno2

15 employees 80% of revenue is Health Technology Kno2, Aprima EHR, IHDE, St Luke's Health Partners

Technical Career path 3x Microsoft Data Platform MVP, AspInsider

Page 3: Healthcare Interoperability

“The extent to which systems and devices can exchange data, and interpret that shared data. For two systems to be interoperable, they must be able to exchange data and subsequently present that data such that it can be understood by a user.” - HIMSS

What is interoperability?

Page 4: Healthcare Interoperability

“What if you had a cell phone plan that only allowed you to call other customers of your carrier? That’s the situation for most healthcare providers today, when they join a data sharing network.” – Sequoia Project

What is Interoperability?

Page 5: Healthcare Interoperability
Page 6: Healthcare Interoperability
Page 7: Healthcare Interoperability
Page 8: Healthcare Interoperability
Page 9: Healthcare Interoperability
Page 10: Healthcare Interoperability
Page 11: Healthcare Interoperability

How many mg do I take?

When was that surgery?

Page 12: Healthcare Interoperability
Page 13: Healthcare Interoperability
Page 14: Healthcare Interoperability
Page 15: Healthcare Interoperability
Page 16: Healthcare Interoperability

HOW DID WE GET HERE?

THE PAST

Page 17: Healthcare Interoperability
Page 18: Healthcare Interoperability
Page 19: Healthcare Interoperability
Page 20: Healthcare Interoperability
Page 21: Healthcare Interoperability
Page 22: Healthcare Interoperability
Page 23: Healthcare Interoperability

Why is patient data sharing so complicated?

Page 24: Healthcare Interoperability
Page 25: Healthcare Interoperability

Mary Smith, TX ???

Page 26: Healthcare Interoperability
Page 27: Healthcare Interoperability
Page 28: Healthcare Interoperability

But data sharing isn’t new? Why is healthcare so far

behind?

Let’s take a look…

Page 29: Healthcare Interoperability
Page 30: Healthcare Interoperability
Page 31: Healthcare Interoperability

ASTM

American Society for Testing and Materials

Formed in 1898 First Standard on steel rails issued Henry Ford Emerging standard during WWII

Page 32: Healthcare Interoperability

COMMITTEE F04

Formed in 1962 Global Agenda for Medical Device Medical and surgical instruments,

orthopedic devices, implant systems MRI to Manufacturing

Page 33: Healthcare Interoperability

HL7 Formed in 1979 Reached maturity 1992 Defines the “What”

Page 34: Healthcare Interoperability

I think you missed a pipe on line 4…

Page 35: Healthcare Interoperability
Page 36: Healthcare Interoperability

IHE Formed in 1998 “improve the way computer systems

share information” Defines the “How”

Page 37: Healthcare Interoperability

[XDR] Cross-Enterprise Document Reliable Interchange[XDS-SD] Cross-Enterprise Sharing of Scanned Documents [MPQ] Multi-Patient Queries [PAM] Patient Administration Management[PIX] Patient Identifier Cross-Referencing (PIX)

IHE Profiles

Page 38: Healthcare Interoperability

HL7 V3 2005 Based on XML and Object Oriented Principles Far more rich and flexible

RIM 1.0 (first non-draft) – Jan 2001 ANSI/HL7 RIM Release 1 – Approved July 2003 ISO 21731 (RIM Release 1) - Approved 2006

Page 39: Healthcare Interoperability
Page 40: Healthcare Interoperability
Page 41: Healthcare Interoperability

IHE CCD =

HL7 RIM CDA + ASTM CCR

Page 42: Healthcare Interoperability

Connecting with the right format is not enough

Page 43: Healthcare Interoperability

We can help!

Page 44: Healthcare Interoperability
Page 45: Healthcare Interoperability

DIRECT TRUST 2010 A “Network” of HISP’s (no more peer to peer) Provides addressing similar to email Establishes security standards Uses IHE XDR as the protocol Can transport many document types (CCD, CDA, DICOM, PDF) Based on web technologies (HTTP, DNS) Private non-profit ultimately governed by HITPC & NwHIN

Page 46: Healthcare Interoperability

Sending……

Page 47: Healthcare Interoperability

WHERE ARE WE GOING?

THE FUTURE

Page 48: Healthcare Interoperability

I don’t see any patients?

Page 49: Healthcare Interoperability

THE SEQUOIA PROJECT 2012 Non-profit “advance the implementation of secure, interoperable

nationwide health information exchange” Teamed with Care Connectivity Consortium ONC transitioned management of eHealth Exchange for

maintenance to Sequoia Supports Carequality initiative

Page 50: Healthcare Interoperability

COMMONWELL ALLIANCE❮ 2013❮ Interoperability group❮ Cerner, McKesson, Athena, Allscripts❮ Epic NOT a member❮ IHE XCA or FHIR❮ Roles

❮ Enrollment❮ Record Locator❮ Patient Identification & Linking❮ Data Query & Retrieval

Page 51: Healthcare Interoperability
Page 52: Healthcare Interoperability

CAREQUALITY 2014 Common Framework “dedicated to accelerating progress

in health data exchange among networks, providers, payers, EHR and HIE vendors.”

EPIC, ORION, eClinicalWorks, Nextgen, Surescripts, Kno2 Record Locator Services, EHR Vendors Existing private/public networks and platforms Uses IHE profiles

Page 53: Healthcare Interoperability
Page 54: Healthcare Interoperability

CAREQUALITY Uses IHE Profiles Roles

Initiator Responder Record Locator Service

XCPD Flow

Page 55: Healthcare Interoperability

THE ARGONAUT PROJECT 2015 Private Sector Open internet standards Promotes FHIR to replace CCDA, FHIR APIs to replace

DIRECT “replace healthcare-specific document and messaging

standards with the more universal and essentially free equivalents taken from the Internet.” - John Halamka

Page 56: Healthcare Interoperability

ARGONAUT SPONSORS Accenture athenahealth Beth Israel Deaconess

Medical Center Cerner Epic Intermountain Healthcare Mayo Clinic

MEDITECH McKesson Partners HealthCare System SMART at the Boston Children’s

Hospital Computational Health Informatics Program

The Advisory Board Company Surescripts

Page 57: Healthcare Interoperability

FHIR Fast Healthcare Interoperability Resources Lightweight, no overhead Uses “Modern” web stacks. HTTP, REST Developers love it, integrates the same as other apps Pronounced “fire”

Page 58: Healthcare Interoperability
Page 59: Healthcare Interoperability
Page 60: Healthcare Interoperability

Just stay to the right….

Page 61: Healthcare Interoperability

INTEROPERABLE?Can your HIE receive an HL7 CDA via DIRECT IHE XDR over the Surescripts HISP?

Then, Yes.

Page 62: Healthcare Interoperability

THANK [email protected]@jarodf