Difference between revisions of "2018-01-29 TSC WGM Agenda"

From HL7 TSC
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 36: Line 36:
 
| || || ||||'''TSC Co-chair Dinner'''|||
 
| || || ||||'''TSC Co-chair Dinner'''|||
 
|-
 
|-
−
| ||17:45 - 18:10||||Welcome and TSC Chair Report|| Austin Kreisler, TSC Chair|||  
+
| ||17:45 - 18:10||||Welcome and TSC/CTO Report|| Wayne Kubick, CTO|||  
 
|-
 
|-
−
| ||18:10 - 18:30||||CTO Report||Wayne Kubick|||
+
| ||18:10 - 18:15||||Ballot Report||Lynn Laakso|||
 +
|-
 +
| ||18:15 - 18:20||||PMO Update||Dave Hamill|||
 +
|-
 +
| ||18:20 - 18:30||||UTG Project Update||Ted Klein|||
 +
|-
 +
| ||18:30 - 18:35||||FHIR Update||Lloyd McKenzie|||
 
|-
 
|-
 
| ||19:00 - 20:00|| || <u>Steering Division Meetings </u><br/>
 
| ||19:00 - 20:00|| || <u>Steering Division Meetings </u><br/>
Line 70: Line 76:
 
| width="10%" colspan="1" align="right"|'''Facilitator'''
 
| width="10%" colspan="1" align="right"|'''Facilitator'''
 
| width="35%" colspan="1" align="left"|Austin Kreisler
 
| width="35%" colspan="1" align="left"|Austin Kreisler
−
| width="25%" colspan="1" align="right"|'''Note taker(s)'''
+
| width="25%" colspan="1" align="left"|'''Note taker(s)'''
 
| width="30%" colspan="1" align="left"|Anne Wizauer
 
| width="30%" colspan="1" align="left"|Anne Wizauer
 
|-
 
|-
Line 85: Line 91:
 
|                                                                                |
 
|                                                                                |
 
===============================================================================--->
 
===============================================================================--->
−
 
+
|}
  
 
<!---=======================================================
 
<!---=======================================================
Line 98: Line 104:
  
 
===Agenda===
 
===Agenda===
−
#Welcome and TSC Report - Austin Kreisler, TSC Chair
+
#Welcome and TSC/CTO Report - Wayne Kubick, CTO
−
#CTO Report - Wayne Kubick
+
#Ballot Report - Lynn Laakso
 +
#PMO Update - Dave Hamill
 +
#UTG Project Update - Ted Klein
 +
#FHIR Update - Lloyd McKenzie
  
 +
Links to reports:
 +
#PMO Update
 +
#[https://gforge.hl7.org/gf/project/tsc/docman/Reports/HarmNov2017Report.pptx Harmonization Report]
 +
#[https://gforge.hl7.org/gf/project/tsc/docman/Reports/2018JAN_Ballot_Report.pdf Ballot Report]
 +
#FHIR Update
  
−
Links to other reports:
 
−
#PMO Report - Dave Hamill
 
−
#Harmonization Report - Ted Klein
 
−
#Ballot Report - Lynn Laakso
 
−
#FHIR Report - Lloyd McKenzie
 
  
 
===Q&A===
 
===Q&A===
 +
*Questions for Lloyd McKenzie:
 +
**For the use of Jira in balloting - what about large organizations who have people who are not HL7 members reviewing and commenting? They would have to train on Jira right? Lloyd: We're going to do our best to make the submission process relatively painless. In terms of what we're doing with Gforge right now, we don't offer training and we have hundreds of people who do that. Jira will likely be even easier. If we need to provide training we can certainly do a webinar and provide a link to it.
 +
**DOD, VA, etc. will take the comments from the SMEs, roll them together, and then vote them all at once. The spreadsheets are handy in that process. Is there an equivalent process in Jira? We would have to get user IDs for all of these folks? Lloyd: For those who do block voting, the answer is we have thought about that and in the requirements there is a description of what that will look like. That will change somewhat but we're trying to enable that type of behavior in a way that still meets our objectives with Jira; the person who has the issue makes the submission so they're the ones that get the notifications.
 +
**We need to make sure that the security issues with government laptop software are addressed. Lloyd: It will be a website. We will absolutely monitor that as part of the trial and then figure out how to address it if need be.

Latest revision as of 00:50, 30 January 2018

Back to TSC_Minutes_and_Agendas

Day Date ' Time Icon Event Chair Scribe Room
Monday 2018 January 29 AM Q1
Q2
PM Q3
Q4
Q5 TSC Monday Co-Chairs Dinner/Meeting
Austin Kreisler Anne Wizauer


- - - Collect food/drink from buffet
TSC Co-chair Dinner
17:45 - 18:10 Welcome and TSC/CTO Report Wayne Kubick, CTO
18:10 - 18:15 Ballot Report Lynn Laakso
18:15 - 18:20 PMO Update Dave Hamill
18:20 - 18:30 UTG Project Update Ted Klein
18:30 - 18:35 FHIR Update Lloyd McKenzie
19:00 - 20:00 Steering Division Meetings

Domain Experts - Camp - 3rd Floor
Foundation and Technology - Canal - 3rd Floor
Structure and Semantic Design - Magazine - 3rd Floor
Technical and Support Services - Jackson - 3rd Floor

Minutes

Meeting Information

HL7 Co-chairs dinner/meeting

Location: St. Charles Ballroom, 3rd Floor

Date: 2017-01-26
Time: 17:15-21:00pm
Facilitator Austin Kreisler Note taker(s) Anne Wizauer


Agenda

  1. Welcome and TSC/CTO Report - Wayne Kubick, CTO
  2. Ballot Report - Lynn Laakso
  3. PMO Update - Dave Hamill
  4. UTG Project Update - Ted Klein
  5. FHIR Update - Lloyd McKenzie

Links to reports:

  1. PMO Update
  2. Harmonization Report
  3. Ballot Report
  4. FHIR Update


Q&A

  • Questions for Lloyd McKenzie:
    • For the use of Jira in balloting - what about large organizations who have people who are not HL7 members reviewing and commenting? They would have to train on Jira right? Lloyd: We're going to do our best to make the submission process relatively painless. In terms of what we're doing with Gforge right now, we don't offer training and we have hundreds of people who do that. Jira will likely be even easier. If we need to provide training we can certainly do a webinar and provide a link to it.
    • DOD, VA, etc. will take the comments from the SMEs, roll them together, and then vote them all at once. The spreadsheets are handy in that process. Is there an equivalent process in Jira? We would have to get user IDs for all of these folks? Lloyd: For those who do block voting, the answer is we have thought about that and in the requirements there is a description of what that will look like. That will change somewhat but we're trying to enable that type of behavior in a way that still meets our objectives with Jira; the person who has the issue makes the submission so they're the ones that get the notifications.
    • We need to make sure that the security issues with government laptop software are addressed. Lloyd: It will be a website. We will absolutely monitor that as part of the trial and then figure out how to address it if need be.
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=2018-01-29_TSC_WGM_Agenda&oldid=19501"