National Institute of Standards and Technology (NIST)
M
Davera Gabriel
Johns Hopkins University Institute for Clinical and Translational Research
M (CSDO)
Dan Vreeman
HL7 International
O
P
Ted Klein
Klein Consulting
O
P
Marc Duteau
HL7 International
O
P
Joan Harper
Canada Health Infoway
O
John Snyder
National Library of Medicine
O
P
Rob Hausam
MITRE
O
Alex Kontur
ONC
O
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).
Agenda Topics
Meeting was recorded
Agenda Outline
Time Allocation
Lead
Agenda Item
Administrative
5
JB
Rollcall & Proxies
Note that meetings are recorded
Agenda check
Status
10
JB
Responses for RFP for web-based terminology editor to support UTG/THO were due 7/1
Marc has indicated that he is working on the ~9 tickets that need to be implemented in the CI build this week to prepare
There are other considerations in preparation for R5
Removing identifier systems from R5
Adding external code system metadata stubs from HTA pages to THO and removing external code system identifier information from R5
Handling hl7.org/fhir value sets that reference THO anchored code systems
Handling content in FHIR spec that is anchored in THO (see next topic)
TK: The only items in Sent for Implementation are HTA items that do not include coded content. What are people looking for with the release?
JB: Follow up with Carol and Rob about what THO content is driving the need for the release
TK: Possibly we could have a THO release by 7/29 with Sent for Implementation content only
There is also an issue with one of the packages, 3.1.0, that wasn't reported as an error or warning so is happening transiently while content is processed during the build with a duplicate value sets. Concerned with what caused it or where it came from. Unsure if this will be incorporated in next release.
Handling THO anchored content in the FHIR spec FHIR-37440
-
Getting issue details...STATUS
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
JB to respond to FHIR ticket to start conversation with Grahame
Discussed adding a tab to list and describe all extensions in THO
This will be brought to Vocab call this week and TSMG Monday
Individual extensions would be added through UTG change proposal
Subcommittee Work in Progress
15
JB/RD
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...STATUS
Add tabs for deprecated content (based on deprecation task force)
UP-321
-
Getting issue details...STATUS
Add default value of 'true' for all code systems without a <caseSensitive> element (mainly external code systems) unless otherwise specified to resolve warnings in THO
UP-322
-
Getting issue details...STATUS
Changes submitted
Need to start discussions (with FMG?) about having ability to render extensions in THO
Ask Reuben to follow up
Execution of Deprecation representation and policy in UTG/THO
