Geographies Meeting 2010-05-28
Jump to navigation
Jump to search
Comment from Paul Tuten
Paul: For the timeline component, requirement for interim check-ins in order to track progress.
Comment: There seems to be a philosophical divergence around NHIN directs position with respect to NHIN Connect and the Gateway and if all the connection overhead going to be superimposed to the physician level.
Response from Umesh and Gary: NHIN Direct is independent with respect to NHIN Connect and Gateway.
Comment from Umesh regarding requirement of a HISP: Nothing fundamental about the design that requires a HISP. A HISP would make things easier. All that is required for a pilot is to follow the NHIN Direct Trust model.
Source code available on Google code put up by both MS and Cerner.
Comment from Paul regarding whether pilots will assume a HISP is present or will have to be created: Have pilots representing both models. Item for future discussion.
Comment from Paul on whether the number of IGs is capped: We are probably not capping, as long as they agree to meet the requirements.
Comment from Paul : If there is a Geography you are representing, make this information public so we know who to reach out to etc.
Notes from Implementation Geographies Workgroup
Date: May 28, 2010
Time: 2pm-3pm
Attendees: Francois Andry, Douglas Arnold, Frank Clark, Umesh Madan, Gary Christensen, Paul Tuten, Lee Jones
Actions for this Week
# |
Date |
Action |
Status |
Owner |
Due Date |
19 |
5/28/10 |
Response to question from Frank Clark: In the case of the NHIN Direct Pilots, will the Physicians sign DRSA agreements and go through the on-boarding process required for the connect-gateway entities? |
Open |
Paul |
N/A |
20 |
5/28/10 |
Identify which Implementation Geography you are representing, if any, on the main page: http://nhindirect.org/Implementation+Geographies |
Open |
WG |
N/A |
Actions from last Week
# |
Date |
Action |
Status |
Owner |
Due Date |
16 |
5/21/10 |
Clarify NHIN Direct branding nuances for proposed operating model on wiki |
Open |
Arien |
5/28/10 |
17 |
5/21/10 |
Update Guidelines to clarify coverage of MU exchange components and reflect other WG suggestions (including addition of the NHIN Exchange-NHIN Direct transaction and pilot timelines) |
Open |
Paul Tuten |
5/28/10 |
18 |
5/21/10 |
Review guidelines and provide feedback on the wiki |
Open |
WG |
5/28/10 |
Agenda
- Review action items from last week
- Discussion
- Next Steps
Notes
Comment from Paul Tuten
Participation guidelines and time line components need to be reviewed with the group. Partial feedback has been received.
Call for comments on the Implementation Geographies participation guidelines and checklist:
Name |
Comment |
Francois Andry |
None |
Douglas Arnold |
Going through the metrics. Questions on language around inter/intra state. No 5 - Provider to HIE exchange, until those exchanges are implemented statewide we cannot talk about connecting them. |
Frank Clark |
None |
Umesh Madan |
None |
Gary Christensen |
None |
Paul Tuten |
16 has not been addressed |
Lee Jones |
Clarification required on guideline no. 1. Is there an 'admission criteria' vs. 'recognition criteria'? Paul: the first three musts should be met, more like intent to conform than an admission criterion. |
Call for comments on the timeline:
Name |
Comment |
Francois Andry |
None |
Douglas Arnold |
Going through the metrics. Questions on language around inter/intra state. No 5 - Provider to HIE exchange, until those exchages are impleneted staatewide we cannot talk about connecting them. |
Frank Clark |
None |
Umesh Madan |
None |
Gary Christensen |
None |
Paul Tuten |
16 has not been addressed |
Lee Jones |
Clarification required on guideline no. 1. Is there an 'admission criteria' vs 'recognition criteria'. Paul: the first three musts should be met, more like an intnet to conform than an admission criteria. |
Comment from Paul Tuten
Paul: For the timeline component, requirement for interim check-ins in order to track progress.
Comment: There seems to be a philosophical divergence around NHIN directs position with respect to NHIN Connect and the Gateway and if all the connection overhead going to be superimposed to the physician level.
Response from Umesh and Gary: NHIN Direct is independent with respect to NHIN Connect and Gateway.
Comment from Umesh regarding requirement of a HISP: Nothing fundamental about the design that requires a HISP. A HISP would make things easier. All that is required for a pilot is to follow the NHIN Direct Trust model.
Source code available on Google code put up by both MS and Cerner.
Comment from Paul regarding whether pilots will assume a HISP is present or will have to be created: Have pilots representing both models. Item for future discussion.
Comment from Paul on whether the number of IGs is capped: We are probably not capping, as long as they agree to meet the requirements.
Comment from Paul : If there is a Geography you are representing, make this information public so we know who to reach out to etc.