Stream: implementers
Topic: List or Bundle for related resources
Yunwei Wang (Jun 29 2021 at 20:44):
I have a collection of FHIR PlanDefinitions. Now I am going to develop a customized operation which returns related PlanDefinitions for a given one. The purpose is that when client select a PlanDefinition, the server will provide, "you may also want to check these related plans". Such relationships are pre-calculated using PlanDefinition's characterization, such as purpose, target, etc. When I return the result of related PlanDefinitions, should the result be a List or a Bundle?
Lloyd McKenzie (Jun 29 2021 at 21:21):
My leaning would be a searchset bundle. You could even define the operation as a _query. That's more or less what it is.
Lloyd McKenzie (Jun 29 2021 at 21:22):
That would also give you paging control.
Yunwei Wang (Jun 30 2021 at 14:19):
Thanks @Lloyd McKenzie Interesting idea about using _query. I checked FHIR spec but there is not much content about _query search. Assume I create a OperationDefinition "foo" with type _query. Since it is defined as a operation but used as search parameter, should I indicate that in CapabilityStatement's searchParam section or operation section?
And how do I specify which "regular" search parameters can be appended to _query=foo? For example, _count is allowed but no others.
Lloyd McKenzie (Jun 30 2021 at 14:36):
I think we have a tracker item about that. I vaguely recall that whatever search parameters you support at the 'base' or for the resource you invoke the operation from, it's expected you'd also support for the operation. Would that work for you?
Last updated: Apr 12 2022 at 19:14 UTC
