Meeting Information

Meeting ID: 912 9786 9819

Passcode: 594748

Chair:  Reuben

Scribe: Davera

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




Roel Barelds

Precipius b.v.

Sylvia ThunHL7 Germany
TProxy to ReubenCarol MacumberClinical Architecture
Reuben DanielsSaludax
Davera GabrielJohns Hopkins University BIDS
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
TProxy to DaveraRob 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
Hope GrayU of Alabama - Birmingham - HL7 Intern

PHugh GloverBlue Wave Informatics

PCraig AndersonPfizer
TProxy to ReubenPeter JordanHL7 New Zealand

Minutes of previous teleconference (2022-08-11)

Agenda Topics

Agenda Outline

Agenda Item


Meeting Minutes from Discussion



TC Minutes Approval



Quorum has been met

Motion to approve minutes from 11-08-2022: DG moves, RB seconds: Motion Passes 6-0-0.

TopicNew PSS ReviewContinuousCarol

electronic Product Information (ePI) Implementation Guide PSS-2102 - Getting issue details... STATUS

eMail from Craig:

For discussion:
1)    Identifiers for external code systems 
2)    Information about the code systems and whether there could be any potential IP issues 
3)    Other questions raised by HTA members

Regarding the TSC e-Vote 2022-08-16 - Technical Steering Committee - Confluence (, there was a discussion and questions at the TSC meeting earlier today about the terminologies associated with the ePI Implementation Guide. We took an action to address those questions at the next HTA meeting and to then come back to the TSC next Monday (Aug 29) for the TSC to make a final decision on our IG (we are aiming for the January ballot).


After review of the project, Craig shared a list of Code Systems and Value Sets from Code systems required to support this IG. Questions presented about some known licensed terminology products in this list (e.g.: WHO ATC, MeDRA...) Options regarding licensed content were also reviewed.  For example the EMA SPOR-RMS distributes a value set from MeDRA. Seeking implementation guidance to optimize the IG utilization of these Value Sets.  

Craig indicates the IG is aiming to be based on R5 (if possible) due to changed in the Medication regulation resources in R5.

JB moves to accept PSS, RB seconds. Motion passes 6-0-0.

BDP Mapping for productCode - FHIR-37676 - Getting issue details... STATUS  

OO is doing work around the BiologicallyDerivedProduct resource, and our folks from the Blood Banking world want us to map codes to ICBAA and ISBT, which are behind a paywall. The JIRA for this work is

Is it permissible to pull a small sample set as an example code set with clear notations that these codes are from another source? 

A current version of the code usage (Product Codes and Types) is here:


UTG/THO Update

ContinuousJess and Reuben

TopicCoordination of content publication between Publisher and THO
  • 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.

External SDO and Code System Issues

(review JIRA tickets

ContinuousCarol/ Reuben

JIRA Dashboard in progress

Canonical for NCI Thesaurus

HTA-36 - Getting issue details... STATUS

THO Change per Carol -?


HTA-71 - Getting issue details... STATUS


HTA-108 - Getting issue details... STATUS

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


Stub requires approval: College of American Pathologists (CAP) eCC (electronic Cancer Checklists)

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

JB: Motion to approve CLIA page. DG Seconds.  Motion passes 6-0-0


  • 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