Details
-
Change Request
-
Resolution: Considered for Future Use
-
Highest
-
FHIRCast (FHIR)
-
2.1.0-ballot [deprecated]
-
Infrastructure & Messaging
-
Get Current Context
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
Description
http://hl7.org/fhir/uv/fhircast/2022MAY/2-9-GetCurrentContext.html
Hubs MAY support returning the current context of a session, as defined below.
Suggest to make this a SHOULD:
Hubs SHOULD support returning the current context of a session, as defined below.
Attachments
Issue Links
- is voted on by
-
BALLOT-35222 Affirmative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35819 Affirmative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35890 Affirmative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35961 Affirmative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36032 Affirmative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36128 Affirmative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36199 Affirmative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36486 Affirmative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
- relates to
-
FHIR-41034 Should getCurrentContext be mandatory?
- Waiting for Input
-
FHIR-36890 GetCurrentContext is primarily used for content sharing, and shouldn't be required or implied to be required for context sync.
- Applied
- mentioned in
-
Page Loading...