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).
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
Management
5
CM
Welcome to members and guests
Rollcall & Proxies
Note that meetings are recorded
Administration
15
CM
Announcements
Holiday Schedule: canceled meetings 12/22, 12/29
Update from TSC
TSMG Standing Subcommittee Updates
HL7 Terminology Authority
10
CM, RD
HTA update - Meeting next week: 12/16
OIDs requirement across HL7 product
Currently a requirement for CDA, not FHIR
CMS-HCC, CMS-RxHCC ... coding system requirement
RD: suggesting that unless a request is made to the HTA for an OID, to NOT make this a requirement as a part of the standard HTA process. There is significant overhead main ting this part of the process. Per this link OIDs can be created and maintained by the THO, thus reducing the overhead for external system registration, especially in light of the THO becoming the official source of truth for identifier registration.
ST: In Germany we are using OIDs, but strategically are moving more toward FHIR / URI format. Germany also has their own OID registry, and for those entries tat re not managed centrally by HL7 we have a registry for just German records
JH: in Canada we would most likely use an OID anyway becuase we do not anticipate what version we might use (V2, FHIR). Within Canada we do jurisdictional registration that doesn't get promoted up to HL7 / realm designation
CM: We have mentioned that THO will become the official source of identifier records. If this becomes a policy decision, it must go to the TSC for a decision. There could be a financial impact to HL7 for which we do not have information regarding, nor a strategy for replacing that revenue stream if this is adopted.
Action item for Bryn: go to TSC... if an external code system doesn't already have an OID assigned, then the HTA would adopt a process to automatically generate the OID as a part of this process and not require external system owners to register and pay for a new OID, as is the process now. The minimal set of metadata will be added to the OID registry to prevent the use of the allocated OID by any other party.
Implication of this would be to consider the future of the OID registry and replication of the information and search capability in the OID registry in the THO. Another Action "in the wings" or implied in this action is cleaning up the OID registry, updating the records to reflect a current source of truth.
Timeslot(s) for "Ask an Expert" - Rob McClure, Peter Jordan
RD: Must check in with Sadana re: any formal education at HL7. Proposal for not a formal HL7 educational offering, need to develop the content to form a proposal for this kind of a session.
BR: will be running the same Quality Measures scenario in January, can participate in a joint session again
Need to locate a server with the appropriate content to support the QM use case
(the link above should be confirmed & updated if necessary) process document reflects edits made 29Nov21 (after the TSC meeting) next step is for the TSMG to provide input
