This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Vocab TQA Minutes"
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
CALL IN is standard Vocab HL7 number. 1 770-657-9270, Participant Passcode: 598745 | CALL IN is standard Vocab HL7 number. 1 770-657-9270, Participant Passcode: 598745 | ||
10a – 11:30a ET | 10a – 11:30a ET | ||
− | Attendees: Rob McClure, Rob Snelick, Susan Barber | + | Attendees: Rob McClure, Rob Snelick, Susan Barber, Stan Huff |
Standard Vocab quorum requirements: 1 Project lead or Vocab chair and two participants was met. | Standard Vocab quorum requirements: 1 Project lead or Vocab chair and two participants was met. | ||
===Agenda for 2/22/16=== | ===Agenda for 2/22/16=== | ||
Line 39: | Line 39: | ||
###Continue discussion of CIMI SNOMED CT Extension Namespace | ###Continue discussion of CIMI SNOMED CT Extension Namespace | ||
===Discussion=== | ===Discussion=== | ||
− | # | + | # Worked on Reference page table of terms to define x 40 min |
− | # | + | # Discussed SNOMED CT extension x15min |
+ | ##CIMI use the SCT Ext for the following activities: | ||
+ | ###As a tool to capture needed concepts during the development of CIMI Models | ||
+ | ###There are two outcomes of this tool use: | ||
+ | ####The new concepts are added to an external code system standard (this might occur after initial publication of the CIMI model) | ||
+ | ####The new concepts remain as HL7 concepts and therefore have to be managed and published by HL7 | ||
+ | ##Issues to decide noting that the extension will be used by CIMI in any case | ||
+ | ###Should the SCT Ext tool be used by other WG? I think we should assume that all HL7 use will follow the same process | ||
+ | ###What do we do with the concepts not included in an external code system? | ||
+ | ####Do we export them out of the tool into MIF and publish them as another HL7 code system? | ||
+ | ####Do we publish an official SCT Ext namespace? | ||
+ | ####Both? | ||
+ | ####Something transitional where we initially publish in MIF but then stop? Is it okay to have another way to publish HL7 code systems? | ||
+ | ####Do we move other HL7 code systems to the SCT extension and retire MIF as a code system tool? | ||
+ | |||
+ | ====Next Agenda==== | ||
+ | # Rob S. Provide V2 Table entry for glossary | ||
+ | # If Stan is available - more thoughts on CIMI SCT Extension as noted above | ||
+ | ##Need to meet with CIMI to get the WG input. |
Revision as of 20:12, 22 February 2016
Backto Main Page
Contents
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
- Admin
- Call planning.
- Confirm Co-sponsor participants
- Vocab is Ted and Rob McClure
- HTA – Heather
- CIMI – Stan
- SD/CDA – Lisa
- V2 – Rob Snelick
- V3 – Woody
- FHIR – Lloyd
- Continue work of identifying critical terminology issues for HL7 products documented on Requirements page
- Discussion on best approach to begin collecting information on QA issues across products.
- Continue discussion of CIMI SNOMED CT Extension Namespace
Discussion
- Worked on Reference page table of terms to define x 40 min
- Discussed SNOMED CT extension x15min
- CIMI use the SCT Ext for the following activities:
- As a tool to capture needed concepts during the development of CIMI Models
- There are two outcomes of this tool use:
- The new concepts are added to an external code system standard (this might occur after initial publication of the CIMI model)
- The new concepts remain as HL7 concepts and therefore have to be managed and published by HL7
- Issues to decide noting that the extension will be used by CIMI in any case
- Should the SCT Ext tool be used by other WG? I think we should assume that all HL7 use will follow the same process
- What do we do with the concepts not included in an external code system?
- Do we export them out of the tool into MIF and publish them as another HL7 code system?
- Do we publish an official SCT Ext namespace?
- Both?
- Something transitional where we initially publish in MIF but then stop? Is it okay to have another way to publish HL7 code systems?
- Do we move other HL7 code systems to the SCT extension and retire MIF as a code system tool?
- CIMI use the SCT Ext for the following activities:
Next Agenda
- Rob S. Provide V2 Table entry for glossary
- If Stan is available - more thoughts on CIMI SCT Extension as noted above
- Need to meet with CIMI to get the WG input.