meet your interoperability goals and realize your vision

Michelle Schneider Senior Solutions Engineer [email protected] LinkedIn: Michelle Schneider 978-805-4143

Interoperability - Realizing Your Vision

Agenda

•  3 Main Goals •  Interoperability Types &

Definitions

•  How to prepare

•  Questions & Answers

Interoperability

Interoperability describes 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

Interoperability

“The act of taking thousands of proprietary systems that were created as good ‘ol, stand-alone, I don’t need anyone, I am king of the hill, you can’t boss me around, attitude, and making them share information.”

~Michelle Schneider

Interoperability - Government Driven in Healthcare Three main goals of the U.S. Government: 1.  To improve health outcomes 2.  To improve health care quality 3.  To lower health care costs

Interoperability – Goals of the U.S. Gov’t

Goal #1: To improve health outcomes ü  Information more quickly ü  Accessible history ü  Clinical Decision Support ü  Decrease risk for errors

ü  Transcription ü  Missing information such as allergies ü  Shared problem list


Goal #2: To improve health care quality ü  Information more quickly ü  Accessible history ü  Clinical Decision Support ü  Decrease risk for errors



Goal #3: To lower health care costs ü  Information more quickly ü  Accessible history ü  Clinical Decision Support ü  Decrease risk for errors


Interoperability Advantages

•  More efficient •  Reuse data over and over •  Monitoring – all in one place •  Alerting – electronic from one place •  Shorter implementation time

•  Safer •  Decreased Cost •  Fewer ins/outs

HIMSS Defines Interoperability

Foundational

ü  Unidirectional ü  Receiving system is not required to interpret

the data

System A System B

Foundational Interoperability

Point-to-Point interfaces

ü  Lab orders to a reference lab worklist ü  Bedside device results to a .txt file ü  Discharge messages to a housekeeping app

System A System B

Foundational Interoperability

Point-to-Point interfaces

System A System B

“I am diabetic” ???


Structural

ü  Uniform movement of healthcare data ü  Defines the syntax of data exchange ü  Purpose and meaning preserved ü  Ensures interpretable at the data field level

System A System B


Structural

ü  Lab orders to a reference lab that creates the visit and order in the reference lab LIS

ü  Bedside device results to a critical care system to display in a flowsheet

ü  Discharge messages to a housekeeping system that updates bed status to dirty upon receipt

System A System B


Structural

System A System B

“I am diabetic” “Je suis diabetique”


Semantic

ü  Two or more disparate systems exchange information in a usable way

ü  Structured and codified for interpretation by downstream systems

ü  Supports electronic exchange of patient summary information ü Goal – Improve quality, safety, efficiency and efficacy of

healthcare delivery

System A System B

System C

Semantic Interoperability

System A System B

System C

engine


System A

System B

System C

engine

Order Entry

LAB

RAD

Bedside Devices

RX

DOC


System A System B

System C

lab rad

engine

MD


System A System B

System C

lab

MD

rad rad

engine

lab

MD


System A System B

System C

lab

MD

rad

rad

lab

rad

engine

lab

MD

MD

Interoperability

System A System B

System C

Engine

Interoperability

System A System B

System C

Engine

engine

Interoperability

System A System B

System C

Engine

engine

RAD MD LAB B/AR PHI QA

Are you prepared for Semantic Interoperability?

In the ONCs “Ten Year Interoperability Roadmap, 2015-2017”, it is all about putting the architecture in place to “Send, receive, find, and use a common clinical data set to improve health and health care quality”

Ten guiding principles and checkpoints

1.  Build upon the existing health IT infrastructure 2.  One size does not fit all 3.  Empower individuals 4.  Leverage the market 5.  Simplify 6.  Maintain modularity 7.  Consider the current environment and support multiple

levels of advancement 8.  Focus on value 9.  Protect privacy and security in all aspects of

interoperability 10. Scalability and universal access

Taken from: A shared nationwide interoperability roadmap

Interoperability

Taken from: A shared nationwide interoperability roadmap


A current inventory of facilities: •  What is in place now? •  Hospitals •  Clinics •  Rehab Facilities •  Laboratories •  Extended Care


A current inventory of technology: •  What is in place now? •  EMR •  Applications/Best of Breed/Stand Alone •  Interfaces •  Interface Engines


Community Connections: •  Physician Groups/ACO •  Network Members •  HIE •  Pop Health


What’s not automated? •  Paper •  Fax •  Reference Lab Results •  What are you scanning •  Manually importing/exporting anything?


Time for a visual


What can you keep? •  #1 guiding principle — “Build upon the existing

health IT infrastructure” •  Product/Application Upgrade •  Reimplementation •  Refinement •  Reeducation


•  Do you have any quick wins? •  Workflow review – Audit, adjust, implement

•  Label printer •  Barcode scanner •  Dictionary/Table management •  Interface

•  Relatively low cost, morale boosting, efficiency producing


•  What should be automated? •  Patient Safety – Scanning, EMPI •  Patient Outcomes (Turn-around-time, Decision

support, scheduling) •  Certification – CQM •  Attestation – Patient portal, TOC •  Efficiency – (Payroll, materials, archiving)

•  Can existing infrastructure be leveraged?


What should be replaced?

•  Uncertified •  Sunset •  Simply cannot meet needs long-term


•  Outline work to be done •  Action plan:

•  What can existing resources manage? •  Adding FTEs vs. Outsourcing •  Project Management •  Vendor Search •  Engine and Interfaces •  Implementation consultants •  Testing and Analyst

How can Iatric Systems help?

•  Engine Assessment – Free! •  EMPI Assessment – Free! •  Interface Engine implementation •  Interface Development •  Project Management •  Gap Analysis Solutions: •  Security Audit Manager •  Meaningful Use Dashboard •  Bedside barcode specimen collection •  Interface Engine/Physician office integration (POI)

I Can Help!

Michelle Schneider Senior Solutions Engineer

Iatric Systems, Inc.

Phone: (978) 805-4143 E-mail: [email protected]

Connect with me on LinkedIn: MichelleSchneider

Read our Blog and sign up for the topics that interest you: new.iatric.com/blog-home

Interoperability — Realize Your Vision Contact Us

Follow Us:

http://new.iatric.com/blog-home For more information:

Please contact your Iatric Systems Account Manager Send an email to [email protected]