Change assumptions given on the wiki to a clear list of definitions for comprehensive HIE, using full/partial terms suggested by Will Ross

Open

Vassil

6/1/10

Actions from last week

#

Date

Action

Status

Owner

Due Date

24

5/18/10

Vassil will create pages on Point 2 (Between an HIE participant and a stand-alone entity outside the HIE) and Point 3 (Between a participant in one HIE and a participant in another)

Open

Vassil

5/25/10

25

5/18/10

Rich Kernan will complete Comprehensive HIE Scenarios

Open

Rich

5/25/10

26

5/18/10

WG will review pages on Point 2 (Between an HIE participant and a stand-alone entity outside the HIE) and Point 3 (Between a participant in one HIE and a participant in another) and make comments/additions

Open

WG

5/25/10

27

5/18/10

WG will review Comprehensive HIE Scenarios and make comments/additions

Open

WG

5/25/10

28

5/18/10

Next week: Vassil will ask for cloning of the User Stories (look at parts of the User Stories that can be enhanced)

·Have different point of view than Vassil on assumptions oAssumption that a source belongs to an HIO ·Need to define HIO – Does a HIO represent a combined source and source HISP? ·Concern that the WG’s scope is too small if we’re just trying to tell existing HIOs that they should use the correct NHIN Direct transaction (to be discussion later in meeting)

Parag More

Are we only addressing the inter HIO transaction and not addressing how we would communicate with the edge?

Vassil Peytchev

·We are looking at three main scenarios, as outlined on wiki ·It’s up to each HIO to decide how interaction is done inside of it

Wenzhi Li

Pass

Will Ross

·Trying to understand the boundary between existing NHIN specs and NHIN Direct ·How does the comprehensive HIE service address the needs of sites that don’t have existing NHIN capabilities and just have NHIN Direct? oVassil Peytchev – The majority of the wiki addresses this use case

Tony Mallia

·Thinks vision of the diagram is wrong, we should look at the interaction between the protocols ·Need to keep in mind that we may be looking at the interaction between a push model and a pull model. Cannot assume that this will be push end-end.

Comment from Arien Malec ·Attempt to state Vassil’s assumption: By definition, a comprehensive HIO has solved the internal HIO communication problem from both push/pull transaction perspectives ·Two models: oVA/DoD/Kaiser – Uniform set of IT services and all local information inside HIO is handled oHeterogeneous – Does not have a comprehensive capability (ex: state HIEs) oFirst entrants to NHIN exchange fall into former, but many state HIEs fall into the later ·Thinks that Vassil is only looking at first case, the second case should be leverage NHIN Direct services Comment from Vassil Peytchev ·Does not assume that only homogenous HIOs would be comprehensive, but does assume that the majority of heterogeneous HIOs have solved this issue ·A comprehensive HIO should have the ability to satisfy the NHIN Direct user stories in some fashion oArien Malec – Restated, a comprehensive HIO should have solved motivating use cases for NHIN DirectComment from Karen Witting ·Need to write down definitions, hard to interpret content without clear definitions ·The section called assumptions should be changed to definitions oTerm comprehensive HIO is a bad name and needs to be more precisely defined oAlso need to define seamless interoperability Comment from Arien Malec ·Definition of comprehensive HIO presumes that all use cases are fully solved within the HIO ·A lot of states are implementing statewide services but aren’t solving within their HIO all of the use cases for NHIN Direct – these would not be comprehensive HIOs Comment from Will Ross ·Suggest the use of the terms full vs partial, applicable to both HIOs and level of interoperability Comment from Tony Mallia ·NHIO already has a NHIN Exchange definition, can’t use this term for our purposes Comment from Vassil Peytchev ·NHIO implies participation in NHIN Exchange and corresponding policy requirements ·We should leave policy as a separate issue and focus on issues related to technical comprehensive HIE capabilities Feedback on Arien’s Clarification of a Comprehensive HIO

Name

Feedback/Comment

George Cole

Hard to define, we need a list of transactions/properties that must be supported to meet this definition

Lin Wan

·Second Will’s recommendation to use full/partial terminology and to enumerate what services are included in each ·Using term comprehensive HIE may make things more difficult

Didi Davis

·Current assumptions are very broad ·Like the idea of defining HIO ·Third Will’s suggestion to use partial/full terms and provide an explanation of each

Matthew Weaver

Agree with George and Didi

Thanos Tsiolis

Would like to see list of capabilities for comprehensive HIE in bullet format

Parag More

Nothing to add

Wenzhi Li

Add definitions to wiki

Will Ross

Agree that we should turn assumptions into concise, thorough definitions

Tony Mallia

Confused by WG concern to give HIO a definition other than that as defined by NHIN Exchange

Comment from Arien Malec ·The definition of a HIO as given by NHIN Exchange is not sufficient for our purposes ·Ability to be a node on NHIN Exchange doesn’t say anything about the additional capabilities of that organization internally Comment from Tony Mallia ·Aboundary/transitional node has two faces, one as a node on NHIN Exchange and one as a presence in NHIN Direct Comment from Vassil Peytchev ·We are trying to define both sides of a node, whereas the term NHIO only defines one side ·Returning to Karen’s earlier question about why the WG is doing this: oIf we agree that the scenarios we have correspond with real-life situations and that we can let organizations do their internal communication however they want, we therefore assume that external communications leverage NHIN Exchange oIf an exchange happens between an NHIN node and a non-NHIN node, we want to make the types of exchange between these nodes compatible ·The concrete implementation groups will answer how this interoperability happens Comment from Karen Witting ·Are comprehensive HIE services and NHIN Exchange services the same thing? oVassil Peytchev - NHIN Exchange capabilities a core part of comprehensive HIE services Comment from Tony Mallia ·WG should look at how interoperability would happen on both sides (NHIN Exchange and NHIN Direct) at an abstract level Comment from Vassil Peytchev

Vassil to change assumptions given on the wiki to a clear list of definitions for comprehensive HIE, using full/partial terms suggested by Will Ross