Meeting ID: 912 9786 9819
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)
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
|O||Julie James||Blue Wave Informatics LLP|
|H||X - (Davera)||Susan Matney||Intermountain Health|
|H||P||Sylvia Thun||HL7 Germany|
|H||P||Carol Macumber||Clinical Architecture|
|H||P||Davera Gabriel||Johns Hopkins University Institute for Clinical and Translational Research|
|L||P||Suzy Roy||SNOMED International|
|O||Andrea MacLean||Canada Health Infoway|
|O||Ted Klein||Klein Consulting / HL7 UTG / Vocabulary WG CoChair|
|L||Rob Hausam||Vocabulary WG CoChair|
|O||Mareike Przysucha||HL7 Germany|
|L||Rob McClure||US Realm Liaison|
|O||Rory Davidson||SNOMED International|
|O||Diana Wright||Lantana Consulting Group|
|O||P||Joanie Harper||Canada Health Infoway|
Minutes of previous teleconference (2021-11-17)
Meeting Minutes from Discussion
TC Minutes Approval
Quorum was met
Motion to approve Minutes:
RB moves, RD seconds: Motion Passes 4-0-0
No call 12/30
|Topic||SNOMED CT sub-ontology||N/A||Suzy|
Floating conflict, so periodic attendance, feel free to let Suzy know in advance when we have an agenda item for SNOMED
Produce a new product, a subset of SCT INT.
International Patient Summary is the go to product being discussed around the world (G7 etc..). While a large number of countries etc.. are adopting the IPS, SNOMED have included all the terminology in the GPS (freely available subset of SCT INT content covered under creative commons). Through this we've learned more about how they want/need to implement the content, anticipating what is next is the idea of doing a post data analysis. Currently GPS is a flat list of codes without relationships and thus can't build intentional value sets etc.. Collaborated with the University of Manchester, who has some sub-ontology tools, to analyze the IPS refset and the use of a sub-ontology to support the post data analysis use case. The prospect of this was brought to the SCT Governance board and approved the announcement. The IPS sub-ontology (ISO) product itself is still in development and led by Suzy. Steering committee meets next week and is open to additional use cases and early testers to provide feedback on things like included content and release schedule. The IPS sub-ontology will also be available under the creative common license (or something akin) and the GPS will still be available and updated every year in Sept. The SNOMED HL7 refset will be the over arching container for the ISO will be separate. Thus, local/country edition extensions aren't currently contemplated as being included. A FAQ will be created to hopefully answer common questions. Hoping to launch in 2022 (Q1 or Q2).
Q: Will ISO be a SNOMED terminology?
A: Being worked through, right now, it's characterized as a "mini SNOMED" but details are to follow
Q: Versioning stated by SCT URI Standard? Distribution format? RF2?
A: Again, being worked on...Andrew Atkinson and SNOMED Advisory groups will participate.
|Continuous||Jess and Reuben|
Non-HTA managed code systems retired in continuous build of THO: http://build.fhir.org/ig/HL7/UTG/external_terminologies.html
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.
Revisit OID required?
In the case of CCN and HCC (items below), requestor is not asking for an OID, only a URL for FHIR based IGs. Independent of the cost of creating OIDs, who's responsibility is it to create an OID for use in other HL7 products? The requestor? HTA?
Currently the HTA has agreed the process will be to 1) create the code system metadata, including the URL and 2) notify the requestor that an OID may be required for cross product use and point them to the current OID registry process. Additionally, the HTA will temporarily not require OIDs on the code system metadata template and raise through the TSMG, a request to TSC around the ability to create OIDs for requests that come in through the HTA for a new external code system identifier.
|Topic||New PSS Review||Continuous||Carol|
External SDO and Code System Issues
(review JIRA tickets https://jira.hl7.org/projects/HTA/summary)
JIRA Dashboard in progress https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=13701
HTA Vote: RB moves, RD seconds: Motion passes: 4-0-0
GLN as an Identifier System
CMS Certification Number as an Identifier System
CMS Hierarchical Conditions Categories and Prescription Drug Hierarchical Condition Category
ENDED CALL HERE
Updated CS Identifier process guidance
|Continued from previous||Carol|
We are almost through the core principles.
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).
|Topic||Continued from previous||Reuben|
Any Other Business
ODH request from CDC . Jess has reached out and received no reply to date.
Looking for advice to coordinate PHIN VDAS content with THO. Defer to discuss in Vocab main call 18Nov21
Potential convenience copies...
Call adjourned at 9AM EST