Jess Bota

Lisa Nelson

Michael Faughn

Dan Vreeman

Ted Klein

Marc Duteau 

Joan Harper

John Snyder

Rob Hausam

Alex Kontur

• Continuing to work with Lawrence Gerstley on Jira automation for submitters
  
  • Working on adding ability to perform automatic validation using the IG Publisher upon submission of proposed changes
• Ted completed adding release labels to previously implemented UTG tickets
  • Finalizing the documentation for the Terminology Curator to specify how to add the release labels moving forward
• Following the WGM, there will be two UTG/THO subcommittee calls that meet on alternate weeks using the same time slot
  • One call will focus on UTG/THO policy/process
  • Other will focus on reviewing tickets in Consensus Review

• THO cleanup
  
  • These tickets have approval from TSMG to proceed in UTG
    
    • Fix the "All HL7 Code Systems" tab to exclude external content
    • Add tabs for deprecated content (based on deprecation task force)
    • Add default value of 'true' for all code systems without a <caseSensitive> element (mainly external code systems) unless otherwise specified to resolve warnings in THO
  • Need to start discussions (with FMG?) about having ability to render extensions in THO
    • Ask Reuben to follow up
• 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 agreed to follow up 
    • CMG: Lisa Nelson, Alexander Henket
      • Lisa following up 
    • V2: Michael Faughn, Frank Oemig, Rob Snelick
  • Will continue to follow-up on filling Realm-based and Vocab OSGs
• THO release schedule
  • Need input from TSC/HQ and they have requested some information from TSMG on documentation and level of effort 
    • Info sent to Rob and Bryn who will follow up with TSC
• Vocab suggests that TSMG require all code systems to have a Steward
  • UTG submitters would need to get WG approval from the Steward to propose changes to the code system
  • Discussed on main TSMG call but no one wanted to make a motion to make this a policy
  • Steward definition
    • The WG responsible for the maintenance and upkeep of the code system (not to be confused with Publisher who makes the content available)
      • This implies that the WG has the domain expertise/knowledge related to the code system
    • The primary point of contact for questions or issues with the code system
  • FYI: Vocab added an extension for steward, there is a proposal to update the definition of publisher (which was intended to represent steward) and remove the extension
  • Might be a good idea to get a count of how many code systems in THO do not have a steward value
    • <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="inm"/> </extension>
  • Michael Faughn performed analysis on the number of code systems without a Steward value
    • Out of 797 code systems, 236 do not have a Steward value
    • Code systems broken out by product family:
      • 38 V2, 147 V3, 47 FHIR, 3 unified
    • Current TSMG solution is to make corresponding Management Group responsible (by either having them assign the WG responsible or by assigning them to the MG itself)
      • In the FHIR space, it could be the resource owner
      • V2 - make the V2 management group responsible
      • V3 - will be a multi-management group exercise.  CMG will take a look at the V3 sets first.  FMG will take a look at the list next to determine which is the appropriate responsible party. 
        • Austin is reviewed the list and found 3 code systems appropriate to assign to Structured Docs
        • Should consider having other WGs look over the list (MnM, OO)
    • 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.
      1. Rob Hausam will check with Lloyd and whether and how we can do this.
      2. Will bring this back for the Vocab call in 2 weeks.