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)
ManagementQuorum reached (co-chair + 2) Yes/No

Management Minute Approval


Head's up! USA Daylight Savings ends on Sunday. This call will be one hour earlier for you starting next week. 

Methodology

Progress towards publication

Balloted triaged: 64

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.


[FHIR-36910] persistent, pre-existing findings across systems ? - Jira (hl7.org)

Eric to propose path forward for: [FHIR-36910] persistent, pre-existing findings across systems ? - Jira (hl7.org)



FHIR-36792 - DxReport-select doesn't select DxReports ... TRIAGED

Eric to propose path forward for FHIR-36792 - DxReport-select doesn't select DxReports ... TRIAGED



[FHIR-36910] persistent, pre-existing findings across systems ? - Jira (hl7.org)

Content-sharing clarifications

  1. Delete action: should implementing clients consider a delete as an "undo", or a removal of the key/value entirely.
    1. E.g. in the case when an app has an existing value, which is then updated interoperably, then deleted interoperably, should the app revert to the existing value or delete the value entirely?
    2. Note this jira: [FHIR-36910] persistent, pre-existing findings across systems ? - Jira (hl7.org)
    3. Kamal: individual apps with pre-existing finalized findings should probably reject modifuication to those findings (perhaps except statuses of amending). We don't want FHIRcast to dicate this behavior, because we think they're business rules of the application. 

During WG discussion, we wrote and proposed a potential resolution to – [FHIR-36910] persistent, pre-existing findings across systems ? - Jira (hl7.org)



Logout valueset issue - 

  • New valueset for logout reason is here: Reasons for sending a logout event. - FHIRcast v3.0.0
  • Can we add:
    • system-initiated vs user-initiated is meaningful because applications should consider user-initiated logouts as stronger guidance to close the session, than system initiated. Further, some system initiated logout reasons reasonably indicate distinct application behavior. Specifically:   
      • 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.
  • And change system-initiated
    • Definition to: The application in active use by the user, or the Hub has initiated the logout.


  • Alex to validate need for system-downtime code. (e.g. are you sure an app can send a system-downtime logout while it's down?)
  • Update valueset
  • Test at some industry testing event. 

 

Alex confirms that his system does have an edge-case in which a system-downtime is able to be communicated and means that additional processing of messages will fail.

Next steps:

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. 



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