Difference between revisions of "2011-06-20 TSC Call Minutes"

From HL7 TSC
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 3: Line 3:
  
 
===Meeting Info/Attendees===
 
===Meeting Info/Attendees===
{{:TSC Meetings}}
+
   [[Category:2011 TSC Minutes]]
   [[Category:2011 TSC Minutes|Agenda Template]]
 
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 24: Line 23:
 
|width="0%"|'''Affiliation'''
 
|width="0%"|'''Affiliation'''
 
|-
 
|-
|?||Calvin Beebe||HL7 SSD SD Co-Chair
+
|x||Calvin Beebe||HL7 SSD SD Co-Chair
 
|-
 
|-
|?||Woody Beeler||HL7 FTSD Co-Chair
+
|x||Woody Beeler||HL7 FTSD Co-Chair
 
|-
 
|-
|?||Bob Dolin||HL7 Board Chair
+
|x||Bob Dolin||HL7 Board Chair
 
|-
 
|-
|?||Tony Julian||HL7 FTSD Co-Chair
+
|x||Tony Julian||HL7 FTSD Co-Chair
 
|-
 
|-
|?||Austin Kreisler||HL7 TSC Chair, DESD Co-Chair
+
|x||Austin Kreisler||HL7 TSC Chair, DESD Co-Chair
 
|-
 
|-
|?||Lynn Laakso ||HL7 staff support
+
|x||Lynn Laakso ||HL7 staff support
 
|-
 
|-
|?||Patrick Loyd|| HL7 T3SD Co-Chair
+
|x||Patrick Loyd|| HL7 T3SD Co-Chair
 
|-
 
|-
 
|regrets||Ken McCaslin||HL7 T3SD Co-Chair
 
|regrets||Ken McCaslin||HL7 T3SD Co-Chair
 
|-
 
|-
|?||Charlie Mead||HL7 ArB Chair
+
| ||Charlie Mead||HL7 ArB Chair
 
|-
 
|-
|?||Ravi Natarajan||HL7 Affiliate Representative
+
|x||Ravi Natarajan||HL7 Affiliate Representative
 
|-
 
|-
|?||Ron Parker||HL7 ArB Alternate
+
| ||Ron Parker||HL7 ArB Alternate
 
|-
 
|-
|?||John Quinn||HL7 CTO
+
|x||John Quinn||HL7 CTO
 
|-
 
|-
|?||Gregg Seppala||HL7 SSD SD Co-Chair
+
|regrets||Gregg Seppala||HL7 SSD SD Co-Chair
 
|-
 
|-
|?||Ed Tripp||HL7 DESD Co-Chair
+
|x||Ed Tripp||HL7 DESD Co-Chair
 
|-
 
|-
|?||Jay Zimmerman || HL7 Affiliate Representative
+
|x||Jay Zimmerman || HL7 Affiliate Representative
 
|-
 
|-
| || ||  
+
|x ||Brian Pech || observer
 
|-
 
|-
 
| || ||
 
| || ||
Line 64: Line 63:
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
|-
 
|-
|colspan="3" |'''Quorum Requirements (Chair +5 with 2 SD Reps) Met: '''(yes/No)
+
|colspan="3" |'''Quorum Requirements (Chair +5 with 2 SD Reps) Met: '''yes
 
|-
 
|-
 
|}
 
|}
Line 73: Line 72:
 
#Approve Minutes
 
#Approve Minutes
 
#Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] –
 
#Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] –
 +
#*Action items from WGM
 +
#**Calvin to check with the Cochairs of Structured Documents on naming for what title they want to use when they go beyond DSTU for an Implementation Guide.
 +
#**Austin and Patrick will check on the 2.x side on an implementation profile term.
 +
#**Patrick will look for his mapping of NCPDP to the RIM and let us know.
 
<!--              -->
 
<!--              -->
 
<!--    Approvals  -->
 
<!--    Approvals  -->
 
#Approval items:
 
#Approval items:
 +
#*'''Motion:''' to approve [http://gforge.hl7.org/gf/download/trackeritem/1961/8453/InM-WrappersRequirements-Scope-20110518.doc project scope statement] for InM of FTSD, cosponsored by SOA: ''InM Wrappers requirements determination'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=772 Project Insight # 772], [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=1961 TSC Tracker # 1941].
 
<!--              -->
 
<!--              -->
 
<!--  Discussion  -->
 
<!--  Discussion  -->
#Discussion topics:  
+
#Discussion topics:
 +
#*Review of Ballot Guidance post-2011May WGM - see [http://gforge.hl7.org/gf/download/docmanfileversion/6330/8445/BallotGuidance_post2011MayWGM.doc draft document] and Project Services [http://www.hl7.org/documentcenter/public/wg/projectServices/HL7%20PS%20-%20Electronic%20Ballot%20Chart%20-%20Final.pdf balloting guidance chart].
 +
#*TSC Communication Strategy at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=696 Project Insight ID # 696]
 +
#*[http://gforge.hl7.org/gf/download/docmanfileversion/6329/8444/TSC_Strategic_Initiatives_20110531.doc TSC Strategic Initiative Dashboard measures] project planning
 
#Reports: (attach written reports below from Steering Divisions et al.)
 
#Reports: (attach written reports below from Steering Divisions et al.)
 
<!-- #WGM Planning - -->
 
<!-- #WGM Planning - -->
Line 88: Line 95:
 
===Minutes===
 
===Minutes===
 
'''Minutes/Conclusions Reached:'''<br/>
 
'''Minutes/Conclusions Reached:'''<br/>
 +
#Introduction of visitors (including declaration of interests) Brian Pech observing
 +
#Agenda review and approval - Austin Kreisler reviewed the agenda and Ed added that we should report from the nominations committee, first under discussion topics. Austin added we should address Gregg’s resignation. Move right into that discussion.
 +
#*John moves we offer Gregg a letter of thanks, Calvin seconds. Send to both Gregg and to the VA to thank them for Gregg’s service. Unanimously approved. ACTTION ITEM: Austin and John will work with HQ to get that thank-you letter for Gregg together with HQ.
 +
#Approve Minutes of [[2011-06-13 TSC Call Agenda]], Ravi and Jay abstain, vote 5/0/2, approved.
 +
#Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] –
 +
#*Action items from WGM
 +
#**Calvin to check with the Cochairs of Structured Documents on naming for what title they want to use when they go beyond DSTU for an Implementation Guide. Calvin missed last week’s call and will take this up this coming week.
 +
#**Austin and Patrick will check on the 2.x side on an implementation profile term. Patrick has not been able to move this forward. He may have time this week.
 +
#**Patrick will look for his mapping of NCPDP to the RIM and let us know. Patrick has not had time to work on this.
 +
<!--              -->
 +
<!--    Approvals  -->
 +
#Approval items:
 +
#*'''Motion:''' to approve [http://gforge.hl7.org/gf/download/trackeritem/1961/8453/InM-WrappersRequirements-Scope-20110518.doc project scope statement] for InM of FTSD, cosponsored by SOA: ''InM Wrappers requirements determination'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=772 Project Insight # 772], [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=1961 TSC Tracker # 1941].
 +
#**Tony reports the purpose is to gather requirements for wrappers project. Scope is only to gather requirements, not a ballot project. If they get requirements they will start another project scope to take it forward. On a doodle poll to participate, he’s had only 5 or 6 respondents. Patrick reports this is needed in order to move the SAIF artifact definition forward. Existing sets of requirements are 4 or 5 years old and need to be validated. Previous wrappers project as well as Canadian wrappers requirements need vetting
 +
#**'''Vote:''' unanimously approved. Need to flag this project for attention by the SAIF AP. Lynn will forward to Dave Hamill.
 +
<!--              -->
 +
<!--  Discussion  -->
 +
#Discussion topics:
 +
#*Review from nominations committee. Ed reports we have two candidates for DESD and SSD SD, and one nomination for FTSD, T3SD and at least one for Affiliate, which meet all the minimum requirements for nominations. Austin thanks Ed for his work on the Nominations Committee.
 +
#*Review of Ballot Guidance post-2011May WGM - see [http://gforge.hl7.org/gf/download/docmanfileversion/6330/8445/BallotGuidance_post2011MayWGM.doc draft document] and Project Services [http://www.hl7.org/documentcenter/public/wg/projectServices/HL7%20PS%20-%20Electronic%20Ballot%20Chart%20-%20Final.pdf balloting guidance chart].
 +
#**Once we have the ballot guidance we may need to update them both. One is for how you choose, and then once you’ve chosen, the other is how you proceed with it.
 +
#**Two action items regarding on what to call implementation profiles versus implementation guides.
 +
#**Discussion on ISO implementation around sections of a document being normative versus informative. Implementers wishing one-stop shopping for the standard and its implementation guidance would like that.
 +
#**Ravi leaves the call; move Communication Strategy to next week.
 +
#**Ed says that the distinction between documents that have conformance criteria versus general implementation guidance is valuable, e.g. Pairing up a normative standard with normative implementation guide. Woody notes whether the issue is how we publish them. With the profile you might ballot normative and a guide would be informative but if it contains both types of information as in a profile it must ballot normative even if it contains informative guidance. Austin adds you need checkboxes on the project scope to indicate what the development intent and resulting ballot level will be. How will it be clearly indicated when the developed material is a Word document. So it seems we want a new indication on the project scope and what we call it remains up in the air. Realm specific rows collapse, for example. Follow up on action items and next week we can wrap this up.
 +
#*TSC Communication Strategy at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=696 Project Insight ID # 696] postpone to next week.
 +
#*[http://gforge.hl7.org/gf/download/docmanfileversion/6329/8444/TSC_Strategic_Initiatives_20110531.doc TSC Strategic Initiative Dashboard measures] project planning; Austin and John have not had time to develop a project scope.
 +
#Reports: (attach written reports below from Steering Divisions et al.)
  
  
'''''Please don't forget to hang up from the conference call '' (VOIP users)'''
 
 
===Next Steps===
 
===Next Steps===
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
|-
 
|-
 
|colspan="4" |'''Actions''' ''(Include Owner, Action Item, and due date)''<br/>
 
|colspan="4" |'''Actions''' ''(Include Owner, Action Item, and due date)''<br/>
* .
+
* Austin and John will work with HQ to get that thank-you letter for Gregg together with HQ.
 +
* Need to flag the wrappers project for attention by the SAIF AP. Lynn will forward to Dave Hamill.
 
|-
 
|-
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
*.
+
 
 +
*[http://gforge.hl7.org/gf/download/docmanfileversion/6329/8444/TSC_Strategic_Initiatives_20110531.doc TSC Strategic Initiative Dashboard measures] project planning;
 +
*Review of Ballot Guidance post-2011May WGM - see [http://gforge.hl7.org/gf/download/docmanfileversion/6330/8445/BallotGuidance_post2011MayWGM.doc draft document] and Project Services [http://www.hl7.org/documentcenter/public/wg/projectServices/HL7%20PS%20-%20Electronic%20Ballot%20Chart%20-%20Final.pdf balloting guidance chart].
 +
* TSC Communication Strategy at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=696 Project Insight ID # 696].
 
|}
 
|}

Latest revision as of 01:24, 28 June 2011

TSC Agenda/Minutes

Meeting Info/Attendees

HL7 TSC Meeting Minutes

Location: call 770-657-9270 using code 124466#
GoToMeeting ID: 165-215-206

Date: 2011-06-20
Time: 11:00 AM U.S. Eastern
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso
Attendee Name Affiliation
x Calvin Beebe HL7 SSD SD Co-Chair
x Woody Beeler HL7 FTSD Co-Chair
x Bob Dolin HL7 Board Chair
x Tony Julian HL7 FTSD Co-Chair
x Austin Kreisler HL7 TSC Chair, DESD Co-Chair
x Lynn Laakso HL7 staff support
x Patrick Loyd HL7 T3SD Co-Chair
regrets Ken McCaslin HL7 T3SD Co-Chair
Charlie Mead HL7 ArB Chair
x Ravi Natarajan HL7 Affiliate Representative
Ron Parker HL7 ArB Alternate
x John Quinn HL7 CTO
regrets Gregg Seppala HL7 SSD SD Co-Chair
x Ed Tripp HL7 DESD Co-Chair
x Jay Zimmerman HL7 Affiliate Representative
x Brian Pech observer


Quorum Requirements (Chair +5 with 2 SD Reps) Met: yes

Agenda

Agenda Topics

  1. Introduction of visitors (including declaration of interests)
  2. Agenda review and approval - Austin Kreisler
  3. Approve Minutes
  4. Review action items
    • Action items from WGM
      • Calvin to check with the Cochairs of Structured Documents on naming for what title they want to use when they go beyond DSTU for an Implementation Guide.
      • Austin and Patrick will check on the 2.x side on an implementation profile term.
      • Patrick will look for his mapping of NCPDP to the RIM and let us know.
  5. Approval items:
  6. Discussion topics:
  7. Reports: (attach written reports below from Steering Divisions et al.)
  8. Open Issues List


Supporting Documents

  • See links

Minutes

Minutes/Conclusions Reached:

  1. Introduction of visitors (including declaration of interests) Brian Pech observing
  2. Agenda review and approval - Austin Kreisler reviewed the agenda and Ed added that we should report from the nominations committee, first under discussion topics. Austin added we should address Gregg’s resignation. Move right into that discussion.
    • John moves we offer Gregg a letter of thanks, Calvin seconds. Send to both Gregg and to the VA to thank them for Gregg’s service. Unanimously approved. ACTTION ITEM: Austin and John will work with HQ to get that thank-you letter for Gregg together with HQ.
  3. Approve Minutes of 2011-06-13 TSC Call Agenda, Ravi and Jay abstain, vote 5/0/2, approved.
  4. Review action items
    • Action items from WGM
      • Calvin to check with the Cochairs of Structured Documents on naming for what title they want to use when they go beyond DSTU for an Implementation Guide. Calvin missed last week’s call and will take this up this coming week.
      • Austin and Patrick will check on the 2.x side on an implementation profile term. Patrick has not been able to move this forward. He may have time this week.
      • Patrick will look for his mapping of NCPDP to the RIM and let us know. Patrick has not had time to work on this.
  5. Approval items:
    • Motion: to approve project scope statement for InM of FTSD, cosponsored by SOA: InM Wrappers requirements determination at Project Insight # 772, TSC Tracker # 1941.
      • Tony reports the purpose is to gather requirements for wrappers project. Scope is only to gather requirements, not a ballot project. If they get requirements they will start another project scope to take it forward. On a doodle poll to participate, he’s had only 5 or 6 respondents. Patrick reports this is needed in order to move the SAIF artifact definition forward. Existing sets of requirements are 4 or 5 years old and need to be validated. Previous wrappers project as well as Canadian wrappers requirements need vetting
      • Vote: unanimously approved. Need to flag this project for attention by the SAIF AP. Lynn will forward to Dave Hamill.
  6. Discussion topics:
    • Review from nominations committee. Ed reports we have two candidates for DESD and SSD SD, and one nomination for FTSD, T3SD and at least one for Affiliate, which meet all the minimum requirements for nominations. Austin thanks Ed for his work on the Nominations Committee.
    • Review of Ballot Guidance post-2011May WGM - see draft document and Project Services balloting guidance chart.
      • Once we have the ballot guidance we may need to update them both. One is for how you choose, and then once you’ve chosen, the other is how you proceed with it.
      • Two action items regarding on what to call implementation profiles versus implementation guides.
      • Discussion on ISO implementation around sections of a document being normative versus informative. Implementers wishing one-stop shopping for the standard and its implementation guidance would like that.
      • Ravi leaves the call; move Communication Strategy to next week.
      • Ed says that the distinction between documents that have conformance criteria versus general implementation guidance is valuable, e.g. Pairing up a normative standard with normative implementation guide. Woody notes whether the issue is how we publish them. With the profile you might ballot normative and a guide would be informative but if it contains both types of information as in a profile it must ballot normative even if it contains informative guidance. Austin adds you need checkboxes on the project scope to indicate what the development intent and resulting ballot level will be. How will it be clearly indicated when the developed material is a Word document. So it seems we want a new indication on the project scope and what we call it remains up in the air. Realm specific rows collapse, for example. Follow up on action items and next week we can wrap this up.
    • TSC Communication Strategy at Project Insight ID # 696 postpone to next week.
    • TSC Strategic Initiative Dashboard measures project planning; Austin and John have not had time to develop a project scope.
  7. Reports: (attach written reports below from Steering Divisions et al.)


Next Steps

Actions (Include Owner, Action Item, and due date)
  • Austin and John will work with HQ to get that thank-you letter for Gregg together with HQ.
  • Need to flag the wrappers project for attention by the SAIF AP. Lynn will forward to Dave Hamill.
Next Meeting/Preliminary Agenda Items