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

Why not sending the Event Notification Response as an event?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - No Change (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related Page(s):
      (NA)
    • Related Section(s):
      Event Notification
    • Grouping:
    • Resolution Description:
      Hide

      Bas wishes to retract comment, per conversation during May, 2020 FHIR Connectathon

      Show
      Bas wishes to retract comment, per conversation during May, 2020 FHIR Connectathon
    • Resolution Vote:
      Eric Martin / Bill Wallace: 8-0-0

      Description

      Why not send the response as an event? The HTTP status code would be – event received. The event would be status updated.

      Existing Wording:

      For websocket subscriptions, the id of the event notification and the HTTP status code is communicated from the client to Hub through the existing websocket channel, wrapped in a json object. Since the websocket channel does not have a synchronous request/response, this id is necessary for the Hub to correlate the response to the correct notification.
      Feedback from implementers is requested here. This is the only proposed communication from the subscriber to the Hub over websockets and the use of an HTTP status within a websocket connection, wrapped in json is weird. However, it seems important to enable the Hub to optionally track and/or broadcast synchronization state.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bvdh Bas van den Heuvel
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: