Meeting Information

Meeting ID: 912 9786 9819

Passcode: 594748

Chair:  Carol/Reuben

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:

H - HTA Member

O - observer

L - liaison


P - present

A - Apologies

X- Proxy



Julie JamesBlue Wave Informatics LLP

Roel Barelds

Precipius b.v.

HX - (Davera)Susan MatneyIntermountain Health
HXSylvia ThunHL7 Germany
Carol MacumberClinical Architecture
HXReuben DanielsSaludax
HXDavera GabrielJohns Hopkins University Institute for Clinical and Translational Research

Wayne Kubick


Suzy RoySNOMED International
Andrea MacLeanCanada Health Infoway
Jessica BotaUTG/Apelon
Ted KleinKlein Consulting / HL7 UTG / Vocabulary WG CoChair
Rob HausamVocabulary WG CoChair
Mareike PrzysuchaHL7 Germany
Rob McClureUS Realm Liaison
Rory DavidsonSNOMED International
Diana WrightLantana Consulting Group
Joel SchneiderNMDP/CIBMTR
OXJoanie HarperCanada Health Infoway

Minutes of previous teleconference (2021-12-02) 

Agenda Topics

Agenda Outline

Agenda Item


Meeting Minutes from Discussion



TC Minutes Approval


Quorum was met

Motion to approve Minutes:

RD moves, RB seconds: Motion Passes 4-0-0 

No call 12/30, Next call 1/13


UTG/THO Update

ContinuousJess and Reuben

Non-HTA managed code systems retired in continuous build of THO:

THO changes have been implemented and is a first big step to using THO as the single source of truth.

Next step is to clean up the records and align with new template from HTA confluence pages. 

TSMG has referred a question to TSC around the OID request process, awaiting Rob M's return to act as liaison to TSC.

TopicNew PSS ReviewContinuousCarol

Two PSS's for review

  • PSS-1884 - Getting issue details... STATUS - Approved
  • PSS-1903 - Getting issue details... STATUS - Approved

External SDO and Code System Issues

(review JIRA tickets

ContinuousCarol/ Reuben

UTG/THO tickets:

JIRA Dashboard in progress


  •   HTA-8 - Getting issue details... STATUS
  • NIH/NLM provides a "metathesaurus representation" of DSM-V, which states "DSM-V is is a set of diagnostic criteria for ICD9CM and/or ICD10CM codes.  There are no native DSM-5 codes, it is not a standalone terminology." 
  • The APA provides guidance and criteria by which the ICD10CM (or legacy ICD9CM) should be utilized for diagnosis. Initial research shows that there are no DSM V codes 
  • Changes to the DSM can be found here and are characterized in two ways
  • Related FHIR ticket that added the URI: FHIR-13998 - Getting issue details... STATUS

Discussion: How should DSM-V be represented? One Supplement to ICD10CM, One Supplement to ICD9CM then a value set including ICD10CM and ICD9CM codes as defined by DSM-V

HTA Resolution: 

HTA agrees that DSM-V is not a stand alone code system. 

The DSM-V code system URI, rooted in was created in 2017 and is being used at an HL7 affiliate (Netherlands, for sure). Thus, it is not possible to remove the URI from FHIR R4. However, the HTA does not agree that the DSM-V meets the criteria for a code system (no concepts with identifiers, see above for more information). HTA will open a THO ticket to add verbiage about DSM in a "Using DSM-V with FHIR" page and thus, in R5, users will be provided additional information on it's use. 

Deeper Missive: Perhaps HL7 can approach the APA about how to represent the DSM-V criteria (nay classification) in a consistent way across version. 

DID NOT GET TO THESE ITEMS DURING CALL, any independent progress made on these items are noted below and/or on the tickets themselves. Will be added to next HTA call agenda for review and/or approval.



  • HTA-65 - Getting issue details... STATUS
  • Assigned to:


  • HTA-64 - Getting issue details... STATUS
  • Page (old format) exists without identifiers here ORPHANET





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


Updated CS Identifier process guidance

Continued from previousCarol

We are almost through the core principles. Having issues scheduling a call before holiday break. Will look into January for next call.

The draft is located here: Validating and Requesting Identifiers for External Code Systems and Identifier Systems

HTA members and observers are asked to review the drafted text, directly edit where changes are needed and use the comment functionality to ask additional questions. We will review again (and hopefully approve on the next HTA call, which will be at the WGM).

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

Any Other Business


AdjournmentMeeting adjournedN/ARD

Call adjourned at 

  • No labels