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
X
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."
Agenda Topics
Meeting was recorded
Agenda Outline
Time Allocation
Lead
Agenda Item
Administrative
5
JB
Rollcall & Proxies
Note that meetings are recorded
Approval of meeting minutes
Status
10
JB
The CI build frozen since 2/20 (i.e. no more proposals will be processed) with release of THO v3.1.0 is in progress
Grahame and Ted suppressed warnings from missing <caseSensitive> elements
Ted notes that many from V3 also remain (may be retired)
Unsure of the process required now that TSMG is newly formed since the last release
Current process models how we track other IGs
If we want to continue that, we may need to see how the model aligns with the organizational FHIR IG process
To be discussed later: Is THO an IG? It is not a FHIR IG
Need approval by Friday 2/25 at the very latest
Clarified that in TSMG charter, TSMG has the authority to approve publications of THO
Fields needed for release
Publication request
TSC approval (link to TSMG approval)
Next steps: Create publication request and vote on it tomorrow during TSMG's main call
Sprint 2 of UTG Jira development items is in progress, focusing on release tracking
Still need to carve out time to work on this, but made progress on updating descriptions for each state in the UP project
Funding secured to help with automating some of the Jira workflow steps
Josh working with Lawrence to get him started, need to follow up
Dan to double-check agreement with Lawrence
Biggest priority is notifications
THO work in progress (did not make 3.1.0 release)
List all resources by <title>:
UP-277
-
Getting issue details...STATUS
Handle external content in "All Code Systems" tab
Moving "Using X with FHIR" pages
Update from Vocab call
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
Subcommittee Work in Progress
40
JB
THO release schedule
Need input from TSC/HQ
No policy for announcing freeze/release
Ted suggests that the announcement goes on the HL7 website
Dan suggests adding it to the HL7 calendar: HL7 Calendars as well as announce via Zulip (which thread?)
Lynn posts the announcements of publications in the Announcements stream under New Publication. THO publications could be announced in zulip there. Or maybe under a new topic of New terminology.hl7.org Publication.
Issues raised during THO release
No governance policy for <caseSensitive>, suggest discussing on HTA call
On discussion on terminology services, if a code system does not identify if codes are case sensitive or not then servers cannot validate correctly
Also helps curator by not cluttering with warnings
Many affected are retired
INFO should be thrown for external code systems, WARNINGS for HL7 code systems
What about code systems with content "not-present"?
No way for publisher to know whether or not to throw the warning
Could ask Grahame to not throw warnings for these as well, based on url being terminology.hl7.org
Tracked by
HSCR-155
-
Getting issue details...STATUS
and its subtasks
Outreach subcommittee is reviewing draft email to Management Groups
Review other recommendations
Next Steps
Move forward with plan to request that Management Groups provide at least one person to be part of an OSG for the Product Family OSGs
Draft email provided to TSMG Outreach Subcommittee for review
Lisa provided feedback that even after relaxing requirements there just aren't enough people to do the work, although it is important
Perhaps the new implementation division should be involved in this issue
Ask Rob and Peter for help recruiting for Realm-Based OSG
Ask TSMG main call for Vocab/TSMG members for the Vocab OSG
TSC clarification
Need to ask for clarification for ad hoc OSGs (separate request) and how OSGs may change but membership does not automatically refresh on tickets already in Consensus Review
Expectations for when members of an OSG need to change
Adjournment
0
JB
Call adjournedat 5:00PMEST. Next call in one week at 4:00PM EST March 1, 2022.
