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

Prevent missing close events when resubscribing

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • STU
    • Subscribing and unsubscribing [deprecated]
    • Hide

      We will update the multi-anchors scenario page to encourage implementers to consider closing all contexts between disconnecting and re-subscribing to prevent an orphan'd tab.

      Show
      We will update the multi-anchors scenario page to encourage implementers to consider closing all contexts between disconnecting and re-subscribing to prevent an orphan'd tab.
    • Bas van den Heuvel / Trent Nolin: 7-0-0
    • Clarification
    • Non-substantive

    Description

      To improve user experience, Hubs SHOULD follow a successful subscription with an event notification informing the newly subscribed application of the most recent *-open event for which no *-close event has occurred, according to the app's subscription. Hubs that implement this feature, SHALL NOT send an app events to which it is not subscribed.

      This might result in missing the most recent close event. So the client behavior should be that no patient is selected unless a -open event is received. When not using the GET endpoint. How long does a client need to wait before it can determine that the patient has been closed?

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: