FHIR Chat · Custom _query=name&parameter1=foo&parameter2=bar · implementers

Stream: implementers

Topic: Custom _query=name&parameter1=foo&parameter2=bar


view this post on Zulip Nathan Hall (Nov 13 2018 at 20:03):

I have some custom parameter names that are needed from a third part (filterByAge=true&ageInDays=1000)y. If I want to pass those along, would I do something like

/MedicationRequest?_query=customName&filterByAge=true&ageInDays=1000

or something else?

view this post on Zulip Nathan Hall (Nov 13 2018 at 20:09):

would i make a custom operation for this?

view this post on Zulip Lloyd McKenzie (Nov 13 2018 at 21:51):

_query may end up getting deprecated as it's largely redundant with custom operations - and custom operations are more clearly defined. So I'd encourage going the custom operation route.

view this post on Zulip Brian Postlethwaite (Nov 13 2018 at 21:53):

These sound more like custom search parameters, which are really no different to normal search parameters, defined with the Search Parameter resource on the server.


Last updated: Apr 12 2022 at 19:14 UTC