Loading...

XML

Word

Printable

JSON

Specification:

FHIRCast (FHIR)
Raised in Version:

current
Work Group:

Infrastructure & Messaging
Related URL:
https://build.fhir.org/ig/HL7/fhircast-docs/2-9-GetCurrentContext.html
Related Page(s):

Get Current Context
Grouping:
- Fit-For-Teleconference
Resolution Description:
Hide

At least one needs to be implemented.

Options are

We can mandate one to be implement (say in configuration which one is supported).

We can mandate resent of current context upon subscription (2.4.4)

We can mandate GetCurrentContext (2.9)

Mandate both.

The implementation of GetCurrentContext is considered as being easier on hub as well as client. As such will:

remove section 2.4.4. from the specification (to prevent race condition).

change section 2.9 to state that implementing GetCurrentContext is REQUIRED.
Show
At least one needs to be implemented. Options are We can mandate one to be implement (say in configuration which one is supported). We can mandate resent of current context upon subscription (2.4.4) We can mandate GetCurrentContext (2.9) Mandate both. The implementation of GetCurrentContext is considered as being easier on hub as well as client. As such will: remove section 2.4.4. from the specification (to prevent race condition). change section 2.9 to state that implementing GetCurrentContext is REQUIRED.
Change Category:
Correction
Change Impact:
Non-compatible
Applied for Version:

current

It seems that the standard heavily relies on getCurrentContext being available.

But the spec leaves this functionality as optional.

Is it possible to have a reliable FHIRcast session without a getCurrentContext endpoint? Should it become mandatory?

relates to

FHIR-36980 GetCurrentContext is not extensible to multiple anchor context scenarios

FHIR-36890 GetCurrentContext is primarily used for content sharing, and shouldn't be required or implied to be required for context sync.

FHIR-37085 Strengthen requirement for GET call