Chair: @ Julie James
Scribe: @ Julie James
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
Global eHealth Collaborative
|American Dental Association|
|H||P||Julie James||Blue Wave Informatics LLP|
|H||A||Susan Matney||Intermountain Health|
|H||Sylvia Thun||HL7 Germany|
Minutes of Teleconference 2019-07-09
Motion to accept proposed HG and seconded JN.
Meeting Minutes from Discussion
Quorum was met (just)
Motion to accept proposed HG and seconded JN. Carried unanimously
|Topic||AHA Terminology use in HL7 publications||Follow up; JMJ will undertake tasks needed to get the 3 steps outlined in the last meeting actioned|
Happened last week; not sure if any HTA members were able to attend.
|Topic||SNOMED CT content request dates||Email sent to co-chairs 22 July 2019|
|Topic||Realm Transferable Standards Specifications project|
Any further discussion/notes in the document on the ARB site
No further action required until an updated proposal is received by HTA.
|Topic||Update to GOM and Liaison with TSC -|
In development: HTA Updated ToR
For the GOM.....general procedures regarding HTA needs to be in the GOM.....how do I do X for terminology would not currently have any help in the GOM.
Members on this call were comfortable that JMJ reach out to TSC with the aim of improving dialogue between HTA and TSC and getting better terminology processes "mandated" through TSC. This might include asking for HTA presence at part of the TSC meeting on the Saturday prior to a WGM.
|Topic||Identification of code systems policy -|
How do we structure the URL for code systems?
We need a policy on the procedure and then the process. A policy outline was discussed below - this needs to be more fully documented.
Must be in harmony with the external code system management processes we have already
First, we document the process of how to get a canonical URL from a code system that has one
Second, we set up something like a pro forma to request code systems to provide a canonical URL, including why HL7 needs one (and be included on the form to collect external terminology data). This may need to include guidance to the code system owner about how to establish a canonical URL
We feel, given our understanding of what a canonical URL represents, it is not acceptable for anyone other than the code system owner to issue a canonical URL.
FHIR tracker items in H Group for HTA consideration - they are all external code system use requests
We looked at this briefly and most relate to the canonical URL issue.
We need to have the FHIR Tracker Group H review as a regular agenda item.
No further news at this time.
|Adjournment||Meeting adjourned||At 9.50pm BST|