FHIR Chat · Search with Multiple Parameters · implementers

Stream: implementers

Topic: Search with Multiple Parameters


view this post on Zulip Shahzeb Jadoon (Oct 08 2019 at 12:42):

Dear All,

I implemented search for Patient id and it works fine but i am stuck with multiple parameters. I do not know search will work with multiple parameters.
I want to send all these parameters:
ConditionParameters.png

view this post on Zulip Lloyd McKenzie (Oct 08 2019 at 13:40):

There's not a whole lot of point sending the other parameters if you're also sending _id, as that locks you to a single record. However, nothing keeps you from doing what you're doing so long as you fill in all the variables.

view this post on Zulip Emilia Branny-Jankowska (Nov 18 2020 at 16:59):

Dear Colleagues, let me say 'hello' and ask a question here..
In US Core there are multiparameter searches, but the specific comparators, modifiers, chains, multipleAND and multipleOR etc. are defined per parameter in the relevant SearchParamater JSONs. If I implement US Core as organization, I do not want to support single parameter search, but need to highlight which comparators can be used in multiparameter search - how do I do it?
I would link to a search parameter definition JSON, but - not supporting a standalone search by this parameter - I can see no good way of linking the JSON from the Capability Statement...
Any ideas, solutions, please?

view this post on Zulip Yunwei Wang (Nov 18 2020 at 18:11):

If you want to implement US Core, then you have to implement all the "SHALL" search parameters (single or combined). You do have flexibility to choose which "SHOULD" parameters you would like to support.

view this post on Zulip Emilia Branny-Jankowska (Nov 19 2020 at 16:54):

Thank you, @Yunwei Wang My question is actually about comparators, as well as e.g. multipleAND, multipleOR which are SHOULD or MAY. If I implement those for a search parameter, I publish a Search Parameter JSON with supported comparators and link to it in my search parameter definition in Capability Statement.
But if it is only a multiparameter search where I support these comparators (I do not support a search on date as such), I no longer have the search parameter listed in my capability statement, so cannot link the JSON. Does it mean that for multiparameter searches the clients should be guessing which comparators they could use on my server and just try them out?

view this post on Zulip Yunwei Wang (Nov 19 2020 at 19:25):

search-parameter-combination is a combination of individual parameters. You cannot add a non-existing parameter to a combination.


Last updated: Apr 12 2022 at 19:14 UTC