Success full processing could be handled with a new syncerror type event, e.g. message-processed.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Event Notification
    • Hide

      A Subscriber may respond to an event notification with an HTTP 200 indicated that it is able to implement the context change or an HTTP 202 (Accepted) to indicate that it has  successfully received the event notification, but has not yet taken action. If the subscriber attempts and fails to follow the context described in the event notification, it SHOULD send a syncerror event to the hub documenting this failure in synchronization. 

      Also see question FHIR-25851 where this is also described.

      Show
      A Subscriber may respond to an event notification with an HTTP 200 indicated that it is able to implement the context change or an HTTP 202 (Accepted) to indicate that it has  successfully received the event notification, but has not yet taken action. If the subscriber attempts and fails to follow the context described in the event notification, it SHOULD send a syncerror event to the hub documenting this failure in synchronization.  Also see question FHIR-25851 where this is also described.
    • Eric Martin / Bill Wallace: 8-0-0
    • Correction
    • Compatible, substantive

      This requires the application to decide and report this within the context of the http call.
      This basically requires the hub to send all events in parallel and not in turn. In the case of user interaction, this might take some time, even more than 30 seconds. Especially as there. might be more than application requesting this…
      As indicated above. The HTTP response should mean message received. Success full processing could be handled with a new syncerror type event, e.g. message-processed.

      Existing Wording:

      If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber SHALL respond with an HTTP error status code as described in Event Notification Response. If the Hub does not receive a successful HTTP status from a event notification, it SHOULD generate a syncerror event to the other subscribers of that topic. A syncerror notification has the same structure as the other event notification with a single FHIR OperationOutcome as the event's context.

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

              Created:
              Updated:
              Resolved: