Vocab TQA Minutes

Backto Main Page

Older Minutes for Vocab TQA here

2016-02-08_Minutes
2015-02-05_Minutes
2015-02-12_Minutes
2015-03-05_Minutes
2015-03-19_Minutes
2015-05-26_TQA_minutes
2015-06-09_TQA_minutes
2015-07-07_TQA_minutes
2015-07-21_TQA_minutes
2015-08-18_TQA_minutes
2015-09-01_TQA_minutes
2015-09-28_TQA_minutes
2015-10-12_TQA_minutes
2015-10-26_TQA_Minutes
2015-11-09_TQA_Minutes
2015-12-07_TQA_Minutes
2015-12-21_TQA_Minutes

Ongoing minutes for the TQA Project in reverse chronology here

2016-02-22 Meeting

CALL IN is standard Vocab HL7 number. 1 770-657-9270, Participant Passcode: 598745
10a – 11:30a ET
Attendees: Rob McClure, Rob Snelick, Susan Barber, Stan Huff
Standard Vocab quorum requirements: 1 Project lead or Vocab chair and two participants was met.

Agenda for 2/22/16

1. Admin
   1. Call planning.
   2. Confirm Co-sponsor participants
      1. Vocab is Ted and Rob McClure
      2. HTA – Heather
      3. CIMI – Stan
      4. SD/CDA – Lisa
      5. V2 – Rob Snelick
      6. V3 – Woody
      7. FHIR – Lloyd
   3. Continue work of identifying critical terminology issues for HL7 products documented on Requirements page
      1. Discussion on best approach to begin collecting information on QA issues across products.
      2. Continue discussion of CIMI SNOMED CT Extension Namespace

Discussion

1. Worked on Reference page table of terms to define x 40 min
2. Discussed SNOMED CT extension x15min
   1. CIMI use the SCT Ext for the following activities:
      1. As a tool to capture needed concepts during the development of CIMI Models
      2. There are two outcomes of this tool use:
         1. The new concepts are added to an external code system standard (this might occur after initial publication of the CIMI model)
         2. The new concepts remain as HL7 concepts and therefore have to be managed and published by HL7
   2. Issues to decide noting that the extension will be used by CIMI in any case
      1. Should the SCT Ext tool be used by other WG? I think we should assume that all HL7 use will follow the same process
      2. What do we do with the concepts not included in an external code system?
         1. Do we export them out of the tool into MIF and publish them as another HL7 code system?
         2. Do we publish an official SCT Ext namespace?
         3. Both?
         4. Something transitional where we initially publish in MIF but then stop? Is it okay to have another way to publish HL7 code systems?
         5. Do we move other HL7 code systems to the SCT extension and retire MIF as a code system tool?

Next Agenda

1. Rob S. Provide V2 Table entry for glossary
   1. heather will be attending to help craft a unified HL7 Terminology/Vocab glossary
2. If Stan is available - more thoughts on CIMI SCT Extension as noted above
   1. Need to meet with CIMI to get the WG input.