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

Meeting Details

Date: 

Time: 2PM

Coordinates:  Join Zoom meeting: https://zoom.us/j/5100467805 | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)

Attendees

Agenda

  • JIRA Tickets - Backlog
  • Next Meeting

LINKS TO JIRA - OO on FHIR DASHBOARDS

Meeting Notes

Backlog

The following are tickets that have action items (waiting for input, assigned to WGM or email outreach) that need to be completed prior to discussing again.

  • FHIR-40765 - Getting issue details... STATUS Now that FHIR-26674 is closed, what about this? 
    • 5/15 - added to the block vote since Elliot cannot retract the comment and it was resolved by FHIR-26674.  Unable to mark it duplicate b/c the other issue is already voted on.  Marked this Not Persuasive as it was handled by FHIR-26674.
  • FHIR-39448  
    • This ticket was reopened after R5 publication
    • We reviewed the previous proposed changes and confirmed that the changes still need to be made
    • Robert Hausam will add to the list of proposed changes if any additional changes are required; and we will discuss next time.
    • 5/15 - added to the block vote with an addition; Bas removed his in-person as the suggested changes were adequate; and we added that the author may 
  • FHIR-38985
    • WGM Work: FHIR-38985 - What happens if the definition deviates from the Observation? TRIAGED
      • With the removal of Instantiates[x] from Observation - this issue will be moved to the extension
      • Extension definition will need to be updated: 
        • If inconsistent - an error can be thrown
        • From OO resources - the deviation can be added as a rule/constraint
        • Review of Extensions - on the stats page – GG to send this out again
        • 5/15 - will give GG a week to get back to us on this action item
  • FHIR-38833
    • This ticket was reopened after R5 publication
    • Added to the FHIR-I session at WGM on Thursday Q2
    • See if we can get FHIR-I to add another time slot for Rob to participate
    • WGM Work: FHIR-38633 - Target Awareness Element or Extension TRIAGED
      • For R5 the proposal for an extension was to get some experience with the requirement; we should reconsider the proposed disposition 
      • Should this be "Communication" instead of a separate extension that was proposed for R5
        • Actual communication with the patient should use the Communication resource.
          • user (patient/clinician) acknowledges the communication by marking the action in a system
        • Flag the awareness of the patient b/c that the information was presented to the patient but there is no systematic acknowledgment
        • Lesser fidelity communications – push the communication but receipt is unknown (e.g., "null" flavor)
        • Need to raise across resources on how to capture 
      • 5/15 - will give GG a week to get back to us on this action item
  • Stale trackers (2x asks for info or lack of activity)
    • FHIR-14722 - Getting issue details... STATUS
      • 5/15 - added to the block vote as Not Persuasive
    • FHIR-15726 - Getting issue details... STATUS
      • 5/15 - added to the block vote as Not Persuasive
  • Easy fix or compare with present state (already done) 
    • FHIR-14781 - Getting issue details... STATUS
      • 5/15 - Task - there is a state machine in two places in the Task resource.  
      • Persuasive with Modification
        • Move/Merge the content in Section 12.1.2.2 Task State Machine to Section 12.1.8 Task state machine.
        • Added to block vote 
    • FHIR-16368 - Getting issue details... STATUS
      • 5/15 - Decided to take care of this here as it is more of an administrative issue than substantive.
      • Not Persuasive
        • DeviceComponent has been deprecated, there is not a reason to reference it the Device Boundaries and Relationships.
        • Added to block vote.
    • FHIR-41255 - Getting issue details... STATUS
      • 5/15 - missing the value-string search parameter and will add
      • TC - Persuasive
        • Will fix by adding the value-string search parameter
        • Assigned to JD
    • FHIR-41250 - Getting issue details... STATUS
      • 5/15 - missing the version search parameter and will add
      • TC - Persuasive
        • Will fix by adding the value-string search parameter
        • Assigned to JD
    • FHIR-40266 - Getting issue details... STATUS
      • Asked for examples on May 4, 2023 and follow-up on May 9, 2023
      • Find Not Persuasive if we cannot get the use cases from Joakim Antus to substantiate the need
      • Added to block vote to see if there are any updates from the submitter and/or it is pulled again for discussion
    • FHIR-32154 - Getting issue details... STATUS
      • Added to block vote with the current disposition of Persuasive
    • FHIR-25552 - Getting issue details... STATUS
      • Should have the same resolution as FHIR-25554
      • Not Persuasive 
        • Added to block vote 
    • FHIR-36401 - Getting issue details... STATUS
      • All of the comments from the submitter were addressed in the disposition
      • Added to block vote
    • FHIR-36305 - Getting issue details... STATUS
      • All of the comments from the submitter were addressed in the disposition
      • Added to block vote

Block Vote will go out between now and Thursday, May 18 and be on the agenda for discussion on May 25, 2023.  Currently the Block has 15 issues.

-------------Adjourned at 3:01 PM EDT----------------

Follow-up on Future Calls

  • FHIR-34207 - Need to follow up with Hans and Dan