Meeting-20080914

TSC - Technical Steering Committee

Sunday, September 14, 2008 6:00 PM (US Pacific Time)

back to TSC Minutes and Agendas

Attendance

Expected

• CTO: John Quinn
• Domain Experts: Jim Case (primary), Austin Kreisler (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: Frank Oemig,
• ARB Chair: Charlie Mead
• HQ: Karen Van Hentenryck

invited

• Charles Jaffe (CEO); Ed Hammond (HL7 Chair); Chuck Meyer (HL7 Vice Chair); Ed Tripp (newly elected TSC member to take office Jan. 2009); Ravi Natarajan (newly elected TSC member to take office Jan. 2009)

Agenda

1. (5 min) Meeting Admin
   1. Roll Call - The following individuals were in attendance: John Quinn, John Koisch, Calvin Beebe, Ken McCaslin, Woody Beeler, Frank Oemig, Ed Hammond, Jim Case, Jane Curry, Ravi, Gregg Seppala, Austin Kreisler, Ioana Singureanu, Helen Love, Charlie McCay, and Karen Van Hentenryck
2. Continued discussion - Enterprise Architecture deliverable - J. Koisch reported that the ArB discussed the communication plan for this project. They've drafted a vision, talked about the timeline and milestones, stakeholders, socialization, etc. The ArB believes that the SAEAF reprents a framework that can yeild measurable efficiences in terms of the development and adoption of standards, He reviewed the timeline, which includes peer review and engagement of groups within HL7. They hope to release the slide desks to the co-chairs listserv. They feel that is a requirement for a set of out-of-cycle meetings between now and the Jan 2009 WGM. One needs to be a face-to-face, the other two can be virtual meetings (calls) for vetting/feedback. In Jan. they hope to deliver an impact and education, drafts to comments. Finalce the document at the May 2009 WGM. John reviewed the communication plan for the Sept WGM and the plans for the out-of-cycle meetings. One of these will be F2F, with the other two being virtual sessions to include community vetting/comment. In Jan. they hope to understand the organizational impact of this change, and should provide educational sessions. They believe several work groups will wish to to be early adopters of this work and there will be ArB outreach to those who are interested. Koisch noted that many of the TSC issues discussed yesterday might have a different answer given the enterprise architecture. For May, they will be looking at the re-organization of the work groups, and look at reconstituted ballots. Beeler feels that in Jan 2009, there should be meetings with MnM, publishing etc to determine how to deal with the current content (how to convert the current materail). The ArB has discussed having the SAEAF and other documents completed by early Nov. Mid to late Nov. is the appropriate date for the F2F meeting. McCay feels the TSC needs to take on the task of developing a presentation on this work. STakeholders include work groups, vendors, the larger community, other SDOs and contracting offices. The potential impactes include
   • potential realignment of work groups
   • alignment of processesfor work products across specifications
   • quality critera for ballot participation and progression
   • Enhancement and refinemtn of conformance framework for V3 to incorporate SOA concerpts
   • Backwards compatibiityh considerations of SAEAF principels on existing specs and work in progress. All impacts should be discussed if not dealt with by Jan. Beeler wishes to speed up adoption i.e., if things don't make sense stop doing them now.
3. Timetable for socialization, review and endorsement
   1. 1. What documents need to be reviewed and approved, by whom, and when/how
      2. Benefits identification -- who is this good for, and how will we know the good is delivered
   2. Timetable for demonstrating, piloting, and rollout
      1. Organizational -- changes to committee structures and responsibilities
      2. Content -- what is the impact on those developing content
      3. Education -- who needs to learn what when, and how will that happen
      4. Tooling -- What changes to tools will be needed and when
      5. Adoption -- who will adopt and when
4. Roadmap, WG 3 year plans and SWOTs
   1. next steps - relationship between HL7 roadmap, TSC plans, SD plans, and WG plans
   2. Exploitation - who needs to see these plans, and why?
5. Resource issues - Helen Stevens
6. Project Template approvals - McCaslin
7. Mirth Tool issue
8. Legal right to use HL7 vocabulary in non-HL7 specifications
9. Agenda for Tuesday Lunch