Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
STU
-
Get Current Context
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Clarification
-
Compatible, substantive
-
Yes
Description
GetCurrentContext is primarily used for content sharing, and shouldn't be required or implied to be required for context sync.
Maybe move it out of "FHIRcast specification" ?
Attachments
Issue Links
- is voted on by
-
BALLOT-35069 Negative - Christopher Schaut : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35732 Negative - Vassil Peytchev : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35757 Negative - Kimberly Herman : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36066 Negative - Amit Popat : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36239 Negative - Daniel Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36289 Negative - David Sundaram-Stukel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36318 Negative - Chris Courville : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36368 Negative - Danielle Friend : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36393 Negative - Cooper Thompson : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36418 Negative - Isaac Vetter : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36264 Negative - Thanos Tsiolis : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36343 Negative - Daniel Rutz : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
- relates to
-
FHIR-36980 GetCurrentContext is not extensible to multiple anchor context scenarios
- Triaged
-
FHIR-41034 Should getCurrentContext be mandatory?
- Waiting for Input
-
FHIR-37085 Strengthen requirement for GET call
- Deferred