Chair:  @ Julie

Scribe: @ Julie


Attendee type:

H - HTA Member

O - observer

L - liaison


P - present

A - Apologies



HPJulie JamesBlue Wave Informatics LLP

Roel Barelds

ICT Group

HPSusan MatneyIntermountain Health
HPSylvia ThunHL7 Germany
HPCarol MacumberApelon Inc.
HPReuben DanielsSaludax
HPDavera GabrielJohns Hopkins University Institute for Clinical and Translational Research

Wayne Kubick


Jane MillarSNOMED International
Andrea MacLeanCanada Health Infoway
OPSoraya AssarMotive Medical Intelligence

Minutes of Teleconference 2019-10-15 

Motion to accept proposed ST, seconded DG; carried unanimously

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion



Minutes Approval

Quorum is met 

Motion to accept proposed 

TopicURLs for External Code Systems

There is a document started with the framework Initial Code System Request Letter

Members are welcome to start adding text to this for each paragraph, especially the paragraph about 'Brief description of the FHIR requirement for a URL'

Reuben Daniels and Caroline Macumber


From Zulip (RMcC)

  1. If the code system authority is immediately engaged and crafts a url they want and own - use that and stop
  2. If we need to create something because above is not happening fast enough, use the (or some tbd better base) where the xxx is an established (at HL7 OID site or other) short symbolic name
  3. Publish this via UTG
  4. Understand that this url can change when the steward decides to establish something that is better aligned with their domain. Obviously this is a big deal with implications, but it's a fact, as we see here. So we need a defined process to manage this and I'd except this is something HTA, with our help, will craft as the responsible entity in HL7 for external code systems. I'd like better clarity on how we technically help folks go through a transition like we see here. For now, @Eric Haas seems to describe the result of this process.
TopicCode system statement for specifications

See updated policy at General policy on the use of external code systems in HL7 standards .

Investigate the possibility of getting something direct in the IG Publishing tool Julie James

TopicISO Codes  - update

Roel has updated the ISO 3166 page on HTA Confluence.  Thanks to Roel for this excellent work.

Julie has written to ISO regarding ISO 4217 Currency codes and ISO 639 Language codes; awaiting response; then set up pages for them on the HTA Confluence

Other ISO standards to check:
ISO 11073 Nomenclature for Personal Medical Device Communications; terminology is managed through the IHE PCD Profile Rosetta Terminology Mapping Overview; used in  8.16 Resource DeviceMetric and PoC Device IG.  Julie Jamesreach out to the Med Devices group to ask about their arrangements for use of this standard (Melvin)

FHIR also uses the IANA Time Zones

TopicFHIR Tracker Items

 [#25207] Summary: Update Licence Note for Value Sets based on SNOMED GPS

Need to craft a new statement to use in the IPS Specification (and others) Caroline Macumber

AdjournmentMeeting adjourned

At 21.59 

For next meeting (if time) 1) Back to terms of reference 2) How to get vocab facilitators engaged and how to get project teams to engage with their vocab facilitator 3) How will UTG engage to bridge the gap, especially as the IG publisher and UTG become more integrated (still a way off)

  • No labels