|
|
| (4 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | ==HL7 Technical Steering Committee (TSC) == | + | ==HL7 Technical Steering Committee (TSC) Decision-making Practices (DMP) == |
| | | | |
| | ===Decision-making Practices Document (DMP), Version [2]=== | | ===Decision-making Practices Document (DMP), Version [2]=== |
| − | See MS Word version available at [http://hl7projects.hl7.nscee.edu/docman/view.php/52/1083/TSC%20DMP%2020090126.doc] | + | See MS Word version available at http://www.hl7.org/Library/Committees/tsc/TSCDMP20100222_approved.doc, Last updated 2010-02-22 |
| | | | |
| − | This document was separated from the [[HL7 Technical Steering Committee|over-all TSC definition document]] to allow its amendment and adoption by the TSC.
| |
| | | | |
| − | This document defines the decision-making practices of the Health Level Seven (HL7) Technical Steering Committee (TSC), also referred to as “Work Group”. The TSC will adhere to a set of decision-making practices that ensure consensus, openness, and balance of interest . The practices as outlined in this document are designed to enable timely decision-making, balanced with an earnest attempt to ensure that input from all affected parties is considered. The decision-making practices are intended to govern the standard operating procedures of the TSC, and are not intended to conflict with rules governing ballot procedure as defined by ANSI and the HL7 Governance and Operations Manual (GOM).
| + | ====Revision proposed for 2010-12-13: ==== |
| | + | Link to Generic DMP v3.0 at http://www.hl7.org/Library/Committees/pi/Generic_HL7_WG_DMP_v3.0_Template_approved.doc |
| | | | |
| − | In the event of joint meetings, the DMP of the host Work Group shall be the governing document.
| + | Customizations needed for TSC: |
| | + | Removed 2.a, b, c, f, g |
| | + | <br/> |
| | + | *added 2.1 on participation |
| | + | **opportunity to speak only guaranteed for members |
| | + | **guests are otherwise regarded as observers |
| | + | *changed 2.2.c observers shall not cause distractions, may seet attention of chair if wish to comment on agenda topic and shall not otheriwse participate in deliberations |
| | + | *changed 2.3 |
| | + | **deleted 2.3.a scheduled conference calls may be attended by persons registered on the list server (not applicable for closed membership group) |
| | + | **added 2.a guests may petition chair to become observers, announce their presence, rules of courtesy |
| | + | **customized 2.3.b to include permalink to TSC Wiki |
| | + | *3.a.iii updated URL for TSC Wiki |
| | + | *3.2.1.b changed to reflect TSC Retreat preliminary agenda |
| | + | *5 notes Specific quorum of chair plus five voting members including two steering divisions |
| | + | **5: should the Chair be counted as the co-chair representing his/her constituent in the event no other cochairs of that constituent are present? |
| | + | **5 b) deference of decisions if key stakeholders not present ''deleted'' as Roberts rules provide for tabled motion |
| | + | **5.1.b deleted for direction setting |
| | + | **5.2.b cannot have more than one presiding co-chair (cannot switch from Austin to John Quinn and back, etc) |
| | + | **5.c: WGM where elected TSC member vote cannot be represented should elect ad-hoc. |
| | + | *6.3 changed based on closed membership |
| | + | **6.f preponderance of influence deleted |
| | + | **6.1.d removed - no ballot reconciliation |
| | | | |
| | | | |
| − | '''1. Work Group meetings are open to all interested parties.''' <br>
| |
| − | :Meetings of the Work Group are open to everyone to ensure that viewpoints of all affected parties have an opportunity to be shared and considered. Everyone will be given an opportunity to speak; however, the chair may limit discussion on topics deemed to be non-constructive. Depending on the purpose or mode of the meeting certain participants are expected to attend. Other HL7 members may be asked to attend to provide specific input regarding a particular issue. The following list identifies expected participation by meeting type. All Work Group meetings are open; this list simply identifies anticipated participants.
| |
| − | :* <u>Scheduled conference call meetings</u> are attended by persons registered on the TSC list server (i.e. tscadmins@lists.hl7.org). Persons not subscribed to the Work Group list may still attend, however, all meeting announcements, minutes, and other notices will be sent to the list and posted to the TSC’s Wiki page. Therefore anyone expecting to participate is encouraged to join the list so that the Work Group can communicate with them..
| |
| − | :* <u>TSC Meetings during Working Group Meetings</u> may be attended by any working group meeting attendee. Participants are asked to introduce themselves and identify the nature of their affiliation with HL7.<br><br>
| |
| − | '''2. Meeting Notification.'''<br><br>
| |
| − | :All activities will be conducted in a public light with efforts made to ensure ample notification of those interested. The TSC shall utilize two key mechanisms to notify the interested parties of its activities: the TSC<nowiki>'</nowiki>s listserv and Wiki page(s). The listserv (and/or Wiki) will be used predominantly for discussion threads, notifications, and draft documents; whereas the wiki page will be used predominantly for final documents and document resources (decision documents, minutes, papers, etc.). <br>
| |
| − | :Any use of the terms '''post''', '''posted''', or '''posting''' refers to notification subject to these constraints.
| |
| − | <br><br>
| |
| − | :Minutes and Agendas: [[TSC_Minutes_and_Agendas]] <br>
| |
| − | :CCYY-MM-DD TSC WGM Agenda City<br>
| |
| − | :CCYY-MM-DD TSC WGM Minutes City<br>
| |
| − | :CCYY-MM-DD TSC WGM Actions City<br>
| |
| − | :CCYY-MM-DD TSC Call Agenda<br>
| |
| − | :CCYY-MM-DD TSC Call Minutes<br>
| |
| − | :CCYY-MM-DD TSC Call Actions<br><br>
| |
| − | '''3. Notification of meetings and the intended agenda is provided prior to the meeting.''' <br><br>Binding decisions can be made only at meetings with the required advance notification; only recommendations and non-binding decisions can be made at special purpose meetings.<br><br>The chair of the TSC shall make every attempt to ensure that all parties with an interest in agenda topics are made aware of the meeting time and location subject to the documented notification requirements. As appropriate, TSC activities will be cross-posted to other HL7 Wiki sites, depending upon the topic and type of meeting as indicated in the following list. Certain meetings are subject to Bylaws guidelines for notification. Please refer to the Bylaws for additional information.<br>
| |
| − | #* <u>Working group meeting agendas</u> are posted in the meeting brochure. A preliminary agenda is developed by Wednesday of the prior working-group meeting and posted with the minutes within 2 weeks. The preliminary agenda is finalized on a scheduled conference call two weeks prior to the working group meeting and posted within 2 business days. Recognizing the dynamic nature of working group meetings, the agenda may require updates. Notification will be satisfied so long as at least two of the following venues are used:
| |
| − | #** <u>E-mail notification by 6:00 pm local time the evening before the event</u>
| |
| − | #** <u>Notification on the bulletin board (near the registration desk) at least 2 quarters prior to the event</u>
| |
| − | #** <u>Announcement in the general session or lunch session prior to the event</u>
| |
| − | #* <u>Scheduled/Periodic telephone conference call meeting agendas</u> are to be posted no later than 24 hours prior to the call. Preliminary agendas are to be determined at the close of each teleconference.
| |
| − | #* The agenda, for either a conference call or working group meeting, will include the purpose of each topic, anticipated discussion time and whether it is intended to set direction or to make a decision.
| |
| − | #* Should the TSC require <u>action between scheduled meetings</u> there are two alternatives. First, a Special Purpose Meeting may be called as defined in the Bylaws (Section 11.04), which requires 30 days notice. Alternatively, the issues may be discussed as an informal group, bringing forward recommendations to the list or as a discussion topic for the next regularly scheduled TSC meeting. Recommendations by the informal group are not binding decisions until acted upon by the TSC.<br><br>
| |
| − | #'''Decisions made at TSC meetings are recorded in meeting minutes and posted.'''<br><br>Minutes are recorded and posted for all TSC meetings including the date, time, and location of the meeting, a list of attendees, the intended agenda, a brief summary of discussion topics, and the outcome of proposals made (including vote tallies if votes were taken).<br><br>Minutes from a working group meeting will be posted no later than 2 weeks of the last day of the conference and in compliance with HQ deadlines; minutes from a conference call will be posted within one week of the call.<br><br>
| |
| − | # '''Decisions made at non-working group meetings (conference calls and special purpose meetings) are summarized during the next working group meeting.'''<br><br>In the interest of facilitating good communication among the TSC members, those decisions that were made between working group meetings will be summarized and available at working group meetings. This communication will contain, at a minimum, abbreviated summary of the issues involved and the decisions made by the TSC. Any TSC decisions are subject to the practices documented elsewhere in this paper.<br><br>
| |
| − | #. '''Quorum for TSC meetings: For decision making, the chair (or designate) and at least five other TSC members must be present, including at least two of the four elected Steering Division representatives (or their alternates) . For direction setting, the chair (or designate) and at least four TSC members must be present.'''<br><br>Attendance for all meetings is recorded in the meeting minutes, including the participant name and constituency they represent. The recorder for the meeting is responsible for ensuring minutes are taken and posted. Due to the balanced makeup of the TSC, "Preponderance of Influence" is not viewed as a substantive issue for the TSC. The chair may cast a vote as a tie-breaker.<br><br>In all circumstances, the TSC can have no more than one presiding chair. All other TSC members, act as regular voting members when not presiding. Unlike other HL7 technical committees or SIGs with multiple co-chairs, the chair shall not change within the course of a given meeting.<br><br>Although any issue may be discussed within TSC meeting venues at any time, binding actions cannot be taken without sufficient notification and quorum. Absence of either of these conditions allows the TSC to issue recommendations that must subsequently be ratified by the TSC subject to satisfying constraints placed upon binding decisions.<br><br>
| |
| − | # '''Decisions made by the Technical Steering Committee are reached using a simple majority vote. The TSC will always strive for consensus in decision-making.'''<br><br>While decisions are made by simple majority vote, the TSC shall endeavor to make its decisions via a consensus process. For a decision to be called consensus, it must receive two-thirds (66%) majority support. While determining if consensus is being reached, a variety of techniques may be used informally to assess the position of the group, including but not limited to straw poll, Robert<nowiki>'</nowiki>s Rules of Order, seeking response to a hypothetical opposing view, and polling each participant to voice their position on the issue.<br><br>When formal votes are taken appointed or elected TSC members shall always receive a vote. For non-binding decisions only, all meeting participants may have the opportunity to vote at the discretion of the chair.<br><br>Once voted, quorum is revisited to adjust for abstentions. Quorum must be met across yeah-s and neah-s for the vote to carry.<br><br>It is recognized that revisiting previously made decisions inhibits TSC progress and should be discouraged. That said, circumstances might exist that warrant re-opening of discussion on a previously visited issue. To dissuade this practice, such re-opening requires a formal motion, second, and simple majority affirmative vote of the TSC as subject to the quorum rules in this document; however, in order for the decision to be considered binding, advance notification, as defined in this document, is required<br><br>
| |
| − | # '''TSC Members unable to participate in TSC activities in person may <u>not</u> do so by proxy.'''<br><br>The Technical Steering Committee does not recognize voting by proxy. There is ample opportunity to support or oppose proposals under consideration through TSC Wiki discussions, email and conference calls. If a member feels strongly enough about a particular topic to want consideration by the TSC, that member shall be present for the topic to be considered. The chair will be sensitive and considerate in attempting to accommodate schedules to ensure the member can be present at the appropriate venue.<br><br>'''Note:''' The four TSC members who serve as Representatives of a Steering Division each have an elected Alternate Representative who can attend and vote in TSC meetings when the primary Representative is unable to attend. '''Votes by Alternate Representatives are not deemed to be ''proxy'' votes.'''<br><br><u>Statement of Position</u>. Those HL7 members wishing to establish a position on a topic under consideration by the TSC in writing may do so subject to the notification requirements below. Statements of Position received prior-to or during the meeting will be shared by the chair as part of the discussion on the related topic. The chair has the responsibility to voice and represent these positions during relevant discussion, though they are not under obligation to support or defend them. These statements do not carry the weight of a vote and are included as informational items only for consideration by the TSC. All Statements of Position received in electronic form will be included as attachments to the minutes.<br><br>
| |
| − | # '''The TSC shall rely upon Robert<nowiki>'</nowiki>s Rules of Order in the event that formal guidance is needed or requested.'''<br><br>The TSC intends to ensure the effective and active engagement of all participants. To ensure fair and just participation, the TSC shall follow its documented decision-making practices, falling-back upon Roberts Rules of Order in the event of a question or concern. Since Robert<nowiki>'</nowiki>s Rules of Order provides formalism for addressing almost all matters of process, this provides a "backup mechanism" of formality in the event that it is required.<br><br>It is the responsibility of the chair to guide the TSC to an efficient and effective outcome. The TSC shall follow, in this order of precedence, these Decision-making Practices (which cannot conflict with HL7 Policies and Procedures or the HL7 Bylaws), HL7 Policies and Procedures, the HL7 Bylaws, and Robert<nowiki>'</nowiki>s Rules of Order. TSC-established decision-making practices can refine the HL7 Policies and Procedures and Bylaws so long as they remain in accordance with those documents.<br><br>In the event that an issue arises where formality is required and other guidance exists, Robert<nowiki>'</nowiki>s Rules of Order shall take precedence. This provides a "common denominator" to keep in-check the power of the chair and to confirm the rights of all TSC members.
| |
| | | | |
| − | ===Quorum Examples===
| + | '''Comment from T3SD meeting 20101206 '''- need more specific language on expectations of Co-Chairs and Representatives whether they are expected to canvass their Steering Division to ensure they accurately represent their constituency, or cast votes based on their own thought leadership endorsed by their constituency. |
| | + | |
| | | | |
| − | Based upon PIC<nowiki>'</nowiki>s Decision Making Practices Document version 1.3, adopted December 1, 2003.
| |
| | | | |
| − | # Simple scenario<br>''6 persons, including two elected Steering Division representatives , attend a meeting, including the chair (or their designate).''<br><br>Quorum is established and the TSC can conduct its business as usual. All participants are eligible for voting;<br><br>
| |
| − | # Tie scenario<br>''6 persons, including two elected Steering Division representatives,attend a meeting, including the chair (or their designate).''<br><br>Quorum is established and the TSC can conduct its business as usual. In the event of a tie this will not constitute a consensus decision, because the consensus majority (66%) criterion has not been met.<br><br>
| |
| − | # Non-representative scenario<br>''6 persons, not including two elected Steering Division representatives, including the chair (or their designate).''<br><br>Quorum is not established and the TSC cannot conduct official business, because two members representing a Steering Division are not present.<br><br>
| |
| | | | |
| | Below is a quick reference for meeting configurations. (Note: this table does not have a direct correlation to the scenarios above.) . | | Below is a quick reference for meeting configurations. (Note: this table does not have a direct correlation to the scenarios above.) . |
| Line 56: |
Line 45: |
| | |- | | |- |
| | |'''Member Designation''' | | |'''Member Designation''' |
| − | |align = "center"|'''1'''
| |
| − | |align = "center"|'''2'''
| |
| − | |align = "center"|'''3'''
| |
| − | |align = "center"|'''4'''
| |
| − | |align = "center"|'''5'''
| |
| − | |align = "center"|'''6'''
| |
| − | |align = "center"|'''7'''
| |
| − | |align = "center"|'''8'''
| |
| − | |align = "center"|'''9'''
| |
| | | | |
| | |- | | |- |
| − | |'''Chair or Designate''' | + | |'''Chair or Delegate (e.g., CTO)''' |
| | |1 | | |1 |
| | |1 | | |1 |
