ANSI Anti-Trust Policy:  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).

Administrivia

Approve Minutes

• • 2023-04-27+Main 

    • Motion to accept as distributed: JD Nolen/Dan Rutz: Against: 0 Abstain: 1 In Favor: 9

OO Project Proposal Triage

• No new Proposal (reviewed 5/4/2023)

Other (Project Approvals, NIBs, etc.)

• Expiration of standards:
  • HL7 Version 3 Standard: Clinical Statement Pattern, Release 1 - August 2024 - Re-affirmation or Withdrawal for May 2024 Ballot
• Catalog Ballot Reconciliation (2020-Sept)
  • Where are we with validating that the meeting minutes can be applied to jiras and update those jiras – there is one row missing a disposition
    • We will handle this on the catalog call tomorrow along with any other outstanding jiras
• ONC New Proposed Rule HTI-1 on Information blocking and increase USCDI to version 3
  • Laboratory RFI (LOI, LRI, FHIR COW/FOE, and could consider commenting on Catalog, LIVD efforts) - See pages 331 - 334

Other OO on FHIR Trackers that need a vote  

FHIR-34491 - Getting issue details... STATUS - 

Motion to find it Not Persuasive

• JD Nolen / Marti Velezis : 10-0-0
• Resolved - No change required

OO on FHIR Block Vote (sent on 4/26/2023)

FHIR-7194	2015May core #254 - nothing disagreeable here. But what is described would apply equally well to almost any discrete observation		May 10, 2015	Apr 25, 2023	Clement McDonald	TRIAGED	Unresolved	DSTU1		US Lab [deprecated] (FHIR)
FHIR-7195	2015May core #255 - be aware that ask at order entry questions are still under development		May 10, 2015	Apr 25, 2023	Clement McDonald	TRIAGED	Unresolved	DSTU1		US Lab [deprecated] (FHIR)
FHIR-8007	2015May core #1331 - Develop lab value set that is more specific then 'all' of LOINC.		May 10, 2015	Apr 25, 2023	Brett Marquard	TRIAGED	Persuasive with Modification	DSTU1		US Lab [deprecated] (FHIR)
FHIR-9213	Consolidate gao-result and gao-alternate into a single profiled BasicResource		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9214	Allow multiple Order submission on Gao $evaluate service		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9215	GAO-Order as a Wrapper May Not Make Sense		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9216	Gao-Order.Reason should only be a codeablConcept		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9217	Clarification for Gao-Order.date		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9218	Provide Separate Gao Services for Questionnaire evaluation		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9219	Gao Service should be modeled as a conformance statement, not as Device		Jan 11, 2016	Apr 25, 2023	Danielle Friend	TRIAGED	Unresolved	DSTU2		Guideline Appropriate Ordering (GAO) [deprecated] (FHIR)
FHIR-9231	us-labs has different ICD-9CM / ICD-10CM system URIs than expected		Jan 12, 2016	Apr 25, 2023	Alexander Henket	TRIAGED	Unresolved	DSTU2	ValueSet [deprecated]	US Lab [deprecated] (FHIR)

Motion to accept as sent out:

• JD Nolen/Elliot Silver: Against: 0 Abstain: 0 In Favor: 10

• Check back in June for progress

UP-44 -no value set content defined for v2 table 963 value set 

• We had discussed and taken a vote on this back on 2022-06-10, but I'm not sure at this point if that is still what we actually want to do.  If we discuss it again together hopefully we can decide if that is what we want or we can figure out a good alternative plan.

Discussion this week:

• The following value set should be used: http://build.fhir.org/valueset-device-safety.html - This binding was done in FHIR
• Code system is pointing to NCBI Thesaurus
• Used in DEV-14
• Add to the HCP Call
  • Need to add example from EUDAMED to add to the list of example values
  • Create a JIRA to get the terms added into the http://build.fhir.org/valueset-device-safety.html
• Craig Newman: https://terminology.hl7.org/CodeSystem-v2-tables.html already references the FHIR value set for device safety
  • Need to determine if this is matching in Table 2C - make sure Michael Faughan is aware of this issue – he is working on syncing Chapter 2C content
  • and determine if it gets updated in the next release
  • For V2 we will use what is in the FHIR value set
  • Will need to figure out how to properly document the fact that the value set is drawn from 2 code systems 
• Next THO deadline is June 4, 2023
• Create a JIRA for v2
• Leaving UP-44 open for now – so that the new tickets and this one can be linked
• 5/3 - Need to follow up with Ulrike Merrick to see if the v2 Ticket was created.

Add "GTIN", "serialized GTIN" and other UDI Types to UniveralIDType (http://terminology.hl7.org/CodeSystem/v2-0301) to be able to specify that a Universal ID is of "GTIN" Universal ID Type.

This would help to apply to HD Data, EI Data, EIP Data, etc. the Universal ID Type "GTIN", examples are:

HD based Data (HD-2 (Universal ID) is of "GTIN" Universal ID Type:

• MSH-3 (Sending Application), 
• MSH-5 (Receiving Application), 

EI based Data (EI-3 (Universal ID) is of "GTIN" Universal ID Type:

• SAC-3 (Container Identifier), 
• SAC-4 (Primary (Parent) Container Identifier)
• PRT-10 (Device ID)
• PRT-16 (UDI Device Identifier)

EIP based Data (EIP-1-3 and EIP-2-3 (Universal ID) is of "GTIN" Universal ID Type:

• SPM-2 (Specimen ID), 
• SPM-3 (Specimen Parent IDs), etc.
  • Both of these are related to the work GS1 is currently discussing to maybe create a "serialized" GTIN for all containers which would be a worldwide unique code (would be default barcode on tubes, slides, tags etc.) 

CX datatype uses HL70203 for example in PID-3 (not applicable), but maybe in OBX-5.

V2-25519 - Getting issue details... STATUS  

• Added to WGM Friday Q1 (see ticket) 
• Application Identifiers: https://www.gs1.org/standards/barcodes/application-identifiers
• there are other agencies that assign UDIs that may need to be considered as well
• Motion to find Persuasive
  • Will create a THO proposal to add the Issuing Agencies into the Universal ID type
  • Rob Hausam /  Kathy Walsh : 10 - 0 - 0
  • Assigned to Ralf Herzog to create the THO proposal

4/27 -Discussion:

• New jira is to track which agencies need to be considered
• Also use in EI – for the serial number of the device ID
• GS1 has other application identifiers – https://www.gs1.org/standards/barcodes/application-identifiers GTIN is only one of them, so may have to review these and then we could use the GD1 data matrix format for many different identifiers
  • 10, 11 17 and 21 already have other parts in the UDI carrier

• V2 Dashboard 

Discussion Topics: 

JIRA 

Block Vote of old Jira trackers set for next main call - see: https://confluence.hl7.org/pages/viewpage.action?pageId=161072874#id-20230504Main-OOonFHIRBlockVote(senton4/26/2023)

• JIRA Backlog Cleanup -

• • Plan of attack to cleanup stale JIRAs.
  • Need to triage the older tickets to see if they are still relevant/valid (any volunteers???)
    • We may just want to create block votes for any tickets that are no longer relevant/valid
  • We have been getting 6-12 tickets per meeting if we have prepared the tickets in advance
  • We will continue to work through the backlog

The following are draft pages to organize and author content for each of our health care product resources: 

• BiologicallyDerivedProduct
• Devices
• Nutrition Product
• VisionPrescription

OO Resource Coverage

• Need to discuss developmental roadmap for each of the OO resources for R6
• Added R6 planning to WGM agenda
• Need to discuss what needs to be done prior to WGM to prep for discussions
• Add Resource reorg comments to module pages

Notes

• Marti revised related resource for each topic area to where the resources align to current modules
• Definitional resources were in workflow (pattern is still there) but those are now in administrative – Marti and Jose to take off-line