Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR R5 Subscriptions Backport (FHIR)
-
1.2.0-ballot
-
FHIR Infrastructure
-
STU
-
Channels
-
-
Clarification
-
Non-substantive
Description
In several of the interaction diagrams, creating a subscription with and without a handshake is described. The diagrams include an arrow from the server to the client communicating the Subscription.status.
For the non-handshake case, this is straightforward, the Subscription.create response just has the Subscription with status=active, or a reference to the Subscription with a status = active (depending on the prefer header.
But when there is a handshake, how is the Subscription.status=accepted communicated to the client? Does the client need to subscribe to their Subscription resource to know when it has been accepted? (kidding - that's turtles all the way down) Or will the client just poll on their Subscription to see if it got accepted or rejected?
Attachments
Issue Links
- is voted on by
-
BALLOT-58162 Negative - Christopher Schaut : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59187 Negative - Vassil Peytchev : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59211 Negative - Kimberly Herman : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59225 Negative - Daniel Rutz : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59250 Negative - Danielle Friend : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59264 Negative - Cooper Thompson : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59278 Negative - David Sundaram-Stukel : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59326 Negative - Chris Courville : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
-
BALLOT-59340 Negative - Amit Popat : 2024-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU
- Balloted
- relates to
-
FHIR-43613 Apply Subscription changes from backport IG ballot to FHIR Core
- Triaged