Hub Implementation - Amazon S3

[Pages:24]Hub Implementation

April 4, 2019

?Copyright 2019 The eHealth Exchange. All rights reserved. Confidential.

You Asked, We Listened

Roadmap

Enhance Architecture

Expand Reach

Streamline

Prepare

Expand Breadth

Notify

Qualified Health Information Network (QHIN) Analysis

Refer

Hub Platform

Carequality

FHIR Directory

PULSE

Purpose of

Integration

Use

Record Locator

Direct Messaging

Future: ? FHIR

Resources ? Patient

Matching

Future: ? PDMP ? Images

Future: ? Push vs

Pull

Future

2

?Copyright 2019 eHealth Exchange. All rights reserved

What's changing?

Current State

Multiple Connections Per Participant

Dignity (20+)

DoD (60+)

SSA (150+)

Michiana (6)

Tiger Institute

(3)

VA (200+)

3

?Copyright 2019 The eHealth Exchange. All rights reserved. Confidential.

Future State

1 Connection Per Participant

Dignity

Expands Reach Lowers Cost Introduces New Capabilities

DoD

SSA

Hub

Michiana

VA

Why Are We Doing This?

One Connection to eHealth Exchange Participants

Participant

Participant

Participant

1 Connection

Participant

1 connection vs 270+

Hub

1 Connection

Participant

1 Connection

Participant

4

2019 ? eHealth Exchange. All rights reserved.

Participant

Participant

Why Are We Doing This?

One Connection to All Carequality Networks

NetSmart

NextGen

AthenaNet

1 Connection

Participant

1 interface vs 300+

Hub

122 Connections

Epic Care Everywhere

1 Connection

Commonwell eCw

5

2019 ? eHealth Exchange. All rights reserved.

Surescripts

Who Selected The Hub?

? Formal Request for Proposal (RFP) process

? Evaluation Workgroup scored vendor responses

? Unanimously recommend Intersystems' HealthShare

Evaluation Workgroup:

? Advent Health ? California HIE Association ? Childrens Dallas ? CRISP ? DaVita ? Common Spirit ? DoD ? Kaiser ? Humana ? OCHIN ? Superior Health Plan ? SSA ? VHA ? Walgreens

6

?Copyright 2019 The eHealth Exchange. All rights reserved. Confidential.

What Will the Hub Do?

Initiator (Your organization)

Direct your queries to the Hub's Endpoint URLs listed

in the new Hub-aware directory instead of using the Responder's endpoints

Hub

Hub Aware Directory

using the Responder's Home Community ID. (No change)

Responder (eg General Hospital)

Sub-organizations are differentiated by the Assigning

Authority, by HCID, or by repository unique IDs

depending upon gateway design

Directory and Hub rules reduce duplicate Carequality queries

and excess volume

7

?Copyright 2019 The eHealth Exchange. All rights reserved. Confidential.

How Will Data Flow?

8

?Copyright 2019 The eHealth Exchange. All rights reserved. Confidential.

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download