Attendee type:

M - TSMG Member

O -Observer / Guest

Attendance:

P - present

A - Apologies

X - (Apologies with Proxy)

Name

Affiliation

Administration

• TSMG appointments for 2023
  • Slate needs to be developed
    • Expiring members and willingness to stand again (y/n)
      • Davera - yes
      • Sylvia - no
      • Rob M - no
      • Peter - no
      • Michael - yes
      • Roel - yes
• JB: Next THO freeze is planned for October 23
  • Announcements went to Zulip, co-chair list.

Code System: https://build.fhir.org/ig/HL7/fhir-ips/CodeSystem-absent-unknown-uv-ips.html

Map to SNOMED: https://build.fhir.org/ig/HL7/fhir-ips/ConceptMap-absence-to-snomed-uv-ips.html

The request from the IPS project for the TSMG is:

1. Obtain approval (hopefully) from TSMG to publish the IPS STU 1.1 update with the current "Absent and Unknown Data - IPS" code system using the present 'http://hl7.org/fhir/uv/ips/CodeSystem/absent-unknown-uv-ips' canonical url.
2. For the IPS STU 1.1 publication, the "Absent and Unknown Data - IPS" code system content will remain in the IPS IG (and will not - yet - be moved to THO).
3. We will initiate discussions again with SNOMED Int. about the possibility of moving the "Absent and Unknown Data - IPS" concepts to SNOMED CT (International Edition and IPS Free Set/Terminology), in preparation for the IPS FHIR IG STU 2.0 ballot and ultimate publication.
4. If, in further discussion, no agreement is able to be reached with SNOMED Int. and the "Absent and Unknown Data - IPS" concepts are not incorporated into SNOMED CT, then we will consider and most likely would plan for moving this code system and its content to THO for the official IPS STU 2.0 publication.

DG:  discomfort with conflating "none pertinent for this section of the record" with "none known" concept. RH: this can be brought up in another ballot

LN: is this an acceptable use case for "null Flavor?"  Does this value set has the granularity to express the required expressions?  RH:  this is a different approach. 

CM: due to the maturity level of the IG and if the process for the THO were in place, then this request would fail.  RH / JD:  its between maturity level 2 & 3. 

RH: urgency on this matter is due to the high demand for this content internationally

RD:  are there any breaking changes  JD:  yes there is one errata in the document that could be considered a breaking change. RH: utilization in Canada impactful.  The ask is to get these concepts in SNOMED CT, or of failing that into THO, but unsure which way this may go.  As such, want to be sure there is a source for this Value Set.  In prior correspondence: SNOMED CT do not want to include "no information" codes. 

RD Motion Seconded: LN: TSMG approve IPS publishing the Code System using the canonical url under the condition that the IG remain under FMM 2 Motion passes 6-1-0

• Decide on a version value for the next THO release.
  1. Here are the tickets planned for the release: https://jira.hl7.org/issues/?jql=project%20%3D%20UP%20AND%20status%20in%20(%22Sent%20For%20Implementation%22%2C%20%22Queued%20for%20Next%20Implementation%22)
  2. JB (via email) I think the major consideration here is the inclusion of the THO licensing agreement
  3. Must decide on this call because it will hold up the release
  4. RD:  Moves to version 5.0.0 DG: Seconds  Motion passes 7-0-0
     1. LN: when was it frozen  CM: yesterday... RD:  should be published by the end for the first week in November (also the last release this year)
• Terminology expectations for IG developers
  • Terminology Expectations for IG Developers (Simplified)
  • JB and RM have attempted to simply the policy. Group reviewed the policy discussion summarized below
    • Policy applies to any HL7 Implementation Guide
    • Input from FMG and TSC has been included, CMG has not commented. Policy should be applicable across product lines.
      • For this to work, everything in THO will need to have an OID to support CDA
    • Action Items from last week: validate that the first few steps are the same as those in Validating and Requesting Identifiers for External Code Systems and Identifier Systems
  • JB (via email)Main discussion point probably should be how to prevent duplicate urls while recommending that IG authors anchor their content in THO regardless of any plans for it to be added later
  • CMG will add this item to their agenda on Wednesday
  • CM:  is there an implication that there would need to be tooling in place in order to enforce this policy?
    • RM  could employ ticketing to allow tracking / interaction with the community that could be used immediately without having to wait for tooling to enact this process.  
    • re: tooling - need to have a discussion with Grahame re: tooling to do lookup of a dB of URIs (confirming no duplicates)
  • If recommendation is that this should be a JIRA-based process then there would need to be a ticket-type of TSMG added.  Review of these tickets would then be a standing agenda item on the TSMG main calls (this one)
  • Reviewed open question in this call.  Next week: goal is to finalize verbiage. 
    • RD will draft list of the consolidated Tooling requirements for IG Publisher and duplicate URI handing that call

Discussion ended here no further agenda items were discussed

• OHDSI Symposium follow-up
  • OMOP + FHIR track: high attendance
  • Upcoming proposal for Vocab WG re: OMOP Vocab / External Terminologies
    • FMG / FHIR - I proposal in the wings
  • SSSOM workshop to be repeated virtually
• Vulcan FHIR-to-OMOP project
  • New participants: SMILE Digital Health
• Proposal: developing a core UCUM Value Set (Upcoming)
  
  • • CMG / V2 / OHDSI communities expressing interest
    • FHIR / CMG vale sets not currently aligned

Product Management Council

• • Met Friday 21-10-2022
  • CDA MG will present at November PMC Webinar. TSMG likely next webinar thereafter.

TSC Membership - (deferred: RM not available at 10:12)

• RM will take to the TSC: 4 year terms, then one year off and establishing 2 alternate members as outlined above 
•   RM: update re: proposal from TSMG?
  • in TSC meeting: other management groups had not yet discussed this topic.  This will be reviewed in today's (this week's) TSS meeting. Update next week
  • Bryn will bring back this update if RM is not available

• Deprecation Policy and Implementation
  
  • Tabs created
  • Deprecation Policy Framework
  • Issue logged to render identifier.period: https://github.com/HL7/fhir-ig-publisher/issues/455
    • Lloyd disagrees with rendering identifier.period. Would rather hold deprecated identifiers in naming systems but enhance tooling to link code systems to their identifier systems based on url
  • RD:  this is the intended purpose for the CodeSystem / ValueSet can be linked to corresponding naming system established by the code system: url value is equivalent to the preferred url in the name - so they should
  • RD:  is Lloyd going to provide a link to the naming system?
    • JB: need to establish this as policy before he should go do this
  • RD:  will discuss this with Grahame to understand what his position is

• Terminology Server (Implementation Requirement)
  • Follow-up from WGM - next steps re: terminology server (service) requirements (1-page description)
    • Needs to clearly state why we do not have what is needed in the currently available services including THO or tx.fhir.org
    • Jess / Reuben / Rob Hausam/Davera
      • working draft of the document is here
      • initial conclusion for editing period has passed
• UTG / THO Subcommittee work in progress
  • Vocab WG follow-up: Policy Requiring Identification of Stewards for HL7 (Internal) Code Systems
    • Rob H reached out to Grahame about mining for steward values
    • List of code systems without steward is here