Difference between revisions of "2011-03-07 TSC Call Minutes"

From HL7 TSC
Jump to navigation Jump to search
 
(No difference)

Latest revision as of 13:09, 16 March 2011

TSC Agenda/Minutes

Meeting Info/Attendees

HL7 TSC Meeting Minutes

Location: call 770-657-9270 using code 124466#
GoToMeeting ID: 165-215-206

Date: 2011-03-07
Time: 11:00 AM U.S. Eastern
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso
Attendee Name Affiliation
regrets Calvin Beebe HL7 SSD SD Co-Chair
x Woody Beeler HL7 FTSD Co-Chair
Bob Dolin HL7 Board Chair
x Tony Julian HL7 FTSD Co-Chair
x Austin Kreisler HL7 TSC Chair, DESD Co-Chair
x Lynn Laakso HL7 staff support
regrets Patrick Loyd HL7 T3SD Co-Chair
x Ken McCaslin HL7 TSS SD Co-Chair
1st half Charlie Mead HL7 ArB Chair
x Ravi Natarajan HL7 Affiliate Representative
Ron Parker HL7 ArB Alternate
x John Quinn HL7 CTO
x Gregg Seppala HL7 SSD SD Co-Chair
Ed Tripp HL7 DESD Co-Chair
x Jay Zimmerman HL7 Affiliate Representative
x Wendy Huang Invited guest, IC co-chair
x Melva Peters Invited guest, IC co-chair


Quorum Requirements (Chair +5 with 2 SD Reps) Met: yes

Agenda

Agenda Topics

  1. Introduction of visitors (including declaration of interests)
  2. Agenda review and approval - Austin Kreisler
  3. Approve Minutes of 2011-02-21 TSC Call Agenda, 2011-02-28 TSC Call Agenda
  4. Review action items –
    • Task # 1579 for Ken: Create Project Scope Statement for TSC Product and Services Strategy Project - close this task, tracker (# 1364) and project (# 648) due to lack of availability / participation
  5. Approval items:
  6. Discussion topics:
    • “Eclipse SMD tooling rollout” and funding implications. (Ravi)
    • IC Response to TSC minutes 2011-01-11
    • What should be reported on a regular basis? What should those reports look like?
    • Update on CMET R3 (ANSI affirmation) - Woody reports: we determined in late November that we can probably accomplish the CMET approval without reaffirmation (as yet not fully confirmed) and hence we "suspended" this.
    • Need for statement on what V3 includes (it's not just V3 Messaging) like RIM, Datatypes, 21090, CDA, are all part of V3 - Charlie Mead.
    • Request for TSC to develop guidelines on what should be Informative vs. DSTU vs. Normative, at TSC Tracker # 1815
  7. Reports: (attach written reports below from Steering Divisions et al.)
    • PHER (DESD) has decided to pull the ELR IG Release 2 project for the time being.
  8. Open Issues List


Supporting Documents

Minutes

Minutes/Conclusions Reached:

  1. Introduction of visitors (including declaration of interests) – Wendy and Melva on the line from IC in regard to their discussion item.
  2. Agenda review and approval - Austin Kreisler – move guest topics to top of discussion section and then Ravi’s issue.
  3. Approve Minutes of
  4. Review action items –
    • Task # 1579 for Ken: Create Project Scope Statement for TSC Product and Services Strategy Project - close this task, tracker (# 1364) and project (# 648) due to lack of availability / participation.
      • Ken cannot do it on his own and he has not had response back on others available to participate in the activity. John notes that the product identification project is underway and he is returning to Ann Arbor to go through the last batch of product briefs from Martopia, who will develop a form of product strategy.
  5. Approval items:
    • Tabled Motion: Approve Model Automatic Exchange (MAX) for UML Models Project Scope Statement for Tooling WG of T3SD, at TSC Tracker # 1779, Project Insight #742 (no ballot deliverable)
      • Patrick emailed to return this to table for next week.
    • Tabled Motion: Approve Project Scope Statement - Semantic Health Information Performance and Privacy Standard (SHIPPS) for CBCC of DESD, at TSC Tracker # 1787, Project Insight # 724. (2011May draft for comment ballot deliverable). Without an updated Project Scope Statement, return this to table for next week.
    • Tabled Motion: Approve Project Scope Statement for PHER of DESD - HL7 Version 2.5.1 Implementation Guide: Vital Records Death Reporting, Release 1 (US Realm) at TSC Tracker # 1812, Project Insight # 735. (2011May DSTU ballot deliverable).
      • This was tabled pending discussion of DSTU vs. Informative; return this to table for next week.
    • Tabled Motion: Approve Project Scope Statement for Government Projects of DESD - HL7 Readiness to Support Meaningful Use, at TSC Tracker # 1636, Project Insight ID# 712. (no ballot deliverable).
      • Is this project meaningful any longer? We’ve already started dealing with MU without having the policy this project was going to develop… John is ‘plugged in’ to the S&I framework, based on conference at HIMSS with ONC leadership, but it is enabled through Accenture. The white paper deliverable is not feasible for taking the resources away from other efforts at this point. Ken moves to withdraw the project. Others acknowledge that we should ask Government projects to withdraw. Ed says to table for two weeks. Returned to table.
    • Motion: Approve DSTU publication extension request for HL7 Implementation Guide for CDA Release 2: Quality Reporting Document Architecture (QRDA), Release 1 for SDWG for one year atTSC Tracker # 1816, Project Insight # 210.
      • Suggestion to include on the template the number of times it has been requested for extension as well.
      • Woody moves to consider all three as they were approved as sibling documents.
    • Motion: Approve DSTU Publication Extension Request for SDWG- HL7 Implementation Guide for CDA Release 2: CDA Framework for Questionnaire Assessments, Release 1 for one year at TSC Tracker # 1817, Project Insight # 381.
    • Motion: Approve DSTU Publication extension request by SDWG for HL7 Implementation Guide for CDA Release 2: Operative Notes, Release 1, for one year at TSC Tracker # 1818, Project Insight # 728. Noted request does not have the ballot reconciliation activities or link included.
    • VOTE: All three DSTU extension requests unanimously approved.
    • Amend publication request to include number of times it has been extended. Ken suggests they submit the first publication request as well. Ken suggests they also post the publication request documents on their WG page.
  6. Discussion topics:
    • IC Response to TSC minutes 2011-01-11
      • Melva reports they met with ArB reps in Cambridge and Sydney. They agreed to maintain the scope beyond V2, and are waiting to hear the next steps needed. Austin notes that there is a need to populate the ECCF with artifacts needed, particularly for V3. ArB will be balloting the SAIF as an informative ballot in the upcoming cycle and member participation in the review would be most welcomed. They are curious on reconciliation of comments on the peer review from last summer. Charlie notes that the comments matrix is published, and two substantive comments from IC for revision were incorporated into the material that will be in the ballot cycle. Wendy suggests we connect at May meeting to review comments. Austin notes that involvement in the SAIF program development is best achieved through subscription to the SAIF-arch-pgm list. Melva notes it’s not clear in her mind where IC fits in. Austin notes there’s a project from MnM in developing the SAIF IG and IC needs to have a piece of that, preferably as cosponsor. IC should self-nominate to be part of that project. Wendy notes that IC was not included in developing that scope statement. Woody comments that the list of cosponsors and participants should not be considered a closed list – we want others participating. It’s a TSC project but MnM is taking the lead on coordinating it.
    • “Eclipse SMD tooling rollout” and funding implications. (Ravi)
      • Background: CfH working on Eclipse SMD intent to help HL7 move to next gen tooling framework for modeling. 1.02 version of project was funded by NHS and looking for HL7 to move the next version forward. At last week OHT meeting was told it was stalled due to lacking funds. Configuration management piece is critical deliverable to start rolling out product. Ravi would like to see TSC support to request Board to fund this development or he fears it will be lost for lack of implementation. Woody asks as though this is a subset of changes or the full set of changes discussed last year – it’s a subset of changes that are needed to continue with migration. Woody agrees that the funding is needed but not that the TSC may be able to exert much influence on funding availability. Austin recommends that he craft a motion for the TSC but he also needs to be clear as to what the amount of funding is that is needed. John notes that he spoke with Jane and they don’t have a clear estimate. There is also a dependency for access to MIF representation of RIM on a VHA tool. Gregg notes the project is proceeding using a tool Dave Carlson is working on but cannot comment on its use; the models are compatible but their expressions are different. John will try to get some concrete numbers from Jane and possibly Lloyd. Bob is out of the country right now but it will have an impact on the Health Story effort. Ravi would like the Tooling committee to assess the impact of the adoption of the different pieces and what that means. Ravi will coordinate with John and Woody offline and bring back a motion next week.
    • Request for TSC to develop guidelines on what should be Informative vs. DSTU vs. Normative, at TSC Tracker # 1815
      • Project being requested is IG for DSTU.
      • Lynn shows the December TSC newsletter article on ballot guidance at http://www.hl7.org/documentcenter/public/techNewsletter/HL7_TECHNEWSLETTER_20101215.pdf.. Noted that we’ve balloted them informative and DSTU – Ken asks if we ‘should’ have been balloting them as such. Ed notes that a Normative IG would create problems for realm-specific localization. John reports that the HITSP process fell under the scrutiny for lack of ballot process. What are the action items? Who would draft a policy? Ed is unavailable next week. Can we discuss on the TSC list? Woody clarifies that DSTU is a normative-track ballot.
  1. Reports:
    • PHER (DESD) has decided to pull the ELR IG Release 2 project for the time being.


Adjourned 12:01 PM EST


Next Steps

Actions (Include Owner, Action Item, and due date)
  • Ravi will coordinate with John and Woody offline and bring back a motion next week on the SMD.
Next Meeting/Preliminary Agenda Items
  1. Discussion topics:
    • Request for TSC to develop guidelines on what should be Informative vs. DSTU vs. Normative, at TSC Tracker # 1815
    • What should be reported on a regular basis? What should those reports look like?
    • Update on CMET R3 (ANSI affirmation) - Woody reports: we determined in late November that we can probably accomplish the CMET approval without reaffirmation (as yet not fully confirmed) and hence we "suspended" this.
    • Need for statement on what V3 includes (it's not just V3 Messaging) like RIM, Datatypes, 21090, CDA, are all part of V3 - Charlie Mead.
  2. Pending Motions:
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=2011-03-07_TSC_Call_Minutes&oldid=7778"