Caroline Macumber(CM) 

Davera Gabriel (DG)

Reuben Daniels (RD)

Daniel Vreeman  (DV)

Rob McClure (RM) 

Bryn Rhodes (BR) 

Jessica Bota (JB) 

Lisa R. Nelson (LN)

Michael Faughn (MF)

Peter Jordan (PJ)

Roel Barelds (RB)

Sylvia Thun (ST)

Grahame Grieve (GG)

Joan Harper (JH)

Patrick McLaughlin (PM)

Robert Hausam (RH)

Suzy Roy (SR)

Cara Schlegel (CS)

Robert Hausam (RH)

Carmela A. Couderc (CC)

• Announcements
  • SNOMED Expo registration open / program link is here
• TSC co-chair call this week now open to all who are interested (now entitled: TSC updates)
  • Tuesday, Aug 30, 2022 04:00 PM Eastern Time (US and Canada)
  • Conflicts with standing UTG/THO subcommittee call
• Call for HL7 comments on (US) ONC’s Interoperability Standards Advisory (ISA) and preparing for Draft USCDI Version 4

Trackers for rejection:

• • • Alignment and completeness of NamingSystems/terminology pages/OID Registry (FHIR-20363)
      • Recommendation: Reject on the basis that THO will be the single source of truth and the referred to content will no longer be authoritatively available from the FHIR core specification.
    • Missing Valueset OIDs (FHIR-20376)
      • Recommendation: Reject and refer reporter to the UTG process where V3 terminology content is now maintained.
    • Which type of ValueSet identifiers an HL7 v3 OID of a ValueSet is? (FHIR-22846)
      • Recommendation: Reject on the basis that this is a question and not a change request. Refer reporter to a the Vocabulary WG. 
    • ImagingStudy qa issue — copyright for terminology artifacts (FHIR-24683)
      • Recommendation: Address as a ballot comment pending advise from HL7 HQ.
    • OID missing from HL7 Version 2 Table 007 (FHIR-26383)
      • Recommendation: Reject and refer reporter to the UTG process where these V2 terminology content is now maintained. 
    • HL7 Version 2 Table 0004 (4.3.15.4) missing OID information in summary (FHIR-26384)
      • Recommendation: Reject and refer reporter to the UTG process where these V2 terminology content is now maintained. 
    • Verify OID on Act Substance Admin Substitution code (FHIR-26392)
      • Recommendation: Reject and refer reporter to the UTG process where V3 terminology content is now maintained.
    • Inconsistent usage of OIDs/URIs overview (FHIR-31621)
      • Recommendation: Reject on the basis that THO will be considered the source of truth for terminology artefact OIDs and URIs. For broader alignment, another tracker should be raised.

DG: Motion to Reject these items above as a block becuase they no longer pertain to the content in THO.  MF: Seconds.  Motion passes 6-0-0 

Reuben Daniels will update these tickets

• • • • • OID Registry trackers
          • Medication Request Status OID valid? (FHIR-26394)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID not available in HL7 OID registry (FHIR-26395)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for Medication Request Intent value set not in HL7 OID Registry (FHIR-26396)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for Medication Status value set not in HL7 OID registry (FHIR-26397)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for Link Type not registered in HL7 OID Registry (FHIR-26399)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for care plan intent not registered in HL7 OID Registry (FHIR-26400)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for care plan activity status not in HL7 OID Registry (FHIR-26401)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry. 
          • OID for Encounter Status not in HL7 OID Registry (FHIR-26404)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry.
          • OID for Goal Status not found in HL7 OID Registry (FHIR-26405)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry.
          • OID for Contact Point System not registered in HL7 OID Registry (FHIR-26413)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry.
          • Event Status ValueSet OID is not registered with HL7 OID Registry (FHIR-26416)
            • Recommendation: Reject on the basis that value set OIDs are not required to be in the HL7 OID registry.
          • Inconsistent usage of OIDs/URIs overview (FHIR-31621)
            • Recommendation: Reject on the basis that THO will be considered the source of truth for terminology artefact OIDs and URIs. For broader alignment, another tracker should be raised.

TK: recommends that these be put into the OID registry.  Any objects could be used in CDA.

RD: this is not a TSMG responsibility to do that.

TK: suggesting that the TSMG assign curation of this content to the WG that created the code system

RD: would consider recommendation to assign these to the WG that generated them.  solution could be to reject these tickets and suggest the originating WG generate required content to the OID registry. 

John:  these came up when  we mapped from CCDS to FHIR. 

JB: Motion to reject tickets and urge the submitter to reach out to curating WG re: adding this content to the OID registry becuase it impacts the C-CDA FHIR mapping and without this it could lead to conflicts in C-CDA.  In the future this is risk that could be avoided.  Additionally there should be a note indicating this is not the responsibility of the TSMG to make those changes.  DG: Seconds. Motion passes 7-0-0

Trackers for discussion and reassignment:

• • • Clarify the use of fragment (FHIR-33947)
      • Recommendation: Reassign the ticket back to Vocabulary WG who are responsible for this page with a note in support of adding the following test after "Fragments can only be published by the code system authority, or according to a process defined by the authority, if they have defined one." to "In HL7 International, fragments may only be published with the agreement of the Terminology Services Management Group (TSMG)."

RD: there are 2 options - this can be assigned back to the Vocab WG with a recommendation to just assigned back to the Vocab WG.  DG: moves this is approved and sent back to the Vocab WG with the aforementioned note.  CM: Seconds 

Motion passes 7-0-0

• •  
    • Define rules around CodeSytem.content for hl7-defined code systems (FHIR-35966)
      • Recommendation: Comment to provide TSMG support and reassign the ticket to FHIR-I who are responsible for tooling.

if something other than HL7 or FHIR is in the base, a code system can be owned by a group other than FHIR-I

• Connectathon / WGM
  • Request to Andrea for "Ballot Harmony" BoF session sent - waiting for a response
  • Connectathon Track Kick-off meeting: Thursday 9/8 12:30-1:30p EASTERN
• Proposal from OMOP + FHIR Terminologies subgroup (for Vocab WG) underway
  • follow-up from SNOMED / OHDSI discussion 8/1

• Generation of v2.91 Vocabulary and discrepancies of V2 Tables with THO
  • generation of terminology is accomplished via a tool (a .pdf document)
    
    • The source of truth for the gender harmony vocabulary will end up in THO after the ballot but before publication.   The URL is anchored in terminology.hl7.org; however right now the content is in the FHIR ballot.   The reasons for this are complicated and are related to tools and timing.  However the gender harmony content is rendered in 2.9.1 chapter 2C, it must be very very clear to balloters and users that the source of truth of the content is in THO (will be soon) and the printed v2 ballot is just a snapshot of the content at the time the document is generated; the websites with the live content must be used to access the guaranteed correct source of truth for it.
  • It is not possible to repair all this content in time for the ballot in a few days
  • CM: the Gender Harmony ballot content must be ready for the ballot
  • Options are as follows:
    • Chapter 2C of the v2.91 specification will need a note that states that the underlying source of publication for the v2.91 ballot is not aligned with THO (hundreds of differences)... renders this chapter as not normative
      • Point readers to the THO V2 tables xml code system content as a short term solution 
    • Gender Harmony content will eventually be published in THO, which includes the V3 Content (Rikki Merrick is managing this alignment) but initially will be published in the FHIR core specification.  
    • MF: suggesting V2 ballot content is published the same way as always and the corrected content be manually curated back into THO
  • MF: Motion to recommend to V2 Management group Chapter 2C of the v2.91 specification with a note that states that the underlying source of publication for the v2.91 ballot is not aligned with THO. Point readers to the THO V2 tables xml code system content as a short term solution. Chapter 2C will require two urls:  one to V2 tables and on to concept domains. DG: Seconds Motion passes 8-0-0
  • Michael Faughn will communicate this decision back to the V2 Management group Ted Klein will assist with the wording of this communication
• Release of THO (RD will provide update)
  • TSMG should approve freeze date (previously discussed 9/5) 
  • Motion to freeze September 5 with intent to publish prior to the WGM, CM: Seconds. Motion passes 8-0-0
• E-vote for review of terminology expectations for IG developers
  • Terminology Expectations for IG Developers (Working)
  • E-vote has been set up: 2022-07-11 TSMG e-Vote
  • eVote to be completed by last week
  • Issues raised so far
    • RM suggests that THO anchored links in other areas should redirect/resolve
    • RM suggests that url should include IG name to avoid conflicts
  • Standard workflow is needed - progress requires more input
    • Jess and Rob M to carve out time to review at WGM (or potentially before)
• Many CodeSystems use terminology.hl7.org urls when they should be hl7.org/fhir FHIR-37440 - Getting issue details... STATUS
  • Michael Faughn extracted code systems and value sets (resources matched by id) from the THO/FHIR NPM packages
  • UTG/THO subcommittee working through differences across elements for duplicates to determine what is consequential 
  • Grahame has agreed to help with handling duplicates, including involvement from other WGs as needed

• Versioning policy for UTG/THO
  • Reuben to provide update on first meeting - weekly Wednesdays 4p EASTERN 
  • This week's discussion topic: HL7 terminology systems in THO
• Standard copyright for HL7 content
  • Raising suggestion to have a standard copyright statement for content maintained and published by HL7
  • Dan V to chat with Grahame and agrees more discussion is needed

• 8/25 Meeting
  • electronic Product Information (ePI) Implementation Guide PSS-2102 - Getting issue details... STATUS   Accepted