140 likes | 246 Views
Technical Steering Committee report Jan 2008. Charlie McCay TSC Chair. Topics. TSC activity since Sept Deliverables so far Objectives for 2008 Summary. Members. Charlie McCay (Chair), John Quinn (CTO), Karen VanH (HQ) Affiliates Charlie McCay, Frank Oemig Structure and Semantic Design
E N D
Technical Steering Committee report Jan 2008 Charlie McCay TSC Chair
Topics • TSC activity since Sept • Deliverables so far • Objectives for 2008 • Summary
Members • Charlie McCay (Chair), John Quinn (CTO), Karen VanH (HQ) • Affiliates • Charlie McCay, Frank Oemig • Structure and Semantic Design • Calvin Beebe, Greg Seppela • Domain Experts • Jim Case, Austin Kreisler • Foundation and Technology • Ioana Singureanu, Woody Beeler • Technical and Support Services • Ken McCaslin, Helen Stevens Love
Establishing the TSC • Initial meeting Sept, first full meeting this WGM • Confirmed formation documents on wiki: • Mission and Charter • decision making practices • Mission, Responsibilities, Composition and Formation document • Established working relationship with CTO
Activity since formation at Sept WGM • 13 conference calls • 12 pre-calls (CM, KVH, JQ) • Regular Steering Division Calls • Quiet TSC list and wiki • Very quiet SD lists • 25 issues logged with the TSC
Jan WGM • Sun 5-8pm • Monday – 5:30-8:30 pm plenary for all committee co-chairs Others welcome (meal for co-chairs only) Reports, Open Mike Session, SD breakouts • Tues Lunch
Deliverables • Worked with CTO on reforming the ARB • Established use of wiki for minutes, agendas and committee documents • Established use of gForge for issue tracking • Draft processes for committee formation and Dissolution • Approved various project scope statements • Web migration coordination
In process • Issue tracking in gForge • TSC input to and use of “HL7 Product and services strategy” • Establishing the Project Services Committee
Committee structures Bedding in of the Steering Divisions, and establishing the respective roles and relationship to the TSC of the non-technical committees such as PIC, Marketing, Project Services, CIC and ARB
Examples of Other Issues addressed • 2.6 publishing issue (deprecated messages) • Schema errors and ballot quality • ISO/CEN/HL7 collaboration work management • Scope of HDF, and relationship to other architecture and process documentation • Release of single HL7v3 edition for 2007+2008
Focus for 2008 • TSC reporting and communications processes • Establish effective ARB and Project Services Committees • Clarify roles/responsibilities • Issue management and tracking • Make real the HL7 Product and Services strategy
Summary • Clarity of roles / process vital • Visibility of work plans and what is being done • TSC success metrics • Concrete delivery to stakeholders
Affiliates • Charlie McCay and Frank Oemig • No issues raised yet by Affiliates to TSC • What does the affiliates council want from the TSC? • How do you want to hear about the TSC? • How can the TSC reach our international consumers? What do they want?
References • TSC Wiki: http://hl7tsc.org/ • TSC issue tracker: http://hl7projects.hl7.nscee.edu/tracker/index.php?group_id=52&atid=313