Clarify that context change requests are successful upon Hub's broadcast of them

XMLWordPrintableJSON

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

      Based on the comments and proposed resolution in FHIR-25857, we should make this more clear as described in this request.

      Accept the Proposed Resolution that broadcast by the Hub of a requested context change is confirmation to the requestor that the change is made to the shared session.

      Consider adding an additional diagram to better illustrate this flow. 

      Show
      Based on the comments and proposed resolution in FHIR-25857 , we should make this more clear as described in this request. Accept the Proposed Resolution that broadcast by the Hub of a requested context change is confirmation to the requestor that the change is made to the shared session. Consider adding an additional diagram to better illustrate this flow. 
    • Isaac Vetter / Eric Martin : 5-0-0
    • Clarification
    • Non-substantive

      We should clarify that a Hub can respond with a 2xx/202, but still ignore a context change request and that the indication of success is the broadcast of that event notification.

      Existing Wording:

      Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.

      Proposed Wording:

      Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor. A requested context change may not be accepted, even following an HTTP 202.

            Assignee:
            William Maethner
            Reporter:
            Isaac Vetter
            Isaac Vetter
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: