Attendee Pass: HTAMeet
Chair: Caroline Macumber
Scribe: Reuben Daniels
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
|H||A||Julie James||Blue Wave Informatics LLP|
|H||P||Susan Matney||Intermountain Health|
|H||Sylvia Thun||HL7 Germany|
|H||P||Carol Macumber||Clinical Architecture|
|H||P||Davera Gabriel||Johns Hopkins University Institute for Clinical and Translational Research|
|L||Suzy Roy||SNOMED International|
|O||P||Andrea MacLean||Canada Health Infoway|
|O||P||Ted Klein||Klein Consulting / HL7 UTG / Vocabulary WG CoChair|
|O||P||Rob Hausam||Vocabulary WG CoChair|
|L||P||Rob McClure||US Realm Liason|
|O||P||Carmela Couderc||Vocab WG CoChair|
Minutes of Teleconference 2020-06-24
Motion to accept proposed and accepted.
Meeting Minutes from Discussion
Quorum is met
Motion to approve Minutes proposed
Roel moves, Devera seconds: Motion 10-0-0
Any others wish to volunteer for re-election...to balance the "turnover"? Julie is happy to volunteer (as I think it's my position that's unbalanced things as it is)
Wayne has reached out:
|Topic||External SDO Issues or additional topics||Continuous|
Carol and Suzy Roy
and Sara Armson
From the last meeting: Suggested wording for Co-Chair List announcement
Title: Updates to Licensing for LOINC and to the HTA External Terminologies Content
Body of email:
The HL7 Terminology Authority (HTA) is notifying all co-chairs of HL7 WG that LOINC has, this June, updated its license agreement for use of the LOINC - Logical Observation Identifiers, Names and Codes - terminology. Specific wording must be used in any product or service utilizing LOINC; this wording is provided for you in the "Arrangement or agreements with HL7 for use of content" on the LOINC - Logical Observation Identifiers, Names and Codes page of the HTA External Terminologies pages.
Since many of our HL7 products reference the use of LOINC, this is of relevance to most of you; please communicate it within your WG and especially to all how are working on materials for ballot and/or publication.
The HTA is also taking this opportunity to update you about recent new content additions to the External Terminologies - Information pages on Confluence. These include the Dartmouth Atlas of Health Care, ICD-10-PCS, International Standard Classification of Occupations 2008 (ISCO-08)
Please check, and if OK, Julie will post to the Co-Chair list
|Topic||Code system "stub" creation||New||Carol/Reuben|
Support of implementer community process for creation of code system "stubs" and expected interaction with HTA"
Overarching question - Who has the official responsibility of governing the creation of these external codesystem stubs?
Suggestion from Julie to take the discussion forward:
1) Obviously history influences a current situation. The requirement is to learn from history and do better, not repeat it. My personal observation on the discussion from last meeting was that "we" have inherited issues that technology (specifically in the MIF) "created" - that are the main terminology using community both were and are largely unaware of and which had little if any value to their business.
2) Continuing to "maintain" (using that in its broadest sense) content that is "unreliable" is unwise, and in the long run is a disservice to the community we aim to serve. There was a desire to "clean up" stubs but there was no sense of who would be responsible for this.
3) Suggestion: develop a governance and maturity process for external code system use for code systems not on the HTA pages (yet) This may be very naive, but having sat through all the discussion last meeting, if this is too naive, maybe our existing set up is too complex ?
a) Have a "table" with minimum information requirements to "get things to work" especially for FHIR processes (siting a code system, or referencing one via a value set); without this - no content; no new code system "stub" resource in UTG. Use the HTA pages framework as initial - use MUSCOW for the various sections.
b) Set time frame for full content as per HTA pages to be provided using the HTA process. If not provided, then code system resource stub gets "retired" (hope that is possible!)
For "old content" - start a retirement process......Ask the community about use of code system....if no response....retire.
Need a process for communicating with the FHIR Community on potential breaking changes regarding external terminologies - advance warning etc. (ref NUCC codes)
Discussion needs to centre on having a plan to then put forward to Grahame and the FHIR community
|Topic||Update to new PSS Process||New||Julie/Wayne|
Currently the process has this:
How should the question read? Should we create a pick list based on the external systems listed in vocabulary.hl7.org or the HTA page instead of asking people to list the terminologies?
All external terminologies should be registered with HTA
Picklist of known external terminologies is ideal. When the external terminology is no in the list, they pick other and use free text.
Group feels strongly that we should extend this data capture to NIB.
ENDED CALL HERE
Julie: I have not done anything further about this..... please indicate what we might suggest....
|Topic||When a code system is not a code system||New||Julie|
Discussion of when a code system is not a code system but is a syntax….
|Topic||Discussion with FHIR - Managing change in code system identification||Report||Reuben|
Agreement was reached that one central place must be designated for management of external code systems, and Austin, Wayne, Grahame and Reuben all agreed that UTG was the correct place. However, there are issues with external code system content in the first content relase of UTG, and those need to be addressed before additional content can be migrated (including existing FHIR non-ballot bound terminology).
Need to start here at next meeting
Call adjourned at 20:00 UTC
- Reuben Daniels create the ISCO-08 Page
- Reuben Daniels to check with Joshua Procious to determine if we can transfer tickets from FHIR or UTG project to the HL7 JIRA project
Julie James will draft a note to co-chair list reintroducing the External Terminologies pages, pointing out LOINC update as an example, seeking feedback on changes and pointing out recent new additions (Dartmouth Health Atlas, ICD10PCS, ISOC-08 etc..)
- Julie James to create agenda for next joint on 08 July 2020
- 8-Jul-2020:Davera Gabriel will run with NCI Thesaurus vs NCI Meta-thesaurus matter.