Page History

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

WHO SARS-CoV-2 Variants

• Page drafted here: WHO SARS-CoV-2 Variants
• Requestor has been asked to review

ICD-11 MMS

• International Classification of Diseases 11th Revision
• JB Motion to Approve, DD seconds: 4-0-0
• The HTA page covers foundation and MMS, suggest breaking them up

• Jess to implement as separate entries at THO, taking verbiage that applies to lineralizations and MMS to the MMS metadata record.

PharmVar (participants not on call, holding for next)

• Reviewed PharmVar content via https://www.pharmvar.org/genes on 11/10
• General agreement that this is a code system where concepts are unique
• Agreed to add more information to the code system metadata record page: Pharmacogene Variation (PharmVar)
  • The following content should be placed in a "Using PharmVar with HL7 products" page, not the metadata record.

  • "In the context of the representation of PharmVar in HL7 standards: 

    • The concept identifier is the PharmVar ID
    (these are unique)
  • Display name is in column 1 (Allele Name)
  • Remaining columns are properties
    • The concept display name is the Allele Name
    • There are several concept properties associated with PharmVar concepts (Legacy Label, Variants, etc.)
    Code
    • The code system is represented with an is-a hierarchy
• Likely no need for a convenience copy for implementers as they will likely only be interested in certain portions of PharmVar
• Kevin and team will review HTA page once updated with this information
  • Page has been updated and Kevin has been tagged to review
  • Still awaiting copyright information

W3C DID

• Page drafted here: W3C Decentralized Identifier (DID)
• JB Motion to Approve, DD seconds: 4-0-0

• Next Step: HTA awaiting copyright information

Medi-Span Electronic Drug File

• Medi-Span Electronic Drug File
• Requested more information from requestor

(Did not get to these items)

UDAP Capability Rest Security Service

UICC TNM Staging

• Drafted page reviewed by requestor, ready to be approved by HTA
• RM: Need clarification if those alternate oids are identifiers or version identifiers
  • Can move forward with current identifiers
  • Send note to Kai and Sylvia to show how we plan to represent UICC TNM and note that previous editions are not represented as alternate OIDs (last part of OID looks like it is being treated as version but confirmed it is not just for this code system so not a root we can tie to)
• Will seek clarification prior to approving metadata for addition to THO

X12 Insurance Type

• Pending review by someone who knows the X12 content to determine what is the definitive source
• Asked Mary Kay to draft a page and HTA will review when ready

HGNC

• Joel to propose updated text for what should be used for the code and HTA will review and update the resources as necessary

GL String Code

• Joel will follow up to make progress on this one

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

• Initial review complete. Invited submitter to an HTA call for further information.
• Will attend 11/10 HTA call

PGKB-ClinAnnLevels

• Jira
  server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key HTA-70

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

  Jira
  server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key HTA-75

  , 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

      Jira
      server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key HTA-49

    • 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

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

• 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 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 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.