Chair: Julie James
Scribe: Julie James
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
Global eHealth Collaborative
American Dental Association
Blue Wave Informatics LLP
|H||Present||Susan Matney||Intermountain Health|
|H||Apologies||Sylvia Thun||HL7 Germany|
Minutes of TC 2019-02-14 Approval as on Confluence
Motion for acceptance of the Minutes of the previous TC was proposed by RB and seconded by JN; the motion was carried: For 4; Abstain: 0 Against 0
Minutes from Discussion
|Management||Meeting timing||For the next call, 31 March 2019, when the rest of the world has not yet changed to summer time, we will meet at 21.00 UTC (5pm EST)|
|Topic||SNOMED CT IPS Free Subset|
See email thread from Florent Desgrippes, ASIP Santé
JMJ has responded to ASIP Santé separately over the French use of SNOMED in collaboration with Jane M.
RMcC: Use of SNOMED content in any standard is SNOMED's responsibility. As HTA, we have already worked out with SI how to use S-CT in standards development.
|Topic||Characteristics of Realm Transferable Standards Specifications|
Characteristics of Realm Transferable Standards Specifications SGB and ArB
Developing guidance for the criteria for something targeted as a universal standard, compared to what should be considered a realm-specific (for SGB/ArB).
For terminology binding, an exemplar value set that is actually realm specific is "OK"in a universal standard or IG; this may be using content from a code system that some realms cannot use, either because the content is inappropriate or because it is under license.
Suggest that HTA send this guidance to the ArB for their draft and request that, if the PSS goes forward to a project with deliverables, that they ask HTA for guidance/direction on the use of terminology artifacts in the universal realm.
JMJ to contact ArB.
|Topic||General policy on the use of external code systems|
The group reviewed the content below:
The above will be reviewed again with the plan to publish after this call
Proposal to publish on Confluence: Proposed RB, seconded RMcC; For 4; Abstain: 0 Against 0
JMJ to ask HQ to send out notification to cochair list
Note: "good vocabulary practices as defined by HL7" appear not to be currently documented; this may be a future task for the HTA/Vocab WG
|Topic||HL7 Terminology Portal|
Previous discussion: The portal was created by HQ. The wording needs a lot of work, and the content at present is entirely focused on SNOMED, or alternatively accept this is only about SNOMED and change the title of the portal.
DIscussion: HTA - we don't want this to only be SNOMED. However, this page content as it is could be used as a landing page for the SNOMED part of the whole portal.
We can start to use our page on Confluence to collate the content we want, then give that to HQ to update; see: External Terminologies - Information
Also, point to mapping between code systems but must document the use case(s) for the mapping
HQ did write to WHO regarding licensing etc.; did not have a response so recontacted, with formal statement that "unless we hear" we assume that the information we provide to our community about the code system is OK
We will work through 1-2 per meeting
|Topic||New S-I Collaboration Agreement - to be carried forward to next meeting|
Review of the agreement; any changes to be made
|Topic||Publication of Policy on Retired or Legacy HL7 Code Systems - to be carried forward to next meeting|
email from 20190206 19.41 UTC
1) HTA - Communicate the policy to TSC, begin conversations on how the policy can be enforced
2) HTA – Confirm where the policy should permanently live with necessary HL7 parties
|Management||Update on HTA Confluence site tidy up|
Documents to be done next - outstanding action for JMJ