Page History

• Announcements
• Upcoming Meeting Schedule (Quorum is 6 attendees + 1 co-chair)
  • TSMG calls are weekly now 3:30p (EASTERN)
  • Potential for alternating times aiming to accommodate more members.  With an additional time - perhaps the membership can attend at least one of the two regular meeting times. 
    • RD will reach out to the TSMG members that could not attend re:  potential additional  / alternating meeting times
• New TSMG members should self-assign to subcommittees
  • Ioana will join the Education / Outreach subcommittee
  • Will touch base with John 
• UTG/THO subcommittee call (90 mins alternating w Vocab WG main call) 
  • Need someone to run the call for a couple months 
  • MF: can Marc take this role?
    • same quorum rules would apply, if voting
    • JB will reach out to Marc 
• THO versioning call
  • Need to reschedule (usually met during this time slot)
  • A call for a new slot will will be circulated
• Action Items from last week
  • ALL TSMG members need to review the comments. on Terminology Expectations for IG Developers Policy and be prepared to discuss today

(APPROVED)

• Terminology Expectations for IG developers
  
  • Terminology Expectations for IG Developers (Draft For TSC Consideration V2)
  • Review of WGM comments
  • Per JB:  the naming.system identifiers are in fact visible in THO.  JB will add clarifying language about this in the policy.
  • One more outstanding comment to resolve - then back to TSMG before sending to the TSC

• Technical correction for THO due to corrupt R3 package
  • Grahame confirmed we do not need the technical correction urgently (as initially suspected) and it can wait until next freeze/release scheduled for 2/12
  • Need publication request for next release (and to determine major/minor)
• Determine if V2 can have some vocabulary outside of THO
  • There are examples/user defined tables that have been added to THO
  • Proposed Motion (pending quorum): The TSMG will propose a means of identifying and tagging HL7 Value Sets and Code Systems in THO whose sole intended purpose is to be used as examples.

• Duplicate CS/VS across FHIR core and THO
  • Mostly cleaned up but need to determine what to do with remaining code systems
  • Remaining duplicates seem to be ballot bound, trying to get confirmation via https://chat.fhir.org/#narrow/stream/179165-committers/topic/Code.20Systems.20with.20wrong.20URLs
  • Once CS cleanup is complete, need to clean up VS accordingly
• Duplicate URLs in THO
  • Duplicate URLs in THO for CVX: http://build.fhir.org/ig/HL7/UTG/CodeSystem-CVX.html vs. http://build.fhir.org/ig/HL7/UTG/CodeSystem-v2-0292.html
  • Suggestion to confer with HTA to see what information from the retired page needs to be ported to the active page
    • Work complete via

      Jira
      server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key UP-374

      and ready for review/vote
  • Marc suggested we may not need to implement this based on discussion at WGM for an IG Publisher request to have duplicate OIDs be a warning if one of the entries is retired
  • JB: please vote when quorum established on the UP ticket & submit this as a proforma change (before the freeze on 2/12)

• Recommendation from Vocab to TSMG on handling of THO OIDs
  • OID issue has been resolved in R4B and R5 FHIR core
    • Should be reviewed by Vocab/TSMG
  • With most of the duplicate code systems removed from FHIR core, the THO entry and OID remains
    • There are a handful of duplicates that remain that are believed to belong in FHIR core
    • Others have been sent to WGs for review/consolidation via https://chat.fhir.org/#narrow/stream/179165-committers/topic/Code.20Systems.20with.20wrong.20URLs
  • Goal is to document resolutions for both OID fixes and duplicate resolution for transparency
    • Started discussion on Zulip: https://chat.fhir.org/#narrow/stream/194616-terminology-.2F-utg/topic/OID.20issues
  • JB: As a follow-up creating a info sheet describing what occurred would be helpful
• Review fix for 'All HL7 Code Systems' tab

  • Jira
    server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key UP-320

  • Options are to break down by product family or maintain two separate manifests (more work and more prone to error), more details in ticket comment
  • Discussion included adding the following comment to the ticket: 
    • Discussion in TSMG meeting 13Dec22 included a suggestion to define a THO category extension that could be used to drive categorization of these pages within THO, reducing the need to manually maintain manifest lists for each product family, etc.  This could be enabled through a custom xslt template.  This would be a good solution conferring a reduction of work for THO maintenance. 
  • Decision on this topic requires a vote.  Quorum not established but discussion was fruitful
• UTG/THO Subcommittee recommendation about adding release tracking information to THO
  • Suggests linking dashboard that tracks tickets implemented by release version (see https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=16115) to the Directory of Published Versions page on THO (https://terminology.hl7.org/history.html)

Parking lot and work in progress

• Workflow for THO releases (moving content approved in ballot to THO AND how to handle missed THO deadline)
  • Requires discussion - priority item to resolve
  • This is a key component of the IG Developer tutorial
  • This item is blocked without the expectations for IG developers policy being developed.
  • 8Nov22 TSMG meeting: deferred
• Versioning policy for UTG/THO
  • Finished proposal for HL7 Code System elements
  • There are a few higher level considerations before moving over to Value Sets
  • Progressing to finish HL7 Value Sets and moving to External Identifier System Metadata Records

• • No Quorum 1Feb23.  Next meeting on Wed 11 January 3-4pm EASTERN US.  
    • 211LA main topic
    15Feb23