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

Subcommittee Lead: Jessica Bota 

Supporting TSMG Co-Chair: Reuben Daniels 


Tuesday 8:00-9:00PM UTC

Tuesday 4:00-5:00PM USA EDT

Wednesday 6:00-7:00AM AEST

Wednesday 9:00-10:00AM NZDT 

See for meeting details.


Attendee type:

M - TSMG Member

O -Observer / Guest


P - present

A - Apologies

X - (Apologies with Proxy)



M (Co-Chair)


Reuben DanielsSaludax


Jess Bota

Apelon, Inc.

Lisa Nelson


Michael Faughn

National Institute of Standards and Technology (NIST)
Davera GabrielJohns Hopkins University Institute for Clinical and Translational Research

Dan Vreeman

HL7 International

Ted Klein

Klein Consulting


Marc Duteau 

HL7 International

Joan Harper

Canada Health Infoway

John Snyder

National Library of Medicine

Rob Hausam


Alex Kontur

Ravi KafleWashington State Department of Health
Abdullah RafiqiICF
Hope GrayUAB - Birmingham, HL7 Intern
Martha JonesGeorge Mason, HL7 Intern

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).

Agenda Topics

Meeting was recorded

Agenda Outline

Time Allocation


Agenda Item
  • Rollcall & Proxies
  • Note that meetings are recorded
  • Agenda check
  • Progress continues to be made on integrating automated IG publisher validation into UTG process
New Business30 JB/RD
  • Handling THO anchored content in the FHIR spec FHIR-37440 - Getting issue details... STATUS  
    • Michael has completed an initial review 
      • Assumption is that resources will share <id> (we know this isn't a rule but we need something to link the resources)
      • There are 42 code systems anchored in THO that are only in the FHIR core specification
        • Need to do same analysis for value sets
        • Assume they need to be moved but would like to finish analysis
      • There are 72 code systems and 190 value sets that are potential duplicates across THO/FHIR
        • Discuss how to address changes across the following code system elements:
          • meta.lastUpdated (all) - not consequential
          • date (all) - not consequential
          • url - once moved, should all be anchored in tho
          • experimental (19) - we assume that all code systems may have been set to false upon moving to THO but this requires verification
          • title (23)
          • valueSet (70)
          • meta.profile (62) - not consequential
          • description (22)
          • publisher (18) - not consequential
          • name (8) - consequential, involve WGs if needed
          • contact (18)
          • status (17)
          • oid (25) - consequential and require cleanup, need to understand how this is happening from Grahame as there are duplicate OIDs across and within THO and FHIR (urn:oid:2.16.840.1.113883.4.642.1.0)
          • property (1)
          • hierarchyMeaning (1)
          • extensions
            • telecom
            • standards status
            • workgroup
            • fmm
          • concepts (18) - consequential, involve WGs if needed
        • Discuss how to address changes across the following code system elements:
          • name (29)
          • oid (5)
          • status (19)
          • standards-status (10)
          • title (63)
          • description (25)
          • normative-version (1)
          • experimental (159)
          • immutable (123)
          • compose.include.system (19)
          • date (180)
          • extensions 
            • fmm (25)
    • Goal is to get a list of resources we consider duplicates or easily categorizable fixes (only have non-consequential differences) and then a list of duplicate resources that need to be consolidated/resolved
      • Grahame can handle the duplicates and WGs will need to be involved in the resources that need consolidation
  • Education session for WGM (Monday lunch slot for FHIR committers)
    • Should be clear about where resources should live
    • For required bindings, the value set and associated code system should live in the FHIR spec
Subcommittee Work in Progress15JB/RD
  • THO cleanup
    • These tickets have approval from TSMG to proceed in UTG
      • Fix the "All HL7 Code Systems" tab to exclude external content UP-320 - Getting issue details... STATUS
      • Add tabs for deprecated content (based on deprecation task force) UP-321 - Getting issue details... STATUS
      • Add subtabs to categorize identifier systems
      • Add profiles and extensions to THO
      • List resources by title (currently name)
  • Execution of Deprecation representation and policy in UTG/THO
    • Deprecation Policy Framework documents policy and next steps
    • Immediate priorities
      • Perform inventory of deprecated content across THO
      • Create tabs where deprecated content exists
        1. Document deprecation and expectations around deprecation on THO subtabs
        2. Must also document retired, as there is often confusion between deprecation and retirement
      • Requested IG Publisher change to render identifier.period for CodeSystem and ValueSet:
  • Task force recommendation review and implementation (voting, quorums, WG health, etc.): UTG Task Force Recommendations to TSC 
    • Tracked by HSCR-155 - Getting issue details... STATUS and its subtasks
    • Continuing to fill OSG voter slots
      • FMG: John Moerke, Bryn Rhodes, Rob Hausam
      • CMG: Lisa Nelson, Alexander Henket, Marc Duteau
      • V2: Michael Faughn, Frank Oemig, Rob Snelick
    • Will continue to follow-up on filling Realm-based and Vocab OSGs
  • Vocab suggests that TSMG require all code systems to have a Steward
      • Vocab WG to run a query for each code system across FHIR core to identify the resources and their responsible WG(s) for each listed code system.
      • Rob Hausam reached out to Grahame to determine best way to do this
      • Might be able to use binding to determine steward by mining it out from resource that is referencing it
   Adjournment0 JBCall adjourned at 4:XXPM EDT. Next call in two weeks at 4:00PM EDT August 30, 2022.

Action items