Concall-20080707

TSC - Technical Steering Committee

Monday, July 7th, 2008 11:00 AM (US Eastern Time, GMT -5)
To participate, dial 770-657-9270 and enter pass code 124466#
GoToMeeting at https://www.gotomeeting.com/join/822618174
GoToMeeting ID: 822-618-174 

back to TSC Minutes and Agendas

Attendance

Expected

• CTO: John Quinn
• Domain Experts: Jim Case (primary), Austin Kreisler (alternate)
• Foundation & Technology: Ioana Singureanu (primary), Woody Beeler (alternate)
• Structure & Semantic Design: Calvin Beebe (primary), Gregg Seppala (alternate)
• Technical & Support Services: Ken McCaslin (primary), Helen Stevens Love (alternate)
• Affiliate: Frank Oemig,
• ARB Chair: Charlie Mead
• HQ: Karen Van Hentenryck

invited

• Charles Jaffe (CEO); Ed Hammond (HL7 Chair); Chuck Meyer (HL7 Vice Chair)

Apologies

Austin Kreisler

Agenda

1. (5 min) Meeting Admin
   1. Roll Call - The following individuals participated on the call: Ioana Singureanu, Gregg Seppala, John Quinn, Chuck Meyer, Calvin Beebe, Charlie McCay, Ken McCaslin, Charlie Mead, Woody Beeler, Karen Van Hentenryck and Don Lloyd.
   2. Accept Agenda - Agenda was unanimously approved.
   3. Approve Minutes from concall-20080623 - Minutes were unanimously approved.
2. (20 min) Standing Committee Reports/Approvals
   1. CEO Report - The report was distributed via email. No questiions or issues were raised.
   2. CTO Report - Quinn distributed his report via email. No questions or issues were raised.
   3. ARB report - Charlie Mead reported that the ArB did not meet last week. An issue has emerged in the context of the NCI specification of a Person Service (a specification that the ArB is planning on using as an example of the type of specifications that would be produced as ballotable specifications). In the current RIM world view, the creation of Entity instances is fundamentally linked to instances of Registration Acts. From a RIM perspective, this means that ‘Entities only exist in the context of Roles.’ The issue emerges when one considers the Entity state diagram and what it ‘means’ in the context of a Registration Act, i.e. how the semantics of the Entity instance’s life cycle and the Registration Act’s process semantics are partitioned across RIM structures vs the partitioning of the same semantics in a services world.
   4. Affiliates Report - Nothing to report.
   5. Domain Experts - Nothing to report.
   6. Foundation & Technology
   7. Structure & Semantic Design - MOTION by SD: To approve the Order Sets Publication project proposal. The follow up on the outstanding items is document below. The motion was unanimously approved. [1]. Follow up on:
      • Specific contact name from implementers listed - Thomson-Reuters: JERRY OSHEROFF (Jerry.Osheroff@thomson.com; )Wolters Kluwer: HOWARD STRASBERG (Howard.Strasberg@wolterskluwer.com)
      • Clarification on the breadth of coordination and acknowledgment of OO in the context of this standard, ideally as co-sponsors - The group is willing to have OO acknowledged as co-sponsor, and has met with OO, SD and PC multiple times as noted below in thier response.
      • This project's relation to a May 2007 ballot- The project proposal submitted represents an amendment to the pre-existing Project Proposal which was in the old format, they simply migrated to the new Project Proposal form for the same project.
   8. Technical & Support Services - McCaslin reported that their steering division did not meet last week. Trying to get project facilitators is high on their list and willb e addressed on this week's call.
3. (30 min) Discussion topics
   1. TSC Elections - Charlie McCay noted that nominations for the TSC closed last week. There are two individuals standing for each of the two steering divisions but no candidates were nominated for the affiliate representative to the TSC.
   2. TSC approval for upcoming ballot cycle
      • New standards titles requiring TSC approval - All ballot titles were approved with the following caveats: (1) (US) will be appended to the end of the MITA document (2) Domain Experts steering division co-chairs will check on the Clinical Decision Support: Virtual Medical Record, Release document to determine whether the corresponding project scope statement has been approved. Without seeing a project scope statement, it appears that this particular document would overlap with other documents being products by other Work Groups within HL7.
        • HL7 Version 3 Standard: Composite Privacy Consent Directive, Release 1 (1st DSTU Ballot) – Community Based Collaborative Care
        • HL7 Implementation Guidance for Unique Object Identifiers (OIDs), Release 1 (1st Informative Ballot) – Attachments WG
        • HL7 Version 3 Standard: Clinical Decision Support; Virtual Medical Record (vMR), Release 1 (1st For Comment Only Ballot) – Clinical Decisions Support
        • HL7 Version 2 Implementation Guide: Clinical Genomics; Fully LOINC-Qualified Genetic Variation Model, Release 1 (1st DSTU Ballot) – Clinical Genomics
        • HL7 EHR Long Term Care Functional Profile, Release 1 (1st Informative Ballot) – EHR
        • HL7 Version 3 Standard: Medicaid Information Technology Architecture (MITA) Style Guide, Release 1 (1st Informative Ballot) – Community Based Collaborative Care
        • HL7 Version 3 Standard: Claims and Reimbursement: Special Authorization, Release 1 (1st DSTU Ballot) – Financial Management
      • New DSTU ballot requiring TSC approval - All of these DSTU ballot requests were unanimously approved.
        • HL7 Implementation Guide for CDA Release 2 - Level 3: Healthcare Associated Infection Reports, Release 2 – Structured Documents [This may have already been seen by the TSC as it was initially scheduled for ballot last cycle.]
        • HL7 Implementation Guide for CDA Release 2 - Level 3: Personal Healthcare Monitoring Reports, Release 1 – Structured Documents
        • HL7 Standard for CDA Release 2: Quality Reporting Document Architecture, Release 1 – Structured Documents
        • HL7 Version 3 Standard: Clinical Genomics; Genetic Variation, Release 1 – Clinical Genomics
        • HL7 Version 3 Standard: Medical Records; Composite Privacy Consent Directive, Release 1 – Community Based Collaborative Care
        • HL7 Version 3 Standard: Drug Stability Reporting (eStability), Release 2 – RCRIM
        • HL7 Version 3 Standard: Order Set Publication, Release 1 – Clinical Decision Support
        • HL7 Version 3 Standard: Public Health; CDISC Content to Message - Study Design, Release 1 – RCRIM
        • HL7 Version 3 Standard: Public Health; CDISC Content to Message - Study Participation, Release 1 – RCRIM
        • HL7 Version 3 Standard: Common Terminology Services, Release 2 – Vocabulary
        • HL7 Version 3 Standard: Drug Stability Reporting (eStability), Release 2 (1st DSTU Ballot) –RCRIM [Please note as well that this name indicates a change from the Release 1 name of this material: "HL7 Version 3 Standard: Regulated Studies - Drug Stability Reporting, Release 1"]
        • HL7 Version 3 Implementation Guide: Drug Stability Reporting (eStability), Release 2 (1st Informative Ballot) – RCRIM
        • HL7 Version 3 Standard: Public Health; CDISC Content to Message - Study Design, Release 1 (1st DSTU Ballot) – RCRIM
        • HL7 Version 3 Standard: Public Health; CDISC Content to Message - Study Participation, Release 1 (1st DSTU Ballot) – RCRIM
        • HL7 Implementation Guide for CDA Release 2 - Level 3: Personal Healthcare Monitoring Reports, Release 1 (1st DSTU Ballot) – Structured Documents
        • HL7 Standard for CDA Release 2: Quality Reporting Document Architecture, Release 1 (1st DSTU Ballot) – Structured Documents
      • Normative ballots requesting open ballot pools - All of these normative ballot requests were unanimously approved.
        • HL7 Version 3 Standard: Observations; Common Observation, Release 1 (3rd Normative Ballot) – WG co-chair prefers open pool
        • HL7 Version 3 Standard: Observations; Observation Request, Release 1 (2nd Normative Ballot) –WG co-chair prefers open pool
        • HL7 Version 3 Standard: Orders; Composite Order, Release 1 (2nd Normative Ballot) – WG co-chair prefers open pool
        • HL7 Version 3 Standard: Orders; Orders and Request Pattern, Release 1 (2nd Normative Ballot) – WG co-chair prefers open pool
      • Documents requiring TSC approval to ballot directly as normative - This request was unanimously approved. Don Lloyd asked whether a For Comments Ballot counts as a prerequisite for normative balloting as there are no quorum requirements. The TSC indicated that yes, this would satisfy the GOM statement that under normal circumstances subject matter of a normative ballot weill habe been subject to a review ballot.
        • HL7 Version 3 Standard: Structured Documents Architecture, Release 1 (previously at Comment Ballot)

Call adjourned at 11:50 am ET.