Does the subscriber need to subscribe to syncerror event?

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Event Notification Errors
    • Hide

      Discussed during HL7 Connectathon with Isaac, Bas, and Will.

       

      Agreed that subscribers should subscribe to a syncerror event because not all systems will care or know how to handle them, so we shouldn't automatically send out sync error events. Only send them to those apps that care and have subscribed.

       

      We will also clarify that the subscriber can send a syncerror notification to the hub, just like a normal Request for Context Change, to inform the hub that they were unable to change context. This is to handle the cases where a subscriber cannot synchronously change their context in response to an event notification so the HTTP response will just represent receiving the notification, not acknowedgement of actually changing context.

      Show
      Discussed during HL7 Connectathon with Isaac, Bas, and Will.   Agreed that subscribers should subscribe to a syncerror event because not all systems will care or know how to handle them, so we shouldn't automatically send out sync error events. Only send them to those apps that care and have subscribed.   We will also clarify that the subscriber can send a syncerror notification to the hub, just like a normal Request for Context Change, to inform the hub that they were unable to change context. This is to handle the cases where a subscriber cannot synchronously change their context in response to an event notification so the HTTP response will just represent receiving the notification, not acknowedgement of actually changing context.

      Does the subscriber need to subscribe to syncerror event?

      Existing Wording:

      All standard events are defined outside of the base FHIRcast specification in the Event Catalog with the single exception of the infrastructural syncerror event.

            Assignee:
            William Maethner
            Reporter:
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: