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)

Attendees

Attendee type: T - TSMG Member O - observer L - liaison	Present P - present A - Apologies X- Proxy	Name	Affiliation
O		Julie James	Blue Wave Informatics LLP
T	P	Roel Barelds	Precipius b.v.
T		Sylvia Thun	HL7 Germany
T	P	Carol Macumber	Clinical Architecture
T	P	Reuben Daniels	Saludax
T	P	Davera Gabriel	Johns Hopkins University Institute for Clinical and Translational Research
L		Wayne Kubick	HL7 (CTO)
L		Suzy Roy	SNOMED International
O		Andrea MacLean	Canada Health Infoway
T	P	Jessica Bota	UTG/Apelon
O		Ted Klein	Klein Consulting / HL7 UTG / Vocabulary WG CoChair
L		Rob Hausam	Vocabulary WG CoChair
O		Mareike Przysucha	HL7 Germany
T		Rob McClure	US Realm Liaison
O		Rory Davidson	SNOMED International
O		Diana Wright	Lantana Consulting Group
O	P	Joel Schneider	NMDP/CIBMTR
O		Joanie Harper	Canada Health Infoway
O		Carl Leitner	World Health Organization (WHO)
O		Chris Melo	Philips Health Care
O		Mica Carr	ICHOM
O		Sean Muir
O		Corey Spears	MITRE

Minutes of previous teleconference (2022-04-21)

Agenda Topics

Agenda Outline	Agenda Item	Status	Lead	Meeting Minutes from Discussion
Management	Quorum TC Minutes Approval Announcements	N/A	Reuben	Quorum is met Motion to approve minutes from 05-05-2022: JB/RD: 4-0-0.
Topic	UTG/THO Update	Continuous	Jess and Reuben	Tickets requiring content check: UP-304 - Getting issue details... STATUS UP-317 - Getting issue details... STATUS 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 TSMG Agenda Item Davera Gabriel : Passport Only, Drivers License Number Only, International, U.S. sub-tabs RD: Need to introduce dynamic pages in the long-term 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 Davera Gabriel add to TSMG call on 7/20/22
Topic	New PSS Review	Continuous	Carol	PSS-1980 - Getting issue details... STATUS PSS-2005 - Getting issue details... STATUS
Topic	External SDO and Code System Issues (review JIRA tickets https://jira.hl7.org/projects/HTA/summary)	Continuous	Carol/ Reuben	JIRA Dashboard in progress https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=13701 U.S. Employer Identification Number (EIN) HTA-74 - Getting issue details... STATUS Escalated via https://chat.fhir.org/#narrow/stream/179190-united-states/topic/identifier.20system.20for.20TAX.20identifiers Page created here: United States Employer Identification Number (EIN) Motion to Approve (with the IP information to be be filled in by Carol): JB/RB: 4-0-0 HPO HTA-25 - Getting issue details... STATUS Updated Human Phenotype Ontology to be consistent with the comments in JIRA (adding a non-preferred URI) Jessica Bota - ready to proceed through the UTG THO Process Motion to Approve: DG/JB: 4-0-0 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 a 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-06-02 Joel to invite HGNC to next HTA meeting Genotype Ontology (GENO) HTA-67 - Getting issue details... STATUS Davera Gabriel to research and gather information. stub here: Genotype Ontology Progress made Davera will work with Joel to make progress 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) Progress made Davera will work with Joel to make progress CLINVAR-RS HTA-69 - Getting issue details... STATUS Requested additional on how this star rating system would be used as a code system. 2022-06-06: Davera Gabriel please add to next TSMG call DID NOTE GET TO ITEMS BELOW HERE on 20220606 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 Pharmacogenomic Star Alleles (PharmVar Pharmacogene Variation Consortium) HTA-85 - Getting issue details... STATUS
Topic	Updated CS Identifier process guidance	Continued from previous	Carol	We are almost through the core principles. Will look into March for the next call as we were not able to find a time in Feb 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). 2022-04-21: Renewed call for feedback before the May 2022 work group meeting.
Topic	FHIR Tracker: OID specified on page for ICD-9CM is registered for ICD-9	Continued from previous	Reuben	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.
Topic	Any Other Business	Continuous	RD
Adjournment	Meeting adjourned	N/A	RD	Call adjourned at 10:00AM

Page tree

Teleconference 2022-06-02

Chair: Carol

Scribe: Carol

Antitrust Statement:

Attendees

Minutes of previous teleconference (2022-04-21)

Agenda Topics