Request for Context Change respones should be a 202, not just any successful HTTP response. (2xx)

XMLWordPrintableJSON

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

      This is a duplicate issue. We already voted (and implemented) this change:

      >If the Hub URL supports FHIRcast and is able to handle the subscription or unsubscription request, the Hub SHALL respond to a subscription request with an HTTP 202 "Accepted" response to indicate that the request was received and will now be verified by the Hub.

      Show
      This is a duplicate issue. We already voted (and implemented) this change: >If the Hub URL supports FHIRcast and is able to handle the subscription or unsubscription request, the Hub SHALL respond to a subscription request with an HTTP 202 "Accepted" response to indicate that the request was received and will now be verified by the Hub.
    • Isaac Vetter/Eric Martin: 16-0-2
    • Correction
    • Compatible, substantive

      We should change the response to a context change request to be more specific – an HTTP 202 to better clarify the intent that the event has been accepted, but not yet acted on by the Hub

      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.

      Proposed Wording:

      The Hub SHALL either accept this context change by responding with an HTTP 202 Accepted or reject it by responding with any 4xx or 5xx HTTP status.

            Assignee:
            Unassigned
            Reporter:
            Isaac Vetter
            Isaac Vetter
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: