2012-02-06 TSC Call Minutes

From HL7 TSC
Revision as of 18:18, 13 February 2012 by Llaakso (talk | contribs) (moved 2012-02-06 TSC Call Agenda to 2012-02-06 TSC Call Minutes: minutes approved)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

TSC Agenda/Minutes

Meeting Info/Attendees

HL7 TSC Meeting Minutes

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

Date: 2012-02-06
Time: 11:00 AM U.S. Eastern
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso
Attendee Name Affiliation
x Calvin Beebe HL7 SSD SD Co-Chair
x Woody Beeler HL7 FTSD Co-Chair
x Freida Hall HL7 T3SD Co-Chair
x Tony Julian HL7 FTSD Co-Chair
x Austin Kreisler HL7 TSC Chair, ad-hoc member
x Lynn Laakso HL7 staff support
x Patrick Loyd HL7 T3SD Co-Chair
x Charlie Mead HL7 ArB Chair
Don Mon HL7 Board Chair
x Ravi Natarajan HL7 Affiliate Representative
Ron Parker HL7 ArB Alternate
x John Quinn HL7 CTO
Helen Stevens Ad-hoc member
x Ed Tripp HL7 DESD Co-Chair
x Pat Van Dyke HL7 SSD SD Co-Chair
x Mead Walker HL7 DESD SD Co-Chair
x Brian Pech observer


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 2012-01-30 TSC Call Agenda
  4. Assign review dates or update status on WGM action items:
    • Austin will also need to flag the Tooling EHR Profile designer as a SAIF Architecture project.
    • Austin suggests we follow up with Education as well as HQ on the idea of Monday Q1/Q2 tutorials for cochair and facilitator training topics
    • Woody will send John his few slides on primitives in UML for code systems, vocabulary and datatypes.
    • Freida will take it up with Dave that the PSS doesn't currently indicate whether an agreement is in place with whatever organization is collaborating.
    • Ed needs to draft a list of responsibilities for the ORC liaison.
    • Lynn will add a tracker (WGH Tracker # 2173) to follow up on how to automate a crawl to check for WG web page updates. Completed.
    • Austin suggests he talk with John, Mark and Karen on what is being done in the effort to identify implementation references and bring it back to discuss later
    • John's recommendations on ArB Composition; Outstanding discussion topic tabled from 2012-01-15_TSC_WGM_Agenda
    • Action items from last week
      • Austin will send a note to the DESD and WG co-chairs explaining why Clinical Sequencing, for Clinical Genomics project was tabled. Recommend they produce separate scope statements or clearly show the deliverables and sequence of what they're producing in this scope statement. Completed: See update at TSC Tracker # 2154
      • Austin will contact the SD and WG chairs to iron out what is going on with Implementation Guide for CDA Release 3 – Representation of vital signs / physiological data compatible with ISO11073 for GAS WG, to develop an IG on CDA R3 when it doesn't exist yet, and SDWG has not approved cosponsorship. Completed: See update at TSC Tracker # 2151 - Austin reports it is actually CDA R2 and SDWG has agreed to cosponsorship.
      • Woody will follow up with them on a second DSTU implementer for the Pharmacy Service Profile for SOA WG. FTSD did not have quorum this past week.
      • Woody will check back with Vocabulary on the pending question on Common Terminology Services – Release 2 (CTS 2) - Normative for Vocab WG.
      • Lynn will follow up on details with the same registration process for the pharmacy OOC meeting. Completed: see http://www.hl7.org/events/pharmacy032012/.
  5. Approval items:
    Projects:
    Publication Request
    Withdrawal requests:
  6. Discussion topics:
    • Definition of DAMs and Functional Profiles at TSC Tracker # 2165 for offering click-through license. Tabled Motion: DAMS in the V3 ballot and the list of EHR FPs recognized by the EHR WG be the definition of DAMs and FPs.
    • Schedule discussion for upcoming conference call the review of the draft SI criteria metrics and determine exactly how we count them
  7. Reports: (attach written reports below from Steering Divisions et al.)
  8. Open Issues List


Supporting Documents

  • See links

Minutes

Minutes/Conclusions Reached:

  1. Introduction of visitors (including declaration of interests) - Brian Pech is observing
  2. Agenda review and approval - Austin Kreisler - do the action items after the approval items.
  3. Approve Minutes of 2012-01-30 TSC Call Agenda - Ravi abstains, passes 5/0/1
  4. Approval items:
    Projects:
    • Tabled Motion: Approve project scope statement for Clinical Sequencing, for Clinical Genomics at Project Insight # 841, TSC Tracker # 2154. Noted that there should be a deliverable date noted for objective to DSTU - Austin reports the Work Group is not ready to report the clarifications requested by the TSC. Remains tabled.
    • Tabled Motion: Approve project scope statement for Implementation Guide for CDA Release 3 2 – Representation of vital signs / physiological data compatible with ISO11073 for GAS WG of DESD at TSC Tracker # 2151. Austin describes the clarification of CDA R2 and SDWG agreement to cosponsor.
      • Vote: Unanimously approved
    • Tabled Motion: Approve project scope statement for Pharmacy Service Profile for SOA WG of FTSD, cosponsored by Pharmacy WG of DESD at Project Insight # 838, TSC Tracker # 2159. No word back, remains tabled.
    • Motion: Approve project scope statement for Gene Expression for CG WG of DESD at Project Insight # 333?, TSC Tracker # 2172; Mead describes that it will initially will ballot comment only then to ballot informative and progress to normative. Concern is to identify the pieces they intend to go to normative; Mead notes that the Work Group is not certain yet either but will determine as they develop. They do not indicate that the DAM is a product of the project. We pushed back last week to identify which artifacts were balloting at which level. Consistency in asking for that specificity was discussed. Two concerns raised; identification of what they intend to be normative, and whether there will be a DAM produced that will be subject to the discussion scheduled later on making DAMs publicly available. Project schedule timeline after DSTU for proceeding to normative is not specified though normative balloting is checked as being in scope. They may choose to uncheck normative and advance a new PSS when it will go normative, or add to their timeline for the normative ballot. Mead will also inform them that our interpretation of the scope is that a DAM will not be published as a separate product/artifact but as part of the domain. Return to table.
    Publication Request
    • Tabled Motion: Approve publication request for Security WG of FTSD, V3 Security DAM, R1 (Composite Security and Privacy Domain Analysis Model aka Security Domain Analysis Model) at Project Insight # 529, TSC Tracker # 2104. Lynn reports that Don has been provided with a publishable file format. Woody notes that security and privacy terminology has taken careful consideration of late; Amended motion: Mead suggests we approve it and let Publishing and the WG resolve the title of the document. Calvin seconds.
      • Vote: Unanimously approved
    Withdrawal requests:
  5. Discussion topics:
    • Definition of DAMs and Functional Profiles at TSC Tracker # 2165 for offering click-through license. Tabled Motion: DAMS in the V3 ballot and the list of EHR FPs recognized by the EHR WG be the definition of DAMs and FPs.
      • Woody wishes to amend his motion to be those DAMs balloted as Informative documents (as compared to DSTU). Woody clarifies a V3 informative document is standalone by definition. A DAM as part of a V3 domain is not a standalone document. Charlie Mead asks if a DSTU definition of a DAM is more formal or robust than what we currently have? We don't want to cross over rules for DAMs and DSTU. This is for the purposes of intellectual property. The ArB is being asked to provide a robust definition on the semantic definition of a DAM. Lynn cautions that we want to provide a definition and not only a description. Woody asks why the Board needs such a definition when the operational definition will meet their needs for the IP issues. Ed recalls there was some extensive information in the motion that was passed by the Board. Mead recounts the DAM is defined in the HDF, one in the CIC style guide, and one in the ArB documentation in the SAIF artifact definition under a slightly different name, which Charlie adds addresses only static semantics. Austin seeks to create a definition to apply to artifacts going forward. Ravi asks if this is a marketing thing. Austin notes they wish to announce this at HIMSS. Amended motion: DAMs are identified in their name, as balloted informative documents, and approved for informative publication. Functional profile definition will be defined by the EHR WG.
      • Pat suggests we define Functional Profiles are recognized once reaching the highest level of ballot (informative or normative) and approved for publication. She'll write up a definition and circulate it.
      • Vote: unanimously approved.

Adjourned 12:01 EST

Next Steps

Actions (Include Owner, Action Item, and due date)
  1. Lynn will make technical correction to the action item of the minutes from the WGM.
  2. Mead will follow up with CG Gene Expression on Project schedule timeline after DSTU for proceeding to normative is not specified though normative balloting is checked as being in scope. They may choose to uncheck normative and advance a new PSS when it will go normative, or add to their timeline for the normative ballot. Mead will also inform them that our interpretation of the scope is that a DAM will not be published as a separate product/artifact but as part of the domain.
  3. Publishing and the Security WG will resolve the title of the document for the (Composite Privacy and ) Security DAM
  4. Assign review dates or update status on WGM action items: assignees please review and update
    • Austin will also need to flag the Tooling EHR Profile designer as a SAIF Architecture project.
    • Austin suggests we follow up with Education as well as HQ on the idea of Monday Q1/Q2 tutorials for cochair and facilitator training topics
    • Woody will send John his few slides on primitives in UML for code systems, vocabulary and datatypes.
    • Freida will take it up with Dave that the PSS doesn't currently indicate whether an agreement is in place with whatever organization is collaborating.
    • Ed needs to draft a list of responsibilities for the ORC liaison.
    • Lynn will add a tracker (WGH Tracker # 2173) to follow up on how to automate a crawl to check for WG web page updates. Completed.
    • Austin suggests he talk with John, Mark and Karen on what is being done in the effort to identify implementation references and bring it back to discuss later
    • John's recommendations on ArB Composition; Outstanding discussion topic tabled from 2012-01-15_TSC_WGM_Agenda
    • Action items from last week
      • Austin will send a note to the DESD and WG co-chairs explaining why Clinical Sequencing, for Clinical Genomics project was tabled. Recommend they produce separate scope statements or clearly show the deliverables and sequence of what they're producing in this scope statement. Completed: See update at TSC Tracker # 2154
      • Austin will contact the SD and WG chairs to iron out what is going on with Implementation Guide for CDA Release 3 – Representation of vital signs / physiological data compatible with ISO11073 for GAS WG, to develop an IG on CDA R3 when it doesn't exist yet, and SDWG has not approved cosponsorship. Completed: See update at TSC Tracker # 2151 - Austin reports it is actually CDA R2 and SDWG has agreed to cosponsorship.
      • Woody will follow up with them on a second DSTU implementer for the Pharmacy Service Profile for SOA WG. FTSD did not have quorum this past week.
      • Woody will check back with Vocabulary on the pending question on Common Terminology Services – Release 2 (CTS 2) - Normative for Vocab WG.
      • Lynn will follow up on details with the same registration process for the pharmacy OOC meeting. Completed: see http://www.hl7.org/events/pharmacy032012/.
Next Meeting/Preliminary Agenda Items