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
Ted Klein
Klein Consulting
O
P
Marc Duteau
HL7 International
O
Joan Harper
Canada Health Infoway
O
John Snyder
National Library of Medicine
O
P
Rob Hausam
MITRE
O
Alex Kontur
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).
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
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
No immediate need presented for ad hoc THO 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
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
