Robust HIE WG Tracker
Jump to navigation
Jump to search
Action Items | |||||
# |
Date |
Action |
Status |
Owner |
Due Date |
1 |
4/1/2010 |
Revise IHE Implementation page to match revised Abstract Model |
Closed |
Arien |
4/6/2010 |
2 |
4/1/2010 |
Post an example of “intended recipient” |
Closed |
Arien |
4/6/2010 |
3 |
4/1/2010 |
Comment on statement 3.2 |
Open |
Thanos Tsiolis |
4/6/2010 |
4 |
4/1/2010 |
Raise metadata related topics to the Content Packaging group, unless we define a key reason why the HSP, rather than the Source/Destination, needs to care about metadata. |
Closed |
Arien |
4/6/2010 |
5 |
4/1/2010 |
Work with NHIN WG and ONC Policy Office to clarify the assumption that the NHIN Direct transactions are presumed to take place after a policy decision to transport data has already been made. If the endpoint does not transport electronically, will transport via fax, mail, courier, etc. |
Closed |
Arien |
4/6/2010 |
6 |
4/1/2010 |
Review Robust HIE page with these questions in mind: |
Open |
Group |
4/6/2010 |
1. Source-Destination HSP transactions | |||||
2. HSP-HSP Transactions | |||||
7 |
4/6/2010 |
Arien will frame up topics for next discussion |
Open |
Arien |
4/13/10 |
8 |
4/6/2010 |
Next time we will have a formalized discussion around John’s proposal: should we be looking at the metadata as the core issue, not the transaction? |
Open |
All |
4/13/10 |
9 |
4/6/2010 |
Take to User Story Workgroup: Confirm that the Status Update User Story is a “must have” |
Open |
Arien |
4/13/10 |
10 |
4/6/2010 |
Take to Security and Trust Workgroup: does there have to be a separation between HSP and the destination? |
Open |
Arien |
4/13/10 |
11 |
4/6/2010 |
Take to Robust HIE: if I am an HIO serving a geographic area and I have HSP’s running NHIN Stack and are peers does that help me or hurt me? |
Open |
Arien |
4/13/10 |
12 |
4/13/2010 |
Arien and Vassil will frame up topics for next discussion |
Open |
Arien & Vassil |
4/20/10 |
13 |
4/13/2010 |
Explore the assumption that NHIN Direct uses current NHIN specifications, using the current IHE Implementation proposal as a starting point (http://nhindirect.org/IHE+Implementation) |
Open |
All |
4/20/10 |
14 |
4/13/2010 |
Explore the assumption that NHIN Direct uses either the REST or SMTP implementation proposals. How would that fit with or conflict with the current NHIN? |
Open |
All |
4/20/10 |
15 |
4/20/2010 |
Provide the NHIN Exchange design principles for comparison with design principals of NHIN Direct (Rich) |
Open |
Rich |
4/27/2010 |
16 |
4/20/2010 |
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/2010 |
17 |
4/27/2010 |
Contribute to the discussion on the Wiki about User Experience [LINK?] |
Open |
All |
4/27/2010 |
18 |
4/27/2010 |
Conversation for next meeting: think about recommendations for the concrete implementation group |
Open |
All |
4/27/2010 |
19 |
5/6/2010 |
Rich will take the first shot at Extended User Story |
Closed |
Rich Kernan |
5/11/2010 |
20 |
5/6/2010 |
Please review this group, and join if interested: http://nhindirect.org/IHE+Implementation+Development+Team |
Closed |
All |
5/11/2010 |
21 |
5/11/2010 |
Rich will take the first step by integrating suggestions of the group |
Open |
All |
5/17/2010 |
-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 |
|||||
22 |
5/11/2010 |
Recommend to Keith that he restarts the conversation on the Content Packaging WG |
Open |
Vassil |
5/17/2010 |
23 |
5/11/2010 |
Vassil will add a link to Keith Boon’s blog post on XDS metadata”: http://motorcycleguy.blogspot.com/202010/04/quick-overview-of-ebxml-rim-objects-in.html |
Open |
Vassil |
5/17/2010 |
Key Decisions | |||||
# |
Date |
Key Decision |
Source |
||
1 |
4/1/2010 |
Assumption is that the holder of the data has already made the legal decision to release the data to the intended recipient |
All |
||
2 |
4/6/2010 |
Vassil Peytchev will be lead |
Open |
||