Office of the National Coordinator for Health Information Technology (ONC)
O
John Snyder
National Library of Medicine (US)
O
P
Ted Klein
TK Consulting
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).
Minutes Approved as Presented
2022-02-16 TSMG Agenda and Minutes
This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."
TedK: OID 1.0.3166.2 symbolicName Value Set Information OID 2.16.840.1.113883.21.224 symbolicName hl7VS-stateProvince Description Concepts used to specify a state or province. Used in Version 2 messaging in the Extended Composite ID with Check Digit (CX), Performing Person Time Stamp (PPN), and Extended Composite ID Number and Name for Persons (XCN) values as well as the Accident (ACC) segment. Content Logical Definition all codes
PJ: This is a Canadian resource, and there may not be a role for this content on the THO
Carol: this is a source of truth for this issue, TK: this is not ISO, need to remain aware of where the resource is coming from. Carol: we may need to author a policy statement re: this kind of situation, as this is not the first time this has become an issue. Referencing terminology content that is available elsewhere... likely an HTA task to draft recommendations regarding these situations.
Joan: there are other ISO 3166 references in THO. TK: these are historical artifacts from V2. Licensing to ISO was a barrier to the V2 community
Issue: Remove Retired External Code System metadata records to resolve the issues with mixed case font
Warnings will be thrown if <caseSensitive> element not present
To remove warnings from THO v3.1.0, HL7 code systems suppressed had <caseSensitive> set to 'true' and external code systems were manually suppressed: seehttp://build.fhir.org/ig/HL7/UTG/qa.html
Need to clean up additional HL7 content suppressed warnings and determine how to handle external code systems
RD: Motion: for the retired metadata code system records, such as those that are generating errors with code sensitive errors, these should be removed from THO. Second: BR. Motion passes 8-0-0
Publication request for approval by TSMG
Confirmed that TSMG has the authority to approve publications of THO
JB: Motion to approve the publication release request, RD: Seconds. Motion passes 8-0-0
Freeze for release v3.1.0 still active and release of v3.1.0 in progress
Moving "Using X with FHIR" pages to THO
Reuben to continue working with Lloyd and Grahame to discuss how those pages will be managed once in THO and make sure they are consistent with core FHIR spec, which will refer to them
Vocab WG follow-up: Policy Requiring Identification of Stewards for HL7 (Internal) Code Systems
Vocab WG should decide whether THO code systems and value sets should have the steward as mandatory. Would help with knowing who to follow up with in the UTG process.
In Vocab WG - Motion passed: Vocab WG recommends that TSMG implement a rule stating that: Every HL7 code system in THO must have a steward WG. The steward WG has to be one of the WGs that are authorized to propose making changes to an HL7 code system in THO.
RD: Suggesting there may need to be a better description of what a Steward is / what that entails before crafting a policy statement. When there is a proposal for the definition, this issue would be brought back to this group.
THO release schedule
Need feedback from TSC/HQ
AI: the information about these discussions will be fw: to Bryn & Rob to support presentation / discussions with the TSC
Status updates (no changes from last week)
Onboarding new development resource, Lawrence, to help with Jira automation
There is a need for some specific requirements for Lawrence to work on
TK: Josh has been in touch to develop this list of specific requirements
Will create business requirements for a UTG Editor
Sprint 2 of UTG Jira development items with a focus on release tracking in progress
Refining current implementation of release tracking
