Does the hub decide to accept/reject context change? Based on what grounds?

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Request Context Change
    • Hide

      First, please note that the immediate HTTP 4xx or 5xx returned by the Hub is the acceptance of the context change request HTTP "message". 

      We will update the specification to clarify that a successful (2xx) immediate, synchronous HTTP response by the Hub does not necessary acceptance of the context change itself, rather simply a communication-level ack. 

      >Does the hub decide to accept/reject context change? Based on what grounds?

      FHIRcast defines the communication of the acceptance/rejection of a requested context change. How this decision is made is not specified.

      The specification does not enumate the grouds on which a Hub may reject context change requests. 

      Show
      First, please note that the immediate HTTP 4xx or 5xx returned by the Hub is the acceptance of the context change request HTTP "message".  We will update the specification to clarify that a successful (2xx) immediate, synchronous HTTP response by the Hub does not necessary acceptance of the context change itself, rather simply a communication-level ack.  >Does the hub decide to accept/reject context change? Based on what grounds? FHIRcast defines the communication of the acceptance/rejection of a requested context change. How this decision is made is not specified. The specification does not enumate the grouds on which a Hub may reject context change requests. 

      Does the hub decide to accept/reject context change? Based on what grounds?
      Is it the role of the hub to determine this? If so how to do this in a multi-authorisation scheme environment?

      Existing Wording:

      The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.

            Assignee:
            Isaac Vetter
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: