FHIR Chat · duplicates with _include

Stream: implementers

Topic: duplicates with _include

Caitlin Voegele (Jan 20 2022 at 18:56):

When using _include in search, is there a place in the spec that specifies that a single resource shouldn't be returned twice as "matched" and "included" in the search results? If you only have one returned, what should the search be ("matched" or "included") on the resource?

Gino Canessa (Jan 20 2022 at 19:00):

I don't know of a place that it is specified cleanly, but the Constraints on bundle include a combination of rules that I believe force it:

fullUrl must be unique
fullUrl cannot be version specific

In the comments for Bundle.entry.search.mode, there is the line:

There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.

So, while well-hidden, match takes priority.

Caitlin Voegele (Jan 20 2022 at 19:05):

Gino Canessa said:

I don't know of a place that it is specified cleanly, but the Constraints on bundle include a combination of rules that I believe force it:

fullUrl must be unique

fullUrl cannot be version specific

In the comments for Bundle.entry.search.mode, there is the line:

There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.

So, while well-hidden, match takes priority.

Thanks @Gino Canessa !

Elliot Silver (Jan 20 2022 at 19:18):

Although, it might be included as a match on one page, and an include on another page of the search.

Last updated: Apr 12 2022 at 19:14 UTC