• Tickets requiring content check: None
• Identifier System layout suggestion from Lloyd: Should we add sub-tabs for International, Passport and U.S. identifier schemes - just to make things a bit easier to navigate?
  • http://build.fhir.org/ig/HL7/UTG/identifiers.html
• Moving towards THO as the single source of truth for terminology content at HL7
  • How should THO align with the OID registry? 
    • 451 external OID registered
      • 332 complete
      • 8 deprecated
      • 2 edited
      • 2 obsolete
      • 78 pending
      • 8 rejected
      • 21 retired
    • Reuben suggests that this is a TSC issue, there is a lot of non-maintained content
      • Deprecate use of OID registry for terminology-related OIDs
      • Otherwise we are trying to maintain two repositories, one of which is not being maintained
      • Also an impact on HQ due to business model/revenue stream implications
      • Middle ground could be to still charge for an OID and add them to THO, but will require paid resources to do so
  • People are using identifiers from oidref.com such as https://oidref.com/2.16.840.1.113883.4.290 in their implementations
    • We are saying THO is the single source of truth, so what do we do with these?
    • Rob suggests adding identifier systems (under 113883.4) as identifiers with uri such as urn:oid:2.16.840.1.113883.4.XXX as FHIR allowed identifiers (urns)
    • Will need to enumerate them, but will be difficult to find in THO
    • Many of them will never show up in a FHIR instance
    • Should raise on TSMG main call

NDF-RT/MED-RT FHIR pages: FHIR-35800 - Getting issue details... STATUS

Motion to fix broken link to NDF-RT source to https://evs.nci.nih.gov/ftp1/NDF-RT/, add a note in the NDF-RT Comment column stating that it has been replaced by MED-RT, and adding text to MED-RT page that it has replaced NDF-RT. Motion: DG/RB: 5-0-0

Added this comment to the ticket. 

Proposed initial policy for HTA (from Lloyd via FHIR-35932 - Getting issue details... STATUS ):

If an identifier system is not listed in HL7 Terminology, the process to follow depends on the 'scope' of the identifier:

• for identifiers with international or US-realm scope, requests SHOULD be submitted to the HL7 Terminology Authority (HTA) who can help to determine an appropriate URI and ensure it is hosted in HL7 Terminology.  For specifications published by HL7 International, this is a SHALL rather than a SHOULD.
• for identifiers with national scope, requests MAY be submitted to either the local affiliate organization, or with the concurrence of the affiliate to HTA
• for local identifiers (e.g. medical record numbers, lab order numbers, etc.), the URI to use should be defined by the organization that issues the identifier

Should consider an HTA template for Identifier Systems. 

DID NOT DISCUSS

PSS-1980 - Getting issue details... STATUS

PSS-2005 - Getting issue details... STATUS

PSS-2074 - Getting issue details... STATUS

DID NOT DISCUSS

JIRA Dashboard in progress https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=13701

HPO

HTA-25 - Getting issue details... STATUS

Davera Gabriel  to update Human Phenotype Ontology to be consistent with the comments in JIRA and notify Jessica Bota when it's ready to proceed through the UTG THO Process

HUGO

Exists in THO here https://terminology.hl7.org/NamingSystem-v3-hgnc.html

HTA-71 - Getting issue details... STATUS is indicating that this is actually two code systems and needs to be split.

HTA has an incomplete metadata page here: HGNC which has been updated

RD: The existing URL is in the normative R4 specification. We could update the metadata information to clarify that the existing code system is meant to represent the gene nomenclature and the associated IDs and create a second code system record to represent the gene nomenclature groups and their IDs. However, before proceeding with that as an option, HTA would 1) like to consult with the code system owner. if this was already done, we would like that information and 2) have CG WG confirm if the use of a prefix would solve the issue and avoid the need to split the normative resource. Another option would be to create a formal FHIR partition for the code system, though not ideal. 

Note that this is used internationally and the impact is potentially large. A single OID exists for this code system and would also need to be addressed if a second code system was registered. 

Reuben Daniels will invite the code system owner to further discuss. 

2022-04-21

• Clinical Genomics invited the code system owner to attend the HTA call.
• Chris is a contact from HUGO but is not available this week.
• He may attend the HTA call on the 5-May-2022.

Genotype Ontology (GENO)

• HTA-67 - Getting issue details... STATUS
• Davera Gabriel  to research and gather information. stub here: Genotype Ontology

SEPIO-CG

• HTA-68 - Getting issue details... STATUS
• Davera Gabriel  to research and gather information. stub here: Scientific Evidence Provenance Information Ontology-ClinGen Extension (SEPIO)

CLINVAR-RS

• HTA-69 - Getting issue details... STATUS
• Requested additional on how this star rating system would be used as a code system.

2022-04-21:

• Suggested adding to the TSMG agenda for 25-April-2022 TSMG Main Call.

PGKB-ClinAnnLevels

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

2022-04-21:

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

ICPC, ICPC-DAN

• See discussion here: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/icpc.20term
• ICPCDAN HTA-75 - Getting issue details... STATUS , see related discussion here https://chat.fhir.org/#narrow/stream/179202-terminology/topic/What.20are.20'example'.20code.20systems/near/271897941

Discussion:

• Roel Barelds  to pick up and investigate

ISO-21089

• • https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Term.20of.20use.20for.20core.20CS.20with.20ISO.2021089.20Lifecycle.20Event.20codes 
  •  https://terminology.hl7.org/2.1.0/CodeSystem-iso-21089-lifecycle.html
    
    • Morten has opened a ticket HTA-49 - Getting issue details... STATUS
    • Roel Barelds will reach out to ISO and create an external terminologies page.
    • Reuben Daniels will review RB's comment and follow-up.
    • No update from last meeting
    • Reuben suggests a review of ISO pages is needed to determine how to update / maintain them
    • Potential source of fragments to go into tx.fhir.org

ICD-10-GM

• • ST raised that the ICD-10-GM page has disappeared from the HTA's External Terminologies Information Pages. Reuben Daniels will investigate.
  • No update.

FHIR Tracker: OID specified on page for ICD-9CM is registered for ICD-9

DID NOT DISCUSS

• The OID 2.16.840.1.113883.6.42 is stated in
  • the ICD-9-CM HTA Confluence Page as the OID for ICD-9-CM
  • the FHIR core specification's Using ICD-[X] Codes with FHIR Page as the OID for either ICD-9 or ICD-9-CM
  • the HL7 OID Registry as the OID for ICD-9 
• 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 Vocablary 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 HL7 OID Registry as the OID for ICD-9CM (diagnosis codes)
• 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

2022-04-21:

• RD to discuss with Rob McClure.