Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-41378

Add rationale to userLogout and userHibernate

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • User hibernate event [deprecated]
      User logout event [deprecated]
    • Hide

      We'll add a new structure to the userLogout and userHibernate of "context" containing a parameter resource. Support of this feature is encouraged for senders, but not required. That resource will contain – 

      We'll define a valueset of reasons for logout and hibernate that the sender of the event can populate to interoperably communicate the initiator of the event. Currently the content of the valueset is: user-initiated, system-initiated. 

      Also, we'll update the definition of userHibernate to explicitly state that it can be the result of: a "session time-out or other reason"

       

       

      Show
      We'll add a new structure to the userLogout and userHibernate of "context" containing a parameter resource. Support of this feature is encouraged for senders, but not required. That resource will contain –  We'll define a valueset of reasons for logout and hibernate that the sender of the event can populate to interoperably communicate the initiator of the event. Currently the content of the valueset is: user-initiated, system-initiated.  Also, we'll update the definition of userHibernate to explicitly state that it can be the result of: a "session time-out or other reason"    
    • Bas van den Heuvel / Eric Martin: 5 - 0 - 0
    • Enhancement
    • Compatible, substantive
    • current

    Description

      Currently, the userLogout and userHibernate events suggest that implementers should consider how to react to these two event.

      http://build.fhir.org/ig/HL7/fhircast-docs/3-2-3-userlogout.html

      However, there is currently no way for a subscriber to specify why they are logging out. For example, if application A wants to log the user out when the user deliberately logs out of application B, but not when application B times out, application B has no way to distinguish between the two when sending a userLogout event.

      Pre applied in FHIR-41378 by bvdh · Pull Request #499 · HL7/fhircast-docs (github.com)

      Attachments

        Activity

          People

            bvdh Bas van den Heuvel
            npandela Nicholas Pandelakis
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: