Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendee type:

H - HTA Member

O - observer

L - liaison

Present

P - present

A - Apologies

Name

Affiliation

HPJulie JamesBlue Wave Informatics LLP
HA

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
L

Wayne Kubick

HL7 (CTO)

L
Jane MillarSNOMED International
O
Andrea MacLeanCanada Health Infoway
OPSoraya AssarMotive Medical Intelligence

...

Motion to accept proposed xxST, seconded xxDG; carried unanimously

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Management

 Quorum

Minutes ApprovalQuorum 

Quorum is met 

Motion to accept proposed 

TopicURLs for External Code Systems

There is a document started with the framework Draft Letter for URL Request

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

TO BE WORKED ON

From Zulip (RMcC) https://chat.fhir.org/#narrow/stream/179202-terminology/topic/USA.20Dental.20Code.20System.20Canonical.20URLs

  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 http://hl7.org/fhir/sid/xxx (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 https://www.iana.org/time-zones

TopicFHIR Tracker Items?Nothing when checked 2019-11-11; have things moved to JIR?

 [#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 adjournedAt   

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)