Date:   

Facilitator:  @

Note Taker: @ 

Attendees

Present

Name

Affiliation


Anthony Julian Co-chair

Mayo Clinic

Nick Radov Co-chair

United Healthcare

Isaac Vetter  Co-chair

Epic

Brian Frankl  Co-Chair

Surescripts

Alex Liu 

Epic

Bas van den Heuvel 

Phillips

Catherine Ladd 

Microsoft

Christopher Carr 

Siemens

Craig Newman

Altarum     

David QuiEpic

Eric Martin 

Siemens

Kamalanathan Gnanadesikan 

Microsoft

Ulrike Merrick

Vernetzt, LLC

Gino Canessa 



Paulius Galinauskas 

Canon



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

Decision Link(if not child)

No InM call next week.

ManagementQuorum reached (co-chair + 2) Yes/No

Management Minute Approval

Methodology

Progress towards publication

Balloted triaged: 66

Balloted submitted: 0

Balloted undone: 84

Unballoted, and undone: 71


Add Jira Grouping of "Fit-for-teleconference" (or Scheduling = "NextCall")to put issues in a queue for discussion.

Next steps:

  • Read through undone jiras
  • Add a proposed resolution to Jira, or even in comments
  • Add Jira Grouping of "Fit-for-teleconference" to put issues in a queue for discussion.


For the resolution of: [FHIR-43040] change logout valueset to better differentiate between system events - Jira (hl7.org)

  • Bas van den Heuvel to Update this  value set with these values:
    • system-initiated: The application in active use by the user, or the Hub has initiated the logout.
      • system-timeout:
        • Definition: System initiated logout. Implies that system will reasonably be available in the near future.
        • Display: "Automated logout due to user inactivity"
      • system-downtime:  
        • Definition:System initiated logout. Implies that additional processing of messages will likely fail.
        • Display:"Temporarily unavailable due to system maintenance"
      • system-error:
        • Definition: System initiated logout.Implies that additional processing of messages will fail.
        • Display: "System encountered error resulting logging out the user. System is unavailable.
    • user-initiated: The user initiated the action. 




 Eric has a PR related to: FHIR-36792 - Getting issue details... STATUS




Review block-vote-5 for scheduling. 




Alex – this Hub capability seems super hard --

Processing Update Events and Current Context

A FHIRcast Hub SHALL process a [FHIR resource]-update event even if the anchor context referenced differs from the current context (the anchor context is present in the context attribute in [FHIR resource]-update events). The proposed [FHIR resource]-update event SHALL be processed in scope of the referenced context (not the current context) following the same rules as if the referenced context were the current context. The current context is not changed by a [FHIR resource]-update event that references an anchor context that is not the current context.





Kamal: this would result in an error for our Hub. 

Paul: is this a multi-tab scenario?

Kamal: from a clinical safety perspective, it seems important to not update a context that's not in-focus. 

Alex: agreed.

We think that this behavior should definitely not be mandated on Hubs, and should probably not be allowed.


Management

 Next agenda



 Adjournment
 Adjourned at

Supporting Documents

Outline Reference

Supporting Document

Minute Approval
FHIRCast Jira not done

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh


Action items

  •  

InM Work Group