2014-06-02 TSC Call Minutes

From HL7 TSC
Revision as of 14:09, 2 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-02
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 regrets 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 regrets Pat van Dyke . Andy Stechishin
ex officio Invited Guests Observers HL7 Staff
. Stan Huff (HL7 Chair) w/vote . Lloyd McKenzie . 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-05-19 TSC Call

Governance

  1. Discussion topics: FHIR Registry (Lloyd)

Management

  1. Review action items –
    • TSC Definition of Domain Analysis Models and Functional Profiles TSC Tracker 2165 (Pat and Tony)
    • Ken will clarify with Karen on permissibility of dot releases with ANSI and approaches for technical corrections.
    • Need to extract the errata publication guidance from the 2013-01-12 minutes and TSC Tracker 2403 and review and make available.
    • the International Council was told the TSC would identify the next conformance profiles and the TSC should discuss further. Ken to speak to Chuck about it.
    • 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?
    • Ken and Calvin will address the potential for a survey on conformance profile development - see https://www.surveymonkey.com/s/WKNZSYM.
  2. Approval items for discussion referred from e-vote:
    • Project approval request of International Patient Summary template for SDWG of SSD SD at Project Insight # 1087 and TSC Tracker #3231
      • Giorgio writes "There are relationship among “projects dependencies”, “external collaborations”, “scope of the project” and timeline that I’d like to clarify a little bit. " Other votes were 7/0/0 in favor.
    • Project Approval request of Common Product Model (CPM) Release 2 Normative and Structured Product Labeling (SPL) Release 6 Normative for OO of SSD SD cosponsored by RCRIM of DESD at Project Insight # 1114 and TSC Tracker #3306
      • Jean writes "This is another project that intends to use the old datatypes and I am personally opposed to that and would like to know the process that projects need to undertake to get granted license to use the old datatypes."
    • (defer for further discussion by FGB) Project Approval request of Patient Care WG Develop FHIR resources and profiles for the second DSTU release for Patient Care WG of DESD at Project Insight # 1105 and TSC Tracker #3277
      • Austin writes: "I believe adding FHIR profiles based on C-CDA to the project scope is a major scope change and it also turns this project into a hybrid Universal/US Realm project (C-CDA is clearly US Realm specific). Dows the TSC want these sorts of hybrid projects for FHIR? If so, then just about every FHIR project moving forward that includes C-CDA in scope needs to now also go through the US Realm Task Force. I think FMG has unwittingly made a mistake in pushing work groups to add C-CDA to the scope of their base FHIR resource development projects. This needs TSC discussion on how US Realm vs. Universal projects should be managed"
    • Project Approval request of Health Care Devices to Develop FHIR resources and profiles for the second DSTU release for Health Care Devices WG of DESD at Project Insight # 1103 and TSC Tracker #3278
      • FMG discussions on requiring WG FHIR projects to include work on CCDA profiles calls into question any WG FHIR projects.
    • (postpone) Project Approval request of Electronic Health Record-System (EHR-S)Functional Requirements Documentation for Laboratory Interoperability Transactions – EHR-S Functional Requirements Implementation Guide for Lab Orders Interface (LOI) for OO WG of SSD SD cosponsored by EHR of SSD SD and CGIT of DESD at Project Insight # 1096 and TSC Tracker #3308
    • (postpone) Project Approval request of Electronic Health Record-System (EHR-S)Functional Requirements Documentation for Laboratory Interoperability Transactions – EHR-S Functional Requirements Implementation Guide for Lab Results Interface (LRI) for OO WG of SSD SD cosponsored by EHR WG of SSD SD and CGIT of DESD at Project Insight # 1095 and TSC Tracker #3309
      • Austin writes "These two scope statements state that they are not constraining an existing standard. From my perspective, that means these two projects are developing guidance documents that do not qualify to be on the normative track. That means neither of these qualify as a DSTU either. They instead should be balloted as Informative not DSTU. These two proposed projects bear some resemblance to the C-CDA Companion Guide document that was balloted as Informative. That document provides additional guidance on implementing C-CDA without providing additional constraints on the standard."
      • Update: OO has reviewed again and changes are pending to clarify - anticipate e-vote again next week
  3. Approval items from e-vote ended 2014-05-23: Approved 8/0/0 with Ad-Hoc, ARB, 2 Affiliate, and DESD, FTSD, SSD SD, and T3SD voting
  4. Approval items from e-vote ended 2014-05-30: 8/0/0 with Ad-Hoc, 2 Affiliate, ARB, DESD, FTSD, SSD SD & T3SD participating
  5. Approval items for e-vote next week:
  6. Discussion topics:
    • 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
    • BAM review
    • TSC Three-year planning - do we need to review it?
    • 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).
  7. Reports: (attach written reports below from Steering Divisions et al.)
    • Congratulations to RCRIM WG on their request for Normative publication of HL7 Version 3 Standard: Structured Product Labeling, Release 5 at Project Insight # 325.
    • Co-chair deadline awareness
  8. 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-02_TSC_Call_Minutes&oldid=13501"