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

Chair:  @Julie James

Scribe: @ Julie James Rob McClure

Attendees

Attendee type:

H - HTA Member

O - observer

L - liaison

Present

P - present

A - Apologies

Name

Affiliation

H

Heather Grain

Global eHealth Collaborative

L

Jane Millar

SNOMED International

HP

Jean Narcisi

American Dental Association
HPJulie JamesBlue Wave Informatics LLP
HP

Rob McClure

MD Partners

L

Robert Hausam

Vocabulary Co-chair

HP

Roel Barelds

ICT Group

HASusan MatneyIntermountain Health
HASylvia ThunHL7 Germany
L

Wayne Kubick

HL7 (CTO)

OPAndrea MacLean (InfowayInfoway

Minutes of Teleconference 2019-05-28 Approval as on Confluence

Motion to accept proposed JN and seconded RB ; all in favour.

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Management Minutes ApprovalMotion to accept proposed JN and seconded RB ; all in favour
TopicRealm Transferable Standards Specifications project

Review and prepare for joint call with ArB

There was a long discussion among participants noting that the document is a bit unclear as to its core purpose.  Is it focusing on

  • what is necessary to use a realm-specific IG in a different realm
  • or is it about the criteria that SHALL be met to be considered a Universal realm IG

The HTA did not see the need to address the former issue, but being more clear about criteria for a universal realm may be useful.

For terminology, it may not acceptable to bind to a particular terminology, even when that is globally applicable - for example a required binding to LOINC because in the UK the NHS might need to use SNOMED CT instead.   

Terminology is not the only situation where misalignment on required aspects may occur.  One possible solution/mechanism would be to allow a universal IG to be cloned for use in a realm that can not align, but that HL7 would ballot and review to "certify" that the realm-specific clone is consistent with the universal.  Finally, HTA would like to clarify at what level the 'universalness' must apply.

Note also the CIMI PSS for Vital Signs in FHIR - not discussed

TopicUpdate to GOM and Liaison with TSC  - not discussed

In development: HTA Updated ToR


TopicIdentification of code systems policy  - not discussed

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

TopicFHIR Terminology  - not discussed

FHIR tracker items in H Group for HTA consideration - they are all external code system use requests

Likely to be carried forward

Adjournment
Adjourned at 5pm ET
  • No labels