The Nexus Effect - Managed Cloud Interfacing for Data Exchange

Presented by: Joseph Wortmann

Vice President of Operations at YourCareUniverse

DISCLAIMER: The views and opinions expressed in this presentation are those of the author and do not necessarily represent official policy or position of HIMSS.

The Problem with Direct Interfacing

A B

C

D

E

F

G

H

Interface Engine Solution to Direct Interfacing

Interface Engine

A B

C

D

E

F

G

H

Advantages of the Interface Engine Approach

• Creates an abstraction that simplifies

- 8 versus 20+ connections

• Substantially more maintainable and sustainable

• Places control of interfaces back in the hands of the hospital

Disadvantages of the Interface Engine Approach

• Potential single point of failure

• Interface engines can be expensive

• Interface engineers are expensive and relatively rare

• Abstraction is limited to facility or IDN scope

Why is Scope So Important?

• Healthcare interfacing world has changed

• Forced interaction between facilities and the state– Forced for Public Health Reporting by Meaningful Use U2

– Being forced by states for Medicaid reporting

• ACO model forces interaction between facilities

• Outreach Lab and Rad models forcing interaction between facilities

• Others being added constantly

Facility/IDN-Based Interface Engines Cannot Address the

New World Order

Why?

A B

C

D

E

F

G

H

Cloud-based Interface Engine

A B

C

D

E

F

G

H

Managed Cloud-Based Interface Engine

• Solves the New World Order problem through abstraction

• Must be:– Owned by an independent third-party

– Managed – creation, monitoring and maintenance

– Located in the cloud

– Fully secure

– Purchased operationally

Advantages of Managed Cloud-Based Interfacing

• All the advantages of facility/IDN-based interface engines without:

– Single point of failure

– Capital expense

– Personnel expense

• Not limited by scope

Thank You!