HL7 Technical Steering Committee

From HL7 TSC
Jump to: navigation, search

- It's Mission, Responsibilities, Composition and Formation

Introduction

This document includes a complete definition of a restructured Technical Steering Committee (TSC), its composition and relationships. It is based on recommendations made by the HL7 Technical Transition Task Force (T3F) to the HL7 Board.

Background

The T3F developed this document during the first four monthes of 2007 and presented it the the HL7 Board for adoption in May 2007. The plan was revised collaboratively with the Board during May and was adopted in early-June 2007, leading to the initial TSC elections during the summer of 2007.

In this context, "Technical Steering Committee" refers to the elected and appointed representatives of a ten-member committee that will oversee the technical affairs of HL7 and is the primary focus of this document. This group will continue to convene Technical Steering Committee Plenary Meetings of the Co-chairs of all HL7 Technical Committees and SIGs at each WGM.

Status of this Document

The T3F intended that this document be a "contract" between the Technical Steering Committee and the HL7 Board of Directors. It should be a "living" document that evolves as the TSC evolves. It should not be replaced by a "Charter" for the Technical Steering Committee, but rather the Charter should be drawn from this document and evolve as this document and the TSC itself evolves.

The T3F recommended that the TSC adopt a "Sunset" Review" of this document to commence early in 2010, after the new TSC has been functioning for two years. At that time, all of the recommendations for TSC structure and function should be formally reviewed. The TSC should then make a report to the Board assessing what is working, what is not and include proposed changes, if any are needed

Mission

Mission Statement

The HL7 Technical Steering Committee oversees and coordinates the technical effort contributed by the HL7 volunteers who make up the HL7 Working Group. Its mission is to assure that the efforts of the Working Group are focused on the overall HL7 mission established by the HL7 Board.

The Technical Steering Committee and the HL7 Working Group operate in such a way so as to:

  • respect the contributions and ideas of the talented individuals who make up the Working Group;
  • maintain an effective focus on the goals of HL7;
  • assure that the all major decisions are based on consensus of the stakeholders;
  • maximize sharing and "re-use" of work products between elements of the Working Group;
  • use project management to assure that project goals are articulated and met;
  • reduce competition and conflict between the elements of the Working Group; and
  • assure that HL7 standards are developed on a solid architectural foundation that assures consistency and interoperability.


Success Criteria

The Technical Steering Committee success criteria must focus on three core objectives -- assuring the continuity and vitality of the HL7 volunteer-based Working Group; maintaining coherent inter-operable standards while minimizing duplication of effort; and providing sound consensus-based standards that meet the needs and schedule requirements of HL7's clients.

The Technical Steering Committee will be successful if HL7 members can easily find answers to the following sorts of questions:

  • What is HL7 doing in the area of xxx? Where xxx is an area of interest to a member
    • what publications exist?
    • what active projects / work-items are there?
    • what committee is responsible for that area?
  • What is happening on this project?
    • When will it deliver?
    • What can I do to make that faster / more likely to deliver on time?
    • What has happened recently (is it really active?, has it delivered on schedule?) What is happening to this publication?
  • How do I know what to do at a WGM?
  • What is the status of a particular HL7 specification or document?
    • Who is using / plans to use this publication?
    • What feedback was received to this DSTU?
    • What change proposals are open for this publication?
    • Who maintains this document, and where do I send comments / questions
    • What is the ballot history for this document (when was it balloted, and what were the comments and resolution, and what was the ballot pool)
    • Are there any plans to produce a revision for this document?

Defining success criteria in this way shows how the TSC is mandated to expose the information that is needed for the board and membership to be able to plan effectively and to support the promotion of the consensus-based products. It also underpins the importance of work reuse, and only having as many projects and committees as are needed. Finally it defines success in a way that reflects the questions that led to the recommendations to restructure the TSC.

Responsibilities

This section is based on Strategic Initiative documents, on-going revision by the T3F, the Mission statement above, and consideration of the stated responsibilities of the Technical Steering Committee as documented in HL7's Bylaws and the Policies and Procedures Manual. These responsibilities are shared, as noted below, with the four Steering Divisions (SD) (sub-groups of committees) that report to the Technical Steering Committee.

Oversees Execution of Standards Development

Assures that the efforts of the Working Group (WG) are effectively focused on accomplishing the product and services strategy set forth by the Board.
  • Participates in development of an HL7 Product and Services strategy for adoption by the HL7 Board
  • Oversees the TSC Steering Divisions (SD) in the establishment and management of projects and project teams to accomplish the product and services strategy set by the Board. To that end, it works through the SDs to:
    • Approve new work groups based on priority projects
    • Dissolve work groups no longer required based on the HL7 Products and Services strategy
    • Works with sub-groups to align and prioritize projects in accordance with the products and services strategy
    • Working with the subgroups, helps to ensure the availability of project resources
      • helps with resource provision or recruitment (people, rooms, tools, etc)
      • includes ensuring the continuity, vitality, and effectiveness of the HL7 volunteer-based Working Group
  • Approve, monitor, and perhaps intervene in overall product development
    • Works with the SDs and the PMO to oversee the tracking of projects to meet HL7 objectives. The Steering Divisions will function to assure that they or the committees under them set milestones, monitor and ensure that quality assurance has been done
  • Performs top-level review and authorizations as specified in the formal development process:
    • Working with the SDs, reviews, approves, and prioritizes requests for new projects.
    • Working with the SDs, recommends project probation or dissolution to the Board
    • Sets remit for ARB and Project Management Office and serves as escalation point for issues not resolved at the committee or SD level.
    • ensures that quality checks in the project development process are satisfied.
    • Reviews and approves requests from Technical Committees to initiate a ballot and serves as escalation point for ballot response handling.

Provides a Coherent Architecture and Development Process

Establishes (or reviews) the Technical Architecture, the development methodologies, and the work processes to be used by the WG in developing HL7 consensus-based standards specifications
  • has overall responsibility for the development and adherence to an HL7 Technical Architecture and the development, maintenance, and execution of an HL7 standards development process
    • working through SDs, makes sure that architecture and process is developed, communicated (documented, etc), maintained and enhanced.
      • through Committees such as MnM, Vocabulary, and PIC as well as the ARB.
  • defines and manages international harmonization mechanism
  • ensures that the balloting of any HL7 specification, or portion thereof, is carried out in accordance with HL7 Bylaws and ANSI rules.
  • holds ultimate responsibility for harmonization of committee work products. Harmonization is the process whereby the various shared models of the HL7 Technical Architecture, are defined for common use by the HL7 Working Group and for use between collaborating SDOs. The harmonization process must consider the requirements of the HL7 architecture, the need for sharing and re-use, and the requirements of the various domains of use. The tasks of the Technical Steering Committee will include:
    • to define the principles under which harmonization activities should operate;
    • to lay out the general processes to be followed;
    • to assign responsibility for the carrying out each harmonization area to a specific committee or project within the Working Group; and
    • to monitor and act as the focus for appeals to the process.

Oversees the Technical Operations of the Working Group

Assures that the WG works smoothly together and covers the work scope in a consistent manner.
  • Ensures that Working Group policies and procedures and bylaws are followed
    • With the SDs, oversees execution of procedures for committee creation, dissolution, and co-chair elections.
    • ensures that meetings and calls are carried out according to policy
  • Oversees continuous quality process
  • Works through SDs to identify cross-domain and cross-function gaps, overlaps, discrepancies, potentials for collaboration, and conflicts and recommends resolution
  • responsible for any official interpretation of the HL7 standards.
    • resolves conflicts within the Working Group and prioritizes resources according to project priority (example, room balancing at WGMs)
    • ensures the impartial handling of substantive and procedural

complaints regarding any action or inaction as related to the production of HL7 specifications.

Primary Communication Vehicle for the Technical Operations of HL7

Serves as technical authority of HL7, communicating status and guidelines regarding standards and operations.
  • serves as technical escalation point for any questions related to the technical operations of HL7
  • reports to the Board, the WGM, and the membership on Technical operations news, status, and issues as appropriate
  • responsible for any official interpretation of the HL7 standards.

Composition

The T3F spent several meetings deliberating the appropriate composition and style of functioning for the Technical Steering Committee. This section reflects the results of those discussions, and addresses three topics:

The order of these topics is arbitrary and the discussion will, of needs, include both forward and backward references. The T3F did not attack any of these topics de novo. In every circumstance, we built on the guidance provided by earlier Strategic Initiative, ORC and Transition documents. We sought to recognize the principles and objectives that underlay each of those documents and to maintain those principles and objectives while improving, we hope, the resulting framework.

HL7 Committee Structure

The HL7 Working Group is made up of a number of volunteer-driven Committees and SIGs that have been highly successful, to both their own and to HL7's credit and benefit. Simultaneously, however, as the numbers of groups expanded, their breadth, number and diversity posed major challenges for coordination and collaboration between them. Discussion and debate on such issues in the forum of the previous Technical Steering Committee (TSC) became difficult and unproductive in recent years, and failures in coordination have begun to threaten the effectiveness of HL7.

The challenge of the Strategic Initiative was to address these coordination and collaboration issues while retaining the essential vitality of a Working Group made up of and driven by the best, brightest and most dedicated medical informaticists and information scientists available. The essence of the Strategic Initiative proposal was to revise the leadership of the Working Group from a single TSC with representation from each Committee and SIG to a two-level hierarchy of a Technical Steering Committee (TSC) and a small set of Steering Divisions (SD, a new term). This was the foundation from which the T3F developed this proposal.

The starting point for this discussion was a previously developed Strategic Initiative document titled "Creation of the Transitional Technical Task Force (T3F)". The final proposal can be summarized with the "nested list" of bullet points at the end of this paragraph. The remainder of the topics in this "HL7 Committee Structure" section discuss the rationale and principles behind this proposal, specific responsibilities of the TSC and SDs, and the definition and committees in each Steering Division. The proposed hierarchy is:

  • Technical Steering Committee -
    6 elected voting representatives, 4 appointed voting members
    TSC-elected Chair
    • Foundation & Technologies Steering Division
      9 existing TCs and SIGs
      2 Elected SD Co-Chairs plus Co-Chairs of TCs & SIGs in SD
    • Structure & Semantic Design Steering Division
      10 existing TCs & SIGs
      2 Elected SD Co-Chairs plus Co-Chairs of TCs & SIGs in SD
    • Domain Experts Steering Division
      17 existing TCs and SIGs
      2 Elected SD Co-Chairs plus Co-Chairs of TCs & SIGs in SD
    • Technical & Support Services Steering Division
      9 TSC-appointed Committees (7 formerly Board-appointed, 2 new)
      2 Elected SD Co-Chairs plus Co-Chairs of Committees in SD

Organizing Principle

During its deliberations, the T3F made the following observations:

  • HL7 members join committees because of their personal (or corporate) interest in the subject matter content of the committee, regardless of whether their interest stems from academic, development or implementation activities.
  • The original break-out of committees (provided in the SI document) aggregates the committees by commonality of what they produce and the relationship of that work product to the other Working Group committees. The T3F found this is to be a sound approach.
  • One of the key activities of the TSC will be to identify and reduce those places where committees are "stepping on each others toes" or "reinventing the wheel." Coordination within the proposed Steering Divisions will facilitate this activity.
  • The existing relationship between TCs and SIGs may need to be "re-thought", because the Steering Division strategy will clearly place a number of SIGS in a Steering Division that is different from that to which their current "parent TC" is assigned.
  • It will be important to not disrupt existing collaboration while establishing this organization, and it is clear that many topics may best be managed, in "matrix fashion" between committees in two or three Steering Divisions.
  • A number of committees clearly produce products that fit in two or even three of the Steering Divisions. This may be effective, or it lead the TSC to consider whether to recommend these groups be split.

Ultimately, the T3F recognized that the organization as proposed is imperfect, not by design, but by the nature of the HL7 Committees and SIGs that do not permit simplistic classifications. Regardless of what is proposed, someone will question the result. The key element however is to establish the three-tier structure first, gain the advantages of focusing critical organizational thinking into smaller meetings so that the work can get done, and then evolve the structure over time.

Technical Steering Committee Role

The Technical Steering Committee (TSC) will be the focal point for decision making, harmonization, issue resolution, project and committee creation and dissolution within the Working Group. The TSC will be a representative consensus body of elected and appointed members. (Specifics are in a later section of this document.)

The T3F notes that however the Steering Divisions are defined, and whatever additional relationships may exist between committees, the Technical Steering Committee will not be successful in meeting HL7's objectives unless it can assure the harmonization of content and design across HL7 standards.

As a consequence, the notion of required harmonization and shared stewardship must clearly be a fundamental principle of the TSC, of the Steering Divisions, and of each TC and SIG. Overall, it is the TSC that must define and manage the processes that bring about such harmonization and then must delegate similar responsibilities to the Steering Divisions and to the committees.

Further, the TSC must have a central role in project management. It is assumed that the project life cycle strategy being developed will be a fundamental process for all HL7 work. The TSC will incur responsibilities:

  • to approve projects (after they are vetted in the Steering Divisions)
  • to initiate projects to carry out its mission (such as harmonization)
  • to oversee the functions of the Project Management Office, and
  • to maintain the project life cycle definition

Certainly, several of these responsibilities will need to be delegated in whole or in part to the Steering Divisions or to specific committees.

Steering Division Definition and Composition

In keeping with the original Strategic Initiative document, T3F proposes to divide the existing Technical Committees, Special Interest Groups and Board-appointed Committees into four functional groups called Steering Divisions (SD). Each Steering Division will be a committee in its own right made up of the Co-Chairs of the groups in the SD. It is expected that each SD will meet face-to-face during each Working Group Meeting and will conduct conference calls, as needed. A partial list of specific SD responsibilities includes:

  • nominate and elect the representative from that SD to the TSC, who will also serve as a Co-Chair of the SD
  • nominate and elect an Alternate representative to the TSC, who will also serve as a Co-Chair of the SD
  • review proposed projects and make recommendations for action to the TSC
  • monitor project status within the SD
  • review proposals to create, modify or dissolve Committees and SIGs in their SD and make recommendations for action on same to the TSC
  • identify coordination issues within and between the committees of the SD and resolve these or recommend resolutions to the TSC
  • identify coordination issues between SDs and their committees and recommend resolutions to the TSC
  • undertake harmonization tasks as delegated by the TSC
Foundation & Technologies Steering Division

Committees and projects in this space focus on providing the fundamental tools and building blocks that other Committees should use to build the standards, and upon the technology infrastructure that implementers of HL7 standards must manage.

  • Implementable Technology Specifications (ITS)
  • IMplementation/Conformance
  • Infrastructure & Messaging
  • Modeling & Methodology
  • RIM-Based Application Architecture: RIMBAA (formerly Java)
  • Security
  • Service Oriented Architecture (SOA)
  • Templates
  • Vocabulary
  • Related multi-committee projects:
    • Dynamic Model
    • Harmonization
    • HL7 TermInfo
Structure & Semantic Design Steering Division

Committees and project in this space focus on creation of basic patterns and common messages that could exist on their own, but are mostly used by others.

  • Arden Syntax
  • Clinical Context Object Workgroup (CCOW)
  • Clinical Decision Support
  • Clinical Genomics
  • Clinical Statement
  • Electronic Health Record (EHR)
  • Financial Management
  • Orders & Observations (OO)
  • Patient Administration
  • Personnel Management
  • Scheduling & Logistics
  • Structured Documents
  • Related multi-committee projects:
    • Common Message Element Types (CMETs)
Domain Experts Steering Division

Committees and projects in this space focus on creation of messages, services, documents using many of the common structures in place, yet expanding it in key areas as well.

  • Anatomic Pathology
  • Anesthesiology
  • Attachments
  • Clinical Interoperability Council (CIC) voice only - no vote
  • Child Health (formerly Pediatric Data Standards)
  • Community Based Collaborative Care (CBCC)
  • Emergency Care
  • Government Projects
  • Health Care Devices
  • Imaging Integration
  • Laboratory
  • Patient Care
  • Patient Safety
  • Pharmacy
  • Public Health Emergency Response (PHER)
  • Regulated Clinical Research Information Management (RCRIM)
Technical & Support Services Steering Division

These committees are currently Board-appointed. In future, the T3F recommends that they be appointed by the TSC, subject to Board approval. The committees will elect their own Co-chairs, subject to TSC approval. For the most part, these groups are functioning on efforts of volunteers who accepted a board request (past) or will accept a TSC request (future) to take on these responsibilities in collaboration with the designated staff liaison. Because these groups were not members of the previous TSC, they had no voice in TSC decisions, even though they were working alongside the volunteers in the other groups. Thus, the addition of these committees to a Steering Division provides those volunteers equal voice (and responsibilities) in the TSC affairs.

The primary feature of these committees is that their projects and products provide direct support to the Technical Committees and SIGs of the Working Group and thereby enable the Working Group to function efficiently.

  • Education
  • Electronic Services
  • International Mentoring Committee (voice only, no vote)
  • Marketing Committee
  • Process Improvement Committee (PIC)
  • Project Services -- a new group that will take responsibility for the Project Life Cycle and will serve as the primary support for the PMO
  • Publishing
  • Tooling
Architecture Review Board

The T3F believes the Architecture Review Board (ARB) fulfills a critical mission that must continue under the TSC. To that end, the T3F is proposing that the ARB become a TSC-appointed committee that "stands alone" (independent of the Steering Divisions), and (see below) that the ARB have a voting representative on the TSC. Normally this representative will be the ARB Chair, but in the circumstance that the ARB Chair is already a member of the TSC, a different ARB member will also be named to the TSC.

Maintaining Open Communication with TSC Constituent Committees

The structure of the TSC threatens to isolate the Technical Committee and SIG leadership to discussions in only a single Steering Division, whereas, under the previous TSC, communication and collaboration occurs across a variety of committees with no established barriers. In order to avoid such isolation, the Technical Steering Committee should establish procedures such that:

  • even though the Steering Divisions have the first-level responsibility for coordinating the activities within their divisions, all proposals for new or changed Projects and all proposals for new or changed committee status should be shared with the members of all Steering Divisions as soon as the proposal is released for review by any SD. This will allow cross-SD comment and the opportunity to seek modifications in proposals before they have been formally adopted at an SD.
  • at each WGM, the TSC should hold a Technical Steering Committee Plenary Meeting of all of the Co-chairs. This session should be chaired by the TSC Chair. In addition to "TSC Retreat" style presentations the plenary should include an "open mic" period during which individual Co-chairs can present concerns and issues. The plenary would hear a brief presentation of the issues, and accept a written form of the issue (similar to a ballot comment). The TSC should then have the obligation to acknowledge all issues, assign them to an SD or other group for response/action, and assure that the issue is indeed addressed or responded to by the assigned group.

Composition and Functioning of TSC

The makeup of the proposed Technical Steering Committee is illustrated in the following chart. It includes ten voting members -- six elected representatives, two Board-appointed positions (the CTO and a liaison), and up to two TSC-appointed positions. It also has a non-voting secretary, to be assigned by HQ, and other staff support positions. Specifics of the election processes, terms, etc. are in following sub-sections.

TSCComposition.png

TSC Membership

Steering Division Representatives

Each of the four Steering Divisions (SD) will have an elected voting Representative on the TSC. Further, each SD will elect an Alternate Representative who is authorized to attend TSC meetings and vote in the event the elected Representative from that SD is unable to participate. This assures strong, consistent representation from each SD. In addition, the primary and alternate representatives will serve as Co-Chairs of the Steering Division itself.

The election process for SD Representatives is patterned after the process used in 2006 to elect the T3F representatives:

  1. During a nomination period of at least 30 days, nominations for representatives of the SD will be accepted from the Co-Chairs of the Committees and SIGs that make up the SD.
  2. The nominees are expected to be individuals who are either current Co-Chairs or a past Co-Chair of one of the Committees or SIGs in the SD. Effective service on the TSC will require such experience. Nominees should be prepared to commit at least two hours a week to the TSC, if elected.
  3. HL7 staff will contact nominees to verify their willingness to stand for election, and to solicit a brief nominees "statement" for distribution.
  4. Individuals who are nominated to represent more than one SD will be asked to choose which nomination they wish to accept, and must reject the other(s).
  5. An election period of at least 30 days will follow the nomination period. The votes will be cast by the Committees and SIGs in the SD, using their normal decision-making practices.
  6. Each Committee will cast votes for two of the candidates, and will be asked to state a preference for one of the two as their primary representative. (This preference will be tallied only if there is a need to resolve a tie.)
  7. The candidate receiving the most votes will be named the Representative for that Steering Division. The candidate receiving the next higher number of votes will be named the Alternate Representative for that SD. Both the first and second place candidates will be named Co-Chairs of the SD.
  8. Tie votes will be resolved by tallying the primary representative preferences for the candidates involved in the tie. If tally also results in a tie, the decision will be made by drawing lots, unless one of the candidates involved wishes to defer to the other(s).
Affiliate Representatives

Two Affiliate Representatives will be elected by the "global" HL7 Affiliates -- the "traditional" affiliate organizations plus the US affiliate. (During the initial election, the HL7 Board is requested to designate a consensus body to nominate and cast votes for the US Affiliate.)

The election process for Affiliate Representatives is:

  1. During a nomination period of at least 30 days, nominations for Affiliate Representatives will be accepted from the affiliate organizations.
  2. Nominees should be prepared to commit at least two hours a week to the TSC, if elected.
  3. HL7 staff will contact nominees to verify their willingness to stand for election, and to solicit a brief nominees "statement" for distribution.
  4. An election period of at least 30 days will follow the nomination period. The votes will be cast the Affiliates, using their normal decision-making practices.
  5. Each Affiliate will vote for one or two of the candidates, depending upon how many Affiliate Representative positions are being filled in that election. (See discussion of member terms, below.)
  6. The one or two candidate receiving the most votes will be named the Affiliate Representative(s), depending upon how many positions are being contested.
  7. Tie votes will be resolved by drawing lots, unless one of the candidates involved wishes to defer to the other(s).
Representative Election Timing

In order to assure the greatest diversity and balance of the representatives on the Technical Steering Committee, the election of Representative Members will be phased, with the Election for Steering Division Representatives coming first, election of Affiliate Representatives second, and appointed TSC members being designated last. These periods may overlap, but the nominations for Affiliate representatives should start after the slate of candidates for SD representatives has been established, and Affiliate representative elections should commence only after the SD elections are complete.

Board-Selected Members

The HL7 Board of Directors will select or appoint one members to the Technical Steering Committee.

  1. The Chief Technology Officer who will hold an ex officio voting position on the Technical Steering Committee.
Technical Steering Committee-Appointed Members

The Technical Steering Committee will also appoint two members to the TSC. They are:

  1. An Architecture Review Board (ARB) Representative. The T3F believes that the ARB fulfills a vital "independent" role in HL7 and should have voting representation on the TSC. Normally this representative will be the ARB Chair, but in the event that the Chair is already a TSC member, or declines to serve, another ARB member will be selected.
  2. An ad hoc TSC-Appointed Member will be appointed on a variable term, not to exceed two-years, based on requirements or needs for balance or expertise that the Technical Steering Committee may from time to time identify. This will be a voting position.

Membership Terms

All normal membership terms on the Technical Steering Committee shall be for two years, and will run on a calendar year basis. (See exceptions, below). There are no term limits, members may serve successive terms.

Technical Steering Committee Elections should be held between the "Spring" and "Fall" Working Group Meetings each year, for candidates who will take office in January of the following year. Each year, representatives for two of the four Steering Divisions will be elected as will one of the two Affiliate Representatives. The appointed positions do not need to be staggered.

Vacancies

In the event that a member must resign from the Technical Steering Committee, the following procedures shall be used to fill vacancies:

  1. For SD Representative positions, the Alternate Representative will be designated to serve the remainder of the vacated term, and the Alternate position will be re-filled in the next election cycle.
  2. For Affiliate Representative positions, the Affiliate Council will be asked to name an individual to serve the remainder of the vacated term.
  3. For the Board Liaison and the ARB Representative appointed positions, the appointing body will be asked to fill the vacated position as soon as possible. The initial term of the replacement appointee will run until the second year-end following the appointment.
Term Exceptions

The following exceptions exist for the two-year, calendar-term rule above:

  1. The CTO holds a standing ex officio membership, and therefore that TSC term is dependent upon the term of service as CTO.
  2. The term of ad hoc TSC-Appointed Member will start when the TSC makes the appointment and will end as determined by the TSC, but cannot exceed two years.
  3. During the summer of 2007, elections are planned for all six elective positions. In order to establish staggered terms, two of the four elected SD representatives and one of the two elected Affiliate representatives will be designated to serve an initial "half-term." This designation will be determined by drawing lots.
  4. Because of the desire to have the TSC start functioning in September 2007, the initial terms of the elected and appointed members will be extended by to cover the period from September 16, 2007 through to the nominal start of their terms on January 1, 2008.

Election of Technical Steering Committee Chair

The Chair of the Technical Steering Committee will be elected by the Technical Steering Committee itself. The Chair shall be selected from the voting members of the TSC. There will be no formal designation of a Co-Chair or Vice-Chair for the Technical Steering Committee. The Technical Steering Committee can take whatever steps it wishes to assure coverage when the Chair is unavailable for a particular meeting, including, if it wishes, naming a standing Vice-Chair.

TSC Chair as Member of HL7 Board

The elected TSC Chair be an ex officio voting member of the Board, just as the Technical Chair has been in the past. This enables the Board to become a strategic body and defer tactical activities to the CEO, CTO, etc. If the TSC Chair is an active member of the Board, it helps communications in both directions. Even though the Board will be strategic, it still holds full responsibility for HL7's success and the TSC must act to assure that success, and by the nature of its duties, the the TSC will be making Strategic technical recommendations that must be properly represented and understood at the Board.

Term of Office

The Chair will be elected for a two-year term of office, regardless of how long the candidate's membership term has left to run.

In the not unlikely event that the term of office runs longer than the Chair's term as a member, the TSC may use its "TSC-Appointed" position to extend the Chair's membership, or may petition the Board to temporarily expand the TSC membership to allow the Chair to serve out the term of office.

The Technical Steering Committee should seek to establish Chair terms of office that run on a calendar basis. As with regular terms, the term of the initial TSC Chair shall be extended to cover the period from September 16, 2007 through December 31, 2007.

Decision making and delegated decisions

By and large, decisions of the Technical Steering Committee will be made by vote. There are however, tactical decisions, such as approvals for ballot, exceptions to ballot rules, etc. that have, in the past, been assigned to the Technical Chair of HL7 as part of HL7 By-laws or Policies. Such decisions should be assigned to the CTO, using the individual SDs and committees as resources, with the TSC providing a venue for appeal of such decisions.

Relationship of TSC to CTO

In the course of its deliberations, the T3F paid particular attention to the role of a Chief Technical Officer (CTO). Ultimately, the T3F came to the conclusion that the relationship between the CTO and the TSC should mirror the relationship between the CEO and the Board of Directors each acting assure the success of the other.

This decision was predicated on the assumption by the T3F that the TSC would participate in the Board's selection of the CTO and that the following principles will be applied in making a CTO selection, in priority order:

  1. A proven consensus builder
  2. Someone who knows and is known to the HL7 Working Group
  3. Likely to have been a Co-Chair or “facilitator”, but not necessarily required
  4. Have a strong understanding or working knowledge of the technology that HL7 defines and is dependent upon.

In that context, the following motion was unanimously adopted by the T3F.

T3F Motion Unanimously Adopted April 3, 2007

WHEREAS:

  • The task of over-seeing and coordinating the technical activities of Health Level Seven requires the full-time attention of a knowledgeable professional, "Technical Officer";
  • The effective coordination of the various committees and SIGs requires a restructuring of these into three or four sub-groups reporting to an elected Technical Steering Committee;
  • The Technical Steering Committee must assure the continued involvement and support of HL7's Core Resource - volunteer-driven Working Group; and
  • The success of the Technical Steering Committee and the success of the "Technical Officer" are inextricably intertwined, and, further, are essential to HL7's success;

THEREFORE, the Transitional Technical Task Force RESOLVES to recommend:

  • The "Technical Officer" should be recruited to work with and support the Technical Steering Committee in its responsibilities to oversee HL7's technical activities;
  • The "Technical Officer" should report to the CEO and the HL7 Board, and should be a voting member of the Technical Steering Committee.
  • The Chair of the Technical Steering Committee should be be elected by the voting members of the Technical Steering Committee, and selected from within the members of the Technical Steering Committee.
  • The Technical Steering Committee and its Chair should delegate responsibilities and operational decision-making (to be defined later) to the "Technical Officer."
  • The Technical Steering Committee should have a role in recruiting and evaluating the "Technical Officer."

Relationships

Clearly, the central role that the Technical Steering Committee will play within HL7 demands an understanding of the relationships of that group to the rest of HL7. To this end, the T3F has created the following chart.

TSCRelationships.png

The Technical Steering Committee (TSC) and its four Steering Divisions (SD) are shown in relationship to the Board of Directors (BOD) on the right. The TSC and SDs make up the "Working Group" of HL7, and the relationships between them are discussed in earlier sections of this document.

The left hand portion represents the employees of HL7 and the Staff of AMG, and these relationships are shown for example here and are not considered further in this report.

The committees and SIGs that make up three of the four SDs are entirely made up of volunteers and are formed by petition to and approval of the TSC. The fourth SD, the Technical & Support Services Steering Division (ST on the chart) is made up of committees appointed by the TSC, chaired by a volunteer, but made up of a mix of volunteers, employees and staff. Hence, they sit on the boundary between the Employees and Volunteers, as do the Board-appointed committees.

The most critical concept exposed by this chart, is that the TSC, SDs and committees on the right, and the Staff and Employees on the left cannot be successful in their endeavors without robust productive collaboration between them. HL7 has always been fortunate to have minimal contention and maximum cooperation between its employees, staff and volunteers, and this T3F report is predicated on the continuation of that relationship.

Decision Making Practices

The decision making practices of the TSC have been moved to a separate document. (2007-09-18)

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.