Action: Review the GOM Section 9.10 Regarding

HL7 Terminology Authority Call

Agenda

Host:
Password: hl7termauth / Date: 2017-10-26
Time: 4pm
Timezone, USA, New York
Facilitator / Heather Grain / Note taker(s) / Heather Grain
Attendee type H - HTA Member
O - observer
L - liaison / Attendance
P - present
A - Apologies
N - not present without apologies / Name / Affiliation
H / Heather Grain / Global eHealth Collaborative
H / Rob McClure / MD Partners
H / Sandy Stuart / Kaiser Permanente
H / Jean Narcisi / American Dental Association
H / Julie James / BlueWave
H / Ted Klein / KCI Inc.
L / Jim Case / National Library of Medicine/IHTSDO
L / Wayne Kubick / HL7 (CTO)
L / Robert Hausam / Vocabulary Co-chair
L / Jane Millar / SNOMED International
Quorum Requirements Met:

1Opening

1.1Agenda Confirmation

Agenda confirmed

1.2Minutes of Previous Meeting

Minutes of meeting 28 Sept 2017.

2Membership

Action: Review the GOM section 9.10 regarding

-Membership

-Affilliate council attendee

-Non-english speaker

-There are currently observers and members, it was suggested that we have a membership type between observer and member for those who are required as they are on the agenda. Such attendees are not considered voting members. This could be appointments ‘ex-officio’.

Action: Wayne to make recommendation to change the GOM based upon the advice provided by the HTA on membership.

2.1Free Sub-Set

2.1.1Request for free subset

Action: Message to International Council – that though we wish you to use SNOMED CT – a license is needed.

Heather offered to gather previous documentation on our suggestions and expectations and share with HTA to confirm and then inform Affiliate council. – for review on next call. We have previously notified them, but need to inform them that there will be no ‘free subset’.

2.2Content Requests

2.2.1Allergy request

Actions: Rob Hausam to complete the request documentation. – Status is this going forward?

2.3Publishing

2.3.1External Terminology Web Page

Review Content Document and next stages - appendix attached.

2.4Harmonization

2.5Process Guidance to FHIR

Rapid prototyping development vs mature quality processes need to be addressed
Content issues - identified because we were looking at content and identified problems
How to retain speed but improve quality

Action: When this activity, the subset specification process, and the harmonization with the latest version of SNOMED CT is trialed the guidance documentation will be created (progressive notes are to be kept)

Status: this is active as part of UTG project.
Heather asked if UTG is dealing with management of processes where e.g. SNOMED CT information is updated (new content in a new release of SNOMED CT). Ted indicated that they are not.

ACTION: heather to check with Grahame to see if there is any progress on procedure for updates (e.g. the nutrition value set).

2.6Other Business

2.6.1Update from SNOMED International

Review of agreement report

Affiliates – display link to SNOMED CT international members

Provision of support and guidance is available from SNOMED CT international in the development of value sets.

2.6.2Watch List procedure

Watch list items to be discussed and reviewed every 4 meetings (2 months).

3Appendix: Known issues and Watch Items

3.1SNOMED CT HL7 International namespace use

HTA to determine method of operation

Decision: until the UTG project determines the method of handling new content there will be no use of the namespace.

3.2Publishing

LOINC survey instrument attribution
Policy for publishing value set definitions referencing external terminologies (current and future)
When a value set definition refers to external terminologies without listing the content we need to:
Ensure licensing requirements for use is appropriately attributed and defined
When value set definitions are published there is a need to automatically reference the page of external terminologies and licensing links for use.
Every published document will include that information.
Include in this policy and process in the external terminology web page.
Move this item to the active agenda as this is achievable.
Additionalissues associated with publishing for HTA.
The way value set definitions are persisted in the families do not have populated content about the source/owner. This field is often not populated at the moment. This is not part of the value set definition but is part of the code system specification. This includes use of reference sets or sub sets of code systems.
When producing published documents – it is necessary to identify the code system used and when this is an external code system there is a need to provide the link to the external owner.
The way the V3 ballots work – has the publishing tooling not expanding the value sets. CCDA does but others do not.
ACTION: include on agenda for publishing meeting discussion in San Diego – Heather to request this be added to the Vocab. Agenda. HTA to request this discussion. We will request that this be highlighted on the agenda for HTA. Currently Wednesday Q3 is the meeting with Vocabulary and Publishing (focusing on general publishing of vocabulary).
Inclusion of maps in publications

3.3Value Set Specification Projects

3.4Tooling

3.5FHIR content request updates

Awaiting information from Grahame G about how FHIR will update terminology resources to match the international release.

3.6policy statement on SCT allowed binding strengths in FHIR for clarification (Ted)

On hold at the moment until other processes are determined more clearly.

Ted suggested this be moved to the watch list. We need to determine semantic implications of binding strength of expansions which are subject to profiles. This issue is not restricted to FHIR.

4External Web Page Content

Reference to HTA – link

Link to the document on external vocabularies

List of terminology products and organizations with whom we have agreements

LOINC

SNOMED International

American Dental Association SNODENT

External content should be brought through Harmonization. The Harmonization and balloting process will be the trigger updates to the information provided on this page. If these requests go through harmonization the HTA can be informed and take on the liaison and organization of licensing agreements. Working Groups are not empowered to make such arrangements.

The tooling below aims to provide a quick reference to find tooling and information about external terminologies used in HL7 standards. This provides a traceable process to assist standards users.

Develop a table of information about each code system including:

Formal name of the code system

Short name or abbreviation of the code system
Owner of the code system
Technical identifier/s of the code system
Link to information about the code system – this should contain information about how to obtain the content.
IP information and Licensing - link
HL7 users of this information – e.g. HL7 product use link?
Information current as at

SNOMED CT

This is a code system with regularly released editions, an international edition, and national editions. HL7 international realm specifications shall only use the SNOMED CT international release. Realm specific specifications shall use either the international or the edition of that Realm. Use of a Realm specification outside that Realm will require specific additional licensing from SNOMED International or the National Release Centre/s of that Realm.

Full title: SNOMED Clinical Terms

Owner: SNOMED International

Scope of content (semantic space) all content relevant to healthcare

Technical Identifiers: note: this terminology requires identification of the code system and the version of the code system being used. The identifiers shown here are for the code system (and do not indicate the version)

OID - 2.16.840.1.113883.6.9
URL -

Link to information about the code system:

Licensing information

HL7 users of this information – V2.x, V3, CDA, FHIR
Information current as at: 2017 September 15

LOINC

Full title: Logical Observation Identifiers, Names and Codes

Owner: Regenstrief Institute

Scope of content (semantic space) LOINC is a common language (a set of identifiers, names, and codes) for identifying health measurements, observations, and documents.

OID - 2.16.840.1.113883.6.1
URL -

Link to information about the code system:

Licensing information

HL7 users of this information – V2.x, V3, CDA, FHIR
Information current as at: 2017 September 15