Office of the National Coordinator for Health Information Technology (ONC)
National Library of Medicine (US)
Washington State Department of Health
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-04-11 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."
The committee will create an additional meeting to discuss & resolve these
Call for UTG OSG Voters
Management Groups forProduct Family OSGs
FMG: John Moerke
CMG: Lisa Nelson, Alexander Henket
V2: Michael Faughn, Frank Oemig, Rob Snelick
Vocab WG follow-up: Policy Requiring Identification of Stewards for HL7 (Internal) Code Systems
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.
Out of 797 code systems, 236 do not have a Steward value
38 V2, 147 V3, 47 FHIR, 3 unified code systems
Current supported 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
Vocab WG to run a query for each code system across FHIR core to identify the resources and their responsible WG(s) for each listed code system.
Robert Hausamwill check with Lloyd and whether and how we can do this.
Will bring this back for the Vocab call in 2 weeks.
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.
Austin Kreisler reviewed list of V3 code systems and assigned 3 to Structured Docs
Meeting weekly with Lawrence to review automation progress
GitLab is configured
Working on automatic verification using IG Publisher upon submission of proposed changes
Technical Steering Committee (TSC) matters
Decision Making Practices
Default Decision making practices are here, select portions of this document are available to be modified by WGs
comparing defining quorum section - changed subcommittee and electronic voting section(s)
also changes to the manner of making routine decisions, whether there is a requirement for voting or not
Reuben: an outstanding unknown issue has to do with how subcommittees make decisions - do they vote or not?
Lisa: CMG doesn't have voting in their sub-groups, Structured Docs also does not vote in their subgroups
Sub-committee eVoting: added section "quorum for the TSMG requires that a co-chair and at least 50% of the current members be present... Any sub committee meeting... " this section should be reviewed by the TSMG membership and approved in an upcoming meeting before going to the TSC
Motion to accept changes to document RM, Second: DG Motion passed 7-0-0