Difference between revisions of "2009-06-08 TSC Call Agenda"

From HL7 TSC
Jump to navigation Jump to search
Line 56: Line 56:
 
#** [http://www.hl7.org/documentcenter/public/techNewsletter/HL7_TECHNEWSLETTER_20081125.pdf#page=8 Why do three year plans?]
 
#** [http://www.hl7.org/documentcenter/public/techNewsletter/HL7_TECHNEWSLETTER_20081125.pdf#page=8 Why do three year plans?]
 
#** How do we provide linkage and feedback to the Roadmap (and the Roadmap Task Force)?
 
#** How do we provide linkage and feedback to the Roadmap (and the Roadmap Task Force)?
#**Project Insight and GForge cost-benefit analysis - from listserv thread - can we use this for three-year planning
+
#**Project Insight and GForge cost-benefit analysis - from [http://lists.hl7.org/read/messages?id=152760 listserv thread] - can we use this for three-year planning
 
#*Review and discuss [http://hl7projects.hl7.nscee.edu/frs/?group_id=52 Work Group Health documents], and determine a plan to agree what the metrics should be in the spreadsheets, and what we show on the Monday evening cochairs meeting in Atlanta
 
#*Review and discuss [http://hl7projects.hl7.nscee.edu/frs/?group_id=52 Work Group Health documents], and determine a plan to agree what the metrics should be in the spreadsheets, and what we show on the Monday evening cochairs meeting in Atlanta
  
 
=[[TSC Agenda item list| Future Agenda item list]]=
 
=[[TSC Agenda item list| Future Agenda item list]]=
 
=[[TSC Action item list|Click for TSC Action Item List]]=
 
=[[TSC Action item list|Click for TSC Action Item List]]=

Revision as of 14:04, 5 June 2009

TSC - Technical Steering Committee

Monday, June 8, 2009 11:00 AM (US Eastern Daylight Time, GMT -5)
To participate, dial 770-657-9270 and enter pass code 124466#
GoToMeeting at https://www.gotomeeting.com/join/165215206
GoToMeeting ID: 165-215-206 

back to TSC Minutes and Agendas

Attendance

Expected

  • Chair: Charlie McCay
  • CTO: John Quinn
  • Domain Experts: Austin Kreisler (primary), Ed Tripp (alternate)
  • Foundation & Technology: Ioana Singureanu (primary), Woody Beeler (alternate)
  • Structure & Semantic Design: Calvin Beebe (primary), Gregg Seppala (alternate)
  • Technical & Support Services: Ken McCaslin (primary), Helen Stevens Love (alternate)
  • Affiliate: Ravi Natarajan
  • ARB: Charlie Mead (primary), John Koisch (alternate)
  • Ad-Hoc: Jim Case
  • HQ: Lynn Laakso

Invited

  • Charles Jaffe (CEO)
  • Ed Hammond (HL7 Chair); Bob Dolin (HL7 Vice Chair)
  • Marc Koehn (EA IP)
  • Karen Van Hentenryck (HQ)

Apologies

Agenda

  1. (5 min) Meeting Admin
    1. Roll Call -
    2. Accept Agenda -
    3. Approve Minutes from
    4. Review action items
  2. (20 min) Standing Committee Reports/Approvals
    1. CEO Report -
    2. CTO Report -
    3. ArB Report -
    4. Affiliates Report -
    5. Domain Experts -
    6. Foundation & Technology -
      • proposed RASCI (Responsible, Accountable, Supportive, Consulted, Informed) chart discussion to manage the apparent overlap between various work groups and projects in our Steering Division: Draft RASCI chart. We would like to propose the approach and a first draft chart. In view of great upcoming changes, it may be useful to use RASCI charts for the entire organization collaboratively with the work groups to identify the responsibilities and interests of various stakeholder. A RASCI chart approach may be used for other new, cross-cutting activities initiated by the TSC.
      • Project Insight and GForge cost-benefit analysis - from listserv thread
    7. Structure & Semantic Design -
    8. Technical & Support Services -
  3. (30 min) Discussion topics
    • Open Issues List
    • Technical Newsletter call for articles - deadline June 23rd to Karen Van Hentenryck
    • Requiring NWIP and HL7 Project Scope Statements to include a table of related products and projects, and to describe the intended scope boundary and joint maintenance approach for each
    • Tabled Motion:The TSC provide a structure and format guideline for three year plans to the WGs that describes the content detail required for their own project guidance and decision making processes.
      • Why do three year plans?
      • How do we provide linkage and feedback to the Roadmap (and the Roadmap Task Force)?
      • Project Insight and GForge cost-benefit analysis - from listserv thread - can we use this for three-year planning
    • Review and discuss Work Group Health documents, and determine a plan to agree what the metrics should be in the spreadsheets, and what we show on the Monday evening cochairs meeting in Atlanta

Future Agenda item list

Click for TSC Action Item List