FHIR Chat · Chained parameters in _filter search language · implementers

Stream: implementers

Topic: Chained parameters in _filter search language


view this post on Zulip Mattias Flodin (Dec 28 2017 at 16:19):

In the Chained parameters section of the search documentation, it talks about chained parameters that reference multiple possible resource types that share a name, and states that "Servers SHOULD reject a search where the logical id refers to more than one matching resource across different types. For example, the client has to specify the type explicitly using the syntax in the second example above." Where the syntax in question is:

GET [base]/DiagnosticReport?subject:Patient.name=peter

Now I'm wondering, what would this requirement look like in the _filter search language? I'm assuming the same requirement exists there. Would I do something like

GET [base]/DiagnosticReport?_filter=subject[type eq Patient].name eq peter

?

view this post on Zulip Grahame Grieve (Dec 28 2017 at 21:26):

I don't know, actually. i would think we'd still want the same underlying rule


Last updated: Apr 12 2022 at 19:14 UTC