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-01-16-20 WGM - will do after R5 is published

  • 2023-03-02 Main
    • Motion to approve as posted Marti, Riki, no further discussion, against:0, abstain: 1, in favor: 14

OO Project Proposal Triage

• PSS-2171 - – Adverse Event Clinical Research Implementation Guide

• PSS-2170 --School Based Physical Fitness Testing Domain Analysis Model

Other (Project Approvals, NIBs, Expiring standards, etc.)

• Expiration of standards:
  • HL7 Version 3 Standard: Clinical Statement Pattern, Release 1 - August 2024 - Re-affirmation or Withdrawal for May 2024 Ballot
• Update to Charter
  • We reviewed and made updates during WGM - we will have to re-create based on the latest version here (OO Mission and Charter - Pre-Publication) and the notes from the WGM minutes https://confluence.hl7.org/pages/viewpage.action?pageId=139660361#id-2022091923WGM-Mission/CharterReview
  • And we need to change Vocabulary to Terminology Infrastructure
  • Then we can upload and send the link to Anne
• Email from Lynn about submitting withdrawal Request for CMET Spec - Co-Chairs (Ulrike Merrick ) to deal with

PAC Submission

• Request endorsement of the following submission to PAC for O&O attribution in the letter

  • Suggested Paragraph for inclusion in the HL7 response to the CMS-0057-p Advancing Interoperability and Improving Prior Authorization Processes proposed rule

    One of the significant issues identified by the HL7 balloting and review process for the Burden Reduction Implementation Guides is the need to make information regarding prior authorization (PA) and documentation supporting medical necessity assembled by the ordering provider available to the performing provider. This may either be documentation to enable the performing provider or supplier to submit a prior authorization if they are required to do so, or to inform the performing provider supplier that an authorization has been provided. CMS may wish to note that HL7 has approved extending an implementation guide focused on exchange of this information for Durable Medical Equipment (DME) and Home Health services, supported by CMS, to all exchanges of FHIR-based orders and the supporting documentation between an ordering and performing provider.   The updated IG is currently entitled FHIR Orders Exchange (FOE), and is intended to address a common approach across orders and referrals to external providers and suppliers.  It’s primary sponsor is the HL7 Orders and Observations WG  and the updates should be balloted in the HL7 September 2023 ballot cycle.  While this IG is not ready to be cited as recommended or required in the expected final rule, it may be appropriate to note its development in the preamble to encourage implementers to support a common method of exchanging PA information between an ordering and performing provider.

    We also note that enabling the performing provider or supplier to obtain additional information that may have been missing or not yet available on the initial order transaction, the Da Vinci CDex implementation would similarly be targeted to support request for further information form the ordering provider.

  • Motion to submit the updated text (removed extra space before "The updated", fixed typo "form ordering provider" to "From ordering provider" added "yet" in front of "ready to be cited: Riki, Rob, no further discussion, against:0, abstain: 4, in favor: 11

May 2023 WGM - OO, Joints and WGM+ Coordination - not discussed

• 2/24 - Room Requests have been made - Need to check about 3 weeks out to cancel any rooms not needed.
• OO WGM 202305 - Agenda
  • Updates to the agenda were posted (link above)
  • Need to follow-up with BR&R with a list of topics (Marti Velezis) and date/time  
• WGM+ Schedule
  • Monday Q1 - SHALL not schedule WGM 
  • Tuesday Q1 - SHOULD not schedule WGM (ONC/USCDI, Argonaut, Gravity)
  • Rob Hausam (not available TH  Q1/Q2)

NOT DISCUSSED

E-signature Update:

• The e-signature draft was submitted to the PAC.  I did get a request from Christopher at Quest to quote a paragraph and am following up with PAC on when we are locked in enough to do so.

Vocabulary

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 still will 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.

Add 'GTIN' to HL70301 and HL70203

V2-Jira Review (time permitting)

• V2 Dashboard 

R5 Wrap-Up

• Update developmental roadmap in diagnostic module http://build.fhir.org/diagnostics-module.html#roadmap – must do by end of QA period
  • Create a confluence page.  JD to make the Jira for this change.
  • Rob will updated before the COW call tomorrow at 10 AM ET.
• Review FMM levels, because all 0 will be removed by policy, unless we ask for an exception
  • ask FMG to permit to progress into the publication with an FMM0 to allow further development together with the other resources to which they are related.
    • DeviceDispense, missing resource proposal approval
    • InventoryReport
    • InventoryItem – has resource proposal conditionally approved to keep them at FMM0
  • BiologicallyDerivedProductDispense – has approved resource proposal – move up to FMM1
  • DeviceAssociation - has approved resource proposal – move up to FMM1
  • Motion to have the following FMM levels Ralf, Elliot, no further discussion against: 0, abstain; 1, in favor; 11
• QA issues to deal with: 175
  • Reviewing the ones we agreed to make changes to – need a team call for Rob, Jose, Marti, JD – use the catalog call slot tomorrow for this work

Discussion Topics 

PACIO Question (20 min)

Discuss the use of the Observation.method field in the PACIO Personal Functioning and Engagement IG. We have a ticket (FHIR-38308) from our September ballot about using an approach like Gravity has for personal characteristic observations (e.g., race) within our IG that focuses on therapy-based observations in the post-acute care world. We have a proposal for how this would work on our PACIO IG that we’d like to get feedback on and also get your thoughts on a few edge cases.

• FHIR-38308
  • Questions asked of the patient or a relative or from provider observations
  • Need to have source of information
  • Similar approach to Gravity project
    • They use observation.method using this value set: http://hl7.org/fhir/us/sdoh-clinicalcare/2022Jan/ValueSet-SDOHCC-ValueSetObservationMethod.html
  • What about using provenance resources?
• DISCUSSION:
  • Not sure this is an appropriate use of method
  • Should use performer for this instead
  • Method might be appropriate for the actual form used – specific
  • Should use provenance for that -that’s what that is designed
  • US core folks also pointed towards provenance for this use
    • Can indicate the role
  • Performer is the person responsible for the information
    • But this may be sometimes conflated with the person recording the information
    • If the physician asks the question – would that make the patient the performer?
      • You also need to capture who conducts the interview
    • The definition is about “responsible” – the clinician is responsible for recoding this information
    • How is the level of pain answer documented?
      • Assumption is the default is from the patient
    • Should we create a standard extension to the resource to record the source of answer?

CALL ADJOURNED 1:59 PM ET - BELOW NOT DISCUSSED

VisionPrescription

• Confirm March 14, 11-12pm ET FM Meeting that OO joins to finalize ownership transition 
  • Call info: https://www.hl7.org/concalls/CallDetails.cfm?concall=63932
  • Marti plans to attend

Modules (Updates on any progress)

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

• BiologicallyDerivedProduct
• Devices
• Nutrition Product

• JIRA issues (for discussion)
  
  • Diagnostic Report
    • FHIR-40540
      • Wait for the FHIR-39168 to determine if the items in this ticket were addressed before closing/retracting
      • Need to check status with Robert Hausam if it has been updated for R5 QA period
    • FHIR-19362 - Incorrect reference direction Procedure -> DiagnosticReport
      • What do we want to do with this — it was not included in R5
    • FHIR-40581 - Getting issue details... STATUS Updates to Developmental Roadmap in Diagnostics Module. 
  • Observation
    • FHIR-39448 - Vital Signs Panel 
      • Need to check status with Robert Hausam if it has been updated for R5 QA period
  • 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

FROM CHAT:

• Andrea Pitkus 1:20 PM
  • the performer (who is collecting/documenting the observation)?
• Karl Naden (MITRE) 1:22 PM
  • http://hl7.org/fhir/us/sdoh-clinicalcare/2022Jan/ValueSet-SDOHCC-ValueSetObservationMethod.html
• Andrea Pitkus 1:23 PM
  • concur with rob
  • concur riki
  • aligns with loinc method too whether survery, assessment, lab test, radiology, etc
  • http://hl7.org/fhir/compartmentdefinition-relatedperson.html
• JD Nolen 1:30 PM
  • https://build.fhir.org/observation-definitions.html#Observation.performer
• Andrea Pitkus 1:32 PM
  • Many AOEs are observations, including time, date, LMP reported by patient, etc
  • Member is used for care teams includes reference to related person, pt, practitioner etc – but no link to the observation resource
  • patient upon which the observation is recorded.