FHIR Chat · bundle resource within a bundle · implementers

Stream: implementers

Topic: bundle resource within a bundle


view this post on Zulip Bapi Behera (Jul 06 2021 at 16:20):

When the API is called with NDC, the response is a bundle with bundle-type=Search Results
However, when the API called with RxCUI, it has multiple NDC - Can we make the bundle resource in a bundle resource? In other words, how to return the multiple bundle resources in a single source?

view this post on Zulip Lloyd McKenzie (Jul 06 2021 at 16:57):

A search always returns all results in a single Bundle. There is no 'group by' functionality to organize the results into sub-bundles. The only way to get back Bundles in a search is to be searching the Bundle endpoint for pre-existing stored Bundles.

view this post on Zulip Gino Canessa (Jul 07 2021 at 18:45):

We have been exploring a similar issue for batched notifications (e.g., I need to send 'x' primary resources and each one may have additional resources included). So far, the options have been creating a list in the notification (e.g., MessageHeader.focus), doing the same but with a graph of sorts (to allow defined relationships for things like the same resource being included twice), or adding annotations to Bundle.entry (e.g., how Bundle.entry.search.mode works today).

As of right now I would lean towards an extension on Bundle.entry since it would allow for much more general use (a similar issue has been brought up in the current Argonaut Write project - in a call to add/update one resource it can be useful to include additional info for the server case it needs the data).

It seems that an extension such as bundle-entry-grouping would check most of those boxes alone, though we may also need something equivalent to the current Bundle.entry.search.mode in order to identify a primary vs. included resource. (Sorry, thinking as I am typing =).. Or, we could bake that into the grouping itself, e.g., if the grouping is an ID it implies the primary resource included.


Last updated: Apr 12 2022 at 19:14 UTC