Notes from Comprehensive HIE Workgroup

Status of Notes: DRAFT
Date: May 18, 2010
Time: 2pm-3pm
Attendees Honora Burnett, Arien Malec, George Cole, Vassil Peytchev, George Cole, Tom Silvious, Noam Artz, Karen Witting, Mark Stine, Wenzhi Li, Will Ross, Rich Kernan, Jackie Key, Kevin Puscas & Adeola Odunlami

Actions from this 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)
Open
Vassil
5/25/10

Actions from last week
#
Date
Action
Status
Owner
Due Date
21
5/11/10
Rich will take the first step by integrating suggestions of the group
-Better word for transaction (clinical scenario)
-Create a chart: name of person, and then their role, the capabilities of the system that each of the doctors have access to
Mid-update will have
All
5/17/10
22
5/11/10
Recommend to Keith that he restates the conversation on the Content Packaging WG
Completed
Vassil
5/17/10
23
5/11/10
Vassil will add a link to Keith Boon’s blog post on XDS metadata: http://motorcycleguy.blogspot.com/2010/04/quick-overview-of-ebxml-rim-objects-in.html
Completed
Vassil
5/17/10

Agenda
· Deliverables for June 11
o Comprehensive HIE Services Description and Diagram (may be needed by Concrete Implementations work group)
o Comprehensive HIE Scenarios (may be adopted as new user stories by User Story Review work group)
· Milestones/activities need to happen between now and June 11th in order to have these deliverables ready for June 11th
· Dependencies between comprehensive HIE and the other workgroups?
o IHE Concrete Implementation workgroup update
o Do other work groups need deliverables from comprehensive HIE in order to produce their own deliverables for June 11th
o Does comprehensive HIE need anything from other workgroups in order to produce its deliverables?
· NHIN Direct in the context of a comprehensive HIE:
  1. Within the HIE, specific agreements and policies apply, this is out of scope for NHIN Direct
  2. Between an HIE participant and a stand-alone entity outside the HIE
    • sending
    • receiving
  3. Between a participant in one HIE and a participant in another HIE (assuming both participate in NHIN Exchange)
Notes
Feedback on three cases and the potential for a fourth case where there are two HIE’s that don’t participate in the limited production exchange
  • Within the HIE, specific agreements and policies apply, this is out of scope for NHIN Direct
  • Between an HIE participant and a stand-alone entity outside the HIE
    • sending
    • receiving
  • Between a participant in one HIE and a participant in another HIE (assuming both participate in NHIN Exchange)
Comment from Tom Silvious
· Keep scope limited, we don’t want to lose end sate objective to engage different stakeholders

Comment from Noam Artz
· States are still confused as they are trying to figure out their perspective as an intermediary between local and national efforts
· Fine to limit the scope but want to make sure that
Comment from Karen Witting
· Ignore cases that aren’t relevant
· Needs to go in both directions
· Might want to add to some – a statement/analysis
Comment from Wil Ross
· Most important is that we have time/bandwidth constraints so can’t propose to do all things
· Have limited # of user stories
· Have comprehensive HIE
· Connect + Direct? Just Connect?
· Keep to a couple of patterns
Comment from Rich Kernan
· Keep messaging clear
· What from all the NHIN services can someone implement in the minimum set of these services?
· What is a participant look like?
Comment from Arien Malec
· Respect to issue #1
· Some cases when this is true, and some cases when this is not true
· Important for states to all understand how they fit together
· Where it makes sense to focus on nationwide, NHIN Direct has focused
· CONNECT is a label, product component
Comment Vassil Peytchev
· Points 1,2 are clear
o 2 will be starting point for services description diagram
o Describing the services as an HIE can provide to participants in addition to other NHIN Direct services that makes it possible to interact with anyone outside the HIE using the NHIN Direct protocols
o Similar to cross over diagram
§ Bottom part isn’t end to end
§ Bottom left/right corner with own services in that area
o Vassil will create a discussion page for point 2 (Between an HIE participant and a stand-alone entity outside the HIE)
· Point 3 is confusing
o Bringing out issues and looking at what currently exists and what could work in different scenarios
o Open ended
o Vassil will start a page on 3 (Between a participant in one HIE and a participant in another)to list certain cases and others will join to contribute to a description that boils down to “there are many ways to skin this cat, and we need to make sure that the business flow is the same for the end user”
Comment from Arien Malec
· Is this really out of scope?
· There are use cases that NHIN Direct has introduced and not met by NHIN Exchange
· Not use the same transaction, but workflow
· Conclusion: my expectation as a provider is that the workflow feels the same regardless of which of these three cases this is (technology may be different)

· 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)
· Rich Kernan will complete Comprehensive HIE Scenarios
· 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
· WG will review Comprehensive HIE Scenarios and make comments/additions
· Next week: Vassil will ask for cloning of the User Stories (look at parts of the User Stories that can be enhanced)
Dependencies between comprehensive HIE and the other workgroups?
  • IHE Concrete Implementation workgroup update
  • Do other work groups need deliverables from comprehensive HIE in order to produce their own deliverables for June 11th
  • Does comprehensive HIE need anything from other workgroups in order to produce its deliverables?