FHIR Chat · URL endpoint for context change requests? · FHIRcast

Stream: FHIRcast

Topic: URL endpoint for context change requests?


view this post on Zulip Jesper Dam (Jan 04 2022 at 11:19):

Not sure if this is the right forum to ask, but as far as I can tell, the FHIRCast spec says that to request a context change, an application should send a POST to the hub.url URL (the same endpoint as you use to subscribe/unsubscribe)

However, all the examples seem to append a topic identifier to the URL when sending context change requests.
That is, to subscribe they POST to https://hub.example.com, and then to request a context change they POST to https://hub.example.com/someguid.

As far as I can tell, both the sandbox github code and the example code listings in the STU2 spec do this. I just can't find anywhere in the actual specification which says to use this separate endpoint.

So which is correct? Should the topic be appended to hub.url when requesting context change? And if so, can anyone point to where in the specification this is mandated?

Thanks in advance

view this post on Zulip Isaac Vetter (Jan 07 2022 at 05:55):

Hey Jasper -- wow, that's a great observation. The normative language of the specification takes precedence. I believe that the hub.url is the address to which context requests should be made, not hub.url/hub.topic. A careful reading of the example in the spec does show that the guid-looking path at which the context change request is made is different from previous examples of the hub.topic guid. Regardless, would you mind logging a jira issue against FHIRcast for this? As you describe, the current examples are misleading.


Last updated: Apr 12 2022 at 19:14 UTC