Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
STU
-
Subscribing and unsubscribing [deprecated]
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Clarification
-
Non-substantive
Description
To improve user experience, Hubs SHOULD follow a successful subscription with an event notification informing the newly subscribed application of the most recent *-open event for which no *-close event has occurred, according to the app's subscription. Hubs that implement this feature, SHALL NOT send an app events to which it is not subscribed.
This might result in missing the most recent close event. So the client behavior should be that no patient is selected unless a -open event is received. When not using the GET endpoint. How long does a client need to wait before it can determine that the patient has been closed?
Attachments
Issue Links
- is voted on by
-
BALLOT-35217 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35895 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36037 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36133 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36204 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36491 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35824 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35966 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted