Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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


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 (

  •  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:


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.


 Next agenda

 Adjourned at