Date/Time: 02 Aug 2022
https://www.hl7.org/concalls/CallDirectory.aspx for meeting details. Attendees
Attendee type: M - TSMG Member O -Observer / Guest Attendance: P - present A - Apologies X - (Apologies with Proxy)
Reuben Daniels Saludax M
Apelon, Inc. M P MaxMD M P National Institute of Standards and Technology (NIST) M Davera Gabriel Johns Hopkins University Institute for Clinical and Translational Research M (CSDO) HL7 International O Klein Consulting O P HL7 International O Canada Health Infoway O National Library of Medicine O P MITRE O ONC O P Ravi Kafle Washington State Department of Health O Abdullah Rafiqi ICF O P Hope Gray UAB - Birmingham, HL7 Intern O P Martha Jones George Mason, HL7 Intern 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).
Meeting was recorded
Agenda Item Administrative 5 JB Rollcall & Proxies Note that meetings are recorded Agenda check Status 10 JB No responses received for RFP for web-based terminology editor to support UTG/THO Will not be reissued due to ONC funding schedule, remains a high priority that may be included in next award New Business 30 JB/RD Reminder to review Terminology Expectations for IG Developers Scheduling next THO release No immediate need presented for ad hoc THO release Handling THO anchored content in the FHIR spec
FHIR-37440 Getting issue details...
A comparison from this commit must be performed. Per Rob H: this is ~1600 files, thus this cannot be a manual process to inventory / check the possible changes Does this need to be done before R5 - a high priority task??? Can we escalate this other technical resources? This doesn't require a terminology SME. Two classes of checking Content that exists in both THO and R5 with the same canonical URL Exact match on content - remove resource from R5 Grahame modified version so that it referenced THO or FHIR based on the version, not sure logic though If minor version is 1, it was migrated as part of 4.0 cleanup and 4.1 prep. If 3, it was part of prep for R4B, Ted saw some with minor version a 6 All have a major version of 0 in THO due to some build hack to pull out the right thing and not give duplicate resource errors Versions are different - look to see if the content is different & determine which content is correct - a manual review Content is different, do manual review to determine which is the most up to date - another manual process Content anchored in THO that only exists in R5 Move to THO and remove from R5 Michael has completed an initial review Assumption is that resources will share <id> (we know this isn't a rule but we need something to link the resources) Will go back and compare NPM packages for THO CI build and FHIR CI build Some cleanup to occur on the list of discrepancies Once we have this list we will be better positioned to compare the resources We know this will likely be iterative to determine which changes matter (we know url and version will be changing) Need reliable patterns for making block decisions/updates Confirm scope of moving over external info from http://build.fhir.org/terminologies-systems.html
FHIR-35933 Getting issue details...
See resolution in ticket above Entries with "Using X with FHIR" will remain, but will be linked to THO Changes to bulk update from HTA pages do not need to occur prior to R5 freeze but would like to get done before R5 is published (early 2023) Only non-substantive changes can be made during this time Other things would need to go through FMG For identifier systems, Jess to coordinate with Lloyd to get them removed from FHIR spec since they have already been added to THO Subcommittee Work in Progress 15 JB/RD Reuben to raise adding extensions to THO in their own tab (on main TSMG call) Related ticket:
FHIR-28612 Getting issue details...
THO cleanup These tickets have approval from TSMG to proceed in UTG Fix the "All HL7 Code Systems" tab to exclude external content
UP-320 Getting issue details...
Add tabs for deprecated content (based on deprecation task force)
UP-321 Getting issue details...
Execution of Deprecation representation and policy in UTG/THO Deprecation Policy Framework documents policy and next steps Immediate priorities Perform inventory of deprecated content across THO Create tabs where deprecated content exists Document deprecation and expectations around deprecation on THO subtabs Must also document retired, as there is often confusion between deprecation and retirement Requested IG Publisher change to render identifier.period for CodeSystem and ValueSet: https://github.com/HL7/fhir-ig-publisher/issues/455 Task force recommendation review and implementation (voting, quorums, WG health, etc.): UTG Task Force Recommendations to TSC Tracked by
and its subtasks
HSCR-155 Getting issue details...
Continuing to fill OSG voter slots FMG: John Moerke, Bryn Rhodes, suggest adding Rob Hausam CMG: Lisa Nelson, Alexander Henket, Marc Duteau V2: Michael Faughn, Frank Oemig, Rob Snelick Will continue to follow-up on filling Realm-based and Vocab OSGs Vocab suggests that TSMG require all code systems to have a Steward 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. Rob Hausam reached out to Grahame to determine best way to do this Might be able to use binding to determine steward by mining it out from resource that is referencing it Adjournment 0 JB Call adjourned at 4 :55PM EDT. Next call in two weeks at 4:00PM EDT August 16, 2022. Action items