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

Presence:

P - present

A - Apologies


Name

Affiliation

H

A

Heather Grain

Global eHealth Collaborative

H

P

Rob McClure

MD Partners

H

A

Jean Narcisi

American Dental Association

H

P

Julie James

Blue Wave Informatics LLP

H

P

Roel Barelds

ICT Group

HASusan MatneyIntermountain Health
HPSylvia ThunHL7 Germany

L


Wayne Kubick

HL7 (CTO)

L


Robert Hausam

Vocabulary Co-chair

L


Jane Millar

SNOMED International

L


Carol Macumber

Vocabulary Co-Chair

L
Ted KleinVocabulary Co-Chair
L
Russell HammVocabulary Co-Chair




Minutes of TC 2019-01-31 Approved as on Confluence

Motion for acceptance of the Minutes of the previous TC was proposed by RmC and seconded by RB; the motion was carried: For 3; Abstain: 0: Against 0



Agenda Topics

Agenda OutlineAgenda ItemMinutes from Discussion
TopicGeneral policy on the use of external code systems

The group reviewed the content below:

  1. Where ever possible HL7 artifacts that reference coded content should use externally managed, established, curated concepts made available as a versioned code system (or can be a subset of said code system) that is
    1. Follows good vocabulary practices as defined by HL7 e.g.
      1. Have definitions for each concept and the relationships it uses
      2. Uses meaningless identifiers
      3. Manages synonymy
    2. Under the curation of an established organization that is committed to maintaining the code system content, i.e. a terminology authority (see also ISO/TR 12309:2009
      Health informatics -- Guidelines for terminology development organizations) and particularly
      1. Either provide, or work with HL7 to establish an identifier for the code system
      2. Provide a current human contact for the content and a link to a source for the content
    3. Has established processes for content improvement
    4. Has straightforward licensing requirements
    5. Provides easy access to the code system content, either directly or through shared terminology services, including having the current version available to support publishing and maintenance of those published artifacts
    6. Is well established for use to describe the concepts in question (i.e. well established for use in the context of the concept domain)
    7. If alternatives are available, code systems that have low or no cost for use are preferable
  2. Any publication or draft HL7 artifact that references an external code system must:
    1. Clearly identify the external content:
      1. as governed by IP restrictions beyond those of HL7 and
      2. that any use of the content beyond review of the HL7 artifact for implementation requires the implementer adhere to the IP requirements of the owning organization.
    2. Provide a web-link to the licensing information for the content and/or provide a short description of the requirements
    3. References the code system version when the artifact is published, and whether the version for use is important for the artifact

The above will be reviewed on the next meeting of the HTA

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
TopicHL7 Terminology Portal - to be carried forward to next meeting

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.

http://www.hl7.org/portal/index.cfm?ref=common

TopicNew S-I Collaboration Agreement - to be carried forward to next meeting

Review of the agreement; any changes to be made

http://www.hl7.org/documentcenter/public_temp_33BC7CE3-1C23-BA17-0C8EB47075B9F62D/mou/IHTSDO_CharterAgreement.pdf

TopicPublication 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

Policy on use of Retired or Legacy HL7 Code Systems

ManagementUpdate on HTA Confluence site tidy up

Teleconference section has been done.

Documents to be done next

  • No labels