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
Ravi Kafle
Washington State Department of Health
O
Abdullah Rafiqi
ICF
O
Hope Gray
UAB - Birmingham, HL7 Intern
O
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
Jess cannot run call on 10/25, check with Reuben
Reuben will run the call
Status
10
JB
THO freeze scheduled for 10/23
Jess expects fixing of ICF, NCIT and ATC entries, and adding subtabs for identifier systems
Reuben wants to add rendering of existing profiles and extensions as approved by TSMG
Any update from V2MG on alignment of V2 publication with THO?
Michael has been working on this, pulling out of Chapter 2c publication then diff against those artifacts in THO
New Business
30
JB/RD
Marc created dashboard to track UTG tickets implemented in each release
There are 42 code systems anchored in THO that are only in the FHIR core specification
Need to do same analysis for value sets
Assume they need to be moved but would like to finish analysis
There are 72 code systems and 190 value sets that are potential duplicates across THO/FHIR
Continue to discuss how to address changes across the following code system elements:
meta.lastUpdated (all) - not consequential
date (all) - not consequential
url - once moved, should all be anchored in tho
experimental (19) - we assume that all code systems may have been set to false upon moving to THO but this requires verification
title (23)
valueSet (70)
meta.profile (62) - not consequential
description (22)
publisher (18) - not consequential
name (8) - consequential, involve WGs if needed
contact (18)
status (17)
oid (25) - consequential and require cleanup, need to understand how this is happening from Grahame as there are duplicate OIDs across and within THO and FHIR (urn:oid:2.16.840.1.113883.4.642.1.0)
property (1)
hierarchyMeaning (1)
extensions
telecom
standards status
workgroup
fmm
concepts (18) - consequential, involve WGs if needed
Discuss how to address changes across the following value set system elements:
name (29)
oid (5)
status (19)
standards-status (10)
title (63)
description (25)
normative-version (1)
experimental (159)
immutable (123)
compose.include.system (19)
date (180)
extensions
fmm (25)
Goal is to get a list of resources we consider duplicates or easily categorizable fixes (only have non-consequential differences) and then a list of duplicate resources that need to be consolidated/resolved
Grahame can handle the duplicates and WGs will need to be involved in the resources that need consolidation
