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
Sprint 2 of UTG Jira development items has been pushed to production
Includes workflow state cleanup and addition of release tracking
Continuing to work with Lawrence Gerstley on Jira automation for submitters
Subcommittee Work in Progress
40
JB
THO cleanup
Cleanup of old UTG GitHub branches based on policy
Update release labels
Fixing the "All HL7 Code Systems" tab
Adding tabs for deprecated content (based on deprecation task force)
Set <caseSensitive> to true for remaining code systems (unless otherwise specified)
Unsure if numeric-only identifiers should be true or false
Clarify on HTA call Thursday
Need to start discussions (with FMG?) about having ability to render extensions in THO
Tracked by
HSCR-155
-
Getting issue details...STATUS
and its subtasks
Email sent to Management groups on 3/8 requesting oversight group voters
Responses due by 3/31, reached out again today, 4/5
FMG has nominated John Moerke for the FHIR OSG
Remind MGs that nominees can include WG participants
Will continue to follow-up on filling Realm-based and Vocab OSGs
THO release schedule
Need input from TSC/HQ and they have requested some information from TSMG on documentation and level of effort
Info sent to Rob and Bryn who will follow up with TSC
Vocab suggests that TSMG require all code systems to have a Steward
UTG submitters would need to get WG approval from the Steward to propose changes to the code system
Discussed on main TSMG call but no one wanted to make a motion to make this a policy
Steward definition
The WG responsible for the maintenance and upkeep of the code system (not to be confused with Publisher who makes the content available)
This implies that the WG has the domain expertise/knowledge related to the code system
The primary point of contact for questions or issues with the code system
FYI: Vocab added an extension for steward, there is a proposal to update the definition of publisher (which was intended to represent steward) and remove the extension
Might be a good idea to get a count of how many code systems in THO do not have a steward value
Michael Faughn performed analysis on the number of code systems without a Steward value
Out of 797 code systems, 236 do not have a Steward value
Code systems broken out by product family:
38 V2, 147 V3, 47 FHIR, 3 unified
Current TSMG solution is to make corresponding Management Group responsible (by either having them assign the WG responsible or by assigning them to the MG itself)
In the FHIR space, it could be the resource owner
V2 - make the V2 management group responsible
V3 - will be a multi-management group exercise. CMG will take a look at the V3 sets first. FMG will take a look at the list next to determine which is the appropriate responsible party.
Workflow process for use of internal code system identifiers in FHIR and beyond
Need to determine what kind of content should/should not be added to THO (i.e. if used in a balloted IG)
