FHIR Chat · reverse chaining on unspecific ResourceType · implementers

Stream: implementers

Topic: reverse chaining on unspecific ResourceType


view this post on Zulip Simone Heckmann (Sep 06 2018 at 11:46):

Is this allowed: [baseurl]?_has:Provenance:target:entity=1234
Use case: I want to see all Resources that have been created from one specific entity, without knowing of what types these may be.

view this post on Zulip John Moehrke (Sep 06 2018 at 11:55):

How is that different than searching for Provenance records given that entity; then following the Provenance.target element? I am doing it in two steps, you want one?

view this post on Zulip Simone Heckmann (Sep 06 2018 at 13:10):

Basically yes, it's the same. I was just wondering if my example was syntactically allowed. The description of the _has parameter isn't conclusive on the matter. Your proposal could be the workaround in case it isn't :)

view this post on Zulip René Spronk (Sep 06 2018 at 13:25):

Looks legit to me.

view this post on Zulip Alexander Zautke (Sep 06 2018 at 13:45):

_has is defined as a parameter for all resources. Therefore, with regard to the last sentence of section 2.21.0.15.1 Variant Searches, it should be valid.

view this post on Zulip John Moehrke (Sep 06 2018 at 14:20):

I was mostly seeing if I understood the use-case. I can see value in the use of _has here.

view this post on Zulip Patrick Werner (Sep 06 2018 at 17:38):

hapi doesn't support it, but VONK supports it i think


Last updated: Apr 12 2022 at 19:14 UTC