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

Chair: Caroline Macumber 

Scribe: Davera Gabriel 


Wednesday, February 16, 8:00-9:30PM UTC

Wednesday, February 16, 3:00-4:30PM USA ET

Thursday, February 17, 6:00-7:30AM AEST

Thursday, February 17, 9:00-10:30AM NZDT   

Zoom link -

Find your local number:


Attendee type:

M - TSMG Member

O -Observer / Guest


P - present

A - Apologies

X - (Apologies with Proxy)



M (Co-Chair)PClinical Architecture
M (Co-Chair)PThe Johns Hopkins University
M (Co-Chair)PSaludax
HL7 International
M (TSMG Rep to the TSC)
MD Partners, Inc.

P (first 60 minutes only)

Carol Proxy for last 30

MX (Proxy: Reuben)Apelon, Inc.
M(conflict w first 30 minutes)MaxMD
MPNational Institute of Standards and Technology (NIST)
Mabsent first 60 minutes, Reuben proxyHL7 New Zealand
MPPrecipius b.v.
HL7 Germany
Health Intersections
Canada Health Infoway
National Library of Medicine
Hausam Consulting LLC
OPSNOMED International
Joe FlackJohns Hopkins BIDS
Office of the National Coordinator for Health Information Technology (ONC)
John SnyderNational Library of Medicine (US)
Ted KleinTK Consulting

Antitrust statement

Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).

Minutes Approved as Presented 

2022-02-09 TSMG Agenda and Minutes

This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."

Agenda Topics 

Meeting was recorded

Agenda Outline

Time allocationLead

Agenda Item

  • Note that meetings are recorded
  • Welcome to members and observers


  • Announcements 
  • Policy & Process Documentation Repository
    • Requirements
    • Disposition - library approach
    • Each TSMG Subgroup should have their own pages
      • HTA pages will be linked (& stay where they are)
      • Reuben created draft stub for these pages here
        • Review table heading  / column definitions
        • Status from subcommittees
  • HTA description verbiage in GOM and on this page have been updated 
TSMG Standing Subcommittee Updates

  • TSMG Education / Outreach subgroup regular meetings
    • Doodle Poll: 2 replies
    • Tues-Thurs 2-3 EASTERN
      • Any preferences? (Lisa?)

  • OMOP + FHIR harmonization group
    • Project Planning documentation underway - (DV / FE)
    • May Connectathon / WGM activities planned
      • dQM & Oncology Use Cases: May Connectathon activities
      • BoF session in WGM
    • dQM: AMIA Plenary Proposal (March / November), NCQA DQS, CMS Connectathon (July)

  • May Connectathon Management
    • Planning committee meeting Tuesday 21Feb
      • proposed global workflow for Terminology Management

      • chat with David Hay about what we need in Connectathon Management tool
    • All Track leads:  sign-up requirements
      • Declare terminology servers required / identified
      • Additional sign-up requirements from TSMG?
    • IG / Track Workflow
    • Terminology Services track offerings

  • Progress with UTG Oversight Groups - Outreach next steps

  HL7 Terminology Authority10


  HL7 Terminology / Unified Terminology Governance (THO/UTG)10RD/JB
  • Freeze for release v3.1.0 scheduled for 2/20
    • Concerns about timing as there are many high priority tasks that require implementation/approval prior to the freeze 
      • Being slowed down by build issues from new IG Publisher update
        • Ted reports there is some debugging required as of early this am & states
          • This is causing a problem: <name value="PassportNumNS_AFG"/>  this needs to be addressed in order to resolve the ticket below
    • Jess moving Identifier Systems to THO, Lloyd to help with moving Passport Numbers 
      • Almost complete but ran into build issues: UP-285 - Getting issue details... STATUS
    • Reuben moving "Using X with FHIR" pages to THO
      • 15-Feb-2022 Updates
      • UP-289 pro forma UTG ticket raised and associated branch in bitbucket created.
      • Issues
        • The agreed table has a column for links to external Code System Metadata Records in THO. However, some of the code systems with a "Using With FHIR" page do not have corresponding metadata records in THO. Specifically, MED-RT, NCI Metathesaurus, Unique Ingredient Identifier (UNII). Do we simply state that there is no metadata record in for these?
        • The Using ICD With FHIR page refers to multiple versions of ICD, accordingly there are multiple URI and OID values (depending on the variant). I have opted to not provide a single URI or single OID and stated Check metadata record instead.
        • The Using NDF-RT With FHIR page (in the FHIR spec) states that NDF-RT should not be used in favour of MED-RT. Accordingly, I will not migrate this page.
        • ISO-3166 has multiple OIDs and URIs.
        • Incorrect data in Using With FHIR Pages
          • Noting that some of the Using X With FHIR pages have information which is in conflict with HTA confluence pages and HTO metadata records, do we correct the FHIR pages?
          • Errata / typos
          • Data which refers to part of the FHIR specification e.g. ValueSets which use the particular code system.
          • Do we correct these now, or in a future release of THO?
        • Should we have a note which states that if information in the table or in the Using With HL7 Standards pages themselves are in conflict with the a Code System Metadata Record then the Code System Metadata Record is authoritative? 
        • RD: Moves that a statement asserting if there is a conflict between the "Using xxx code system on FHIR pages" and the code system entry in the THO metadata record, that the latter is the authoritative source. Seconded: DG  Motion passes 7-0-1
  • Vocab WG follow-up: Policy Requiring Identification of Stewards for HL7 (Internal) Code Systems
    • Vocab WG should decide whether THO code systems and value sets should have the steward as mandatory.
      Would help with knowing who to follow up with in the UTG process.
    • In Vocab WG - Motion passed: Vocab WG recommends that TSMG implement a rule stating that:
      Every HL7 code system in THO must have a steward WG.  The steward WG has to be one of the WGs that are authorized to propose making changes to an HL7 code system in THO. 
  • THO release schedule
    • THO was originally designed to be released "on demand" although there has been a recent push to align with ballot cycles
    • Should ask Dan and Viet to weigh in as it affects the implementation community
      • RD: suggesting there are 3 dates per year guaranteed, and then provide the flexibility to add additional releases on an ad hoc basis based on community needs.
      • PJ:  there are some changes out of HL7 control like external code systems that may by necessity trigger a release
      • TK: external code system changes are mostly metadata, the most important component which may rise to the need for a change would be if a url changed
      • optimally... be dependable but also nimble to be responsible to the community needs
      • RD:  to BR - please ask the TSC about this topic / approach, so TSMG can vote on this next week
      • 15-Feb-2022: 
        • Main points from yesterday's subcommittee call below, more discussion required to determine path forward
          • There are concerns that HL7 doesn't have the resources to commit to the number of releases (three per year plus ad hoc if needed)
          • TSC needs additional understanding about tasks and the process for publishing a THO release
            • Most of it is documented and will be followed for the 3.1.0 release
          • Release takes about 3 days (i.e., waiting for builds), heads down time is about 8 hours
            • Very dependent on the IG Publisher, has taken up to 2.5 weeks in the past
          • Suggestion not to release if not enough changes have been implemented in the CI
          • THO is changing functionally with each release and is hard to release, that makes it hard to estimate freeze dates
            • Will be easier to create a schedule once UTG/THO is more stable, then can focus on consistent/reliable delivery
          • This decisions should involve TSC and HQ
  • Status updates (no changes from last week)
    • Onboarding new development resource, Lawrence, to help with Jira automation 
    • Will create business requirements for a UTG Editor
    • Sprint 2 of UTG Jira development items with a focus on release tracking in progress
      • Refining current implementation of release tracking
Technical Steering Committee (TSC) matters10RM
  • Decision Making Practices

Supporting Documents

Outline Reference

Supporting Document

Minute Approval2022-02-09TSMG Agenda and Minutes