2009-07-27 TSC Call Agenda
Jump to navigation
Jump to search
TSC - Technical Steering Committee
Monday, July 27, 2009 11:00 AM (US Eastern Daylight Time, GMT -5) To participate, dial 770-657-9270 and enter pass code 124466# GoToMeeting at https://www.gotomeeting.com/join/165215206 GoToMeeting ID: 165-215-206
back to TSC Minutes and Agendas
Contents
Attendance
Expected
- Chair: Charlie McCay
- CTO: John Quinn
- Domain Experts: Austin Kreisler (primary), Ed Tripp (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: Ravi Natarajan
- ARB: Charlie Mead (primary), John Koisch (alternate)
- Ad-Hoc: Jim Case
- HQ: Lynn Laakso
Invited
- Charles Jaffe (CEO)
- Ed Hammond (HL7 Chair); Bob Dolin (HL7 Vice Chair)
- Marc Koehn (EA IP)
- Karen Van Hentenryck (HQ)
Apologies
- Austin Kreisler
- John Quinn
- Ed Tripp
Agenda
Meeting Admin
- Roll Call -
- Accept Agenda -
- Approve Minutes from 2009-07-20 TSC Call Minutes
- Review action items –
- From 2009-07-20_TSC_Call_Minutes: DAM Medical Records Composite Privacy – ACTION ITEM- ARB to review and discussion. How would one trace conformance back to this document.
- From 2009-07-20_TSC_Call_Minutes:HL7 Version 3 Standard: XML Implementation Technology Specification, Release 2 - need to clarify on whether this covers both datatypes and structures. ACTION ITEM: Woody will check with Grahame Grieve and then update the TSC
(20 min) Standing Committee Reports/Approvals
- CEO Report -
- CTO Report -
- EA IP Update
- ArB Report -
- Affiliates Report -
- Some vendors asked the Italian HL7 Affiliate for having (a sort of) HL7 certification for their products. The real point is to define what does it mean to certify HL7 a product... but any HL7 affiliate faced somehow this issue? What is the position of HL7 org about that?
- Domain Experts -
- Patient Care invited to discuss broader issues of clinical implementation guides:
- technical consistency issues (CDA implementation guides, DCM specification, and V3 Messages all having different documentation forms)
- content consistency issues (how do we detect inconsistency between specifications in a scalable and actionable way)
- maintenance responsibility (how do the set of templates used in the implementation guides relate to the DCM and other work that is being done in Patient Care)
- Patient Care invited to discuss broader issues of clinical implementation guides:
- Foundation & Technology -
- Request for extension of DSTU trial period: Vocabulary - TermInfo: "Using SNOMED CT in HL7 V3" at TSC Tracker #1101
- Structure & Semantic Design -
- Technical & Support Services -
(30 min) Discussion topics
- Ballot item e-vote review
- Open Issues List
- PSS at TSC Tracker 999: TSC Product Visibility Project Proposal
- TSC Wiki Draft Product List
- HL7 Wiki Draft Product List
- Feedback on draft matrix on domains.
- Does this need to be approved as a project? Does the TSC wish to modify the product list before “approving” it? Are we ready to send the Product Brief templates to the appropriate work groups to fill out?
- TSC Tracker 1082:provide a structure and format guideline for three year plans to the WGs, now tied to PS WG project to clean up Project Insight. See example
- TSC Tracker 749: Review the role of the steering divisions
- TSC Tracker 745: HQ to explore cost of providing secretarial support to the WGs
- TSC Tracker 1001: TSC Large Customer Partnerships Project Proposal
- PSS at TSC Tracker 998: TSC Project Visibility Proposal
- PSSat TSC Tracker 997: TSC Work Group Visibility project proposal
- PSS at TSC Tracker 999: TSC Product Visibility Project Proposal