Page tree
Skip to end of metadata
Go to start of metadata

Chair:  @ Julie James

Scribe: @ Julie James

Attendees

Attendee type:

H - HTA Member

O - observer

L - liaison

Present

P - present

A - Apologies

Name

Affiliation

HP

Heather Grain

Global eHealth Collaborative

L

Jane Millar

SNOMED International

HP

Jean Narcisi

American Dental Association
HPJulie JamesBlue Wave Informatics LLP
HA

Rob McClure

MD Partners

L

Robert Hausam

Vocabulary Co-chair

HA

Roel Barelds

ICT Group

HASusan MatneyIntermountain Health
H
Sylvia ThunHL7 Germany
LA

Wayne Kubick

HL7 (CTO)





Minutes of Teleconference 2019-07-09 

Motion to accept proposed HG and seconded JN.

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Management

 Quorum

Minutes Approval

Quorum was met (just)

Motion to accept proposed HG and seconded JN.  Carried unanimously

TopicAHA Terminology use in HL7 publicationsFollow up; JMJ will undertake tasks needed to get the 3 steps outlined in the last meeting actioned
TopicHarmonisation

Happened last week; not sure if any HTA members were able to attend.

TopicSNOMED CT content request datesEmail sent to co-chairs 22 July 2019
TopicRealm 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.

TopicUpdate 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.


TopicIdentification of code systems policy  - 

https://chat.fhir.org/#narrow/stream/179202-terminology/topic/DICOM.20providing.20FHIR.20CodeSystems.20and.20ValueSets

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.

  • Provide a mechanism to ask for a code system URL - asking HTA for this
    • does this code system have a canonical URL
      • if yes - what is it?
      • If no - obtain and test the canonical URL, confirming that it is acceptable to the code system owner.   
    • is a FHIR terminology service provided using the canonical URL

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.

TopicFHIR Terminology  

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.

TopicMembership

No further news at this time.

AdjournmentMeeting adjournedAt 9.50pm BST
  • No labels