2013-05-28 TSC ANSI/GOM Task Force notes

TSC Agenda/Minutes

Meeting Info/Attendees

HL7 TSC ANSI/GOM Task Force Meeting Minutes Location: call 770-657-9270 using code 985371#		Date: 2013-05-28 Time: 6:00 PM U.S. Eastern
Facilitator: Austin Kreisler		Note taker(s): Lynn Laakso

Quorum n/a
Attendees
.	Calvin Beebe
	Jean Duteau
	Freida Hall
.	Austin Kreisler
.	Lynn Laakso (scribe)
delayed	Pat Van Dyke

Agenda

Link to updated GOM Action Items:

• Freida will check with Karen to see if ANSI would consider allowing HL7 to pre-load the ballot pools with all voting members and ask them to opt-out, or offering them the interest areas they can be automatically signed up for. (from 2013-04-23_TSC_ANSI/GOM_Task_Force_notes)
• Jean will write something on How do we flag balance issues on the ballot tally page among voter categories? 'No single interest category can constitute a majority.' Don would need to create % summaries of the interest types and the mechanism to "lock down" enrollment at any point after the enrollment closes where it comes into balance

Status: We’ll need to submit proposed changes to the GOM by end of June, other than ANSI audit issues which are already approved work items.

Review of the continued list of Partial List of Needed or Suggested Changes still has areas that have not been addressed. Final set of comments from the ANSI auditor now available

• the ANSI auditor has provided response on an item we've discussed (excerpt of email from Karen to GOC):
  1. The way we define consensus body and how we determine balance.

  They are requesting

  1. That we change our procedures to do a balance check before the ballot begins (we currently check this one week or so into the ballot) and that balance we applied to the consensus group, not the ballot group. This can be done a couple of different ways, so we will need some discussion here. Also we need to clarify how abstentions are treated and whether or not an abstention is considered a vote.

Resolve “backup” dilemma encountered when CTO is not available.

14.03.06 Ballot Pool or Consensus Group Variance Process Any Affiliate or organizational member experiencing a change in voting representatives or any other situation which impacts current ballot pools or consensus groups shall request a variance of process from the CTO. A request for variance of process shall include a detailed explanation for such a request and clearly identify the individuals involved. The CTO shall triage the issue, engage the appropriate parties, and assure resolution of the issue. Documentation of the variance and its resolution will be retained with the ballot material for review during the ANSI audit process.

• Freida sends Issue 1305003, which reads "The GOC agrees that a process dependent on a single individual is less than optimal given the nature of our organization. The GOC will seek to define viable alternatives and scan the GOM for similar occurrences."

Minutes

Minutes/Conclusions Reached:

Please don't forget to hang up from the conference call (VOIP users)

Next Steps

Actions (Include Owner, Action Item, and due date) .

Next Meeting/Preliminary Agenda Items 2013-MM-DD ANSI/GOM Task Force notes.

© 2013 Health Level Seven® International. All rights reserved.