Robust HIE Meeting 2010-04-27

Notes from Robust HIE Workgroup

Status of Notes: DRAFT
Date: April 27, 2010
Time: 2pm-3pm
Attendees: Lin Wan, Chris Voigt, Didi Davis, Thanos Tsiolis, Noam Arzt, Parag More, Mark Stine, Will Ross, Gary Christenson, Tony Malia, Rich Kernan, Arien Malec &Vassil Peytchev

Actions for This Week

#	Date	Action	Status	Owner	Due Date
17	4/27/10	Contribute to the discussion on the Wiki about User Experience [LINK?]	Open	All	4/27/10
18	4/27/10	Conversation for next meeting: think about recommendations for the concrete implementation group	Open	All	4/27/10

Actions from Last Week

#	Date	Action	Status	Owner	Due Date
15	4/20/10	Provide one page comparison guidance principles of NHIN with design principals of NHIN Direct (Rich)	Open	Rich	4/27/10
16	4/20/10	Express dependency to S&T workgroup -- post to their page and make a comment and request that it becomes part of their discussion (Vassil)	Open	Vassil	4/27/10

Agenda:

• Review graphic from Arien: Graphic
• Impact of concrete implementation group discussion - backbone protocol vs. edge system protocols.
• What does "IHE Implementation" mean? Preparing for concrete implementation work.

Notes
Review graphic from Arien: Graphic
· Current NHIN Exchange
· XCA and XCR
· Leaves out some of the XDS B transactions that would occur within and IHO
· Points:
· Current set of transactions tend to have as their scope node to node
· Notion of routing is new
· Defining edge interaction is new
Comment from Lin Wan
· Will we cover end user?
· What is the edge interaction?
Comment from Noam Arzt
· Moving patient data around, but not specifying how the data gets out of the transport
· Edge interactions are unspecified, and on the top they are a little more specified
· Address Directory
· Global within the trust network
Comment from Vassil
· The directory part has not been specified beyond the concept level
· Those who are interested should look at Abstract Modeling WK
Comment from Mark Stine
· Address directory is more of a domain, DNS type service … can it be clarified that it is more of a hierarchy than an address directory? Vassil doesn’t think so.
· Should change to HISP Routing Directory
Comment from Tony Malia
· Assumption that a HISP equivalent to a node because they are put in the same place
· Same diagram
Impact of concrete iplementation group discussion - backbone protocol vs. edge system protocols
· Source and destination can operate in a “holding mode”
· Continuity of connection is a factor to
· Factors associated with protocol – EX: must be connected always, can be discontinuous etc … did those come up at the meeting?
· Design guidance … at least one needs to represent a pulling mode
· Nothing from HISP-HISP
· HISP to HISP or Edge Protocol
Comment from Lin Wan
· Should think about Edge Protocols as well
· Vote for both
Comment from Chris Voight
· Edge protocol shouldn’t be a requirement for success
· Goal of NHIN Direct is to define one or a set of transactions
Comment from Didi Davis
· Phased approach (HISP to HISP first and then move
· Minimum number
Comment from Noam Arzt
· Both parts of this should stay in
Comment from Mark Stine
· Initial focus should be on HISP-HISP
· Maintain simplicity
Comment from Will Ross
· Lower part is NHIN to NHIN classic
· Can be interactions between nodes and edge, but the key is that there are two HISP or NHIN notes that are communicating
· NHIN Direct – there could be one
· Talk about HISP-HISP but also focus on edge to edge
Comment from Tony Malia
· Idea of the conformance point
· Allows different HISPs to talk to different HISPs
· Main thing was to get NHIOs or nodes to speak to other notes
· Who is going to plug and play with what
· If mobility is important than having standard source protocol is important, if it isn’t then
· We should support plugablity but that shouldn’t exclude larger organizations
Clarification from Arien
· Provide advice/feedback and a vision for how the robust services and the routed services fit to scale
· If focusing on the backbone model
· How do we ensure interoperability and harmonization are to scale
What does "IHE Implementation" mean? Preparing for concrete implementation work.

• Three technological areas:
  • IHE implementation
• Based on previous discussions
• More generic description of this more appropriate?
  • IHE Metadata based implementation
  • SOAP based
• Content/trust models
• Is strict protocol adherence an appropriate consideration for Robust HIE Interoperability?
  • Allowed for transform of the protocols
  • Grounded on the fact that the NHIN Protocols use SOAP and associate stack with allows metadata richness and security & trust model to be fully expressed
  • Should we guide concrete implementation group to concentrate on the metadata and apply the appropriate protocols or should we emphasize the compatibility of protocols between concrete NHIN direct Implementation and current protocols
  • Look at this from the User Perspective
  • Contribute to the discussion on the Wiki about User Experience
  • Conversation for next meeting: think about recommendations for the concrete implementation group