2022-11-08 InM WG Agenda/Minutes

Date: November 8, 2022

Facilitator: Isaac Vetter

Note Taker: Riki Merrick

Attendees

Present	Name	Affiliation
	Anthony Julian	Mayo Clinic
x	Nick Radov	United Healthcare
x	Isaac Vetter	Epic
x	Ulrike Merrick	Vernetzt, LLC
	Craig Newman	Altarum

Create Decision from template

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).

Agenda Topics

Agenda Outline	Agenda Item	Meeting Minutes from Discussion
Management	Quorum Reached (co-chair + 2) Y/N
Management	Minute Approval	Skipped
	Rob McClure asked for gender harmony issues to be discussed outside of this recurring InM call due to a standing conflict.	Ulrike Merrick to reach out Rob to see, if he can attend the V2 Management calls to discuss this topic there instead - those are weekly on Fridays 9-10 AM alternating with 3-4 PM ET. If that is not feasible, we may consider switching FHIRcast call time with this call for this purpose (short term) - note: FHIRcast call for 11/22 has been canceled
Methodology	Nick's v2 SN jiras: [V2-25401] Deprecate SN.1 (Comparator) value of "=" - Jira (hl7.org) [V2-25402] Clarify that SN.1 (Comparator) can be used for antibody titer observation values - Jira (hl7.org) [V2-25403] Deprecate SN.3 (Separator/Suffix) value of "+" - Jira (hl7.org)	For all of these, we are just discussing, but not voting today [V2-25401] Deprecate SN.1 (Comparator) value of "=" - Jira (hl7.org) changing the datatype for the same test is difficult for some systems, so when both NM and SN can be used, OO has recommended to use SN, as that can accommodate comparators, ratios and ranges the base standard should list what should be done, not accommodate the lowest common denominator added a comment in jira Ulrike Merrick to take this issue to OO [V2-25402] Clarify that SN.1 (Comparator) can be used for antibody titer observation values - Jira (hl7.org) That makes sense and should be called out, at least add an example Ulrike Merrick to take this issue to OO. See comments in jira. [V2-25403] Deprecate SN.3 (Separator/Suffix) value of "+" - Jira (hl7.org) That makes sense and should be specifcally called out - important to know the range of +, which is suported with different SCT codes Ulrike Merrick to take this issue to OO. See comments in jira.
	Riki to create block vote for Da Vinci Notification jiras that had been CfFU.	General discussion about notification IG: Notifications not specifically named in the CMS rule CMS is requiring V2 messages for ADT from hospitals that are subject to that regulation – or they are doing this using DIRECT – payors want to have these via FHIR in the long run Notifications IG is waiting for subscription uptake (R4B may not get uptake, since R5 is about to come out) to see, if we need to update that IG to support subscriptions Current ADT message data quality (patient name, provider name and organization name is the only required elements per the regulation) – DIRECT trust has put out the ADT V2 IG (they want to use direct messaging for transport) – if we can at least use that message profile, even if not using Direct for transport
Management	Next agenda
Adjournment		Adjourned at

Supporting Documents

Outline Reference

Supporting Document

Minute Approval

V2 unresolved issues filter

T	Key	Summary	Assignee	Reporter	P	Status	Resolution	Created	Updated	Due

Loading...

Refresh

InM unresolved FHIR issues

T	Key	Summary	Assignee	Reporter	P	Status	Resolution	Created	Updated	Due