Meeting Information

Meeting ID: 912 9786 9819

Passcode: 594748

Chair:  Carol

Scribe: Carol

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)


Attendee type:

T - TSMG Member

O - observer

L - liaison


P - present

A - Apologies

X- Proxy



Julie JamesBlue Wave Informatics LLP

Roel Barelds

Precipius b.v.

TPSylvia ThunHL7 Germany
TPCarol MacumberClinical Architecture
TPReuben DanielsSaludax
Davera GabrielJohns Hopkins University BIDS

Wayne Kubick


Suzy RoySNOMED International
Andrea MacLeanCanada Health Infoway
TPJessica BotaUTG/Apelon
Ted KleinKlein Consulting / HL7 UTG / Vocabulary WG CoChair
Rob HausamVocabulary WG CoChair
Mareike PrzysuchaHL7 Germany
TPRob McClureUS Realm Liaison
Rory DavidsonSNOMED International
Diana WrightLantana Consulting Group
OPJoanie HarperCanada Health Infoway
Carl LeitnerWorld Health Organization (WHO)
Chris MeloPhilips Health Care
Martha JonesICHOM
Alex Goel
Kris Gray
OPHope GrayU of Alabama - Birmingham - HL7 Intern

Minutes of previous teleconference (2022-07-14)

Agenda Topics

Agenda Outline

Agenda Item


Meeting Minutes from Discussion



TC Minutes Approval



Quorum has been met

Motion to approve minutes from 07-14-2022: 

TopicIRI request from FHIR RDF GroupContinuousReuben

FHIR RDF group is prepared to help with work of adding IRIs to THO

  • See TSMG minutes here 2022-07-25 TSMG Agenda and Minutes
  • Initial authoring - FHIR RDF will provide information for code systems used in HL7 products
  • Maintenance going forward - HTA to include IRIs going forward for external code systems.
    • Gaurav Vaidya, also applies to identifier systems (e.g., passport numbers, driver's license numbers, device identifiers)?
  • IRIs are used outside of HL7, essentially these create a map for exchange for code system information, paired with code, for use elsewhere

Versioning is not addressed at this time, relies on concept permanence of the underlying code systems.


  • RD: Resource constraints - we will need a full commitment and support from FHIR RDF. If they can provide it, then we have not technical concerns. We will clarify that their support includes on-going maintenance. 
  • RB: Right now, an IRI, what happens when there are more? 

UTG/THO Update

ContinuousJess and Reuben

  • Content created but not yet approved by HTA
    • UP-332 - Getting issue details... STATUS
  • Need to add to THO: Human Phenotype Ontology
    • Will move forward 
  • Update on bulk move from HTA Confluence to THO
    • Reuben trying to get this done by the August 21 deadline
    • Once this is done - how does HTA process new requests and edits?
      • RM: we need a place to gather information and move to THO, makes editing code system resources easier. giving up confluence would be very difficult for the drafting and gathering process 
      • RD: At present, the thought was that once confluence information has moved, the idea is that only create or update code system metadata records. pro forma would then be necessary. 
      • JB: Process is not laborious, staying with the current process would be less effort than creating tooling in JIRA to support our processes would be quite large.
      • CM: once bulk transfer is complete, the following will happen
        • All pages whose information has been migrated to THO resources will be reorganized under a heading called "Archived Code System Metadata Records - in THO) and new information will be under a "Draft Code System Metadata Records").
      • New requests? - Stay in Confluence for drafting information, once UTG ticket starts, then it progresses via UTG
      • Edits? - Should be done in UTG
    • Communicate via Sept WGM slides
  • THO release check. Please check if any of the following proposals are critical to have in a published release of THO prior to the content deadline.
    • Getting issues...
    • Getting issues...
TopicCoordination of content publication between Publisher and THO
Rob M
  • Terminology review expectations and process or IG Developers
      • Terminology Expectations for IG Developers (Working)
        • Paths will be reworked (if possibe)
      • RM: For internals, base could always be Currently, it may be that publisher will look in THO and if it can't find in THO, looks internally, then it builds a local reference. Otherwise, it's harder to identify what is intended to be moved vs. what is intended to stay local in the IG. 
      • Pro Forma vs CR - Only issue that may come up, URL copied and pasted will 404 - though that's not a violation of the URL as a URI -  we need to know if the publisher can work anyway both before and after the move of content from local packages to THO.
TopicNew PSS ReviewContinuousCarolNone

External SDO and Code System Issues

(review JIRA tickets

ContinuousCarol/ Reuben

JIRA Dashboard in progress


HTA-71 - Getting issue details... STATUS

    • Content has Gene Groups and Gene Symbols, used to be only a numerical ID.
      • For Gene Symbols - Because of historical reasons, and we don't want to have everyone change URLs and IDs, the URL will allow people to remove HGNC:, from the official HGNC:(integer) for Gene Symbols
      • For Gene Groups - For this, we could do HGNCG:(integer) so it works the same way for Gene Groups.
      • Concern is where cases that same numeric value in both places
        • 1625 in Gene Symbols means XCR1 where as 1625, Gene Groups has different meaning. The number alone is not unique. 
      • Gene Groups - - retain original OID
      • Gene Symbols -

Ended Meeting Here

X12 Insurance Type

CDA-1513 - Getting issue details... STATUS

  • Pending review by someone who knows the X12 content to determine what is the definitive source



HTA-89 - Getting issue details... STATUS

Reviewed the ticket and marked as In Progress pending additional information from implementers

GL String Code

HTA-84 - Getting issue details... STATUS

Reviewed the ticket and marked as In Progress pending additional information from implementers

Pharmacogenomic Star Alleles (PharmVar Pharmacogene Variation Consortium)

HTA-85 - Getting issue details... STATUS

Initial review complete. Invited submitter to an HTA call for further information.



Created stub: Clinical Laboratory Improvement Amendments (CLIA)
FHIR-36926 - Getting issue details... STATUS


  • HTA-70 - Getting issue details... STATUS


  • RD to discuss with Carol about creation of a Confluence page.




TopicContinued from previousReuben
  • The OID 2.16.840.1.113883.6.42 is stated in
  • The OID 2.16.840.1.113883.6.2 is stated in
    • THO/UTG's ICD-9-CM Code System Metadata Record as the OID for ICD-9-CM
    • the HL7 OID Registry as a retired OID for ICD-9CM with the following note: Note that this has been retired in favor of an explicit split between the diagnosis codes and the procedures codes as per the Vocabulary TC decision on Wednesday Q4, January 21, 2004.  Replaced by 2.16.840.1.113883.6.103 and 2.16.840.1.113883.6.104 as voted by committee.  -T. Klein
  • The OID 2.16.840.1.113883.6.103 is stated in
  • The OID 2.16.840.1.113883.6.104 is stated in
    • the HL7 OID Registry as the OID for ICD-9CM (procedure codes)
  • Requirement:
    • What are the correct OIDs for
      • ICD-9; and
      • ICD-9-CM 
  • Rob McClure to provide an update after checking in with the US Realm group.  No Update


  • RD to discuss with Rob McClure.

Any Other Business

AdjournmentMeeting adjournedN/ARD

Call adjourned at 10:00AM

  • No labels