Attendee Pass: HTAMeet
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
|H||P||Julie James||Blue Wave Informatics LLP|
|H||P||Susan Matney||Intermountain Health|
|H||P||Sylvia Thun||HL7 Germany|
|H||P||Carol Macumber||Clinical Architecture|
|H||P||Davera Gabriel||Johns Hopkins University Institute for Clinical and Translational Research|
|L||P||Suzy Roy||SNOMED International|
|O||P||Andrea MacLean||Canada Health Infoway|
|O||Ted Klein||Klein Consulting / HL7 UTG / Vocabulary WG CoChair|
|L||P||Rob Hausam||Vocabulary WG CoChair|
|O||Mareike Przysucha||HL7 Germany|
|L||P||Rob McClure||US Realm Liaison|
|O||(P)||Rory Davidson||SNOMED International|
Minutes of previous teleconference (2021-06-23)
Motion to accept DG and CM seconded;
Meeting Minutes from Discussion
TC Minutes Approval
Quorum was met
Motion to approve Minutes:
DG moves, CM seconds: Motion 4-0-0
Check here: https://confluence.hl7.org/display/PS
External SDO and Code System Issues
IMO terminology - check if in THO already; if not, tag Jess on the page
Update on WHO (Julie)
<<So I was invited to a meeting in Geneva in late 2019, regarding a WHO FHIR initiative. While I was there, I ran into Robert Jakub, who was also at the meeting, and talked to him about two different issues: that HL7 needs some practical license to support publishing IGs that mention who terminologies, and include codes from them, and that we need to figure out how ICD-11 works on a FHIR terminology server
With regard to the first, mainly I was explaining that we're in some intermediate space - we're pretending to use the terminologies, so that other people can use them properly, and also hosting validation tooling. With regard to that discussion, a few weeks ago he sent me their agreed license for icd-11, a variation of creative commons. It had some particular requirements added, and I and Michael Lawley pushed back hard on one of them (all ICD-11 value sets must include UUIDs as well as codes). He hasn't responded to that yet. I believe that we are treating this as a template for other WHO terminologies, but he hasn't confirmed that in writing. I have no problem with HTA pushing that same issue; I don't have any particular desired outcome other than that HL7 published IGs can use the WHO terminologies that they need to, without licensing making that impossible (where we appear to be now)
The second, that's been a more active discussion - Michael Lawley and I have hosted ICD-11 on our servers, and figured out what that looks like, and iterated with Robert and Can Celic on the details - what are code systems? what properties? what filters? I proposed some possible URLs for code system URLs, and said that he was code system owner, so he would choose. He chose who.int namespaces, from memory - I can't check while I'm on holiday. Anyway, all this was effectively research from my perspective; I can't put iCD-11 up on my public terminology server because of the licensing issues.
The second, that's been a more active discussion - Michael Lawley and I have hosted ICD-11 on our servers, and figured out what that looks like, and iterated with Robert and Can Celic on the details - what are code systems? what properties? what filters? I proposed some possible URLs for code system URLs, and said that he was code system owner, so he would choose. He chose who.int namespaces, from memory - I can't check while I'm on holiday. Anyway, all this was effectively research from my perspective; I can't put iCD-11 up on my public terminology server because of the licensing issues. >>
HTA response: Important to communicate with each other when we're dealing with external terminology owners. HTA has a template and a process and has been working this with Robert and Can, not just for ICD11 but also the other WHO terminologies. Please check International Classification of Diseases 11th Revision as we have already put this through the formal process quite recently. We stopped because there was some confusion coming back "about what Grahame was doing with WHO". Given your clarification, and that the HL7 community needs all the terminologies, not just ICD, and given what you have said, we will continue to work directly with WHO using our template for the process.
Sylie: and colleagues in Germany (from last HTA meeting) to reach out to Robert and Can and remind them of what they did with HTA for ICD-11 and ask for the same process for ICF etc. The clear message for WHO is that the need to work with the HTA for how to use their terminology in HL7 standards, especially as they are moving towards using FHIR in their services.
We should also Garrett Mehl for WHO Digitial Health Technology - the CIEL (Columbia International eHealth Laboratory)
Rob McC: We must have a process that will support change, especially to get out of space where we are so challenged by having "incorrect" URIs etc.
CCC Nursing Classifications - split into Diagnosis and Intervention; should the concepts be represented as two different code systems with two different code systems identifiers. The content contains "two different aligned taxonomies" the CCC of Nursing Diagnoses and Outcomes, and the CCC of Nursing Interventions and Actions. But the same code is used for concepts in the two different contexts, giving two different meanings. The code system is now by managed by HCA....(Jane Inglebright)...Carol could reach out on this.
The definition of the Value Set is in the CI build of THO. The value set is extensionally defined, so it consists of the 26k concepts. But this (THO) is not an expansion; services cannot be run from it.
|Topic||HL7 Terminology Services Management Group||Ongoing||Reuben |
Final meeting of subgroup has happened and a proposal has gone to TSC for eVote/discussion next Monday in order to get a decision before the "retreats". The TSMG will be allowed to set policy; the exact ringfencing of the "policy area" has not yet been defined. Should be announced for September WGM
TSC eVote: TSC e-Vote 2021-07-05
TSC eVote Proposal: Terminology Services Management Group Proposal
|Topic||UTG/THO Update||Continuous||Jess and Reuben|
|Topic||Updated CS Identifier process guidance||New||Carol|
Carmela has offered to improve upon the current document process for external stakeholder engagement to procure CS identifiers.
The draft is located here: Validating and Requesting Identifiers for External Code Systems and Identifier Systems
HTA members and observers are asked to review the drafted text, directly edit where changes are needed and use the comment functionality to ask additional questions. We will review again (and hopefully approve on the next HTA call, which will be at the WGM).
|Topic||Any Other Business||Continuous||Julie|
Julie on Holiday.....chairs for next 2 meetings? 21/7/21 Carol can chair
If no chair for 4/8/21 will cancel
Call adjourned at 21.05 BST