2014-06-09 TSC Call Agenda

From HL7 TSC
Revision as of 14:33, 9 June 2014 by Llaakso (talk | contribs)
Jump to navigation Jump to search

TSC Agenda/Minutes

Meeting Info/Attendees

Standing Conference Calls

TSC will hold a Conference Call at 11AM Eastern time, each Monday except during scheduled face-to-face Working Group Meetings unless otherwise noted at TSC_Minutes_and_Agendas.

GoToMeeting at https://global.gotomeeting.com/join/426505829 using VOIP
For those without access to microphone/speakers:
US: +1 (224)501-3318
Canada: +1 (647)497-9379
Italy: +39 0 230 57 81 80
Access Code: 426-505-829
GoToMeeting ID: 426-505-829
HL7 TSC Meeting Minutes

Location: call 770-657-9270 using code 985371#
NEW GoToMeeting ID: 426-505-829

Date: 2014-06-09
Time: 11:00 AM U.S. Eastern
Facilitator: Ken McCaslin Note taker(s): Lynn Laakso
Quorum = chair + 5 including 2 SD represented yes/no
Chair/CTO ArB International Affiliate Rep Ad-Hoc
. Ken McCaslin . Tony Julian . Jean Duteau . Austin Kreisler
. John Quinn . Lorraine Constable . Giorgio Cangioli .
Domain Experts Foundation and Technology Structure and Semantic Design Technical and Support Services
. Melva Peters Woody Beeler . Calvin Beebe . Freida Hall
. John Roberts . Paul Knapp . Pat van Dyke . Andy Stechishin
ex officio Invited Guests Observers HL7 Staff
. Stan Huff (HL7 Chair) w/vote . . obs1 . Lynn Laakso
. Don Mon (Vice Chair) vote . . . obs2 .
. Chuck Jaffe (CEO) vote . . . .

Agenda

Housekeeping

  1. Introduction of visitors (including declaration of interests)
  2. Agenda review and approval -
  3. Approve Minutes of 2014-06-02 TSC Call Agenda

Management

  1. Review action items –
    • TSC Definition of Domain Analysis Models and Functional Profiles TSC Tracker 2165 (Pat and Tony)
    • Ken will send survey on conformance profile development to Karen to issue the survey to her list.
    • Woody report back on collaboration with ARB and MnM to narrow the scope of the SAIF IG to allow completion of the project in a reasonable period of time.
    • 2585 Define list of machine-processable artifacts for membership benefit - Ken will follow up with Stan on who is the Marketing committee chair and the Board's intent with the list
    • Freida will draft PSS for Positioning Security Risk Analysis standard within HL7 and circulate to TSC; next steps?
  2. Approval items referred for discussion:
    • Mission and Charter Statement Update for FGB
      • [FHall] Can we clarify statements below see ** comments they are unclear:
        1. FGB will identify an FGB cochair unless otherwise designated by FGB to act as TSC liaison and attend the TSC meetings to escalate product issues and bring recommendations back to the FGB. ** we have other precedent for a group to elect its co-chair, what does ‘identify’ and ‘designated’ mean; also seems in conflict with statement further down “The FGB will select two co-chairs from the group for staggered two year terms.” Consider changing ‘select’ to ‘elect’ for consistency with other HL7 processes.
        2. In lieu of the CTO, a Product Director would be a member to facilitate participation in the enterprise-wide product strategy. ** Who are “Product Director”s?
        3. Each member should have expertise in HL7 governance processes ** What does mean, they read ‘x’ documents, have ‘x’ experience? Please clarify.
    • Project Approval request of Provenance for Clinical Document Architecture (CDA R2) Documents Implementation Guide for CBCC WG of DESD at Project Insight # 1093 and TSC Tracker #3314
      • The realm has not been identified, but given its focus on S&I and US based participants, it needs to be a US Realm project (Austin)
      • PSS says ONC and HL7 have agreement in place but it is not on the Agreements page – maybe in process? (Freida)
  3. Approval items from e-vote: Approved 6/0/0 with Ad-Hoc, 2 Affiliate, ARB, FTSD, and T3SD voting.
  4. Projects pending input:
  5. Discussion topics:
    • BAM review (Tony)
    • Review of definition of 'implementation guide' and 'conformance'
      • Final Definitions
        • Implementation Guide
          An implementation guide is often created to organize a collection of conformance profiles, functional requirement specifications, or templates for specifying a set of related interactions described in a use case or use cases. Implementation guides typically describe broader conformance requirements such as application behavior. Such requirements may include how a set of interactions (messages, documents, etc.) are to be used to enact certain application functionality among applications (actors).
        • Conformance
          Conformance is defined as the fulfillment of a product, process, or service of specified requirements [ISO-17000, OASIS]. The concept of conformance is essential to any standard for providing an objective measure of how closely implementations satisfy the requirements defined in the standard.
    • Review of action item to define relationship between help desk and WG cochairs
    • WG Health – Impact on SD project approval
    • Determine the next 2-4 profiles for Conformance Testing (candidate topics: LRI, CDA R2, EHR-S FM, EHR-S FPs).
  6. Reports: (attach written reports below from Steering Divisions et al.)
    • TRAC:
      • Would measurements from before and after the changed process to disallow a single check box to enroll in all of the ballots be meaningful for ballot quality assessment?
      • TRAC report/recommendation on governance metric for project scope statements submitted late for deadline
    • Co-chair deadline awareness
  7. Open Issues List

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


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

Retrieved from "https://tscwiki.hl7.org/w/index.php?title=2014-06-09_TSC_Call_Agenda&oldid=13535"