Robust HIE Meeting Agenda and Notes - May 11, 2010
Jump to navigation
Jump to search
Concrete implementation update
Comment from Wes Rishel
· Are there links for user stories?
Comment from Karen Whiting
· Would like to get the group together
Comment from Lin Wan
· Get Content Group to come up with something
· Result of face to face meeting, the date on deciding moved to June 6th
Review scenario for NHIN Direct and NHIN Exchange combined use
· User of NHIN Exchange and NHIN Direct and how they will be able to combine the two scenarios
· Corresponds to discovering user story from specialist
· End – provider to patient transaction
· Page 1 is the overlay of what is new and how these combine
· Page 2/3 are reference/background
Comment from Arien Malec
· Helpful to place this into clinical context
· Feedback to expand: there will be an evolution of capabilities when you assume that Dr. Marks has access to a comprehensive HIE capability
Comment from George Cole
· Better word for transaction (clinical scenario)
Comment from Didi Davis
· Have to add some “what ifs”
· Nice and short
Comment from Thanos Tsiolis
· Beginning called assumptions
· Create a chart: name of person, and then their role, the capabilities of the system that each of the doctors have access to
Comment from Wes Rishel
· Is there a distinction between two physicians that are in the same HIOs and two physicians that are in HIOs that are interconnected within NHIN exchange
· Gender specific
Comment from Karen Witting
· What is the purpose of this document?
· Keep us both grounded in what matters clinically
· NHIN Exchange doesn’t have XDS or document sharing in it
· Will enable document exchange
· NHIN Direct Referral Response: from Referral User Story
Comment from Eric Heflin
· Project out to logical conclusion – classical use case model
· Have an alternate path or scenario for each user story
· Merge into each user story
Comment from Will Ross
· See the assumption that one of the actors lacks this advanced HIT capabilities
Comment from Lin Wan
· Transaction 4 – NHIN Connect/NHIN Exchange work together
· Why does the last transaction say query/retrieve documents?
Comment from Vassil Peytchev
· Agree that this needs to evolve
· 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
Review suggestion for Intra-HIE use of NHIN Direct
From Parag More
Three components
Initiating HER
HIR infrastructure group
Patient is getting refereed
Based on endpoint the HIE infrastructure acts like a broker
Requires destination to build XDR receiver
Trust model – when document goes to HIE, is it registered in registry for other things?
Mail is separated
Only reviewable by sender
Acknowledge that within an HIE even the Direct exchange will be subject to security across the HIE
WG will use the Wiki to add comments/questions about the suggestion for Intra-HIE use of NHIN Direct
Next steps and deliverables
Next steps – how can we ensure step up and step down?
· Look at Keith Boone’s list and list the pieces that can fit in
· Looking for a volunteer to take the table from Keith Boon’s blog post, and describe the creation of the required metadata based on configuration/policy agreement between the Source and Source HISP (as a opposed to requiring the Source to dynamically provide the metadata on submission)
· Add link to the Wiki on this agenda page
· Recommend to Keith that he restarts the conversation on the Content Packaging WG
· Vassil will add this link to the Wiki
· Lin Wan two more questions:
XDR has a way to indicate that this is a reply to a previous message
How do we reconcile – if we do this, do we still need MIME packaging
Notes from Comprehensive HIE Workgroup
Status of Notes: DRAFT
Date: May 11, 2010
Time: 2pm-3pm
Attendees Rich Kernan, Honora Burnett, Arien Malec, George Cole, Didi Davis, Thanos Tsiolis, Vassil Peytchev, Wes Rishel, John Moehrke, Karen Witting, Parag More, Eric Heflin, Mark Stine, Will Ross, Tim Cromwell, Jackie Key, Matt Weaver & Lin Wan
Actions from this 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 |
Open |
All |
5/17/10 |
| 22 |
5/11/10 |
Recommend to Keith that he restarts the conversation on the Content Packaging WG |
Open |
Vassil |
5/17/10 |
| 23 |
5/11/10 |
Vassil will add a link to Keith Boon’s blog post on XDS metadata”: [1] |
Open |
Vassil |
5/17/10 |
Actions from last week
| # |
Date |
Action |
Status |
Owner |
Due Date |
| 19 |
5/6/10 |
Rich will take the first shot at Extended User Story |
Closed |
Rich Kernan |
5/11/10 |
| 20 |
5/6/10 |
Please review this group, and join if interested: http://nhindirect.org/IHE+Implementation+Development+Team |
Closed |
All |
5/11/10 |
Agenda:
- Concrete implementation update
- Review scenario for NHIN Direct and NHIN Exchange combined use.
- Review suggestion for Intra-HIE use of NHIN Direct.
- Next steps and deliverables
Concrete implementation update
Comment from Wes Rishel
· Are there links for user stories?
Comment from Karen Whiting
· Would like to get the group together
Comment from Lin Wan
· Get Content Group to come up with something
· Result of face to face meeting, the date on deciding moved to June 6th
Review scenario for NHIN Direct and NHIN Exchange combined use
· User of NHIN Exchange and NHIN Direct and how they will be able to combine the two scenarios
· Corresponds to discovering user story from specialist
· End – provider to patient transaction
· Page 1 is the overlay of what is new and how these combine
· Page 2/3 are reference/background
Comment from Arien Malec
· Helpful to place this into clinical context
· Feedback to expand: there will be an evolution of capabilities when you assume that Dr. Marks has access to a comprehensive HIE capability
Comment from George Cole
· Better word for transaction (clinical scenario)
Comment from Didi Davis
· Have to add some “what ifs”
· Nice and short
Comment from Thanos Tsiolis
· Beginning called assumptions
· Create a chart: name of person, and then their role, the capabilities of the system that each of the doctors have access to
Comment from Wes Rishel
· Is there a distinction between two physicians that are in the same HIOs and two physicians that are in HIOs that are interconnected within NHIN exchange
· Gender specific
Comment from Karen Witting
· What is the purpose of this document?
· Keep us both grounded in what matters clinically
· NHIN Exchange doesn’t have XDS or document sharing in it
· Will enable document exchange
· NHIN Direct Referral Response: from Referral User Story
Comment from Eric Heflin
· Project out to logical conclusion – classical use case model
· Have an alternate path or scenario for each user story
· Merge into each user story
Comment from Will Ross
· See the assumption that one of the actors lacks this advanced HIT capabilities
Comment from Lin Wan
· Transaction 4 – NHIN Connect/NHIN Exchange work together
· Why does the last transaction say query/retrieve documents?
Comment from Vassil Peytchev
· Agree that this needs to evolve
· 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
Review suggestion for Intra-HIE use of NHIN Direct
From Parag More
Three components
Initiating HER
HIR infrastructure group
Patient is getting refereed
Based on endpoint the HIE infrastructure acts like a broker
Requires destination to build XDR receiver
Trust model – when document goes to HIE, is it registered in registry for other things?
Mail is separated
Only reviewable by sender
Acknowledge that within an HIE even the Direct exchange will be subject to security across the HIE
WG will use the Wiki to add comments/questions about the suggestion for Intra-HIE use of NHIN Direct
Next steps and deliverables
Next steps – how can we ensure step up and step down?
· Look at Keith Boone’s list and list the pieces that can fit in
· Looking for a volunteer to take the table from Keith Boon’s blog post, and describe the creation of the required metadata based on configuration/policy agreement between the Source and Source HISP (as a opposed to requiring the Source to dynamically provide the metadata on submission)
· Add link to the Wiki on this agenda page
· Recommend to Keith that he restarts the conversation on the Content Packaging WG
· Vassil will add this link to the Wiki
· Lin Wan two more questions:
XDR has a way to indicate that this is a reply to a previous message
How do we reconcile – if we do this, do we still need MIME packaging